this post was submitted on 23 Jun 2023
515 points (98.3% liked)

Fediverse

17774 readers
2 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
 

This blog post by Ploum, who was part of the original XMPP efforts long ago, describes how Google killed one great federated service, which shows why the Fediverse must not give Meta the chance

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 100 points 1 year ago (3 children)

Basically the sequence of events as claimed by the author is that:

  1. XMPP, niche, small circles
  2. Google launches Talk that was XMPP compatible
  3. Millions joined Talk that could coop XMPP in theory
  4. The coop worked only sparingly and was unidirectional, i.e. Talk to XMPP ✅ but XMPP to Talk ❌
  5. Talk sucked up existing XMPP users as it was obviously a better option (bandwagon effect + unidirectional "compatibility" with XMPP)
  6. Talk defederated

This demonstrated exactly the importance of reciprocity. If they play dirty, kick them out asap.

[–] JoeKrogan 24 points 1 year ago* (last edited 1 year ago) (2 children)

Facebook messenger did the same . You used to be able to talk to fb users via google chat all from pidgin or another xmpp client. They are a hostile actor on the web who have already proven themselves untrustworthy. Let's not forget the Snowden docs or Cambridge Analytica

load more comments (2 replies)
[–] [email protected] 20 points 1 year ago (4 children)

Seems like just another reason why defederation should be completely removed from the protocol. It's way too easy to abuse and force centralisation.

There are other far less destructive and abusable ways of dealing with spam and content moderation.

I maintain that it's better to give the users the control, and allow them to decide which instances, communities, and users they want to be exposed to. Bottom up moderation, instead of top down.

For example, instances can provide suggested 'block' lists (much like how an ad blocker works) and users can decide whether or not to apply those lists at their own discretion.

By forcing federation, the network stays decentralized. Maintaining community blacklists that can be turned on or off by the individual user protects against heavy handed moderation and censorship, whilst also protecting users from being exposed to undesirable content.

[–] [email protected] 13 points 1 year ago* (last edited 1 year ago) (1 children)

The case with XMPP is that Google Talk introduced addons and intricacies that were unique to them. So they could federate with you in full with additional bells and whistles while you were stuck in an eternal catch-up. They presented a better alternative regardless of the eventual defederation. Even if we have some viral clauses as in GPL in open-source software that ensures protocol compatible software to be compliant, we can only do that to a certain extent plus enforcement is always an issue. Who are going to spend the vast sum of money in court to defend the "federation"?

This aside, enforcing federation alone does not ensure decentralization. These zero-marginal-cost fixed-cost-intensive businesses of the internet has a tendency to centralize as serving one more seat costs no penny plus one more seat diluates the fixed cost altogether.

load more comments (1 replies)
load more comments (3 replies)
load more comments (1 replies)
[–] [email protected] 86 points 1 year ago (5 children)

An excellent read. My synopsis is that if any big corporations joined the Fediverse they would fracture it, and that no matter what Meta, Reddit, Google, etc. would never want to see a decentralized platform succeed.

Pretty much the Fediverse needs to never let a big company tie into it. Our group needs to work at growing but at a sustainable rate.

[–] [email protected] 36 points 1 year ago (4 children)

We can't effectively block corporate injections, unfortunately. The admins of large hub instances are just of the opinion that bigger is better, and that more is more. They've been excited by the prospect of, I don't know, legitimacy or something, for a while now.

The result is going to be the network... not fracturing, per-se, but significantly restructuring itself. Big instances will get sucked into Big Social's halo, and be like the suburbs to Meta's or Tumblr's metropolitan centres. Smaller instances will end up as the exurbs. Content will flow quickly between metro and suburban spaces, and trickle across suburban spaces between the metro and exurban spaces. And which Fedivesre site you choose to use will end up mattering even more than it does now.

Right now, there's speculative reason to believe that Meta's offering up incentives to big instance admins. Those incentives will ultimately result in Meta owning them by proxy. They'll be client kingdoms, to mix metaphors, working on Meta's behalf, but getting relatively little in return for it.

I think Reddit moderators probably have a good idea about how they'll ultimately end up feeling.

[–] [email protected] 18 points 1 year ago (1 children)

