Skip to main content


⚠️ Important headsup if you are on the server mastodon.cloud:

Mastodon.cloud no longer seems to be moderated. Its admin account hasn't posted since Feb 2023, its code of conduct is blank and there are vile racists posting from there. The racists have been reported many times but their accounts are still active.

Because of this, other server admins are starting to block mastodon.cloud completely.

If you're on mastodon.cloud you might want to move to another server ASAP: fedi.tips/transferring-your-ma…

in reply to Fedi.Tips

No need for me to worry about that since I already migrated a long time ago!
in reply to Fedi.Tips

hey @OpenForumEurope you may want to move off Mastodon.cloud

It's not going to be a good look remaining on an unmoderated server.

in reply to Fedi.Tips

according to this article (the contact email there is for sujitech) the instance is run by the same people as at least Pawoo, mstdn.jp. The company still seems active...

masknetwork.medium.com/why-we-…

This entry was edited (3 months ago)
in reply to ikuturso

@ikuturso

Either they aren't moderating, or they are allowing really awful stuff to be hosted.

Either way, it's not a good idea to be on such an instance.

in reply to Fedi.Tips

Extreme racism, n-word

Sensitive content

This entry was edited (3 months ago)
in reply to Fedi.Tips

Extreme racism, n-word

Sensitive content

in reply to Fedi.Tips

p.p.s. A lot of legitimate non-problematic accounts joined mastodon.cloud when it was still moderated. I'm guessing most of the ones still on there are there because they don't realise what has happened.

If you know someone still on mastodon.cloud, you might want to politely let them know what the situation is and suggest they move. I'm sure most will be horrified about what's happening and keen to move to a different server. If they need help moving, the guide is at fedi.tips/transferring-your-ma…

reshared this

in reply to Fedi.Tips

Can sympathize, m.c was my first home on the fedi because I didn't know the lay of the land, as it were, and it had open registration. I used the account less and less and eventually deleted it a couple years back, but good neighbors can definitely join bad instances out of sheer ignorance and stay because the face-eating leopard hasn't eaten their faces (yet).
in reply to Fedi.Tips

Is it possible to search?

newsie.social/relationships

Full Mastodon addresses aren't completely viewable

in reply to psuPete

@psuPete

As far as I know you can't search your follows/followers list, sorry 😔

in reply to Fedi.Tips

