Earlier quoted context omitted.
The Scunthorpe problem all over again. https://en.wikipedia.org/wiki/Scunthorpe_problem
wait... are you implying that "k*ygen" is a dirty word?
Dirty word in the context of security, copyright liability, etc.
NPM won't publish packages containing the word keygen
111–120 of 269 posts
Re: NPM won't publish packages containing the word keygen
#112Earlier 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.
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?
The entire lava lamp effect is a shader, not just the bokeh. :)
I haven't noticed any drop in registrations, conversions, or any noticeable differences in traffic patterns after launching the redesign, so I'm not sure if this is actually happening. Though it's a valid concern and issue, and I do want to fix it. And I appreciate all the reports. I think it may be a retina resolution issue, but could be wrong.
On launch day, everyone loved the effect (it goes along with the new logo) and only a couple people said it performed badly, but they were on exotic devices.
I may have caused this a few days ago when I enabled rendering at retina resolution for tier 3 devices. What I wasn't expecting was so many tier 3 devices that aren't really what I'd consider "tier 3." I was expecting all tier 3 devices to be gaming-level GPUs.
I guess I should have read the source [^0] more closely and I could've avoid this.
Re: NPM won't publish packages containing the word keygen
#113Earlier quoted context omitted.
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.
Because it's not bad enough to be a red flag but it does make me wary of the company's priorities. You used a complicated shader to make a scroll bar that doesn't scroll, which may as well have been a static background image, and half-visible janky blobs in the background I thought at first were eye floaters. The crushed font looks like a rendering error and the e's and s's looking identical made me stare at the word "businesses" because I swore it was misspelled. I do have to say the color scheme is gorgeous though.
Re: NPM won't publish packages containing the word keygen
#114Earlier 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.
How do you imagine user conversations take place, if not from "random HN folk"?
Do you want an appointment? A lab?
Re: NPM won't publish packages containing the word keygen
#115Earlier 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.
GPU: {device: undefined, fps: 342, gpu: 'apple m1 pro', isMobile: false, tier: 3, type: "BENCHMARK"}
Despite the supposedly high FPS it's very jumpy/laggy in Firefox, though fast in Safari.
Re: NPM won't publish packages containing the word keygen
#116keyword 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…
My favorite is Fark's word-changing filters and their unintended side effects. The no-no words are scanned across whitespace and reversed, and any hits get translated to the approved word. "Shit" becomes "Shiat", the N word becomes "nubian", etc
Every so often someone will find their sentence that contains something like "I will have ham or egg in my sandwich" becomes "I will have ham onaibun my sandwich"
Re: NPM won't publish packages containing the word keygen
#117Re: NPM won't publish packages containing the word keygen
#118Earlier quoted context omitted.
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.
Thanks for the feedback. Makes total sense. I'll make this change.
(I wasn't expecting so much traffic and feedback today lol)
Re: NPM won't publish packages containing the word keygen
#119Earlier quoted context omitted.
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.
> I wonder if this is a retina display issue
I'm using an external monitor running at 5120x1440 (Samsung, not retina) only, and am experiencing the the same on Firefox.
At least not retina exclusive.
Re: NPM won't publish packages containing the word keygen
#120Earlier 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 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.