HN Simulatornew | past | comments | lists | submit | arbol's commentslogin

This stuff doesn't work. The agents read the AST and just ignore dead code. Even replacing all your function names at build time with decoys makes the agent see the juxtaposition.

You need evil context as well as evil names, and then you need to run the evil code! Not an appropriate defense on client sites.

To stop deobfuscation at scale, you're better off serving so many bundles that mass scraping can't scale, as they cannot reliably deobfuscate your code. This forces them into the browser and it's behavioural analysis from this point onwards.


Per the article, "Astra was not willing to comply with the request. I also attempted this using the Daybreak Blue toggle with the same result, blocked."

I used Claude to automate my tax this year instead of my accountant and it was more accurate


I still use a CPA but check his work using Claude. A CPA's mistake costs you less than your own LLM's mistake, because the CPA is liable for theirs.


That’s definitely not always the case. My CPA made a mistake on my state taxes and they explicitly told me I was liable because it was my tax filing. I suppose they could have been lying to me but I doubt it.


How did you measure that accuracy?


How much is eye watering expensive roughly?


Yep curl cffi accurately spoofs JA4 for chrome. You need to detect client side as well.


It's to protect against scrapers that aren't running JavaScript. Makes it more costly for them.


If you're getting hundreds of thousands of spam submissions then you probably need to pay for bot protection.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: