Yeah, I get that approach. IMO for 99% of people joining an instance that blocks Threads is probably a good idea. However, I’m not one of them, and I think most people on this specific instance aren’t either, hence why we’re here instead of somewhere else. I think that for my “threat model”, the benefits of having access to the full Threadiverse outweigh the possible downsides.
Yes. Meta is a shit company, and I’m not a fan of corporations in general so they’re doubly shit. Frankly, I hate them and everything they’re about. My point still stands. Particularly, for my threat model, I want to be able to monitor the situation and interact with people who feel “forced” to be on Threads.
Ahh, you’re sneaky. Okay. So you’re suggesting we actually pollute the fediverse so much, that Threads users have to migrate, once there’s such an unwrangleable liability that Meta pulls out. I’m in.
A lot of good people are on enshittified social media (Threads in particular) because they feel pressured by their social network (their actual set of human contacts) to “go where the people are”. Some of them are there because they don’t know that the free Threadiverse exists, particularly Lemmy (I’ve never met anyone IRL who knows what Lemmy is).
It’s not a silver bullet, and obviously I’m just one guy making uncoordinated comments and posts, but I think that there is some benefit to interacting with Threads users if and only if you personally can take on the extra load of doing so.
If we wanted to make a “coordinated” campaign against Threads, IMO the strategy would be to (1) be nice to people from Threads who decide to come to our communities, so long as they behave, and (2) post openly coordinated anti-Meta messaging distributed throughout the Fediverse in places where Meta can’t just take it down, of course placing this messaging in appropriate communities. I.e., make the free world a challenging place to be for a company that doesn’t respect freedom. But I’m not experienced/sociable enough to orchestrate item (2).
Yeah, I get that approach. IMO for 99% of people joining an instance that blocks Threads is probably a good idea. However, I’m not one of them, and I think most people on this specific instance aren’t either, hence why we’re here instead of somewhere else. I think that for my “threat model”, the benefits of having access to the full Threadiverse outweigh the possible downsides.
Man, but… Have you looked at all the downsides Meta has helped implement in the last decade+?
Yes. Meta is a shit company, and I’m not a fan of corporations in general so they’re doubly shit. Frankly, I hate them and everything they’re about. My point still stands. Particularly, for my threat model, I want to be able to monitor the situation and interact with people who feel “forced” to be on Threads.
Ahh, you’re sneaky. Okay. So you’re suggesting we actually pollute the fediverse so much, that Threads users have to migrate, once there’s such an unwrangleable liability that Meta pulls out. I’m in.
Not really.
A lot of good people are on enshittified social media (Threads in particular) because they feel pressured by their social network (their actual set of human contacts) to “go where the people are”. Some of them are there because they don’t know that the free Threadiverse exists, particularly Lemmy (I’ve never met anyone IRL who knows what Lemmy is).
It’s not a silver bullet, and obviously I’m just one guy making uncoordinated comments and posts, but I think that there is some benefit to interacting with Threads users if and only if you personally can take on the extra load of doing so.
If we wanted to make a “coordinated” campaign against Threads, IMO the strategy would be to (1) be nice to people from Threads who decide to come to our communities, so long as they behave, and (2) post openly coordinated anti-Meta messaging distributed throughout the Fediverse in places where Meta can’t just take it down, of course placing this messaging in appropriate communities. I.e., make the free world a challenging place to be for a company that doesn’t respect freedom. But I’m not experienced/sociable enough to orchestrate item (2).