Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Deceased User Policy

docs.github.com

Post reply on HN
Print view View original

1–10 of 109 posts

Re: GitHub Deceased User Policy

#2

Post by dannyw »

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.

Re: GitHub Deceased User Policy

#3

Post by wdb »

dannyw wrote: 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.

Yes, even LinkedIn is problematic. My dad is still listed on LinkedIn and Google while he passed away few years ago. Total silence from both, even when sending the death certificate.

Re: GitHub Deceased User Policy

#4

Post by vbsteven »

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.

Re: GitHub Deceased User Policy

#5

Post by toomuchtodo »

vbsteven wrote: 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

Re: GitHub Deceased User Policy

#6

Post by ktross »

I lost my fiancée to cancer a few years ago, and this just reminded me that I suggested she create a GitHub account years ago. I didn't know she had used it, but this post prompted me to check, and it turns out she created some (good) issues on a few Minecraft/CraftBukkit projects.

It's great to see companies dedicating resources to putting these policies in place. It can make a huge difference while someone is going through the most difficult time in their life.

Re: GitHub Deceased User Policy

#7

Post by barakados »

vbsteven wrote: 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.

This sounds like an interesting idea! I’m eager to help any way I can.

Re: GitHub Deceased User Policy

#8

Post by modeless »

dannyw wrote: 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

Re: GitHub Deceased User Policy

#9

Post by dazhbog »

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 account and repos if a death cert is received.

Post reply on HN