Twitter source code reveals end-to-end encryption feature
2 min. read
Published on
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
Key notes
- Twitter first started working on an encryption feature in 2018, but the development was abandoned.
- References to end-to-end encryption are found in Twitter's source code, suggesting that encrypted DMs are coming to Twitter.
Twitter is going through a lot of changes currently, and following the addition of end-to-end encryption in Messanger, it seems that Twitter is working on a similar feature.
This is a welcome feature since it will encrypt the communication between the two participants, making it completely private from third parties, including Twitter.
Is Twitter bringing back DM encryption?
According to a recent tweet from independent researcher Jane Manchun Wong, it seems that Twitter is planning to introduce end-to-end encryption for direct messages.
As you may know, Twitter already worked on a similar feature called secret conversations way back in 2018. However, the feature has been abandoned for unknown reasons and never fully developed.
While looking at Twitter code for Android, Wong noticed several references to the encryption keys in the code.
In the source code, there’s even a message mentioning encryption keys and end-to-end encryption between the two parties.
The introduction of end-to-end encryption will make communication more private between the two parties, and it will provide an additional layer of security in case Twitter gets breached.
Currently, there’s no official confirmation from Twitter regarding this feature. Twitter owner Elon Musk responded to Wong’s tweet with a winking emoji which we assume is a subtle nod that this feature is in development.
Most users rely on encrypted messaging software for secure communication, and it’s encouraging to see that Twitter is focusing on the privacy of its users.
Are you excited about end-to-end encryption on Twitter? Let us know in the comments section below.
