@neptune22222 @tomcoates the idea is that you'd be communicating over the fediverse. Your fediverse handle would be how people message you.
Conversation
Notices
-
Embed this notice
Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 01-May-2024 22:12:50 JST Evan Prodromou -
Embed this notice
Evan Prodromou (evan@cosocial.ca)'s status on Friday, 03-May-2024 08:03:40 JST Evan Prodromou @tomcoates @JsonCulverhouse @dalias @neptune22222 I think E2EE by definition means keys in the client only.
Keys on the server are for HTTP Signature only.
-
Embed this notice
Tom Coates (tomcoates@me.dm)'s status on Friday, 03-May-2024 08:03:41 JST Tom Coates @JsonCulverhouse @dalias @evan @neptune22222 we’re very conscious about the risks of instances holding keys rather than clients. But part of this project is checking into options and potential solutions, so I wouldn’t want to commit to a particular solution right now.
-
Embed this notice
Jason Culverhouse :flipboard: (jsonculverhouse@flipboard.social)'s status on Friday, 03-May-2024 08:03:42 JST Jason Culverhouse :flipboard: @dalias @evan @neptune22222 @tomcoates
Are we going to be able to register a additional public key to use for encrypted messages?
This way you can encrypt and send messages but we can decrypt on device?
Right now only the #activitypub server implementation holds your private key. So not really end to end.
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Friday, 03-May-2024 08:03:44 JST Rich Felker @evan @neptune22222 @tomcoates But that identity is controlled by a third party (the instance). How do you intend to be able to use it in e2ee?
-
Embed this notice