How to block Bluesky from Mastodon:

[feditips@social.growyourown.services]

How to block Bluesky from Mastodon:

1. Go to the profile page of the account @bsky.brid.gy@bsky.brid.gy
2. Click ⋯
3. Click "Block Domain" to stop seeing Bluesky accounts
4. Click "Block" to prevent your own account being bridged to Bluesky

You may need to copy-paste @bsky.brid.gy@bsky.brid.gy into the search box on your server to make the profile appear.

If you can't find the account @bsky.brid.gy@bsky.brid.gy, your server is probably already blocking the Bluesky bridge.

#FediTips #Bluesky

[ramkay@mastodon.social]

@FediTips done

Thanks

[timmaddog@mstdn.social]

@FediTips
Blocked!

[neimi@voi.social]

@FediTips

Done

[oranger@piaille.fr]

@FediTips
Tks

[sgt1372@sfba.social]

@FediTips Just did this too!

[lawyersgunsnmoney@mstdn.social]

@FediTips Thank you very much! This help is very timely. I found out yesterday that my block was incomplete so have been working to fix that. Also, the app I was using did not give you the option of blocking the domain which was a pain in the ass to figure out. Since I'm using the web interface on my laptop, at least the option is there. One account got through yesterday so appreciate the assistance very much!

[ricardoharvin@mstdn.social]

@FediTips

Ironically, most of the worst accounts I've seen are hosted on mastodon.social.

Most of the Bluesky accounts I don't like are annoying, not scammy or spammy (so many mastodon.social accounts), or malicious.

kolektiva maintains the highest obnoxious/trollish (and therefore blocked) to useful account ratio.

[vol4life8657@tweesecake.social]

@jonathan859 @FediTips Good lord.

[jorgecandeias@mastodon.social]

@FediTips There isn't any bridging to bluesky unless you actually follow the bridge account. Blocking to avoid bridging is totally useless.

[firlefanz@writing.exchange]

@FediTips

I actively used Bridgy until a few months ago (when Bluesky started hosting US government accounts).

It really is a shame, but Bluesky has become a threat to many of my friends here, and so blocking is the only option these days.

[raphaelmorgan@disabled.social]

@ricardoharvin @FediTips most of the bluesky accounts I don't like seeing are of the "I want to share this post, but they don't have a CW (bc idt they can?), but if I repost the link it'll direct people off of fedi and onto a centralized site" variety the posts themselves, the accounts themselves, are usually fine or even good. I just wish they were on fedi proper lol

[irina@wandering.shop]

@FediTips Done, thanks!

[lawyersgunsnmoney@mstdn.social]

@FediTips Hey buddy, I checked and have the bridge and the domain blocked. Not sure how that account got through but I have a follow up question if you're able to help. I understand that someone could create and alias account to my profile on Bluski and determine that I've blocked them, is that right?

[fluffgar@mastodon.scot]

@FediTips When it still looked like Bsky might turn out okay, and perhaps even federate properly one day, I promoted the bridge. Even used it. But looks like that's not the future they chose.

I still have an account there but it's literally just for work reasons. The worse it gets there the stronger the likelyhood I'll just delete/abandon it entirely.

[somegregariousdude@dragonscave.space]

@FediTips Successfully blocked. My next question is, how do I completely block Threads as well?

[ottaross@mastodon.social]

@FediTips didn't realize that I had been merely muting it, so have just switched to blocking instead.

[virtuous_sloth@cosocial.ca]

@jorgecandeias @FediTips
That's not as obvious as you might think.

I think it's been fixed, but there was this issue with bridgy, noticed a few months ago, where a user who was bridged linked to a post of a user who was not bridged and on bsky the bridged "quote" post (this was pre- supported quote posts) pulled the avatar image of the non-bridged person and blew it up then cropped it resulting in a creepy situation caused by a gap in the bridge logic and some quirk in bsky image processing.

[marcusmasto@mas.to]

@FediTips

Done. Thank you.

[virtuous_sloth@cosocial.ca]

@jorgecandeias @FediTips
Had the non-bridged user known this was a possibility they might have chosen to block the bridgy account to reduce the chances of such an occurrence. Not that the onus should have been on them but still, given the occurrence was not intentional it does remind us that defense-in-depth has utility, especially for vulnerable people.