⚠️ 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
p.s. If you want an easy way to discover reliable good servers, there are human-curated server lists at https://fedi.garden and https://joinmastodon.org/servers
All the servers listed on these sites have to comply with certain standards of technical reliability and moderation.
p.p.s. If you want help with moving there's a guide at https://fedi.tips/transferring-your-mastodon-account-to-another-server
ugh
I just moved there with my non-fiction accounts
This is so tiresome
Oh no, really sorry to hear 😞
Hopefully the human-curated server lists can help reduce this kind of situation happening to people.
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.
Just report them to Amazon, does that work?
https://www.whois.com/whois/pawoo.net
nasd1066
Fedi.Tips
Humphrey Archer
Ari Sovijärvi
PlutarchName 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
@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.
@FediTips the same admin was responsible for mstdn.jp and pawoo.net, both of them also abandoned and running with outdated and unsupported versions.
(It's what I infer from https://mstdn.jp/@Sujiyan/109564291832002068)
Recording of Interview of maintainer of Pawoo/Mstdn.jp/Mastodon.cloud :D by @[email protected] @[email protected] and joined by ~12 audiences like @[email protected] etc *83 mins Link: https://mega.nz/folder/DvpnwYBK#2VtqBLiZH9WMICcPdTb0MA
@cadusilva @FediTips TIL those are all the same admin... and also this:
@FediTips Hm.. I believe they are part of some other instance, maybe pawoo?
I remember a company being behind .cloud and another big instance
@FediTips
I see many legitimate accounts there. I've decided to limit the server, but not block it. This way people can continue following each other, but hear-me.social is protected.
If anyone here does have a follow relationship with anyone on .cloud, please let them know the ship has no captain and it's vulnerable to attacks, and they should jump onto a new one.
If the owner has no interest in having anything to do with the site, why do they keep it going? Why don't they seek a new owner? They should at least let people on their instance know.
Alison Meeks
Wendroid 🇺🇦
Wilm
C_Chell
Cadu 
Hoshino Lina (星乃リナ) 🩵 3D Yuri Wedding 2026!!!
stux⚡️
Mastodon Belgium Admin
Mark Wyner Won’t Comply 
Skwerlgyrl
Sam Nabi
Jigme Datse
🥑 Yours Truly! Unruly 🇨🇦🇪🇺🇺🇦🌻
schuh
gunstick
Jerry on Mastodon
Codewizard