Mastodon.technology Shutdown
ashfurrow.com
Mastodon.technology Shutdown
1–10 of 604 posts
Re: Mastodon.technology Shutdown
#2I am sorry to hear that, but I can totally support them, and sincerely wish them the best of luck, dealing with a pretty awful situation.
Re: Mastodon.technology Shutdown
#3I always suspected this would be a massive problem with Mastodon. I contemplated running a server, but there's no way to know beforehand when you'll be running into a limit, like cost or time. Can you really build a social network on volunteers that invest their own money and time, with little reward?
Re: Mastodon.technology Shutdown
#4I think it’s unfortunate for us users but at least on an open source platform migrating to a new instance is possible. That said - this will be a hit to the community.
It just shows how relying on infrastructure with a low bus factor is risky and something for future attempts to consider.
Re: Mastodon.technology Shutdown
#5Re: Mastodon.technology Shutdown
#6Not different enough than Twitter or too different from it?
Not enough marketing?
Bad UX?
Re: Mastodon.technology Shutdown
#7The mastodon.technology had some interesting folks. I've migrated my account to the mastodon.social instance. Moving accounts on Mastodon is pretty easy so that's a positive.
Re: Mastodon.technology Shutdown
#8I think that's a very salient and responsible choice. With the freenode debacle coming to mind immediately I think it's important to remember how risky a change of ownership can be in particular if the users are not aware of it. Certainly a painful decision to shut the instance down, but a decision with a lot of foresight. An active migration might create disarray but it also forces people to make an active choice to trust another host.
Re: Mastodon.technology Shutdown
#9Thank you for your volunteering and I hope your family member gets better Ash. I think it’s unfortunate for us users but at least on an open source platform migrating to a new instance is possible. That said - this will be a hit to the community. It just shows how relying on infrastructure with a low bus factor is risky and something for future attempts to consider.
There are risks to every "bus factor," but I can totally get behind requiring a team of a certain size to be behind whatever infrastructure I rely on.
Most of my dependencies have a bus factor of 1 (Yours Troolie), as I write packages for my own consumption.
They are really, really good modules, and I publish them as general-purpose modules, but don't expect people (other than me) to really use them.
I did write a fairly massive infrastructure project, and managed it, alone, for ten years, then it was taken over by a team, and "went viral," in a sense. The best thing I ever did for that project, was toss the keys to the new team, and walk away. It's in very good shape, now.
Re: Mastodon.technology Shutdown
#10What do you think is the main issue with Mastodon not really getting mainstream adoption? Not different enough than Twitter or too different from it? Not enough marketing? Bad UX?
Also recent privacy concerns and less recent issues with internet hostility means we're already past peak twitter, so mastodon is having to break into a declining market.