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

91–100 of 269 posts

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

#91

Post by richrichardsson »

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 also horrifically slow on Chrome macOS:

    {
        "fps": 130,
        "gpu": "amd radeon pro 5300m",
        "isMobile": false,
        "tier": 3,
        "type": "BENCHMARK"
    }
Definitely wasn't 130 FPS and made the whole page stuttery.

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

#92

Post by quesera »

reuben364 wrote: post #54
vmilner wrote: post #39

Earlier quoted context omitted.

I remember a conversation with some using an in-house file transfer system “Oh you won’t be able to send more than X GBytes, at that point the chances that the base64 encoding contains a banned rude word become too high, and the transfer will fail”

I wonder what the optimal encoding is given a list of banned words for any substring of a message.

gzip?

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

#93

Post by arp242 »

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.

When you emailed me about this a few weeks ago I played around a bit with the shader, and just creating fewer blobs made the problem go away (reducing "for (int i = 0; i Good to hear it's not just me though (and the effects also aren't disabled for me either).

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

#94

Post by babypuncher »

hbn wrote: post #25
withinboredom wrote: post #8

keyword moderation is terrible and only affects the language(s) you know about. It doesn't actually prevent the content (the goal of these types of filters) from being served. It'd be like a virus scanner preventing a program from running because it had the name 'virus' in it ... which would prevent itself from running -- probably.

My favorite is the online name censoring in video games. Dark Souls infamously just does a straight check of any string match within the name against a big list of no-no words. So in this fantasy game where everyone is running around as a knight, anyone who has "knight" in their game will appear as "k***ht" to other players. There's also a famous image I've seen online from another game where the guy's name was Nasse…

It makes sense for Dark Souls games because multiplayer is a lot less optional. Player names will appear in your game, and turning this feature off really hurts the experience.

Their hamfisted approach leaves a lot to be desired. I have a feeling it is a product of being designed and implemented by non-native English speakers.

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

#95

Post by Etrnl_President »

bitwize wrote: post #50
lopkeny12ko wrote: post #32

I must be missing something obvious. What's malicious about the word "keygen"? What's the issue with ssh-keygen? gpg --gen-key?

"Keygens" are programs that generate valid product keys in order to crack software copyright protection. Under the DMCA or similar laws in many other countries, they are illegal to use, create, or distribute.

Jokes on them, I run a keygen almost daily, for software I don't have, because I like the cool chiptune.

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

#96

Post by jeffhuys »

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.

Works horrendously bad on Firefox, works great on Safari/Orion...

Macbook Pro M1

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

#97

Post by jeffhuys »

loeg wrote: post #89
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.

It stutters on an M1 Macbook running Chrome, for example.

M1 running Safari (specifically Orion) works 60fps... How?!

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

#98

Post by willsmith72 »

vmilner wrote: post #39
hbn wrote: post #25

Earlier quoted context omitted.

My favorite is the online name censoring in video games. Dark Souls infamously just does a straight check of any string match within the name against a big list of no-no words. So in this fantasy game where everyone is running around as a knight, anyone who has "knight" in their game will appear as "k***ht" to other players. There's also a famous image I've seen online from another game where the guy's name was Nasse…

I remember a conversation with some using an in-house file transfer system “Oh you won’t be able to send more than X GBytes, at that point the chances that the base64 encoding contains a banned rude word become too high, and the transfer will fail”

This is awesome

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

#99

Post by devmor »

zirgs wrote: post #70
devmor wrote: post #17

Reminds me of the times I've seen junior devs changing "password" to "wordpass" to bypass automated commit checks for sensitive data. These kinds of checks are so trivially defeated, the only people they actually stop is people trying to do legitimate work.

Tbh in this case that check is useful. It prevents devs from accidentally including passwords in their commits.

Not a perfect example, but the point is that it's not stopping anyone from doing anything malicious.
Post reply on HN