It will be interesting to see how it compares to the Keycard Shell[2] a fully open-source wallet with swappable smart cards using the same secure element as found in credit cards etc.
It was simple, just fucking worked.
Leave it to some uninspired people to fuck things up.
1. 1 custom domain (<simple-word-or-two>.com): this will be used for friends, family and any online accounts that know me IRL.
Use Fastmail masked addresses with my custom domain where it makes sense like an online account for amazon.
2. 1 custom domain (<online-nickname>.xyz): this will be used for a blog, professional IRL interviews, correspondence, github.
Use Fastmail masked addresses with my custom domain where it makes sense.
3. Masked emails using fastmail.com: for online accounts that are ephemeral, random newsletter signups etc. Don't want to associate any of my custom domains or IRL identity. Don't care if these are portable.
My main goals are:
- Separate my online identity/alias used for my blog (2) from gov entities, banks etc (1).
- for more anonymity/privacy use the fastmail.com domain with masked addresses to blend in with others on this domain.
I'd love feedback and to read what you do if you want to share :)
Glove80 has a better key well and thumb cluster for most people though. I have made a detailed comparison here:
https://danieldk.eu/MoErgo-Glove80-Review
Also agree with the sibling commenters. In order, get:
- Help from an expert/exercise/do very regular breaks.
- A properly adjustable chair.
- A height-adjustable desk (get an electronic one, it's the only one you will ever tune properly, other desks are too much effort).
- Only then an ergo keyboard.
An ergo keyboard is worthless if you do not get the basics right (diagnose the issues, letting the blood flow, having a good posture). I am in some ergo keyboard Discords and it happens far too often that people by an ergo keyboard, but do not even have a setup where they can have a good posture.
To make it extra fun, my $HOME directory is immutable:
chflags uchg "${HOME}"
(Simply setting it read-only would work too.)Preventing arbitrary writes in $HOME breaks things, but it's actually quite rare.
I should document this setup. Or perhaps it's better to keep the madness to myself...
* (paranoia) can you trust your printer not to leak the secret? (either in local memory, or to send it to its cloud mother-ship?) you can encrypt your information and print that, but then you are back to square one: where do you backup the password;
* and most importantly, long term resilience: given that with normal printers you can only print on soft materials (like paper, or perhaps plastic), they won't last floods, fire, and other unlikely events; (even if one laser etches some information on a steel sheet, I don't know how resistant to abrasions it is;)
However, by actually drilling holes into a metal sheet, the only way to permanently make the data irrecoverable, is to destroy the object completely.
>The .age-recipients files also include the public key for an offline disaster recovery key. I generated the key with age-keygen, encrypted it with age -p, printed the ciphertext as a QR code, and wrote the random passphrase in pen. This is a bit convoluted, but I don’t trust printers. All this was done in a tmpfs, so nothing reached storage. Only had to do this once, and have been using that key as the anchor for all my disaster recovery data. https://words.filippo.io/dispatches/passage/
But using either of these tools to have your DNS redeploy-able to a new provider is a great idea for resiliency.
I've been thinking about doing this for my personal domains, but not sure if it's a good idea