

연패
Can mean “to lose multiple times in a row” (連敗) or “to win multiple times in a row” (連霸).
연패
Can mean “to lose multiple times in a row” (連敗) or “to win multiple times in a row” (連霸).
I dump my encrypted data to someone who probably practices 3-2-1 rule (which is Backblaze for me). I mean, these guys back up data for a living.
show me the money
black sheep wall
power overwhelming
operation cwal
food for thought
How I played Starcraft as a child
.ch
Same here. I spent last month transitioning all my servers to NixOS and it feels so comfy! I do a small test on my desktop when I do something that might break stuff first, and then add it to server’s config later.
--target-host
and --use-remote-sudo
makes it even better too.
If you’re considering (something) + Syncthing, try Orgmode. It looks like Markdown but has a lot of features for note management and navigation.
The hardest part would be how to trigger the kill-switch periodically without showing it to your adversary whilst keeping it easy. Having your device queried directly would be a dead giveaway. My idea without involving people would be as follows:
But since this plan relies on the secrecy, it’s kind of ruined now. That, and I think your threat model is a bit too extreme.
A dead man’s switch doesn’t quite protect you from garden hose cryptanalysis though. Nothing stops them from asking you to tell them if he got a dead man’s switch.
No, not a mix of both. Either exclusively wins only, or losses only. Only way to tell these two apart is to see if this information is being celebrated or not…