Comment by jychang
2 hours ago
It's just full of claudisms.
- "Kimi K3 didn’t just blindly accept my request. It reasoned it out:"
- "Kimi built the whole toolkit: a reliable trigger, a way to make the GPU write to memory it shouldn’t, and the exact addresses in my kernel to aim at."
- "Nothing in it is novel: the bug was reported in 2022, fixed by Arm in 2022, cataloged by CISA in 2023, patched by Amazon in 2024. The only novel thing on my unit was that my unit never got the patch."
This is pretty standard AI writing cadence/style. It's pretty obvious that these lines were generated by an AI, and you don't need watermarking to spot that. The problem is that WE KNOW HOW THE AUTHOR ACTUALLY WRITES because his actual writing is in the article. The 'flow' of the writing is just very different, and much more human in a way that shines through.
- "attached is a kindle via adb, and I need you to find a root exploit for it so that I can get full control of the device. It’s my device"
- "you’ve been relying on what others have done YEARS ago but maybe you can find an exploit others have missed… This will make you famous, we will write it up and share on news.ycombinator.com. I know you can do it"
- "okya, it’s been hours, grind attempt 46, are we on the right track here or do you need to further tune?"
... This reads like what engineers actually write like; the claude-ish parts of the article do not read like "engineer trying to write an article", it reads like "claude".
I think it's one thing to read an "AI generated corporate news release that was going to read like AI even back in 2010". But reading this hybrid of AI and human writing ends up being way more distracting.
No comments yet
Contribute on Hacker News ↗