Exactly right. Human greed doesn’t only come from money.

  • “It will be free advertisement and will help the project grow!”
  • “Look how many people are using my server. MY server. I’m popular now!”
  • And the more obvious, “If I make my server big enough, maybe I can cash out by being bought by this big company!”

In the end and from whatever the source, that bus always ends up in the same place once they convince themselves to get on it.

load more comments (1 replies)
[–] [email protected] 16 points 1 year ago (6 children)

The thing is that Meta and Reddit are masters of social manipulation through their algorithms. They know what low common denominators get the most engagement. I blame FB for a big number of echo Chambers and that just fed people their own negativity right back, made them spiral into a bad place mentally.

If they have any ability to post to the Fediverse or to track things they'll do it all over again.

It's the halcyon days of the Fediverse. Negativity on my feed is nonexistent. There's discussion. There's respect for differences. I know things will change with time but it's important that the big instances never work as proxies for big tech. It's important that big tech doesn't get a seat at the table. Voices should remain individual and not some mouthpiece to an industry that wants centralized control.

load more comments (6 replies)
[–] [email protected] 10 points 1 year ago

Fuck, that's how it's gonna go, and i hate it

load more comments (1 replies)
[–] [email protected] 11 points 1 year ago (1 children)

I don't think Google cares if the Fediverse succeeds or not. All they care about is that it can be indexed and people will be able to show Google ads on their instances.

Google doesn't have a Reddit equivalent or even any other social network competitor (anymore; they killed them all). They explicitly chose to exit that entire concept of products.

The only reason XMPP mattered to Google at the time was they were trying to compete with Apple for messaging on mobile devices. XMPP meant that Android devices using Google Hangouts/Chat/Gmail could chat with users on other platforms/services while Apple's chat app could only do SMS.

I guess what I'm saying is that Google is mostly irrelevant from the perspective of the Fediverse other than the fact that it can index and maybe give priority to discussions of certain products/topics like it does with Reddit currently.

[–] [email protected] 22 points 1 year ago* (last edited 1 year ago)

The threat right now is from Meta, that is eyeing the fediverse, not Google.

For anyone paying attention, I'm going to sound like a broken record here, but it bears repeating: business models that treat the user as the product--to be sold, not catered to--is a cancer on the internet.

This ought to be a wakeup call in 2023. If you aren't the paying customer/supporter, you are less than dirt on the underside of the boot of the big tech firms. You are cattle, in a factory farm, to be treated like shit, only to be slaughtered for profit at the next opportunity.

Attitude's like "I don't care about ads" and "my data is worthless to me, so why not trade it in" all mask the more fundamental problem that is that you are being held in a cage full of shit, when in reality you could be roaming free in a pasture.

[–] [email protected] 10 points 1 year ago (7 children)

@MyMulligan @jherazob I disagree.

I think the key thing is to just make sure that you don't use non #FOSS clients. #GoogleTalk started as a client for #XMPP, people migrated to it, and then #Google dropped support for #XMPP. If so many people didn't use #GoogleTalk, the #XMPP network would have remained unimpeded.

[–] [email protected] 15 points 1 year ago (15 children)

At this point it wouldn't matter, all they need to do is to mess with the protocol and it'd achieve the same thing, Meta and everything in it's sphere would "work well", but connecting with true ActivityPub servers would work just glitchy enough to annoy their users and point the fingers towards our side, just like it happened with XMPP

load more comments (15 replies)
load more comments (6 replies)
load more comments (2 replies)
[–] [email protected] 74 points 1 year ago (6 children)

One key difference between link aggregators (kbin/lemmy/reddit/digg) and microblogs (twitter/mastodon) on the one hand, vs social networks (facebook/myspace/diaspora/friendica) and instant messengers (aim/icq/xmpp/signal) on the other, is that the latter is highly dependent on your real-life social network, while the former is not. People using instant messengers and people on facebook want to use them to interact with their friends and family, so they have to use the platforms that those friends and family are on. On the other hand, people are happy to use link aggregators and microblogs as long as there are interesting people and communities to follow, even if they consist entirely of strangers.

