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. 😅

@j3j5 Yeah defs a fan of this project and into integrating at some point. For the moment I'd like to reduce the overall size of the blocklist and focus on something with a bit less nuance like "the top most blocked instances" since it's easier to grock without nuance IMO.

Ideally instance operators would then add / remove more allowed/blocked instances from there.

@mauve @j3j5 Fedinuke or Oliphant tier 0? (Although the oliphant list is questionable now given recent events..)

@mauve In case you missed it, this seems like an interesting update that may better fit your goals for using #TheBadSpace

https://ubiqueros.com/notes/9jacmunvir

@j3j5 very much so 🥰 We'll be doing some more work on our moderation system in thr next quarter so it'll be useful to see where we can align

@mauve right, while I agree it would be useful, this kind of thing doesn't exist for a few reasons. one, as you found, bad instances like to track who have blocked them, either as a kind of high score or for retaliation. two, collecting such statistics would require instances to disclose their block lists in a machine-readable format, which plenty do not do and are not willing to do.

@thisismissem Yeah good point. Any benefits to mastodon's format instead of the fediblocksync format? I assume the mastodon one is more widely deployed at this point?

@mauve yeah, that and most blocklists I know are deployed in that format; though there is a bunch of interest in moving towards a standard format, not purely adopting Mastodon as standard.

@mauve like, fediblocksync but with the ability to obscure the really harmful URLs would be wise, but it's kinda a future piece of work

@thisismissem Dang yeah having all these domains in a list seems like a great way for folks seeking out communities like that to find each other 🥶 Ah well, we'll adopt whatever new thing comes along once we get to it!

@thisismissem @mauve Would hashing the URLs of instances, publishing the hashes, and then when a server wants to federate hashing its name, checking it against the list, and blocking accordingly be a solution here? Similar strategy to how haveIbeenpwned handles things I think...

@hank Yup! I think as @thisismissem alluded to the only challenge is getting folks to actually adopt such a strategy. :P

@hank @mauve I don't think that'd work in this scenario.

@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.