Live data from Hacker News

GitHub Deceased User Policy

docs.github.com

11–20 of 109 posts

Re: GitHub Deceased User Policy

#11
post #9

I was thinking the other day that I would like to open-source all my random projects or startup files if I die but I couldn't think of a good way to do it. I guess maybe a private repo with instructions could do, but it requires a technical person in the family or friends to check it if/when GH gives them access. The way that Facebook does it with their memorial service is not bad. You can set what happens with the a…

As an option you can do dead man switch + some automation. Once per month script sends you an email with link. If you don't click the link in 1-2 months, script opens everything.

Of course, that won't handle corner cases like jail or coma, but should work for most everyday scenarios.

Re: GitHub Deceased User Policy

#12
post #9

I was thinking the other day that I would like to open-source all my random projects or startup files if I die but I couldn't think of a good way to do it. I guess maybe a private repo with instructions could do, but it requires a technical person in the family or friends to check it if/when GH gives them access. The way that Facebook does it with their memorial service is not bad. You can set what happens with the a…

I have a document outlining to my (non-technical) wife where all the secret keys can be found, and some suggestions on friends to contact for help using them.

Re: GitHub Deceased User Policy

#13
post #2

GitHub/Microsoft is really setting themselves up to be a customer-centric (different to user-centric!) tech platform. If you try doing this process with Google, you are given a canned form and you'll probably (not) hear back from a robot.

I think you are giving them too much credit - Microsoft won’t talk to anyone who isn’t a partner and GitHub tends to just be silent on anything they can’t cut and paste an answer to. It’s more an issue that mumbling on about your algorithm and submitting support tickets while bereaved kin desperately seek access to a loved one’s account is just incredibly bad PR and always makes the front page - and nobody wants the job of dealing with that.

Re: GitHub Deceased User Policy

#14
post #8
post #2

GitHub/Microsoft is really setting themselves up to be a customer-centric (different to user-centric!) tech platform. If you try doing this process with Google, you are given a canned form and you'll probably (not) hear back from a robot.

Google has Inactive Account Manager, a dead man's switch for your account: https://support.google.com/accounts/answer/3036546?hl=en

Their activity detection does not inspire confidence. Google is an incredibly bad proxy for user activity.

Edit: downvoted but no substantive responses? Guidelines are for thee but not for mee, I guess.

Re: GitHub Deceased User Policy

#15
post #2

GitHub/Microsoft is really setting themselves up to be a customer-centric (different to user-centric!) tech platform. If you try doing this process with Google, you are given a canned form and you'll probably (not) hear back from a robot.

I think you are giving them too much credit - Microsoft won’t talk to anyone who isn’t a partner and GitHub tends to just be silent on anything they can’t cut and paste an answer to. It’s more an issue that mumbling on about your algorithm and submitting support tickets while bereaved kin desperately seek access to a loved one’s account is just incredibly bad PR and always makes the front page - and nobody wants the…

Microsoft will definitely speak to people who aren’t partners - I work for a small business (12 people) and the two times I have had to go to Microsoft for support on 365 they have been incredibly helpful.

Re: GitHub Deceased User Policy

#17
post #4

It’s nice that they built something into the service but I think can this problem can be solved independent of the service. One of my weekend project ideas is a small deadman-switch service that pings you every X days to press a button, if it hasn’t heard from you in Y days it sends a private key encrypted file and some instructions. Think onetimesecret with a button and a timer.

https://www.deadmansswitch.net/ Built by /user?id=StravosK

Now the question is: What happens to the DeadMansSwitch service if something were to happen to its maker? It's like we need to form mini multi-generational cults to keep human services like that going for as long as humans keep going until the point they stop.

Re: GitHub Deceased User Policy

#18
post #11
post #9

I was thinking the other day that I would like to open-source all my random projects or startup files if I die but I couldn't think of a good way to do it. I guess maybe a private repo with instructions could do, but it requires a technical person in the family or friends to check it if/when GH gives them access. The way that Facebook does it with their memorial service is not bad. You can set what happens with the a…

As an option you can do dead man switch + some automation. Once per month script sends you an email with link. If you don't click the link in 1-2 months, script opens everything. Of course, that won't handle corner cases like jail or coma, but should work for most everyday scenarios.

I am building such service, will release it in 2 weeks. It would check on you by email or sms in periods you define and if the trigger is met (eg you did not reply in X days/hours) it would send your predefined messages or webhooks or zapps or...

Re: GitHub Deceased User Policy

#20
post #2

GitHub/Microsoft is really setting themselves up to be a customer-centric (different to user-centric!) tech platform. If you try doing this process with Google, you are given a canned form and you'll probably (not) hear back from a robot.

On my local market it's the reason Google cloud adoption among medium to large companies and institutions is laughably low. Microsoft's support exists, it's a real argument towards them.
Post reply on HN