A lot of bots were spamming the instance which was causing an IO bottleneck, and thus timeout issues. We're looking into solutions to limit their impact, such as rate-limiting users. We're trying to do it in such a way that it doesn't impact regular users which is why it's taking a bit longer.
Awesome, thanks for the update. You guys rock.
Yea, rate-limiting per user instead of per IP might be a bit more complicated.
Appreciate the work y'all put into this.
You guys seem to handle fine, but if you need to toss a few ideas at a network engineer, ping me.
Thank you!
Shit just doesn't work
It’s A LOT worse on lemmy.world, I’d say most of the instances are overloaded that prime time instances.
a .world refuge here, can confirm it's overloaded, now I'm moving to lemm.ee
Yea I have an account on both sh.itjust.works and lemm.ee
For the last day or so lemm.ee has been more reliable but otherwise sh.itjust.works was very good too. Ultimately, I feel like this whole thing was meant for having a lot more smaller instances rather than huge ones.
It was the bot bullshit, as others have said. I was kinda expecting it once I saw the posts about the account spamming new C/s, but it hit harder and longer than I thought it would.
That's what...she said?
Conversely:
So did that homegrown green
Lmao!
theres apparently some bots running around posting from it as well, may or may not be causing extra load
I've been seeing that error, and sometimes when I click on a post it sends me to an error page instead. Reloading seems to work, eventually.
Jerboa app is stable in the way that it just won't show you shit until it clears the error pages lol
Ya been getting errors and I'm using the world instance. I imagine it's server capacity and the amount of people posting, joining etc (which is a good thing if that's the case with people coming over)
Home of the sh.itjust.works instance.
