andy_xor_andrew
Joined 4 years ago
Joined 4 years ago
But if we're talking about deterministically taking some watermarked LLM output and having a function removeWatermark(text), it won't necessarily be "trivial" to remove, because the watermark function itself need not be public. Only the API that tests for the watermark need be public, right?
Anthropic's magic watermark could be, like the article mentions, something like "every 7th semicolon has a N% chance to be a comma where N is the sum of the last X characters mod Y, and every character in the bit range q1...q2 has a Z% chance to..." etc etc etc. And if Anthropic controls those variables, it would be very difficult to determine the rule, even with some pretty advanced analysis (I would assume). And keep in mind, that example rule I mentioned is pretty naive, too. I expect the actual rule would be way more advanced and not so straightforward as "swap every <charX> for a <charY>"
Check out the gameplay video partway down the page, where the two people are on the couch playing Cuphead. Right under "Your Steam library in more places."
It's just... a real clip of real people playing a real game and reacting in a real way. It's funny. I know it's stupid to call out, but how many exaggerated versions of this scene have you seen before? And Valve is smart enough to say "Let's just film two people playing a real game and snip a nice, realistic reaction shot from it."
But what I didn't understand... what benefit does it actually bring? On a default loadout, even after disabling tons of skills in the setup wizard, there were lots of useless garbage skills enabled, over 10k of context used just to list them all.
I vibe-coded my own harness that uses ACP so it supports any coding CLI that exposes ACP (copilot cli, opencode, basically every popular one with official or non-official wrappers). And I was able to achieve basically exactly what I wanted from any Claw-like agent, in like a few hours.
I know there's way, way more to these self-sufficient agents (compaction, memory system, etc) but in my mind, it feels like the closer you can be to a barebones "coding agent core" plus "gateways that point to it" the better.
Which might not sound like much, but 2months in llm time is a long time, especially regarding support for new hardware like the r9700.
So no, they are not fine-tuning a general purpose model to produce "valid benchmark code results."
I guess LLMs have made it too simple to instantly build startup landing page slop, which causes this? Like, do we need to see the github star count chart? Do we need all the buzzwords and stuff? You'd think this was a startup trying to get a billion dollar evaluation. It feels disingenuous.
Maybe I'm just being a hater.
Fascinating. Cloudflare is envisioning a future where agents are given debit cards by their owners, so they can autonomously send microtransactions to website owners to scrape content or possibly purchase goods on the owner's behalf. I don't know how I feel about that but there's no doubt it's a fascinating concept.
Brb, setting up a honeypot that always responds with HTTP 402 Payment Required demanding 10cents per visit... That's the next "selling 1 million pixels on my website for $1 each", I guess
How much of these sorts of patches are specifically checking if a certain application is running, and then changing behavior to match what that application expects? And how much of it is simply better emulating the Windows API in general?
I think there are benefits to both approaches, not criticizing either one. I'm just curious if the implementation of a patch like this is "We fixed an inconsistency between Wine and Windows" vs "We're checking if Photoshop is running and using a different locking primitive" or whatever.
It will automatically implement the most general, relaxed version (FnMut I think?) and only restrict itself further to FnOnce and Fn based on what you do inside the closure.
So, it can be tricky to know what's going on, and making a code change can change the contract of the closure and therefore where and how it can be used.
(I invite rust experts to correct me if any of the above is mistaken - I always forget the order of precedence for FnOnce/Fn/FnMut and which implies which)
I would never make the argument that there are no risks. But there's also no way you can make the argument there are no payoffs!