Apparently not many people believe me when I say that "normal" users using the "block this domain" option, is functionally just a mute....

There's gonna be LOTS of very mad people when they find out for themselves that meta/Threads can still see their posts....😬🤦‍♂️

To actually block Threads, you have to be on an instance that actually blocks them. As of right now, the biggest instance that blocks Threads is masto.to

So all this talk most of you are doing, means absolutely nothing because the majority of you are still federated....

#Threads #Meta #Fediverse #Mastodon #Fedi #FediMeta #FediTips #MastoTips

@BeAware If I'm on an instance the blocks Threads, and I post something, and my account is followed by someone on an instance that does not block Threads, and my follower boosts my post, then anyone on Threads following my follower will see my post (assuming the day has come when messages flow from Mastodon to Threads). And that Threads account can then boost it on Threads and my post, from a Mastodon Threads blocking instance, can then even go viral on Threads.

Isn't this so?

@Jerry hmm. I don't think so, because if it's like a normal activityPub instance, it would honor the block and the boosted post is a direct relay of the post from the original server, so blocks should be honored with boosts.

"Quote posts" however, arent the same and could be relayed to Threads.

Boosts are block protected because of the way it's built into the code as far as I'm aware.🤷‍♂️

@BeAware

You say If it’s like a normal activitypub instance, but firstly there’s the big if there, and secondly that assumes there is such a thing as a normal instance.

I’d say the whole point of a distributed system like this is to allow different instances to operate differently, not to be all under the same umbrella like the centralized social media platforms.

So basically, it’s considered a feature that what you’re talking about doesn’t really exist.

Everybody needs to realize that anything they post on this platform is effectively public to anyone who wants to access it, including

@Jerry

@BeAware

Right, and the standard is basically broadcasting for anyone listening, and that’s my point.

@Jerry

@BeAware

We can see that blocks aren’t honored by the protocol by the fact that people don’t honor the blocks as they engage with the protocol.

@Jerry

@volkris @Jerry I've never had this experience on my own instance. Every block that I've made so far, has been honored. And yes, I usually check.

Follow

@BeAware

It’s like saying everybody obeys gun laws since I’ve never been shot.

No, this is important because a lot of people in this platform don’t realize how tenuous the privacy controls actually are. We really need to emphasize that so much on this platform is based on good faith expectation instead of actual engineered control.

People need to know how little guaranteed privacy they have here because people rely on the system that isn’t actually nailed down.

@Jerry

@volkris @Jerry sure, but what I'm saying is exactly how the standard handles it and how threads would need to handle it and why that would be, and you're dismissing it like it's not the case, but it is.

I feel we're going in circles. You're stating that we need people to understand, yet you're denying things that are fact, completely doing the thing you're saying we shouldn't do...

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.