Great news!

It’s not about looking what’s happening in the garden, it’s about entering in the garden. It’s two very different situations.

Meta is a dog shit in the middle of a dumpster. Episode 36384927338

A good implementation would be a warning at the creation of a community. Lemmy looks if a community already exist on the instances and display them. It would be on top of a better search.

It’s a similar situation as with the unions. We can all manage to have a pay rise by ourselves. Or, we unionize and ask together for the pay rise.

Defederating the instance is like unionizing. We all go forward instead of individually to have weight. This weight is in form of killing asap the federating attempt, as threads.net users will have nothing to see in the Fediverse. If you let each user manage the situation, threads.net can do whatever they want. There is no individual responsibility in this case. We have to play collectively.

We need to play collectively because the Fediverse isn’t one monolithic network, unlike Meta. It’s a federated network. It’s each instance and Meta. This is why unionizing is important. It’s the Fediverse and Meta. This is the magic of activity pub. You can let others use the protocol but say no to the interaction with them.

The second aspect is that Meta is relying on “cognitive capitalism”. Meta will use free cognitive time from the Fediverse to capitalize. This has huge implication on mental health and all kind of minorities relying on the Fediverse for various reasons. We can say all together no to this, what isn’t possible individually. I recommend the book “The Soul at Work From Alienation to Autonomy” by Franco “Bifo” Berardi. It’s a good book to understand the issue with Meta and others.

You’re playing the classic “it’s the individual responsability” game. It’s how you deregulate everything and the consumer losses every right.

We have to acknowledge that we have systemic or/and societal issues. This is a systemic issues so a common thing.

Absolutely no problem!

By chance, the instances (for or protecting minorities) I’m on are all defederated of threads.

For mastodon if it can help:

• Open your favorite text editor and write threads.net

• Save it as csv

• On your profile on Mastodon, click “edit profile” and scroll to “import/export”.

• Choose “import”, it will open a menu.

• In this menu be sure to click on “Following list” and choose “Domain blocking list”.

• Browse and select your CSV

• Click upload

Longer user know about it. It’s good to post it time to time (as a reminder or not) so people know about it.

Infinity grow is a mirage. We need to understand that. It’s fine if a social media as a limit.

What’s important is how you manage to keep it in life. Even here, you have a limit. It’s conservative to think that it will last for ever as you will encontre the same issue as with infinite grow.

The fact is that thing appear, have a lifespan and die. Social media aren’t immune to it.

With the last court rule in Norway, Meta must ask your consent otherwise they can’t do anything. This is a huge issue for them on the fediverse. They must ask the consent of each European user what is nearly impossible. One solution is to filter were the instances are hosted. They don’t interact with the instance hosted in Europe. But, it doesn’t resolve the issue looking how the fediverse work. This is why Europe won’t see Thread.

To prevent, instances should migrate to be hosted in Europe. The second is to change how fediverse works. It’s fondamental to add options to ban some instances not just defederate. It’s the tactic of putting meta and instance that federate with them on the side.

This reminds me of the issue with some image content we spoke at the beginning of the week. I saw it like astroturfing. I would be surprised if this federation of Thread has a similar end.