Live data from Hacker News

GitHub Deceased User Policy

docs.github.com

91–100 of 109 posts

Re: GitHub Deceased User Policy

#91
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

Thanks, I wasn't aware of this service, even though I've been a pretty heavy Google services user for (looks it up)...holy crap, almost 17 years now.

Re: GitHub Deceased User Policy

#92

A former co-worker of mine passed away 8 or 9 years ago, and every year I get a LinkedIn notification asking me to congratulate them on their upcoming work anniversary. It's terrible.

Same thing was happening to me - LinkedIn has a solid deceased policy. I submitted a request with a link to a public obituary, and less than 24hrs later their page was gone. Bittersweet, I’ll miss seeing them pop up now and then, but also won’t feel like they are being disrespected by inaccurate online updates and notifications. https://www.linkedin.com/help/linkedin/answer/2842/deceased-...

I too submitted a request to LI regarding the passing of a colleague. Support handled it the very same day.

Re: GitHub Deceased User Policy

#93

Earlier quoted context omitted.

off topic, and it makes for boring conversation. but: > "Downvoting has always been used to express disagreement." Paul Graham, February 16, 2008. this is something that bothered me for years. I know this is how people behave, that the workflow allows and enables it, and the culture we've built around our tools enforces that. When I watch my own feelings before downvoting it isn't my rational self but my petty lizard…

Edit: I took a quick look at this at it's even easier than that. You can do it with just stylus/Stylish. @-moz-document domain("news.ycombinator.com") { [title=downvote] { display: none } } As a personal experiment, I'm going to leave this enabled for myself and see how long before I find the urge to downvote some comment. :D Original: You could hide the button with TamperMonkey pretty easily (send an email if you ge…

thanks I will try your style receipt. it's fascinating to see how these things effects one emotionally.

Re: GitHub Deceased User Policy

#94
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…

Can it be done by api? If so, you can setup a service that will do it automatically after a year, and just set a reminder to rest the timer every 6 months or so.

Re: GitHub Deceased User Policy

#95
post #65
post #54

If one of your friends is a freenode user and comes down with a slight case of death, please contact the freenode staff via chat.freenode.net #freenode and their account will be memorialised. (I had to do one of these a few days ago and it's sadly not the first) A lot of providers will be happy to figure something out, too - the previous-to-this one situation the deceased also had a linode account and once I got thro…

> slight case of death What counts as slight? Also, it sounds like something I would hear on an Oversimplified history video.

For answers to this and other questions of life, the universe, and everything, stop whatever you are doing and download a copy of The Hitchhiker's Guide to the Galaxy.

For best results, get the first 5 books of the trilogy and do nothing until you have read them all. It will change your life. :)

Re: GitHub Deceased User Policy

#96

A former co-worker of mine passed away 8 or 9 years ago, and every year I get a LinkedIn notification asking me to congratulate them on their upcoming work anniversary. It's terrible.

Facebook sends me emails every year suggesting that I post birthday wishes to deceased relatives.

Re: GitHub Deceased User Policy

#97
post #88
post #54

If one of your friends is a freenode user and comes down with a slight case of death, please contact the freenode staff via chat.freenode.net #freenode and their account will be memorialised. (I had to do one of these a few days ago and it's sadly not the first) A lot of providers will be happy to figure something out, too - the previous-to-this one situation the deceased also had a linode account and once I got thro…

Thank you for sharing, and please accept my condolences. About memorialising IRC nicks, I understand why this is done but maybe it doesn't need to be a perpetual reservation? When an amateur radio operator passes, their callsign becomes a SK (silent-key): http://www.silentkeyhq.com/main.php After a period of time, the callsign can be allocated to somebody else. Often this is a descendant of the operator, but not alwa…

For usernames / callsigns there are other advantages to reserve them indefinitely like the possibility of them being impersonated. This is compounded because of the fact that on IRC your only method of communication is the internet.

Re: GitHub Deceased User Policy

#98
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…

Code isn't worth as much as people think without the humans.

I would challenge you to ask yourself why you want to wait until you're dead to share these things. Why not share some of them now?

Re: GitHub Deceased User Policy

#99

Earlier quoted context omitted.

a) The guidelines don't say anything about needing to give a substantive response instead of downvoting. b) The guidelines do say not to complain about voting. c) Both the creator of HN and its moderators have repeatedly said that downvoting for disagreement is perfectly fine. "Downvoting has always been used to express disagreement." Paul Graham, February 16, 2008. https://news.ycombinator.com/item?id=16131314

off topic, and it makes for boring conversation. but: > "Downvoting has always been used to express disagreement." Paul Graham, February 16, 2008. this is something that bothered me for years. I know this is how people behave, that the workflow allows and enables it, and the culture we've built around our tools enforces that. When I watch my own feelings before downvoting it isn't my rational self but my petty lizard…

the whole UX of down and upvoting is flawed from the onset, the binary choice of reactions is the real problem and is not how human interactions work

Platforms should provide more options for feedback on a given post other than up or down voting.

Re: GitHub Deceased User Policy

#100

A former co-worker of mine passed away 8 or 9 years ago, and every year I get a LinkedIn notification asking me to congratulate them on their upcoming work anniversary. It's terrible.

Same thing was happening to me - LinkedIn has a solid deceased policy. I submitted a request with a link to a public obituary, and less than 24hrs later their page was gone. Bittersweet, I’ll miss seeing them pop up now and then, but also won’t feel like they are being disrespected by inaccurate online updates and notifications. https://www.linkedin.com/help/linkedin/answer/2842/deceased-...

[deleted]
Post reply on HN