Post

That is a long headache that gets complicated based on the org and IT structure. Surprisingly difficult with some governments. In the case above I would strongly prefer that they use their domain but have given up having that fight endlessly and my moderation team trying to do tech support.

I see. What's the calculus then to decide to verify anyway? I can see value in drawing that line, with the justification "we don't want our users to just take our word for it, we want to demonstrate the trust signals of the network"

0 reposts2 likes

I think if it wasn’t a novel mechanism we’d have more uptake and less confusion. Emily wrote guides but it ended up being largely tech support work. I can’t train a moderator on policies and domain configuration easily so gave up on that as a requirement. Entirely capacity driven.

Setting a DNS record (or a text file on the web server) is hardly a novel mechanism, it's how every single platform does domain verification. Anyone with a website can do it so long as their social media team can talk to their web team. They'll have had to do it for Google Analytics etc already.

That's fair. I've wondered about an in-app nudge for accounts that have a single website in their bio. That's likely to be their website, and we could poke them to say "hey, looks like you've got a website, wanna set that as your handle?"

All out of the hands of trust and safety though. Not disagreeing with your recommendations but requires a cross team effort to drive this and all I own is whether a badge is issued via a consistent process.