Posted this in another thread but what company would you trust to launch and maintain this kind of service? You need to know that when you kick the bucket in 10, 20, 30, 40, 50 years etc that the switch is actually going to work. You need a company with the right moral compass; funding to pay for hosting, maintenance etc; and the longevity to keep going for the next 100 years. Companies on the "maybe" list for me inc…
> Posted this in another thread but what company would you trust to launch and maintain this kind of service? A law firm. That is the "correct" answer to this problem and is what people actually use.
Show HN: DeathSwitch
31–40 of 51 posts
Re: Show HN: DeathSwitch
#32You've got to be kidding me. Despite the policy difficulties of running a site like this (when is someone dead?, how long until release of secrets?, how to deal with lack of access to emails? etc), This site is completely insecure. https://www.deathswitch.com/members/myaccount.php is vulnerable to a CSRF hijack through the update email page. This literally took 20 seconds to find...who knows what would happen if I de…
After the recurring payments stop coming through?
Re: Show HN: DeathSwitch
#33Your wishes are important after you die (and statistically, we're all likely to die). It's well worth recording them, even if you feel you don't have much in the way of assets to pass on.
Re: Show HN: DeathSwitch
#34You've got to be kidding me. Despite the policy difficulties of running a site like this (when is someone dead?, how long until release of secrets?, how to deal with lack of access to emails? etc), This site is completely insecure. https://www.deathswitch.com/members/myaccount.php is vulnerable to a CSRF hijack through the update email page. This literally took 20 seconds to find...who knows what would happen if I de…
> when is someone dead?, how long until release of secrets? After the recurring payments stop coming through?
There's a lot that can go wrong that has to be thought up before-hand and debugging in production for this type of service is completely unacceptable.
Re: Show HN: DeathSwitch
#35You've got to be kidding me. Despite the policy difficulties of running a site like this (when is someone dead?, how long until release of secrets?, how to deal with lack of access to emails? etc), This site is completely insecure. https://www.deathswitch.com/members/myaccount.php is vulnerable to a CSRF hijack through the update email page. This literally took 20 seconds to find...who knows what would happen if I de…
Not that there's anything wrong with (what's likely) shared hosting, but it doesn't paint the best picture.
To the author: Your idea is good, but it was executed poor, and it's not a by any means. If it is, the logistics of it are too damn difficult to warrant your service (or any service that does this, for that matter).
Re: Show HN: DeathSwitch
#36The big issue - as has been mentioned - is how do we know this service will be there when we need it. The answer is it needs to be tied to some infrastructure that's reliable and already has access to this data. And yes, paying $2/mo for this is nonsensical for someone relatively young. This is a problem without a solution, but this is also not a solution. To be frank, the odds that this domain even resolves this tim…
Surprised me too.
Re: Show HN: DeathSwitch
#37"Be a great way to ensure you can tell heaps of ----s to go ---- themselves after you're dead"
maybe you could pivot and focus on that. ;)
Re: Show HN: DeathSwitch
#38Without debating the merits or otherwise of this service, it's worth using it as a reminder to spend a little bit of time and not much money and ensure you and your loved ones have a legal Will. Your wishes are important after you die (and statistically, we're all likely to die). It's well worth recording them, even if you feel you don't have much in the way of assets to pass on.
Re: Show HN: DeathSwitch
#39Re: Show HN: DeathSwitch
#40With no reply, the computer deduces you are dead or critically diabled, and your pre-scripted messages are automatically emailed to the individuals you designated.
Change 'diabled' to 'disabled'