I use OpenFreeMap for a personal site (basically only for me) and I noticed some tiles dropping yesterday-ish. I figured it would be fixed soon. But I had no idea it was such an interesting cause!
it's embarrassing how you keep accusing wplace of being rife with "script kiddies" who supposedly keep clearing their cookies and/or rotating their IP address to draw more, when you haven't even looked at it long enough to realise that you need to log in with a google account to draw. no curiosity for the thing you wrote nearly a thousand words about. no investigation. they're just incompetent in the simplest way you can imagine
For context: You get more than just 1 pixel to place, and can store up to like 50. The more you draw the more you can store - and you recharge 1 pixel every 30 seconds. It's not like the old r/place on reddit.
well the thing is even if 99% of people using it are legitimate good-faith creative users, the bad-faith "script kiddies" are very much the ones generating so much traffic since they generate so many more requests-per-timeframe than a regular user
Extremely interesting insight, and surely no one expected the word of mouth for Wplace to explode into 2 million users, well even if we consider the art bots.
Anyways I've never been interested in "what the hell do we use to display tiled maps" until now, so that's really great. And holy cow, the people Cloudflare are really nice.
Would shipping a shared service worker that had aggressive client-side caching (even preventing any "last-modified" checks from hitting the servers) have helped, or would you have expected that it was fresh browser instances each time? If lots of people were scripting it, maybe the code to do it was public somewhere and could have had a PR to save the bandwidth on the client-side 😄
How did you end up solving the "too many files" issue? Just increase the OS file limit, or something else in code?
Non-logged-in guest users (myself included) mostly visit wplace not to draw, but just to see all the artwork, which literally spans the entire globe, both zoomed in and zoomed out. That explains the high tile requests per user. I wonder if that 2 million figure refers only to registered accounts, excluding guest viewers without an account.
Believe it or not, almost entirely all of those users are legitimate. It was a worldwide phenomenon for those few days among teenagers and young adults.
Interesting!
I use OpenFreeMap for a personal site (basically only for me) and I noticed some tiles dropping yesterday-ish. I figured it would be fixed soon. But I had no idea it was such an interesting cause!
it's embarrassing how you keep accusing wplace of being rife with "script kiddies" who supposedly keep clearing their cookies and/or rotating their IP address to draw more, when you haven't even looked at it long enough to realise that you need to log in with a google account to draw. no curiosity for the thing you wrote nearly a thousand words about. no investigation. they're just incompetent in the simplest way you can imagine
My guess is, you probably have bigger worries when 2 billion requests flood in...
But yeah quite sad to see it being labeled solely as that. It's a much more creative canvas, rather than simple "script kiddies".
For context: You get more than just 1 pixel to place, and can store up to like 50. The more you draw the more you can store - and you recharge 1 pixel every 30 seconds. It's not like the old r/place on reddit.
well the thing is even if 99% of people using it are legitimate good-faith creative users, the bad-faith "script kiddies" are very much the ones generating so much traffic since they generate so many more requests-per-timeframe than a regular user
Extremely interesting insight, and surely no one expected the word of mouth for Wplace to explode into 2 million users, well even if we consider the art bots.
Anyways I've never been interested in "what the hell do we use to display tiled maps" until now, so that's really great. And holy cow, the people Cloudflare are really nice.
What app is that to do the natural language calculation (for the 100 million requests thing)
https://soulver.app/
thanks!
Would shipping a shared service worker that had aggressive client-side caching (even preventing any "last-modified" checks from hitting the servers) have helped, or would you have expected that it was fresh browser instances each time? If lots of people were scripting it, maybe the code to do it was public somewhere and could have had a PR to save the bandwidth on the client-side 😄
How did you end up solving the "too many files" issue? Just increase the OS file limit, or something else in code?
I don't know what Wplace's users were doing, but I helped them set up the self-hosted server and now they are running on their own infrastructure.
If they were launching new Chromium instances then no amount of caching would have helped.
I haven't solved that issue yet, I've written my questions here:
https://community.nginx.org/t/too-many-open-files-at-1000-req-sec/5796
I believe it's the combination of multi_accept + wrong limits, but I'm waiting for the experts' opinions.
Guess you could write a Worker that runs on a schedule and uses CF API to check top referers and add/remove any above X rps to the page rules
Yes, exactly, I was thinking something like that.
Non-logged-in guest users (myself included) mostly visit wplace not to draw, but just to see all the artwork, which literally spans the entire globe, both zoomed in and zoomed out. That explains the high tile requests per user. I wonder if that 2 million figure refers only to registered accounts, excluding guest viewers without an account.
Believe it or not, almost entirely all of those users are legitimate. It was a worldwide phenomenon for those few days among teenagers and young adults.
Hi. Thanks for being chill and transparent about this, it's appreciated.
Congrats on surviving that load!
Note that the 206 status is normally.still successful. It's the code for a successful response to a Range request.