3 ms·
As TFA points out, a major change is that bot traffic now comes from honest users via their LLM sessions, so you don't even necessarily want to block automated
by hombre_fatal 4mo ago
As TFA points out, a major change is that bot traffic now comes from honest users via their LLM sessions, so you don't even necessarily want to block automated bots anymore.
The game is shifting to a better ideal: how do you design a service knowing that any user/request might be automated?
Especially in place of the historical, easy solution/hack where you have some sort of gate that, once passed, puts the user in some trusted low-scrutiny tier, like a forum's registration page.
It's a similar question to designing a system so that it's resilient to account take-overs. (i.e. The user was a trusted human until now, and now it's a spammer)
Example: on a forum, run new posts through an LLM to classify it as spam which is a magic solution we always wish we had (remember akismet?) but was too rudimentary.
- wildzzz 4mo agoYou use API tokens for things intended to be machine to machine communication and captchas for things intended to be filled out by humans. Not every site or service wants automated input, even if it's being directed by a human. I dont want forums like HN just filled with a bunch of agents talking to eachother, where's the human connection?
- hombre_fatal 4mo agoCaptchas are dead or will be dead shortly. The question is what do you do in a world where you can't tell human from machine, or when there's now honest machine traffic that acts on behalf of honest users. > You use API tokens for things intended to be machine to machine communication Who uses it and why? Not for websites where the agent is making read-only web requests for the user. And now that agents have generalized abilities/intelligence, there's fewer and fewer incentives to use APIs since the arms race to keep humans and machines segregated is ended/ending. We need new ideas and paradigms, not cling on to old ones that won't work.