Crypto Twitter shares security concerns regarding Meta’s recent NFT integration news

Meta recently announced its latest NFT feature will allow users to connect their digital wallets to Instagram and Facebook.

On Aug 29, Facebook and Instagram’s parent company Meta announced that its users will now be able to post digital collectibles and Non-Fungible Tokens, or NFTs, across both platforms by simply connecting their digital wallets to either site.

While Meta’s announcement may have seemed to some like a mass adoption win for some digital asset enthusiasts, not all members of Crypto Twitter were thrilled by the news.

Skeptical users took to social media to express concerns surrounding the security and privacy of the data disclosed when digital wallets are connected to these social media platforms.

Twitter user and Web 3 community member NPC-Picac tweeted, “I don’t think entrusting digital collectibles to connect to “Meta” is in any way smart”

Another Crypto Twitter community member, CryptoBartender, raised concerns about what Meta could possibly do with the data they access from digital wallets, tweeting, “So they can figure out which wallets are yours and keep tabs on you and your crypto activities?”

Some users felt that publicly attaching valuable digital assets to one’s identity could turn users into targets for fraud and theft. A user operating under the handle famousfxck questioned, “This is great for adoption. But isn´t it also dangerous?”

Others shared their thoughts on individuals broadcasting even more personal data for the benefit of companies that have long histories of abusing users’ data and privacy.

In the announcement, Meta disclosed that, as part of keeping its platforms safe and enjoyable, “people can use our tools to keep their accounts secure and report digital collectibles which go against our community guidelines”. Meta has not yet shared any concrete plans it has to keep its user’s digital wallet-related data safe.

About Author


Deprecated: Directive 'allow_url_include' is deprecated in Unknown on line 0