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

141–150 of 269 posts

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

#141

Post by hinkley »

_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

At the dawn of the search engine age I was in Japan, and so I spent some time not being able to learn about shitake mushrooms, as was a common western spelling at the time (they are not shi-ta-ke mushrooms, they are in fact shi-i-ta-ke mushrooms, hence the spelling change, even though we still pronounce them wrong).

You couldn’t say shit on the internet. I mean what the fuck.

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

#142

Post by marcosdumay »

quesera wrote: post #92
reuben364 wrote: post #54

Earlier quoted context omitted.

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

gzip?

A random binary string will be accepted until something between 4 and 8 times the size.

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

#143

Post by zb3 »

ezekg wrote: post #128
lopkeny12ko wrote: post #120

Earlier quoted context omitted.

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.

Wasn't expecting so much candid feedback today. There was a Launch HN yesterday that had a 3D rubik's cube on their home page. It was literally pointless. But kind of neat. But you probably hated that as well, if I could assume. But I say that to point out that lots of companies do it, sometimes simply because we can (just look at Stripe and GitHub). I think the lava lamp effect is cool. The perf issues can and will…

I'm sorry, but what should just. be a _progressive enhancement_ in this case completely ruins the user experience for me. However, I'm probably not your target audience, I'm just commenting on this trend in general.

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

#144

Post by jmull »

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.

> keyword moderation is terrible and only affects the language(s) you know about.

It doesn't seem that hard for npm to review lists of the most common keyword searches and identify the ones strongly associated with piracy (or other things negative for their business).

I agree, though, that keyword moderation is pretty terrible. It might work from npm's perspective, in that it might be annoying enough to pirates that they'll find some more convenient place to upload/download. I don't think it will have any overall impact on privacy though.

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

#145

Post by RobotToaster »

codetrotter wrote: post #38
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

Time to change the name of your business to kexgen I guess.

KeyJen.

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

#146

Post by Nifty3929 »

jeffhuys wrote: post #106
vbezhenar wrote: post #81

Earlier quoted context omitted.

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.

"colgate" is rude. "bra" is rude. "maxipad" is rude. "masterbaiter" is rude and funny. "amputee" is rude, even. This goes far...

Why is "amputee" rude?

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

#147

Post by jwestbury »

jazzyjackson wrote: post #103
PurpleRamen wrote: post #63

Earlier quoted context omitted.

Maybe it's time to convert base64 to high UTF8-areas. I guess there won't be any keyword-filter yet for ancient egyptian hieroglyphs. I'm curious whether there are already emoji-filters...

https://github.com/qntm/base32768 https://github.com/keith-turner/ecoji :D

> ecoji

In a similar vein, a former colleague of mine created this Python package: https://pypi.org/project/piickle/

It's functionally the same as pickle, except it binary-encodes the data with spaces and pickle emoji.

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

#148

Post by RobotToaster »

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.

"see boss, nothing is using the word "keygen", so obviously we have removed all keygens".

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

#149

Post by Daneel_ »

ezekg wrote: post #128
lopkeny12ko wrote: post #120

Earlier quoted context omitted.

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.

Wasn't expecting so much candid feedback today. There was a Launch HN yesterday that had a 3D rubik's cube on their home page. It was literally pointless. But kind of neat. But you probably hated that as well, if I could assume. But I say that to point out that lots of companies do it, sometimes simply because we can (just look at Stripe and GitHub). I think the lava lamp effect is cool. The perf issues can and will…

I appreciate you engaging with commenters on this, it’s nice to see.

From my perspective I agree with a lot of the other commenters - it’s just design for design’s sake. It’s an expensive way to add minor visual flair that heavily degrades the experience for a sizeable number of users. In terms of value provided to the user: it’s basically zero, or often worse than zero.

Personally, it feels over-designed, which the stretched font for the headings really reinforces. I’d drop the shader, re-evaluate your font choice for the headings, and focus on layout and readability a little more - using the site on my iPhone feels really cramped and like the whole page is getting cut off on the right-hand side constantly. I can’t scroll horizontally to see the rest of the code, for example.

I do like the little text-flicker/flipboard animation on the “keygen” logo though. That looks clean and well-suited to the theme of the site.

Post reply on HN