I mean this as genuinely non-snarkily as possible: I have been literally building my own personal productivity and workflow tools that could do things as shown.
Is this now a violation of the Claude terms of service that can get me banned from claude-code for me to continue work on these things?
I meant OEMs rushing the gun on new features that aren't fully baked. That probably does add support burden. (I don't know if it happens anymore but it used to be a problem on the OEM forks)
They should at least be shipping monthly updates with the months security updates. Well some months have not had any since Google is now trying to batch them to be quarterly because OEMs couldn't keep up with monthly security fixes.
I think this is one of the reasons I prefer claude-code and codex. All the files are on my disks and if claude or codex were to disappear nothing is lost.
I agree. For me it's annoying because everything it generates is too tailored to the first stuff I started chatting with it about. I have multiple responsibilities and I haven't been able to get it to compartmentalize. When I'm wearing my "radiology research" support hat it assumes I'm also wearing my "MRI physics" hat and to weaves everything for MRI. It's really annoying.
You asking how reductions in protections related to processed food (that already allow ultra processed foods) will affect safety when the new advice is to eat "real food" and seems to emphasize items that are pretty easy to confirm visually?
(I mean besides the fact that the FDA came into existence due to things like selling watered down white paint as "milk")
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.
reply