Aurelian

As long as you protect that password store with a sufficiently strong password that you store in a password manager that has a sufficiently strong password :P

I joke but yes some sort of password store is what you would use but make sure that password store needs something like a yubikey with a strong private key on it ^⁠_⁠

The problem is how many random characters can you remember in your head?

A good encryption key would be around 32 characters to form a 256 bit encryption key.

You can do a fun game of encrypt the encryption key with a password but that’s just another vulnerability in the chain.

I recommend getting a PGP key stored on a yubikey and then encrypt all your notes with it since it’s all in markdown, I store my notes on Google drive and keep them decrypted in memory so that I can still use Obsidian.

What about envoy proxy?

Nothing else on the market has as low latency implications to workloads that I am aware of.

Exactly what I would have done !

Very interesting indeed.

I guess a usecase like this easily slips past most developers due to lack of exposure :?

Is the need to respond as a separate entity so frequent that separate accounts for each entity would not be enough or is the user switching process too much friction?

I feel like this is the answer to almost any case where many people hate on something.

Not sure if clever meta humor or wrong community XD

Not sure if clever meta humor or wrong community XD

It’s a shame this doesn’t go further and make the knowledge open source.

If the hosts for this project ever stop then all the info contribution goes to waste :/

I know it would be impractical but i would like to see something like this powered by an open repo where for example all the guides and plant info was stored in a format like markdown docs.

Could use something simple like Docusaurus to power the front end and then have contributors use some sort of front end that wraps that git pull part so non coders could still add to it.

The beautiful thing is that plant data can be accessed without any compute.

The magic of the bad server is they have an R&D budget plus ops team so some waste while testing is covered, you tend to pay for mistakes on the good (home) server :P

Plus getting feedback from a good team beats a rubber duck XD

And then sometimes you use a work server to design the pattern for the home server.

Started with Evangelion Magi naming and now I just use the pet name generator in Terraform.

Random_pet