# e2ee

Published articles for e2ee.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Operator, I need an exit from Big Tech calls

DevFeed: [Operator, I need an exit from Big Tech calls](<https://devfeed.tech/articles/operator-i-need-an-exit-from-big-tech-calls-95266.md>)

Original publisher: [Read original article](<https://element.io/blog/operator-i-need-an-exit-from-big-tech-calls/>)

Author: Steve Loynes

Published: 2026-10-22T10:04:19Z

Content type: release

Language: en

Sources: [Element Blog](<https://devfeed.tech/sources/element-blog.md>)

Topics: [Matrix](<https://devfeed.tech/topics/matrix-org.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [audio](<https://devfeed.tech/tags/audio.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [call](<https://devfeed.tech/tags/call.md>), [chat](<https://devfeed.tech/tags/chat.md>), [choice](<https://devfeed.tech/tags/choice.md>), [community](<https://devfeed.tech/tags/community.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [conference](<https://devfeed.tech/tags/conference.md>), [control](<https://devfeed.tech/tags/control.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [devices](<https://devfeed.tech/tags/devices.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [e2ee](<https://devfeed.tech/tags/e2ee.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [voip](<https://devfeed.tech/tags/voip.md>)

### AI overview

MatrixRTC is an open standard for coordinating multiparty encrypted calls across Matrix. Each server can run an SFU; callers publish to their own server's SFU or, if unavailable, another participant's, while participants can join without operating one. Calls can be pinned to selected SFUs, and the protocol supports multiple users and devices. Element Call currently uses LiveKit, but MatrixRTC does not mandate a transport; the excerpt describes independent implementation in Tammy and an interoperability demo. Element Desktop and Web are integrating calls with Matrix-identity E2EE and guest access, while Element Mobile is moving to native MatrixRTC support. ESS Community supports around 50 participants and ESS Pro around 200, depending on deployment. The excerpt says recording, captions, transcription and SIP features that require server-side actions are reserved for Pro offerings. It also describes cSFU as an approach under exploration, with performance and scalability benefits presented as expected rather than established.

### Source excerpt

All good things come to those who wait! MatrixRTC is finally here: the world's first decentralised, end-to-end encrypted (E2EE), multiparty VoIP protocol.

## End-to-End Encryption: A Modern Implementation Approach Using Shared Keys

DevFeed: [End-to-End Encryption: A Modern Implementation Approach Using Shared Keys](<https://devfeed.tech/articles/end-to-end-encryption-a-modern-implementation-approach-using-shared-keys-23988.md>)

Original publisher: [Read original article](<https://quickbirdstudios.com/blog/end-to-end-encryption-implementation-approach/>)

Author: Allison Poppe

Published: 2023-03-07T14:07:27Z

Content type: tutorial

Language: en

Sources: [QuickBird Studios Blog](<https://devfeed.tech/sources/quickbird-studios-blog.md>)

Topics: [End-to-End Encryption](<https://devfeed.tech/topics/end-to-end-encryption.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [To-Do](<https://devfeed.tech/topics/todo.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [e2ee](<https://devfeed.tech/tags/e2ee.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [end-to-end-encryption](<https://devfeed.tech/tags/end-to-end-encryption.md>), [general](<https://devfeed.tech/tags/general.md>), [implement](<https://devfeed.tech/tags/implement.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [post](<https://devfeed.tech/tags/post.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

End-to-end encryption keeps data encrypted as it travels between authorized devices, with the decryption keys remaining on those devices. The excerpt introduces a shopping list app that syncs across a computer, phone, and watch, while its server is accessible to the user's roommates. Because the server cannot be treated as secure from them, E2EE is presented as a way to keep the list unreadable to people who can access the server. The excerpt ends before describing the shared-key implementation.

### Source excerpt

End-to-end encryption, otherwise known as E2EE, is an incredibly important aspect of modern application security. It's not only necessary to make sure that the data in our application is secure, but also to make sure that the data we send and receive is as well. Users rightfully expect that the data they are entrusting you with is kept safe with you and protected from anyone who shouldn't see it as much as possible. End-to-end encryption is one of the best tools in our toolbox to make sure that this happens. In this article, we give you a head start on how to implement a modern way of end-to-end encryption into your app. The post End-to-End Encryption: A Modern Implementation Approach Using Shared Keys appeared first on QuickBird Studios.