My hope is it means it assigns coded identifiers and the key remains local. When the document returns, the identifiers can be restored. So the PII itself never leaves the premises.
Interestingly, the touch screen of the 2-in-1 worked really well! I often relied on the touch screen to do light web browsing when the trackpad was acting up.
Similar experience and timeline with codex, but tried it last week and it's gotten much better in the interim. Codex with 5.2 does a good job at catching (numerical) bugs that Opus misses. I've been comparing them and there's not a clear winner, GPT 5.2 misses things Opus finds and vice versa. But claude-code is still a much better experience and continues to just keep getting better but codex is following, just a few months behind.
Extremely red states don't care. They won't flip at all. And none of the districts are even remotely competitive. Only the primaries matter.
A cursory look says Wyoming has a population of ~580k and ~340k registered voters. The article says Wyoming has 46k people on ACA. Republicans win landslides in Wyoming (40%-50% margins) and 46k people is 12% of voters max (likely closer to ~4% at risk).
Thanks. So, the upside is saving money, at the expense of alienating poorer voters in (this example) a state where their majority is so big they don't care.
When people don’t have access reliable healthcare, they tend to use even more expensive (for society) options like emergency rooms and grey/black market. People who become disabled or die from lack of healthcare don’t tend to pay much in the way of taxes.
To my knowledge, legal protections against unpaid emergency room bills not leading to credit harm or debt collection exist only in California and New York. Also, emergency rooms are very limited in the care they dispense - they don't dispense chemotherapies.
> Individuals who were unemployed made roughly 2.5 times as many preventable emergency care visits as those who had a job (Figure 3).
> Lack of health insurance coverage was another factor that appeared to play a role in preventable ER visits.
> According to the study, individuals without health insurance had more preventable visits to the ER than those with health insurance (Figure 4).
> This suggests that uninsured individuals may not seek primary care for chronic conditions ahead of an urgent episode or they may rely on emergency rooms for general health care needs.
Congress is likely to flip for many reasons. This is just a drop in the bucket. Places like Wyoming aren't on the table. Republicans are in a jam because nobody can challenge Trump without being primaried.
The real problem for Trump and Republicans is they do great when Trump himself is actually on the ticket. That's his power. Unfortunately for him, he will never be on a ticket ever again. But he still holds considerable influence over primary voters. Primary voters don't win marginal States. Trump is a paper tiger but because of his control over primaries Republicans are trapped.
Maybe instead Microsoft could allow Windows 11 to install and run on machines that are otherwise capable and just flash red screens at you all the time where otherwise ads would show up that constantly nag that "THIS COMPUTER IS FUCKING INSECURE!" or something. It would be equally as annoying but I'm sure running latest Windows 11 but with TPM 1.0 instead of TPM 2.0 will be more secure than running Windows 10 without bug fixes and security patches.
(But my understanding is there were other things like bumping minimum supported instruction sets that happened to mismatch a few CPUs that support the newer instruction sets but were shipped with chipsets using the older TPM)
Same here. So far everything I have found to help LLMs is just good practice generally: automated tests, documentation, clear issue descriptions, a neat commit history, well featured code etc.
I sort of disagree. It's somewhat like having hypercard again. You can build fun UI things and make machines do what you want them to do. You can care about the parts you want to care about and not sweat about the parts you don't want to learn in detail (yet). And Claude and codex make great guides/Sherpas.
There are just too many parts involved to do anything. For example today I built a simple data collection app to use on my phone that involves inventories with photos for a tedious workflow I have to do. I knew what I wanted but didn't know how to even choose which tools to bother learn. And just even trying things to see if an approach works or not without spending hours learning one thing or another or wading through the hell of web search is really great.
Things I learned today that I figure everyone else must know: if you want to take a photo from a webapp I guess you need https. So I decided to try mTLS (knew it existed but never had the time) so asked Claude to write me a short tutorial about setting it up, creating keys, importing them (including a cool single line trick of spinning up a python server and downloading the keys on my phone rather than find a USB stick or whatever). And then helping me figure out a path out of the suffering of Chrome and Firefox hating self-signed CA. But at least I figured out how to make Firefox happy. But it would insist on prompting me for the certificate for every htmx request. But chatting with Claude I learn caddy is pretty cool, it's go. Claude suggests an auth boxcar when I balk at adding auth and user management to my app because I think the webserver should handle all this shit (wtf is a boxcar? Claude clues me in). I tell Claude to use go or rust to build the boxcar because Jesus Christ "yay" build another service just to get a good damn customized CRUD app on my phone that can take a picture. Claude picks go which is fine by me. (Incidentally I can't write go, but I can read it and it's on my "to be learned" agenda and go seems safer than a pile of python for this simple thing) The boxcar was fine but Claude was struggling with getting headers to work in the caddy config. So while Claude is working on that I do a quick Google about whether caddy can have extensions because there has to be a better way to "if someone has authenticated successfully, give them a cookie that will last an hour so they don't have to mash the confirm about using the certificate for every goddamn htmx request" than spin up a web service. Interrupt Claude and suggest an extension instead of a boxcar. Claude's on board so we ditch the boxcar. Have Claude and codex evaluate the extension for security. They find important issues about things a jerk might do, fix them. So successful mTLS connections transition to session cookies. So my dumb CRUD tool doesn't have to worry about auth. Which it didn't have to do anyway except browsers say so etc because my phone is literally only able to access the server via VPN anyway.
Other things I have learned today that only wasted 5min of Claude's time rather than hours of mine: Firefox camera access can't control flash, focus or zoom. So call out to the native app instead.
This is all quite fun and the tool I'm building is going to really make my own life better.
>only wasted 5min of Claude's time rather than hours of mine
I mean will you (we) retain all that it did after a few months go by? You may say we don't need to, but that sounds a little shallow given we're both on HN. Do you remember Gatsby's criticism of "Summer People"?
I don't even remember things I did two years ago unless I leave good breadcrumbs and documentation. I don't think it's particularly worse than pulling in some dependency or framework from GitHub that will be completely different next year anyway. And Google's prone to change anything in Android anyway. Mobile or web seems like a foundation of quicksand, it's not anything I care about. The real takeaway is I can be productive without wasting my time on all the damn churn by just-in-time learning aided by these tools.
I'm pretty sure I will remember how easy and correct it was to modify Caddy vs the months of putzing around building Rube Goldberg constellations of services crap that I did last year for a different thing and that even Claude wanted to do. I've done the whole wading through outdated blog posts and trying to read documentation on other projects that I was doing. Learning five different projects and having to maintain seven services running in docker just so that I can use a tool to capture photos and store them in a webapp that can only be used if connected to my own VPN is insane and it's why I am not a web developer. I will 100% remember what 200 lines of golang does after looking at it again. The 1000 lines of JavaScript that were and backend auth crap that no longer exists: good riddance.
And no I don't trust my memory about what Gatsby said about Summer people without looking it up. I read Gatsby 30 years ago.
Probably a human could put a copyright on a prompt (that would be the "source" and the LLM would be a compiler or interpreter) and the generated code would be derivative of the prompt and any inputs.
It would probably get into whether the prompt itself is considered copyrightable. There is some threshold for that since I have heard some patches are considered insignificant and uncopyrightable.
This sort of translation is probably well trodden the status of something like "Translate Jules Verne's 'Vingt Mille Lieues sous Les Mers' to English" has plenty of predicates.
In terms of images, this seems more like a translation. "Translate this photo into the style of George Seurat". Whether George Seurat would have a copyright claim is not as clear but it seems pretty intuitive that the result is a derivative of the photo.
reply