This question is mainly for those that have family/friends depending on their self-hosted services/data. Does anyone have a plan for the worst case scenario in terms of data access/passwords/making sure your services are kept running if people depend on them? I know I sure don’t, it’s just a strange curiosity my brain thought up and I wondered if anyone else had considered this?
I should set up that bitwarden feature that lets people ask for access and they get it if you don’t respond in a set amount of time.
I bought a separate laptop and set it up with an encrypted password that both my wife and I know. It contains instructions on everything from my self hosted stuff to anything else related to my personal life that she would need. It’s 100% offline to keep it safe from a network compromise. This whole thing was especially important since I wanted to make sure my family could access all photos, calendar, contacts, etc for the last decade that are stored on my server.
It takes time to transfer everything to it (all in Obsidian) since it’s a brain dump… But it actually benefits me too. I’ve had a few times where I was like “how the hell did I set that up?” and had some instructions on there the helped lol.
Definitely recommend this to others to consider.
Since others were posting end of life style docs, here is another: https://www.erikdewey.com/bigbook.htm
That’s actually some good info there.
It’ll die with me. Albeit probably a slow death over a couple months, I have to be realistic here - none of my family members will care enough to keep anything running in the long run.
It’s the same fate your grandma’s unfinished knitted scarves and socks had a couple years ago.
I had a few cousins who took and finished all my grandma’s unfinished quilts. They were already into quilting though. YMMV, but it is a good example - if there is someone who can understand/take this over give it to them.
This is why my lab is well documented and managed by runner.ci workflows and the vault password and keys are in an encrypted file in my will. Explicit instructuons for decryption are in same will and handled via one time pad.
Also all of my loved ones know that I am not suicidal and will not under any circumstances take my own life…because reasons.
Anyone at the reading of my will can either take up administration, or put the resources on codeberg funded by a trust for 3 years after my death. If what I’ve built cannot be forked within 3 years i lt deserves to die with me.
I’ve made a note in a paper notebook with my master password for the password manager for my wife, but she’s totally uninterested in anything I do with my server - she tried to understand, but it didn’t work. At least she’ll have access to my emails and other stuff in case I die before her.
Same here. I don’t see how she would manage, she’s not THAT technical. I told her she’d probably be good for another few years barring breaking updates. Beyond that, she’ll need to find someone to retrieve any content she wants to keep. For this reason, I keep all photos with a paid service (ente) as I don’t want to risk her losing those.
INB4: she = MY wife, not yours :)
Haha! For sure not mine!
When my brother’s brother-in-law passed, he gave all that to my brother. Both on the high end of tech/self-hosting capabilities. I’ve come to the conclusion much of it wasn’t worth it.
I’ll be focusing on ensuring access to financial accounts is passed on cleanly. And I’m working on digitizing all remaining physical photo negatives, then planning how to share all digitally with family while still alive. Since I don’t expect any to be interested in maintaining a server after I’m gone, I’m thinking I’ll keep it simple and just give everyone an external hard drive with all the photos. It’s up to them to do what they want with the drive. A copy to each sibling is increases odds it’s survives for a generation.
I’ll make project notes and plans available to anyone interested, but no hard feelings if no one is interested. And my music and movies can disappear for all I care. My tastes are pretty mainstream so I’m not thinking about archival value.
I decided very long ago not to pollute the gene poo, so everything dies with me.
gene poo
Indeed, sounds polluted enough 💩
Ha! Spell check fail
I’ve learned to wear brown pants so it’s not as bad.
I know of this project: Dead Man Hand
I doubt anyone else will know how to deal with the server tbh. Nobody else really uses it, either. Inertia’s a pain, and while I do technically have other users here, I think the most recent login aside me was 6 months ago. They’ll have access to the password to get into stuff to handle whatever accounts they need to, and I may include instructions on how to turn my blog into an epub file if they want to do that, but the server itself likely won’t last more than a month after I die.
No :/ my server will probably die with me. My people are going to complain why homeassistant isn’t working, why automated lights don’t turn on and why nothing has been added to the plex library in forever. Just not sure who they’ll complain to lol.
At the end of the day, its my hobby and they’ll just have to live with how it was before. The hardware will be there if anyone wants to start up their own thing, but I don’t see it happening.And this is why I try to recommend to every single person starting their smart home to plan it so that if everything dies, their internet, their router, power gets restarted, and their HomeAssistant gets corrupted, and you die, at the same time, that everything will work exactly as expected, because with MANY smart home systems they will just stop functioning or be stuck in a bad mode until your family hires someone to fix it.
That’s why I lean hard towards KNX
I figure by then, it will all be part of some AI training set one day. Hopefully my shitty writing and bad opinions poison the shit out of it.
There’s a project on github just for this, I forget what it’s called.
Basically they’ve developed a mechanism for providing instructions and access to security (usernames, passwords, etc).
I’ll see of I can find it
Looks interesting but explicitly says it’s “alpha software “ and hasn’t been updated in five years. I’d be weary of using something like this in such a critical situation.
Replying to get notified!
So you get a notification, spacelord suggested Hereditas: https://github.com/ItalyPaleAle/hereditas
Not sure if it’s the same one OP is thinking of, though.
Edit: also, from further down: https://github.com/potatoqualitee/eol-dr
Passwords, usernames and access keys are all important, but what about technical knowledge? If you’re the one hosting all of that, it’s presumably because you’re the most knowledgeable about that in your group. Without you, even if they have access, will they know how to keep things running, especially when things go wrong?
If?
I suppose you could add the qualifier “unexpectedly”
From the moment I understood the weakness of my flesh, it disgusted me. I craved the strength and certainty of steel. I aspired to the purity of the Blessed Machine. Your kind cling to your flesh, as though it will not decay and fail you. One day the crude biomass you call a temple will wither, and you will beg my kind to save you. But I am already saved, for the Machine is immortal… Even in death I serve the Omnissiah.
