Usually there's a bodies-in-the-streets phase... guillotine was theatrical, bolsheviks called it the red terror, nazis were well the nazis, italians strung em up on meathooks, tienamin used tanks (after the famines), baltics did straight up ethnic cleansings, last week iranians gunned down thousands corralled in the squares.
Luckily we're still only in the "kidnap and beat-up by the secret police" phase, haven't had the mass executions yet. Only a singular execution here and there.
> I’m glad to be a bystander and not participant, that’s for sure.
Hope that's because you're not in the USA. USA-based bystanders is how this shit happens.
It's "eh, we haven't gotten to this problem yet, lets just see where the possibilities take us (and our hype) first before we start to put in limits and constraints." All gas / no brakes and such.
Safety standards are written in blood. We just haven't had a big enough hack to justify spending time on this. I'm sure some startup out there is building a LLM firewall or secure container or some solution... if this Cowork pattern takes off, eventually someone's corporate network will go down due to a vulnerability, that startup will get attention, and they'll either turn into the next McAfee or be bought by the LLM vendors as the "ok, now lets look at this problem" solution.
Yeah, I was thinking it definitely needs to be correlated to geopolitical tensions in some way. Polymarket data might be helpful in this case- and provides incentives for putting this kind of data together.
US car companies became banks that happen to make cars.
How much would you like to pay for that 80k new truck? Sure, we can give you that monthly payment, lets just structure it as a 10-year loan where you end up paying twice that on a rapidly depreciating asset. Boom, we've just sold two cars and only had to manufacture one.
right. I stopped reading at "ENSUE_API_KEY | Required. Get one at [dashboard](link to startup showing this is an ad)"
First thought: why do I need an API key for what can be local markdown files. Make contents of CLAUDE.md be "Refer to ROBOTS.md" and you've got yourself a multi-model solution.
Main objection to corporate AI uptake is what are you gonna do with our data. The value prop over local markdown files here is not at all clear to even begin asking that question.
I was simply just made uncomfortable by how much CYA the lawyers had to insert into a technical blog post.
This is fun cool tech and I appreciate the insider look, but when the lawyers are peering over your shoulder so much that they need to plaster their "final product may be different" disclaimer even to a r&d audience, well, the Disney Imagineering org sounds more like Disney Legaleering.
I mean, they kind of have to. The last thing you want is some disgruntled Disney-goer trying to get a quick refund or discount for false advertising by saying they, "expected olaf to interact with them, because it looks like he does in the promotional videos"
reply