diff --git a/content/posts/fediverse-blocklists.gmi b/content/posts/fediverse-blocklists.gmi index 0d947e6..c9db14a 100644 --- a/content/posts/fediverse-blocklists.gmi +++ b/content/posts/fediverse-blocklists.gmi @@ -62,6 +62,10 @@ If tier0.csv were merely an unbiased list of the most widely blocked instances, Some instances migrate their domains. If the old instance was already deemed worthy of a suspension and the new instance maintains the same staff with no visible attempt to change its reputation, then I deem the new location to be as block-worthy as the old location and make an override. It's the same bad actors under a different banner. +### Retractions + +A separate list exists for retractions from my tier0.csv list. I don't add entries to my retractions list when I remove dead instances, or when an admin on a removed instance prefers not to be included in it (some wish to remain less prominent). + ## Intended use The original goal was to make a blocklist appealing to instances with a more laid-back moderation approach, so that they would actually implement a decent blocklist and limit the reach of the worst actors. Unfortunately, the final tier0.csv blocklist is 350+ entries; this is still a bit much for the moderate instances. diff --git a/content/posts/fediverse-blocklists.md b/content/posts/fediverse-blocklists.md index e73cd10..091adbc 100644 --- a/content/posts/fediverse-blocklists.md +++ b/content/posts/fediverse-blocklists.md @@ -70,6 +70,10 @@ If `tier0.csv` were merely an unbiased list of the most widely blocked instances Some instances migrate their domains. If the old instance was already deemed worthy of a suspension and the new instance maintains the same staff with no visible attempt to change its reputation, then I deem the new location to be as block-worthy as the old location and make an override. It's the same bad actors under a different banner. +### Retractions + +A separate list exists for retractions from my tier0.csv list. I don't add entries to my retractions list when I remove dead instances, or when an admin on a removed instance prefers not to be included in it (some wish to remain less prominent). + ## Intended use The original goal was to make a blocklist appealing to instances with a more laid-back moderation approach, so that they would actually implement a decent blocklist and limit the reach of the worst actors. Unfortunately, the final `tier0.csv` blocklist is 350+ entries; this is still a bit much for the moderate instances.