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

NPM won't publish packages containing the word keygen

mamot.fr

Post reply on HN
Print view View original

201–210 of 269 posts

Re: NPM won't publish packages containing the word keygen

#201

Post by franky47 »

evv wrote: post #199

Oh. As the creator and reluctant maintainer of npm's "ssh-keygen", this is awkward! First question: does this mean I won't be able to publish patches to the package? Why do I not want this package under my control? The original package simply calls spawn for your real `ssh-keygen` with the appropriate arguments. No real problem, (although there is very little value here). But a contributor added support for Windows b…

> But a contributor added support for Windows by uploading opaque binary builds for Windows

> "only" downloaded ~1600 times/week

This begs for an audit.

Re: NPM won't publish packages containing the word keygen

#202

Post by throwaway290 »

zelse wrote: post #184
jorvi wrote: post #169

Earlier quoted context omitted.

Filters like that are so trivial to bypass on a higher level too. Look at how many gamer or forum tags are “Lovecraft’s Cat”. And good luck catching those cases on a non-manual basis.

I once happened across a Github where all the repos were subtle little bits of anti-Semitic cant relating to the Holocaust. More than subverting them, they also often function as dog-whistles for fellow travelers. (For those not getting the specific one used above, Lovecraft had a black cat and a common name for black cats at the time combined a now nigh-unprintable racial slur for black people with the word 'man'.)

Github has a reporting feature!

Re: NPM won't publish packages containing the word keygen

#203

Post by rcxdude »

ezekg wrote: post #112
spdustin wrote: post #78

Earlier quoted context omitted.

With respect, all of that for some bokeh? Is it worth it for y’all? Do you know how many folks just leave when the stuttering starts?

The entire lava lamp effect is a shader, not just the bokeh. :) I haven't noticed any drop in registrations, conversions, or any noticeable differences in traffic patterns after launching the redesign, so I'm not sure if this is actually happening. Though it's a valid concern and issue, and I do want to fix it. And I appreciate all the reports. I think it may be a retina resolution issue, but could be wrong. On launc…

Another danger here is testing with the website being the only thing on the PC: some people use their computers like that but many others will have many different things open at once: just because it can run at an acceptable FPS on the detected hardware doesn't mean the resource use is acceptable on a system which is multitasking. I usually have >100 tabs in my browser and at least 20 of which are loaded: they cannot all demand what your site demands, even though the hardware is quite high-end.

Re: NPM won't publish packages containing the word keygen

#205

Post by internetter »

ezekg wrote: post #58
xavxav wrote: post #49

Earlier quoted context omitted.

Unrelated, but your homepage has very bad FPS using firefox on mac due to the animation. Once I manage to scroll it works quite well.

Thanks. That shader doesn't seem to play nicely with some GPUs and I'm still working on edge cases. If possible, could you look at your console logs and email me your specs? They should be logged. Email is in bio. It should be doing automatic categorization of the GPU to determine render quality, but maybe something's still incorrect there.

It's very laggy for me, and I'm on high end hardware.

{"CANVASES":2,"GPU":{"fps":209,"gpu":"apple m2","isMobile":false,"tier":3,"type":"BENCHMARK"},"RESOLUTION_RATIO":2,"BLOB_COUNT":20,"BLOB_AMPLITUDE":"52.60","BLOB_RADIUS":"2.54","POSITION_X":"4.43","POSITION_Y":"1.72","RANGE_X":"4.64","RANGE_Y":"6.51","SPEED_X":"9.60","SPEED_Y":"4.51"}

Re: NPM won't publish packages containing the word keygen

#206

Post by evv »

franky47 wrote: post #201
evv wrote: post #199

Oh. As the creator and reluctant maintainer of npm's "ssh-keygen", this is awkward! First question: does this mean I won't be able to publish patches to the package? Why do I not want this package under my control? The original package simply calls spawn for your real `ssh-keygen` with the appropriate arguments. No real problem, (although there is very little value here). But a contributor added support for Windows b…

> But a contributor added support for Windows by uploading opaque binary builds for Windows > "only" downloaded ~1600 times/week This begs for an audit.

Yes.

If npm lets me publish a new version, I'd be happy to remove the Windows binaries.

Re: NPM won't publish packages containing the word keygen

#207

Post by Dylan16807 »

rcxdude wrote: post #203
ezekg wrote: post #112

Earlier quoted context omitted.

The entire lava lamp effect is a shader, not just the bokeh. :) I haven't noticed any drop in registrations, conversions, or any noticeable differences in traffic patterns after launching the redesign, so I'm not sure if this is actually happening. Though it's a valid concern and issue, and I do want to fix it. And I appreciate all the reports. I think it may be a retina resolution issue, but could be wrong. On launc…

Another danger here is testing with the website being the only thing on the PC: some people use their computers like that but many others will have many different things open at once: just because it can run at an acceptable FPS on the detected hardware doesn't mean the resource use is acceptable on a system which is multitasking. I usually have >100 tabs in my browser and at least 20 of which are loaded: they cannot…

How many tabs are simultaneously visible? An animation in a non-selected tab won't get much in the way of resources, so the number of loaded tabs shouldn't be a big factor.

Re: NPM won't publish packages containing the word keygen

#208

Post by olaulaja »

lopkeny12ko wrote: post #120
ezekg wrote: post #58

Earlier quoted context omitted.

Thanks. That shader doesn't seem to play nicely with some GPUs and I'm still working on edge cases. If possible, could you look at your console logs and email me your specs? They should be logged. Email is in bio. It should be doing automatic categorization of the GPU to determine render quality, but maybe something's still incorrect there.

With all due respect, this is possibly the dumbest rebuttal I've heard. Why do I need a powerful GPU or even need my GPU to waste compute cycles just to view a webpage? Just get rid of it entirely. The visual flair is not adding any value. It's a performance drag, highly distracting, and serves no useful purpose whatsoever. This "trend" in modern web design is truly infuriating.

So I took a look at the actual shader, and it really should not require anything powerful (decade old, worst-you-can-get hardware might struggle). A much more likely explanation (that the gp is alluding to but didn't explicitly say) is that the issue is related to your GPU drivers or related software. These are often buggy and/or hit a slow path for whatever reason. This is almost guaranteed to happen for some browser/os/hardware/driver combo (of which there are _many_) and you seem to have drawn today's short stick.

The animation itself looks fine, its slow enough that it doesn't feel distracting. Just a bit of flavor.

Its mostly just a few calls to a cheap noise function and no footguns I can see. Also hurrah for dev tools and open text formats! If you're looking for better performance, it looks like the noise could be precomputed (the same blob always gets the same noise)". Might be faster, might just hit more bugs.

Re: NPM won't publish packages containing the word keygen

#209

Post by TheFreim »

ezekg wrote: post #61
sixothree wrote: post #46

Earlier quoted context omitted.

GenKey?

Our CLI already uses genkey as a command so unfortunately that's no bueno: keygen genkey Can't do genkey genkey. That's just weird...

I mean, you could just flip it around?

    genkey keygen
Post reply on HN