This week I read a post about the death of the Boeing whistleblower, and how Boeing might have suicided him.

I don’t care about if the rumors are true or not, however someone mentioned in the comments that in such situations one should always have a Dead Man Switch.

For those who don’t know a Dead Man Switch is basically an action TBD in case you die, like leaking documents, send messages/emails, kill a server etc . . .

The concept tickled me a bit, and I decided I want to build a similar system for myself. No, I am not in danger but I would like to send last goodbyes to friends and family. I think it would be cool concept.

How would you go and build such service?

I thinking of using a VPS to do the actions because it would be running for a while before my debit card gets cancelled.

The thing that is bugging me out is the trigger, I will not put that responsibility onto someone that’s cheating, so it would have to be something which can reliably tell I am dead and has to run regularly.

Where is what I come up with :

  • Ask a country association through email if am I am dead.

  • Check if I haven’t logged out on my password manager in a week. If it’s even possible.

TLDR; Give me ideas on how to build a DEAD MAN SWITCH and what triggers should I use.

  • Hegar@kbin.social
    link
    fedilink
    arrow-up
    22
    ·
    9 months ago

    I always thought it was just like an email set to future send in say a week or 2, then every few days or every week you go in and bump forward the date.

    I always heard a Dead Man’s Switch defined as a switch which goes off once you stop pressing it. So you just set up something to go off in the future, then for as long as you’re alive you keep preventing it from going off.

    • jkrtn@lemmy.ml
      link
      fedilink
      arrow-up
      28
      ·
      9 months ago

      As long as you’re okay with the edge cases on that: jailed, hospitalized, or other event lasting two weeks and your switch goes off.

      • Hegar@kbin.social
        link
        fedilink
        arrow-up
        12
        ·
        9 months ago

        Yep, false positives are a problem for a dead man’s switch.

        Two weeks without being able to get internet access or word to a friend is definitely possible but seems pretty unlikely.

        You could make it more than 2 weeks out but I think that’s a good middle ground between avoiding false positives and striking while the iron is hot, you know? Imagine sending an email beginning “if you’re reading this I’m dead…” and having recipients think “Yeah, that was ages ago.”

      • ransomwarelettuce@lemmy.worldOP
        link
        fedilink
        arrow-up
        6
        ·
        9 months ago

        Yeah that’s my problem, a false positive in this situation is not something that atrocious, but I would catch slack by my friends for the rest of my life hehehe.

        • Troy@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          Just make it ridiculous. Like instructions to get an artifact that will resurrect you from a museum in France… Then if it goes off by accident, it is comedy.

      • jeremyparker@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        9 months ago

        This is the core issue with the traditional dead man’s “switch” – it doesn’t require death to go off, just letting go of it, and there are other reasons why that might happen. By extension, a switch that requires you to log into something periodically might be problematic if you’re predisposed. Personally I’d just set a longer timer, a month is probably fine and, unless your “exposure” is extremely time sensitive, a month won’t matter once you’re dead.