1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-30 15:22:09 +00:00

Compare commits

..

2 commits

Author SHA1 Message Date
Rohan Kumar
48f1e3873e
Add supplementary blocklists 2023-07-23 15:56:55 -07:00
Rohan Kumar
7001adaaae
Add a webmention rewrite 2023-07-23 15:53:17 -07:00
3 changed files with 24 additions and 6 deletions

View file

@ -5,18 +5,15 @@ I maintain three main blocklists for the Fediverse:
=> https://seirdy.one/pb/pleroma.envs.net.csv The pleroma.envs.net blocklist => https://seirdy.one/pb/pleroma.envs.net.csv The pleroma.envs.net blocklist
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. Unlike the other two lists on this page, it wasn't made for general use (though you're welcome to use it as reference). 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. Unlike the other two lists on this page, it wasn't made for general use (though you're welcome to use it as reference).
=> https://seirdy.one/pb/tier0.csv tier0.csv => https://seirdy.one/pb/tier0.csv tier0.csv
=> https://seirdy.one/pb/tier0-retractions.csv tier0-retractions.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 FediBlockHole users. Note that this list is larger than the bare-minimum I recommend; that'd be FediNuke. 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 FediBlockHole users. Note that this list is larger than the bare-minimum I recommend; that'd be FediNuke.
=> https://seirdy.one/pb/FediNuke.txt FediNuke.txt => https://seirdy.one/pb/FediNuke.txt 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. 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.
This list is not comprehensive; to keep this list small, I excluded many really bad instances. I take into account not just severity, but also notoriety and liklihood of reaching/harming people on other instances (e.g. spewing toxicity in others' mentions, running blockbots, etc). Bad instances that mostly keep to themselves are less likely to cause problems for a new admin, and therefore less likely to get included in this minimal list. This list is not comprehensive; to keep this list small, I excluded many really bad instances. I take into account not just severity, but also notoriety and liklihood of reaching/harming people on other instances (e.g. spewing toxicity in others' mentions, running blockbots, etc). Bad instances that mostly keep to themselves are less likely to cause problems for a new admin, and therefore less likely to get included in this minimal list.
@ -45,8 +42,7 @@ There were some block-overrides for instances with fewer than 11 votes. Here's h
Under ten controversial entries were excluded despite having more than enough votes, after consulting with other admins. Typically, these were instances that didn't pose a major safety risk, but did fail many admins' "vibe check" or exhibit major governance issues. Under ten controversial entries were excluded despite having more than enough votes, after consulting with other admins. Typically, these were instances that didn't pose a major safety risk, but did fail many admins' "vibe check" or exhibit major governance issues.
I also excluded Twitter mirrors such as BirdSiteLive and bird.makeup; I maintain a separate list for those: I also excluded Twitter mirrors such as BirdSiteLive and bird.makeup; I maintain a supplementary list for those, described later.
=> https://seirdy.one/pb/bsl.txt
### Bias sources ### Bias sources
@ -146,6 +142,16 @@ Oliphant has been getting understandable push-back for this issue in his blockli
Since then, Oliphant has removed that admin's list (and his own) from his blocklists' trusted sources. I removed the same ones. Oliphant also stopped generating the unified-max blocklist, as the potential for misuse was too great. Since then, Oliphant has removed that admin's list (and his own) from his blocklists' trusted sources. I removed the same ones. Oliphant also stopped generating the unified-max blocklist, as the potential for misuse was too great.
## Supplementary blocklists
Some supplementary blocklists I maintain with very different criteria:
=> https://seirdy.one/pb/bsl.txt Twitter bridges: BirdSiteLive and bird.makeup
These are services that allow Fediverse users to follow any Twitter user. Now that far-right figures are back on Twitter, these instance pose a problem. Admins wishing to ban a single Twitter user will need to ban that user across over 100 different Twitter mirrors. Moreover, any interactions with bridged accounts are unseen by the account holder on Twitter. Twitter users may not have consented to such mirroring. Admins wishing to simply ban mass-Twitter-mirroring can import this list.
=> https://seirdy.one/pb/corpo.txt Corporate social media with user-hostile dark patterns
A short list containing instances run by social media companies that have displayed user-hostile behavior, for anybody who doesn't wish to support such practices. Privacy abuse, growth-mindsets, dark patterns, and a history of vendor lock-in are common (but not all universal) themes.
## Future ## Future
Once Threads and/or Tumblr start federating, I plan to make a separate blocklist for "mainstream" social media platforms that prioritize profit over safety. I've explained my views on Threads in another post: Once Threads and/or Tumblr start federating, I plan to make a separate blocklist for "mainstream" social media platforms that prioritize profit over safety. I've explained my views on Threads in another post:

View file

