But if there is an official CNN Mastodon instance, it’s suddenly real easy to see if someone claiming to be a CNN reporter is real or not.
Are they @john.smith@cnn.news? If not they’re a fake.
It would also work for official Microsoft accounts or Colgate-Palmolive or the government.
Seems like a good idea to me. And if you like federation it sounds better than a semi-official instance everyone uses that verifies things, sort of recreating a mini-Twitter “super” instance that is “more equal” than the others.
I can put an @microsoft.come email in my profile, but it’s meaningless because it’s not verified.
But if MS has their own instance, then your handle(?) proves you have an account on that instance. And presumably only employees and company accounts would be allowed to have such user accounts.
Note, however, that Mastodon has a sort-of identity-ish verification system, in that a website link in your profile will be shown with a green check if the website links back to your profile with a `rel=me` attribute.
Like sure, slack / teams can see all your data, but if you have a trivial problem such as being in the EU, you suddenly now have a compliance problem if specific data gets put on the service.
Run mattermost on your own server and many of the problems go away.
Mastodon is a bit different because it's federated, but I assume since it's more akin to a social network, it's similar to running a community support website compliance wise.
check your company intranet. chances are probably great you can find your own 'twitter' clone struggling in an overcommitted vmware instance or chugging along on a second generation Intel pizza box somewhere in a forgotten closet. These things never got patched because the implementation came from the vendor (along with free merch), so theres no local knowledge on how to fix them if they ever break. If you look hard enough, you might even find the add-on "blogging" platform your company got sold when they complained discount twitter for the office wasnt engaging anyone.