@christopher @david_ross The person who started it burned out. A cooperative might take ownership over it (or at least they were talking about taking it over).
@skiant @david_ross I am sad to hear that. ๐ Hopefully he will get better.
@skiant @david_ross Oops, sorry. My gender bias hit me...
@david_ross it's like saying Linux is closing or Crypto currencies will disappear. It will never close simply because anybody with a computer can recreate it in a weekend
@NoLimitCoin it's a particular hosting service that is closing. I stand by the statement as I am NOT referring to Mastodon.
@david_ross I thought the title was Mastodon is closing.
@david_ross I was catched by the upper case S like a newbie. Silly me.
Any updates from social.coop on this @mayel
@nev any updates? ^^
@david_ross Sorry, I don't know!
@david_ross
Who is hosted on maastodon?
@david_ross
Octodon's a big one.
@thegibson It's one of only THREE Mastodon hosting services I'm aware of, so I'd imagine there will be plenty affected.
Alice is keeping her instances, so that's not something to worry about. She's just burned out on running the business side of it.
@Mainebot yeah that was 100% communicated and I'm disappointed another person in tech has hit burnout. I won't @ them out of decency, but just to say thanks to them for making decentralization available to less tech focused folk.
I'd consider taking it on, but I'd need some insights first. Will reach out in email.
@thegibson @david_ross mastodon.social used to be until three days ago, too (I think it was a temporary measure?)
@bhtooefr @david_ross @thegibson in some ways these closures are a healthy sign -- an instance is shutting down, but the fediverse is still strong. This is nigh impossible in corporate social media platforms.
I do think it's important to learn why & how the closures are happening--not so we can prevent them, but so we can build healthier, more resilient communities.
@edsu @thegibson @david_ross And, this isn't even instance closure, it's just a hosting service winding down (and the owner focusing on her own instance).
@bhtooefr @david_ross @thegibson you're right, it's not instance closure, it's instanceS closure ...
@edsu @thegibson @david_ross @bhtooefr Seems like a good reason to avoid instances that rely on Mastodon-specific hosting.
@seanl @bhtooefr @david_ross @thegibson yes, there's some truth to that for sure.
@thegibson @david_ross @bhtooefr @seanl btw, if you are curious, part of the discussion of whether social.coop should take on maastodon is happening over at https://www.loomio.org/d/jgGJ8ucA/proposal-to-take-over-a-mastodon-hosting-service-hosting-external-instances-but-also-to-enable-the-creation-of-thematic-sister-coop-instances
@edsu @seanl @bhtooefr @david_ross
good to see....
if Mastodon.social is lost, that will be a real problem for the fediverse... I don't think the fabric will deal well with that big of a hole.
@thegibson @edsu @bhtooefr @david_ross Is mastodon.social hosted on maastodon.net?
I'll feel a lot more comfortable with this idea once the "Support account migration" issue has been closed. It seems like quite an important feature if instances are going to periodically disappear.
@robinjanssens that's a good point --- but sometimes it's nice to start over ---
so it's not a wash.
@robinjanssens also, holy issue thread batman -- that conversation is gold, thanks!
@david_ross Oh no. Does somebody know the reasons?