- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
You must log in or register to comment.
I wonder how that breaks down in terms of numbers of users. The largest instances seem to have federated, and they’re the ones that cost the most to run, and Meta has vast amounts of disposable income. I worry Meta will fund some of them in exchange for influence.
Meta doesn’t need to bother with back-channel influence peddling of existing instances. If Meta simply opened its own Lemmy instance it would immediately be the largest Lemmy instance by orders of magnitude.
For all I know Meta or X or Reddit already control or outright own one or more instances. I don’t hang out wherever the fediverse admins hang out, so I don’t have any tea to spill.
We haven’t blocked Threads yet, but I haven’t seen any content from it either. When exactly are Threads supposed to federate?
Good to see so many instances work together to keep the evil out of the fediverse
I’ve used this analogy before, but threads is like a huge, 5k passenger cruise ship docking in a small town in Alaska. You don’t have to know ahead of time that the 2 public bathrooms, one at the general store and the other at McDonalds, aren’t going to be enough. You can also forecast the complaining about how everything isn’t really tourist ready. It will suck for everyone. The small museum will be overrun and damaged, the people will be treated like dirt. It’s an easy forecast.
Here’s the important bit, just because they’ve never been in the cruise line business, doesn’t mean you have to give them a chance to ruin your town.
edit: made sentence make sense.
The problem with analogies is that they are not literally the thing that you’re analogizing, so there’s going to always be parts of the analogy that don’t “work.”
In this case, what resource is Threads (the cruise ship) actually using from the small town (the rest of the Fediverse?) that causes the inhabitants of that small town any actual trouble? The fact that people on Threads can read posts from people on the Fediverse doesn’t actually affect people on the rest of the Fediverse in any way. If you’re concerned about the converse - the Fediverse being overrun with content from Threads - that’s not actually something that they’re implementing.
that’s not actually something that they’re implementing.
That’s not true, their CEO said that you’ll be able to converse and comment without leaving the app in the near future. Also, most instance owners are small, they could be overwhelmed pretty easily.
I’m 100% sure that this small town isn’t ready for a cruise ship. That’s not to say, that in a year or two, we couldn’t be prepared for it. Right now, the relatively small influx from Reddit brutalized the existing community. This is the wild, wild, west for Meta because they’re not getting enough new users for their shareholders in their existing platforms, I’m sure they’re salivating.
A Threads users’ content is only going to be visible outside of Threads if the user explicitly opts in to that. The vast majority of people aren’t going to do that, or even be aware they can do that. In this analogy, most of the people aren’t going to be aware their cruise ship has docked at a town and aren’t going to be interested in getting off of it.
What do you mean? I follow a lot of hashtags on Mastodon. Won’t I be seeing a lot of Threads content if I’m on a server federated with them without explicitly opting into that?
Where are you getting this information and if it’s true? Even if it’s true, Meta isn’t known for sticking with what works for the user, but what works for their shareholders. They will figure out a way to exploit and/or extinguish the fediverse.
In the cruise ship analogy, they will stay on the boat the first few 3 or 4 times so everyone backs down and then they’ll open the bridge for all 5k. None of this rocket science.
Why do you want them here so bad?
Here’s where I got that information.
Why do you want them here so bad?
Because I believe in open protocols and freedom of discourse. I think that widespread adoption of open protocols like ActivityPub are a good thing.
I think that widespread adoption of open protocols like ActivityPub are a good thing.
Why is it a good thing?
Edit: I should clarify this question. You’re saying you like open discourse, etc., but if threads EEE’s the crap out of the fediverse, then this side is gone and you’re killing off open discourse. Also, corporations like meta, are closed discourse.
Meta can not EEE the fediverse. The worst they can do is create their own distinct fediverse. But anyone who doesn’t want to participate will still be using the open fediverse. They can’t take your instance or force it to update to their standards.
It keeps things open to competition. It prevents situations like we saw with Reddit, where single organizations are able to gatekeep content and force everyone to use their portals to access it.
User opts in? Or instance opts in?
Users. They’re talking about whether Threads’ user content will be “broadcast” out to external instances.
Yes, which as far as I understand functions via an instance federating with another instance, bringing users along with it regardless of input.
I know theres a future version on the way that will let users block out set instances, but since when do users need to pick and choose what instances their instance shows them?
Is it really that big? I thought a bunch of folks tried it for a week then stopped–especially when they realized you can’t delete your account without also deleting your linked Instagram account (assuming you have one).
They can’t have it both ways, is it 100 million and amazing or is it small and needing content?
good.
Don’t stop now
For clarity:
- The 41% number combines both instances that have actually blocked Threads and those who have pledged to do so at some point, so “have blocked” is a bit misleading
- As stated, this is a percentage of instances, not users. Roughly 24% of users are on instances that have limited, blocked, or pledged to block Threads.
How do we as users go about blocking them? Can we yet? Or do we have to wait for v .19?
Pre-0.19 I assume you would need to be on an instance that is blocking them.
Post-0.19 you can block them as an instance, meaning “any posts from communities which are hosted on that instance are hidden”
So, the answer still varies depending on your goals for blocking.
yes, on Mastodon when a user block an instance, it’s more like a mute than a block. Your posts will still be available to them, but you won’t see their content.
The only solution if you want to protect your content from being shared on an instance is to block it at the instance level AND that the instance use Authorised Fetch.
Not all instances have this feature on.
Thank you!
