Instance-level blocking (Bluesky ➔ Fedi)

[electricduck]

On fedi, I'm able to block entire instances from interacting with my account. This is handy to stave of potential troll/harmful instances from interacting with you, or just being able to choose to not federate with an instance anymore due to personal concerns (Threads, for example, comes to mind)

On Mastodon, I'm able to do this relatively easily from a profile:

Unless I missed something, there doesn't seem to be anyway to do this from Bluesky. The only way I could see it being handled it via another DM command.

[electricduck]

Potentially related to #1406, since instance-level blocking is achieved by the fact instances themselves have their own fedi accounts (e.g. @[email protected])

[Tamschi]

I'll tag this "compat" since there actually is an equivalent blocking feature in Bluesky that could be used to translate this perfectly.

The bridge would have to expose moderation lists each with every user from a particular instance, and listen for the subscription records for these lists.

---

As an extended version of this feature, these lists could be used to replicate inter-instance moderation actions onto Bluesky (where those are fully public on fedi), though I believe this isn't strictly part of AP.

It's not possible to detect when an individual ActivityPub user blocks a third party instance I believe, though they could still DM Bridgy Fed to block a moderation list once doing so is available. (#1632)

[snarfed]

Good feature request! Afaik instance blocks like this aren't an AP protocol-level feature, they're implemented out of band, internal to each instance.

@Tamschi per-instance moderation lists is an interesting idea! Substantial project, but I suspect any other way to do this would be pretty substantial too.