this post was submitted on 14 Dec 2023
69 points (96.0% liked)
The Agora
1600 readers
10 users here now
In the spirit of the Ancient Greek Agora, we invite you to join our vibrant community - a contemporary meeting place for the exchange of ideas, inspired by the practices of old. Just as the Agora served as the heart of public life in Ancient Athens, our platform is designed to be the epicenter of meaningful discussion and thought-provoking dialogue.
Here, you are encouraged to speak your mind, share your insights, and engage in stimulating discussions. This is your opportunity to shape and influence our collective journey, just like the free citizens of Athens who gathered at the Agora to make significant decisions that impacted their society.
You're not alone in your quest for knowledge and understanding. In this community, you'll find support from like-minded individuals who, like you, are eager to explore new perspectives, challenge their preconceptions, and grow intellectually.
Remember, every voice matters and your contribution can make a difference. We believe that through open dialogue, mutual respect, and a shared commitment to discovery, we can foster a community that embodies the democratic spirit of the Agora in our modern world.
Community guidelines
New posts should begin with one of the following:
- [Question]
- [Discussion]
- [Poll]
Only moderators may create a [Vote] post.
founded 1 year ago
MODERATORS
Serious question - I’m not up to speed on what kind of effort goes into defederating/refederating. If it’s easy, then is “wait and see” an option?
Alternatively, is preemptively defederating now and refederating later if we want also an option?
If both options are on the table, I say wait and see just because it’s unexplored territory though I agree that it probably won’t be great. If it’s a big pain in the ass to change our stance, also wait and see; that way we only have to do the PITA thing once.
It is, there's basically a setting on the server to block certain instances. So the admin would just update that setting to enable/disable federation. However, defederation doesn't delete any data on either side, it just stops the flow of new data.
So if you care about Meta having a copy of all content for some period, the better option is to defederate now and refederate later if they somehow play nice. There is a risk that Threads could defederate from any instances that blocked it, but I'm guessing they're not going to bother, I think they're just looking for data to scrape.
It's actually relatively trivial to scrape the public data of any instance. If Meta really cared (which I highly doubt), there's nothing stopping them spinning up a temporary instance with a bot that auto-subscribes to all communities it knows about.
Defederating from threads doesn't change the fact that all information on any instance is pseudonymous, but very public.
Sure, but they have to actively do that, whereas federation just gives it to them. I want them to have to put in the work to scrape the various instances, not get it for free.
Couldn't they just get an intern to spend an afternoon actively doing that? It can't be that hard. I'm not a programmer, but it seems to me that if someone has the proficiency to set up an instance, they would have the proficiency to set up crawlers.
Probably, but they'll want to integrate it somehow as well. One of the main points of federation is to get access to more content, which means your users have more stuff to look at, which means you get more data to link interests to ads to improve click-through. Scraping it would just give them the data, but they'd have to recreate it for their users to consume.
So scraping is only half the battle here.
Both are an option and easy enough.
Honestly, and that's my personal take as a user not as an admin... I'm in the "wait and see" boat, but I'm nor particularly full of trust about this so my goto would be: