In my opinion, there are two big things holding Lemmy back right now:

  1. Lemmy needs DIDs.

    No, not dissociative identity disorder, Decentralized Identities.

    The problem is that signing up on one instance locks you to that instance. If the instance goes down, so does all of your data, history, settings, etc. Sure, you can create multiple accounts, but then it’s up to you to create secure, unique passwords for each and manage syncing between them. Nobody will do this for more than two instances.

    Without this, people will be less willing to sign up for instances that they perceive “might not make it”, and flock for the biggest ones, thus removing the benefits of federation.

    This is especially bad for moderators. Currently, external communities that exist locally on defederated instances cannot be moderated by the home-instance accounts. This isn’t a problem of moderation tooling, but it can be (mostly*) solved by having a single identity that can be used on any instance.

    *Banning the account could create the same issue.

  2. Communities need to federate too.

    Just as instances can share their posts in one page, communities should be able to federate with other, similar communities. This would help to solve the problem of fragmentation and better unify the instances.

Obviously there are plenty of bugs and QoL features that could dramatically improve the usage of Lemmy, but these two things are critical to unification across decentralized services.

What do you think?

EDIT: There’s been a lot (much more than I expected) of good discussion here, so thank you all for providing your opinions.

It was pointed out that there are github issues #1 and #2 addressing these points already, so I wanted to put that in the main post.

  • Isildun@beehaw.org
    5·
    1 year ago

    You can subscribe to any content anywhere as long as neither instance is on the other’s block list. If your instance hasn’t federated with the other instance yet, then you need to do that thing where you search for “!community@instance” and wait a few minutes. Otherwise, you just go to that community while on your home instance (e.g. for you, “mander.xyz/c/community@instance”) and click subscribe.

    • redcalcium@c.calciumlabs.com
      5·
      1 year ago

      Heck, you don’t even need to enter the community in the ! Lcommunity@instance format. Simply copy pasting the community url like https://lemmy.world/c/communityname to the search field works as well.

      • Isildun@beehaw.org
        3·
        1 year ago

        TIL. I guess they must have improved it recently. That’s one of the worst parts about starting on a smaller instance for sure. Being able to copy+paste the URL from its source is really helpful.