Vue normale

Reçu aujourd’hui — 3 décembre 2025

Waymo Hits a Dog In San Francisco, Reigniting Safety Debate

Par :BeauHD
3 décembre 2025 à 02:02
A Waymo robotaxi struck a small unleashed dog in San Francisco -- just weeks after another Waymo killed a beloved neighborhood cat. The dog's condition is unknown. The Los Angeles Times reports: The incident occurred near the intersection of Scott and Eddy streets and drew a small crowd, according to social media posts. A person claiming to be one of the passengers posted about the accident on Reddit. "Our Waymo just ran over a dog," the passenger wrote. "Kids saw the whole thing." The passenger described the dog as between 20 and 30 pounds and wrote that their family was traveling back home after a holiday tree lighting event. The National Highway Traffic Safety Administration has recorded Waymo taxis as being involved in at least 14 animal collisions since 2021. "Unfortunately, a Waymo vehicle made contact with a small, unleashed dog in the roadway," a company spokesperson said. "We are dedicated to learning from this situation and how we show up for our community as we continue improving road safety in the cities we serve." The spokesperson added that Waymo vehicles have a much lower rate of injury-causing collisions than human drivers. Human drivers run into millions of animals while driving each year. "I'm not sure a human driver would have avoided the dog either, though I do know that a human would have responded differently to a 'bump' followed by a car full of screaming people," the Waymo passenger wrote on Reddit. One person who commented on the discussion said that Waymo vehicles should be held to a higher standard than human drivers, because the autonomous taxis are supposed to improve road safety. "The whole point of this is because Waymo isn't supposed to make those mistakes," the person wrote on Reddit.

Read more of this story at Slashdot.

Kubernetes Is Retiring Its Popular Ingress NGINX Controller

Par :BeauHD
3 décembre 2025 à 01:01
During last month's KubeCon North America in Atlanta, Kubernetes maintainers announced the upcoming retirement of Ingress NGINX. "Best-effort maintenance will continue until March 2026," noted the Kubernetes SIG Network and the Security Response Committee. "Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered." In a recent op-ed for The Register, Steven J. Vaughan-Nichols reflects on the decision and speculates about what might have prevented this outcome: Ingress NGINX, for those who don't know it, is an ingress controller in Kubernetes clusters that manages and routes external HTTP and HTTPS traffic to the cluster's internal services based on configurable Ingress rules. It acts as a reverse proxy, ensuring that requests from clients outside the cluster are forwarded to the correct backend services within the cluster according to path, domain, and TLS configuration. As such, it's vital for network traffic management and load balancing. You know, the important stuff. Now this longstanding project, once celebrated for its flexibility and breadth of features, will soon be "abandonware." So what? After all, it won't be the first time a once-popular program shuffled off the stage. Off the top of my head, dBase, Lotus 1-2-3, and VisiCalc spring to my mind. What's different is that there are still thousands of Ingress NGINX controllers in use. Why is it being put down, then, if it's so popular? Well, there is a good reason. As Tabitha Sable, a staff engineer at Datadog who is also co-chair of the Kubernetes special interest group for security, pointed out: "Ingress NGINX has always struggled with insufficient or barely sufficient maintainership. For years, the project has had only one or two people doing development work, on their own time, after work hours, and on weekends. Last year, the Ingress NGINX maintainers announced their plans to wind down Ingress NGINX and develop a replacement controller together with the Gateway API community. Unfortunately, even that announcement failed to generate additional interest in helping maintain Ingress NGINX or develop InGate to replace it." [...] The final nail in the coffin was when security company Wix found a killer Ingress NGINX security hole. How bad was it? Wix declared: "Exploiting this flaw allows an attacker to execute arbitrary code and access all cluster secrets across namespaces, which could lead to complete cluster takeover." [...] You see, the real problem isn't that Ingress NGINX has a major security problem. Heck, hardly a month goes by without another stop-the-presses Windows bug being uncovered. No, the real issue is that here we have yet another example of a mission-critical open source program no one pays to support...

Read more of this story at Slashdot.

Donald Trump s’en prend violemment à la Somalie, un « pays pourri » selon lui, et promet de durcir encore plus sa politique d’immigration

Le président américain a multiplié les propos incendiaires contre la Somalie. La semaine dernière, il a annoncé son intention de « suspendre définitivement l’immigration en provenance de tous les pays du tiers-monde ».

© Evan Vucci/AP

Le président américain, Donald Trump, à la Maison blanche, à Washington, le 2 décembre 2025.

L’administration Trump limoge huit juges chargés de l’immigration à New York

