Reading the article I thought it was some massive popular framework. But when I visited the library's github page, it seems to have only 8 favorites. Am I missing something?
I've Just Liberated My Modules
101–110 of 827 posts
Re: I've Just Liberated My Modules
#102I think it's amusing to see this from the perspective of the company. Some guy uses your trademark without your permission so you tell him to knock it off. He refuses, so you go around him, and so he protests... by fucking over all of his users. In a dispute that doesn't involve them. And people are celebrating this.
Then you realize that if your assumptions are wrong, any conclusion from them is valid.
Re: I've Just Liberated My Modules
#103FYI I'm the one who republished left-pad after it was unpublished. I think of it similar to letting a domain name expire. The original author removed the code and I forked it and published a new version with the same package name. The main issue was there were so many hard coded dependencies to 0.0.3 so I asked npm support if they could allow me to re-publish that version and they complied since I was now the maintai…
Re: I've Just Liberated My Modules
#104Re: I've Just Liberated My Modules
#105Re: I've Just Liberated My Modules
#106The fact that this is possible with NPM seems really dangerous. The author unpublished (erm, "liberated") over 250 NPM modules, making those global names (e.g. "map", "alert", "iframe", "subscription", etc) available for anyone to register and replace with any code they wish. Since these libs are now baked into various package.json configuration files (some with 10s of thousands of installs per month, "left-pad" with…
Re: I've Just Liberated My Modules
#107Earlier quoted context omitted.
This is incredible. They screwed the author about ownership once and then they did exactly the same thing again.
Did they? Most open source licenses aren't revokable - you don't have to stop distributing the code just because the author asks you to stop. That seems especially true in this case, considering the author chose[1] to license left-pad under the WTFPL[2]. I'd say re-publishing the package counts as NPM doing "whatever the f * they want" with the code. [1] https://github.com/azer/left-pad/blob/master/package.json [2] h…
Sounds like we could start seeing npm specific releases with different licences to the github repo (or npm specific branches with different licencing)
Obviously npm could re-publish the non npm specific code, but that would be more manual than a simple revert of an unpublish.
Re: I've Just Liberated My Modules
#108I think it's amusing to see this from the perspective of the company. Some guy uses your trademark without your permission so you tell him to knock it off. He refuses, so you go around him, and so he protests... by fucking over all of his users. In a dispute that doesn't involve them. And people are celebrating this.
Re: I've Just Liberated My Modules
#109I think it's amusing to see this from the perspective of the company. Some guy uses your trademark without your permission so you tell him to knock it off. He refuses, so you go around him, and so he protests... by fucking over all of his users. In a dispute that doesn't involve them. And people are celebrating this.
Re: I've Just Liberated My Modules
#110Earlier quoted context omitted.
Just because they've trademarked "kik" doesn't give them complete control over all instances of that 3 letter string in the world. See the 8 factors of trademark infringement, and trademark law in general; this is just a kik lawyer being threat happy.
+1 also US Trademark != the whole world. NPM should have handle this better!
It's not good that NPM-the-piece-of-infrastructure is vulnerable to this, maybe a registry like this shouldn't be under control of a single company, but we don't know enough to decide what options NPM Inc-the-company had.
I hope they clean up/better communicate their policies around this, once they have them figured out (e.g. the package dispute page doesn't discuss trademarks).