str4d

#52 and #56 have improved recipient line parsing to the point that it could be behind an internal trait. Serialization still needs to be refactored.

The reason for requiring an explicit `brew tap` before installation is to ensure that the repository is not tied to GitHub, but instead to a domain I control. This enables...

This is imported via the `chrono`, `fuse`, `fuse_mt`, and `zip` crates; nothing we can do until they can be bumped.

I can see a benefit for both kinds of approaches, and _technically_ both could work in `rage-mount`. I intended its UX to basically be close to `mount` for familiarity, so...

> `rage-mount [-i IDENTITY] -t file foo.age foo` Yep, this matches what I was envisaging as a bind-style mount alongside the age file. It's also probably the easiest to get...

LOL NOPE Mounting an age file inside a single-file FUSE filesystem was relatively easy. However, I cannot get a bind mount to work from that fuse FS to the target...

I decided to give up on bind-mount, and instead just use a symbolic link (that I clean up on exit). This is implemented in #190.

UX notes: - Use command symlinks for the three cases: - Encrypted archive to tree - Encrypted file to unencrypted file - Directory tree containing encrypted files, to transparent tree...

Hmm, those were supposed to be removed from the spec. cc @FiloSottile They were part of the early draft spec, and in fact `rage` did implement support for them! But...

The current issue with this PR is that it provides way too little performance improvement for the CPU cost it incurs. I still need to dig into this and figure...