Comment on How will this community survive its Eternal September?
w0odl@lemmy.radio 3 months agoI’ve had that thought and we’ve talked about it a bit with respect to upgrades, but honestly, it opens a larger can of worms and trust levels.
There’s a lot of sensitive information that I’m already by default trusted with and finding someone that, to be honest, I can trust would be a big conversation.
Also… deploying this ship is not the easiest thing in the world, even as a docker container. Documentation is like the wild west and sometimes, you have to take a best guess or know how docker deploys work or how the instance itself works.
BUT you are correct. if this is going to be a long lasted instance, having other people on board would help.
vk6flab@lemmy.radio 3 months ago
Ultimately this is about risk mitigation, about what happens if. There are many different ways to tackle this. I have not found a guaranteed solution, but here are some to consider:
Note that I’m not advocating one solution over another. This is more an attempt at identifying ways to mitigate any potential “risk” in whatever shape that arrives.
I’ll also note that the amateur radio on-air experience is essentially ephemeral in nature. There is nothing wrong with treating this community in the same way. It has a nice symmetry to it if anything.
w0odl@lemmy.radio 3 months ago
Awesome post! Since you made the original post, I’ve actually already started a github wiki to address my concerns about what it would look like going forward. To address them in line:
vk6flab@lemmy.radio 3 months ago
I don’t know how you have implemented this, but on AWS we tend to set up an automatic snapshot every x-hours that expires (gets deleted) after y-days. If worse comes to happen, you resurrect the latest snapshot and you’re up and running. This isn’t a high stakes environment, so small levels of data loss might be acceptable to the community.
I’d be happy to look at and assist with your GitHub repository. Note that I am unable to make a specific time commitment at this point.
I did consider making the “business” aspect explicit in my list, but shied away from it, since with that comes “commercialism” and many mistake that within the context of Amateur Radio. For example, I’ve been told by “experts” that my podcast is a commercial enterprise and should be banned from local repeaters because I make an eBook available of the transcripts and in the past I had a “Donate” button on my website - no longer, thanks to the shenanigans by PayPal.
There is nothing wrong with “failure”. It’s a state, just like “on” or “off”. If it doesn’t do what you want, then you might call that state “failure”, but if it did exactly what you planned, then that might be called “success”, even if from the outside looking in, the two are identical, the instance is no longer responding. In other words, this is a matter of perspective and planning. Which is why we’re having this conversation in the first place :-)
w0odl@lemmy.radio 3 months ago
We’re using linode services on this instance and we backup nightly, but not everything. I’d only want to implement a higher level of backups if we needed it because costs go up.
I’d never really think/imply this is a business. I make no money from this. Just more in the thought of people working together to make this a better place.