Strategic Decision by Meta Favors the Community More Than the Priority of Absolute Privacy during the First Rollout

Meta, the company behind Facebook, WhatsApp, and Instagram, has now widely deployed a long-awaited feature to its microblogging service Threads, direct messaging (DM). While this addition addresses a long-standing user request and moves Threads further towards becoming a standalone social network, a significant detail has emerged: the DMs are not end-to-end encrypted. Such a move by Meta raises an important debate on user privacy, platform strategy, and the new face of digital communication.

Rollout and its restrictions

The new DM feature enables the Threads users who are 18 and up to have one-on-one text-only communications with their followers or mutual followers on Instagram. Available through a new envelope icon, its first features are rather simple, as it supports textual messaging, emotive reactions, mutes, and spam reporting. Meta has noted that the future updates will involve even more complicated features like group chats and inbox filters.

Nevertheless, end-to-end encryption (E2EE) is one of the key concerns that draw attention to privacy-related users. In contrast to other popular communication platform of Meta, WhatsApp, Threads DMs lack the safety of communication provided by the messaging service. It would imply that Meta company, the operator of Threads, could theoretically access the contents of this message in case of the need.

What does End-to-End Encryption mean?

End to end encryption is a technique of safe communication technique whereby a third party would be incapable of accessing information as it moves between one end system or devices totally. Simple as it is, the messages can be read only by the sender and the intended recipient. The content of the communication cannot even be accessed by the service provider (in this case, Meta). This is the reason why E2EE is taken as the gold standard of privacy in digital conversation.

What is the reason they do not encrypt? Meta’s Perspective

Responding to the move, Meta confirmed the move to Bloomberg with its vice president of products Emily Dalton Smith saying that encryption is not of more essence to the community focused messaging by Threads community. As she pointed out, the original aim of Threads DMs is a direct connection and communicating with each other on whatever is currently happening, finding continuation in long-existing community interactions within the common field of the application. This indicates a plan of strategic separation with services such as WhatsApp, which are exclusively aimed as safe personal messaging programs.

Rather than focusing on the privacy of messages at the very beginning via E2EE, it seems that Meta prioritizes the fast implementation of features and community input. According to the company, it is going into DM rollout with a safety-first attitude, including limiting DMs to 18+ and by limiting DMs to Instagram accounts that already follow or are being followed by each other. They also state, that their messaging has been safeguarded by their high-level privacy standards, account security and safety infrastructure.

Speed and Integration comes first

Among the possible justifications of the lack of E2EE, there may be the wish to integrate and implement the DM feature fast. Technically, a secure end-to-end encryption is a complicated process that may need extensive efforts and long development time. Meta could have been trying to make DMs available to Threads users sooner at the expense of delaying E2EE, thus making the app more functional and competitive with its current competitors (e.g., X (formerly Twitter)).

More than that, Meta has been developing a more comprehensive project to integrate its different messaging apps (Messenger, Instagram Direct, WhatsApp) into a one backend system. Although this ambitious project targets a smoother and possibly an encrypted cross-platform experience in the future, this is a complex effort, which might contradict the short-term rollout plan of Threads DMs.

User to User Implications and Future of Threads DMs

The move to introduce Threads DMs with no end-to-end encryption begs some legitimate questions to users, who attach importance to digital privacy. Although Meta maintains that it has a safe infrastructure of its technology, those differences between non-encrypted and end-to-end encrypted lines of communication remain basic. When the chances of sensitive discussions are at stake, there are still alternatives where E2EE is enabled by default.

E2EE that is lacking on Threads also makes it stand in another league when compared to some of its competitors. As X actively continues to expand and at other times discontinue its end-to-end encrypted direct messages, Bluesky, another decentralized microblogging provider, focuses on user agency and privacy more as principles, and several of its influencers already distrust such services, as they have done with other services, setting its platform more towards privacy-conscious customers.

The question as to how user feedback will inform the future of Threads DMs will have to be asked. Since the platform is still in the process of becoming a full-scale social network, rather than merely being an Instagram companion, the need to further expand into offering improved privacy due to the addition of such options like end-to-end encryption, will only increase.

Meta has stated that it is going to keep working on DMs in Threads based on user feedback, so the future performance of E2EE may well have good results. Until that day comes, Threads users are advised to be careful and aware of the encryption status when having their personal chats.