mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-27 14:12:09 +00:00
Correction about retractions
This commit is contained in:
parent
b61d84cf5d
commit
4d55894d73
2 changed files with 5 additions and 2 deletions
|
@ -12,7 +12,7 @@ A large list of instances that I find worth suspending. After the first couple h
|
|||
=> https://seirdy.one/pb/tier0.csv tier0.csv
|
||||
=> https://seirdy.one/pb/tier0-retractions.csv tier0-retractions.csv
|
||||
|
||||
A much smaller semi-curated subset of pleroma.envs.net suitable for the majority of instances wishing to uphold the Mastodon Covenant's moderation standards. I hope to make it a good starting point for your instance's blocklist, with wiggle room for your own adjustments. Regularly importing tier0.csv won't account for retractions; a sibling blocklist for tier-0 retractions exists for that purpose. Importing the retractions blocklist will remove its entries from your instance's blocklist.
|
||||
A much smaller semi-curated subset of pleroma.envs.net suitable for the majority of instances wishing to uphold the Mastodon Covenant's moderation standards. I hope to make it a good starting point for your instance's blocklist, with wiggle room for your own adjustments. Regularly importing tier0.csv won't account for retractions; a sibling blocklist for tier-0 retractions exists for that purpose. Importing the retractions blocklist currently does nothing, unfortunately; right now, it's a manual process.
|
||||
|
||||
|
||||
=> https://seirdy.one/pb/FediNuke.txt FediNuke.txt
|
||||
|
@ -128,5 +128,7 @@ It doesn't have a lot of content yet, but that will change with time. I've share
|
|||
|
||||
I like the idea of a separation between receipt-tracking projects and blocklist-generating projects. Reasons in a blocklist tend to invite retaliatory harassment in an effort to make admins hide their blocklists, often in the form of (very dubious) legal threats (defamation and privacy regulations have come up).
|
||||
|
||||
My greatest priority right now is solving retractions. Getting off of a list needs to be made much easier.
|
||||
|
||||
[note 1]: I did not consider dox attempts against certain neo-Nazis a reason to block.
|
||||
|
||||
|
|
|
@ -18,7 +18,7 @@ I maintain three blocklists for the Fediverse:
|
|||
: A large list of instances that I find worth suspending. After the first couple hundred entries (imported and then reviewed), I started collecting receipts. Since early 2023, every entry has documented reasons and receipts. I share these with multiple people in a collaborative document, but I don't share it publicly due to risk of harassment.
|
||||
|
||||
[`tier0.csv`](https://seirdy.one/pb/tier0.csv)
|
||||
: A much smaller semi-curated subset of `pleroma.envs.net` suitable for the majority of instances wishing to uphold the Mastodon Covenant's moderation standards. I hope to make it a good starting point for your instance's blocklist, with wiggle room for your own adjustments. Regularly importing `tier0.csv` won't account for retractions; [a sibling blocklist for tier-0 retractions](https://seirdy.one/pb/tier0-retractions.csv) exists for that purpose. Importing the retractions blocklist will remove its entries from your instance's blocklist.
|
||||
: A much smaller semi-curated subset of `pleroma.envs.net` suitable for the majority of instances wishing to uphold the Mastodon Covenant's moderation standards. I hope to make it a good starting point for your instance's blocklist, with wiggle room for your own adjustments. Regularly importing `tier0.csv` won't account for retractions; [a sibling blocklist for tier-0 retractions](https://seirdy.one/pb/tier0-retractions.csv) exists for that purpose. Importing the retractions blocklist currently does nothing, unfortunately; right now, it's a manual process.
|
||||
|
||||
[`FediNuke.txt`](https://seirdy.one/pb/FediNuke.txt)
|
||||
: A curated subset of `tier0.csv`, containing what I deem the "worse half" of it. This contains instances I really do recommend most people block, or at least avoid. I try to make it a suitable candidate for a "default blocklist", and use it as reference when I evaluate the quality of other blocklists.
|
||||
|
@ -119,6 +119,7 @@ The biggest complaint I've heard is the lack of reasons and receipts. {{<mention
|
|||
|
||||
I like the idea of a separation between receipt-tracking projects and blocklist-generating projects. Reasons in a blocklist tend to invite retaliatory harassment in an effort to make admins hide their blocklists, often in the form of (very dubious) legal threats (defamation and privacy regulations have come up).
|
||||
|
||||
My greatest priority right now is solving retractions. Getting off of a list needs to be made much easier.
|
||||
|
||||
[^1]: I did not consider dox attempts against certain neo-Nazis a reason to block.
|
||||
|
||||
|
|
Loading…
Reference in a new issue