Notices by Joseph Quattrocchi (quattrocchi@mastodon.cloud)

@Sujiyan @mellifluousbox @haubles Instance closures seem to be very common. Should Mastodon GmbH consider offering a service to take over or host instances that are losing their maintainers?

Of course, full data portability would make closures less disruptive. But the persistence of posts themselves is also important: old posts help people navigate, search, and filter the enormous volume of information on the internet. When an instance disappears, that public record can disappear with it.

@Sujiyan Apparently there is a bot campaign to delete mastodon.cloud. Seems nefarious.

https://masto.ai/@Linux/116433041170995383

@warning @Linux @Sujiyan @mellifluousbox @haubles The instance maintainer is active and engaged, regularly posting content. The instance is funded, and the organization behind it has a track record of supporting and developing Mastodon.

The conflict: (1) .cloud is based in Japan, (2) they aim to keep the instance open, (3) they lack dedicated admin and moderation teams, though that’s common across many instances, and (4) it’s one of several internet projects they support, not a primary focus.

@Sujiyan They point to a few examples, which overstates the scope of the issue. Here's the link: https://social.chinwag.org/@FediThing/116030359239630783

@Sujiyan There is a renewed viral campaign calling for users to leave or mass-block this instance. Since I’ve been using the service, there have been several such campaigns, focused on moderation levels and software updates.

Given the broader impact on the user base, it would be helpful to know whether and how you plan to address these concerns, or if there is an official statement users can reference.

@FediTips The admin’s main account is @Sujiyan, boosted from @TheAdmin. Their last post was on August 7, 2025. Hopefully, concerned Fedizens are motivated to work toward constructive solutions with them.