Narretz

That's a DoS / memory consumption attack, so not as dangerous as the rest from today.

that's true. But even for some of the easiest cases some browsers don't support them. input[type=month] for example still has no custom UI in Firefox or Safari. And Chrome has had one for 14 years!

Where do you draw the line? Some SaaS acceptable? VPS? Bare metal? Or your own server in your own home?

It's not a question of gained ground. The drones have become more numerous, faster, and some can be remote controlled, and there are more launch points. Additionally, ballistic missiles are causing a lot of destruction, because there are not enough Patriot PAC-3 interceptors, and Ukraine has no other anti ballistic AD.

Sounds like it specifically does not apply to subscription usage.

Gonna be interesting for how long it stays available like this. It's a scraper's dream.

my guess is many people use nitter to do automatic scraping of Twitter for various projects, i.e. they can't believe they "have" to do it because so many people still use Twitter.

I'd say there's also oversight/supervision. Which was manual at the start with a human signing off on commands/incrementally built allow/block lists, and now seperate models evaluating commands and blocking them based on some parameters. This is the weakest model, but it'll evolve as well.

Iirc correctly Opus 4.7 had the same problem, safety filters were triggered way too easily at the beginning.

There a few benchmarks out there where all existing models have abysmal scores. So it's not actually a problem if Antrophic's older models are bad, especially if the jump to the newest model is huge, and the competition is also way below it.

They are now reporting that is a major incident:

> We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

> Cache entry Linux-pnpm-store-6f9233a50def742c09fde54f56553d6b449a535adf87d4083690539f49ae4da11 (1.1 GB) saved to GitHub Actions cache for TanStack/router, scope refs/heads/main — keyed to match what release.yml will look up on the next push to main

Imo I think this shouldn't have been possible, as in release should use its own cache and rebuild the rest fresh. It's one thing that the main <> fork boundary was breached, but imo the release process should have run fresh without any caches. Of course hindsight is 20/20.

--before doesn't save you globally, only min-release-age does, which is in npm since March iirc.

Dispatch and scheduled tasks have been available for a few weeks already, although with limitations.