I feel like I'm opening myself up to some abuse by posting this, but I still use my original brown Zune every day. I bought one as soon as they became available and I've always loved it. I've swapped out the original hard drive twice (once early on for a 100 GB HDD until it died, and then for a 128 GB SSD), and I've replaced the battery twice as well. Sometimes I wonder if I just hold onto it out of nostalgia, but I hope it will last a long time to come!
The UK has had mail voting for years. It works very well. Your ballot is marked with a unique reference vote. Once you mark the ballot, you fold and seal it, then put it into another envelope that also comes with the ballot.
This is a bit random, but I have a cameo appearance in Counterfeit Monkey as my rockstar alter ego 'Nexami Engeo.' Cool to see the game being mentioned on Hacker News
The clients are. The platform they all run on top of is centralized, made up its own irresponsibly insecure key handling and crypto protocols, and is proprietary.
A lot of trust is rooted in their centralized proprietary walled garden API and to make matters worse they actually silently bypass hardware security modules in favor of keys exposed to system memory!
They even encourage users to expose their PGP private keys to their browser and didn't even bother to isolate it to a service worker so browser plugins can't steal it (or just supporting hardware tokens which GPG already did just fine)
Almost everything they do is non standard, not interoperable with anything else, not distributed to keyservers. They are the internet explorer of cryptography.
They did this in the name of UX but it turns out you can have super easy PGP UX AND follow standards as OpenKeychain has demonstrated.
Keybase introduced lock-in and their own protocols for problems that did not at all need them. They are 2 steps forward on UX and one huge backwards step for security.
You have been on this crusade for a long time now and you have posted this link often, I just realized that keybase is not just a GPG replacement and that using it with my smart card is not a good fit and not the problem they want to solve. So I just accepted that and actually tried to figure out what keybase is actually doing and why rather then demanding they do what I initially wanted from it.
They have been focusing on a per-device key system and its not really a gpg front-end. NaCl is a well known library and what they do is based on it. Saltpack is an open library they use and they use other open libraries as well. I happen to like the how the keybase security system works and I think it has advantages over the GPG that I like.
If you don't want to use the evil centralized system at least spamming the same issue every-time Keybase comes up. If Keybase is not the solution you like then just move on with your life.
Flyspell in Emacs 26.1 seems to require a version of Aspell that is not officially available for Windows. I might need to put off the upgrade until I can attempt to compile a newer Aspell for Windows myself.
"Error enabling Flyspell mode:
(aspell release 0.60 or greater is required)"
In case anyone else was facing this problem (and isn't too committed to Aspell as a backend for Flyspell), the version of Hunspell from ezwinports[1] (version 1.3.2 at time of posting) seems to be working with Emacs 26.1 on Windows.
