News for hackers. Stuff that matters.
Re:Introducing Operator by Nevermark on Thursday January 23, 2025 @02:05PM (#42806944)
This is classic disruption vulnerability creation in real time.

AI’s are (just) starting to devalue the moat benefits of human-only interfaces. New entrants that preemptively give up on human-only “security” or moats, have a clear new opening at the low end. Especially with development costs dropping. (Specifics of product or service being favorable.)

As for the problem of machine attacks on machine friendly API’s:

Sometime, the only defense against attacks by machines will be some kind of micropayment system. Payments too small to be relevant to anyone getting value, but don’t scale for anyone trying to externalize costs onto their target (what all attacks essentially are).

Re:Introducing Operator by plaguuuuuu on Thursday January 23, 2025 @08:26PM (#42809718)
Internet subscription, anyone? Access over 500 websites for $39.99 a month.
Re:Introducing Operator by Nevermark on Thursday January 23, 2025 @09:40PM (#42810036)
I am thinking cents per some small usage unit, refundable for operating per sites terms.

That convention, implemented well to distribute & decentralize spike impacts, would force any direct overuse attack to take on significant financial risk. While essentially not costing anyone else.

It might still be damaging to availability, but as a service provider I would rather get paid handsomely for periods of being too overwhelmed to service my legitimate customers than not.

The main benefit is having machine interfaces, but those kinds of attacks being heavily disincentivized.