@signalapp I hope you support some kind of optional verification in Keyoxide style.

E.g. "this Signal account verified they control this Mastodon account and this website", but with better wording so people don't just set up lookalike accounts and websites, but it still works to deter impersonation.

The main reason I use Keyoxide is because I got impersonated in Wordpress.org blogs (which do not provide any kind of authentication). AFAIK the only way to prevent that in that platform is using PGP signed messages, which are cumbersome, or using plugins that require login, which are annoying.

@Yuvalne @signalapp So you wouldn't want verification of public identities in Signal? Isn't that exactly the problem of people impersonating Signal? The two verifications don't exclude each other. Make it optional, not everyone has a public identity that needs to be verified, but for those who have, it's important.

Also, safety numbers? No one checks them. Maybe you and tech people, but never in my life did someone check others' numbers but me. Even with those numbers people apply scams every single day working around that: "hey, I got a new number! i broke my old phone!" "ok!" then some days later "I'm broke! can you send me some money?". It happens every single day! Even with security numbers!

Would an optional identify verification fix that? No. Would it improve in some cases? Yes.