first of all, performance, performance, performance (esp. on the UI level). this is so important for social media apps that aim to work at scale.

also, if you want to claim a "first", I would like to see ENS account verification being natively supported by a social media application. no other social media app/frontend seem to take have taken initiative (yet).

for anyone reading not aware, ENS is a decentralized web3 identity/username registry allowing you to use your identity across applications and blockchains.

over 500k users have been using it over the past 5 years to pseudonymously to participate in Defi, DAOs and NFT collecting.

due to it´s decentralized nature, I would claim it as a perfect fit for web3 social account verification. if we take the recent entrance of @vitalik.lens as an example, he added his #lens handle to a text file on his hompage to prove that the account is actually controlled by himself.

however, if ENS account verification would have been enabled on lens frontends, users could have directly verified by his ENS name, that the @vitalik.lens handle is actually controlled by himself.

small mockup below