Just because someone is vegetarian or vegan doesn't mean they don't like the taste of meat.
I'm a strict vegetarian myself and have been for about ten years. But as much as I love plant foods, I absolutely miss meat — I was never a big meat eater, but I would enjoy burgers, salami, pepperoni, bacon, Italian meatballs, prosciutto, things like that.
I dislike Beyond products, which taste a bit weird and metallic to me. The only imitation meat product I've remotely enjoyed is Impossible Burger. Nobody has managed to make anything else — if someone would nail plant-based pepperoni or bacon I would be all over it.
Celsius is not an absolute scale, but that isn't a problem for deltas: (10C - 5C)=5C, (10K-5K)=5K. Celsius is only problematic when multiplying or dividing. 10C is not twice as hot as 5C.
Yes, absolutely. It does not take too much effort, either.
People who say you need adjust your posture are mostly incorrect. Your body will assume a slouching position after a while no matter what. You cannot consciously will yourself to just "sit better". Good office chair and placing your screen at the right height do help enormously; these are things that make your body adopt a certain posture subconsciously. But they're not a complete fix.
The only real fix is to work out. Bad posture resolves itself over time if you build up strength in your muscles and tendons, all the way from your legs to your neck, the whole shebang. You can think of your body as a piece of rope. If not adequately exercised, the individual strings will start to sag and the rope goes floppy. Training tightens the whole thing into a stable, tight bundle.
You don't need to go full "gym bro" or even enjoy it. But you need to do regular strength exercises — squats, deadlifts, crunches, the usual — every week. You don't need to do super heavy lifting or intense cardio, just a healthy, generalized workout routine focused on the whole body. In theory you can do this at home. But as someone who's patently not a gym bro, the only way I was able to do this is to get a personal trainer.
I found a wonderful gym where they did small, four-person group classes. There are many of these around, and while they may be pricier than regular gym membership, they're worth it. You get a personalized program with a trainer who monitors your progress carefully and corrects your form and technique, and keeps you motivated.
I wouldn't work out on my own as I would find excuses to stay away, but by setting up a regular appointment twice a week, I kind of forced myself into it. And when you have a trainer you see twice a week, it's much harder to cancel just because you don't feel like working out that day.
Lastly: Stretches (like the classic "stand against a wall" tricks you find online) do not work, because you're just temporarily stretching muscles and tendons. These need to be actively worked out in to build up, and stretching can actually be counterproductive. This is one reason why physiotherapists typically don't recommend yoga and Pilates, which put too much emphasis on stretching rather than strength exercises.
There was lots of competition in 2019: Volkswagen ID.3, Audi e-tron, Jaguar I-PACE, Polestar 1, etc., as well as lower-end entries like Hyundai Kona, Kia Niro, and so on. Depends on exactly what you think Tesla is competing against.
- All of the other options made a painful trade off on cost or range or something else. Tesla was the only one that had both range and was (to some degree) affordable without being compromised in some way.
Blindsight (and the excellent sequel, Echopraxia) is indeed great.
Solaris by Lem is perhaps the one above all. Lem wrote several of these "inscrutable alien first contact" novels: His Master's Voice, The Invincible, Fiasco, and Eden are basically all variations on this theme, each one unique and highlighting a different aspect of humans' inability to understand the universe. The last three are a little dated now, but still enjoyable to read. HMV is rather dry, a Borgesian essay on an investigation into an alien signal, with lots of references to fictional scientific papers. (Len also wrote two collections of very Borgesian essays that are basically reviews of fictional books: A Perfect Vacuum and Imaginary Magnitude. They're interesting and funny, but I wouldn't put them among his most entertaining work.)
Roadside Picnic by Arkady and Boris Strugatsky is also a masterpiece. They also have a few stories about unseen aliens manipulating the history of humanity by placing traps or transforming humans into infiltrators. The Max Kammerer books (e.g. Beetle in the Anthill) involve this storyline and are very good, probably not well known today.
I tried Tchaikovsky (both Children of Time and Shroud) and found him to be completely unengaging as a writer. Just really dull writing and flat characters. Watts and Reynolds are much better writers. Watts in particular can really pack a punch.
OP here. Sorry if this was premature. I came across it through your earlier comment on HN, started using it (as did a colleague), and we've been impressed enough with how efficient it is that I decided it deserved a post!
I've seen sandbox policy documents for agents before, but this is the first ready-to-use app I've come across.
I've only had a couple of points of friction so far:
- Files like .gitconfig and .gitignore in the home folder aren't accessible, and can't be made accessible without granting read only access to the home folder, I think?
- Process access is limited, so I can't ask Claude to run lldb or pkill or other commands that can help me debug local processes.
For handling global rules (like ~/.gitconfig and ~/.gitignore), I keep a local policy file that whitelists my "shared globals" paths, and I tell Safehouse to include that policy by default. I just updated the README with an example that might be useful[1]. I also enabled access to ~/.gitignore by default as it's a common enough default.
For process management, there is a blurry line about how much to allow without undermining the sandboxing concept. I just added new integrations[2] to allow more process control and lldb, but I don't know this area well. You can try cloning the repo, asking your agents to tweak the rules in the repo until your use-case works, and send a PR - I'll merge it!
Alternatively, using the "custom policy" feature above, you can selectively grant broad access to your tools (you can use log monitoring to see rejections, and then add more permisions into the policy file)
That is very useful. I wasn't sure if I could supply my own override list or how I would even format one, but this solves that problem!
The process control policy, that's kind of niche and should definitely not be something agents are always allowed to do, so having a shorthand flag like you added in that pull request is the right choice.
I'm sure Anthropic and the other major players will catch up and add better sandboxing eventually, but for now, this tool has been exactly what I needed — many thanks!
I also wonder if this could have be a plugin or MCP server? I was using this plugin [1] for a bit, and it appears to use a "PreToolUse" that modifies every tool invocation. The benefit here would be that you could even change the Safehouse settings inside a session, e.g. turn process control on or off.
This would be slash commands that the agent itself wouldn't be able to do, and which would communicate with the plugin via a side channel the agent wouldn't know about. Admittedly I don't know much about the plugin interface in Claude Code, though.
When you say clench, do you mean clench the muscles (i.e. as if biting down), or do you mean jutting your jaw forward?
There is a well known phenomenon among people with (at least some types of) tinnitus that moving the jaw forward increases the sound, but that this also makes the tinnitus go away for a bit. The way my ENT explained it, it has to do with how your brain calibrates sound. Pushing the jaw forward makes the sound louder, which also causes your brain to adjust your hearing to be less sensitive. Or something like this.
With some types of tinnitus, there is a specific connection to the temporomandibular joint. My understanding is that the causes tinnitus are poorly understood, however. There are many hypotheses, but little solid evidence.
I really wish there was a seamless system for this. Once you try to do this kind of thing, you run into all sorts of rabbit holes and cans of worms.
For example, coalescing blobs into "superblobs" to avoid a proliferation of small objects means you invent a whole system for tracking "subfiles" within a bigger file.
And you'll need a compacting job to ensure old, deleted data is expunged, which may be more important than you think if the data has to be erased for privacy or legal reasons.
Object storage has no in-place mutation, so this compaction has to be transactionally safe and must be careful not to leave behind cruft on failure, and so on.
Furthermore, storing blobs in object storage without keeping a local inventory of them is, in my experience, a disaster. For example, if your database has tenants or some other structural grouping, something simple like finding out how much blob storage a specific tenant has is a very time-consuming operation on S3/GCS/etc. because you need to filter the whole bucket by prefix. So for every blob you store, you want to have a database table of what they are so that the only object operations you do are reads and writes, not metadata operations.
Sure, you have things like inventory reports on GCS that can help, but I would still say that you need to track this stuff transactionally. The database must be the source of truth, and the object storage must never be used as a database.
And so on.
This need to be able to store many small objects in object storage is coming up more and more for me, as is the desire to mutate them in-place or at least append. For example, imagine you want to build a kind of database which stores a replicated copy of itself in the cloud. There is no way to do this in S3-like object storage without representing this as a series of immutable "snapshots" and "deltas". It's fast to append this way, but you run into the problem of eventually needing to compact, and you absolutely have to batch up the uploads in order to avoid writing too many small objects.
So lately I've pondered using something else for this type of work, like a key/value database, like FoundationDB or TiKV, or even something like Ceph. I wonder if anyone else has tried that?
Well, I think this is what our company, Archil, is working on. We basically built an SSD clustering layer that proxies/caches/and assembles requests into object storage so that you can run a POSIX file system directly on top.
There's also some really great projects like SlateDB in this space, which could be more like what you're looking for (~RocksDB like API that runs on S3).
Well we have made small objects work well on Tigris (https://www.tigrisdata.com/). And we have several use cases of folks using it as KV store. Funny that you mention FoundationDB, we use that for our metadata storage.
I've heard good things about Tigris. If that means I can store billions of objects without being bankrupted by request cost, and it has fast read access (GCS is quite poor here), then that helps a lot! I'm looking right now for a system that lets me store lots of very small blobs around 4KB each.
I'm a strict vegetarian myself and have been for about ten years. But as much as I love plant foods, I absolutely miss meat — I was never a big meat eater, but I would enjoy burgers, salami, pepperoni, bacon, Italian meatballs, prosciutto, things like that.
I dislike Beyond products, which taste a bit weird and metallic to me. The only imitation meat product I've remotely enjoyed is Impossible Burger. Nobody has managed to make anything else — if someone would nail plant-based pepperoni or bacon I would be all over it.
reply