Show HN: Death Plan Switch, a self-hosted dead man's switch for solo devs

This will be a good e2ee'd hosted service though (at least for someone like me). The problem is how to de-e2ee when the person is gone. Might be workable if the dependent receipient might also be well versed with encryption and had an open public key or so. Yeah, this is tricky.

But either way, it's kinda weird to setup something that will be sued after they are dead and that something is supposed to be maintained and kept up by them.

By the way Google has had this for a while and I signed up for it back in 2018 or so.

they check in it feels like quarterly at most

https://support.google.com/accounts/answer/3036546?hl=en

- Easy to use, my idea is just have a telegram/facebook chatbot, people talk to it in plain English, what is their message, the receiver and the watch time.

- Multi reminder: For example, you can set 3 days to send message 1, 10 days to send message 2 and so on. The idea is the message 1 can be "You are receiving this message because XXX has something to talk, please contact them if you can ASAP". So that if you forgot to "kick the dog" 1 day, your deep personal message won't be sent immediately.

I am not sure why this focus on clients in a context like this feels unsettling to me, but it does.

Hmmm... the market is kinda narrow.

But more importantly, say I self-hosted this service, then, I have to answering emails for the rest of my life telling a program I'm still alive. It's kinda high maintenance all on it's own.

That is assuming this service continuous to run without upkeep, at very least keeping it powered, and connected to the Internet. I'm not really sure what comes first, the end of my life or I got bored of doing it.

I know it sounded inapplicable for a lot of people especially who do remote works, but still if you're thinking about letting a machine run your death plan, maybe it's also the time to start make people connections, such as with lawyers, partners etc, people you can trust and have the capability of handling issues.

Also, if you do remote work, maybe setup an account inheritance plan if the platform supports it, assuming the account is dedicated for working for the effected team of course.

Also also, just an idea, what if you make the check passive? Instead of having to answer emails, some automated procedure will send keepalives to tell the program to not trigger? That will massively lower the cost of using it.

wowww 42 unit tests that Claude made up

I was into it until you considered this a level of assurance

feels like you’ve been out of the software industry for a decade or two

but maybe you know your clientele and they would find this validating. I’ve entered into a couple industries over time where complete non sequiturs are what sold products. “So-and-so has this random unrelated credential, and thats why he will be the trusted partner for this commodities shipment he has no experience in”

It's fine to use AI to create the product – but please, for the love of god, write your own copy. When someone can't be bothered writing their own landing page, I assume they're just not that bothered about the product.

IDK if it's just me, but weekly might be too often?

While it seems like a dark topic to address, I find it very useful, thanks for sharing.

So, you haven’t had enough time to even encounter most edge cases :)

Are you OK bro?