The website is not reachable anymore looks like. For me it just keeps loading. > Error 503 first byte timeout > first byte timeout > Guru Mediation: > Details: cache-hhn11525-HHN 1613548903 1064572670 > Varnish cache server
Their entire docs site is down, yep.
GitHub Deceased User Policy
31–40 of 109 posts
Re: GitHub Deceased User Policy
#32I 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…
Speaking of bukkit, bukkit based minecraft servers are still cool. There's a new one called Paper that's been working out well for my small group.
Re: GitHub Deceased User Policy
#33Earlier quoted context omitted.
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.
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.
Re: GitHub Deceased User Policy
#34Earlier quoted context omitted.
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.
> Their activity detection does not inspire confidence. Google is an incredibly bad proxy for user activity.
I mostly agree with you on Google but your post has no substance either.
Re: GitHub Deceased User Policy
#35GitHub/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…
I disagree. I had an issue last week with the billing platform and contacted support. Was resolved in the same day. I was expecting that I won't get a response (they have millions of users?) but I did. And I'm not a big customer, or a partner or anything that close.
Re: GitHub Deceased User Policy
#36So, on top of financial debt, you can also transfer technical debt to your successors ?
Re: GitHub Deceased User Policy
#37It’s possible and likely that next of kin has no idea what to do with a GitHub account.
Would be better to add a deceased.txt or a text box in settings somewhere.
Re: GitHub Deceased User Policy
#38GitHub/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…
I can testify once you hit a tricky point with GitHub support they're completely useless. And when push comes to shove they'll start playing games - leaving off names in emails so it can't be traced back to a specific employee, sending response that look like they're internal comments, etc. Honestly it was a level of immaturity I didn't expect from GitHub. I went from someone who owned tshirts, hoodies, octopints, etc to someone that only uses them if my work forces me to.
Re: GitHub Deceased User Policy
#39This is great, it will be great if tech companies can also start working with the government systems which recognize the legal heirs as well. In the case of GitHub it may not be so pertinent, but with email ids etc. where bank account details and OTPs are sent to, it may be important for email providers to recognize real world legal entities and work with the usual estate management legislations.
Re: GitHub Deceased User Policy
#40Earlier quoted context omitted.
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.
The research people have been doing into conveying the dangers of nuclear dumps to potentially primitive future peoples is quite fascinating.