Has anyone else been getting a lot more errors on sh.itjust.works recently? Could the server be overloaded?
I've been getting a lot of these messages lately:
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
So I decided to look at the network requests in the browser console. After all, what JSON data was it trying and failing to parse?
Well, turns out that it was pretty much always:
Timeout occurred while waiting for a slot to become available
I don't do a lot of backend work, but I suspect that the lack of slots might be referring to the server running out of resources to process all of the ongoing user activity concurrently. Could we be running into scaling issues?
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.
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.
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.
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)