GitHub Deceased User Policy • Hacker News Board

Re: GitHub Deceased User Policy

#41

Post by modo_mario » Wed, Feb 17, 2021, 8:53 AM UTC

Closi wrote: post #15

zxcvbn4038 wrote: post #13

Earlier quoted context omitted.

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.

That's support you pay for tho. We also were surprised when i worked at a 9 person company to get someone from google on the line too when we were considering using google maps api for a project. Support which wasn't payed for but which I assumes comes from the expectation that we might become a paying customer.

Re: GitHub Deceased User Policy

#42

Post by tinus_hn » Wed, Feb 17, 2021, 9:06 AM UTC

modo_mario wrote: post #41

Closi wrote: post #15

Earlier quoted context omitted.

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.

That's support you pay for tho. We also were surprised when i worked at a 9 person company to get someone from google on the line too when we were considering using google maps api for a project. Support which wasn't payed for but which I assumes comes from the expectation that we might become a paying customer.

The other side is that with some companies you can’t even pay for support if you wanted. I’m looking at you, Google.

Re: GitHub Deceased User Policy

#43

Post by tinus_hn » Wed, Feb 17, 2021, 9:07 AM UTC

smilespray wrote: post #25

joseluisq wrote: post #24

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

It has deceased.

Pining for the fjords

Re: GitHub Deceased User Policy

#44

Post by teekert » Wed, Feb 17, 2021, 9:08 AM UTC

devwastaken wrote: post #32

ktross wrote: post #6

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…

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.

+1 for Paper, also works well with GeyserMC [0] so your Bedrock friends can join. BTW, the GeyserMC community is really great, top notch support via Discord with a fancy integrated bot and automated builds that you can just drop into you plugins folder.

I use this Docker image with Docker-compose: [1]

[0] https://geysermc.org/

[1] https://github.com/itzg/docker-minecraft-server

Re: GitHub Deceased User Policy

#45

Post by [deleted] » Wed, Feb 17, 2021, 9:14 AM UTC

dazhbog wrote: 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…

[deleted]

Re: GitHub Deceased User Policy

#46

Post by meibo » Wed, Feb 17, 2021, 9:16 AM UTC

zxcvbn4038 wrote: post #13

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.

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…

That's not really true in my experience, I've had some issues with quotas being displayed incorrectly on my completely free account recently and got an answer within a few hours, saying that they reset the tracking and relayed a bug report to the team. I honestly think that for now, you can still depend on them to do their due diligence with support.

Re: GitHub Deceased User Policy

#47

Post by matkoniecz » Wed, Feb 17, 2021, 9:24 AM UTC

modo_mario wrote: post #41

Closi wrote: post #15

Earlier quoted context omitted.

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.

That's support you pay for tho. We also were surprised when i worked at a 9 person company to get someone from google on the line too when we were considering using google maps api for a project. Support which wasn't payed for but which I assumes comes from the expectation that we might become a paying customer.

Good luck with getting to Google support if you are paying customer.

"Terraria canceled on Stadia after developer gets locked out of his Google accounts" is just recent example

Re: GitHub Deceased User Policy

#48

Post by wereHamster » Wed, Feb 17, 2021, 9:30 AM UTC

anticensor wrote: post #19

wereHamster wrote: post #10

Can I only have one successor?

If you have multiple heirs, the oldest one is supposed to be entitled as this is an unsplittable item.

Sure, but what if I put someone as an successor and they pass away before me? Wouldn't it be useful to have at least a (prioritised) list? If the first one becomes unavailable (deletes GitHub account, passes away etc) then I could at least be notified by GitHub that I need to update that list.

Re: GitHub Deceased User Policy

#49

Post by sverhagen » Wed, Feb 17, 2021, 9:35 AM UTC

It's thoughtful they have a policy at all. I'm sure, at their scale, this happens all the time. I just can't stop wondering how much of a vector for abuse this is? Ie. hostile takeovers of accounts. Yeah, I get it, they probably have some checks in place, but I imagine the legalities are very different per jurisdiction, and people gonna find loopholes. No?

Re: GitHub Deceased User Policy

#50

Post by [deleted] » Wed, Feb 17, 2021, 9:39 AM UTC

devwastaken wrote: post #32

ktross wrote: post #6

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…

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.

[deleted]