auth

Maybe you're missing some other context. Here's an article about local-first software: https://www.inkandswitch.com/local-first/ Here's an article about why you might want this: https://medium.com/all-the-things/a-web-application-with-no-... Here's another article about a previous attempt at solving this problem: https://herbcaudill.com/words/20240602-local-first-auth and here's the associated readme for how that turned out: https://github.com/local-first-web/auth?tab=readme-ov-file#r...

Re: key distribution, we're just changing it now but in a few days the scheme will be: 1. a community member sends you an invite link containing some onion addresses of community members 2. you sync community data and send a CSR to the community owner. 3. We show an "unregistered" message next to your name until the community owner signs your CSR, at which point you're a full member. We use PKI.js for the certs. For multi-party message-layer encryption with multi-device support we plan on using: https://github.com/local-first-web/auth, which is inspired by Keybase and a Martin Kleppmann paper.

(Quiet founder here) The non-trivial thing about DMs is multiple device support, so that when someone sends you an encrypted DM you will receive it on any of your devices. We've also been prioritizing basic functionality on Android and iOS over many common-sense features like DMs because there is a lot of risk there. All users we talk to need reliable mobile support, so we want to ensure we have that locked down to a sufficient degree before adding a bunch of features (to be a bit melodramatic, we want to make sure we aren't polishing deckchairs on a Titanic!) But we have a concrete plan for encrypted group messaging with multiple device support and removal. We plan on using this library: https://github.com/local-first-web/auth It is very bleeding edge but is based on academic work by Martin Kleppmann and built in conjunction with the fol