oramfs looks pretty cool and is similar to things I'm working on.
   ---
   other yammer:
   Regarding filesystems, I'm struggling to find a way to preserve data
   across corrupt systems damaging it and harddrives that break
   frequently.  This is very hard for me to solve.
   This list still makes no sense to me, no pgp keys, to me people say
   things that make little sense (spam filtering out of nowhere?).  We
   need to get onto better channels.  I wonder what people are using for
   discourse with more cryptographic integrity nowadays.
   I proposed to the lsl project (used for neuroscience research) that
   they encrypt and authenticate their biosignal streams.  I wasn't sure
   what system to suggest and suggested hypercore because it offers some
   small proof of creation after the fact  They were expecting TLS of
   course, which I worry around because it doesn't say anything about
   archival integrity after decryption.  Hypercore wasn't really a good
   suggestion because it is written in nodejs and lsl is in c++ :-/
   Seems go and rust are the future.  I looked up go.sum : dependencies,
   although retrieved from github over the network (scary way to make an
   ecosystem) are hashed via sha256 in a way that can be upgraded
   (reliable, trustworthy).  Inspiring.  There are multiple facilities in
   the go dependency system, for pulling from offline mirrors instead of
   github, but they aren't that easy to find.  Haven't checked if the
   commit id of dependencies is used in the hash, or the worktree
   checkout, or what.
   Haven't checked rust's cargo to see what their approach is.  When
   picking a language, I want to make sure there are ways to quickly check
   where data corruption arises.  I always use submodules and subtrees for
   my dependencies in older languages.
   It's cool that go's approach pressures people to mirror github to dev
   offline.  That could accomplish a lot in the world, although is likely
   a little limited to things written in go.