Hi Michael and everyone. I wrote up some general notes for thinking about this…

#The need for community-level moderation:

I think most Mastodon users get by fine with the standard individual-level options – you follow people you find interesting and block people who act obnoxious when you encounter them. There’s no algorithm pushing obnoxious content onto your ‘home’ feed, nor is it easy for harassers to discover your posts. The first level of discovery is the ‘local timeline’ – this is the main place where members of TheATL.social interact with each other, and why the top priority is to have good moderation of content posted on TheATL.social itself. We already has a clear set of policies for members of the community.

These same moderation policies can be applied to members of other communities – blocking those who violate our rules from interacting with members of our community. However, this strategy has some limitations – first, it effectively asks our moderators to moderate the entire Fediverse, which is an impossible task, especially when harassers may have multiple accounts. It also leaves our users exposed to coordinated harassment campaigns across communities – as long as the harassers are allowed to keep their accounts, they can swarm one target after another and systematically drive anyone they dislike off Mastodon.

Finally, I think we also need to consider indirect interactions, such as slander. It’s not enough for a user to be shielded from abusive messages if the abuser continues to spread rumors among the user’s acquaintances. For this reason, I’d be inclined to simply cut off any community that allows an abuser to participate… though of course, we don’t have the resources to litigate slander accusations.

#What are the options for community-level moderation?

The Mastodon software provides three options for Moderating entire websites. ‘Suspend’ (aka defederation/block) is a complete block; ‘limiting’ (aka silencing) will only prevent content from showing on the federated timeline (If I understand it correctly); ‘reject media’ will avoid copying/showing any images.

TheATL.social currently blocks 5 servers (1 is a subdomain) (see ‘Moderated Servers’). My understanding is that this is a pretty light touch in terms of typical Mastodon moderation. Other community administrators have created long lists of communities that they consider problematic, and others have compiled these into composite blocklists such as Oliphant. Communities can be placed on these lists for a wide range of reasons, so there’s some risk of going along with over-zealous blocking.

Note also that individual users can import these blocklists – so they can hide themselves from these communities, but doing it alone means that a user may be cut out of conversations that their other friends/contacts/acquaintances are participating in.

I skimmed over the Oliphant unified tier 0 blocklist, and it does not block any instances that I interact with, for what that’s worth. I am a bit concerned with the idea of routinely updating the block list based on the Oliphant algorithm. I suspect that the Oliphant project has a tendency to attract administrators who most enthusiastic about blocking. The justifications that I see for blocking would often apply to a lot of mainstream/establishment opinion in the USA (and probably more so in GA).

That said, I’m fully in favor of blocking obnoxious sites simply for the purpose of maintaining a pleasant and productive environment. For instance, brighton.social is on the tier0 list – this is basically a conspiracy theory propaganda mill; the local feed screams paranoia. I’d support blocking brighton.social purely to protect theATL users from wandering into a conversation prompted by their nonsense. I consider this to be the same as public parks having a policy that people need to clean up after their dogs. I consider it very unpleasant to be at the receiving end of a propaganda firehose, even if the propaganda is not personally threatening. (I don’t know if this captures the entire story for why they are on the blocklist – there could be other problems with them)

I did notice two sizable instances that are often considered “borderline problematic” in the defederation debates – and both were set to “silence” rather than “suspend”. One, is newsie.social (where Decaturish is located). I vaguely remember some criticisms about newsie.social a few months back – I think part of it was that people were reposting or repeating opinions that published in the Washington Post or New York Times. Many of the critics wanted nothing to do with journalists. As we’ve seen with the BBC instance, there are a decent number of people in the fediverse who would block those mainstream publishers, either because they have different standards from mainstream society or because they simply don’t want that experience on their Mastodon instance. I wouldn’t necessarily take their ‘block’ as meaning that the instance is anything we’d consider horrible.

The other ‘borderline’ instance I saw silenced was “QOTO” – this instance is controversial because its policy is to only defederate when absolutely necessary (e.g. spam overwhelms the server). Many other instances block QOTO either because they view this as aiding hate-mongers, or because they just want to keep the hate-monges a couple steps removed from them. (Disclaimer, my account was hosted on Qoto before I came here)

So I guess I don’t have a clear opinion here. I think even tier0 may be a bit too stringent, but i can’t suggest a better way to quickly distinguish between those that are exceptionally horrible and those that are everyday horrible. Perhaps just silence them, and treat that as a strike, so that if we have any problems with harassment we quickly block the whole server. I suspect that some need to be blocked outright – if you look at Qoto’s blocklist, that could give you a small number that are absolutely intolerable.

To correct my initial post, @DecaturNature is correct. There are ~5 domains currently blocked, not 2. And, I’m in agreement thus far that a “light” approach to blocked domains is no longer appropriate. I’m looking forward to thoughts and feedback on this thread to inform the next steps on policy related to future domain blocks! Thank you for your time contributing to this discussion.