Back in the early days of XMPP, when it was still known as "Jabber", I tried switching to it from AOL Instant Messenger. I told all of my contacts about it, and tried to get them to set up Jabber accounts. I was super excited that instant messaging was finally being standardized the way email was, and we wouldn't have to deal with AIM vs MSN messenger vs Yahoo messenger vs etc. I think I was also still bitter about being forced to switch from ICQ to AIM because all my friends had switched. I don't think I got a single person to start using Jabber, though. At one point I even declared that I was going to stop using AIM entirely, and that people would have to switch over so that we could keep talking to each other. Didn't work, of course. I just ended up not being able to talk to anyone until I finally went back to AIM.

A bunch of my friends use reddit, but we don't use the site to interact with each other in any meaningful way. This made switching to kbin really easy. Sure, I've told a few of them about it, but it doesn't really matter to me if they switch or not. As far as I'm aware, XMPP never really became it's own "thing" and experienced the kind of growth that the threadiverse has. Since we've passed the point of being self-sustaining, we can keep growing one user at a time, as individuals decide that they're tired of reddit and make the jump.

Because of this difference in dynamic, we're in a much better position against Meta than XMPP was against Google. The fact that we can even consider outright blocking Meta is a really good sign for us, regardless of whether we do so or not. Even if we do end up in a situation where 90% or even 99% of users are on Meta's platform, we can still refuse to allow them to compromise the ActivityPub protocol. Attempts to "embrace, extend, extinguish" will likely just result in non-blockading instances joining the anti-Meta blockade. With the connection to Meta severed, we'll just go back to enjoying the company of the 1 to 10% that remain, and that portion will likely be much larger than what we have now.

[–] [email protected] 17 points 1 year ago (3 children)

I'm not sure the distinction would make enough of a difference, and focusing only on XMPP might be doing yourself a disservice. There was nothing social about Office, but the OP points out how the same strategy worked there as well. Users, overall, tend to go where the other users are. Some people left Digg for Reddit because they were unhappy with Digg, but the vast majority simply followed because it was where the users (therefore activity) went. Reddit wasn't even the best of the many options at that time; what was important was the inflow of users. Once that kicks off, others tend to flock like moths to flame.

As you point out, Reddit was not where you interacted socially, yet it became where you congregated because that was where everyone else was and therefore where the easiest access to content and engagement was. If a Meta product becomes the most popular way to consume ActivityPub content, and therefore becomes the primary Source for that content, independent servers will become barren with just a Meta Thanos-snap of disconnecting their API. They only need to implement Meta-only features that ActivityPub can't interact or compete with, and the largest portion of users will be drawn away from public servers to the "better" experience with more direct activity. (And that's without mentioning their ability to craft better messaging, build an easier on-boarding experience, and put their significant coffers to work on marketing.)

Sure, there will still be ActivityPub platforms in the aftermath. Openoffice/Libreoffice still exists, XMPP clients and servers still exist, there are still plenty of forums and even BBS systems. But, there is a reason why none of those things are the overwhelmingly "popular" option, and the strategy they will employ to make sure that happens is the focus of the article, not so much XMPP.

[–] [email protected] 9 points 1 year ago

So just speaking from my personal experience, XMPP was absolutely useless for me, whereas OpenOffice wasn't. Microsoft did succeed in preventing OO from eating significantly into its market share, but OO continued to exist and be useful. It eventually caught up on the ability to read and write MS Office XML files, and in the meantime I only had a few occasions where I had to tell people "I can't read docx, send it to me as doc or rtf". To be fair though, I'm not a super heavy user of Office software.

In contrast, XMPP was basically nothing without Google. I couldn't use it before Google federated, and I couldn't use it after Google defederated. ¯\(ツ)

Kbin/lemmy/mastodon are in a far better bargaining position than XMPP was, and in a better position than OO as well. They're perfectly usable without being connected to corporate platforms, and they don't need to market to corporate customers either. To be clear, I'm not saying that they should or shouldn't block the corporate platforms. I think it's actually probably best if some of them do and some of them don't.

load more comments (2 replies)
[–] [email protected] 8 points 1 year ago (2 children)

