187
What are some downsides of software being federated? (lemm.ee)
submitted 3 years ago by to c/asklemmy@lemmy.ml
122 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] 3 points 3 years ago* (2 children)

Yes, now please check the title and content of the OP.

The whole discussion is about the downsides of federated protocols/apps/systems vs non-fedreated ones.

And my point was that it's much easier to expand non-federated software.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 1 point 3 years ago (1 child)

    I'm not sure you can make that argument. It's more about having a dedicated developer base than federation. FOSS has almost always been behind corporate development, that's not really a downside of federation itself.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [โ€“] 1 point 3 years ago

    The whole system behind eMail (all the protocols involved and all the software implementing it) has been built by FOSS and non-FOSS, commercial and non-commercial entities.

    Over the decades there were enormous amounts of money and enthusiast labour on it.

    And still it's really hard to make sure that the address in the "From:" field is actually the one that sent the email. And if you try to do something trivial like sending an encrypted message to a random email user, chances are almost zero that that user is actually able to read the encrypted email, because it requires additional configuration.

    There were >40 years of time, millions of man hours and billions of dollars have been invested in the eMail system, and yet trivial things that pretty much every major messaging service has are still outlandish for eMail.

    And not even Gmail, with all their money, managed to fix these issues.

  • permalink
  • fedilink
  • source
  • parent