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

81–90 of 269 posts

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

#81

Post by vbezhenar »

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…

Here's list of substrings World of Warcraft checks in character names.

https://wow.tools/dbc/?dbc=namesprofanity&build=10.0.5.47660...

They spent great effort to build this list.

Most character names in the game are lame anyway and some are just offensive or inappropriate.

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

#83

Post by ptspts »

ezekg wrote: post #56
ijustlovemath wrote: post #31

Earlier quoted context omitted.

unrelated to your question: Your website's very pretty, but doesn't scroll horizontally on mobile. It also looks like there might be a bug in the code sample - where does "fingerprint" come from?

Why would you want to scroll horizontally? Or are you referring to the code samples? It's only a code "sample" (i.e. non-working just to show off the platform), so fingerprint would likely come from something like https://github.com/denisbrodbeck/machineid . Full examples are available in the Go SDK docs [^0]. [^0]: https://github.com/keygen-sh/keygen-go

Please enable horizontal scrolling. I wanted to view the code sample on mobile.

Code samples are usually more relevant than marketing messages.

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

#84

Post by cldellow »

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.

I'm not the person you replied to, but it's janky for me, too.

Console logs: device: undefined, fps: 60, gpu: amd renoir, isMobile: false, tier: 3

FWIW, my laptop is a relatively beefy 2021 model (granted, with integrated GPU). For a business that's not about 3D rendering, spending an innovation token on making sure your landing page can have a smooth background animation seems like it's playing on hard mode.

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

#85

Post by anthk »

mikrl wrote: post #28
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

Try using a Russian Cyrillic е or к or у Sure no one will be able to install the app from the CLI (unless there is a bug in npm’s parsing logic) but you should be fine distributing hyperlinks to skim-readers ;)

Unicode works under xterm and urxvt since long ago, also people can just copy and paste...

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

#86

Post by sandyarmstrong »

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.

Yeah this feels totally broken on my M1 Pro running Ventura.

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

#87

Post by alkonaut »

Waterluvian wrote: post #29

Keyword moderation feels like an unspirited attempt by developers to satisfy incompetent managers telling them to get other incompetent managers, upset about piracy, off their backs. I don't believe anyone involved actually thinks this will make a difference. It's just to address a complaint.

That's almost certainly the case. "What can we do that has an observable effect we can demonstrate as us being responsive, but doesn't have a significant cost [to ourselves]".

It's the same as any other "this shouldn't be done, but a manager asks me to do it". If you aren't ready to die on that hill as I would, then there is nothing you can do. I'd easily take that fight but that's coming from a very privileged position (i.e., I'd not risk not having food on the table if I said no when a manager asked me to add keyword moderation or a dark-pattern cookie banner).

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

#88

Post by anthk »

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.

KMS it's a literal module from Linux/BSD tied to the display technology.

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

#89

Post by loeg »

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 stutters on an M1 Macbook running Chrome, for example.

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

#90

Post by namibj »

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.

Just use a r-ANS entropy coder with feedback skipping symbols that would result in a ban from being possible to encode at that moment... I think.

Unless I've gotten confused about the limits of dynamic prediction abilities in ANS.

I think it's just that the encoder and decoder run in opposite directions through the encoded symbols, but read-ahead during decoding shouldn't be a problem...

Post reply on HN