@ -50,7 +50,7 @@ There were some block-overrides for instances with fewer than 11 votes. Here's h
Under ten controversial entries were excluded despite having more than enough votes, after consulting with other admins. Typically, these were instances that didn't pose a major safety risk, but did fail many admins' "vibe check" or exhibit major governance issues. Under ten controversial entries were excluded despite having more than enough votes, after consulting with other admins. Typically, these were instances that didn't pose a major safety risk, but did fail many admins' "vibe check" or exhibit major governance issues.
I also excluded Twitter mirrors such as BirdSiteLive and bird.makeup; [I maintain a separate list for those](https://seirdy.one/pb/bsl.txt). I also excluded Twitter mirrors such as BirdSiteLive and bird.makeup; [I maintain a supplementary list for those](#supplementary-blocklists).
### Bias sources ### Bias sources
@ -137,6 +137,17 @@ Oliphant has been getting understandable push-back for this issue in his blockli
Since then, Oliphant has removed that admin's list (and his own) from his blocklists' trusted sources. I removed the same ones. Oliphant also stopped generating the unified-max blocklist, as the potential for misuse was too great. Since then, Oliphant has removed that admin's list (and his own) from his blocklists' trusted sources. I removed the same ones. Oliphant also stopped generating the unified-max blocklist, as the potential for misuse was too great.
## Supplementary blocklists
Some supplementary blocklists I maintain with very different criteria:
[BirdSiteLive and bird.makeup](https://seirdy.one/pb/bsl.txt)
: These are services that allow Fediverse users to follow any Twitter user. Now that far-right figures are back on Twitter, these instance pose a problem. Admins wishing to ban a single Twitter user will need to ban that user across over 100 different Twitter mirrors. Moreover, any interactions with bridged accounts are unseen by the account holder on Twitter. Twitter users may not have consented to such mirroring. Admins wishing to simply ban mass-Twitter-mirroring can import this list.
[Corporate social media with user-hostile dark patterns](https://seirdy.one/pb/corpo.txt)
: A short list containing instances run by social media companies that have displayed user-hostile behavior, for anybody who doesn't wish to support such practices. Privacy abuse, growth-mindsets, dark patterns, and a history of vendor lock-in are common (but not all universal) themes.
## Future ## Future
Once Threads and/or Tumblr start federating, I plan to make a separate blocklist for "mainstream" social media platforms that prioritize profit over safety. I've explained my views on Threads in another post: {{<mention-work itemtype="BlogPosting">}}{{<cited-work name="De-federating P92" url="../../../../2023/06/20/defederating-p92/" extraName="headline">}}{{</mention-work>}}. Once Threads and/or Tumblr start federating, I plan to make a separate blocklist for "mainstream" social media platforms that prioritize profit over safety. I've explained my views on Threads in another post: {{<mention-work itemtype="BlogPosting">}}{{<cited-work name="De-federating P92" url="../../../../2023/06/20/defederating-p92/" extraName="headline">}}{{</mention-work>}}.

View file

@ -7,3 +7,4 @@ https://brid.gy/post/mastodon/@Seirdy@pleroma.envs.net/AGJrYW1wzYsoVK74oi,https:
https://blog.puer-robustus.eu/domestizierung-von-nutzern/,https://blog.puer-robustus.eu/post/domestizierung-von-nutzern/ https://blog.puer-robustus.eu/domestizierung-von-nutzern/,https://blog.puer-robustus.eu/post/domestizierung-von-nutzern/
https://revi.blog/P167,https://web.archive.org/web/20221125005852/https://revi.blog/P167 https://revi.blog/P167,https://web.archive.org/web/20221125005852/https://revi.blog/P167
https://blog.lyokolux.space/21-01-15-whatsapp-en-2021-bye-bye.html,https://blog.lyokolux.space/posts/21-01-15-whatsapp-en-2021-bye-bye/ https://blog.lyokolux.space/21-01-15-whatsapp-en-2021-bye-bye.html,https://blog.lyokolux.space/posts/21-01-15-whatsapp-en-2021-bye-bye/
https://privacyguides.org/linux-desktop/,https://www.privacyguides.org/en/os/linux-overview/

1 https://www.tinybrain.fans/accessibility.html https://tinybrain.fans/accessibility.html
7 https://blog.puer-robustus.eu/domestizierung-von-nutzern/ https://blog.puer-robustus.eu/post/domestizierung-von-nutzern/
8 https://revi.blog/P167 https://web.archive.org/web/20221125005852/https://revi.blog/P167
9 https://blog.lyokolux.space/21-01-15-whatsapp-en-2021-bye-bye.html https://blog.lyokolux.space/posts/21-01-15-whatsapp-en-2021-bye-bye/
10 https://privacyguides.org/linux-desktop/ https://www.privacyguides.org/en/os/linux-overview/