| title | date | draft | author | categories | tags | |||
|---|---|---|---|---|---|---|---|---|
Two reasons why organizations should switch to self-hosting social media |
2017-03-16 |
false |
gargron |
|
|
My name is Eugen Rochko and I’m the creator of Mastodon, a free, open-source federated social network server. The flagship instance mastodon.social has over 23,000 users and is growing fast. You can check it out here.
If your organization is hosting a Mastodon instance, it is essentially a self-perpetuating brand awareness campaign. When people from other instances talk to or follow your users, they see your domain name all the time, since it is part of their globally unique usernames. It’s like those sticker ads on cars, except you don’t have to pay for them and it doesn’t disturb anyone because you’re providing a service.
{{< figure src="https://cdn-images-1.medium.com/max/2000/1*LM_XJwv6YpeZxBFMJVty_A.jpeg" caption="Addressing a user from another instance" >}}
Twitter has put their API behind a paywall, strangled the app ecosystem. Twitter censors tweets on behalf of countries like Turkey, messes with its content delivery algorithms in unknown ways. Remember when Facebook changed its news feed algorithms, and overnight every Facebook page’s posts became virtually invisible and “fans” worthless? Unless you paid up to Facebook, of course. Being in control of your own megaphone rather than relying on a third party letting you use theirs is increasingly important.
Your own Mastodon instance means you decide what content to host. You take back control from commercial companies. And without sacrificing reachability — normally if you self-host a website, forum, or blog it means having to bring everyone over from other places, but the federated nature of Mastodon means that people don’t need to leave their own instances to follow yours.