Back

@snarfed.org @activitypubblueskybridge @fedidevs @fediversenews Letting people opt-out IS NOT consent.

@byjp @zatnosk @activitypubblueskybridge @fedidevs @fediversenews I think the main difference is that, like Nostr, Bluesky is just one big monolith with known problematic users (that have to be "filtered" out), so it's hard to moderate effectively. It's the same as any other large Mastodon instance, like dot Social or Gab.

@blake @zatnosk @activitypubblueskybridge @fedidevs @fediversenews Ahh yeah, I guess some users/servers might want/need to block the whole of brid.gy to avoid the risk of specific users on a given bridged platform being able to follow them. That’s not so different to today’s fediverse (lots of people/servers block Threads), but it sucks to lose the other functionality of brid.gy.

@blake @zatnosk @activitypubblueskybridge @fedidevs @fediversenews (Unless you can block specific bridges platforms individually @snarfed.org ? This still seems within the limits of current Fediverse architecture to me, but it’d be a shame if we can’t allow people to select platforms by server, just like with the Fediverse!)

@byjp @zatnosk @activitypubblueskybridge @fedidevs @fediversenews @snarfed@hachyderm.io If you want to block just Bridgy's Bluesky bridge, or just their (upcoming) Nostr bridge, or whatever, you can do that. If you want to block specific PDS's, I don't think there's a way to do that.

@eishiya Yeah, that makes sense—I don’t expect my posts on StackOverflow to end up on some other random site (and it’s frustrating when they do!)
Is Threads much different though? They integrate using ActivityPub in the same way. I block that “server”, and Meta doesn’t (legally) get my data.
With both Threads & Bridgy you’re notified when you’re followed by someone from there, so there’s visibility, but bridgy needs exact username too. This feels okay to me, but I get it feels odd!

@byjp Threads would be using AP natively rather than through a third-party bridge so unfortunately having one's posts there is part of that "native Fediverse" expectation, right alongside all the alt-right servers that one may also prefer to block. And unlike this bridge, Threads is more widely known, so people are more likely to be able to block it in a timely manner, or immediately upon discovering posts from it. No hashtags or contacting the admin required xP

@SuperMoosie @byjp @zatnosk

Considering each instance can have its own terms of service, this is a legal space that is largely untested currently. My thoughts are that the legality will boil down to "follow each instance terms", but it's an amazingly complex thing even there. And I say this even as an instance owner who thinks that bridgy should be explicitly opt-in either per-post, per-user, or per-instance.

Per-instance, to me, kind of makes the MOST sense for having an 'opt-out' tag in the bio -- each instance owner is then making their own users aware of the policy and can give them advance notice if they don't wish to be included. Just having a global "we can have your information even if you're unaware of it" policy is half the problem of the current tech industry snarfing up damn everything as if it's theirs to use, causing all the LLM garbage issues today.

Hell, the fact I'd have to end my wifi SSID in _at least_ two weird tag things, and one of them MUST be the last one, to avoid my wifi SSID, BSSID, and location getting snarfed by mapping cars (google, MS, etc) is just part of this. I have to take up limited characters in my bio for each service I want no part in? I have to make my SSID ugly just so a corp won't use info I didn't consent to them using? While I like the idea of being able to follow friends of mine who are on AT instead of fedi, and refuse to use fedi, it's not worth it being so open; I always figured there would be an opt-in mechanism, not yet more opt-out stuff.

C'mon like, haven't we seen how many times people offering only opt-out are shown the distaste for this? =/ 'bridge' or not, it's still technically a specialized service, it's not transparent just because things are duplicated both ways.