How to Kill a Decentralised Network (such as the Fediverse)

How to Kill a Decentralised Network (such as the Fediverse) par Ploum - Lionel Dricot.

Seems the new Meta instance is known :
https:--www.threads.net
I block it preventively and will keep an eye on it.
https://www.theverge.com/2023/7/5/23784160/instagram-threads-twitter-competitor-web
Instagram’s Twitter competitor, Threads, briefly went live on the web

Instagram’s Threads web interface was live with thousands of brands and creators. The main mobile app launches to everyone on July 6th.

The Verge
@C_Chell @ploum Absolutely flawless move. Good riddance 👍️
@C_Chell
I see, yeah heard a lot bout that, understood!
@C_Chell @ploum This is a good decision you have my respect!
@C_Chell @ploum
you guys are my umbrella.
@ellyponey That kind of Umbrella ? 

@C_Chell @ploum Microsoft is well-known in using this embrace-extend-extinguish tactic; in fact you can almost say they pioneered this. While they seem to have backed off from this for the most part nowadays, the same can’t be said for other Big Tech companies, and with Meta and their past history I’m 100% sure they have ulterior motives for wanting to federate with the Fediverse.

They should be preemptively blocked by all current Fediverse instances, period.

@C_Chell Does blocking it mean we can't follow anyone on there? Pretty disappointing if so. Seeing ActivityPub reach these heights is exciting to me and I look forward to following more people.

@LittleshyFiM It's more to do with blocking meta corp from collecting data on users and other instances and selling them to data brokers and the likes for profit with disregard to privacy and possibly influencing ActivityPub tech and other instances in some ways.

Corporations tried and are stilling doing the same with linux in some ways, anyway they can i.e patent trolling.

It sucks that we'd have to block users on those instances (which is not our intention), but we're doing this specifically to protect users and our instance from meta. That's not even getting into the reputation FB has for letting misinformation and extreme ideologies go rampant.

@Shredd_Tone That's sad to hear. I can't help but think locking things down so quickly and preventing people from following what they want to follow is the very thing Mastodon sought to combat.

Seems like most of the discussion about Meta Threads is basically saying Mastodon should have a whitelist instead of a blacklist when it comes to blocking servers. I'd hate to see things go in that direction. I wish you all the best, but I'm probably gonna try out the migration feature and find a server which is more open soon.

@LittleshyFiM Well, we've always been open but we do have to block instances that are admin and modded by individuals to protect our user data bases. Google apps once blocked mastodon due to instances providing harmful content.

I.e we had to block instances that had been bully users for being bronies, which the admins didn't even care about. Plus other servers that provided child pornography, terrorism etc.

It's not a fun job, but something has to be done. If an instance is isn't taking it seriously or providing something that potentially cause harm to our users. Mastodon had been intended to stop corps profiting off data from their users. If people aren't comfortable with making nfts out of say a users artwork or song for profit, what difference would it make if they dox users for profit?

But having that said, whether you choose to go or stay, you'll always be welcome here to interact with us and I wish you all the best.

@Shredd_Tone I definitely appreciate the hard work that goes into moderation and keeping a community safe. That is certainly not what I was alluding to when I expressed desire for a more open server.

Is blocking Meta Threads a moderation matter? I thought it was more of an ideological protest. A protest which hurts the Fediverse a lot more than it hurts Meta in my opinion. They couldn't care less if we block them, but we miss out on reaching more people and helping ActivityPub break into the mainstream. Although I imagine there are moderation concerns too, most of the reasoning I've seen so far seems very vague and impractical. Even the official Mastodon blog seems optimistic about Threads. Not that they, I, or anyone already on Mastodon thinks people should have a Meta account to use it of course.

@LittleshyFiM @Shredd_Tone If there is one thing we can learn from the past it's that you can't let a single entity get too much control in a federated network.

Sorry but Meta Threads could single handedly get the majority of the user base which would let them dictate changes to the protocol. "Enhance" it. The rest of the network would have to constantly adapt to be compatible with Metas implementation. After a while the Fediverse won't even get recognized anymore. The majority will only know Threads. And at that point Meta will probably just cut the Fediverse integration.

