Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NPM: 429 Too Many Requests

github.com

Post reply on HN
Print view View original

81–90 of 171 posts

Re: NPM: 429 Too Many Requests

#81

Post by Sharlin »

vhakulinen wrote: post #62
ccmcarey wrote: post #33

Earlier quoted context omitted.

It's disappointing. I commented saying as such - https://github.com/npm/cli/issues/836#issuecomment-586990343 > Posting memes/jokes in an issue wastes the time of people who actually need to be able to read through the issue. > Stop it. Use emoji reacts if you feel the need. In two minutes I have 24 dislikes and 13 likes. I think the introduction of emoji reactions was a bad idea, it gamifies the issues system.

> I think the introduction of emoji reactions was a bad idea, it gamifies the issues system. It depends on the community. I've seen many where the reactions are genuine and actually serves a purpose. From what I've seen, its almost always a popular js/node project that attracts this kind if behaviour like seen in this thread (based on my own observations). Last example is vscode's santa hat[1]. It seems that that thr…

JS/Node is the entry-level programming environment of the current era, like PHP used to be, and the community norms (or lack thereof) reflect that.

Re: NPM: 429 Too Many Requests

#82

Post by joeyrobert »

SirensOfTitan wrote: post #47

I’ve been considering checking node_modules into source control for some time now, has anyone else done that successfully? There would be a variety of benefits: 1. Eliminate redownload of packages on every CI build 2. Reduce the amount of gigantic IO operations from unpacking the tens-of-thousands of files sitting in node_modules. 3. Better security: code checked in can be audited better if not downloaded every singl…

Helps if you only have one platform you're developing on and deploying to (e.g. x86-64 Linux). If developing on macOS there can be Mac specific binaries installed, depending on the package.

Re: NPM: 429 Too Many Requests

#83

Post by rebane2001 »

zaphar wrote: post #12
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

I think this is partly a result of two things. 1. GitHub presents an interface that encourages Reddit style behaviour. 2. NPM outages are essentially a meme in themselves at this point. Both of them together create a perfect storm.

Hackernews presents an interface very similar to Reddit - it's more about the community than the interface

Re: NPM: 429 Too Many Requests

#84

Post by bovermyer »

zaphar wrote: post #12
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

I think this is partly a result of two things. 1. GitHub presents an interface that encourages Reddit style behaviour. 2. NPM outages are essentially a meme in themselves at this point. Both of them together create a perfect storm.

I have no comment on #2, as I don't play in that sandbox.

However, regarding #1... the interface allows people to post images in their comments on issues. This has a valid, useful reason - for showing screenshots of bugs, for example.

The problem is not the interface. The problem is the people using the interface.

Re: NPM: 429 Too Many Requests

#85

Post by matsemann »

easytiger wrote: post #48
matsemann wrote: post #14

Earlier quoted context omitted.

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

I mean there is a difference between having fun and conducting yourself in a professional manner where appropriate. With the increase in adoption of certain technologies (node etc) I have noticed a relationship with the people employed to work with them and their poor level of professionalism in the workplace with regard to their work and how they deal with other people (in the UK) and even how they dress. Similar ag…

I'm not saying I want memes everywhere, but since I'm spending 1/3 of my life at work I'd rather it be a good time.

> Go post memes on the LKML and see what happens

I think the seriousness (almost angry tone) in certain communities also is a disservice to attract new members. If I make my first PR in some project, it's easy too feel attacked when the reply is a negative one, albeit strictly professional. If it however has a more light-hearted tone and a bit more sandwiched fun-serious-fun one feels more welcome.

Re: NPM: 429 Too Many Requests

#86

Post by lqs469 »

warpech wrote: post #80
lqs469 wrote: post #76

Earlier quoted context omitted.

It's just a mirror service address, the NPM package is the same. Worrying too much about cybersecurity is a bit of a storm in a teacup.

Well, how do you know it's "just" a mirror service, and it is not using a zero-day to exploit your system, by installing a root-kit or copying your code to their servers? I agree that it's a valid concern.

In fact, you can compare the installed dependencies code line by line, Javascript won't be compiled anyway.

Re: NPM: 429 Too Many Requests

#87

Post by jamil7 »

tokai wrote: post #34
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

>It [...] discourages genuinely useful discussion of workarounds or progress. Does it though? Sounds like an opinion.

> Does it though? Sounds like an opinion.

Given that the comments in question add absolutely no value to the issue and instead insert a bunch of visual noise and fog then I'd argue it's not an opinion.

Re: NPM: 429 Too Many Requests

#88

Post by krab »

imtringued wrote: post #18

Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry

I think that's the issue of cost/reward. The cost is

- N developers can't work for X hours

- or the company can't release new versions due to CI dependency on the registry.

- or the registry removes a package you were using

- or the existing package contents changes to something malicious

BUT you pay this price very occasionally and if you're a small shop, the cost is often negligible.

On the other hand, maintaining your own mirror has very real costs even though they can be small. One time setup, hardware, sometimes license or hosted service fee, security upgrades. When there's a sponsor maintaining the central repository, having very good uptime and offering it for free, the marginal utility of a local mirror is quite small.

Re: NPM: 429 Too Many Requests

#89

Post by drfuchs »

MattRix wrote: post #36
lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

This is the first time I've seen "&c" used instead of "etc", I had to look it up. Interesting abbreviation!

It’s very old-school; check out newspapers and books printed a century or two ago.

Re: NPM: 429 Too Many Requests

#90

Post by w0m »

imtringued wrote: post #18

Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry

or Azure Artifacts, I use it for pip, but I assume the behavior is equivalent across.

https://docs.microsoft.com/en-us/azure/devops/artifacts/get-...

Post reply on HN