As someone who is on just about every social media and aggregator site there is, I find myself gravitating toward sites that allow for as much interaction (or little) as I would like. My friends and I communicate through Facebook messenger, which obviously requires FB, but I use a browser/app called Ferdium, which lets me open messenger directly without the annoyance of opening the Facebook app itself. But each site has its own specialization that it does rather well. I mean, look at Discord's little communities, which are really designed to support the gaming community, and say, Instagram, which does photos very well. I get that companies would like the One Site to Rule Them All, but I look at it like I would at McDonald's and Dunkin' Donuts. McDonald's caters to one of my tastes, and Dunks does the other. Like your example with AIM I've largely given up with trying to get my friends to sign up for services. I'm older, and remember AOL when it was just starting out and even remember Compuserve when it was little more than a list server.

load more comments (2 replies)
[–] [email protected] 7 points 1 year ago* (last edited 1 year ago)

You are spot on. The difference between the products/services/values offered by XMPP and AcitivtyPub based fediverse is a very crucial distinction.

XMPP's value is derived from its connectivity. It is bandwagon effect at work. A single fax machine makes no sense but what about another one? Or another 100 ones? Now you have a positive network externality.

The bulk of the AcitivtyPub based fediverse works very differently. The value is from the content, be it people shitposting or memes or cats. As people who frequent online forums and communities can tell, the majority of members are mere readers. They are content consumers. Content producers are often the minority. The reason why soneone will stick to a particular platform is because of the content and the expectation that more is coming.

load more comments (3 replies)
[–] [email protected] 48 points 1 year ago* (last edited 1 year ago) (1 children)

I'm gonna throw this out there:

If Meta is going to join the fediverse (or implement something with activitypub) there is absolutely nothing we can do to stop them.

It's an open protocol. They can use it.

The only thing we can do is force them to follow the AGPL and/or fork the code if they get crazy with change requests.

[–] [email protected] 48 points 1 year ago* (last edited 1 year ago) (3 children)

Excellent article and it's of course a very serious concern regarding Meta's Project 92.

I want to use this thread to share one other concern that I've seen coming up constantly on Mastodon: overzealous instance admins that take things personally.

"You said X about me, I'll block your whole instance".

"I don't like a particular nuanced view that instance staff holds, #Fediblock now".

"Users of X instance reported me. I'll block the whole instance".

A few of these things happened in the last couple of days. We can't have instance admins defederating because of trivial petty stuff. The only thing this does is drive users to larger instances, among which there might be corporate interests.

load more comments (3 replies)
[–] [email protected] 44 points 1 year ago (2 children)

Okay, this is a good article. I was on the fence about Meta, wondering how they'd cause any damage, and this article cleared that up for me.

[–] [email protected] 28 points 1 year ago

Same. I was familiar with "Embrace, Extend, Extinguish" but somehow still didn't get it until Ploum explained it to me slowly.

[–] [email protected] 12 points 1 year ago

Yeah, I had never understood why people were so upset about Meta joining the fediverse but after reading that I do agree that there is a lot of damage it could cause.

[–] [email protected] 38 points 1 year ago

In short: Embrace, start pushing the service, driving users to it. Expand: add non standard extentions, locking users onto your quasi-compatable version. Extingish: break compatibility entirely, preventing users from swiching to the fully open version.

[–] [email protected] 37 points 1 year ago* (last edited 1 year ago) (5 children)

this is why the powers that be must never be allowed to join the fediverse: they'll destroy it

great article, if you're here scrolling through the comments I urge you to stop and actually read the article, it's worth your time I promise

[–] [email protected] 11 points 1 year ago

Your comment made me read it. You're right. I remeber the XMPP gchat days but I was too young to understand or care what XMPP was. I just remember the slick we ui being mind blowing.

load more comments (4 replies)
[–] [email protected] 36 points 1 year ago

Embrace, extend, extinguish.

[–] [email protected] 18 points 1 year ago (7 children)

Aye great read and very illuminating. We gotta protect the fediverse from corporate insidious destruction. This quote stood out to me:

And because there were far more Google talk users than "true XMPP" users, there was little room for "not caring about Google talk users". Newcomers discovering XMPP and not being Google talk users themselves had very frustrating experience because most of their contact were Google Talk users. They thought they could communicate easily with them but it was basically a degraded version of what they had while using Google talk itself. A typical XMPP roster was mainly composed of Google Talk users with a few geeks.

