16 ms·
Changes to Npm's unpublish policy
- deleted 11y ago[deleted]
- dantillberg 11y agoFrom the article: "we’ve seen a lot of discussion about why unpublish exists at all. Similar discussions happen within npm, Inc. There are important and legitmate reasons for the feature, so we have no intention of removing it..." Could anyone comment on what those reasons are / might be?
- alanh 11y ago> If you contact support, they will check to see if removing that version of your package would break any other installs. If so, we will not remove it. You’ll either have to transfer ownership of the package or reach out to the owners of dependent packages to change their dependency. Wow. A big change. It means publishing on NPM is granting an essentially irrevocable license. (Edit: Not that anything is wrong with that.)
- steveklabnik 11y agoThis is also just pretty much true, due to open source licensing and how it works. I see this as a plain-English clarification more than a significant change in policy. (That is, the part about npm being able to keep your package up even if you want to take it down, not the changes to unpublish generally)
- kibwen 11y agoGiven that they were willing and able to republish left-pad just as it existed before it was taken down, this was already true in practice, though merely selectively enforced.
- steveklabnik 11y agoThat action was described as an exceptional response to exceptional circumstances, I don't believe it had ever been done before. Which doesn't change your point, but is a bit different than 'selectively enforced.'
- profmonocle 11y agoTrue, but most (all?) NPM packages use free software licenses. If you use such a license you've already granted an irrevocable license to everyone. NPM doesn't need your explicit permission to upload the package to begin with. If you want to be selective about who can freely distribute your code, then you shouldn't be using a free software license.
- imtringued 11y agoThis has been in the TOS since NPM existed. Nothing has changed.
- tlrobinson 11y ago> Because all dependents are satisfied by 1.0.1, support agrees to grant Supreet’s request to delete 1.0.0. There are some good changes here, unfortunately this policy will still break projects that use "npm shrinkwrap" to lock down specific versions, which IMHO, anyone who wishes to retain their sanity will do. When this happens AFAIK there's no foolproof way to "patch" your npm-shrinkwrap.json with the new version without deleting it and re-running shrinkwrap, and thus possibly bumping versions of every other package as well. The usual recommendation seems to be "find and replace" the version in npm-shrinkwrap.json with a regex, which is fine if the package's dependencies didn't change but will break if a dependency is added. I'd love to know if there's a better way. FWIW, if you think this is a very rare occurrence, it's now happened to me 3 times in last few months, the latest being less than a week after the left-pad incident [1]. 1. https://github.com/chalk/ansi-styles/issues/15 https://github.com/chalk/ansi-styles/issues/15 2. GitHub issue with additional discussion here: https://github.com/npm/policies/issues/44 https://github.com/npm/policies/issues/44
- xirdstl 11y agoWe also ran into this issue just last week and used the "find and replace" method. Here's one incredibly horrible solution (hack): publish your own "package" to NPM which depends on the shrinkwrapped versions of your dependencies. Per this policy, they won't delete your dependencies since your NPM package explicitly depends on them.
- kibwen 11y agoNew startup idea: "Dependence As A Service". For a nominal fee we'll automatically upload a package that depends on any version of any other package that you desire, and we guarantee that we will never yield to any frantic, desperate pleas to excise these dependencies!
- eblanshey 11y agoTime to start committing dependencies to your VCS.
- 11y ago
- cwmoo740 11y agoCan I write an npm script to look at all my other npm scripts and unpublish and republish them every 23 hours and 59 minutes?
- kibwen 11y agoThe OP addresses this: "No new packages can be published using the same name and version."
- dates 11y agowhat happens if someone writes a script to publish then unpublish every dictionary word?
- choward 11y agoSure, if you want to be a jerk, but you would have to publish a new version every time. You would break my npm-shrinkwrap.json and I would be sure to never use another one of your packages again.
- chadly 11y agoThese seem to be relatively good changes. I still think the reasons they outline for "unpublishing" (still not a word) are not compelling. I would like to see an immutable package feed.
- gtirloni 11y agoAgreed. I don't think unpublish should even exist and it just creates all these scenarios full of subjective decisions that will help some and harm others. If 1.0.0 was published and it has a serious bug, publish a new package with the bug fix. Let 1.0.0 alone forever.
- chris_wot 11y agoIf unpublish shouldn't exist, then neither should there be the ability to rename packages.
- chadly 11y agoYes, you would need to publish a new version of the package with a different name. But the history of what happened (and consequently anyone depending on the old name) would be preserved.
- kibwen 11y agoThey could adopt Github's model, which seems to work well: when you rename something, the old name becomes an irrevocable redirect to the new name (at least, I think it's irrevocable, I haven't tested it), so all existing uses of the old name still work transparently.
- laughinghan 11y agoI have broken GitHub links, I assure you they're not irrevocable. I transferred my project laughinghan/mathquill to its own organization, so the repo became mathquill/mathquill, and then forked it, unwittingly breaking all github.com/laughinghan/mathquill/* URLs: not commits obviously, but Issues, PRs, Commit Comments...my commit messages occasionally link to discussions in commit comments, all of which were broken. :(
- _Marak_ 11y agoSo wait...if I decided I want to remove my work from the internet and become a recluse, I'll have to get permission from Isaacs? What if I just don't want to be bothered anymore by developers looking for support on my projects? NPM jumped the shark a year or so ago. A package manager shouldn't be a ventured capital funded business. We are all going to suffer from Isaac's leadership on NPM.
- steveklabnik 11y agoThis is how open source code works. It has nothing to do with Isaacs, npm, or how npm is funded. Once you give a bit of software to someone with an open source license, they can continue to distribute it to other people, even if you stop distributing it yourself. This is crucial to how the whole thing works.
- _Marak_ 11y agoI really like NPM. It's awesome.
- steveklabnik 11y agoThis has always been the case, and if you'd like to be able to revoke distribution rights from someone at a later time, you'd need to put that in your license terms. No major open source license that I'm aware of features such a clause.
- LamaOfRuin 11y agoYou don't have to use a standard open source license. In fact it appears you can have packages on NPM with no specified license.
- steveklabnik 11y agoTo be clear as to what you're saying: npm does not require you to use a standard license. This is true. So in those cases, it would be different. That's my point: you'd have to specifically use a license which had this term in it. left-pad, for example, did not have this clause.
- kibwen 11y ago> If you contact support, they will check to see if > removing that version of your package would break any > other installs. If so, we will not remove it. This leaves open a window where a package with legitimately no dependents could gain a dependent between the author contacting npm and the review being conducted. You could likely prevent this scenario by immediately bumping the version number and uploading again so that requests for the most recent version of your package don't grab the version that you wish to unpublish (assuming that it's trivial to rectify whatever caused you to want to unpublish the prior version in the first place), but if an npm employee is capable of checking if an unpublish could "break any other installs" then couldn't this review process be automated? Alternatively, if npm supported something like crates.io's "yank" operation then a package author could opt to prevent packages from newly depending on the version in question without needing to first tag and upload a more recent version, and also without breaking anyone's code in case someone's already become reliant on it.
- Furincer 11y agoThe team at NPM deserves a lot of respect for how they have handled this, and the speed at which they've responded to the community's demand. Bashing them for doing this is an unreasonable double standard. First, they provide a free amazing tool and service for the community. Second, they didn't have the wherewithal to fight a legal battle over a naming issue for one of their users. So they complied, and the community got upset. Third, they apologized and took actions to conform to the community's requests. No groveling, no excuses. Fourth, and now people are bashing them for the opposite extreme? This is ridiculous. The NPM team deserves a lot of respect and praise, not loud mouthing from a bunch of users who don't even donate to support the service.
- jsprogrammer 11y agoYour facts are wrong. NPM claims there was no legal threat, they made the transfer on their own volition. Where is the NPM apology? The blog post I saw directly regarding the `kik` package essentially says they did everything right and would do it again. >We stand by our package name dispute resolution policy, and the decision to which it led us. NPM's decision went against their Code of Conduct. Why should that be respected, let alone praised?
- aioprisan 11y agoWhy is this getting downvoted? As I read it as well, NPM went against their own code of conduct.
- chris-at 11y agoThis addresses unpublishing but what happens to (dubious/real) trademark claims under this new policy? Would this keep kik in the registry instead of forcing the dev to give it up?
- levemi 11y agonpm has already says that they acted right in removing kik and that they would keep old versions of kik around as they were. So the dev would be forced to give it up and old versions would remain in npm.
- zem 11y agothe security placeholder package should fix that issue, shouldn't it? i was pretty shocked that they didn't do that in the initial instance - tell whoever owned 'kik' that they had to remove it due to a trademark claim, but then blocked the name and told kik-the-company that it wasn't available to be used as an npm package name.
- deleted 11y ago[deleted]
- jsprogrammer 11y agoSo, NPM is charging forward like they did nothing wrong? Where is the reflection on the kik Dispute Resolution process? How does one non-NPM user (Bob Stratton and kik Interactive) get to harass an actual NPM user (with millions of monthly downloads), in violation NPM policy, and still be taken seriously, let alone succeed in taking package names with literally (according to transcripts) no discussion from NPM? Is it OK to start referring to people as pussies in emails to them if they don't give up their names? Edit: please downmodders, leave a note about why you are downmodding this. Edit2: Wow, hit a nerve here.
- petetnt 11y ago> Where is the reflection on the kik Dispute Resolution process? In their blog? http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
- jsprogrammer 11y agoThat's not much of a reflection: >We stand by our package name dispute resolution policy, and the decision to which it led us. There is no discussion of the transcripts, or the violations of the NPM Code of Conduct[0] that occurred during the takeover. A very popular community member was harassed and NPM took part in it. I haven't seen this issue addressed by any NPM representative. >Harassing other users of the Service is never tolerated, whether via public or private media. >Harassment includes, but is not limited to: ... inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; [0] https://www.npmjs.com/policies/conduct https://www.npmjs.com/policies/conduct NPM not only tolerated harassment, but sided with the harasser.
- alainv 11y agoHarassed? Really? The undisputed transcript[0] doesn't really support that view, in my opinion. [0] https://medium.com/@mproberts/a-discussion-about-the-breaking-of-the-internet-3d4d2a83aa4d https://medium.com/@mproberts/a-discussion-about-the-breakin...
- TheHolyLancer 11y agoThis is completely bullshit a community than is supposed to be ran on maturity and sharing is now being governed with an iron fist. if kik wanted that name, they should have offered honey first, not vague threats of lawers if npm wanted to arbitrate, they need to be neutral and not be for either side (IE don't say you need to pay 1M for the pleasure, but don't just hand them the name). the guy was an ass, but kik started it all off by being an ass
- btilly 11y agoThe problem is that trademark law pushes kik to be asses here. If you're not seen to defend your trademark publicly, you can lose it. So lawyers are constantly looking for trademark violations. And when lawyers find them, they usually start with legal threats.
- LamaOfRuin 11y agoWhat exactly would they do if I sent them a DMCA takedown notice as soon as I requested that my package be unpublished?
- kibwen 11y agoThey could respond by linking you to their terms of service, which explicitly gives them the right to distribute anything that you upload. (You might be able to get around this by pretending that someone else uploaded code that you authored without your permission, implying that they never possessed the right to upload the code in the first place. This is probably illegal, but false DMCA takedowns happen all the time e.g. on Youtube and I've never actually heard of anyone being prosecuted for it (unfortunately).)
- LamaOfRuin 11y agoParenthetical is my point exactly. In practice, this would require them going to court themselves, which I don't expect them to do. There are also many legitimate and well intentioned possibilities that could lead copyrighted, unlicensed code onto NPM in which case they would have no right, regardless of their ToS, to redistributed it. I don't like the law, but it is what it is, and I wouldn't expect NPM to actually back up their new official policy if push came to shove, because as soon as they try to they lose safe harbor.
- striking 11y agoIf you published it under an open source license, you have given them a license to keep the code. Probably nothing, except a DMCA counter-notice.
- LamaOfRuin 11y agoThat would require that they themselves had a basis for a good faith claim, under penalty of perjury, that I was the original copyright owner. That opens them up to liability (as opposed to youtube, which just makes it easy for uploaders to file counterclaim notices). I sincerely doubt NPM would like to shoulder that burden. By uploading it, I have in fact given them a license, as far as I am able, but that doesn't matter if I never had the rights and they get sued for infringement.
- abritishguy 11y agoWhat happens if a package is depended on but contains pirated things?
- spdustin 11y agoDoes NPM require packages to use a license compatible with their asserting an irrevocable license to distribute said package? How is this verified? EDIT BELOW I see some responses (three as of this writing) that quote their terms, and I want to clarify: I know what their terms state, but if those terms are incompatible with the license of the content being distributed, the terms would not be enforceable, or at the very least, would require mandatory arbitration (itself a clause hostile to the individuals accepting these terms) to invalidate. I guess it boils down to: Did attorneys actually vet these terms and practices, or are they banking on the collective generosity and "FOSS spirit" of the community to protect them from litigation?
- bsimpson 11y agoThere is a license field in package.json. If you use npm init to generate that file, it will validate the option you choose against a list of known licenses. So far as I know, if you write your own package.json, there is no requirement to have a license field. Even if you use npm init, you can choose "UNLICENSED". I don't know off the top of my head if they have anything in their terms of use about the rights to permanently distribute published copies; I only know what the tooling enforces.
- kibwen 11y agoThat's covered by their terms of service, quoted in the OP: "Your Content belongs to you. You decide whether and how to license it. But at a minimum, you license npm to provide Your Content to users of npm Services when you share Your Content. That special license allows npm to copy, publish, and analyze Your Content, and to share its analyses with others." Services like this have to account for such rights in their terms of service, because distribution is a minefield even for properly-licensed packages. For example, the MIT license covers only "this software and associated documentation files", which AFAICT means that if you have e.g. a screenshot in your repo then conceivably you could request a DMCA takedown on anyone distributing your repo. Likewise GPL doesn't cover anything but code, not even documentation (you're expected to remember to explicitly use the GNU Free Documentation License to cover that). IANAL, so I'd be happy if someone who was would chime in with any corrections.
- tombert 11y agoMuch as I like Npm, I do kind of have to wonder if all this stuff is a consequence of having a centralized package manager. I personally prefer the Go solution of just specifying a Git repo.
- steveklabnik 11y agoMany package managers do not offer unpublish at all.
- kuschku 11y agoOr the java way of having dozens of seperate maven repos
- comex 11y agoThen you're just shifting the responsibility of preventing squatting from NPM to GitHub or whoever hosts the Git repo in question. (I don't think GitHub permanently reserves deleted usernames, though I could be wrong.) And if squatting does occur, there is nothing like npm's previous guarantee that replacement packages have a different version number. How is that better?
- kibwen 11y ago> I don't think GitHub permanently reserves deleted > usernames, though I could be wrong This doesn't actually matter, because Github allows you to rewrite your repo's history at will. Even if Github prevented you from deleting the repo itself, an irate maintainer looking to "liberate" their code could just delete the entire history of the repo and force-push to achieve the same effect.
- tombert 11y agoI actually tend to fork my dependencies to my own account.
- comex 11y agoYeah, I was being overly security minded and thinking only about the threat of someone taking the name and replacing the package with a malicious one, not the breakage caused by the package disappearing in the first place. In the former case, if the maintainer deletes their GitHub account, it matters whether someone else could register the same name. But of course you're right that Git repos are far more vulnerable to the latter too, unless you fork.
- apocalyptic0n3 11y agoConcerning multiple packages with the same name, is there any reason npm does not use namespaces like some other dependency/package managers do, like Composer? So "kik/kik" and "azer/kik" could coexist, minus legal issues of course.
- steveklabnik 11y agohttps://docs.npmjs.com/misc/scope https://docs.npmjs.com/misc/scope
- spriggan3 11y agoScopes are not mandatory when they should be.
- DrJokepu 11y agoThat would be also a pretty useful feature also for publishing your own branch of a package in npm.
- extra88 11y agoYes, this was my thought when I first heard of the controversy. I think it could make the trademark issue go away also because the potential confusion in the marketplace would be negated by the package name being paired with the author; it's not like what the package has anything to do with what Kik's services do.
- danjoc 11y agoThis really doesn't seem to address the core issues with NPM. Packages need to be signed with GPG. Full stop. If anyone is running unsigned executable code blindly, they've already failed. You might as well be running .exe files emailed to you by a Nigerian prince. https://github.com/npm/npm/pull/4016 https://github.com/npm/npm/pull/4016 Oh. Wow. I'm at a loss for words after finding that... I hope NPM are seriously rethinking this position. shasums are definitely not a substitute for validating gpg signatures by any stretch of the imagination. Anyway, the worries about package removal are misplaced. If production application builds depend on the central NPM repository, they are set up incorrectly. Dependencies should be proxied via a local dependency repository like Sonatype Nexus or Artifactory. It is unprofessional to have builds set up with dependency directly on a repository not under local control. If you need to convince someone in charge why you need to do this, I recommend this presentation: https://www.youtube.com/watch?v=pBJafU0p_Nk https://www.youtube.com/watch?v=pBJafU0p_Nk It's good, and worth your hour. TL;DW the six reasons are enumerated at 30:59.
- joeyespo 11y agoGPG isn't the holy grail. See https://caremad.io/2013/07/packaging-signing-not-holy-grail/ https://caremad.io/2013/07/packaging-signing-not-holy-grail/ Proxying via a local dependency is a good practice, but that can be set up independently of npm.
- danjoc 11y ago>GPG isn't the holy grail. I don't believe anyone ever said it was. It's a far better approach than using shasums for package integrity though. >Proxying via a local dependency is a good practice, but that can be set up independently of npm. That's the point. I see a lot of people hand wringing about removed modules in the future. It's not NPMs job/obligation to provide the javascript world with never ending storage, hosting, and bandwidth. Expecting a third party to host dependencies that make in house apps run is a fool's errand. That strategy can, will, and just did fail.
- joeyespo 11y ago
- the_ancient 11y ago>>Please post comments and questions here. We’ve moved to a Github issue for improved moderation. No you removed comments because you did not like the comments you were getting... You understand that your policies are almost universally opposed by the nodejs development community, and you are attempting to control the conversation in order to prevent a mass exodus from npm as the default package manager for node, which I believe should happen. The NodeJS Package management should be maintained and run by the Node Foundation, or other non-profit group/committee, not NPM Inc.
- spdustin 11y agoI grow more and more confused about this. Here are some quotes from their terms of use, taken verbatim from https://docs.npmjs.com/policies/open-source-terms https://docs.npmjs.com/policies/open-source-terms: Some language was changed recently - the diff for the current version of their open source policy is online [0]. > Nothing in this Agreement gives npm any ownership rights in intellectual property that you share with npm Services, such as your Account information or any Packages you share with npm Services (Your Content). Makes sense. Your code is your code. > Your Content belongs to you. You decide whether and how to license it. But at a minimum, you license npm to provide Your Content to users of npm Services when you share Your Content. That special license allows npm to copy, publish, and analyze Your Content, and to share its analyses with others. This doesn't specify irrevocable, nor clarify how that license could be revoked by the content owner. > When Your Content is removed from the Website or the Public Registry, whether by you or npm, npm's special license ends when the last copy disappears from npm's backups, caches, and other systems. This seems deceitful. What exactly does "when the last copy disappears" mean? Seems to me that "perpetual backups" would effectively make their "special license" perpetual. Speaking of "special license", they really need to have an attorney write this up. > Other licenses, such as open source licenses, may continue after Your Content is removed. Those licenses may give others, or npm itself, the right to share Your Content with npm Services again. Fair enough, and implies that if my license doesn't give them that right, that unpublishing the code should revoke their "special license". > Either you or npm may terminate this Agreement at any time with notice to the other...The following provisions survive termination of this Agreement: "Your Content", "Feedback", "Indemnity", "Disclaimers", "Limits on Liability", and "General Terms" So ... I can terminate the agreement, but that doesn't actually terminate anything? Don't get me wrong, I feel that npm serves an important function in the community, but as this drama continues to unfold, I find myself trusting them less and less. [0]: https://github.com/npm/policies/commit/140ed66e2169e248674fe16e920ba9a052c8a337#diff-1c802f7fe1aa289dbc553c49af4801e3 https://github.com/npm/policies/commit/140ed66e2169e248674fe...
- mixedCase 11y agoUm... was vendoring deleted packages for those packages that depend on the former too obvious? E.g.: 1) left-pad package (containing versions 1.0, 1.2 and 1.5) is being deleted by its author 2) Package X depends on left-pad 1.0 and package Y on left-pad 1.5 3) Packages $PREFIX-left-pad version 1.0 and 1.5 are created from copies of left-pad and X and Y dependencies updated to point to it. (PREFIX being vendor, old, deprecated, or whatever you want) 4) Original package is deleted (with version 1.2 no longer being available in the registry anywhere), and name will remain unavailable for either a) Forever b) # amount of months with potential adopters being able to express their desire of adoption. Ta-da?
- yati 11y agoWhat about a local "internal/secret" package with a dep on left-pad v1.5? Redownloading all the deps (say, on a new box) will fail for left-pad 1.5, and someone has to go and change the dep manually to $PREFIX-left-pad?
- geekamongus 11y agoYou will be assimilated. Your biological and technological distinctiveness will be added to our own.
- sangnoir 11y agoConspicuously missing scenario: Sandra owns the comic drawing package "stickman" and publishes 0.1.0, 0.9.9 and 1.0.0. A few months/years later, Stick Manufacturing Corp [StickMan(tm)] shows up with their Internet of Sticks support package library to go with their registered trademark and want to publish it as "stickman". What happens next? Do they just hand over the package so Stick Corp can publish a new version? Does NPM inc rename Sandra's "stickman" to something else? what happens to Julie's "comic" package that depends on "stickman^0.9.9" when the package is handed over?
- laughinghan 11y agoTheir previous post does specifically address this, in its own bolded bullet-point: ○ The dispute resolution policy minimizes disruption. Transferring ownership of a package’s name doesn’t remove current versions of the package. Dependents can still retrieve and install it. Nothing breaks. Had Azer taken no action, Kik would have published a new version of kik and everyone depending upon Azer’s package could have continued to find it. It was abrupt unpublishing, not our resolution policy, that led to yesterday’s disruptions. http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
- catnaroek 11y agoDo old versions of the package remain under ownership of the original author? Let's assume I publish a package “foo”, and the name is later transferred to someone else. Will npm make it perfectly clear that the versions I published are my intellectual property, rather than that someone else's? My English reading comprehension isn't precisely the best, but I'm pretty sure this concern isn't addressed in the text you cited.
- laughinghan 11y agoThis concern is indeed not addressed in the text I cited. However, though my English reading comprehension isn't precisely the best either, I'm pretty sure this concern wasn't brought up in your comment that I was replying to when citing that text. I don't see this concern addressed in their Package Name Disputes document at all: https://www.npmjs.com/policies/disputes https://www.npmjs.com/policies/disputes Perhaps they'd be delighted if you brought it up in the public forum they linked to at the end of the blogpost? https://github.com/npm/policies/issues/44 https://github.com/npm/policies/issues/44
- roadbeats 11y agothis blog post says; no matter you're happy with or not, we'll keep profiting from your open source work. What community should ask NPM is; if a developer decide to delete his stuff from NPM, keep the versions to not break other people's work, but do not show it on npmjs.com with advertise as you do right now at npmjs.com/left-pad.
- herbst 11y agoThis is the first solution in this thread that sounds fair.
- smoyer 11y agoSo with the new rules, the easiest course of action is to abandon the published packages and fork new versions to a different repository.
- pfooti 11y agoThis seems like a reasonable approach. It does bracket some of the larger issues that the left-pad debacle foregrounded (dispute resolution and the potential of malicious devs to release dangerous code), but it is a good step forward. Restricting unpublish will prevent some major catastrophes in the future. The issue of a malicious user publishing an incremented version with bad code still stands (as a patch semver release on a package that's not 0.X), but that's not particular to npm. It's just part of the trust ecosystem. The issue of conflict resolution is a thornier one. The medium post by the people at kik [0] paints Azer in a slightly less flattering light. His actions aren't precisely sympathetic, especially since the people at kik and npm both attempted to amicably resolve the problem (and Kik has a legit beef here). Conflict resolution is hard to programmatically / procedurally resolve, and in the case of a limited namespace (more people should use scopes, I guess) there's a real issue when you're releasing a package with the same name as something with registered trademarks in the same domain. Argue with trademark law if you want, and the use-it-or-lose-it features it has, but don't get mad at npm and Isaacs for following the lawyer's lead, especially with Azer's general attitude throughout the exchange. 0: https://medium.com/@mproberts/a-discussion-about-the-breaking-of-the-internet-3d4d2a83aa4d https://medium.com/@mproberts/a-discussion-about-the-breakin...
- catnaroek 11y ago> attempted to amicably resolve the problem I'm not sure I'd use the term “amicably” to describe kik's emails. Was it really necessary to use the phrase “banging on your door”? It's perfectly possible to threaten legal action (it's their right) without, in their own words, “being a dick” about it. They could've phrased it like this: “We'd like to settle this dispute amicably, rather than pursue legal action, but we will defend our trademark.” Or something like that. Dunno, IANAL. While Azer's knee-jerk reaction didn't help matters, I can't bring myself to blame him, because I know I would've reacted the same way, if not worse.
- pfooti 11y agoYah, the problem is (IMO at least) inherent in trademark law. If Azer actually created an OSS package (or publicized kik broadly), the lawyers would be pretty much compelled to start banging on his door. If they failed to do so, Kik the corporation would lose their rights to that trademark. So yeah, I agree - the phrasing wasn't super great. But it wasn't actually a threat in itself, just a statement about lawyers being compelled to do what they have to do. An actual threat - hitting with a C&D letter before reaching out - would have been much more aggressive.
- saghul 11y ago"One of Node.js’ core strengths is the community’s trust in npm’s registry. As it’s grown, the registry has filled with packages that are more and more interconnected." IMHO, at the current state of Node's maturity I'd consider relying on a private and for-profit organization for package delivery a weakness, not a strength.
- Sir_Substance 11y ago>A byproduct of being so interdependent is that a single actor can wreak significant havoc across the ecosystem. "It wasn't our fault guys, someone else wasn't upholding their implicit obligations to their users!" Sheesh, grow a spine NPM.
- steveklabnik 11y agoThe next few sentences directly acknowledge that they built a system that let this happen.
- diggan 11y agoFirst of, I love how npm works and the nodejs ecosystem. For me it provides great value and I'm thankful for all the hard work that node/npm developers have put into the software that they are building Secondly, I think, by having a company deciding the fate of the code that we as developers are depending on, it's not a very good idea. There is a inherit conflict of interest between the community and the company. We want to have the code available at all times but the mission of the company is not the same. They care about being in the center of attention, so other companies can depend on them and they make cash. That's what being a business does to you. What I see as the ideal world, is a way to have the best of the software already written (npm cli) combined with a distributed registry that works peer-to-peer. Not only does it solve the conflict of interest, but also scaling, offline access and long-term maintainability. Many folks are working on getting there now, "gx" (package manager using IPFS https://github.com/whyrusleeping/gx https://github.com/whyrusleeping/gx ), "ipmjs" (distributed package manager https://github.com/ipmjs/ipmjs/ https://github.com/ipmjs/ipmjs/ ) and my own work "everythingstays" (scripts that works together with the npm cli [ http://everythingstays.com/ http://everythingstays.com/ ]) If you're interested in solving the problem in a bigger scale than changing npm inc's policies, I recommend you to check out the tools linked above.
- gedy 11y agoAgreed on second point - one of the first things we looked at when introducing node.js at our company was setting up a private in-house npm repository, similar to what many companies due in the Maven ecosystem to both store private packages and filter/proxy the global repo for outages, problems, etc. It was rather hard and awkward, and there was no solution or support offered from npmjs-the-company. Some time after they introduced private (and hosted) npm repos as a paid offering, but this is still not what a lot of companies want. While perhaps I'm jumping to conclusions, a free in-house offering does not seem to be in their business model and therefore the community has suffered a bit. (I'm aware of the unofficial projects for this)
- zer00eyz 11y agoVendoring is the concept, and is separate from the underlying mechanics. Having an "in house" repository is one mechanism, but checking the dependencies into version control is another one. There just isn't really a good way to do this in/with NPM, and the top google results seem to actively discourage pursuing this pattern. Many other languages (well the ones I use frequently) not only have a recommendations on vendoring, but also support more than one path to getting the job done (with trade offs naturally).
- partycoder 11y agoWon't be the last scandal, the JavaScript ecosystem is worrying.
- gmisra 11y agoAs pointed out elsewhere, npm also already supports scoped namespaces: https://docs.npmjs.com/misc/scope https://docs.npmjs.com/misc/scope ...and has for almost a year: > (As of 2015-04-19, the public npm registry does support scoped packages) The right path forward probably involves encouraging major packages (e.g. https://www.npmjs.com/browse/depended https://www.npmjs.com/browse/depended) to move toward scoped package names, and then eventually deprecate non-scoped names.
- diggan 11y agoIf npm have supported scoped namespaces for a long time, why take ownership from Kik instead of suggesting the company behind Kik to create CompanyName/Kik?
- kibwen 11y agoBecause Kik might have argued that any package named "kik" in any npm namespace could have been infringing on their trademark. Namespaces alone aren't the solution to this problem.
- smegel 11y ago> we have no intention of removing it...if the version is older than 24 hours, then the unpublish will fail We haven't removed it, just disabled it apart from a small initial window.
- sneak 11y agoUnpublishing 1.0.0 after 1.0.1 ships is stupid. Not all consumers are in npm. Many of us like to use specific versions. Unpublish should be denied except in the case of compromise. All other changes should be accomplished via point releases.
- adnanh 11y agoCouldn't they all solve this fuss with namespacing packages to the users, like Github for example. In that case kik/kik and azer/kik would be two different packages, and everyone would be happy. This policy is not a solution to the real problem IMO...
- herbst 11y agoThats laughable. I don't see myself publishing code on NPM for which i magically lose my rights when i decide to move on.