Even-handed commentary and opinions on issues folks view as heated topics is not reportable, especially if it’s already behind a CW.
Also, as an aside, if you use “Other”, please include an explanation… If that’s not possible on your software, fair enough — we should push to make the ability to add additional info standard across Fedi with reports.
A reminder: Instance suspensions are, inherently, permanent.
It’s like going into a server room and taking the nuclear option of severing cables instead of unplugging and rewiring them.
Can you eventually reconnect them? Sort of. But, now you have to renegotiate DHCP leases, make sure your routes are set up correctly, find out why it’s connected but no one has internet access…
tl;dr and analogy aside: Mastodon severs followers on permanently when you suspend a server. It’s not an undo-able action, it’s a permanent action, and many users have no idea how it works or how to save that data before it’s gone forever.
Excuse the crude markup, but here’s a snippet of the work we’re doing on the Pawb.Social hardware!
We’ve got the main node hosting all of the various services for Pawb.Social (the multiple Mastodon instances, Lemmy, databases, etc.), and a new node we’re still provisioning for HA use.
Further down we’ve got the NAS (currently backups and Lemmy), two Dell TL4000 tape drives (for backups), and an APC SM3000RM2U backup UPS.
Both of the main nodes are running Proxmox v8 as the host OS (Debian bookworm) and are nearly identical in specs and hardware.
It's a big list of censures (suspensions), hesitations (limits), and endorsements, and it's a good reference in case you need to check the background of a given instance before taking actions.