- cross-posted to:
- fediverse@lemmy.ml
- cross-posted to:
- fediverse@lemmy.ml
The Fediverse is currently divided over whether or not to block Threads. Here are some of the things people are worried about, some opportunities that might come from it, and what we need to do to prepare.
Right, we left there over much smaller reasons than Meta. If Meta is heavily involved in ActivityPub, where to next?
Right, but for how long would we be able to do this? If Threads does federate and get popular, even worse, the communities here get heavily integrated with Threads, wouldn’t it only be a matter of time until Meta makes a push to keep users on their platform over this one?
We come full circle here, if you’re not using Meta’s federated ActivityPub, it’s a ghost town because the goal is for Threads to replace us. What are you doing here on Kbin when all of the communities it is part of is now over on Meta’s instance?
I don’t know if it’s as simple as “don’t use it”. This is Meta we are talking about. You literally can’t not use Facebook to get away from it’s tracking, they track you regardless.
I also don’t really have a horse in the race. I’m with you in that yeah, I’d probably find somewhere else too. But I’m thinking long term with our space here, regardless of whether 41% of instances are defederated, Meta’s involvement is a bad thing due to their immense wealth and, in my opinion, high likelihood they will implement changes that we can’t get away from. I’m not so sure it will be as simple as not using their version. I also don’t think it’s wrong for people to be aware and vocal about this, even if it may not immediately affect us in the moment. Again, we left Reddit over basically the complete inverse of this situation. Reddit closing 3rd party apps to get users into their app vs. Threads adoption of these 3rd party apps to get data from these users.
Why would we be okay making it so that developers and users have to work around finding Meta-stripped builds when we can just… Mitigate how much Meta is able to do it in the first place?
When I said I don’t have a horse in this race, I meant I don’t much care whether my instances federate with it or not. You’re not the first doomsayer over Threads, but I have yet to see anything that would stop this decentralized thing from allowing us to just de-federate or otherwise ignore any changes Threads makes to ActivityPub after the fact. We literally CAN not use Facebook. You may as well say Microsoft is trying to extinguish Linux, but I don’t think they could if they tried. Yes, I’m familiar with EEE, but the things these technologies are used for appear to make them inextinguishable.
That’s not what I was saying, or meant to say. I was saying they are tracking you regardless of whether you do or not. Why allow that to extend further by embracing them into the fediverse? I also don’t think they are inextinguishable, I think there a wide, wide range of ways to fracture then consolidate.
Alas, time will tell and we can only hope it amounts to nothing and all us worrywarts are proven wrong as Meta does nothing but integrate then occasionally serve ads (with of course, all the background tracking).
Out of curiosity and completely unrelated, do you have an Android phone? Not Google? If so, it may be worth checking your active processes running under dev services, there may be a Meta Services and Meta Services Manager running in the background. It’s worth disabling these from the apps list, they literally don’t do anything but serve up ads and track you.
On by default through many phones and carriers, gotta love it.
They can track you right now without federating. These posts are all public. They can just make an account and farm information.
From my understanding between defederating and opting into fetch authorization this can be mitigated. Not prevented entirely, as you said they can just make accounts anywhere, but it prevents serving it up on a silver platter.
Besides that the data alone isn’t the point. It’s that combined on top of everything else.