This site is currently struggling to handle the amount of new users. I have already upgraded the server, but it will go down regardless if half of Reddit tries to join.

However Lemmy is federated software, meaning you can interact seamlessly with communities on other instances like beehaw.org or lemmy.one. The documentation explains in more detail how this works. Use the instance list to find one where you can register. Then use the Community Browser to find interesting communities. Paste the community url into the search field to follow it.

You can help other Reddit refugees by inviting them to the same Lemmy instance where you joined. This way we can spread the load across many different servers. And users with similar interests will end up together on the same instances. Others on the same instance can also automatically see posts from all the communities that you follow.

Edit: If you moderate a large subreddit, do not link your users directly to lemmy.ml in your announcements. That way the server will only go down sooner.

top 50 comments

sorted by: hot top controversial new old
[–] 3 points 3 years ago (1 child)

Sadly, I feel like the Fediverse, based on ActivityPub, was fundamentally designed wrong for scaling potential. I do like Fedi and I like ActivityPub, but I think instances should not have to be responsible for all of this:

  • Owning user accounts
  • Exclusively host communities
  • Serving local and remote users webpages and media
  • Never going down, as this results in users and content becoming unavailable

Because servers "own" the user accounts and communities it's not trivial for users to switch to a different instance, and as instances scale their costs go up slightly exponentially.

I wish the Fediverse from the beginning was a truly distributed content replication platform, usenet-style or Matrix-style, and every instance would add additional capacity to the network instead of hosting specific communities or users.

