Anyone got an API endpoint of the "most blocked instances" handy? I wanna add it to the initialization flow for the #DistributedPress #SocialInbox
Ideally it'd be nice to say "Here's the top 100 most hated instances so you can preemptively block them if you'd like". It's not perfect but I think this would make it easier for small publishers to get started.
Huge thanks for folks/ input on this. We're going to start with the mastodon blocklist format version of gardenfence and go from there.
We'll have a flag for folks to toggle during setup for pulling from a URL and have it set to this one by default:
https://github.com/gardenfence/blocklist/blob/main/gardenfence-mastodon.csv
To be clear though, this will just be on the SocialInbox server to preemtively filter out replies and follow requests from such instances.
Sadly we need a whole new approach to figure out how to prevent instances like this from reading your posts since all your data is available via ActivityPub and HTML on the #dweb. 😅
@mauve you can't prevent read unless content isn't publicly available
@thisismissem Yeah! Exactly. At the very least the inbox level block will help reduce how much your posts get pushed to those instances and their global timelines.
