The Linux kernel AI guidelines are the first sane that I read. It is not a coincidence. Where high level work is done, high level work is pretended, regardless of the tools. github.com/torvalds/lin...

OpenJDK Interim Policy on Generative AI: openjdk.org/legal/ai. This aligns with my experience using GenAI tools: they are good at grasping some dusty context corners, but for surgical OpenJDK work you need to absolutely own every single line you push into the project.

Inteface little snitch for linux

Little Snitch for Linux : un outil de surveillance réseau qui rend visibles les connexions sortantes de vos applications et permet de les contrôler.

👉 github.com/obdev/lit...

Je suis sans voix. Et j'ai beau ne plus travailler là-bas, ca laisse quand même un goût très amer, surtout lorsqu'on connait encore beaucoup de personnes qui y bossent. Ok c'est côté SI, mais ca pique malgré tout. Bon courage pour ton souci en tout cas, même si ca parait mal barré :/

S3 Files and the changing face of S3 Andy Warfield writes about the hard-won lessons dealing with data friction that lead to S3 Files

For two decades, S3 has been an object store, but today it's broader. S3 Files lets you mount any bucket as a file system—Andy Warfield tells the full story; no copies, no sync scripts, no choosing between file and object. www.allthingsdistributed.com/2026/04/s3-f...

The Playground — Lancez votre communauté, organisez vos événements La plateforme gratuite pour créer votre communauté et organiser des événements mémorables.

Petite découverte du jour, une alternative à meetup européenne et gratuite, pour les organisateurs de confs tech par exemple : the-playground.fr

cssDOOM DOOM rendered entirely in CSS. Every wall, floor, barrel, and imp is a div, positioned in 3D space using CSS transforms.

CSS is DOOMed!

I've build DOOM in CSS and every wall, floor, barrel, and imp is a div, positioned in 3D space using CSS transforms.

cssdoom.wtf

Try it out! But... not every browser can handle it. This is taking the browser to its limit. Chrome has some issues. Safari too. Bugs will be filed.

Désormais writizzy.com permet l'usage en équipe, par exemple pour construire des blogs tech. C'est une énorme brique qui s'ajoute au reste !

En plus de l'éditeur de post qui s'est bien amélioré, franchement je m'amuse bien :)

Nvidia hiring for engineers to work on Linux/Arm gaming projects That's a win.

tech.yahoo.com/gaming/artic... : Linux is ready for the gaming ! Nvidia pousse au cul pour améliorer le support de son hardware sous du Linux.

This is one of the @tamboui.dev demo applications, compiled to a native binary using @graalvm.org . It runs natively at 60fps+ (only limited by the refresh rate that is set in the demo) and consumes about 20MB of RAM.

melix.github.io/blog/2026/02...

today’s one-sentence horror:

sudo has been largely maintained by a single person for ~30+ years

