Re:The Rust community's crate host
by steveklabnik on Thursday November 20, 2014 @02:56PM
(#8637779)
I can speak to the Rubygems case: you'd be surprised at how often people publish proprietary/private information, and then need to pull it down. It happens often enough to actually be a burden on the Rubygems team (at least, when I used to co-work with one of them) that they left 'yank' in.
[ Parent
| on HN ]
Re:The Rust community's crate host
by anuragbiyani on Thursday November 20, 2014 @04:17PM
(#8638204)
> you'd be surprised at how often people publish proprietary/private information, and then need to pull it down.
But once published, isn't such information already compromised for all practical purposes ?
I can understand the legal reason behind "pulling it down" (using someone else's IP, etc), but practically speaking the private information once published cannot really be "undone" (at best you can make it hard to find, and disassociate from yourself).
Let's say you accidentally published your name, address, and social security number.
If it is only up for 1 hour, the chances that anyone malicious sees it is low.
If it is there forever, the chances that someone malicious eventually sees it approaches 100%.
Re:The Rust community's crate host
by colordrops on Thursday November 20, 2014 @04:26PM
(#8638256)
What you are saying makes sense, but you are taking on the entire copyright argument with this logic.
Licensing problems or other legal hassles are also foreseeable enough that you'd want to be ready for them.
I think description should be mandatory