So,... has anyone with this issue actually contacted the NPM team and asked what is is about?
I have, yes. Awaiting a response.
NPM won't publish packages containing the word keygen
101–110 of 269 posts
Re: NPM won't publish packages containing the word keygen
#102Earlier 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.
Your homepage needing a shader is at least a hot-pink flag for the whole company. Pretty janky here on Vivaldi as well unless I scroll really slowly.
Re: NPM won't publish packages containing the word keygen
#103Earlier 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”
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...
Re: NPM won't publish packages containing the word keygen
#104Earlier 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.
Your homepage needing a shader is at least a hot-pink flag for the whole company. Pretty janky here on Vivaldi as well unless I scroll really slowly.
What do you mean by this? I wrote the shader because gamedev is an interest of mine, and I wanted to give writing a fragment shader a try for the redesign.
Re: NPM won't publish packages containing the word keygen
#105It's the 80s all over again. But instead of puritanical sysops it's huge multinational corporations. Maybe we'll just call them k3yg3n5.
𝔎𝔢𝔶𝔤𝔢𝔫
𝕶𝖊𝖞𝖌𝖊𝖓
𝐊€ｙģ€ℕ
𝓚𝓮𝔂𝓰𝓮𝓷
𝒦𝑒𝓎𝑔𝑒𝓃
𝕂𝕖𝕪𝕘𝕖𝕟
Ｋｅｙｇｅｎ
ᛕꫀꪗᧁꫀꪀ
Kꫀׁׅܻᨮ꫶ׁׅ֮ᧁׁꫀׁׅܻꪀׁׅ
K⃞ e⃞ y⃞ g⃞ e⃞ n⃞
Ⓚⓔⓨⓖⓔⓝ кєץﻮєภ Nguyen ᏦᏋᎩᎶᏋᏁ kēฯງēຖ 𝐊𝐞𝐲𝐠𝐞𝐧 𝗞𝗲𝘆𝗴𝗲𝗻 𝘒𝘦𝘺𝘨𝘦𝘯 𝙆𝙚𝙮𝙜𝙚𝙣 𝙺𝚎𝚢𝚐𝚎𝚗
Re: NPM won't publish packages containing the word keygen
#106Earlier 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…
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...
Re: NPM won't publish packages containing the word keygen
#107Earlier 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.
Works horrendously bad on Firefox, works great on Safari/Orion... Macbook Pro M1
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.
Re: NPM won't publish packages containing the word keygen
#108I'm assuming keygen must not be part of the package name specifically, right? Because keygen can be part of contained JS content without probs, as the sgml package is demonstrating (containing the legacy keygen element as part of its embedded HTML DTD grammar).
But I'm still curious why keygen would be problematic as part of a package name?
Re: NPM won't publish packages containing the word keygen
#109I 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
Don't get me started
Re: NPM won't publish packages containing the word keygen
#110I 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
Also known as a clbuttic error.
For the uninitiated, the origin of (the popularity of) clbuttic: https://thedailywtf.com/articles/The-Clbuttic-Mistake-