this post was submitted on 23 Jun 2023
411 points (98.1% liked)

Fediverse

17671 readers
30 users here now

A community dedicated to fediverse news and discussion.

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

Getting started on Fediverse;

founded 4 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

you are viewing a single comment's thread
view the rest of the comments
[–] qazwsxedcrfv000@lemmy.unknownsys.com 87 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@lemmy.world 19 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

[–] MisterD@lemmy.ca 4 points 1 year ago

Meanwhile, meta is about to join the fediverse and do it all again.

[–] alaphic@lemmy.world 2 points 1 year ago

I'm sorry, but what do the Snowden docs have to do with anything? I'm out of the loop apparently there

[–] code_is_speech@lemmy.fmhy.ml 18 points 1 year ago (3 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.

[–] qazwsxedcrfv000@lemmy.unknownsys.com 11 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.

[–] code_is_speech@lemmy.fmhy.ml 5 points 1 year ago

Your points are valid, but that doesn't mean we should do nothing. Enforcing federation and using copyleft licensing are both strong defenses against centralization and network dominance by a well funded third party.

As far as GPL goes, from what I've seen, big tech companies tend to take it pretty seriously. There is no reason we shouldn't be using that, and other license protections if we have the option.

As for natural centralization over time, I think that is a far less urgent problem than the current risks we are facing, those being major network fragmentation due to the use of defederation, and the risk of centralization around a proprietary platform and/or instance.

Removal of defederation and strong copyleft licensing seem to be natural first steps in combatting that risk.

[–] neontetra@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (1 children)

I may misunderstand how the fediverse and the software works but my understanding is content such as images gets copied over to federated servers and so it seems to me like the ability to defederate would be a requirement in order for servers to stay in compliance with the law and be able to limit various illegal and morally horrible materials from being copied onto their server and network.

Given that (unless I'm wrong about how this works or there's another way around it I'm not thinking of), at the end of the day is it really possible to not have the ability to defederate? There will be times when it would be needed it seems to me. Or for malicious bot servers, nazis, etc. — lots of potential reasons a full defederation would be desired or required.

[–] Barbarian@lemmy.ml 4 points 1 year ago* (last edited 1 year ago)

That's actually not how it works. Images are hosted by the instance the community is on. Other instances embed those images as links in the page. The image is downloaded from the original instance by the browser.

[–] VubDapple@lemmy.world 0 points 1 year ago

The Beehaw devs are feeling the need to defederate right now due to that being the viable strategy for scaling their mod efforts. What would the solution be if they could not defederate?

[–] sangle_of_flame@lemmy.world 3 points 1 year ago

the thing is that we know that they will play dirty; all corporations play dirty, that's the only way they get that big