My experience has been that the "cost per task" estimate wildly underestimates the cost of top models on most real work, because the tasks (as I understand it) tend to be isolated bits of problem solving or code generation, which rewards writing code that works the first time and not generating too many reasoning tokens. Sol is great for both. However, a lot of real work involves tracking down bugs, working through tests, examining many parts of a codebase, refactoring... even with subagents and good tool use this tends to bloat context before the problem gets solved. Deepseek's absurdly low cache price really shines in these instances, but even GLM 5.3 Flash easily beats the top models on price in real world usage. Maybe that's different if you factor in subscriptions.
Yep, any time you're asked to set up a passkey it feels like Russian Roulette with future access to that account. A year or so ago, a site I relied on started enforcing biometric passkey enrollment. Without thinking about it I logged into the site on my phone and enrolled there, but unfortunately (a) that meant it didn't get registered as an "other device" in the internal system, and (b) the site didn't work correctly on mobile devices (legacy system). So logging in on a desktop would then demand that I activate the passkey, but of course the passkey was on the phone. No way to access it, and the site didn't offer me the QR code / bluetooth method. I don't remember exactly why, but it just didn't work - probably had something to do with it not liking Firefox on Linux or something.
And to add insult to injury, it wasn't even a single factor login the way passkey advocates promise. The site still demanded a normal password to log in! It was actually 3 factor authentication; something I know (the password), something I have (the passkey), something I am (the biometric).
This wasn't some random website that didn't matter made by nobodies. It was a US government website for managing grant money.
> Yep, any time you're asked to set up a passkey it feels like Russian Roulette with future access to that account.
We rolled out passkeys a couple of years ago (I work for an auth/CIAM provider). This was before most passkeys were synced (which gives me the heebie jeebies--that's a valuable set of private keys to be shipping around).
We built passkeys to be an alternate login method, not a primary one, for that exact reason.
Meanwhile, Wikipedia has a policy that says screenshots of applications have to be "as small a version as possible" in order to meet the fair use exception for presentation of copyright work. I can only imagine an exact clone of the interface could be similarly ruled to infringe on Adobe's intellectual property.
Copyright is so flawed... This would mean an hommage is a breach of intellectual property in general, even if you paint it completely differently (say watercolor vs oil)
> A surprising number of people in the state would not consider 1 mile 'walkable'.
In a surprising number of American cities, 1 mile is not walkable, simply because no one thought to put in a sidewalk or have adequate protection for pedestrians. That goes double for places like Lansing, where the sidewalks that are there are often icy during the winter.
Well, it wasn’t where I was as I walked my miles daily. But it was a breath of fresh air compared to Haslett. Haslett reminded me that the walkability of REO town to the Michigan State Capitol seems more like a coincidence than intentional urban planning. Because Haslett often lacked any sidewalks.
I remember one time walking to the Lidl for a 6 mile roundtrip. I think it was the first time when I realized why Americans don’t walk. That walk was one bad experience while nothing bad was happening. For contrast: I live near Amsterdam my whole life.
I live about 90 minutes north of Lansing in a town at about the same latitude as Toronto. Weather-wise, the problem isn't the ice. It's the snow accumulation, the cold. For about 3 months out of the year, you're lucky if it's at -7 C or higher.
It's also just that nothing is structured for it. Homes are built relatively far away from businesses and shops due to zoning, and stroads are the common way to get between the two. And where the stroads end, rural roads begin. It's structured not to be walkable not just at the large city level, but at the small city and town level, too. Our infrastructure is dictated by what the people in the 1940s thought, and they were extremely wrong about a great many things.
Oh cool, someone talking about the really weird bug that I've never seen reported elsewhere. Seems like an issue where certain versions of Unity (to name one engine) doesn't like it when your actual game controller is the second joystick it detects. Not really Keychron's fault or Linux's fault, just a weird engine quirk.
Anyway, if someone finds this by searching, at least on Arch it's as simple as adding a custom hwdb entry at /etc/udev/hwdb.d/61-input-id-local.hwdb:
Why did Anthropic settle with authors for 1.5 billion then? Surely their lawyers must have decided there's a pretty good chance of judges ultimately deciding that it is copyright infringement?
What does that matter? They were sued and the group suing them accepted at $1.5B settlement instead of something theoretically much larger and precedent-setting.
Because the judge ruled that using the books for training was "fair use". The issue was Anthropic downloading and storing pirated content and there is quite a bit of precedent regarding that already...
Because the point of the test is to see what the agentic swarm approach is capable of. If your test assumes that a version of the thing you are trying to build is available in the training data, or can't determine if it matters whether the thing you're building is in the training data, then it's not a very useful test. Most of the time when you consider agentic approaches, you're not trying to rebuild something the agents involved are trained on.
reply