Dunedan

> When Automatic Key Verification is turned on, the Signal client periodically fetches Merkle tree heads from the Signal key transparency server. The client requires that each tree head belong to a lineage endorsed by all registered auditors within the last seven days. If the server does not present valid auditor signatures, the client will raise a warning and Automatic Key Verification will fail. A fully malicious server may therefore maintain a split view of the system for at most one week before client applications start to display warning messages.

(from https://blog.trailofbits.com/2026/08/11/how-trail-of-bits-he...)

Comment · 5 months ago

All the AI hype aside, I wonder if there is a way to avoid becoming one of these faceless corporations where customers are just numbers. For years Amazon has been fantastically customer centered, but at some point they just lost it. I could compile a list where Amazon is actually way more customer unfriendly than in the past now, but I guess everybody already got their own anecdotes about that. So what exactly went wrong and how could that be avoided at other companies?

Comment · 5 months ago

Firefox unloads tabs under memory pressure since more than 4 years: https://hacks.mozilla.org/2021/10/tab-unloading-in-firefox-9...

Comment · 6 months ago

While your statement is true, it leaves out relevant details:

There is a certain threshold for radiation exposure where if exceeded the animal isn't deemed safe for consumption anymore. The vast majority of these cases are from boars in certain areas of Germany nowadays and affect less than 1% of all killed boars [1] [2].

[1]: https://www.deutschlandfunk.de/fast-3000-verstrahlte-wildsch...

[2]: https://www.wildtierschutz-deutschland.de/_files/ugd/173a38_...

Comment · 6 months ago

While the spot market price for electricity in Germany gets negative from time to time, it's far away from doing so every day.

https://energy-charts.info/charts/price_spot_market/chart.ht...

Comment · 6 months ago

Mind that nuclear power relies on favorable weather as well. It's not uncommon in Europe that nuclear power plants have to shut down, because the rivers they use for cooling become too hot.

Comment · 6 months ago

> 1. Stuff happens in the wrong order. […] You don't want the feedback loop after the commit you want it before. Let me do an enforced pre-commit hook to run the jobs remotely on the forge and provide the feedback to the user before they push.

My approach is to utilize https://pre-commit.com/ to have all checks available to run locally during commit (or push), but leave it to contributors whether they want to run it or not. If they don't, the checks still run on the forge after pushing. The upside of this approach is that it still allows contributors to commit without internet access or the forge being down.

> 3. PRs are too inflexible. I don't need 4 eyes on every change, especially in a universe where LLMs exist. The global GDP lost annually to senior engineers staring at a four-line PR waiting for someone — anyone — to type 'LGTM' could fund a moon mission.

Well, that's possible with Github and is just a matter how permissions to merge PRs are configured. Just let every contributor merge changes without explicit approval. And if you want LLM approval, make that a Github Action with mandatory success for merging.

> 4. Stacked PRs are just better. […]

Seems like Github is working on this: https://github.github.com/gh-stack/

> 8. On the flip side, since I need to be online all the time to really work with a team […]

Sure, for communication you need internet access, but working on code can be much more efficient if you can do so without relying on internet access and the forge being available.

I'd even argue working on issues and reviewing PRs should be available entirely offline too with just the state getting synced whenever internet connectivity to the forge is available.

Comment · 6 months ago

That's not correct. "Arbeitnehmererfindungen" only apply to inventions you make as part of your paid work. See https://de.wikipedia.org/wiki/Arbeitnehmererfindung

Whatever you do in your spare time is up to you and your employer has no saying over it, unless he can prove that it negatively impacts your job performance.

Comment · 8 months ago

The even more concerning news to me is that chardet 7.0 is now vibe coded AI slop, as documented in the PR for the rewrite [1]:

> I put this together using Claude Code with Opus 4.6 with the amazing https://github.com/obra/superpowers plugin in less than a week. It took a fair amount of iteration to get it dialed in quite like I wanted, but it took a project I had been putting off for many years and made it take ~4 days.

Given the amount of changes I seriously doubt that this re-implementation has been reviewed properly and I wonder how this is going to be maintainable going forward.

[1]: https://news.ycombinator.com/item?id=47259177

Comment · 8 months ago

> 18A is brand new, yields are probably rough.

That the CPU cores are low frequency cores probably helps with yield as well.

Comment · 8 months ago

When was the last time you played 0ad? Each release brings new changes to balancing and especially a27 contained a lot of them.

Comment · 8 months ago

> My understanding is that the simulation will be bottlenecked by the slowest PC.

That's correct. While 0ad is an RTS, behind the scenes it's still turn-based and in multiplayer games turns can only progress once every participants PC has responded. That's also why the game also feels slow when a player has a bad latency to the player hosting the game.