惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
Help Net Security
Help Net Security
Y
Y Combinator Blog
WordPress大学
WordPress大学
D
DataBreaches.Net
N
Netflix TechBlog - Medium
U
Unit 42
爱范儿
爱范儿
MyScale Blog
MyScale Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
博客园 - 司徒正美
Google DeepMind News
Google DeepMind News
D
Docker
H
Help Net Security
Stack Overflow Blog
Stack Overflow Blog
宝玉的分享
宝玉的分享
博客园_首页
Microsoft Security Blog
Microsoft Security Blog
Engineering at Meta
Engineering at Meta
Know Your Adversary
Know Your Adversary
P
Privacy & Cybersecurity Law Blog
P
Proofpoint News Feed
T
Tenable Blog
S
Schneier on Security
V
Vulnerabilities – Threatpost
V
V2EX
T
Tor Project blog
Security Latest
Security Latest
S
Securelist
G
Google Developers Blog
NISL@THU
NISL@THU
Schneier on Security
Schneier on Security
Webroot Blog
Webroot Blog
小众软件
小众软件
Google Online Security Blog
Google Online Security Blog
阮一峰的网络日志
阮一峰的网络日志
W
WeLiveSecurity
IT之家
IT之家
I
InfoQ
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
月光博客
月光博客
I
Intezer
T
The Blog of Author Tim Ferriss
C
Cisco Blogs
博客园 - 【当耐特】
The GitHub Blog
The GitHub Blog
Cloudbric
Cloudbric
Scott Helme
Scott Helme
The Cloudflare Blog
L
LINUX DO - 热门话题

Element Blog

Organise your chats your way with Sections We’re interoperable, so you can be sovereign Matrix-based ZaPuK confirmed as a core component within Germany’s Deutschland-Stack Element recognised as a Digital Public Good CompuGroup Medical (CGM) and Element partner to transform healthcare communications Sweden goes live with Matrix-based federation! Air-gapped communications for national security Digital sovereignty is built on an open standard that enables federation Introducing the ESS Community migration tool Spaces has landed on Element X! Meedio partners with Element to deliver sovereign communications across Europe Governments need to adopt Matrix responsibly The Cyber Resilience Act: Implications for open source and digital products Latest Signal and WhatsApp breaches show that consumer apps have no place in government Sustainable decentralised comms at Element Exploring MatrixRTC: Real time communication in rooms The Digital Omnibus: opportunities and risks for open source Element’s multi-tenancy TI-Messenger solution secures ‘Good’ rating in gematik commissioned pentest Open source is key to Europe’s digital sovereignty
Seamless encrypted history sharing arrives in Element
Andreas Sisask · 2026-05-13 · via Element Blog

For years, end-to-end encryption (E2EE) has been the gold standard for digital privacy. But it has always come with a silent trade-off: when you add a new member to an encrypted chat, they arrive at a blank slate (as in, they can’t see conversation history). Any previous conversation - no matter how vital to their onboarding - remained locked away, accessible only to those who were already there. You start taking the screenshots of the chat to provide the new member with the necessary context and get them up to speed. Sound familiar?

Today, we are changing that. We are thrilled to announce that Element now supports seamless, secure history sharing for new chat members, effectively ending the ‘blank slate’ era of encrypted collaboration (more on this here). Whether it’s a new colleague getting up to speed on a project, a person you simply forgot to invite to a new chat, or a community member joining a long-running discussion, you no longer have to worry about whether they have the context they need.

View for new members joining a room
View for new members joining a room

By combining the rigour of Matrix’s decentralised, secure architecture with the seamless experience users expect from modern messaging, we’re proving that you don't have to choose between strong security and fluid collaboration.

The challenge of "locked" history

In a standard E2EE environment, messages are encrypted with keys that are only distributed to the participants present at the time the message is sent. When a new person joins, they simply don’t possess the cryptographic keys needed to unlock the chat history. 

For many users, this felt less like a security feature and more like a broken experience. Organisations and communities were often forced to choose: keep history visible but unencrypted, or keep it encrypted but siloed from new joiners. Neither was the ideal solution. If you forgot to invite a person to a new chat, got a new team member, or a new person joined a working group they couldn’t see the conversation history.

How it works: Privacy by design, convenience by choice

Our new feature bridges this gap without compromising the integrity of your E2EE environment. When a chat admin chooses to allow new members to see historical messages, Element now intelligently and securely shares the necessary historical decryption keys with the new participant when they are invited. Instead of broadcasting history in the clear, we’ve developed a secure mechanism to share key bundles directly with authorised new members.

Chat admins retain full authority. You can decide chat-by-chat whether to enable history sharing, ensuring that sensitive discussions remain protected while collaborative ones become truly productive. Crucially, your data remains end-to-end encrypted. The keys are shared via private, encrypted "to-device" messages, ensuring that the history is never exposed to the homeserver or any third parties.

How to use it?

If you want the history of the chat to be shared with new members, just go to the room’s Privacy & Security settings and set the “Who can read history?” to “Members (full history)”. That’s it.

Decide who can read message history
Decide who can read message history

When creating new encrypted rooms, by default the history is not shared. The room header displays whether the history is shared so the members are aware of it at all times.

The room header displays whether the history is shared
The room header displays whether the history is shared

A note about existing rooms

If you notice an existing room in which history is shared, but should not be - you can change that in the Security & Privacy settings before inviting new members. Note that according to the Matrix specification, all historical messages should be made visible to new members if the message was sent while room history was set to shared. However, because some rooms may have accidentally had history sharing on without users realising that, there is currently an additional constraint in place that keys for such past messages are only shared with new members when the room is currently set to share history.

Future enhancements

History sharing does not work yet when a user joins a room via a Space proactively. They need to be invited to the room since the keys for the past messages can only be provided by an existing member of the room (the one who invites them).

We’re really pleased with enabling easy, secure history sharing for new chat members. As far as we know, it’s unique to Element. We’d love feedback on your experience of using it; like any new feature it can doubtless be improved and polished as we get insights from our end-users.