Some examples:
- https://fosstodon.org for FOSS - https://infosec.exchange for infosec - https://sfba.social for the bay area
There's a map of locality-specific instances here: https://umap.openstreetmap.fr/en/map/mastodon-near-me_828094
Some examples:
- https://fosstodon.org for FOSS - https://infosec.exchange for infosec - https://sfba.social for the bay area
There's a map of locality-specific instances here: https://umap.openstreetmap.fr/en/map/mastodon-near-me_828094
> Please consider joining @mastodon.acm.org, a community for #computing researchers & practitioners to connect & exchange ideas with each other, whether you are an ACM member or not.
I feel the response might be something akin to "what would happen if you have a fastmail account and then fastmail closes?". If that's the case, I see absolutely no reason to choose a small instance, just for the sake of reliability and trust in its continued operation.
It's better than email in that regard.
The Covenant includes a commitment from server admins to give users at least 3 months of advance warning in case of shutting down
You can also use a paid instance like https://cloudisland.nz/ or set up your own using a hosted service like masto.host
The problem you describe is real, though, and it's the least friendly thing about Mastodon for new users.
I'd pick a large instance to start with, and move at your leisure.
I'm camped out on a friend's server right now, he said it was strictly for amusement but he's having a whale of a time being a Mastodon admin. When he says he'll definitely give us 2mo notice if he gets sick of it, I know I can trust him on that. That sort of thing.
It's what I did for myself (Follow me! @jerome@leclan.ch), following Simon Willison's post: https://til.simonwillison.net/mastodon/custom-domain-mastodo...
"hi! there's been a huge wave of new members and new instances recently, and that's a Lot of work. i am tired and especially won't be very available in the next months for health reasons, so i won't be accepting new instances for a while." https://fedi.monster/
"Due to overwhelming demand, registrations are currently closed." https://cloudplane.org/
I went this route (via https://marketplace.digitalocean.com/apps/mastodon - I would have used masto.host otherwise). Im keeping an eye on Takahe (https://news.ycombinator.com/item?id=33731739) as hosting mastodon is kind of expensive, for the type of use I make of it.
It’s been working for a few years now and (luckily) I never had major incidents.
It’s very refreshing to be in full control of one’s data (compared to the centralised experience with other socials like Twitter and Facebook).
I will likely switch to Takahe (https://news.ycombinator.com/item?id=33731739) as soon as it's a little more ready, for the reasons you describe.
Some of that could be improved with UI changes but to address it satisfactorily probably requires the server to do some proactive crawling beyond what’s dropped in your inbox.
For just ownership of identity keep an eye on this issue:
I really like the idea of different organizations running their own instances. You don't need an overbearing, exhaustive and centralized system of verification for journalists when something like WAPO or NY Times can run an instance for their employees, much like how email works.
Edit: A lot of journalists just learned about the value of owning their distribution platform now too lol
The biggest advantage of a big instance like mastodon.social is that account discovery and following are much easier when the accounts are on the same instance of you. Otherwise, you have to do a lot of copy and paste into search fields.