Serve Robotics, which runs most of LA’s sidewalk delivery robots, lost $101.4 million in 2025,
($371,286 annual net loss for every robot it had out making deliveries.)
The first advantage its investor deck lists for the robots is “No driver wages.”
This is a slide from that presentation
@NielsRogge@togethercompute@FireworksAI_HQ@PrimeIntellect They're great businesses and I like the teams I've met so far, but only one out of the four has published substantial artifacts to be considered a neolab (in the Silicon Valley sense at least).
My office is hiring an Artificial Intelligence Policy Fellow to help shape AI legislation and track AI developments in the private sector as Congress works to keep pace with the technology.
Experience in AI, policy research, or national security is encouraged.
We found DeepSeek V4.1 Flash 1017 beats GPT 6 Sol on our multi-step offensive cybersecurity task. Sol was tested via the Daybreak trusted access program.
We have been building a cybersecurity benchmark based on simulated corporate networks. This is a valuable indicator for the cyber-risk a model poses if in the hands of a bad actor. We plan to make the full evaluation public in the coming weeks but wanted to share our first immediate finding here.
@dens When there's discussion about the Gen Z location apps (Bump, etc.), I always mention the magic of early Foursquare. You and your team in those days changed the culture.
@petergostev That Gartner Magic Quadrant is from 2025. There was a new one published in September 2026 (https://t.co/195F9IJsNY), but I haven't seen any reprints (i.e. marketing departments who paid $$$$ to share it) floating around.
@TheBalkanHacker I had the same initial reaction. But aside from the message being sent, a shockingly large amount of people building in AI right now are early career and inexperienced with procurement.
Also, it'll damper down CEOs and VCs talking about how they want to use certain OSS models.
As someone who has been involved with selling to the government on the vendor side, here's a few quick thoughts about today's DeepSeek announcement:
- I’m surprised an order like this took so long. A number of states and agencies already banned it on their own devices last year.
- The part I’d watch is the third-party provision, as it covers products built on DeepSeek, not just DeepSeek itself. Scenarios: A vendor using DeepSeek to build software an agency uses, or a service offering DeepSeek models (i.e. Microsoft offering DeepSeek in Copilot), could be pulled into this.
- I’d also watch whether state and local governments, or other vendors who sell to the government, start making procurement decisions based on this order... basically the beginnings of a secure intelligence supply chain.
If you’re selling to the US government at any level, the number one thing you can do is openly disclose the intelligence you use to build and implement your products and services. Procurement professionals tend to be risk averse and may even choose your competitors without you knowing if they're unsure about your offerings.
The Department of Homeland Security is requiring all civilian federal agencies to remove DeepSeek products and 'any third-party services developed using DeepSeek implementations,' and to stop buying them.
@CalimanuLoredan@AndrewCurran_ If you're going through a US gov't procurement process, you (the vendor) will probably be asked.
Although I will say, having had experience, if a procurement officer doesn't know or is unsure about your intelligence stack, they may choose a competitor without contacting you.
@polydaic@AndrewCurran_ Just last month, there was that discovery of Qwen being implemented in the search function of the Federal Register
https://t.co/6e9Qidm3MU
@AndrewCurran_ I wonder how the third-party provision would affect services like Microsoft Copilot (re: Satya's announcement a few months back) https://t.co/64g7QzB3xg
@xeophon Totally not surprising to see this if one is familiar with US gov't procurement. However...
It's not the DeepSeek product exclusion per se that is the problem, but the third-party products and services provision which developers should be paying very close attention to.
@lu__jasper Because like 10-15 years ago, a candidate would be more concerned if they would even get paid a base salary (nevermind potential equity)...