It's not clear which parts of Claude state are safe to sync and which you want to keep local to one machine. I'm doing something with syncthing trying to keep agent session history available and little bits of it keep breaking. I haven't looked at this new feature in atuin does it have a really good understanding of what is worth syncing?
One of the Atuin engineers here. Not sure wht your definition of safety is, but Atuin doesn't attempt anything special in terms of deciding what to sync. Pretty much everything is synced.
All your sessions are end-to-end encrypted so only your machines have access to your sessions! Happy to answer any other questions!
What is wrong with software engineers that we keep making really stupid basic mistakes like this? Sometimes I think programming should require licensing and regular testing.
We direly need to split things into a licensed engineering field which is necessary for working on security- and reliability-critical systems, and a generic unlicensed software developer field where people can screw around with their 1000 dependency JS frontends to their hearts' content. The two should not be conflated and yet so easily are.
Certification do exist for engineers, and various industries and governments impose their own certification programs on platforms and software before they’re authorised for use.
Each with varying degrees of trust. The outcome is never perfect, but that’s not their purpose.
Credentialism is not a solution, it will just get gamed too. Indian diploma mills and mega IT consultancies pump out thousands of "qualified" engineers every year.
Every hiring manager worth their salt has caught at least one completely incompetent applicant with a CV full of certifications.
One of the problems with cryptography implementations is that a bad one will be indistinguishable from a good one on the surface level. Totally broken crypto will superficially look and work as if it it works, and most people won't look deeply. This has been commented upon for years.
Testing doesn't even need to be that rigorous for humans, it's easy to spot someone who is lying about the depth of their experience with a 15 minute conversation.
For AI this will be impossible, however.
If you're talking about testing of code, well "tests can only prove the presence of bugs, not their absence"
University degrees are not the difference between an engineer and a developer, universities have churned out millions of people who don't care about programming and have no idea what they're doing, who are just following the script with as little effort as possible because they were told it was the easiest way to make a lot of money.
And how does this disprove their point? I don’t think its the lines of code you write that allow you to decide whether or not you should roll your own crypto…
I'm willing to bet the vast majority of students and professors at Stanford have consulted an "illegally obtained" textbook at some point. Either directly from Anna or second hand.
I'm getting a lot of mileage converting all my little VMs and containers over to NixOS. Entirely using AI, Claude Code is remarkably good at creating Nix flakes. The declarative OS is a good match for LLM generation of system specs. No side effects of commands to track, everything testable and reproducible by the agent. And NixOS itself works quite well. Most of the packages I need are there and if something's missing Claude doesn't seem to have any problem making it itself.
Stage 1 and 3 of that chain are shocking. I mean, yes, security is very hard, especially in a large codebase, but they look like actively made misguided choices.
Stage 1: one endpoint checks for the token header existence, not its content. From the writeup I'm guessing all the other endpoints do check the content, so why?
Stage 3: checks if the URL starts with http://127.0.0.1, not if the domain is 127.0.0.1, to expose an admin token. Ouch.
Once again proving that ads are an unacceptable security threat. All those sites now deploying ad-blocker blockers should assume liability for whatever ad software they force their readers to run.
I just switched to AVIF after several years of using WebP. Main reason for me is HDR support, but the smaller encoding is nice. Just beware of lossless AVIF, that's a trap.
In GIMP, when you try to save as a "lossless" AVIF, it will add a lossy colorspace conversion step (to 8 bit YCbCr) unless you specifically specify otherwise. And lossless AVIF always loses to lossless WEBP.
reply