Most of the communities I’m interested in are on LW. If LW is down, Lemmy is down for me. It is also important to understand that LW is experiencing these issues because it has the largest population. The more people come to Lemmy the more instances will cross this threshold and will go offline.
Comment on On the future of Lemmy vs reddit
Claidheamh@slrpnk.net 1 year agoThat’s an issue of your instance, not of Lemmy.
Aux@lemmy.world 1 year ago
alex@jlai.lu 1 year ago
The more people build instances and the more people create communities outside of lemmy.world, the more resilient all this will be. Lemmy is the kind of place where you can fix your issues by building alternatives.
Hosting an instance has some cost and technical difficulties, so I don’t go around recommending that, but creating an account on a mid-sized instance and creating communities there for what you like to talk about is in everyone’s power.
ICE_WALRUS@lemmy.world 1 year ago
One issue I see is reports as recent as a month ago of people bringing an instance to it’s knees with a python script on 1 desktop computer. It’s one thing to ask for more instances and investment into the hardware to run them from more people, but it’s another thing not realizing that the code itself is heavily under optimized. For now, and you can see this everytime there’s an outage via the atlassian uptime tracker notes, server owners are throwing more resources to bandaid issues.
I myself am currently running an under optimized application for my company, we are using 4x the amount of money to run it as what it’s meant to replace currently. At a certain point even throwing the kitchen sink at problems stops working.
Lemmy’s code needs to mature more, but im excited about the future for sure.
1984@lemmy.today 1 year ago
There is a nice button on each instance that turns off new registrations. Once an instance owner has enough users and don’t want to upgrade the instance anymore, he checks that one.
It will be impossible to ddos every Lemmy instance, not very efficiently at least.
Aux@lemmy.world 1 year ago
If I’m interested in community X on instance M and M is down it is irrelevant that instances N and O are up - I still can’t access X on instance M.
I don’t know how you people browser Lemmy, but I only read subscribed feed. And most of the communities I care about are on LW. Thus it is absolutely irrelevant that other instances exist. And no, I don’t want to read the cache - I already saw old content.
jdsquared@lemmy.world 1 year ago
But even if I’m on my instance, lemme.ee, and LW is down, I’m not going to see anything from that instance. Which is where the most activity is. So I might see the same link for an article locally, with two comments, and no interaction from the instance with 300 comments.
I mean, eventually other instances will grow, but then they will face the same problems as Lemmy.world.
1984@lemmy.today 1 year ago
While world is down, you can still read everything that was posted and federated before it went down on other instances. It’s not like you suddenly don’t have anything to read (unless you are on here 24 hrs / day).
jdsquared@lemmy.world 1 year ago
It’s not really just about reading, it’s the engagement. I can read something from a couple of hours ago, comment now, and then somebody might read it in a couple of hours. And then comment back. But then I’m barely interested in the conversation because I’ve moved on.
But I’m just nitpicking. I know it’s going to balance out. Or it won’t and we’ll move on to something else that does LOL. Or I can always spend more time outside. Gasp.
1984@lemmy.today 1 year ago
Being outside is dangerous, it has fresh air and sunshine. :)
NathanielThomas@lemmy.world 1 year ago
So it’s Lemmy.world, not all the servers
samus12345@lemmy.world 1 year ago
Correct, I have an alt account on a different instance because .world is down so much.
jack@monero.town 1 year ago
Yes, the network load should be distributed among many small servers. That’s why my main acc is on monero.town