This wired article ( https://www.wired.com/story/join-mastodon-twitter-alternative/ ) about Mastodon is mostly good. It covers the basic features and talks about a shift from Twitter to Mastodon.
It confuses one key issue though, and that’s the “culture” of Mastodon.
What we’re seeing now across the Fediverse are the first adopters. The fringe. The queer. The hackers. The staunch individualists. The communal care takers.
As Mastodon becomes more mainstream, the “culture” will shift.
If you’re here for the culture, be wary... 1/2
Mastodon at it’s heart is a software application wrapped around a federated protocol.
Anyone can use it. Spin up an instance by thenselves or join one they like. It can federate with any other software application using ActivityPub. It is decentralized. HIGHLY resistant to censorship.
And this last part is key.
This platform is IDEAL to users that espouse unpopular viewpoints: fascism, hate, calls for violence, illegal content, etc. 2?/2...
While the culture is of first adopters and is open and affirming right now. Nazi’s and Fascists and $BAD_ACTOR’s will move in once they realize they can’t be censored or kicked off their own instance.
Those who left twitter because Jack didn’t ban folks there are going to be sorely disappointed when they realize that (while folks can be banned from one instance) they can’t be banned from their own instance. 3/2
@kiplet - Yes! And federated with other like minded instances! All running on Mastodon or similar software (eg Pleroma) and using ActivityPub.
So *your* Mastodon community might mute or block their Mastodon community, but they’re still in the Fediverse.
Which is fine.
@tinker I like it. They're free to make their own sub-Confederacy of Gab, and we can mostly not ever be troubled by them.
@galaxis @kiplet @tinker
@rick_777 I'm worried about the possibility that one day, some trolls would write a DoS script to send trolling messages to their victims, which abuses the protocol to make it appears originated from thousands of instances. Or simpler, just launch a flooding attack.
To what extent the current implementations are able to withstand such attacks? If not, perhaps we should do something early on.