Hugo

Sorry, I couldn't make a clear video showing the issue (you can't really understand what's going on in a video). I've made a reproduction script which should help you visualise...

I don't see how using Mirador would help for this situation. Mirador executes a separate command each time the remote storage changes. If that program were `neverest`, it would try...

A secret storage service (e.g.: KeePassXC, himitisu, or even potentially something like 1Password) _is_ a "safe in-memory database". If neverest exist, then the next time that it runs it opens...

> What I had in mind is a layer at the top of secret storages. Once you ask a password from your secret storage, a copy is safely held inside...

I use it with a hardware key (a Yubikey) and it works as follows: - On the first usage, I'm prompted for a PIN code. - The PIN code unlocks...

Interesting approach. The simplest thing I can think of is to just wait for SIGUSR1 and sync when the signal is received.

If you want to block while waiting for a signal, you can use `std::sync::Condvar` to block a thread or `tokio::sync::Notify` to `await` for an event.

As an end-user, I don't quite understand the value in having two layers of photo pickers. I have to select photos in iOS's photo picker, which then show up in...

> The reasoning behind having these two layers of photo pickers is to have Signal have limited access to only the photos you select. My proposal would also result in...

> The type in the rdata module is for the DNAME record type, which is like a CNAME but delegates the entire tree under the name to a new location...