@psuPete might be possible if you export your follower list as CSV (in Mastodon, it's in the Preferences under "Export") and then inspect the CSV with a text editor or spreadsheet application
in reply to Fedi.Tips

Is there a way to search (easily 😬 ) my follows and followers for their respective instances?
in reply to Fedi.Tips

thanks for this post and associated tips. Have thought about moving server before but this post pushed me to act. Thank you.
in reply to Kev

@edgeofstretch

Thanks for taking the time to write these kind words, it's really motivating to hear these posts are useful!

Good luck on the new server 🙂

@Kev
in reply to Fedi.Tips

p.p.p.s. Mastodon.cloud seems to be running a very out-of-date version of Mastodon's server software. This is a bad sign as it means there may be unpatched security holes etc.

This lack of technical updates is another reason to leave mastodon.cloud as soon as possible.

It's never clear how long unmaintained servers will continue. If it disappears without warning, it will be too late to move your account.

If you want help moving, feel free to ask! Also see the guide at fedi.tips/transferring-your-ma…

This entry was edited (3 months ago)
in reply to Fedi.Tips

Cupoftea.social will happily take anyone in need of a well looked after and up to date instance.
in reply to Fedi.Tips

just moved from there to another server, following your instructions (which I found very clear and easy to follow).
in reply to Ken Butler

@nxskok

That's really great to hear, and thanks very much for the feedback 🙏

in reply to Fedi.Tips

true federation will exist when migration will be possible in 3 clicks
in reply to Fedi.Tips

thanks for this! Is there really no way to transfer one's posts to the new server? That seems like a major limitation to changing servers..
Sorry if this has already been asked
in reply to El Duvelle

@elduvelle

- If the server stays online, you can leave your old posts there and they will redirect people to your new account. So, they don't disappear as long as the old server keeps running. More info in transfer guide at fedi.tips/transferring-your-ma…

- You can download an archive of your posts and either keep it for your private records or upload these to a website (there are some services that let you do this for public posts). More about archives at fedi.tips/how-to-download-your…

in reply to Fedi.Tips

thanks!
I thought it was possible to somehow upload the downloaded posts to the new server.. Maybe @jonny would know if that's a thing?
in reply to El Duvelle

@elduvelle

It's not a thing in base masto or glitch, as far as I'm aware, but not for any good reason - one could upload the archive and backdate all the posts even if they wouldn't be treated as the same as the originals by other instances/wouldn't have replies/interactions

in reply to jonny (good kind)

This is possible and it has been done by Fedi platforms such as Firefish which accepted Mastodon archive uploads, but AFAIK they had problems with instance resources?

(For what it's worth, the uploads created new posts with no connection to the old threads but the content was the same.)

This entry was edited (3 months ago)
in reply to Fedi.Tips

This is a solved problem with GoToSocial.

First, they allowed backdating statuses.

Which allowed importing old statuses.

One of the devs created a tool, Slurp, for this purpose. It uses your existing Mastodon archive.

At this time, GoToSocial is the only platform I'm aware of that can handle not just account migration, but post migration as well.

This page talks about migrating to GoToSocial and using Slurp to migrate posts.

This entry was edited (3 months ago)
in reply to D. Olifant

Oooh interesting, thanks for that! 👍

How does it handle the resource issue? Is this part of GTS's design for smaller instances, or can it handle large amounts of members migrating posts?

(EDIT: From that link it sounds like it's currently for small/single user instances?)

This entry was edited (3 months ago)
in reply to Fedi.Tips

Yeah, it doesn't have to worry about the problems of running thousands on the same instance because it's not really designed for that. Although, if there was a large instance like that, they could just prevent it entirely by turning off backdated post imports at the server level in the config yaml.

It's not so much that it can't handle large volume or large amounts of members migrating posts.... it probably can?

It's just that no one has ever tested it. I'm not aware of anything I'd consider a "large" GTS instance, for one. I'm not aware of anyone with, say, 20k followers migrating to a GTS instance, or importing a massive archive to it.

in reply to D. Olifant

@oli

On a slight tangent, I've been trying to find some public GTS instances to list on @FediGarden but there don't seem to be many?

I'm wondering if this is a result of a deliberate design to keep GTS for very small instances? Or maybe the larger GTS instances will appear in time?

in reply to Fedi.Tips

Things like Fediverse Observer and FediDB started dropping many GoToSocial instances, after GTS started messing with scrapers ignoring the robots.txt by permitting admins to create ridiculous stats. This messed with the overall stats of the fediverse, so essentially a lot of GTS instances got wholly blacklisted from public directories, regardless of whether they enabled the 'spoof' setting or not.

Which....I guess stopped those places from scraping GTS server endpoints.

Some people are really mad at the authors over it, but all it's really done is take GTS off the official statistics board entirely.

in reply to D. Olifant

@oli @FediGarden

Ah, yeah, I'm not doing any kind of FediDB-style automated list. Fedi.Garden is just a small manually curated list of good instances that people can join. I don't have any stats, it's just public instances where I've contacted the admin and discussed their safeguards for reliability and moderation, then got their consent to be listed.

GTS doesn't seem to have any public instances at all though?

I'm partly worried about what happens if Mastodon software goes south. Hard fork?

in reply to Fedi.Tips

Mine can be considered public in the sense that you can sign up and your registration will be approved or rejected
in reply to moanos

@moanos @oli

Yeah, that's what I'd call public! In fact it's arguably better if it's approval-based because it shows proper moderation is going on.

in reply to Fedi.Tips

I mean, here's goblin.technology, run by Tobi who basically started GoToSocial.

goblin.technology/

It allows signups. So I'm not sure if that's public or not.

ALL GoToSocial instances require manual review for signups however.

This entry was edited (3 months ago)
in reply to D. Olifant

@oli
@elduvelle
Ya totally. Importing the posts shouldn't be too hard, literally just copy pasting db rows. No reason glitch/masto can't do that. Getting other instances to recognize the move and preserving replies/etc. Would require a bit of work but I don't see a fundamental reason it can't be done. This is one of the essential fixes that needs to be made in base masto to make all other fedi apps easier for instances to try: if we could easily migrate all our accounts in a history-preserving way, that makes it actually possible for us to consider switching to e.g. gotosocial, but without that we can't.
in reply to jonny (good kind)

Yeah, Slurp elides the problem by simply refusing to import any post with a @mention in it. So you essentially are able to import your old posts, but not preserve entire conversation threads.
in reply to D. Olifant

in reply to D. Olifant

It wasn't obvious (to me) from the documentation, but slurp can also dump posts (and other stuff) from one GoToSocial server to a file which you can use to push into a new GoToSocial instance as if it were a Mastodon archive. That was extremely useful when I migrated to my self-hosted GTS.

It appears to work on anything with a Mastodon API, because I also used it to pull down posts/followers from two Iceshrimp instances as well. I haven't tried it on a Mastodon instance, but I believe this means you don't even need a manual export from Mastodon.

@jonny @FediTips @elduvelle

in reply to jer

@nyquildotorg @oli @jonny @elduvelle

"I believe this means you don't even need a manual export from Mastodon."

Hmm... that sounds like it could be misused? 🤔

There was already that instance a few weeks ago that was found to be mass-cloning genuine accounts 😬

in reply to Ember ​

Ahhh okay, sounds good then! Thank you!
This entry was edited (3 months ago)
in reply to El Duvelle

@elduvelle

p.s. Just to add to why there is this situation, servers are run by volunteers who have to pay for all the server's running costs, they don't run ads or sell any data or have any investors.

If accounts move to a server and suddenly upload thousands of posts with perhaps hundreds of images etc, that can be quite a drain on the server's resources.

There was a Fedi platform which experimented with uploading archives, but it slowed down badly when big archives were uploaded.

in reply to Fedi.Tips

that definitely makes sense! Although I imagine servers could have limits in place for the size of migrated posts, or something like that...
in reply to Fedi.Tips

@elduvelle

I understand that many servers are in closets and run on residential energy rates, but identity on social media networks includes posts and images. We are what we wrote and we are what we will write.

It's good to design for the cheapest hardware and internet speeds but to be perfectly honest, some servers can afford it but choose not to because the low hanging fruit is to offer only the bare minimum as long as they can

in reply to David

@drdrowland @elduvelle

The posts and images don't disappear, they remain on the server where they were posted and their username directs people to your new account.

If someone suddenly uploads thousands posts and a similar amount of images, that will cause a strain. If many people do that, it will be even more strain.

The Fedi platform Firefish did actually try this, and it did cause problems. It's mainly to do with the amount of computing resources required to deal with many tasks at once.

in reply to David

p.s. Anything that you host online on other services will disappear at some point (theguardian.com/technology/201…).

If you need to make sure all your posts stay online, you can set up your own server. It doesn't require tech skills and it doesn't require much money either.

Managed hosting costs $5 per month for a single person with the hosting company doing all the techy stuff for you. I encourage people to do this with help and links to providers at growyourown.services/grow-your…

This entry was edited (3 months ago)
in reply to Fedi.Tips

@elduvelle

I love the tips, but making the case that it's cheap enough for an individual to do it only strengthens my case that institutions can and should offer this service for free

in reply to David

@drdrowland @elduvelle

It would be great if they did that, yes. It would be a bit like in the early days of the web when people were often given free web pages by ISPs, universities, community groups etc 🙂

The price per instance also becomes a lot cheaper if a provider hosts lots of instances.

I guess question is which institutions would offer this?

in reply to Fedi.Tips

@elduvelle
i think instances should be able to refuse migration, if it is too big to handle.

I still think that true federation requires the possibility to move everything, posts included, in 3 clicks.

in reply to Fedi.Tips

not sure the best place to report this, it looks the moving from/to settings are now under Account. I used your guide yesterday to change instances, it was very helpful!
in reply to Chuck o Rama

@neontapir

Fine to report errors anywhere, thanks for taking the time! 👍

Which step(s) of the guide are you referring to?

in reply to Fedi.Tips

steps 7 and 10. It looks like Account isn’t under Preferences any more, it’s now a top level item.
in reply to Chuck o Rama

How are you getting to "Account" without clicking "Preferences"? (Genuine question!)
This entry was edited (3 months ago)
in reply to Fedi.Tips

oh, I see, my mistake. When I click Preferences on the main page, I see an item on the left labeled Preferences, and I was expecting Account to be under that. Truth is, time had passed since I’d navigated to the Preferences page, so I forgot that’s how I got there. Nothing to see here. 😀
in reply to Chuck o Rama

@neontapir

Aaah, yeah, I see what you mean!

It is sort of confusing that there's a main "Preferences" option in the general interface but then also a "preferences" section on the Preferences page.

Maybe they should rename it "Settings" for one and "Preferences" for the other?

Thanks for this, it is really useful to hear how people see the interface from their point of view.

in reply to Fedi.Tips

I like that, anything to avoid having two screens with the same name, which makes documentation a bear.
in reply to Fedi.Tips

Oh... The same admin also runs pawoo.net, explains a lot
in reply to Fedi.Tips

they have a second account btw: @ CensorsAreCultists@submarin.online
in reply to Fedi.Tips

re: Extreme racism, n-word

Sensitive content

in reply to 🐈 Kimapr La Gata

re: Extreme racism, n-word

Sensitive content

in reply to Fedi.Tips

the best thing to do with those kind of account is to ignore them and not give them the attention. If you share this for everyone to see you are giving them the attention they want. But yeah unmoderated instance can be pretty bad.
in reply to Konakona

@Konakona @Fedi.Tips

I agree with the idea of not feeding trolls though, as an Instance admin if someone says an Instance needs to be blocked then I want evidence as to why. Blocking another Instance is not something I do lightly. So yes, feeding trolls is not a productive thing to do. Though if you call out an Instance as being unmoderated you kind of have to provide evidence if you expect to be taken seriously.

in reply to Konakona

@konakona

If you let people spread lies about vulnerable minorities, it leads to real world discrimination, violence and murder.

How does someone ignore it when people are physically attacking them in the street?

in reply to Fedi.Tips

my point was that if you are a popular account and share their post you are actually giving them a lot more exposure. Which will only make it worse. Its like free publicity. I don't think you had any bad intentions sharing it. I am just saying its probably not really the best thing to do but its good to point out unmoderated instances because those have bigger issues than racist trolls.
This entry was edited (3 months ago)
in reply to Konakona

@konakona

If I don't give at least one example, some people will assume I'm exaggerating or overdoing it when saying it's racism. They'll say they've never seen anything like that and demand proof.

I tried to pick one example that was most clearly racist.

in reply to Fedi.Tips

fair enough. Though there are some of those so called "free speech" instances that allow such thing. But that one doesn't look like one of those. And yeah pretty suspicious they have no more rules or anything.
in reply to Fedi.Tips

Extreme racism, n-word

Sensitive content

in reply to Fedi.Tips

⚠️ Mise en garde importante si vous êtes sur le serveur mastodon.cloud :

«Mastodon.cloud ne semble plus être modéré. Son compte administrateur n'a pas posté depuis février 2023, son code de conduite est vide et d'ignobles racistes y postent. Les racistes ont été signalés à plusieurs reprises, mais leurs comptes sont toujours actifs.

À cause de cela, d'autres administrateurs de serveurs commencent à bloquer complètement mastodon.cloud.»

Si vous êtes sur mastodon.cloud, vous devriez peut-être changer de serveur au plus vite : fedi.tips/transferring-your-ma…

This entry was edited (3 months ago)
in reply to 0tracas💛

@0tracas
A noter que lorsqu'on migre son compte ainsi, on migre les comptes qu'on suit et ceux qui nous suivent, mais pas les posts eux-même.
------
Please note that when you migrate your account in this way, you migrate the accounts you follow and those who follow you, but not the posts themselves.
in reply to Calaad

I read someone suggest you boost all your old posts to copy them over and retain them if the old server goes down, as a workaround. That sounds scriptable, so maybe someone has already made a script for that, I wonder?
in reply to Marcus

@marcusxms @calaad

That might or might not work depending on whether the server shutting down sends out a deletion command. Many of them do this to tidy away posts from accounts that no longer exist.

You can download a personal archive of your posts but there's currently no way to upload this onto Mastodon:

➡️ fedi.tips/how-to-download-your…

There may be other platforms that allow archive uploads in the future, Firefish experimented with this at one point.

in reply to Fedi.Tips

Alright, maybe instead one could quote share the posts on Friendica and then refer to that account on Mastodon, or possibly boost those quote shared posts. That is until Mastodon itself gains the quote share functionality. I would assume those would not be deleted by that operation?

Or perhaps in that case one may as well script reposting them all, losing the original timestamps but retaining the content, or reposting them inside a quote with a printed timestamp of the original post.

in reply to Marcus

@marcusxms @calaad

There are sites that let you display your Masto archive online as a website, you could refer to these on your new account?

Alternatively, a script could possibly repost the archive to your new account? But it would probably be rate-limited by the new server as someone posting potentially thousands of posts might overwhelm the server's resources.

(This was one of the problems on Firefish's experiment, it overwhelmed the server when the archive being uploaded was large.)

in reply to Fedi.Tips

kinda wish there was a "no longer federate newly created accounts from this instance" thing
in reply to Thibaultmol 🌈

@thibaultmol

Yeah. I'm posting because there are legitimate non-problematic accounts which joined mastodon.cloud while it was still moderated and don't realise what has happened since then. Hopefully they hear about this and move.

in reply to Fedi.Tips

@sclower FYI, you may wanna consider moving, if you've not read the original post, its the one this is replying to.
in reply to Fedi.Tips

Cupoftea.social always happy to get folks over to a better maintained and well ran instance here
in reply to Fedi.Tips

You know what to do @tyler . Though it could just be a honey pot
This entry was edited (3 months ago)
in reply to Fedi.Tips

Looks like it's running an out of date version of Mastodon that stopped receiving updates in April too.
in reply to Fedi.Tips

@reflex I wrote a script to autoblock/silence unmaintained software versions during one of the spam waves: mastodon.scot/@gunchleoc/11197…
Unknown parent

mastodon - Link to source
Fedi.Tips
Vile racist account

Sensitive content

This entry was edited (3 months ago)
Unknown parent

mastodon - Link to source
Tekniquelly correct

@tanghus Got any links to the racist stuff? I just looked at the TL and it’s filled with random junk like an unmoderated ghost ship usually is, but I hadn’t seen the vile stuff yet.

(Not asking because I doubt it’s there, just researching before I suspend a server.)

in reply to Fedi.Tips

Vile racist account

Sensitive content

in reply to nicole mikołajczyk 🔜 39C3

If it's moderated, why is it allowing the worst kind of racial hatred even when it's been reported many times over a long period?
This entry was edited (3 months ago)
in reply to Fedi.Tips

I didn't notice any racist accounts until this was pointed out. Seems I have something else to look at defederating then.
in reply to Fedi.Tips

I moved from there in 2020 because the people then running it had announced it'd shut down. They did end up finding someone to take over. 🤷‍♂️
in reply to Fedi.Tips

We have suspended them already

Rina
Admin @ tootworld.social

in reply to Fedi.Tips

@stux can you please defederate from mastodon.cloud? there’s some really vile stuff there
in reply to Fedi.Tips

If anyone's thinking about moving, I can recommend kind.social/
in reply to Fedi.Tips

thank you. I had no idea. I joined up there many years ago but never actually look at the local feed or anything
in reply to Fedi.Tips

we don't normally repost from this account, but in this case, as we're actively monitoring this we decided we'd post it, and yes, we are considering blocking mastodon.cloud if the situation doesn't improve.
in reply to Fedi.Tips

Collective punishment is unethical. Rule violations are best handled individually, not through broad blocks by association. Mastodon.cloud, despite lighter moderation, has remained open and interoperable for years—unlike other instances that block hundreds of millions of accounts hosted on popular services and eventually shut down.
in reply to Joseph Quattrocchi

It's not collective punishment, don't be ridiculous. It's an individual's right and responsibility to choose an instance, and move instances if they don't like how it behaves.

You're infantilising Fedi members by claiming they have no agency or ability or alternatives.

Also, mastodon.cloud isn't even updating its own software any more, it's several updates behind the latest supported versions. This is not good for its members, it means security holes may not be fixed.

This entry was edited (3 months ago)
in reply to Fedi.Tips

It has become routine for viral posts to rally a mob into blocking entire instances—thousands of accounts—over a few bad interactions. While this may feel empowering for in-groups or those with large followings, it fosters a toxic environment. In this case, a dependable, useful, and constructive instance is being demonized and ostracized.
in reply to Joseph Quattrocchi

@Joseph Quattrocchi @Fedi.Tips

You really believe that an Instance that is several versions behind on support updates is dependable? You believe that people attempting to keep toxic content from being propagated are fostering a toxic environment? I am not understanding your motivations or reasoning here.

in reply to Unus Nemo

I'm motivated to defend an instance that has hosted my account for a couple of years allowing me to access the world wide public discourse by remaining open and interoperable. When other instances were blocking bridges to Threads, Bluesky, Twitter, and Nostr, this instance sought to build bridges. Brigading isn't punishing a negligent admin but all the users and undermining the viability of the protocol itself.
This entry was edited (3 months ago)
in reply to Joseph Quattrocchi

It's not a dependable instance. Its software isn't up to date, there may be bugs that put its users in danger.

The admin hasn't posted in 2.5 years, that is not a sign of dependability.

Quite often instances where the admin stops communicating for years may vanish without warning.

"Brigading isn't punishing a negligent admin "

It's not about punishing anyone, it's warning people that they are on an abandoned instance. Would you rather they weren't warned?

This entry was edited (3 months ago)
in reply to Fedi.Tips

I would have preferred a warning that there’s no official contingency plan if a large instance is abandoned—users are left to safeguard their data and reputations against norm enforcing vigilantes. This seems at odds with the promise that Mastodon and ActivityPub are people-centric.
in reply to Joseph Quattrocchi

The stuff being posted on mastodon.cloud is vile, utterly disgusting sewage. It is saying certain racial groups are subhuman, it is saying that skin colour reflects intellectual ability.

If mastodon.cloud are unwilling or unable to moderate ethnic hatred, even when it's been reported to them by many people over several months, then they shouldn't be running an instance at all.

If my instance was allowing such crap, I would want to be told about it so that I could leave.

This entry was edited (3 months ago)
in reply to Fedi.Tips

This is hostile overgeneralization: there may be evil in the world, but the whole world isn’t evil. Healthy community-building means amplifying constructive solutions and carefully managing destructive urges. While users can always defederate or moderate their own instance, what we’re seeing here is incitement to collective hatred — rallying a large following to ostracize an entire instance based on a few cherry-picked rule violating accounts.
in reply to Fedi.Tips

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.
in reply to Joseph Quattrocchi

@quattrocchi It’s not «unethical», it is the best technical response to an unmanaged cesspool. Blocking individually is pointless against a server where nazis can just make a new account and keep posting.
in reply to Tor Iver Wilhelmsen

@toriver Most people on the service are regular social media users, but here this mob is demonizing the whole instance as a "cesspool" and executing a totalitarian cleansing of everyone on the service.
in reply to Joseph Quattrocchi

@quattrocchi @toriver

Can you please stop using such ludicrous hyperbolic terms for what is just a server block on a federated network where people can move to different servers?

"executing a totalitarian cleansing"? Can you hear yourself? Are you serious or are you a troll?

Real life actual totalitarianism rises when lies about vulnerable groups are allowed to spread widely. Vulnerable groups get attacked and murdered in real life because of such lies: social.chinwag.org/@FediThing/…

in reply to Fedi.Tips

@toriver A healthier response is deescalation. When you punish whole groups including innocent users for transgressions by a few accounts, there is an escalation.
in reply to Joseph Quattrocchi

@quattrocchi No, they are still there. Freedom of speech is not an entitlement to an audience, other servers see the unmanaged server as a problem and defederates from it, reducing its reach. Their house, their rules.
in reply to Tor Iver Wilhelmsen

@toriver Musk and his allies used that argument to rationalize the abuse of his employees and users. I disagree that anyone has the right to abuse other humans even in their house. Social disenfranchisement—cutting people off from public services—is abuse. Most on this platform did nothing wrong. A few bad interactions can’t justify punishing everyone.
in reply to Joseph Quattrocchi

@quattrocchi A given Mastodon instance is a PRIVATE service, not a public one. Again, if they want to sit in their more and more isolated instance then that is fine, after all both Gab and Truth Social use Mastodon without federating with anyone. The rest of the Mastodon servers are not obliged to federate with them either. It’s not «abuse» in any form.
in reply to Tor Iver Wilhelmsen

@toriver A Mastodon instance is a PUBLIC ACCOMMODATION. There are laws around the world addressing common-carriers or gatekeeping regulation of digital platforms.
in reply to Joseph Quattrocchi

@quattrocchi

No one is stopping anyone using mastodon.cloud.

All that is being suggested is people might want to move off it because it seems to be no longer maintained or moderated.

in reply to Joseph Quattrocchi

@Joseph Quattrocchi @Fedi.Tips

Collective punishment would be if I allowed an unmoderated and unmaintained Instance to propagate to my Instance. I really could not blame my users for being upset if I did not block an Instance that is openly allowing racist material to be propagated by their Instance.

I am not about the Cancel Culture. Though reasonable moderation has to be present on an Instance for me to accept that it should be propagated. If you check my Instances Block List you will realize I do not block Instance arbitrarily.

in reply to Fedi.Tips

their contact email is info@sujitech.com and I’ve already sent them an email notifying them of the defederation risk. I suggest others do the same to get their attention.
in reply to Fedi.Tips

@Fedi.Tips

I do not block Instances lightly, though allowing racists posts cross a line I cannot accept. I have blocked maston.cloud on my Instance for now until I see that the Instance Admin starts moderating again.

Unknown parent

mastodon - Link to source
Fedi.Tips

@AnhedonicHedonist

Yeah, that leads into a weird tale about money:

social.chinwag.org/@FediThing/…

Does make one wonder where the money is coming from and why they seemed to disappear after making a super-large donation.

And even if they couldn't be bothered to moderate, why would they stop updating the software? There are plenty of hosts who will do updates automatically for a small monthly fee.

None of it makes sense.

Unknown parent

mastodon - Link to source
Fedi.Tips

@volcano

Yes! There are simple non-technical step-by-step instructions here:

➡️ fedi.tips/transferring-your-ma…

If you want any help with this please ask 🙂

Unknown parent

mastodon - Link to source
Fedi.Tips

Thanks for the digging. If they are still updating makes it very odd that they stopped there, as the Masto developers specifically warn about no security patches to that branch since April 2025.

(And why are they on such an old branch anyway? And if they're updating why aren't they moderating?)

This entry was edited (3 months ago)
in reply to Fedi.Tips

2.5 years of paying the bills. Many instances have shut down because it was too much of a financial burden and the admins lost interest. Here is an admin committed to building an open society but they have other responsibilities. A constructive solution would be that the community offer a moderator to an instance that is already funded.
This entry was edited (3 months ago)
Unknown parent

mastodon - Link to source
Fedi.Tips

Good god... are you sure? 😬

Pawoo is apparently defederated by many servers for illegal material: tweaking.thebad.space/location…

Is it really being run by the same people as mastodon.cloud? That's horrifying.

This entry was edited (3 months ago)
Unknown parent

mastodon - Link to source
Fedi.Tips

@janggolan

If a server's moderation team is not responding to requests to moderate, and it hasn't posted in over 2 years, and its server software is running on a very out of date version, that implies the server isn't being actively maintained.

If the material to be moderated is extremely serious, and the server admin doesn't respond to multiple reports over several months, then the next step is typically defederation.

There is no other option if the server itself won't respond.

in reply to Fedi.Tips

@janggolan I just shared with you the admin account that posted this month. The instance is up so it is being paid for. There are many options to resolve the other valid issues.
Unknown parent

mastodon - Link to source
Fedi.Tips

@janggolan

"Why can't individual accounts just block each other as they have on other services?"

Here is why, explained in one short post: social.chinwag.org/@FediThing/…

in reply to katherine montalto

It's okay, you can move your account to another server and keep your followers, follows, bookmarks, lists, mutes and blocks. Also, your old posts will redirect people to your new account if you do the transfer process.

There's a step by step non-technical guide here which also advises on how to find a new server: fedi.tips/transferring-your-ma…

Let me know if you want help with any part of the transfer!

This entry was edited (3 months ago)
in reply to Fedi.Tips

I'm going to look into doing this over the weekend maybe when I have some time. I guess it's probably a good time since cloud doesn't update that often. I just never know where to jump to. it feels like instances are always dying or running out of money or getting into fights. I hate the idea of jumping ship all the time
in reply to katherine montalto

@katherine_montalto

That's why I set up fedi.garden to try to highlight the servers that have been around a long time and are well-run. Some of the servers listed have been around since 2017, and all of them have active moderation and promise three months warning if they ever shut down.

Mastodon has a similar official server list at joinmastodon.org/servers which also requires servers to have active moderation and promise three months warning if they ever decide to shut down.

in reply to Fedi.Tips

I get that. and i can't thank you enough for putting together such an amazing resource but I've been on cloud since 2018. it's been bought and sold a couple of times since then. I think when I first got on it, it was based in japan. starting on what seems like a safe instance does not mean it will stay safe. I love the fediverse but sometimes it causes me grief and i just want to express that.
in reply to Fedi.Tips

@janggolan I just realized you were part of the threads.net defederation pile-on too. I actually followed you early in the Twitter migration, but haven’t kept up with all your posts. This block-happy, big-brother, demonizing approach seems infantilizing—which you've shown contempt for. It strips users of their own choices. People will just move on to other services; the only thing it hinders is ActivityPub’s growth. Maybe that’s the point.
in reply to Joseph Quattrocchi

This entry was edited (3 months ago)
in reply to Fedi.Tips

The consequences of failed moderation at Facebook or X are well-documented, yet blocking ActivityPub from high-quality sources only makes other platforms more appealing—consolidating power in centralized platforms. Moderation at scale remains unsolved; neither centralized nor decentralized networks have found a perfect answer.
This entry was edited (3 months ago)
in reply to Fedi.Tips

So, I had to contact the owner of mastodon.cloud with no responsible. They might be in a long hiatus or they quitted moderating it and left it like that

We have suspended it on our end but thanks. Keep up the good work

This entry was edited (2 months ago)