Of all of the issues in this world, and you choose to focus on a single boring line about a boring detail in a light and whimsical article about, let me check... street signs.

Oooga booga! Mamdani! Oh no! The politics of it! Help!

Write a letter to the fucking editor if it ruffles your feathers that much. I'm sure they'll be waiting with bated breath to hear your objection.

Give it up, man. Go touch some grass.

> Oooga booga! Mamdani! Oh no! The politics of it! Help!

Mature. I'm sure you'd react similarly if the article talked about a politician you don't like.

The fact that it's a light and whimsical article about street signs is exactly the point. The political content is completely unnecessary to the story, and exists only because the mayor had a PR event.

And for this one when insurance companies are forming syndicates because their underwriting becomes greater than any one company, it just sounds frightening, the sound this thing is going to make when it finally pops.

We lost a mirror in n-gate that was reflecting some of the ugly faces here back at some people that really needed it.

Did the product manager look at this before it was released? We have a lot of work to do here! We need to create a sprint for optimizing it, otherwise no one will like it. Be sure to put the texel fetches in a user story. This should be top priority. Lots of users are very angry.

/s

Chill out and have some fun

50,000 requests in the span of ... 21 days? It might be interesting if it were 50 million in those 21 days (even then, 27 RPS is ... nothing). Drop a report to AWS T&S, block, drop, reject, and move on. This is like less than background noise at this point.

Edit: tamping down a bit of my prickliness because it looks like this individual is a relative newcomer to running internet-facing services. This is actually a pretty good intro to that: the place as a whole is a cesspool and any conceivable “attack”, scan, probe, pentest is, has, or will be happening at all times. Some you can mitigate yourself, others you’ll need to bring in a specialist service (see DDoS sinks and mitigation services, for example) or contact someone’s abuse address, others you just have to ignore because it’s just not directed at you personally, or just not worth more than three seconds’ thought beyond a firewall rule. This is the latter. Maybe interesting if this is the first time you’re seeing something like this, but for more grizzled operators like myself, it doesn’t even register as notable anymore.

> I don't understand why these companies automatically get a pass.

Because these companies have lots of dollars and if I treat them sympathetically enough I might get some of their dollars too.

But my local is a 8xH100, you insensitive clod!

Dozens and dozens of times. And having the bigger pipe has always saved it, along with the supporting infrastructure to churn through that traffic.

> But again, those sort of attacks seem to happen seldom

[citation needed] and direct experience suggests otherwise. The wider internet is a cesspool and you never know the inanity that will spur a bored, annoyed script kiddie with some booter credits to take it out on the local cake shop, like another commenter put it.

I think he was telling something called a joke. It's funny because S3 is expensive and they just got some money.

Give me a break. Sympathy? For microsoft? That might have flown when github was like seven people, but they have nearly unlimited resources to make it better. They're just choosing not to. Let's talk contracts and money before we pull the sympathy card.

I used to be on-call in a high-traffic environment where single customers pushed more bits than entire nations. I chose the role. I didn't want people's sympathy, if anything, I wanted them to complain to management.

If it gets too bad they can quit. Maybe that would be for the best, just wear the thing down until it outright fails and no one wants to touch it. One less bullshit service sucking all of the oxygen out.