indigovole

On's commitment to avoiding search clicks goes beyond their name.

Their logo deliberately looks more like 'qn' or 'nq' than 'on'. I _had_ a pair and couldn't remember or figure who made it for a while.

they did lock up their domain name, which must have taken some doing.

Even with his context-tracking mechanism, the gameplay failures sound like running out of context in the late game, especially the frequent failures of the "check for opponent win conditions every 20 moves." Wondering how much info about the game win state gets captured in the game digests, and how much he could improve the gameplay even with the MCP limitations by focusing there.

What kind of embedded WASM malware are we going to be defending against with this?

If he were not in favor of cutting rates, he would not now be a contender.

Any way to turn off the special effects?

Scoring is wrong. Using all 7 gets a 50 point bonus. Hit this on the very first rack.

must have something to do with paragraph breaks

It's a really interesting question.

I'm sure you could go back 40 years earlier and find programmers complaining about using FORTRAN and COBOL compilers instead writing the assembly by hand.

I think that the assembler->compiler transition is a better metaphor for the brain->brain+AI transition than Visual Studio's old-hat autocomplete etc.

After working with Cursor for a couple of hours, I had a bunch of code that was working according to my tests, but when I integrated it, I found that Claude had inferred a completely different protocol for interacting with data structure than the rest of my code was using. Yeah, write better tests... but I then found that I did not really understand most of the code Claude had written, even though I'd approved every change on a granular level. Worked manually through an solid hour of wtf before I figured out the root cause, then Clauded my way through the fix.

I can picture an assembly developer having a similar experience trying to figure out why the compiler generated _this_ instead of _that_ in the decade where every byte of memory mattered.

Having lived through the dumb editor->IDE transition, though, I _never_ had anything like that experience of not understanding what I'd done in hours 1 and 2 at the very beginning of hour 3.

This amounts to a claim of fair use, since copying occurs. Pretty disingenuous of them to make a claim that an individual user would make.

The outcome of a fair use claim by one of the world's largest corporations to ingest wholesale an entire corpus and use it for commercial purposes is probably not the same as one by an individual person who wanted to watch a movie.

It's not the same use, and is much more likely to be found unfair.

And yet, that is literally all they are asking to do.

Old enough article that we can be sure that its recommendations were not implemented.

It looks excellent, except for the terrible choice of red and green to distinguish parking/no-parking times. AWAK, the different zones would be nearly indistinguishable to around 5% of humans, almost but not entirely men.

let alone the satisfaction of plunking in 10 of them, one after another, muscling them up from my Weimar®-brand currency wheelbarrow.

You can't just dismiss a vuln as, "for the love of god, don't expose XXX to the internet."

It's not great to have an unauthenticated RCE on a machine that is _not_ accessible from the internet, either. Inside-the-network RCE is useful for lateral movement and privilege escalation. RCE that you can find by looking for an open UDP port - instead of a vuln scan on 80/443 - is even better.

Initial entry is an important vuln abuse case, but not the _only_ abuse case.