Oh dear. Will make for an awkward thing to have on your resume.

"CSAM Ninja"

it does at a macroscopic level by making scraping expensive. If every "valid" page is scattered at random amongst a tarpit of recursive pages of nonsense, it becomes computationally and temporaly expensive to scrape a site for "good" data.

A single site doing this does nothing. But many sites doing this has a severe negative impact on the utility of AI scrapers - at least, until a countermeasure is developed.

This will solve nothing. Best case OP 'wins' ands the competent jerk becomes even more difficult, worst case OP 'loses' and loses any authority.

OP is being too nice. He is the team lead. His job is to lead, ands sometimes leaders have to be direct and harsh.

Sure, mate - whatever you need to tell yourself.

> I feel like complaining about Teams

Brother, there is not enough alcohol in the world.for this conversation.

I saw a post remarking that Microsoft had instituted a return-to-office policy

The jab being something to the effect of "imagine being the group that built a tool to help people work remotely and then it sucks so hard everyone has to come back into the office anyway"

A friend who works internally then remarked to me that apparently the person leading Microsoft's AI efforts cried and whined hard enough that his org was allowed to "use Slack instead"

Really the people I feel for are the MSN Messenger engineers. They built something beautiful nearly 30 years ago and watched Microsoft ruin it, kill it with another product they had already ruined (Skype) and then bury the whole lot by building that Electron monstrosity over their unmarked graves

Devops: The gun may only anger it so we keep a sledgehammer nearby in case

Alignment Researcher: Thermite is the safest way to be sure.

Management: Let's wait until James Hamilton's yacht makes landfall and then he'll fix it in 3 minutes.

Just put the printer precariously close to an open window on a high floor and threaten it with a performance review every once and a while.

because your competitors are probably using services that depend on AWS.

I'm sure they'll find some way to weasel out of this.

For DynamoDB, I'm not sure but I think its covered. https://aws.amazon.com/dynamodb/sla/. "An "Error" is any Request that returns a 500 or 503 error code, as described in DynamoDB". There were tons of 5XX errors. In addition, this calculation uses percentage of successful requests, so even partial degradation counts against the SLA.

From reading the EC2 SLA I don't think this is covered. https://aws.amazon.com/compute/sla/

The reason is the SLA says "For the Instance-Level SLA, your Single EC2 Instance has no external connectivity.". Instances that were already created kept working, so this isn't covered. The SLA doesn't cover creation of new instances.

It's not down time, it's degradation. No outage, just degradation of a fraction[0] of the resources.

[0] Fraction is ~ 1

This 100% seems to be what they're saying. I have not been able to get a single Airflow task to run since 7 hours ago. Being able to query Redshift only recently came back online. Despite this all their messaging is that the downtime was limited to some brief period early this morning and things have been "coming back online". Total lie, it's been completely down for the entire business day here on the east coast.

We continue to see early signs of progress!

It doesn't count. It's not downtime, it's unscheduled maintenance event.

If you aren’t making $10 for every dollar you pay Amazon you need to look at your business model.

The refund they give you isn’t going to dent lost revenue.

Check the terms of your contract. The public terms often only offer partial service credit refunds, if you ask for it, via a support request.

amazon's health page is widely enjoyed as a work of fiction. community reports on places like reddit are, actually, more reliable.

and by one I trust you mean a bottle.

Technically what they accomplished is a successful side channel attack.