Pour les associations de défense des migrants, ces départs, comme les précédents, visent à remplacer ces magistrats par des professionnels plus alignés avec la politique gouvernementale sur l’immigration.

© Eduardo Munoz/REUTERS

Des agents fédéraux devant le 26 Federal Plaza, à New York, le 21 octobre 2025.

Le prénom : « Dire que je m’appelle Charles-Edouard, c’est comme endosser un costume trois-pièces »

Un peu lourd à porter, banal ou original, objet de fierté ou de honte… Nous vivons tous avec un prénom. Oui, mais comment ? En décalage, pour Charles-Edouard Chambon. Ce journaliste de 39 ans résidant à Feurs (Loire) a pâti de ce prénom « trop noble » pour son milieu.

© Nicolas Polli pour « Le Monde »

De nouveaux extraits de gameplay pour Transience avec une IA lobotomisée

Par :Loulou
3 décembre 2025 à 01:30

À l’approche de la sortie Transience, prévue pour le 4 décembre, l’influenceur BigfryTV et son studio RESURGENT ont dévoilé de nouveaux extraits de gameplay de leur FPS d’action et d’infiltration. Autant le gunplay a l’air solide et les environnements sont plutôt réussis, autant l’IA ennemie n’a pas l’air du tout au point. Cette dernière est longue à la détente et ne réplique quasiment pas aux tirs du joueur. Lorsque la slow-motion est activée, on peut comprendre que les ennemis ne puissent pas réagir à temps, mais certains passages (1, 2, 3 ou 4) sont un peu abusés même avec la présence d’un silencieux. Et les ragdolls de nos adversaires sont marrantes à voir, surtout ceux qui sont victimes d’un empoisonnement (1 et 2). Malgré tout, on est toujours aussi impatients de pouvoir y jouer, même si on est conscients que l’IA ne sera pas le point fort du jeu.

Transience est toujours prévu pour le 4 décembre prochain. En attendant sa sortie, vous pouvez l’ajouter à votre liste de souhaits Steam, si vous êtes intéressés.

Bridge returned error 0! (20425)

See https://curl.haxx.se/libcurl/c/libcurl-errors.html for description of the curl error code.

Details

Type: HttpException
Code: 0
Message: cURL error Resolving timed out after 5000 milliseconds: 28 (https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://public.api.bsky.app/xrpc/app.bsky.feed.getAuthorFeed?actor=did%3Aplc%3Atoudj53egawswz2ypw3zyn2u&filter=posts_and_author_threads&limit=30
File: lib/http.php
Line: 185

Trace

#0 index.php(73): RssBridge->main()
#1 lib/RssBridge.php(39): RssBridge->{closure}()
#2 lib/RssBridge.php(37): BasicAuthMiddleware->__invoke()
#3 middlewares/BasicAuthMiddleware.php(13): RssBridge->{closure}()
#4 lib/RssBridge.php(37): CacheMiddleware->__invoke()
#5 middlewares/CacheMiddleware.php(44): RssBridge->{closure}()
#6 lib/RssBridge.php(37): ExceptionMiddleware->__invoke()
#7 middlewares/ExceptionMiddleware.php(17): RssBridge->{closure}()
#8 lib/RssBridge.php(37): SecurityMiddleware->__invoke()
#9 middlewares/SecurityMiddleware.php(19): RssBridge->{closure}()
#10 lib/RssBridge.php(37): MaintenanceMiddleware->__invoke()
#11 middlewares/MaintenanceMiddleware.php(10): RssBridge->{closure}()
#12 lib/RssBridge.php(37): TokenAuthenticationMiddleware->__invoke()
#13 middlewares/TokenAuthenticationMiddleware.php(10): RssBridge->{closure}()
#14 lib/RssBridge.php(34): DisplayAction->__invoke()
#15 actions/DisplayAction.php(54): DisplayAction->createResponse()
#16 actions/DisplayAction.php(89): BlueskyBridge->collectData()
#17 bridges/BlueskyBridge.php(164): BlueskyBridge->getAuthorFeed()
#18 bridges/BlueskyBridge.php(633): getContents()
#19 lib/contents.php(104): CurlHttpClient->request()
#20 lib/http.php(185)

Context

Query: action=display&bridge=BlueskyBridge&data_source=getAuthorFeed&user_id=tristankamin.bsky.social&feed_filter=posts_and_author_threads&include_reposts=on&format=Atom
Version: 2025-08-05 (git.master.6a0cc5b)
OS: Linux
PHP: 8.2.29

Go back

mruac

❌