blue_berry

joined 10 months ago
[–] blue_berry@lemmy.ca 1 points 10 months ago

I meant unique in the size and numbers of users. I think at a certain point, you will lose some beginner-friendliness if you want it to scale.

Dunno if it’s still true or not but I also recall that stuff like Lemmy depends on DNS, meaning you have to be able to buy your own domain and depend on that kind of central authority (wasn’t the point of Fediverse stuff to be decentralized?)

Well, then you could just as well call the web itself not enough dezentralized. The Fediverse just builds on that.

Rather recently a good amount of Lemmy servers were oopsied because one of the .tld authorities pulled the rug from under an entire top-level domain name.

Ok, that's not so great

[–] blue_berry@lemmy.ca 2 points 10 months ago

Ok, so we have come to a conclusion here. That's fine. What I'm not sure about is whether these two standpoints will complement each other in some way or work against each other in the future.

I at least will take some interesting points away from this.

[–] blue_berry@lemmy.ca 1 points 10 months ago* (last edited 10 months ago) (2 children)

Mmmh, you could be right there.

Ok, but you have still the other competitors. And even if you count them out, there will always be instances that federate with Threads. That's how the Fediverse works. Yes you can do coordinated actions, but only to a point. For letting Threads enshitificate, you would need an air-tight wall from Threads to all other instances and that's not possible.

[–] blue_berry@lemmy.ca 1 points 10 months ago* (last edited 10 months ago) (4 children)

Interesting point. With activitypub, Threads could try to avoid enshittification.

The Problem: Threads, Mastodon and the other Fediverse apps will soon not be the only players in the Fediverse. At least letting die Facebook of enshittification will not work at this point. And additionally, if Threads decides to franchise its own instances, you have tiny thread-instances all over Social Media not even operated by Meta and that seems pretty resistant to enshittification.

[–] blue_berry@lemmy.ca 1 points 10 months ago

I guess we’ll just have to wait and see.

Yup.

I will personally not be on any fediverse instance that federates with threads.

I will and if it is only to argue with insta-kids about the Fediverse. ha ha :)

[–] blue_berry@lemmy.ca 1 points 10 months ago (6 children)

Its a monopoly, its behaving like a monopoly. But because of network effects, we cannot just ignore it, we have to go in direct combat.

At least if you want the Fediverse (with a diverse instance-landscape) to become big, confrontation with Meta is inevitable.

If you don't want it to become big, that's fine, but then we have a different opinion there.

[–] blue_berry@lemmy.ca 1 points 10 months ago (2 children)

Fair point - but: along with threads, hopefully there will be many other instances with, say, 20 million users combined. So the instance will still have 20 million users federating. And if the reason for the defederation was justified, maybe other instances will jump along too and then Threads loses 21 million users as well.

[–] blue_berry@lemmy.ca 1 points 10 months ago (8 children)

I think its not clear yet who will be eating whose lunch. It will be probably be a continuous back and forth.

[–] blue_berry@lemmy.ca 1 points 10 months ago (4 children)

Why is what too late?

[–] blue_berry@lemmy.ca 1 points 10 months ago* (last edited 10 months ago) (15 children)

A facebook client that can chose to defederate from facebook? The overall vibe on Threads is already not exactly great. Threads growth is limited (altough it could franchise at some point).

It would be good if the market outside Threads would continue to grow at such a rate that it is too expensive for Threads to pull EEE. As it is currently. As long as this is the case, the fediverse has a chance of surving.

[–] blue_berry@lemmy.ca 5 points 10 months ago* (last edited 10 months ago) (1 children)
[–] blue_berry@lemmy.ca 1 points 10 months ago

We can either chose to drive and contribute to the change, or hide away from it and eventually get rolled over.

 

cross-posted from: https://lemmy.ca/post/12225995

cross-posted from: https://lemmy.ca/post/12225991

TL;DR: The common view on Meta’s Threads is that it will be either all good or all bad, leading to oversimplified and at the end contra productive propositions like the Fedipact. But in reality, it’s behaviour will most likely change dynamically over time, and therefore, to prevent us getting in a position, in which Threads can actually perform EEE on us, we need to adapt a dynamic strategy as well.

 

cross-posted from: https://lemmy.ca/post/12225991

TL;DR: The common view on Meta’s Threads is that it will be either all good or all bad, leading to oversimplified and at the end contra productive propositions like the Fedipact. But in reality, it’s behaviour will most likely change dynamically over time, and therefore, to prevent us getting in a position, in which Threads can actually perform EEE on us, we need to adapt a dynamic strategy as well.

 

cross-posted from: https://lemmy.ca/post/12225991

TL;DR: The common view on Meta’s Threads is that it will be either all good or all bad, leading to oversimplified and at the end contra productive propositions like the Fedipact. But in reality, it’s behaviour will most likely change dynamically over time, and therefore, to prevent us getting in a position, in which Threads can actually perform EEE on us, we need to adapt a dynamic strategy as well.

view more: next ›