How to block Bluesky from Mastodon:

[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.

[jorgecandeias@mastodon.social]

@virtuous_sloth @FediTips Yes, I know about that. But it was a bug, not a feature. Bugs happen. And it's been fixed.

[phillycodehound@encryptr.net]

@FediTips@social.growyourown.services @federatedsocialnews@channel.org Or you can just not bridge your account in the first place. ​

[virtuous_sloth@cosocial.ca]

@jorgecandeias @FediTips
We rarely know about bugs until they happen. That's the point. That bug being fixed doesn't help when the next one is revealed.

[billie@social.tchncs.de]

@FediTips

Just to note: #tusky allows muting, not blocking. The blck optipn is missing in #tusky. Using #tusky, you need to do it with the #web #gui.

[andoriansoup@mastodon.social]

@FediTips
Nice

[leeloo@chaosfem.tw]

@jorgecandeias @virtuous_sloth @FediTips
Are you willing to guarantee - on the penalty of death by ICE - that there are no other such "bugs"?

[jorgecandeias@mastodon.social]

@leeloo @virtuous_sloth @FediTips What makes you think I'm within ICE's reach?

[leeloo@chaosfem.tw]

@FediTips
So number 4 - blocking the bot - is the important one?

Asking because Moshidon doesn't show a domain option.

[leeloo@chaosfem.tw]

@jorgecandeias @virtuous_sloth @FediTips
This is not about you, it's about the people who might follow your advice. If you are willing to risk their life, you should be willing to risk your own.

[zenheathen@beige.party]

@FediTips Does blocking the domain still work if someone you follow boosts a toot from it?

[jorgecandeias@mastodon.social]

@leeloo @virtuous_sloth @FediTips Sorry, but that's just silly.

People are here on the fediverse, on a network that is inherently unsafe (as all are). Here, bad actors only need to lay low to grab all the information they want from people, as only when they reveal themselves blocking can happen.

And they worry with the tiny little probability of a bug sending their data elsewhere?

Come on. Be real.

Risk exists right here, right now. People should really be well aware of that.

[leeloo@chaosfem.tw]

@jorgecandeias
Wrong answer.