4 ms·

I'll admit that I cracked up pretty good over this, and am glad that I'm not working in JS/TS every day anymore for reasons among these kinds, but I am firmly o

by sli 5y ago

I'll admit that I cracked up pretty good over this, and am glad that I'm not working in JS/TS every day anymore for reasons among these kinds, but I am firmly on the developer's side on this one. Github suspending the developer's account is well within the realm of the type of questionable actions I expected out of Github after its acquisition by MS and only makes me feel even better about my long-ago move to Gitlab (a story for another time).

glenneroo 5y ago
Sorry to repeat this again (too many repeated threads) but he was already temp-banned from GH around 2013 (i.e. before the Microsoft acquisition) for "creating a script that forced people to watch a library that [he] created", whatever that means: https://youtu.be/varf6oWaFtU?t=202 https://youtu.be/varf6oWaFtU?t=202
Aeolun 5y ago
That’s the craziest thing. What does Github have to do with the npm packages? Why would his account be suspended over an upload to npm?
- toyg 5y ago
  Github owns Npm, so I guess they feel entitled to be "NPM police" and nuke the rest of his output as collateral damage.
  - shagie 5y ago
    NPM has been tightening up its publish and unpublish rules for over half a decade. https://thenewstack.io/the-kik-kerfuffle/ https://thenewstack.io/the-kik-kerfuffle/ That GitHub is now the owner of NPM doesn't change that policy and maturing of the environment. https://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm https://blog.npmjs.org/post/141577284765/kik-left-pad-and-np... > We dropped the ball in not protecting you from a disruption caused by unrestricted unpublishing. We’re addressing this with technical and policy changes.
- laurent123456 5y ago
  Seems reasonable to at least temporarily suspend his account till they know what's going on. His account might have been hacked, or he might have gone mad and sabotage more projects. Still a reminder though that GitHub is a private service and they are within their right to remove your work at any time for any reason, or for no reason.

by sli 5y ago

glenneroo 5y ago

Sorry to repeat this again (too many repeated threads) but he was already temp-banned from GH around 2013 (i.e. before the Microsoft acquisition) for "creating a script that forced people to watch a library that [he] created", whatever that means: https://youtu.be/varf6oWaFtU?t=202 https://youtu.be/varf6oWaFtU?t=202

Aeolun 5y ago

That’s the craziest thing. What does Github have to do with the npm packages? Why would his account be suspended over an upload to npm?

toyg 5y ago
Github owns Npm, so I guess they feel entitled to be "NPM police" and nuke the rest of his output as collateral damage.
- shagie 5y ago
  NPM has been tightening up its publish and unpublish rules for over half a decade. https://thenewstack.io/the-kik-kerfuffle/ https://thenewstack.io/the-kik-kerfuffle/ That GitHub is now the owner of NPM doesn't change that policy and maturing of the environment. https://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm https://blog.npmjs.org/post/141577284765/kik-left-pad-and-np... > We dropped the ball in not protecting you from a disruption caused by unrestricted unpublishing. We’re addressing this with technical and policy changes.
laurent123456 5y ago
Seems reasonable to at least temporarily suspend his account till they know what's going on. His account might have been hacked, or he might have gone mad and sabotage more projects. Still a reminder though that GitHub is a private service and they are within their right to remove your work at any time for any reason, or for no reason.