Elektrine lite

← Feed

@greg@flipboard.social

Post #3154325

2026-05-22 19:07 UTC

@welshpixie@mastodon.art @mike@flipboard.social Good question! Surf works differently from instance-to-instance federation — it's a multi-network client that connects to Mastodon, Bluesky, and other networks independently. So your instance-level blocks of Threads and the Bluesky bridge are fully respected within Mastodon's own federation, but Surf surfaces content from those networks on its own, outside of that federation layer. There is a Mastodon API (/api/v1/instance/domain_blocks) that can expose an instance's blocklist, but only if the admin has chosen to make it public — many instances don't. And even where it is available, it raises a broader question for us: Surf's purpose is to bring multiple networks together in one place, so honoring instance-level federation blocks in a non-federation context is something we'd need to think carefully about. It's actually a topic that has popped up quite a bit lately that I don't have a reliable solution for that doesn't raise even more questions.

Replies (1)

  • @welshpixie@mastodon.art 2026-05-22 19:19

    @greg@flipboard.social @mike@flipboard.social ok - so speaking for everyone on mastodon.art (I'm the owner), and everyone on similarly aligned instances to ours (I know this from experience of seeing this kinda thing repeatedly in my years of being on fedi), anything that takes someone's posts, even if they're public posts, and posts them outside of the platform they were originally posted on, needs to be done opt-in with consent given at the start. 1/2

    Open ##3154326