⚠️ Do not move your account to mastodon.cloud. If you know someone already on mastodon.cloud you might want to suggest they move to a different server.

-Mastodon.cloud's admin hasn't posted since Feb 2023
-There doesn't seem to be any moderation, really awful bigotry is still there months after being reported
-The server software is very outdated and full of unpatched security holes
-Because of all the above, many other servers have defederated mastodon.cloud

#MastodonCloud #FediBlock

@FediTips I'm genuinely surprised that it can still still survive in this zombie state. A lot of Wordpress and similar sites have pretty quickly attracted from the hosting or co-location company's interest after enough reports have been filed against it for objectionable concept or it just being a trojan payload sharing site.

@apz

I wonder if anyone has reported it to the providers higher up the chain? 🤔

There have been reports via Mastodon's own moderation tools but these have AFAIK all been ignored.

@FediTips I don't know, but generally when something web based gets pwned hard enough, sysadmins typically start to raise stink about it. If I spot port scanners or obvious stuff being run against the systems I maintain, I might fire an e-mail to their ISP's abuse address, depending on where they from. With China, Russia etc. I don't bother, US and Europe likely, the Nordics, very likely.
@apz @FediTips lmfao should take a look at catdon.life. It a couple years ago upgraded from v2.5.2 to what version it's currently on v2.7.0.. a release from Jan 2019. Hosts really don't seem to care seems like lol

@apz @FediTips

Just report them to Amazon, does that work?

https://www.whois.com/whois/pawoo.net

Name Servers: ns-115.awsdns-14.com ns-1162.awsdns-17.org ns-1584.awsdns-06.co.uk ns-862.awsdns-43.net

EDIT; oh, and Cloudflare, for mastodon.cloud, actually: https://www.whois.com/whois/mastodon.cloud

Name Servers: cruz.ns.cloudflare.com jake.ns.cloudflare.com
Whois pawoo.net

Whois Lookup for pawoo.net

@plutarch @FediTips Amazon doesn't give a fuck. I reported a huge botnet, got a reply that they could not verify the claim. I went through an internal contact I had to to escalate it. I heard that they basically had laughed at it on their internal chat, with the mentality being that I was some home hosting n00b who got scared when someone scanned them and that I shouldn't expose services unless I wanted them knocked all the time.

Just to bring some context, I set up my first public net connected services when these guys weren't not born yet and only reported it as a courtesy and only because it was relatively big botnet.