The end of the curl bug-bounty tldr: an attempt to reduce the _terror reporting_. **There is no longer a curl bug-bounty program.** It officially stops on January 31, 2026. After having had a few half-baked previous takes, in April 2019 we kicked off the first real curl bug-bounty with the help of Hackerone, and while it stumbled a bit at first it has been quite successful I think. We attracted skilled researchers who reported plenty of actual vulnerabilities for which we paid fine monetary rewards. We have certainly made curl better as a direct result of this: **87 confirmed vulnerabilities and over 100,000 USD** paid as rewards to researchers. I’m quite happy and proud of this accomplishment. I would like to especially highlight the awesome Internet Bug Bounty project, which has paid the bounties for us for many years. We could not have done this without them. Also of course Hackerone, who has graciously hosted us and been our partner through these years. Thanks! ## How we got here Looking back, I think we can say that the downfall of the bug-bounty program started slowly in the second half of 2024 but accelerated badly in 2025. We saw an explosion in AI slop reports combined with a lower quality even in the reports that were not obvious slop – presumably because they too were actually misled by AI but with that fact just hidden better. Maybe the first five years made it possible for researchers to find and report the low hanging fruit. Previous years we have had a rate of somewhere north of 15% of the submissions ending up confirmed vulnerabilities. Starting 2025, the confirmed-rate plummeted to below 5%. Not even one in twenty was _real_. The never-ending slop submissions take a serious mental toll to manage and sometimes also a long time to debunk. Time and energy that is completely wasted while also hampering our will to live. I have also started to get the feeling that a lot of the security reporters submit reports with a _bad faith attitude._ These “helpers” try too hard to twist whatever they find into something horribly bad and a critical vulnerability, but they rarely actively contribute to actually _improve_ curl. They can go to extreme efforts to argue and insist on their specific current finding, but not to write a fix or work with the team on improving curl long-term etc. I don’t think we need more of that. There are these three bad trends combined that makes us take this step: the mind-numbing AI slop, humans doing worse than ever and the apparent will to poke holes rather than to help. ## Actions In an attempt to do something about the sorry state of curl security reports, this is what we do: * We no longer offer any monetary rewards for security reports – no matter which severity. In an attempt to remove the incentives for submitting made up lies. * We stop using Hackerone as the recommended channel to report security problems. To make the change immediately obvious and because without a bug-bounty program we don’t need it. * We refer everyone to submit suspected curl security problems on GitHub using their _Private vulnerability reporting_ feature. * We continue to immediately _ban and publicly_ _ridicule_ everyone who submits AI slop to the project. ## Maintain curl security We believe that we can maintain and continue to evolve curl security in spite of this change. Maybe even improve thanks to this, as hopefully this step helps prevent more people pouring sand into the machine. Ideally we reduce the amount of wasted time and effort. I believe the best and our most valued security reporters still will tell us when they find security vulnerabilities. ## Instead If you suspect a security problem in curl going forward, we advise you to head over to GitHub and submit them there. Alternatively, you send an email with the full report to `security @ curl.se`. In both cases, the report is received and handled privately by the curl security team. But with _no monetary reward offered_. ## Leaving Hackerone Hackerone was good to us and they have graciously allowed us to run our program on their platform for free for many years. We thank them for that service. As we now drop the rewards, we feel it makes a clear cut and displays a clearer message to everyone involved by also moving away from Hackerone as a platform for vulnerability reporting. It makes the change more visible. ## Future disclosures It is probably going to be harder for us to publicly disclose every incoming security report in the same way we have done it on Hackerone for the last year. We need to work out something to make sure that we can keep doing it at least imperfectly, because I believe in the goodness of such transparency. ## We stay on GitHub Let me emphasize that this change does not impact our presence and mode of operation with the curl repository and its hosting on GitHub. We hear about projects having problems with low-quality AI slop submissions on GitHub as well, in the form of issues and pull-requests, but for curl we have not (yet) seen this – and frankly I don’t think switching to a GitHub alternative saves us from that. ## Other projects do better Compared to others, we seem to be affected by the sloppy security reports to a higher degree than the average Open Source project. With the help of Hackerone, we got numbers of how the curl bug-bounty has compared with other programs over the last year. It turns out curl’s program has seen more volume and noise than other public open source bug bounty programs in the same cohort. Over the past four quarters, curl’s inbound report volume has risen sharply, while other bounty-paying open source programs in the cohort, such as Ruby, Node, and Rails, have not seen a meaningful increase and have remained mostly flat or declined slightly. In the chart, the pink line represents curl’s report volume, and the gray line reflects the broader cohort. Inbound Report Volume on Hackerone: curl compared to OSS peers We suspect the idea of getting money for it is a big part of the explanation. It brings in real reports, but makes it too easy to be annoying with little to no penalty to the user. The reputation system and available program settings were not sufficient for us to prevent sand from getting into the machine. The exact reason why we suffer more of this abuse than others remains a subject for further speculation and research. ## If the volume keeps up There is a non-zero risk that our guesses are wrong and that the volume and security report frequency will keep up even after these changes go into effect. If that happens, we will deal with it then and take further appropriate steps. I prefer not to overdo things or _overplan_ already now for something that ideally does not happen. ## We won’t charge People keep suggesting that one way to deal with the report tsunami is to _charge_ security researchers a small amount of money for the privilege of submitting a vulnerability report to us. A _curl reporters security club_ with an entrance fee. I think that is a less good solution than just dropping the bounty. Some of the reasons include: * Charging people money in an International context is complicated and a maintenance burden. * Dealing with charge-backs, returns and other complaints and friction add work. * It would limit who could or would submit issues. Even some who actually find legitimate issues. Maybe we need to do this later anyway, but we stay away from it for now. ## Pull requests are less of a problem We have seen other projects and repositories see similar AI-induced problems for pull requests, but this has not been a problem for the curl project. I believe for PRs we have better much means to sort out the weed with automatic means, since we have tools, tests and scanners to verify such contributions. We don’t need to waste any human time on pull requests until the quality is good enough to get green check-marks from 200 CI jobs. ## Related I will do a talk at FOSDEM 2026 titled Open Source Security in spite of AI that of course will touch on this subject. ## Future We never say never. This is now and we might have reasons to reconsider and make a different decision in the future. If we do, we will let you know. These changes are applied now with the hope that they will have a positive effect for the project and its maintainers. If that turns out to not be the outcome, we will of course continue and apply further changes later. ## Media Since I created the pull request for updating the bug-bounty information for curl on January 14, almost two weeks before we merged it, various media picked up the news and published articles. Long before I posted this blog post. * The Register: Curl shutters bug bounty program to remove incentive for submitting AI slop * Elektroniktidningen: cURL removes bug bounties * Heise online: curl: Projekt beendet Bug-Bounty-Programm * Neowin: Beloved tool, cURL is shutting down its bug bounty over AI slop reports * Golem: Curl-Entwickler dreht dem “KI-Schrott” den Geldhahn zu * Linux Easy: cURL chiude il programma bug bounty: troppi report generati dall’AI * Bleeping Computer: Curl ending bug bounty program after flood of AI slop reports * The New Stack: Drowning in AI slop, cURL ends bug bounties * Ars Technica: Overrun with AI slop, cURL scraps bug bounties to ensure “intact mental health” * PressMind Labs: cURL ko?czy program bug bounty – czy to koniec jako?ci zg?osze?? * Socket: curl Shuts Down Bug Bounty Program After Flood of AI Slop Reports Also discussed (indirectly) on Hacker News.

