Live data from Hacker News

Request Node lib used by 48k modules is now deprecated

github.com

101–110 of 135 posts

Re: Request Node lib used by 48k modules is now deprecated

#101
post #23

When did maintenance mode become deprecated? Why isnt that hyperbole?

They have marked the package as deprecated on NPM. https://docs.npmjs.com/cli/deprecate See the banner on this page: https://www.npmjs.com/package/request They are urging people to consider the enumerated alternatives.

>They have marked the package as deprecated on NPM.

Fair enough, the OP link didnt actually mention deprecated anywhere.

Re: Request Node lib used by 48k modules is now deprecated

#102

Earlier quoted context omitted.

Check forging. Was a big problem years ago when checks were widely used; These days they're almost dead so; (See 'Catch me if you can' film if you didn't already!);

In the UK if I write a check my bank checks with me before honouring it. They don’t just let you wave a piece of paper with numbers on it and empty the account lol.

Direct debits are surprisingly easy to set up in the uk.

Re: Request Node lib used by 48k modules is now deprecated

#103

Earlier quoted context omitted.

Those numbers are not secrets. They're literally just the bank's routing number and your account number. Using those numbers anyone can withdraw/deposit into that account. Madness isn't it?

My bank authenticates with me before honouring a check - is this not common?

I'm from the US and I've never heard of a bank verifying permission before releasing funds, they simply release the funds. As far as I know, US banks no longer check the signature (if they ever did) and no longer validate the date on the check (at least at my bank you can no longer post-date a check).

We recently lost a book of checks and the bank totally wigged out. They demanded that we close the account immediately and it took a decent amount of back and forth to talk them into waiting a week (we wanted existing checks to clear). To my mind, this implied that they did no validation on checks.

Re: Request Node lib used by 48k modules is now deprecated

#104
post #96

Earlier quoted context omitted.

In the UK fraud barely gets noticed by police. In USA there's serious jail time for check fraud

> In USA there's serious jail time for check fraud There's no serious jail time for it in the UK because the system doesn't let you do it in the first place!

The superior system then;

Re: Request Node lib used by 48k modules is now deprecated

#105
post #90

Earlier quoted context omitted.

Yea, makes me think of how every news blog reported mp3 as "dead" when the patent expired, when they should have been saying mp3 is now license free.

I don't think anyone really uses mp3 for audio compression anymore, though. There's FLAC, mp4 (AAC), and free Vorbis (which claims to be competitive with both); and DVDs and whatnot are still using AC3, EAC3, and various other Dolby Digital audio formats. Given that landscape, I don't know why you'd pick mp3.

Well most pirated music albums and songs are still in mp3s. Even bandcamp I chose mp3s for itune, maybe it's bias confirmation, but I don't believe mp3 went out of style.

Do you have a source for this? Is this audio compression for music production people or in general? I just can't see mp3 being out.

Re: Request Node lib used by 48k modules is now deprecated

#106
post #13

I have a question: Is it the responsibility of the package manager to keep users safe? By that, I mean, if there was a security vulnerability that the maintainers refused to fix, what would the process be? Should NPM refuse to install packages marked as deprecated, perhaps after a certain age of deprecation (say, 6 months)? Comparing this to the browser where I believe it is the expectation Firefox, Chrome, Safari et…

It is the responsibility of the developer who added the dependency, or the person who reviewed the PR that added the dependency.

If neither of those are around it is the responsibility of the person who took over either of those responsibilities or the person who now maintains that package.

If that person isn't around then it is unmaintained, and should not be used.

If that sounds complicated it is because it is. In any given package you might have 1-100ish people with responsibilities, but they also have sub-responsibles that they might not know about.

The package management system has no responsibility except to serve the exact version of the exact package you requested. If you expect anything more from them you are not looking for "package management" and npm is probably not the right place to look.

This is one of the reasons I try to not have transitive dependencies in JS projects.

Re: Request Node lib used by 48k modules is now deprecated

#107

Earlier quoted context omitted.

Those numbers are not secrets. They're literally just the bank's routing number and your account number. Using those numbers anyone can withdraw/deposit into that account. Madness isn't it?

My bank authenticates with me before honouring a check - is this not common?

I haven't actually used a check in a looong time so I don't know exactly what you mean.

I do know that I keep the numbers off a check from my checkbook I received when originally opening my bank account like 10 years ago in Lastpass. When sites that don't accept credit need payment information (my student loans mainly) I just copy/paste the numbers into their payment form and the money gets taken out of my account. No verification whatsoever, Nelnet is able to just withdraw the money from my account using those numbers.

I assume anybody with a debit processing backend or service can do the same if they have the routing/account #. It's kind of a wonder peoples money doesn't just disappear all the time really.

Re: Request Node lib used by 48k modules is now deprecated

#108
post #90

Earlier quoted context omitted.

Yea, makes me think of how every news blog reported mp3 as "dead" when the patent expired, when they should have been saying mp3 is now license free.

I don't think anyone really uses mp3 for audio compression anymore, though. There's FLAC, mp4 (AAC), and free Vorbis (which claims to be competitive with both); and DVDs and whatnot are still using AC3, EAC3, and various other Dolby Digital audio formats. Given that landscape, I don't know why you'd pick mp3.

I keep a library of music, ripped from cds I own. My master copy is FLAC, but I use mp3 for on-the-go copies because it is not patent encumbered and it is supported everywhere.

If you have a suggestion for an encoding+container that is will work out of the box both natively and in every major browser, across every major OS (Windows MacOS, Android, iOS and GNU/Linux, specifically distros like Fedora or Trisquel that don't ship nonfree codecs in their default repos), I will gladly switch to it.

Re: Request Node lib used by 48k modules is now deprecated

#109
post #41

Ok, I have been known to have strong opinions on HN, and each one is open to being changed and is rooted in extensive personal experience. I have said that comments are a code smell. I have written extensively in favor of decentralization and even formed two companies to promote it in increasingly sophisticated ways (qbix.com and intercoin.org) So I’m gonna say something that may get me downvoted... Package Managers…

I agree with a lot of the ideas behind what you say, but what is your solution?

That we should use less dependencies? Sure.

That we should review changes in our dependencies? Sure.

But If I were to take a nodejs app and move it from ubuntu version X to ubuntu version Y, node version Z to node version A, and update npm dependencies the code review itself would take me a year.

Is your point that we should only do this to npm dependencies?

Is this a wider problem with how we think about software development as never being finished instead of solving a problem and moving on to the next? Yes.

Re: Request Node lib used by 48k modules is now deprecated

#110

Earlier quoted context omitted.

> You can't just take money out at a bank by giving a bank account number, surely? That's exactly what a check is. It's a legal document that says "I give you X dollars from account Y." You can use a napkin instead of a the pre-filled sheets of paper your bank sends you, and it's still the same legal document. Typically your signature is checked against one on file, but only for large transactions, and of course hand…

Right, but the bank is still entitled to check with me before handing over the cash. They have no way of knowing that I signed the contract. Account numbers and squinting at a signature isn't any kind of proof!

> the bank is still entitled to check with me before handing over the cash.

They're allowed to, but have no (legal or socially expected) requirement to do so. I've never heard of a bank doing so for small (<$10k or so) amounts, and then only if fraud alerts are already present.

Post reply on HN