Or, if it’s just a few bad actors, block based on JA4/JA3 fingerprint?
OpenFreeMap survived 100k requests per second
11–20 of 140 posts
Re: OpenFreeMap survived 100k requests per second
#12> I believe what is happening is that those images are being drawn by some script-kiddies. Oh absolutely not. I've seen so many autistic people literally just nolifing and also collaborating on huge arts on wplace. It is absolutely not just script kiddies. > 3 billion requests / 2 million users is an average of 1,500 req/user. A normal user might make 10-20 requests when loading a map, so these are extremely high, sc…
Re: OpenFreeMap survived 100k requests per second
#13The article mentions Cloudflare, so how much of this was cached by them?
Re: OpenFreeMap survived 100k requests per second
#14Limiting by referrer seems strange — if you know a normal user makes 10-20 requests (let’s assume per minute), can’t you just rate limit requests to 100 requests per minute per IP (5x the average load) and still block the majority of these cases? Or, if it’s just a few bad actors, block based on JA4/JA3 fingerprint?
I think referer based limits are better, this way I can ask high users to please choose self-hosting instead of the public instance.
Re: OpenFreeMap survived 100k requests per second
#15>Nice idea, interesting project, next time please contact me before. It's impossible to predict that one's project may go viral. >As a single user, you broke the service for everyone. Or you did by not having a high enough fd limit. Blaming sites when using it too much when you advertise there is no limit is not cool. It's not like wplace themselves were maliciously hammering the API.
Show us what you have done.
Re: OpenFreeMap survived 100k requests per second
#16Earlier quoted context omitted.
Do you even read the article?
Are you new? Nobody actually reads the articles.
Re: OpenFreeMap survived 100k requests per second
#17Re: OpenFreeMap survived 100k requests per second
#18>Nice idea, interesting project, next time please contact me before. It's impossible to predict that one's project may go viral. >As a single user, you broke the service for everyone. Or you did by not having a high enough fd limit. Blaming sites when using it too much when you advertise there is no limit is not cool. It's not like wplace themselves were maliciously hammering the API.
Re: OpenFreeMap survived 100k requests per second
#19>Nice idea, interesting project, next time please contact me before. It's impossible to predict that one's project may go viral. >As a single user, you broke the service for everyone. Or you did by not having a high enough fd limit. Blaming sites when using it too much when you advertise there is no limit is not cool. It's not like wplace themselves were maliciously hammering the API.
Re: OpenFreeMap survived 100k requests per second
#20>Nice idea, interesting project, next time please contact me before. It's impossible to predict that one's project may go viral. >As a single user, you broke the service for everyone. Or you did by not having a high enough fd limit. Blaming sites when using it too much when you advertise there is no limit is not cool. It's not like wplace themselves were maliciously hammering the API.
You are so entitled... Because of you most nice things have "no limits but...". Not cool stress testing someone's infrastructure. Not cool. The author of this post is more than understanding, tried to fix it and offered a solution even after blocking them. On a free service. Show us what you have done.
That's how agreements work. If someone says they will sell a hamburger for $5, and another person pays $5 for a hamburger, then they are entitled to a hamburger.
>On a free service.
It's up to the owner to price the service. Being overwhelmed by traffic when there are no limits is not a problem limited only to free services.