I guess it's a bit too late for a redesign now... Perhaps decentralized identifiers will take us there in some form in the future.

  • source
  • hideshow 2 child comments
  • [–] 2 points 3 years ago

    While it might not be too late for that update, it would require some reconciliation to happen. There's the potential for multiple users and communities of the same name across servers that would need to be considered.

  • source
  • parent
  • [–] 2 points 3 years ago

    I've made https://lemmy.antemeridiem.xyz/ to help take off some of that load. New registrations are welcomed and it should be maintained for a very very long time 🎂

  • source
  • [–] 2 points 3 years ago (3 children)

    I'm going to set up a general purpose instance tomorrow with the intention of handling a relatively large number of users. The main problem is choosing a domain!

  • source
  • hideshow 6 child comments
  • [–] 2 points 3 years ago (5 children)

    I was also contemplating setting up a new instance for this. I have 100s of gigs of unused ram, CPUs on idle and a 10gbit connection looking for something to do. The only issue I couldn't figure out was the name. I own itjust.works was thinking of something clever subdomain to use with it. I'm glad I'm not the only one with this issue

  • source
  • parent
  • hideshow 8 child comments
  • [–] 3 points 3 years ago* (last edited 3 years ago) (2 children)
  • [–] 2 points 3 years ago (2 children)
  • [–] 1 point 3 years ago

    Dude killer url, nice one! Question for all, I clicked their link and went there and it’s an instance, surely. I tried to comment on their post, but was required to sign in.. I’m already signed in over here, I gotta sign in there, too? Anyhow I tried to sign in with my lemmy.ml creds but that didn’t work. How can I interact with posts there?

  • source
  • parent
  • load more comments (2 replies)
  • [–] 1 point 3 years ago (7 children)

    Naming things is one of the two most difficult issues in IT, alongside cache validation and off-by-one errors.

  • source
  • parent
  • hideshow 9 child comments
  • load more comments (5 replies)
  • [–] 2 points 3 years ago

    @nutomic lemmy.world is a new instance which can also be used.

  • source
  • [–] 2 points 3 years ago

    I don't know what happened but in the last half hour the website has become highly responsive again. Thank you admins for your hard work.

  • source
  • [–] 1 point 3 years ago (1 child)

    I use kbin too.

    New to this feedverse or how you call it.

    Why isn't there one login that can post on all platforms and I have to signup on each separately?

    If there is, you're not making it obvious I guess.

  • source
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (1 child)

    @nutomic @ionhowto you dont have to sign up on multiple instances. if you want to comment a post on another instance, copy the url and paste in into the search field and then your current instance will fetch the post so you can comment on it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    What happens to the users of one instance when that instance is shut down or deleted? Searching for a url seems way too complicated. Can't one subscribe to a server or sub category on a server?

    This I would really want it to work but it's much worse to me than forums even.

  • source
  • parent
  • [–] 1 point 3 years ago*

    Is scaling the server a largely financial issue, or not? @nutomic@lemmy.ml

    could you reasonably confidently say that you could 10x the amount of users for something like 1000$/mo on liberapay?
    If so, would you mind setting a "goalpost" for the community to help lift the financial burden?

  • source
  • [–] 1 point 3 years ago

    hehe just recovered my 3 year old account

  • source
  • [–] 1 point 3 years ago (1 child)

    lemmy.ml should be a roundrobin dns that sends you to a random instance in the pool. Or else you will re-centralize lemmy and curmble under the IT bill.

  • source
  • hideshow 2 child comments
  • [–] 2 points 3 years ago

    Except (as far as I'm aware) your account only exists on one instance. So, if I end up on beehaw.org due to the round-robin, my account on lemmy.ml will not authenticate to that instance. I would have to have a separate account per instance which is hundreds of accounts.

  • source
  • parent
  • [–] 1 point 3 years ago

    I hope it's not inappropriate to comment this here, but if anyone's looking for another space to join, I'm in the process of building Krab Borg. It would be lovely to have people to help fill it out and diversify the communities, as well as suggest what the local ones should look like as I have no idea.

    I'm trying to balance not reinventing the wheel/duplicating existing communities 100 times but also still supporting the idea of decentralisation and creating some duplicates (though this isn't hard and fast, I'm open to feedback).

    I've seeded it with some communities from other servers (including a bunch from lemmy.ml) to get things moving a bit as well.

  • source
  • [–] 1 point 3 years ago (1 child)

    is it possible to move an existing profile to a new server, like on Mastodon? or I need to create a new one and "start over"?

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 1 point 3 years ago (1 child)

    Hi, as one of the new people, is there a way to transfer to another instance or would I have to create a new account there?

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    You have to create a new account. But that's easy ;)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (2 children)

    That's kind of wrong though, isn't it? What about stuff like GDPR data exports? Users should be able to export their data, then import it into another instance, effectively migrating instances.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago (1 child)

    I think lemmy will be bitten in the ass by not having considered clustering/horizontal scaling from the start. Federation alone as a scaling mechanism is only feasible for "nerds". But if the network wants to grow, we will need a few scale-able large hosted instances. And if their only choice is to scale vertically, there will be a hard limit (unless we put a good old Mainframe somewhere ^^).

    Another downside of this design is: you can't run it with high availability. If there's only one process per instance, updating it will mean the whole instance is down. Sure, if all goes well this downtime is under a second. But if it doesn't go well or if a migration is needed, this might quickly become hours.

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    Indeed. If a big instance like lemmy.ml was to be shut down all the communities would be lost. This is simply not sustainable. Why would users put effort building a community if it could be gone at any time?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    That however would be a different problem. A horizontally scaled instance would be able to cope with more users, but if it shuts down for monetary, personal, or whatever reason, it's still down.

    Protecting a community from this is what the decentralized part is for. That is already in place.

    (Although there is a middle ground where you could design the system in a way that one instance is mirrored and load-balanced across different hosters. That would actually also be quite interesting to have. But that's another layer of complexity on top.)

  • source
  • parent
  • [+] 1 point 3 years ago* (last edited 2 years ago) (2 children)
    load more comments (2 replies)
    [–] 1 point 3 years ago*

    @nutomic@lemmy.ml It might be a good idea to default the Communities page to All instead of Local, to help push users into discovering other instances and promote them.

  • source
  • [–] 1 point 3 years ago (1 child)

    Point us to where the coin slot is. E.g. Patreon. We insert coin 🪙, you upgrade.

  • source
  • hideshow 2 child comments
  • load more comments
    view more: next ›