I understand your point, but let’s consider each issue separately:
I claim that node does not need any special attention, see below why.
This is not a problem of storj, or caused by storj, or only impacting storj. it’s a free ddns provider. That’s why I refuse to use anything free, including oracle “free” tier, without becoming a customer. As a counteranecdote – in my whole decade of using cloudflare I have never once had my dns fail. Maybe because DNS is one of their core businesses… Would I use noIP/duckDNS/other crap? Never. Won’t even consider. Storj or not, I want to be able to access my home server.
No you don’t, and that’s the deal. You let storj run node software, and it’s on them to maintain it. If they leave a lot of crap around – not my problem. They will just get less space. So they are incentivized to fix issues.
I have never had to do that. And yet somehow magically every node has only 4 folders under blobs. Magic. Or maybe storj doing their job. Maybe if you waited, instead of rushing to fix things, and gave storj more time there would have been nothing to fix.
Right, but I never experienced any, and wanted examples.
Lol. I would not care if my nodes get less traffic, or more traffic. Again, this is not my problem. I was asked to run this piece of software, and make it accessible on some port, and provide wallet where money drips every month. I have done all that.
Storj is implicitly incentivize to make node as efficient as possible (and this coincidentally benefits me too) so I don’t have to do anything.
My only monitoring is that TCP port is accessible. That’s it. I promised this to be accessible and to keep it accessible does not require me to do anything, just keep the server and modem powered. Which they were already.
Lets consider more examples of unexpected:
- house burns down – welp, I’ll take a loss of storj income.
- Extended power outage – can’t do anything, not going to worry about it.
- Bad update nuked the node. Not my update, not my problem, storj will roll back the recommended node version, it will revert in 15 min.
- Bad OS update breaks stuff – I don’t update OS, and node runs in jail, which I also don’t update. And it’s freebsd, on purpose – it’s not going to break even when updating between major versions, which I’m not going to do, because I don’t have to.
- AirVPN endpoint down for maintenance – I’m not doing anything about it. Node can be offline for a few hours.
- The whole disk array died. I’ll be busy restoring my personal data from backup, I could not care less what happens with node. Hence, not doing anything special. Once I’m done, I’ll start a new one.
- Bad power brownout/transient concussed the UPS and it refuses to turn back on, when power is back, and I’m out of country? (true story, from the past) – Recycle all CyberPower UPSses, never buy that piece of shit, and use APC only. Never had this issue since. But I digress.
so… as long as my server exists it is going to be running, and there is nothing for me to do.
The key is to not self-inflict issues, like using weird DDNS provider, or crappy router, or crooked hardware, or flaky cables.