When your last precedent is #cromwell you probably have a problem
The search for screwpine and bottle gourd: https://fooderalist.com/the-search-for-screwpine-oil.html
Finally, I have succeeded at pineapple upside-down cake:
If anybody remember's Thompson's "Reflections on Trusting Trust", this is a good example. The only thing compromised was the build system; this was completely invisible in the source.
"The not-so-secret life of boarding passes":
"What data you might be leaking publicly on that anachronistic piece of paper you discard in the seat in front of you. Turns out it is an awful lot more than you think…"
I always found #gnupg fun and interesting. But I have nothing to sign or encrypt to make use of it. I guess that works out ok since I sure wouldn't want to have to back up those keys properly.
Had an awesome tour of l'hotel #tallyrand. This was the private audience chamber.
I'm interested in having a discussion about simple authentication schemes in gopher. Anyone who is interested please read my thoughts at
If you think this is an important issue, please boost. Thanks!
I finally got my Norman braised chicken recipe the way I like it, so I thought I'd share with the fedi-foodie-verse
Every year or so I try to transfer my GnuPG keyring to a new machine and wind up half-writing the same rant, over and over again, about how while it's nice that they are absurdly paranoid about incredibly improbable corner-case threats, the end result is to keep people from using it. Pinentry is the current example. Yes, I agree, it provides a form of protection against a threat vector that I'm not worried about. And in the process it makes the suite unusable without docs-groveling.
After a month in Europe I'm not sure that #gdpr actually does anything other than make me click "OK" and then receive the exact same tracking.