this post was submitted on 17 Feb 2026
498 points (97.7% liked)

PC Gaming

13912 readers
853 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] mholiv@lemmy.world 13 points 1 day ago

It’s all about friction. As long as the user has to pick an instance they will always hesitate to pick any federated service. The average user will always choose the path of least resistance.

Proprietary services spend a lot of time trying to reduce friction, and it works.

The only solution I can think of would be a three part one:

  1. The main app of a federated service automatically rotates between a pool or reliable, reputable, non-extremist instances where the user can log in with an email and password.
  2. The federated service makes it trivial to migrate accounts amongst instances.
  3. the user can log into their instance threw any other instance perhaps threw oauth.

This would of course require some federated account login system. Hard but not impossible. It could be some sort of Casandra style ring based account service where nodes are part of the ring.

This eliminates the new user friction.

  1. Download app
  2. Sign up
  3. Login

It works anywhere any time with corpo style low friction. You don’t need to think about instances at all till you are ready to.