waynenilsen

> bot detectors made it extremely difficult

i am looking forward to when we can put this behind us, it is still a major issue

ASIC inference is clearly the future just as ASIC bitcoin mining was

i believe agent native sites will stand up and the incumbents will be forced to adapt

such as agent native shopping platforms whereby a human will bring you something from walmart or what not could spring up and disrupt your instacart of the world

this of course is just one simple example, when it works better for the clawdbot or whatever comes next what are the users going to choose they'll say 'get me some apples from walmart using instacartforbots' because they know the agent success rate will be higher

ah yes thank you very much that did work

still not great in my opinion sadly i think this will likely get worse and perhaps never get better

commit messages as marketing materials and 'kpi's is an anti-pattern i would have preferred to avoid

i can see a new token efficient mirror web possibly emerging using content type headers on the request side

forms, PRG, semantic HTML and no js needed

Frontend QA is the final frontier, good luck, you are over the target.

The amount of manual QA I am currently subjected to is simultaneously infuriating and hilarious. The foundation models are up to the task but we need new abstractions and layers to correctly fix it. This will all go the way of the dodo in 12 months but it'll be useful in the meantime.

agent-browser helped a lot over playwright but doesn't completely close the gap.

> Information leakage may also be occurring via PDF comments or orphaned objects inside compressed object streams, as I discovered above.

hopefully someone is independently archiving all documents

my understanding is that some are being removed

i think when someone makes the cli like this they're going to win

$ phone call bill

ok call_id=3f2a

$ phone status 3f2a

dialing

$ phone status 3f2a

answered

bill: hello

$ phone say 3f2a "hey, quick question"

ok

amazing now do the same for voice and sms!

i see what you are saying now, i have actually started doing my own dockerfiles so everything is in one container it works reasonably well actually eg you install postgres redis x y and z on the same thing the agent is running on then you can start fresh anytime then all of your stuff is on localhost