4 ms·
> In the spirit of other legacy / succession features, is there an opposite option to prefer the account vanishes from the platform entirely? Earlier this year
by mkdirp 5y ago
> In the spirit of other legacy / succession features, is there an opposite option to prefer the account vanishes from the platform entirely?
Earlier this year maintainer of MIT licensed zinit* somewhat disappeared from the internet. Issues weren't being addressed/replied to etc. This of course is fine, they're not expected to provide support or continue maintaining the project if they don't want to. However, in the past few months, the maintainer decided to remove all repos and organisations relating to zinit, causing everyone's profiles to suddenly stop working. People weren't able to initialise their dot files on a new machines. There was no backups nothing. I happened to do update my dot files to the latest version of all the plugins hours after the deletion of the repos, and my whole profile completely broke. I sat there for a good few hours trying to recover. Luckily git is graceful.
Unless there's a method to archive your public OSS repos, removing your profile means all your code will be gone too. At best that's an inconvenience to hobbyists, and at worst, it can break production systems.
In the case of zinit, luckily the community came together and were able to scrape back the latest code based on the local git repos of individuals. I think there are still some repos that have to be recovered.
* zinit is a zsh profile manager, allows for managing binaries, plugins, and other things.
- indigochill 5y ago> at worst, it can break production systems. I assume you don't mean these production systems are depending on reliable access to code in a third-party Github repo because that's fairly easily remedied by at least forking the repo once that repo becomes a dependency (not to mention potentially very dangerous in case of malicious changes), but I'm curious what the scenario you're referring to here is.
- dagw 5y agoI assume you don't mean these production systems are depending on reliable access to code in a third-party Github repo When are people going to stop feigning surprise at this? Being completely unable to deploy a new server just because pypi/npm/github etc. is down has been best practice and standard operating procedure for years now. Keeping a complete audited mirror of everything needed to deploy your product and only pulling code for production from machines you have complete control over is so 2005.
- crawl_soever 5y agoThe same happened to me and I decided to switch to antibody for plugin management. I no longer trust the maintainer as a viable option after what the author said on an earlier thread: "I'm the projects' owner and I can delete them anytime I want. And that just happened – I've had some say major doubts whether I want the time-consuming projects to go on, so I've deleted them" I didnt know that the community took up maintenance though. I will have to check it out.
- gitgrump 5y agoThere are more resilient solutions to this problem. Don't rely on unreliable software.