@darius love it.

@darius Basically a "blocked by default" policy. The instance is blocked by default unless one of our users want tk explicitly follow someone. Makes sense to me.

@darius Really interesting idea. Can I link to that from the thread modeling post? I've already got a paragraph on looking for alternatives between allowlist and blocklist, so it'd fit right in

@darius I'm on another social network that by default does something like this (your allow list is your follow list plus the follow lists of everyone you're following). Works really well.

@darius hope to see this trail of thought continue into real experimentation!

It feels like there would be a whole lot more common ground between the preemptive defederators and the wait-and-see crowd if dubious instances could be quarantined away whilst still having the option to poke holes for individually trusted users.

We also need more documentation on the connectivity options available to instance admins:
https://writing.exchange/@erlend/110671771287690551

@darius This would be an absolute dream!

@darius really love the idea of breaking out of this binary thinking, and there are some great replies that make me have some hope that this may be the third path that has the right balance. some sort of Threads "condom" that protects community interests in the fediverse but still allows *some* flow of intentional information between the servers

@darius I really like this idea!