5 ms·
seems like a good reflection of the current social climate: they have a policy to prevent mildly offensive package names, and they enforce it, but they don't ha
by notatoad 9y ago
seems like a good reflection of the current social climate: they have a policy to prevent mildly offensive package names, and they enforce it, but they don't have a solution to packages randomly disappearing and being replaced with malicious versions.
- barneygale 9y agoIt's a shame there are enough edgy teenagers making npm packages that such a policy is warranted
- deleted 9y ago[deleted]
- Kudos 9y agoThe term "nazi" is not simply mildly offensive, there are likely legal implications if you want to serve users in Germany.
- djsumdog 9y agogotta have priorities.
- newfoundglory 9y agoI miss the days when everyone predicted and solved technical bugs with ease and didn’t have time to do eye—rollingly simple things like say “don’t be an idiot”. Remind me when that social climate was in place, again?
- majormajor 9y agoOr it could be that it's easy to do simple low-hanging-fruit things and harder to do more complicated things. The whole JS ecosystem has come together in a rather ad-hoc way, it's plain stupidity or moronic political gamesmanship to assume more motivation than "nobody thought it worth blocking the entire platform to build a fully-trusted base infrastructure so far." It's funny how many people get easily pissed off about other people allegedly being oversensitive. And it's sad how many of them are part of my same bullied-as-young-nerds cohort, considering that it appears their reaction to getting some power for the first time in their lives was to jump into the bully camp themselves.
- marcosdumay 9y ago> it appears their reaction to getting some power for the first time in their lives was to jump into the bully camp themselves Or maybe they see others using political correctness to bully people around them.
- majormajor 9y agoThat seems like an implausible explanation for a comment trying to make a political issue out of two disjoint things: a package manager design flaw and an editorial control policy for package names. "Publishers" having a level of interest in what goes out on there platform is as old as anything, and so is flawed software design. So I stick by my stance that it seems like tying to try those things together ("you screwed this up because you're morally in the wrong as shown by your focusing on the wrong things") to advance a personal political agenda is the more bullying behavior, here.
- zbentley 9y ago> using political correctness to bully people around them. "Please don't use unnecessarily harmful/crude/we-don't-like-it language when giving names to pieces of computer software that we host, manage, and coordinate for you" counts as bullying now? I think not. As they say, if you don't like it, don't play. And besides, NPM seems pretty focused on package names alone (as they should be). If you absolutely must live out your libertarian fantasy by being insulting, nobody's stopping you from making the API to your package something like: const pkg = require('totally-innocuous') pkg.IHateYouBecauseOfYourEthicityOrGenderOrReligionAndIAmProudOfIt()
- maxerickson 9y agoIt's like how companies still enforce their no masturbating at your desk social mores even when there is urgent business.
- danso 9y agoOne thing is probably easier than the other, and can be tackled asynchronously.