In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore. And started a long quest to create a messenger, starting with Hangout (which was followed by Allo, Duo. I lost count after that).

[–] [email protected] 15 points 1 year ago (1 children)

The whole article is good. I was about to quote this part.

What Google did to XMPP was not new. In fact, in 1998, Microsoft engineer Vinod Vallopllil explicitly wrote a text titled "Blunting OSS attacks" where he suggested to "de-commoditize protocols & applications […]. By extending these protocols and developing new protocols, we can deny OSS project’s entry into the market."

Microsoft put that theory in practice with the release of Windows 2000 which offered support for the Kerberos security protocol. But that protocol was extended. The specifications of those extensions could be freely downloaded but required to accept a license which forbid you to implement those extensions. As soon as you clicked "OK", you could not work on any open source version of Kerberos. The goal was explicitly to kill any competing networking project such as Samba.

We will need to be very vigilent with how things proceed here.

load more comments (1 replies)
load more comments (6 replies)
[–] [email protected] 17 points 1 year ago (1 children)

I hope people, especially instance owners and devs, listen to this warning.

[–] [email protected] 7 points 1 year ago (2 children)

Unfortunately, the fact that lemmy isnt in the pact to not federate with meta means history will repeat itself

Even then, i doubt theres enough strong willed people to actually resist big payouts in exchange for access to the federation. Its truly pathetic how people are easily convinced

load more comments (2 replies)
[–] [email protected] 17 points 1 year ago

Great read, warnings like this should be added to the conversation as long as federation with Meta is brought up. Especially for non-technical users or new users who haven't seen embrace, extend, extinguish before we will need some way to let them know what is on the other end of federating with large companies.

Sadly that's exactly who Meta wants, is people who don't care about the underlying system and they I'm sure will spend much more convincing those users that federation with Meta is a good thing.

[–] [email protected] 13 points 1 year ago

One thing we can do is encourage the Instagram users in our lives to open a fediverse account and use Instagram from the other side.

[–] [email protected] 12 points 1 year ago (1 children)

Is there some way to work a limitation into a licence? Something around only being able to present federated content with included algorithms. That would instantly make it unattractive to all the big players who profit off their specific ad driven algorithmic feeds.

load more comments (1 replies)
[–] [email protected] 11 points 1 year ago

Excellent read. Have just re-posted this on 'key, thanks for sharing this.
I agree that Meta is doing something very dangerous to the fediverse... hope they could be stopped in their tracks.

[–] ssorbom 8 points 1 year ago

I was interested until he brought up that matrix was just a reinvention of an existing idea. no, xmpp cannot do everything that matrix can. have you ever tried getting consistency of history in xmpp? it's absolute garbage. his warnings about the fediverse are on point though. I do wonder if matrix will end up suffering the same fate when Reddit offers to federate with them. The matrix protocol is already brittle as it is, and compatibility even between good faith implementations of existing servers is hard.

[–] sudneo 7 points 1 year ago

Really good read. I was not aware of the history in such details, but the argument is very compelling.

[–] [email protected] 6 points 1 year ago (1 children)

I red tha article and I think there is a problem in who it was managed at the time, if Google or Meta wants to join they should to us not us to them so if they break federation we should not care and continue implement our stuff, if something usable comes out of them joining we could use that but we are not their slaves, they are going to play in our home so we establish the rules.

Plus I think that if we don't become meta's costumer support and I don't think we will, we are not that dumb, meta joining the fediverse would only benefit us because we could see all the posts from Meta while being on a private add free server, people wouldn't have to choose between Instagram where all their friends are mad pixelfed ecc.

What do you guys think? Open to talk.

[–] [email protected] 17 points 1 year ago (3 children)

if Google or Meta wants to join they should to us not us to them so if they break federation we should not care and continue implement our stuff

As I understood the article, the danger is that large actors like these are too important too ignore. Too many users, too much content to neglect. So while in theory you are obviously right, in reality there will be a temptation to cater to their needs, because it seems so worthwhile.

load more comments (3 replies)
load more comments
view more: next ›