Check this out: https://clip.place/w/ajgJ5Hi69bbbxHCK3nXNdj

I just published a video of the new "end to end encryption" protocol for ActivityPub in #Emissary. The UX is rougher than I'd like, but you can see the client app is coming along nicely.

Today, it sends and receives messages using MLS, a widely used industry standard and successor to the Signal protocol.

By June 2026, it should be ready for you.

For more details on the project and my progress, see: https://emissary.dev/e2ee

#JustBetweenUs #e2ee

We Use Signal Now

Because private conversations should stay private.

#signal #privacy #e2ee #messaging #whatsapp #meta

https://rohitfarmer.com/posts/2026/we-use-signal-now/

We Use Signal Now

Because private conversations should stay private.

#signal #privacy #e2ee #messaging #whatsapp #meta

https://rohitfarmer.com/posts/2026/we-use-signal-now/

Debating whether I still need #Obsidian, since I can use #Joplin on my phone, sync via Dropbox, and enable #e2ee.

#foss #fediverse

Check this out: https://clip.place/w/ajgJ5Hi69bbbxHCK3nXNdj

I just published a video of the new "end to end encryption" protocol for ActivityPub in #Emissary. The UX is rougher than I'd like, but you can see the client app is coming along nicely.

Today, it sends and receives messages using MLS, a widely used industry standard and successor to the Signal protocol.

By June 2026, it should be ready for you.

For more details on the project and my progress, see: https://emissary.dev/e2ee

#JustBetweenUs #e2ee

Signal Protocol for a P2P Webapp

TL;DR: I have open-sourced a #Rust implementation of the #SignalProtocol that compiles to #WASM for #Browser-based #P2P messaging, overcoming the #NodeJS limitations of the official library.

I am sharing my implementation of the Signal Protocol designed specifically for the #Frontend. While the official libsignal is the gold standard, its #JavaScript targets are often optimized for Node.js, which creates integration challenges for client-side web applications.

My version is built in #RustLang and compiles to #WebAssembly, utilizing #ModuleFederation to provide robust #Encryption for decentralized environments. It currently powers the end-to-end security for my #P2P messaging project.

Protocol Demo:
https://signal.positive-intentions.com/

P2P App Demo:
https://p2p.positive-intentions.com/iframe.html?globals=&id=demo-p2p-messaging--p-2-p-messaging&viewMode=story

I am looking for feedback from the #Dev and #Infosec community. If you have experience with #Cryptography audits or formal-proof verification, I would appreciate your eyes on the codebase as I work toward a more finished state.

GitHub Repository:
https://github.com/positive-intentions/signal-protocol

#Signal #SignalProtocol #Rust #RustLang #WASM #WebAssembly #OpenSource #OSS #Privacy #Encryption #E2EE #WebDev #Frontend #BrowserTech #Decentralized #WebApps #Coding #Security #SoftwareEngineering #Networking #PeerToPeer #P2P #Cryptography #Audit #CyberSecurity #Tech #JavaScript #Programming #ModuleFederation #P2PWeb #PrivacyTech #SecureMessaging #WebPerf #TechCommunity #InfoSec #WebSecurity

Reminder: TeleGrab is effectively unencrypted and you might as well use plaintext direct posts in the fediverse. Cryptographers have been poking holes in TeleGrab's limited, crippled "encryption" for years. Here's an example from 2022;

https://www.cryptofails.com/post/70546720222/telegrams-cryptanalysis-contest

#chat #Telegram #encryption #E2EE

Reminder: TeleGrab is effectively unencrypted and you might as well use plaintext direct posts in the fediverse. Cryptographers have been poking holes in TeleGrab's limited, crippled "encryption" for years. Here's an example from 2022;

https://www.cryptofails.com/post/70546720222/telegrams-cryptanalysis-contest

#chat #Telegram #encryption #E2EE

@liaizon

Everything on the table:

I should do this, but have been waiting because I *really* want to self-host the main #Emissary and #Bandwagon accounts on my own software.

Right now, Emissary is a great PUBLISHER and READER, but it does a poor job with DMs. So I couldn’t really use Emissary to support questions like this one.

It’s been on my roadmap for a while, and it’s why I’m excited to build #e2ee DMs, too.

But I do plan to launch these as soon as I have a good solution for DMs.

@hollo

Fantastic! If you already support the ActivityPub API (C2S) then the server-side changes are relatively small. Once we've road-tested the spec, I'm happy to help you set it up :)

And, my apologies. I confused you with another project that's doing #e2ee with the Signal protocol. In my defense, https://holos.social is a similar enough name at first glance.

@benpate Yes, of course we're interested in #E2EE too! (For reference, Hollo doesn't have E2EE for DMs yet.) We're completely open to collaborating with the #Bonfire team.

@hollo

Very cool, guys! Kudos!

#Bonfire is also working on encrypted DMs similar to Hollo. They’re using MLS, which is similar, but slightly different from the Signal protocol you’re using.

I know it’s a big request, but what are the chances of getting your #E2EE messages to work with Bonfire (and #Emissary) too?

It would be great for the Fediverse to have a unified E2EE standard in 2026.

Let me know if it’s a possibility. I’m happy to tour you through our work so far!