Recent searches
Search options
As a server admin, what are the things you would like to know before applying a domain block (and/or a #blocklist), or what kinds of steps would you like to perform?
Some of my thoughts:
1. How many people would be impacted on our server and theirs?
2. How _significant_ the impact would be for those impacted?
3. Is the domain actually alive still?
What else?
@hrefna Should the block be permanent?
@hrefna
I don't run Mastodon but have run other online communities on IRC and Discord.
* Reports filed by people on my server.
* The reason for the proposed block, if it isn't one I decided on myself.
* What response the admins of that instance have given when told about said reason (they have been told, right?)
For impact btw I'd want more than just follow relationships. Posts loaded in replies also matters quite a bit for smooth conversations here, if that's not a lost cause anyway.
@hrefna
For me there is only one question: Does it protect my users or do I patronize them with it. My goal is to give the user back the freedom to decide what he wants to see and what not.
Protect means the entire instance is designed to violate our rules.
@hrefna@hachyderm.io Imho if you have to take things into account like "how many people are impacted" it's probably a sign that the block isn't 100% reasonable or justified. A block is either a 1 or a 0. Does it protect my users/instance or not.
@hrefna You must also consider one of the inverse questions: what is the cumulative harm to people on your server while the server remains unblocked—right now and going forward until a block decision is permanently implemented or not.
This is why, in the legal realm, we have temporary injunctions.
The small harm in a proactive, temporary block may be necessary to ensure safety until a permanent decision is made. It is reversible and be weighed against the cost of inaction.
@hrefna blocking a domain is a nuclear option IMHO.
Mostly applicable when the sole purpose of the instance and its administrators is to harass people, spread spam and nonsense and harbour criminal activities.
In any other case, even if the admins are not very responsive to requests of moderation of some of their users, we can still get away by just blocking some individual accounts.
Actually, I think it is more related to how much work is going to take from us as admins to deal with their users than any other thing. 
西风 
- Does the admin tolerate harassment?
- Does the admin voice support for discrimination?
- Does the admin execute their power in favour of an abuser (e.g. punishes anti-discriminatory users, but fine with discriminators)?
If any one of these applies, it's ground for a domain block.
@hrefna those first two are really important. In general, feeling the pulse of the community concerning the block would be what makes the difference between an admin that does things "by themselves” and those that really act as stewards for their community.