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.
You must log in or register to comment.
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.
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.
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.
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.
This is really the only way distributed has a chance to work but you won’t have much power as a server owner to ban users and be an edge Lord. Maybe the next things that comes up will be a true distributed network that also has incentives for people to spin-up new instances when needed.
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 🎂
@nutomic lemmy.world is a new instance which can also be used.
hehe just recovered my 3 year old account
checkmate!
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.
There is a new announcement saying they upgraded hardware yet again
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!
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
sh.itjust.works
I did it! https://sh.itjust.works
Credits go to you for the naming
Lol awesomesauce. I just made an account, I’ll use it as my main instance for a while. Let’s hope we can survive reddit hug of death 2.0 in July!
@autisticaudioguy lol same, just signed up today.
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?
This is a great one! Might use it
can’t wait for fedd.itjust.works to go online!
Keep it simple with
lemmy.itjust.works.If you get this going or need a hand then let me know.
Do you also have a few million dollars under your mattress? 😁
I’d like to tell myself that if it got to the point where it started to cost a few million that i would be able to have it pay for itself!
It’s a week later, but I did get this done finally. I’ve set up https://lem.monster/ . Still doing some tweaking, but it’s open.
Naming things is one of the two most difficult issues in IT, alongside cache validation and off-by-one errors.
choosing the name for my instance was easy. programming related? programming.dev it is!
I’m getting the following error reading this post: “item at index 2 does not exist”
Should I post this on stack overflow or some other Lemmy help community?
Which frontend are you using?
There are only two hard things in CS: naming things, caching, and off-by-one errors.
I already said that
Look at that, you sure did. I missed the “two hard things”. Wasn’t even drunk. 🤷
I name everything as var1 var2 etc.
var37.social incoming
IMHO, selecting an instance is definitely the biggest user experience problem Lemmy has at the moment. New users who are unfamiliar with the platform are going to pick the biggest instances, and that’s going to create performance problems.
We’ll need to prioritize work on instance browsing. Lemmy has outgrown the experience over at join-lemmy.org. If I could wave a magic wand, instance browsing and onboarding would have a way to show instance capacity / performance, a way to categorize and filter instances, and a way to recommend instances based upon interests. That would probably help to spread people out more evenly.
No problem just make a pull request with your changes.
You probably don’t want my code if you want a stable platform. ;)
That said, I dig what y’all are doing, and I’m veteran experience / interaction designer who’s been around the block for a few decades. So I might be able to find some time to mockup some experience concepts and or help to run user tests with audiences that your curious about.
Point us to where the coin slot is. E.g. Patreon. We insert coin 🪙, you upgrade.
deleted by creator
Nope. You can subscribe/post/comment on any community on any instance. There is one small seam though: if you’re the first person to subscribe from your instance, you need to put in the full URL of the community (https://lemmy.ml/c/gaming, for example) to pull it into your instance.
After that, everybody on the same instance as you will see it when searching for communities just like it was local.
EDIT: Oh, forgot to mention: make sure the search is set to “All”, not “Communities” when you do this.
deleted by creator
@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.
I agree because this way, new users will learn what and how to use other instances. Plus, it also helps with finding more content, especially if the user picked an instance without many people which makes there be less communities and content they can check out on first glance.
I disagree because it makes the more narrowly focused topic or theme based instances more daluted, makes everything blur together more, I also see it as a detrament to the smaller intances because they will now there local comunity will have less traffic
Perhaps the default should be a per-instance setting and/or a user preference.
I would agree with a per user or per instance
I think a client that might select a server for you by default (hopefully a trusted one of course) would make things way more easy to understand for the average user. Then making it easier to add or view communities on other instances.
https://toast.ooo is accepting registrations 🎉
I applied for a few other instances but this one came through first. Your downfall is being too good compared to the competition.
It seems like a common issue among ActivityPub services that people flock to the most popular instance and this causes problems. Why can’t load balancing happen transparently? It seems like the main thing that actually makes a difference between which instance users want to join is what the moderation will be like. Like I don’t want to be forced to sign up for an instance with a high amount of censorship compared to the rest of instances.
So maybe user registration should start from a centralized site that can describe the trade-offs of joining the various instances, and users don’t get to select their specific instance by default, but rather they select based on a loose moderation policy, and then load-balancing occurs on the backend.
EDIT: I also want to be able to migrate between instances without losing my community subscriptions.
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?
