HN user
https://ruuda.nl
It doesn’t have to be espionage, it can be just operational risk. There is the case of Trump ordering sanctions against the International Criminal Court, and Microsoft blocking their accounts to comply (https://en.wikipedia.org/wiki/Executive_Order_14203). Or more recently, Trump deciding who gets access to Anthropic’s latest models. You can’t build a business on a vendor who may be forced to block you at any moment.
https://www.metaculus.com/questions/40965/ gives it 71% probability.
Codeberg
It works fine if you don't enable javascript.
I find this article a useful framing for understanding what is happening to GitHub right now. The original is from 2022, but this 2023 repost includes a relevant preface.
The text reads like an LLM was involved in this.
https://github.com/doy/rbw is a Rust alternative to the Bitwarden CLI. Although the Rust ecosystem is moving in NPM's direction (very large and very deep dependency trees), you still need to trust far fewer authors in your dependency tree than what is common for Javascript.
Finally https://www.metaculus.com/questions/9558/50-of-users-access-... can resolve!
Property-based testing is nice, but making it coverage-driven is a game changer. It will explore code paths that naive random inputs will not trigger in a thousand years. In Rust this works very well with libFuzzer and the Arbitrary crate to derive the generators.
I contacted the EU DMA team about my concerns and got a real reply within 24 hours. Not just an automated message, it looked like a real human read my message and wrote a reply. I'd urge other EU citizens to do the same.
It's not complex, in the sense that the rules are simple, but simple rules can still lead to complicated emergent behavior that is difficult for humans to understand, even if each of the 153 steps that the typechecker took to arrive at the result were easy to understand individually.
I tried Zed for some time. Then it had a regression which broke it completely on my laptop. (Zed can't start any more, logging a PlatformNotSupported error even though earlier versions worked fine.) I carefully bisected it, and it turned out to be due to an intentional change in Blade. The issue was acknowledged, and confirmed by several other users. Then it got converted into a "discussion" because there was nothing actionable to do according to the devs. Then the discussion got closed because they are "directing all support questions to Discord going forward". Then Discord announced mandatory age verification.
Mastodon
We wrote https://github.com/chorusone/fastsync for fast ad-hoc transfers over multiple TCP streams.
Give https://rcl-lang.org/#intuitive-json-queries a try! It can fill a similar role, but the syntax is very similar to Python/TypeScript/Rust, so you don’t need an LLM to write the query for you.
RCL (https://github.com/ruuda/rcl) pretty-prints its output by default. Pipe to `rcl e` to pretty-print RCL (which has slightly lighter key-value syntax, good if you only want to inspect it), while `rcl je` produces json output.
It doesn’t align tables like FracturedJson, but it does format values on a single line where possible. The pretty printer is based on the classic A Prettier Printer by Philip Wadler; the algorithm is quite elegant. Any value will be formatted wide if it fits the target width, otherwise tall.
Everything I know about IPv6 comes from this one blog post: https://apenwarr.ca/log/20170810. It’s from 2017, when IPv6 adoption was 17% according to https://www.google.com/intl/en/ipv6/statistics.html; today it’s close to 50%.
It's a Linux thing too. It bit me in particular when running a script in a container that defaulted to ascii rather than utf-8 locale.
Python now uses UTF-8 as the default encoding, independent of the system’s environment.
Nice, not specifying the encoding is one of the most common issues I need to point out in code reviews.
There is a sweet spot for the bass. Lower is better for deep bass, but too low and it stops being a recognizable note, and consumer speakers can't reproduce it. This effect exists though I'm not sure if it is the cause of the pattern here.
They accept Monero too
I find them helpful. It happens semi-regularly now that I read something that was upvoted, but after a few sentences I think "hmm, something feels off", and after the first two paragraphs I suspect it's AI slop. Then I go to the comments, and it turns out others noticed too. Sometimes I worry that I'm becoming too paranoid in a world where human-written content feels increasingly rare, and it's good to know it's not me going crazy.
In one recent case (the slop article about adenosine signalling) a commenter had a link to the original paper that the slop was engagement-farming about. I found that comment very helpful.
Dell XPS used to be like this, but unfortunately Dell discontinued them :'(
Agreed. I got further into this one than usual before I grew suspect, but something felt off.
We did have three bugs that would have been prevented by the borrow checker, but these were caught by our fuzzers and online verification. We run a fuzzing fleet of 1,000 dedicated CPU cores 24/7.
Remember people, 10,000 CPU hours of fuzzing can save you 5ms of borrow checking!
(I’m joking, I’m joking, Zig and Rust are both great languages, fuzzing does more than just borrow checking, and I do think TigerBeetle’s choices make sense, I just couldn’t help noticing the irony of those two sentences.)
I wholeheartedly agree, I wrote about this at https://ruudvanasseldonk.com/2025/llm-interactions.
Sure, a different database schema may have helped, but there are going to be bugs either way. In my view a more productive approach is to think about how to limit the blast radius when things inevitably do go wrong.
FYI in an emergency you can `git push` to and `git pull` from any SSH-capable host without the need to use GitHub.
Rent servers from a local provider. It's cheaper, you get more control over the hardware, but most of all, it avoids correlated failures.