chip
2.7K posts


Core - AI Workspace Launching open-source + hosted (100% free) next week.




Your headphones just became a personal translator in 70+ languages. 🎧✨ Google Translate’s “Live translate” with headphones is officially on iOS. We're also expanding this capability to more countries around the world for both @Android and iOS users. To try it, open the Translate app, tap “Live translate” and connect your headphones.

✨ To inspire more people to go build something now that we have AI to help us (especially non-tech people, cause I still know so many who are scared of building something): I added a [ BUILD IT ] button to IdeasAI.com It's like a mini-Lovable/Replit/v0: Any idea you see you like, you can click [ BUILD IT ], and it will use Opus 4.6 to build a landing page for it And then you can download the code it generated It's not a full startup of course, but a nice preview of what it can be, to give you an idea and inspire you to build it out further The code is live streamed also so you can see it being built 😊 Ironically this itself took me 1 hour to build with AI too Completely free and I pay for the tokens (please don't abuse it :D)






I ordered a $10,000 Mac Studio to test local AI models for my firm. And I sent it back. The tech wasn't bad. It just wasn't ready for what I needed it to do. I’m interested in local for one main reason: data security and privacy. Actually keeping client information on our machines instead of sending it out to AI labs. I spent a weekend running it through: - Journal entries - Tax diagnostics - Real accounting scenarios I had to prompt the same question six to eight times before I got a usable answer. It felt like a second job. The people saying AI will replace accountants in 12 months have not actually tried to use it for accounting. I am not against it. I've been testing it constantly. Being honest about where the technology actually is helps more than pretending it is further along than it is. When local inference gets sharp enough to run smoothly on firm hardware, I'll be there.




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.



