I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do. [^0]: https://keygen.sh
NPM won't publish packages containing the word keygen
121–130 of 269 posts
Re: NPM won't publish packages containing the word keygen
#122Earlier quoted context omitted.
Interesting. I wonder if this is a retina display issue. I just pushed out a change that renders the shader at standard resolution even if the device has a retina display. I don't have a retina display on any of my devices except a 2019 MBA and it renders fine on it. I wonder why.
> I wonder if this is a retina display issue I'm using an external monitor running at 5120x1440 (Samsung, not retina) only, and am experiencing the the same on Firefox. At least not retina exclusive.
Re: NPM won't publish packages containing the word keygen
#123I thought buttbuttination taught everyone how incredibly stupid this is 25-30 years or so ago already? But no. Just a few years ago I tried to enter an answer into a Hungarian Q&A site recommending to take the Algeciras-Tangier ferry and the answer was refused. https://en.wiktionary.org/wiki/geci
- npm sends images you view online to GitHub
- vscode bakes a VPN into npm and turns it on
- The dark defaults of npm
- vscode records editing (browsing) history in InPrivate mode
Azure or OpenAI seem even worse. And Windows has a lot of Edge-like things built into it, including how it tries to get users to use Edge.
Re: NPM won't publish packages containing the word keygen
#124Re: NPM won't publish packages containing the word keygen
#125Earlier 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.
device: undefined
fps: 30
gpu: "intel mesa dri intel hd graphics 400"
isMobile: false
tier: 2
type: "BENCHMARK"
Re: NPM won't publish packages containing the word keygen
#126Earlier 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.
Re: NPM won't publish packages containing the word keygen
#127I must be missing something obvious. What's malicious about the word "keygen"? What's the issue with ssh-keygen? gpg --gen-key?
Piracy. Programs that generate activation codes for proprietary software are called keygens. They usually come with interesting musical accompaniments.
Re: NPM won't publish packages containing the word keygen
#128Earlier 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.
I think the lava lamp effect is cool. The perf issues can and will be fixed.
Re: NPM won't publish packages containing the word keygen
#129Earlier quoted context omitted.
Or, again, turn it off and avoid the whole class of issues, wasted time and asking random HN folk for debug logs.
Don’t listen to random comments on hacker news. It looks cool OP. Don’t throw out the whole thing for a few bugs
Until someone turns up with a new combo where it doesn't work. Because judging by the comments, this seems to be a janky piece of code that isn't well understood.
"Turn it off" (or rather, "rip it out, and throw it away" is good advice. If there is even a slight chance this might come back to haunt you and screw the user experience, it isn't worth it. If your animation is more important than avoiding a horrible user experience, well, that's kind of useful for your customers I suppose.
Re: NPM won't publish packages containing the word keygen
#130Earlier 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.
It's working fine for me on windows and firefox device: undefined fps: 30 gpu: "intel mesa dri intel hd graphics 400" isMobile: false tier: 2 type: "BENCHMARK"