FEP-0806: Simple client-side encryption

https://codeberg.org/silverpill/feps/src/branch/main/0806/fep-0806.md

The FEP now includes the recommended algorithm parameters.

I consider it finished but I don't plan to continue working on my implementation or publishing to the main FEP repository. It would be better to focus on group messaging with forward secrecy (MLS or similar).

#fep_0806 #e2ee

Summary card of repository silverpill/feps, described as: My FEPsCodeberg.orgfeps/0806/fep-0806.md at mainfeps - My FEPs

Replying to @⁨silverpill@mitra.social⁩

@silverpill nice! there is a workgroup meeting tomorrow for activitypub-e2ee, are you planning to be there?

w3.org/events/meetings/ad4d3e0

W3C28 July 2026 | SocialWebCG E2EE Task Force Call | CalendarThe World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.

Replying to @⁨silverpill@mitra.social⁩

@silverpill understandable. fwiw the gate is pretty easy to open, but does require signing a CLA.

how else do you suggest we develop an E2EE protocol for the fediverse? you mention in your FEP that you are giving up on it for a proper E2EE impl. genuinely asking b/c I'm interested in getting E2EE, hopefully interoperable with widest number of clients possible.

also, what do you mean by corporate takeover?

Replying to @⁨elle@weathered-steel.social⁩

@elle

fwiw the gate is pretty easy to open, but does require signing a CLA.

It's not that simple. But it might appear easy if you don't inconvenience them too much, and jump through all the hoops https://github.com/swicg/charters/blob/main/stage-process.md

how else do you suggest we develop an E2EE protocol for the fediverse?

In the same way as everything up until this moment has been developed. Somebody just needs to do it.

If the result is good, others will copy it.

>you mention in your FEP that you are giving up on it for a proper E2EE impl. genuinely asking b/c I'm interested in getting E2EE, hopefully interoperable with widest number of clients possible.

Not giving up - I want to explore a more advanced encryption scheme. I think the basics are not going to change too much.

also, what do you mean by corporate takeover?

A lot of things.

Discussion of potential CG and WG charters. Contribute to swicg/charters development by creating an account on GitHub.GitHubcharters/stage-process.md at main · swicg/chartersDiscussion of potential CG and WG charters. Contribute to swicg/charters development by creating an account on GitHub.

Replying to @⁨silverpill@mitra.social⁩

@silverpill

With NIKE (Non-Interactive-Key-Exchange) one sided forward secrecy is the best you can get. AFAIK the fediverse model strongly favors 0-RTT messaging, so I think the FEP as designed is close to ideal, as something simple that fits the use-case.

I will be the first to admit that my knowledge in the protocol is severely lacking, but if you have cryptography related questions, please let me know.

Replying to @⁨greyarea@mitra.vpclmulqdq.moe⁩

@greyarea

>Non-Interactive-Key-Exchange

I think interactive key exchange is fine too. Activities and requests are often sent back and forth between fediverse servers. The most canonical example is probably the Follow activity to which remote server responds with Accept.

>but if you have cryptography related questions, please let me know.

Thank you. I will surely have a lot of questions in the future.

en