Leace

> Which is why most distributions and other projects has moved to WKDs for key discovery.

Yeah, WKD is a first-class citizen in GnuPG. Creating signatures with "--sender $EMAIL" embeds e-mail in the signature and then gpg --auto-key-retrieve --verify will fetch the key via WKD without the need to touch keyservers.

On first sight this looks interesting but Keybase is years ahead in the UX polish. E.g. on Keybase it's easy to see and add new proofs without a CS degree.

Allow self-signed certs and build reputation as usual. This would still require effort from indie devs to build reputation but as soon as more people start using your app the dialogs disappear. You don't need domain name, anyone can generate self-signed certs.

One variation of this scheme is making Microsoft the CA that issues certs for free with some issuance limits.

For the record Google uses self-signed certs for Android apps.

> Maybe write down my master password and put it in a safe?

Isn't this just moving the goalpost because what if you forget safe combination?

> Without compromising your security - I'd love to know how others approach their personal IT security challenges?

Most of my security is based on OpenPGP keys stored on a Yubikey. In case the first one is broken/lost I've got another one. If both are lost there is a master copy on an offline computer that can be used to provision more Yubikeys.

The key unlocks access to passwords stored in pass. Because pass is based on git and gpg can be used to access SSH then the same yubikey is used to pull/push changes to pass and read encrypted passwords. On both the laptop and the phone (Password Store).

Data on the computer is LUKS-encrypted, unlocked by the Yubikey. Full backup of my laptop's SSD is done via btrfs send/receive to a raid1 array of 3 disks (raid1c3) on a regular intervals. A small subset if very important data (documents) is also backed up via restic to S3 and Backblaze.

I try to "backup" as much of my work as possible by releasing it as open-source (where it's preserved by the Github etc.) or publishing it on a web-site (where it's preserved by archive.org).

> In a similar vein: what happens to my data after I die? How would my (non-technical) family be able to access my pictures and writings? A digital inheritance would be prevented in my security set if I don't prepare.

I've been thinking about this lately and maybe it's not a popular opinion but... would people really need your data when you die? I get access to photos (my SO has the PIN code) but everything else? Maybe this is just digital junk? Who would enjoy browsing terabytes of my data looking for... what exactly?

It's still a thing for people that started using it when it was the latest Google chat product. It may be surprising but people just want stable chat experience not chasing whatever next product Google releases or kills next year.

(I did migrate my family and friends to self hosted XMPP server as Hangouts doesn't have E2EE)

> We do not allow anonymous users (i.e., without a Google Account) to join meetings created by individual accounts.

This quote from the linked post would suggest otherwise.