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

71–80 of 269 posts

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

#71

Post by ezekg »

djbusby wrote: post #66
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.

Just turn it off.

It does turn off when it detects a low-end or integrated GPU. But something may not be working correctly, or is getting miscategorized.

That's why the debug information would help.

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

#72

Post by djbusby »

ezekg wrote: post #71
djbusby wrote: post #66

Earlier quoted context omitted.

Just turn it off.

It does turn off when it detects a low-end or integrated GPU. But something may not be working correctly, or is getting miscategorized. That's why the debug information would help.

Or, again, turn it off and avoid the whole class of issues, wasted time and asking random HN folk for debug logs.

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

#73

Post by aurareturn »

sneak wrote: post #5

NPM is owned by Microsoft, who sell proprietary software, the kind that keygens are made to defeat. Don't expect to see KMS spoofers on GitHub anytime soon for the same reason.

Microsoft was probably also traumatized by keygens for PC games in the 2000s - 2010s.

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

#74

Post by retrocryptid »

franky47 wrote: post #20
_ugfj wrote: post #15

I 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

The Scunthorpe problem all over again. https://en.wikipedia.org/wiki/Scunthorpe_problem

wait... are you implying that "k*ygen" is a dirty word?

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

#75

Post by BudaDude »

djbusby wrote: post #72
ezekg wrote: post #71

Earlier quoted context omitted.

It does turn off when it detects a low-end or integrated GPU. But something may not be working correctly, or is getting miscategorized. That's why the debug information would help.

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

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

#76

Post by mynameisvlad »

sneak wrote: post #5

NPM is owned by Microsoft, who sell proprietary software, the kind that keygens are made to defeat. Don't expect to see KMS spoofers on GitHub anytime soon for the same reason.

There’s several KMS-based activation scripts and servers on GitHub. Did you even take a second to do the briefest of checks before saying that so confidently?

https://github.com/topics/kms

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

#78

Post by spdustin »

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.

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?

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

#79

Post by retrocryptid »

ezekg wrote: post #19

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

Nice to see an alternative to FlexLM. That package was the bane of my existence when we had a bazillion RS/6000s running AIX. And when I worked at Borland, I campaigned (unsuccessfully) against its use.
Post reply on HN