5 ms·
"If the architecture of my code doesn't enforce privacy" This is still techno-optimism. The architecture of your code will not to that. We are long past the li
by praptak 9mo ago
"If the architecture of my code doesn't enforce privacy"
This is still techno-optimism. The architecture of your code will not to that. We are long past the limits of what you can fix with code.
The only action that matters is political and I don't think voting cuts it.
- cyber_kinetist 9mo agoYeah, reminds me of the "Security" xkcd (https://xkcd.com/538/ https://xkcd.com/538/) - a threat from a good ol' 5-dollar wrench defeating state-of-the-art encryption. Never estimate how state actors can use violence (or merely the threat of it) to force people to do things. The only way to respond to that is not through code or algorithms or protocols, but through political action (whether it be violent or non-violent)
- dlahoda 9mo agocan we align that code, algorithm, code to be forms and important forms of political action?
- wizzwizz4 9mo agoSoatok Dreamseeker is working on a more xkcd-538-proof system: https://soatok.blog/2025/08/09/improving-geographical-resilience-for-distributed-open-source-teams-with-freeon/ https://soatok.blog/2025/08/09/improving-geographical-resili... https://github.com/soatok/freeon https://github.com/soatok/freeon. Fundamentally, though, it's built on the assumption that geographical resilience is possible – that a group can be distributed such that no one organisation can perform $5-wrench attacks against enough of them to break the cryptography. (Given that the attack's impossible, a sensible attacker would avoid tipping their hand by attempting it, thus sparing contributors from violence.)
- some_furry 9mo agoI should be clear: Nothing is xkcd-538-proof, in absolute terms. Violence is always possible. But having a tool that is more resistant to authoritarian overreach by being geographically distributed does make it harder to pull these attacks off.
- dlahoda 9mo ago> We are long past the limits of what you can fix with code. example of what is not possible to fix with code?
- cyjackx 9mo agoPicture wrench attacks. What use is your Monero's security, for example, as I turn a screw into you until you give it up?
- thewebguyd 9mo agoShamir's secret sharing. In that scenario, capturing me alone isn't going to get you anything even if I divulge my piece of the secret. You'd still need to find out who has the other pieces, find them, and convince them to divulge as well. Maybe there's 3 of us, and the 4th part of the password/secret/private key is on a server of mine somewhere. If I don't check in for x duration, it wipes itself. Yeah it means my Monero is gone now, but at least my attacker didn't get it.
- Espressosaurus 9mo agoThe threat of the state tossing you in jail until you divulge your password/permit backdooring/etc.
- thewebguyd 9mo agoYou can design in ways such that there isn't a password to give up in the first place. Maybe the key is distributed and you need all x number of people to decrypt. Sure, maybe the state can capture everyone but it becomes significantly harder than targeting a single person and threatening them with torture. Combine that with rate limiting and a dead man's switch.
- Espressosaurus 9mo agoHard power still matters. It gets access to things like fiber closets, upstream dependencies, subtle flaws in encryption schemes that take years to figure out, information linking your networks, and more than I can think of. Cute tech can slow them down until they go through the effort of controlling most of TOR's exit nodes and point the Eye of Sauron at you.