Implementing Encrypted Messaging over ActivityPub


One of the project areas of the Social Web Foundation for the last year has been end-to-end encrypted messaging. ActivityPub, the standard protocol that powers the Social Web, has privacy controls, but they do not protect the content of messages from server operators. Encrypted messaging has become a common feature on many social networks since ActivityPub was created, and its lack has inhibited Social Web adoption and public trust in the network. ActivityPub is extensible, though. As part […]
This entry was edited (1 month ago)
in reply to Evan Prodromou

is this overlapping or alongside the work done by @soatok ?

soatok.blog/2025/12/15/announc…

in reply to Мя ��

@mo Sure! So, Facebook Messenger, Instagram, and X all have end to end encrypted direct messaging.

For messaging-only apps, WhatsApp, Signal, iMessage, Google RCS and Matrix are E2EE. Telegram has an option for E2EE.

There are many social networking platforms that don’t have encrypted dms. LinkedIn, Tiktok, and Snap are some examples there.

I hope that helps!

Social Web Foundation reshared this.

in reply to Evan Prodromou

I must say I am a bit skeptical. E2EE has to be done right or it is less than worthless because no security is better than the appearance of security. At least then you know what you got. And I am not sure if ActivityPub even needs to be a secure messenger. I'd rather people use a messenger with proven security. Keeping messages secure between dozens of implementations seems like a very complicated task.