Thank you all for your comments. I will be responding to each point in the next day or so. However, I do see from the comments that there is an immediate need to implement the Tier 0 Oliphant block list, which has now occured.

Information on this block is available here: https://yall.theatl.social/post/55833

Note that there were some domains for which theATL.social users currently engage. I am giving a 2-week grace period for anyone who wants to keep those domains, otherwise the remaining domains will be blocked after that point.

Thank you all for your comments and contributions to making this instance a good place to be.

I think it’s entirely appropriate to block hate speech and clearly illegal content (CP etc). That stuff has no place in any of our feeds. If there’s a block list that can make that easy I say use it. Obviously be transparent and possibly revisit this discussion periodically but I’m all for it.

I think the tier 0 list is a good start. Most of the servers on it that I’ve encountered on it tolerate or were actively stood up to promote the vile behaviorof their users and they don’t make any community they interact with better. At best they simply take up oxygen, at worst they drive people out of the fediverse.

I would agree completely with utilizing the Tier 0 block list at the minimum. If things got bad, and users were being harassed, then going further would be justifiable to me. I prioritize safe communities over free speech, if a trade-off has to be made.

Funny thing is that threads.net is already ‘suspended’ on the Tier 1 list (but not the Tier 0 list).

Later on, it may be worthwhile to consider using these bigger lists for silencing – it may help improve the quality of the content on the “federated timeline”. For instance, if you look at the tier 3 list it excludes a lot of politics-focused instances (both left and right). Not that politics on Mastodon is a problem, but it may be more enjoyable for most people with more substantial discussions if the loudest political accounts are turned down a notch.

Anyway, that would be a question for the people who actually use the federated timeline (not me)

Likewise, I am not a free speech absolutist- limits should be in place to censor the most repugnant content. Using the Tier-0 list for instance-level blocking is a good approach: light touch, using globally accepted standards.

For the rest, if a user doesn’t want to see content from a user or domain, they can block either/both at their level. As a user, I should be permitted to follow who I choose, consume text/media I wish to see, and block content that which offends me. I don’t need an admin making those decisions for me. An overzealous admin (or instance leadership) blocking domains at the instance level that /they/ find distasteful is far too arbitrary.

However, the admin must balance risk- they own the underlying infrastructure and could be accountable for the content transacted and stored- from both a legal standpoint and with respect to the broader community. Consider a situation where a user is acting against de facto global content standards and the admin does nothing- all users of the instance are at risk of global defederation.

I feel the guidelines established to moderate theatl.social are broad enough to foster open dialog, but also protect the instance from broad defederation. Adding a Tier-0 block is a sensible addition.

Food for thought @michael@yall.theatl.social

I found this comment on blocklist systems to be interesting: https://social.treehouse.systems/@adrienne/111043288202527510

How do we unblock any instance that got on Oliphant tier 0 but are later removed? Is that something that will be checked for?

Another thought – how does blocking and silencing affect the new search system? I guess blocking is obvious…but does silence block search? If so, I think that makes silencing much more impactful and we’d need to be more careful with it.

Hey Y’all!

I wanted to circle back on this discussion thread. Things got a bit busy with the instance upgrade (which is now upgraded to 4.1.6).

• With regards to Tier 0 Oliphant, I had initially thought that the list was primarily bottom-of-the-barrel sort of sites, but on closer look, there were sites included that well, people on the instance utilize - such as newsie.social. I thought that our discussion on our Lemmy server, plus DMs and feedback from the Mastodon side figured out which sites we wanted to exclude from the domain block list. All that being said, my objective with the blocks was to remove the known sources of abusive, illegal, or malicious (e.g., spam, malware) content.
• And then that leaves us in the gray zone. There are instances where 98% of the users are great Fediverse citizens, and then 2% are horrible trolls. There are instances where teams of moderators are carefully watching posts, and others were moderators only step in during extreme situations. And there are instances that are for-profit, non-profit, from different countries and contexts, and so on. I don’t have any straightforward answer as to where the line is located in this grey area, with regards to if a domain should be defederated or not.
• @DecaturNature had a great point regarding what if theATL.social becomes either a target or source of disinformation. A group of users (real or actual) could create accounts on the instance in a coordinated fashion, and turn over the apple cart of our existing community posting disinformation and slander. It would seem the line would be clear that those individuals would not be welcome, but if someone is being a jerk or insincere, is that enough justification to ban them?

Final Thoughts

I’m going to chew through the above points. Obviously other err…large social networks have figured something out. And smaller Mastodon servers have done the same. It is quite likely that the current server rules are not satisfactory to cover all the potential issues, situations, and possibilities of human (or bot) behavior of theATL.social users, or content that is federated to theATL.social. If you have any additional thoughts, please feel free to include below. I don’t have a timeline on changes for server rules, but when there are changes (if you wanted to propose changes), I would prefer if that was a collaborative exercise with the core group of users on this instance.

Thanks again for all your comments and feedback!