I have so far seen no compelling arguments for why a bridge is fundamentally different from any other instance, and instance federation is opt-out by design.
If an instance is too big, block it. If it’s too unmoderated, block it. If you don’t approve of its implementation, block it. If you don’t like it, block it.
It’s pretty core to how the Fediverse works.
No one opted-in to interact with abyssdomain.expert.
The recent chatter about #microformats turning 20 reminded me I’d re-found this book by @johnallsopp when I was clearing out the loft a few years ago.
I kept putting microformats into my markup for years, even though I was convinced no one was using them any more. Then I discovered people had moved on to v2 in #indieweb circles and I had some catching up to do 😂
In short, who are you yelling at? Who do you expect to "fix" things for you? Right now people are coming down on the guy who is building the bridge to bluesky. That specific guy. They're yelling at him and telling him to make different decisions to protect their personal privacy. Is that what people think they signed up for with the fediverse? Fighting with other individual humans and trying to force them to do what you want?
If you’ve been following the Bridgy and Mastodon drama, consider that many Mastodon users don’t want a bridge that allows Bluesky to federate with Mastodon, but they do want Bluesky to support ActivityPub so Bluesky can… also federate with Mastodon. 😜
