this post was submitted on 15 Dec 2025
25 points (100.0% liked)
Privacy
4353 readers
150 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'll take a look when I get a chance, but like you said, it's a public key directory. I thought you were claiming to have a solution to client side keys. Is there trouble with using some existing PK directory scheme?
No, if you read the post it will make more sense.
Or the specification if you're more technical.
I'll see if I can read the post but when I tried this morning, it was way too long. I'll look at the specification. I've been involved in crypto implementation since forever, which is why this looked interesting. But I think the client side also has to be figured out, if it hasn't been yet.
The client side is its own beast. See https://github.com/soatok/mastodon-e2ee-specification?tab=readme-ov-file#components from my initial project (the "key transparency" thing from today slots neatly into the "Federated PKI" hole).
Thanks. I'll look and post comments later if you want them.
Certainly. Thanks <3