IMHO, if the protocol specifications seem like pedantry to you the best thing to do is either drop it or design your own protocol. But if in the end what you do is to release a product that is only half-compliant, the rest of the community will turn their backs on you because, by not complying with the standard, you can produce all kinds of unexpected situations.

Restic (or rustic) and Hetzner storage box 🤩

About that I have made the simplest possible implementation of a syslog server in Rust. I use it to collect OpenWrt logs and store them on my server. ;-)

I was an Inoreader user too, but I discovered Miniflux and cannot be happier 😉

LessPass has the possibility to connect to a database (via its API) to store the configurations made for each site. This API can be used from any of the clients (either the browser extension, the mobile application, etc.).

You set up the DB server wherever you want. If you want something light you can use this implementation. And if you are interested, there is also a command line client.

In my view, both a password file (vault/database) and LessPass are potentially attackable via brute force. I don’t see that one is safer than the other.