Now we need Steam and other companies that "sell" you digital products to do the same.
I don't want my Steam library to go to waste when I die.
GitHub Deceased User Policy
101–109 of 109 posts
Re: GitHub Deceased User Policy
#102Earlier quoted context omitted.
What does memorialized mean in IRC?
Basically the account gets marked memorialized and then will never be expired. So, yeah, as the other reply said, "reserved nickname", but more precisely "reserved accountname indefinitely".
I find it a bit weird that you let nicknames expire for living people if you recognize the importance of keeping someone's identity constant.
Re: GitHub Deceased User Policy
#103Earlier quoted context omitted.
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.
Maybe I should directly apply that language to my post-mortem open source projects:
This repository is not a place of honor. No highly esteemed code is placed here. Nothing valued is here. What is here is dangerous and repulsive to us.
Re: GitHub Deceased User Policy
#104Earlier quoted context omitted.
They say that every man has two deaths. The first when they breathe for the last time. The second when their name is screamed out and cursed at for the last time.
*the second when their last bug in production code is squashed
Sweet, I'm going to be immortal.
Re: GitHub Deceased User Policy
#105Earlier quoted context omitted.
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...
I think most complex part there is testing it from receiver's side.
Re: GitHub Deceased User Policy
#106I would hope that they would keep accounts open. I have written several books that rely on GitHub for the examples. I am almost 70, and if I should disappear unexpectedly, I would hope that readers would have the code available until the material is no longer relevant.
Re: GitHub Deceased User Policy
#107Earlier 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…
I found a way here on HN to use uBlock to set Dark Mode and undo the downvote colors. I don't remember who suggested the Dark Mode. This is from "My Filters"
ycombinator.com##html:style(background-color: #3e3e42 !important)
ycombinator.com###hnmain:style(background-color: #2E2E31 !important)
ycombinator.com##.age:style(color: #ccc !important)
ycombinator.com##.c00:style(color: #ccc !important)
ycombinator.com##.c5a:style(color: #ccc !important)
ycombinator.com##.c73:style(color: #ccc !important)
ycombinator.com##.c82:style(color: #ccc !important)
ycombinator.com##.c88:style(color: #ccc !important)
ycombinator.com##.c9c:style(color: #ccc !important)
ycombinator.com##.cae:style(color: #ccc !important)
ycombinator.com##.cbe:style(color: #ccc !important)
ycombinator.com##.cce:style(color: #ccc !important)
ycombinator.com##.cdd:style(color: #ccc !important)
ycombinator.com##.comhead > a:style(color: #dedede !important)
ycombinator.com##.comhead:style(color: #dedede !important)
ycombinator.com##.hnuser:style(color: #ccc !important)
ycombinator.com##.subtext > a:link:style(color: #ccc !important)
ycombinator.com##.subtext > a:style(color: #ccc !important)
ycombinator.com##.subtext:style(color: #ccc !important)
ycombinator.com##.title > a:style(color: #dedede !important)
ycombinator.com##a:link:style(color: #ccc !important)
Re: GitHub Deceased User Policy
#108I would hope that they would keep accounts open. I have written several books that rely on GitHub for the examples. I am almost 70, and if I should disappear unexpectedly, I would hope that readers would have the code available until the material is no longer relevant.
I can't speak to the legal options available and I am not a lawyer, but if there is a beneficiary you can put in your will/trust that you trust with access to Github, then you could put a couple copies of a keypass database, or even a text file on a couple of USB sticks and put them in a safety deposit box for someone to inherit. I would assume they have power of attorney. Perhaps you can make an agreement with them to periodically push a commit to a README.md file. This assumes you are not making payments to Github. If so, the executor / beneficiary in your will or trust would have to take over making payments. If that is not an option, then maybe the account will stay active if you make them contributors to your project. I don't know if Github will keep a project live if at least one contributor allowed read-write access is active. Everything I am suggesting may violate some AUP/ToS, but I have never been one to let such things get in the way when no other options make themselves available.
On a side note, something I do with VPS providers is to prepay them extra so that I have credit in my account. Even if I stop paying them, my services will stay live for years, if for no other reason than to have cron jobs email people I know so that my morbid bad humor can live on for some time. Perhaps you could do something similar so that your book continues to make money for your estate? Maybe another option would be to find a site that specializes in hosting static content specifically for this purpose and put in redirects on github to that site.
Re: GitHub Deceased User Policy
#109Earlier quoted context omitted.
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...
Do you have a link to this? I would be interested in checking it out.