News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by laughinghan on Tuesday March 29, 2016 @11:20PM (#11386732)

    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
Re:Changes to Npm's unpublish policy by gcb0 on Wednesday March 30, 2016 @02:17AM (#11387297)
that's still the one sided argument the commenter above you highlighted.

just saying it twice from the same month doesn't make it less one sided.

Re:Changes to Npm's unpublish policy by laughinghan on Wednesday March 30, 2016 @02:22AM (#11387311)
Maybe I don't know what you mean by "above you", but, what? The arguments above me I've seen are "missing scenario: ..." and "they didn't address what actually caused all the issues". Which is a one-sided argument is identical to mine?
Re:Changes to Npm's unpublish policy by monochromatic on Tuesday March 29, 2016 @11:23PM (#11386749)
Proximate cause, maybe.