Eugen RochkoI will be opting my account out of the #Bluesky bridge next week. If you follow me from Bluesky (I think there are about 3.9K of you) and want to continue seeing my posts you will need to get an account on the fediverse. Cheers.
Anuj Ahooja@Gargron May I ask why? If there's accounts you don't like there, we have pretty extensive blocking features, including adding ATProto blocklists that pre-block a lot of negative accounts.
Scott Jenson@quillmatiq @Gargron blocking isn't a solution in this case
@scottjenson I'm not sure I'm following - if an account you didn't like joined the Fedi, would you not block them instead of leaving the Fedi altogether?
Andrew 
@quillmatiq @scottjenson @Gargron if a server on the Fediverse allows Nazis, it’s a Nazi bar and the whole server should be blocked. Same concept here. Bluesky welcomed ICE with open arms, therefore it’s a Nazi bar.
As a platform, Bluesky has shown its true colors - it’s just Twitter with a different name.
@piepants Bridgy Fed bridges the entire ATProto network, not just users on the Bluesky stack.
@quillmatiq @piepants @Gargron
This is the same argument Twitter made. You are "too big to fail". This limits your ethical choices, preventing you from being more restrictive.
This is exactly why the fedaverse holds its instances to such high standards because when one does not take a stand like this, the entire server is blocked
@scottjenson There's no too-big-to-fail in what I said above. I'm saying we don't just bridge Bluesky users, we bridge everyone on the entire network, including folks on single-user PDSes (me!), Blacksky users (you can see my bridged Mastodon profile there as well), and a countless number of shared PDSs (see selfhosted.social).
The number of users on non-Bsky PDSes is growing by the day: https://blue.mackuba.eu/directory/pdses
@quillmatiq @piepants @Gargron and that is great, so glad to see bsky growing! My point was that it's very easy for a Fediverse server to block an account like ICE. That doesn't appear to be the same for BSky.
@scottjenson What I referenced above is not Bluesky growing, it's the ATProto network growing *outside* of Bluesky. And, as stated above, there are managed ATProto blocklists that make it just as easy as the blocklists on the Fediverse, and they can be applied to a Bridgy Fed account.
@quillmatiq @piepants @Gargron
fair point, the frustration you're seeing is not directed at anew.social(or bridging in general) but bsky specifically.
@scottjenson I know! This is more for me (us) to understand what tools we aren't providing or aren't sharing well enough.
@jdp23 gave us great advice on improving moderation for Bridgy Fed users, which directly informed our work on a series of blocking features. We want to know when we aren't serving the community the way they need, so we can see if there's something we need to build.
@quillmatiq @jdp23 @piepants @Gargron
It's really a topology problem. If 95+% of all accounts are on bsky, there isn't much you CAN do as it's just one big server (in practice)
@scottjenson There will be things you can do soon, stay tuned 🙂
@quillmatiq @jdp23 @piepants @Gargron
Looking forward to seeing more!
Magnus Ahltorp@quillmatiq @scottjenson Oh, the neverending ”Bluesky will be decentralised soon, we promise”. Bluesky is for all intents and purposes one centralised server. If it wasn’t, you could just bridge your Bluesky instance to the Fediverse, and someone blocking the bridge wouldn’t be an issue.
Dave Winer ☕️@ahltorp @quillmatiq @scottjenson
And people believe that bullshit.
jameshjacksonjr@ahltorp @quillmatiq @scottjenson hmm im not in bluesky but i am part of the atproto network of servers
skaphle@jameshjacks0njr @ahltorp @quillmatiq @scottjenson Why is the bridge called the bsky bridge and not atproto bridge?
Louise Auerhahn 🏳️🌈@quillmatiq @Gargron Is it possible for Bridgy Fed to block ICE from seeing all bridged accounts on Bsky?
JonOne thing you could do is automatically subscribe bridging accounts to a blocklist that in includes ICE -- and DHS, and federal goverrnment agencies and administration issues. You could also block their posts from being bridged here. This isn't a general solution but would address an immediate high-priority issue while you work on other stuff.
(Going in the other direction, you could -- and IMHO should -- do the same for instances on the IFTAS DNI blocklist. But right now i'd say ICE is the higher priority in most people's minds.)
No matter what you do though a lot of people and instances are going to want to block Bluesky and unless and until there's a way to that without blocking Blacksky and Northsky the only solution is to not to bridge.
Also @haubles I am not sure if this falls within the stuff you work on, but this is something mastodon.social and .online should be thinking about. Bridgy Fed is opt-in which is great but still it's not clear to me that most people know that opting in puts you at risk of being trolled -- or worse -- by ICE or DHS. So what can you do at the instance level to help educate people? Or should is a better way to look at Bluesky as similar to fedi instances that host fascists and defederate it?
And as @fromjason points out here, it's similar to the situation with Threads.
https://mastodon.social/@fromjason/115913156758254415
In fact Threads may be even riskier. Bridgy Fed is opt in so people here won't be exposed to ICE etc by default. By contrast posts by people on .social (or any other instance that hasn't deederated from Threads) is just like federation in general: if somebody on Threads follows you and boosts your post, people there will see it unless you as an individaul have opted out by blocking the threads.net domain.