It's the standard embrace, extend, extinguish pattern that we constantly see beeing applied by big corporations against open source projects. And sadly it often works.

Meta Threads is a threat for the Fediverse. Not an opportunity. The only winning move here is to not let them play.
@interru @LittleshyFiM @Shredd_Tone On the other hand, if we block every bigger player that wants to integrate into fediverse, fediverse will never grow out of its corner, and those others might build their own, being the succesful fediverse after all.
Imagine e-mail with "no you cannot mail to gmail because google is evil" or a webbrowser that doesn't work on facebook.com.
@404compliant @LittleshyFiM @Shredd_Tone It depends on the size difference and whether that company can be considered a bad player. The potential user base of a meta product might be enormous. It could crush the Fediverse in several ways.

I didn't say anything against Tumblrs announcement to support ActivityPub because I don't consider them a bad player. Especially since it's owned by Automattic.

Gmail is an interesting example because Gmail is known as a bad player in the e-mail ecosystem. Postfix had to add numerous workarounds because of Gmail specific quirks and Google absolutely doesn't cooperate. So on a standard abiding system you already are unable to send a mail to Gmail. Google is already pulling the "play by our rules" move.

So why isn't Google fully succeeding in this EEE attempt? That's because e-mail went corporate (e-mail is used by systems that probably won't see any change in the next 15 years) and there a multiple players attempting to EEE e-mail at the same time.

@LittleshyFiM @Shredd_Tone It's a protective measure against Meta's aggressive data harvesting, and an attempt to stop the Fediverse becoming another algorithm-driven hate-filled cesspit like Facebook.

If people wanna see that stuff, go to Facebook. If you want a social media experience that protects its users and isn't driven by corporate greed (so typically anti-LGBT, heavily right wing and so on and so forth), Meta needs to be kept out for good

@LittleshyFiM @C_Chell Having that said, it's still possible to follow a user who you are already following on a blocked instance, but not for adding on new users to follow (as far as my knowledge goes, at least). Which I understand isn't ideal.

Here's a discussion I found on the topic: https://github.com/mastodon/mastodon/issues/21798

I've only read a little bit of it, mind you, but there are more links in there too if it helps.

Being able to follow individual accounts from blocked instances · Issue #21798 · mastodon/mastodon

Pitch If a user blocked an instance, he/she should still be able to follow individuals from this instance. Currently, this user gets a 403 error without any explanation of why following this accoun...

GitHub

@LittleshyFiM
It's suspended not restricted so yeah no interactions possible at all

Letting Meta communicate with Fediverse could be dangerous for the health of the Fediverse itself and could essentially bring it into a situation like the one xmpp was in because of Google where Mastodon for example is just fixing issues with the federation with threads taking up time that could be used to add new features instead and at the end meta just realizes that there not enough users in the rest of the Fediverse to justify federating and would just stop federation
@C_Chell

@LittleshyFiM

If I decide to block Meta instance is based on the experience of the past like write in the article https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

Also, Meta even with all good will possible and not trying to extinguish the Fediverse (which I think it's their goal to surf on the trend and then kill it) they can intercept all interactions you can have with a Meta user, even if you post in the public feed, they can legitimately get it (like you can see in the global timeline).

Facebook (and Meta) have in their databases "ghost profiles", that are profiles from user with no account even not when they not interact with Facebook.

Blocking Meta to getting into the Fediverse is a task that all Fediverse administrators should do to save the Fediverse and try avoid these data hungry company out of the Fediverse.

Also the content provided by Meta (an attention based social network company) will guarantee bad content will come.

@fauli1221 @interru @Shredd_Tone

How to Kill a Decentralised Network (such as the Fediverse)

How to Kill a Decentralised Network (such as the Fediverse) par Ploum - Lionel Dricot.

@C_Chell @ploum
I'd go a step further and block the entire ip space owned by facebook. Because we all know they're going to try to find a workaround, and they're going to I'd rather make it as difficult and expensive as possible.
@C_Chell @ploum now that I think about it, a tech channel that I'm a fan of, Bob pony, moves to threads a few days ago. Definitely not so good decision for them :))
@lauraorchid Except if there is a huge demand for unblocking Meta, the instance will keep it blocked.