Partially. It’d help a little bit. But if you federate with another instance that doesn’t block it, that data will still get out.
Essentially the protocol would have to be updated to carry a blacklist that all instances would adhere to, but basically via an honor system.
The only method that could truly protect your data would be whitelisting, but that would severely hamper and fracture the fediverse.
Except that means you defederate from everyone but whitelisted instances in that scenario. If I recall, it doesn’t work as a blacklist, but as a whitelist.
I’m just worried folks are putting too much faith in what defederation means.
Ok, but the number of people that think defederation is in anyway going to prevent this is fairly high.
No, if you’re on the fediverse and someone from a threads instance interacts with your instance.
The IP address is only of the instance server, not yours.
Everybody, please understand what defederating means. It will not stop the defederated instance from getting the data. It just means you don’t pull theirs.
If you want to actually control who gets data, you’d have to switch to a service like Streams. ActivityPub cannot prevent anyone from pulling data. It only allows an instance to decide not to pull from a specific location.
It’s also an indication they’re following US law. They can’t collect data without stating it.
Defederating won’t stop this. Defederating means you don’t pull their data, not the other way around.
We don’t know what they’ll do yet as there’s nothing in the article about what they do with the data or how the protect it.
Setting everything to private by breaks the fediverse pretty much. Imagine if everyone on Twitter was only private. It severely limits everything.
A “public” instance is just one that publishes to other instances if I understand correctly. So they would get the IP of the server instance. Which most instances actually do.
Defederating wouldn’t prevent this. It’s not how the protocol works. Defederating simply means you don’t pull their data, not the other way around.
This wouldn’t matter. Defederating means you don’t pull their data, not the other way around.
The article is just describing how ActivityPub works. What would be more important is how they claim to use that data. But that they collect that data is inherent to how the protocol works. They’d have to mention they collect it legally.
Isn’t the official repo for Lemmy on GitHub?
Haven’t found an easier way to bookmark something I’m following. And I boosted the original post which was well before they revealed their idiocy.
That’s fucking stupid. I’m done here. Someone in the thread even already posted their two different account names. I guess you think that’s just an illusion. Fucking idiot.
What premise? It’s not a philosophy. It’s an outright technical observation. You can do whatever you want. I didn’t say you have to like it. What is there to disagree with? You can say the idea isn’t for you, but it’s still correct.
Ok? I honestly can’t tell if you get the point yet or not though.
Email does that too. It’s even worse, you can make “[email protected]” show up but it’s really [email protected]. Granted, many emails hosts are getting better at flagging these, but one can still click the name to confirm on Kbin or Lemmy.
But that’s not what the post indicated. You can’t ignore the tone of the post and the misconceptions it implies.
Depends on the person. The point is, it’s entirely up to you. And keep in mind you’re not guaranteed to get the same name on every instance you create an account.
Looking into it, aren’t both of these only Mastodon and not part of ActivityPub itself? I can’t find details on them outside of Mastodon.
And what prevents the post from getting published to other instances from different sources?