romeo19361

Thanks Kevin, it's fixed at weekly in V1 so bills don't lapse. For a new version I'm looking at making weekly configurable to a longer timeframe from community feedback.

You're welcome. I'm pitching to an organisation with a heap of members next year. The bus factor was what came up when I ran some scenarios through my AI as to why they might not shop with an independent. :)) Spot on.

Not at this stage. Part of my campaign is to inspire others to create a solution. It came up in my business and this is how I'm dealing with it. I've always been web based. There's actually an app you can download for your phone at deadmanswitch.com If people create their own switches in different flavours I consider this thread to be successful.

Add your 2IC as an Admin on Apple (you need a organisation account) and with Google Play console invite them. You can keep a master document, put the 2FA recovery steps in it, and keep that master password separate from the document. Happy to work through any issues with you mate. :))

Another option for anyone reading this thread is to put the switch on a different host to your main VPS or servers. Cheap hosting paid yearly in advance is one idea under a different billing account or another provider. My switch is hosted in Singapore but the majority of my sites are Australian. So if the Aus servers go down upstream it's less likely the switch will be affected. :)

Personally I'm handling this by paying my monthly hosting bill two months in advance. That gives my 2IC plenty of time to move the sites or provide access to my clients' new provider. Also the 2IC can pay the hosting bill. The reason the switch checks weekly is also to stay in sync with monthly bills paid. Nice insights and thoughtful comments. Thanks, calyhre.

I decided not to monetize or host it for sale that way because I didn't want to deal with the warranty side of things through an insurance provider. The app is free to take and use or do with as you wish. Thinking of adding a longer timeframe to a new version as others have asked too.

<3 thanks squinx :))

I'm glad this has inspired your ideas :)) the project is free to fork, run it through your AI or it's there to inspire your own switch.

The Switch works by pressing a button on a page. The Switch emails the link, so pressing the button confirms everything is okay! An automatic keep alive would keep pinging if you're dead. I agree it's a narrow market. I've put my 2IC in place and I'm meeting with my lawyer soon to add her. This is about having external relationships for sure and I very much appreciate that comment. The cost to me is a small Linode (nanode) and it hooks into SMTP2go which I already pay for ;)

I'll check that out, thanks. I recall turning them off so will look into it :))

The point has been noted, thanks Jen. :))

Point noted, thanks.

Built in, you can pause it on your holiday for up to 28 days

<3

I like my clients :)) that's all I can say. Thanks for the comments.

Fair enough. The readme contains the rehearsal script so you can make sure it's working for you. We don't host this service so you are ensuring the product works for you via rehearsal and usage.

I'm building a business for the long term and those clients are investing money into me. My next of kin is notified first. It just seems sensible to give my clients long term security if I have another health issue or die.

The system checks with contacts after one year to reconfirm. If I don't receive my weekly check-in email I check the server. This is a best effort attempt to ensure business continuity for me if I'm dead. It's better than not having a plan for me. There's a health address you can point to that checks the system is working from an outside monitor. :)

Fair call on the copy, I may tweak it. The product came from a brief I spent two days on, so the thinking is mine even where home page's words aren't entirely. This is a free product. I'm happy to have my Switch in place because my clients are loving the plans.

<3

PHP by Larry Ullman happened to be the first programming book I read in 2002. I love PHP and I can understand what Claude is doing with it.

It's only one button to press each week. I don't have a Garmin, that would be interesting to connect it in that way for your use case.

Would love the feedback and test, thankyou.

The readme goes through rehearsals and contacts reconfirm yearly, and I confirm each still has what they need. Thanks, mate.

Agreed.

I shared it because my business had the need and to inspire others to think about succession. It's dead simple to build with or without AI for a seasoned coder:))

Yes — healthy and fine. I checked in with my Switch yesterday:))

For version 1 we decided for the check-in to be weekly because it can still take 13 days for the Switch to tell the lawyer and/or the 2IC where our master keys are held. Thanks for the link, this isn't locked to google accounts, it's more so for the 2IC to ensure business continuity with servers domains Dropbox etc.

Also, if you miss the first email two more reminders are sent to you before emailing your next of kin. It's only when your next of kin says there's a problem, or doesn't answer, your lawyer and/or 2IC are informed. It's a great point you've raised.