genndelf

Gaussian splats truly is one of the coolest things that’s enabled by modern cameras and computing power.

yo nano banana pro f---ked right now

yo what the fuck LOOOOOOOOOOL

humans taking AI's job

they be acting like a gacha game company right now. nerf the existing characters whenever a new character is about to drop.

my boi Naruto has always been multi-agentic

Software engineers don't get paid to write code; they get paid to solve problems. The faster you realize this, the sooner you'll stop being afraid that AI will replace you and the better your career will be.

@0xlelouch_ I seem to have logged into LinkedIn by mistake.

Vibe coding is more addictive than any video game ever made (if you know what you want to build).

excitement de-intensified ps - saw the date

excitement intensified

The future of Three.js is WebAssembly

Bad Apple but it's displacing its own lyrics with pretext

anyhoo, thoughts on SLMs coming soon

self jerk and you'll be illusionally happy forever

the curse of getting old is realising pain more than priorities

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

Introducing TurboQuant: Our new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup, all with zero accuracy loss, redefining AI efficiency. Read the blog to learn how it achieves these results: goo.gle/4bsq2qI

NVIDIA's Kimodo is the release of the week 🔥 Prompt the timeline whatever your want like: "a person walks forward" → "a person starts jumping", hit Generate, and watch a 3D character do it in seconds (700hrs of pro mocap training. Works on human + robot skeletons. Super fast + free to use on HF)