The end of the #curl bug-bounty

daniel.haxx.se/blog/2026/01/26/the-end-...

Stations and transfers A gallery of drawings depicting the topology of metro stations from different European cities.

Je découvre ce site sur lequel on peut voir toutes les stations de métro de Paris (et d'autres villes) en 3D...

stations.albertguillaumes.cat

Je découvre le site noclip.website sur lequel on peut se promener dans les cartes de beaucoup de jeux.
Attention, c'est très facile de s'y perdre

Pas sûr que cette feature ait beaucoup d'utilisateurs d'ailleurs, un update de CF serait intéressant.

Introducing pay per crawl: Enabling content owners to charge AI crawlers for access Pay per crawl is a new feature to allow content creators to charge AI crawlers for access to their content.

D'un POV purement tech, cela m'evoque le Paywall pour les Bot AI de Cloudflare blog.cloudflare.com/introducing-.... Intéressant dans l'idée, mais avec risques de bypass quoiqu'il arrive, et plus simplement que les sites soit ignorés et donc disparaissent du radar des dev car indispo dans les LLMs.

Ah pas mal ! Je ne l'ai pas encore eu celle-là. A deux doigts du "Et plus vite que ça, feignant".

Et le mode plan est quasiment un indispensable. Tellement pratique de pouvoir affiner le besoin, l'implém, et même souvent avoir des suggestions auxquelles on a pas encore pensé, mais qui sont légitimes.

Le résultat est impressionnant. La machine aurait voyagé en DeLorean, elle n'aurait pas une autre allure.

Le premier intérêt de Kubernetes n'est pas le scaling mcorbin Tech Blog

Sur le blog: Le premier intérêt de Kubernetes n'est pas le scaling

"K8S c’est bien que pour les grosses entreprises", "On est pas Netflix/
Google", "Sans milliers de conteneurs ça sert à rien"…​ Vous avez déjà vu ces commentaires sur K8S ? Ces gens ont tout faux.

mcorbin.fr/posts/2025-1...

Les casques de Réalité Virtuelle (VR) et Réalité Mixte (MR) YouTube video by Deus Ex Silicium

BOUM 💥 Nouvelle grosse vidéo, cette fois consacrée à la réalité virtuelle et dans laquelle j'explique le principe de fonctionnement des casques de réalité virtuelle #VR et mixte #MR avant d'en analyser en détail l'électronique et l'optique 🍿🍿

youtu.be/zfCQ_8-uBy0

👏👏👏

Time to get rid of Windows on my gaming PC. Let's test Bazzite and CachyOS.
I sense significant traction these last months and the annoucement of Steam Machine convinced me to try.

I guess that would be both Struts and Tomcat at the same time on my side.

Spring Boot 4.0.0 available now Level up your Java code and explore what Spring can do for you.

Spring Boot 4.0.0 is out spring.io/blog/2025/11... Congrats team!

TIL: #CGLIB has built-in support for saving generated classes to disk, such as those generated for #Spring #AOP proxies. 😱

Just set the `cglib.debugLocation` JVM system property -- for example:

-Dcglib.debugLocation=build/cglib

Can be quite useful for debugging! 🤓

Spring Framework 7.0 General Availability Level up your Java code and explore what Spring can do for you.

Spring Framework 7.0 is now GA!
Including Java 25 (with Java 17 baseline), Jakarta EE 11, JSpecify null-safety, Jackson 3.0, Kotlin 2.2, JUnit 6.0, plus programmatic bean registration, JmsClient, API versioning, HTTP Interface Client, RestTestClient & more: spring.io/blog/2025/11...

Btw this is coming from someone who used Windows exclusively for development for probably a decade when I started out, up to Windows 8.

As a dev I now value having full control over my OS and I want LLMs to work as I set them up. OS level is unacceptable - not just for me, I suspect for most devs

Universal Entry Point: A Single Entry Point for Context-Aware Coding Assistance | The IntelliJ IDEA Blog Modern IDEs are powerful tools with many useful features. When we talk about developer productivity, one thing that comes to mind is mastering the IDE – learning its features, like refactorings, navig

Modern IDEs are packed with powerful features, but discovering and using them effectively is challenging. 👀
Most developers remember only a few shortcuts – what if your IDE helped you discover its actions like it helps you write code, with completion? ⚡ Learn more in the blog below:
jb.gg/x7ue2e

Meme showing six logical operators illustrated with jack-o'-lantern images. trick OR treat trick AND treat trick XOR treat trick NOR treat trick NAND treat trick XNOR treat