Earlier quoted context omitted.
It's working fine for me on windows and firefox device: undefined fps: 30 gpu: "intel mesa dri intel hd graphics 400" isMobile: false tier: 2 type: "BENCHMARK"
I'm questioning whether or not I should continue into the realm of gamedev... the amount of "works on my igpu from 2015 in low power mode" and "stutters on my rtx 4070 ti" here is making me laugh out loud.
NPM won't publish packages containing the word keygen
171–180 of 269 posts
Re: NPM won't publish packages containing the word keygen
#172Re: NPM won't publish packages containing the word keygen
#173I 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
Re: NPM won't publish packages containing the word keygen
#174Earlier 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…
Re: NPM won't publish packages containing the word keygen
#175I 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
Everyone did, but Microsoft continues to be terrible. Replace Edge with GitHub or npm or vscode and see what a trap this is. - npm sends images you view online to GitHub - vscode bakes a VPN into npm and turns it on - The dark defaults of npm - vscode records editing (browsing) history in InPrivate mode Azure or OpenAI seem even worse. And Windows has a lot of Edge-like things built into it, including how it tries to…
Re: NPM won't publish packages containing the word keygen
#176Earlier 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.
The pixel shader is cool, but consumes too much resources. On my 1080Ti, uses about 20% of GPU to render, which is too expensive for such a simple graphics. I’ve looked at the source, and it seems you’re doing too much computations there. Metaballs are usually rather simple, and they don’t require any trigonometric functions. Compute something like `sum( ball.z / length( pixel - ball.xy ) )` and apply the threshold.…
I sent you an email with a job offer.
Re: NPM won't publish packages containing the word keygen
#177Re: NPM won't publish packages containing the word keygen
#178I 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
Unrelated question, on your site, how do i close the cookie banner? On my phone it obscures most of the screen and i can’t dismiss it.
Re: NPM won't publish packages containing the word keygen
#179Earlier quoted context omitted.
Have you had any publishing issues? My last successful publish on this package was 3 months ago, and I started noticing issues with deploys a few weeks back. Three fun days of CI/CD pipeline debugging to get to this..
After digging around, I found the org and I do own @keygen. And I was able to publish an empty package to the org: https://www.npmjs.com/package/@keygen/js . But it doesn't look like it's searchable, unless there's a caching issue.
Re: NPM won't publish packages containing the word keygen
#180I 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