Some form of compute with a recurring job that checks for a DNS address or domain.
Choose a domain that needs to be regularly paid for as a target.
Reason I would choose something you pay for as the trigger is because not paying a bill after your death is one thing that will be actioned on no matter what.
Exactly what I would have done !
It’s a game where they try to make you impatient enough that you do it for them.
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
Ooh that’s very cool, I must investigate :3
Sorry this message didn’t make it.
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.
Started reading this thinking it was posted in the wrong sub but ended up inspired!
This is very true, pretty much exactly what enterprise code is.
That’s if they know about it and have access to any of the accounts.
For example you can setup a domain.com account that’s almost completely anonymous.