Nutzipper

[Nutzipper @nutzipper]

@MrSumfing What/Where are these societal structures?

[Nutzipper @nutzipper]

@jimscarver It’s good to know there are people like you in the world Jim.

[Nutzipper @nutzipper]

@jimscarver Damn, Jim, just tell me should I go buy a bunker or pour champagne. Or pour champagne in a bunker.

[Nutzipper @nutzipper]

@satnam6502 @docmilanfar Cross field expertise always was a driver for good solutions. It’s just now defense mode is prevailing imo. Hope it’s temporary, as lots of nowadays nonsense.

[Nutzipper @nutzipper]

@norpadon @JustDeezGuy Abandon “matrix” as well?

[Nutzipper @nutzipper]

War is always dead people.

[toly 🇺🇸 @toly]

War is now a job creator

[Nutzipper @nutzipper]

So if AGI is here why Toloka is still a thing?

[Nutzipper @nutzipper]

@toly If there won’t be shortage of open models well trained, what will drive demand for such high price?

[Nutzipper @nutzipper]

https://t.co/2CtQYfGujJ
this is why everyone has to have a toxic friend. I can do it for fair price - BAAS: bitching as a service.

[Nutzipper @nutzipper]

@jimscarver Can’t resist to calculate more

[Nutzipper @nutzipper]

@karpathy I have https://t.co/aME0IQw0bv exactly for that

[Nutzipper @nutzipper]

@matej_cerny That's nice, Scala introducing pointer arithmetics is another big step forward. Seems things are changing in the right direction.

[Nutzipper @nutzipper]

@brunoborges Quite bulletproof, such a security.

[Nutzipper @nutzipper]

lol. no-one foreseen this.

[Andrej Karpathy @karpathy]

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.

[Nutzipper @nutzipper]

@phildaian so whats next?

[Nutzipper @nutzipper]

@phildaian AI is making morons even bigger morons. Moron in the loop I'd say. Or on the hook.

[Nutzipper @nutzipper]

@BWarburg What’s not fun is to be surrounded by people who do not read.

[Nutzipper @nutzipper]

@metaweta Quite polarizing function

[Nutzipper @nutzipper]

@matej_cerny While very nice and OCAP would be more widespread - seems the solution is not that far from just hiding the whole functionality behind API call?

[Nutzipper @nutzipper]

Haven't hear much about CBDCs lately. Guess nothing is happening on that front.