Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files
A commenter says the headline is confusing; passwords are leaked by committing local settings, not by pressing 'Don't Ask Again'.
30 stories
Get a notification every evening
You hear about the digest when it is ready. Turn it off any time.
Notifications are on
You will hear about each evening’s digest when it is ready.
To get notifications on iPhone or iPad, add this site to your Home Screen first: tap Share, then Add to Home Screen. Open it from there to turn notifications on.
Notifications are blocked in this browser. Allow them in site settings and reload.
New notification sign-ups are closed for now. You can follow along with RSS.
Notifications could not be turned on. Check your connection and try again.
Notifications could not be turned off and are still on. Check your connection and try again.
The day’s top discussions
A commenter says the headline is confusing; passwords are leaked by committing local settings, not by pressing 'Don't Ask Again'.
One commenter says running semi-unattended agents on finance machines is dangerous; another cites chronic billing overages as the reason for access restrictions.
Commenters note the difficulty of Rust interop with Clojure and question why Clojure is so popular.
One commenter argues that AI has reduced the value of software and competitiveness; another notes the topic was previously discussed.
The discussion revolves around Bjarne Stroustrup's objections to C++ contracts and concerns about half-baked features.
Commenters note the method is innovative but point out practical challenges like retraining and hardware shortages.
Discussion about the trade-off between security and convenience, and alternatives like Bitwarden.
Commenters criticize GitHub's new PR page, highlighting lack of innovation in code review and issues with conflict display.
Discussion about whether the term 'vibe coding' is derogatory and AI's strength in compatibility tasks.
Commenters note that engineers overcomplicate watering and suggest ancient solutions like Ollas; also, photoperiodism examples are said to be incorrect.
One commenter finds the data collection exhausting and socially concerning, while another is unsurprised given Apple already has such data.
One commenter notes Flide is much faster by computing shared input once; another asks for comparison numbers with Laya.
One commenter suggests two methods to evaluate AI agent skills: self-evaluation or building a custom benchmark.
Commenters note that Deno's security model is a step despite its flaws, but a better open-source solution is needed.
One commenter thinks the UI is nice but questions crate update issues; another asks about advantages over dbx.
One commenter notes the WASM/GPU approach loses OS features; another wants a demo that outperforms HTML+CSS.
One commenter argues that Microsoft forced vendors to allow users to enroll their own keys in Secure Boot.
One commenter asks if it's possible to generate the YAML at runtime without committing it to the repo.
One commenter explains the necessity of static analysis in PHP, while another calls the official Discord community a regression.
Commenters discuss model capabilities being altered in the release cycle and praise the consistency of local models.
A smaller, more technical community
Commenters find the post and linked PDF hilarious and informative.
A commenter is surprised but happy that Redox got VirtIO-FS support before FreeBSD.
The discussion is about systemd's minimal use of Rust without standard library or external dependencies; commenters debate whether it still counts as Rust.
Discussion about the significant energy consumption from idle draw during package building and the need to consider it.
Commenters note that the performance of branchless implementations depends on data order and the advantage diminishes on nearly sorted data.
The week’s most-starred new repositories