5 ms·

Weirdly, the hard part here is reliably knowing when you died. Messy solvable in a localized way. Really, really hard to solve on a global scale.

ISL 4y ago
If your executor sends GitHub a death-certificate, that problem is completely resolved.
Aeolun 4y ago
Eh, if I don’t respond for a few months I’m probably dead enough. It’s something you’d enable yourself, so you’d know that all your repos were made public if you ever wake up from a 6 month coma.
jefftk 4y ago
Why not make it trigger on not logging in for N months, and after ignoring multiple attempts to notify you? This is what Google's inactive account manager does.
- SamBam 4y ago
  But Google's inactive account manager doesn't then publish all your emails on the open web. There could be any secrets (API keys, etc) in a GitHub repo.
  - jefftk 4y ago
    I was going to speculate more about how GitHub could handle this, but it turns out they already have a system where you name a successor and they get control of your public repos 7d after GitHub receives a death certificate or 21d after an obituary. But they don't include private repos: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories https://docs.github.com/en/account-and-profile/setting-up-an...
- watwut 4y ago
  That sounds like extortion to me. Like, stop using github and we will make all your stuff public despite you originally intending it to be private.
  - giancarlostoro 4y ago
    We are talking about the developer opting in.
  - jefftk 4y ago
    We're talking about an optional feature for developers who want it, that you have to go and turn on. (And it should have very clear warnings before you turn it on so you don't accidentally make things public that shouldn't be. Plus, there should probably be some sort of way to tag which repose would still need to stay private even after your death.)
layer8 4y ago
A deadman switch should be good enough.

ISL 4y ago

If your executor sends GitHub a death-certificate, that problem is completely resolved.

Aeolun 4y ago

Eh, if I don’t respond for a few months I’m probably dead enough. It’s something you’d enable yourself, so you’d know that all your repos were made public if you ever wake up from a 6 month coma.

jefftk 4y ago

Why not make it trigger on not logging in for N months, and after ignoring multiple attempts to notify you? This is what Google's inactive account manager does.

SamBam 4y ago
But Google's inactive account manager doesn't then publish all your emails on the open web. There could be any secrets (API keys, etc) in a GitHub repo.
- jefftk 4y ago
  I was going to speculate more about how GitHub could handle this, but it turns out they already have a system where you name a successor and they get control of your public repos 7d after GitHub receives a death certificate or 21d after an obituary. But they don't include private repos: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories https://docs.github.com/en/account-and-profile/setting-up-an...
watwut 4y ago
That sounds like extortion to me. Like, stop using github and we will make all your stuff public despite you originally intending it to be private.
- giancarlostoro 4y ago
  We are talking about the developer opting in.
- jefftk 4y ago
  We're talking about an optional feature for developers who want it, that you have to go and turn on. (And it should have very clear warnings before you turn it on so you don't accidentally make things public that shouldn't be. Plus, there should probably be some sort of way to tag which repose would still need to stay private even after your death.)

layer8 4y ago

A deadman switch should be good enough.