Welcome, lizard dude!
That's utterly meaningless to me
I'm not on Threads
Are you really not understanding how this works?
That screenshot applies *only* to people on Threads, with accounts on Threads
It has nothing to do with anyone on #Mastodon or anywhere else on the #Fediverse
Do *you* understand how any of this works?
Then, I've been replying continually to Mosseri's cloned #Threads posts over here on #Mastodon since mid-December, so I'm well-aware of exactly how all this works -- in reality
Or doesn't work
In a few weeks (or less the way things are going) it'll be time to #DomainBlock #ThreadsdotNet and clear my timeline of all this noise
UPDATE:
See pinned post; Domain Block for @Threads.net and word filter for Threads
cc @wileyfoxyx
Which I have known, and proven over and over, since mid-December on every cloned #Threads post that has shown up on #Mastodon
You don't seem to understand that there are people on Mastodon who have been watching this side-show and doing actual experimentation to see what does and doesn't work
We don't just get our information from the Verge or TechDreck or whatever it's called now
cc @wileyfoxyx
Which I've known since I first started "replying' to Mosseri's cloned Threads posts over here on Mastodon since back in December
Nothing's changed -- all the fresh new drama notwithstanding
@FinchHaven Yeah, it does seem like the only difference now is that they've opened it up to a slightly broader audience, but the functionality is the same as it was for the handful of users they enabled in December/January. I too expected a bit more.
But actually, this is a massive leap. It means they're ready to tell their (some of) userbase about it; ready to take it public.
And don't forget, Mosseri did say at the time that it would take the better part of a year. I think that's still true; we haven't even finished Q1 yet. Remember, Meta is a big corporate with billions of users and tens of thousands (hundreds of thousands?) of employees. The wheels turn slowly in such a company. 🤔
@MisterMadge @FlockOfCats @zuck
Great idea. I'll start
Hey @zuck - go back to your surveillance capitalism monopoly, you blight on humanity!
can you see replies?

An user-level instance block is super easy and quick if one wants to@nartagnan @stux @latsss if you put your information publicly onto the internet, anyone with access to the public internet can access, save, manipulate, and reproduce your data at will
If someone from Threads follows you, your private/followers-only posts will also be sent to the Threads server to be shown to your Threads follower, and so Meta can access that data too
@chromaticliteralist @nartagnan @latsss But this goes with all posts 😉
Keep in mind that Mastodon is a public social network and when posting in the "public" status your post will be "broadcasted" onto the web via ActivityPub for example, like shouting it thorugh a megaphone
If you want your posts protected, post in followers-only and set the account to approve followers 
@stux @chromaticliteralist @latsss
You say blocking at user level has no effect ?
@nartagnan @chromaticliteralist @latsss Yes it does 😉 What i said goes for the whole "public social network" concept
Ofc blocking helps but if one wants to play it 100% safe be sure to look further in how the Fedi works is what i mean
@nartagnan @stux @latsss if your user account blocks the threads domain, no one there can follow you and so your private/followers only posts will not be shared to Meta’s instance
Regardless of your block strategy, Public posts are always accessible to anyone in the web for any purpose they please (including Meta).
Unlisted posts can also be scraped out from the APub network, regardless of block strategy, which an industrial player like Meta would do.
@chromaticliteralist @stux @latsss
Sorry, that was not what I wanted to know.
I know the whole public things.
My question is :
- blocking at a user level do the same (for my account) than a defederation ?
- if, on a 2-users instance, both decide to block tread, is it the same than a defed ?
- concerning Threads conditions too ? Do they treat user-block the same way than a full defed ?
@nartagnan @stux @latsss you’re going to need to look at the docs if you want to split hairs this far into the weeds.
Defederation is the more powerful tool. Metadata is still passed around otherwise.
Threads doesn’t “treat” blocks or defeds at all. The protocol does. Threads doesn’t get a say.
@chromaticliteralist @stux @latsss
Of course they scrap. But is it the same amount of scrapping ?
And considering where they have a say:
If they say "we will consider opt-out of consent if you defederate, but not if you only user-block", they have a say.
I don't have money to go to court for that.
A personal block will stop that user from seeing your data if they are logged in, if they're on the same account you blocked, and *if* their instance is operating under regular Fediverse parameters, a gentlebeings' handshake as t'were.
I hold no hope that Threads will be at all structured as to enforce user-centric moderation on the larger Fediverse.
Hey Stux,
thought so, too, but the user-level block doesn't seem to work properly:
https://astronomy.social/@2ndStar/112140391376401898
(same for me)
@[email protected] Wieso sehe ich deinen toot? Ich habe threads doch geblockt? Oder werden nur die Originaltoots ausgeblendet und die Antworten kann ich sehen?
@Qazm
Thanks.
"You'll still be able to see replies from users elsewhere made in response to posts on threads, and you'll also still see when someone else mentions threads users."
That sounds rather reasonable.
So it would be rather like a discussion here where the setting is "followers only," so everyone will only see posts by people (or bots 😉) whom they follow, correct?
(Which still puts me off at times, having comments apparently coming out of thin air, which is why I...