corford

>and that among those varied independent scans, different people will catch what others miss.

My point was more that very few brains were looking deeply at the long tail of open source code/projects (other than the maintainers of the code themselves); and for the marquee projects that did get proportionally more varied eyeballs (e.g. postgres), it seems even that level of attention was insufficient for code deep inside the project's core.

LLMs change this. They make it much easier for maintainers and motivated users to amplify the power of their eyeballs.

>Do you think that an open source project will receive more AI eyeballs than a closed source project?

Net net, yes.

There was always, in my mind at least, a tension with Linus's Law ("given enough eyeballs, all bugs are shallow").

It's true but the problem is assuming, just because something is open source, it has received sufficient eyeballs. AI now gives us near unlimited eyeballs so, if we survive the bumpy transition, open source should indeed become very secure compared to closed source.

Wasn't kalshi caught wash trading recently?

What does "blended $0.30 per 1M tokens" mean? Is that input or output or average across the two? (asking as am trying to benchmark that cost against public GLM providers on Openrouter)

Zoom out...

For new stuff, maybe. I'm talking about existing startups now absorbing the onslaught of AI.

Stuff made during the move fast and break things era now doesn't hold up very well in the AI era. Or to say another way: startups are very vulnerable now - this new environment is unforgiving towards cutting corners and/or having inexperienced devs

Jesus that one is bad

Agree. If I'm following along correctly, it seems Calif is really the one to blame not Chaingaurd.

One reason (not the only one) is likely strategic - deny potential competitors access to resources i.e. out spend them (competitive CapEx escalation).

yeah but the prose is illustrative (fable/opus wouldn't do it in the same style)

Yeah, sad sign of the times unfortunately.

Go to america.gov (which is Gemini behind the scenes afaik) and type in "play minecraft"

"A week in Beijing and Shanghai with the people building AI in China": https://earnedintuition.substack.com/p/involution-without-ex... does a decent job of exploring some possible reasons

Yep am waiting for some of my whitelisted openrouter providers to pick it up (so far none offer it but hopefully a few will in the next couple of weeks)

> which even they couldn’t access

What would prevent them from getting the data out of postgres?

Where specifically do they say their European plan has ZDR? I just skimmed that page and their FAQs but can't see it (though I might have missed it).

There's already an open weights one mentioned up thread: https://laya.convaiinnovations.com/

Brexit has caused an estimated ~6-8% per capita loss of output: https://www.bbc.com/news/articles/cyv0m164m84o

>inflexibility on the EU side triggered the Brexit referendum.

That's a bit of a stretch

FYI, Hoka have an EU site too

And North Korea?

I know it's cynical/jaded but this just feels like pre-IPO circus noise to me (honestly wouldn't even surprise me if it was orchestrated from within Anthropic themselves)

One of the best takedowns of samas/OAIs spin on this I've seen is this post on X: https://xcancel.com/BetterCallMedhi/status/20974723362578637...

After some iteration, this is what I currently shove in every AGENTS.md to make Fable legible:

## Writing guidelines

These apply to documentation, code comments, commit and PR messages, and replies to the user.

- Write precisely in clear, complete sentences; keep text concise and proportional to task complexity.

- Stay focused: avoid filler, repetition, over-the-top detail, and tangents the user did not ask for. Once a fact is stated, do not restate it for effect ("so the commit landed on a branch nobody was going to merge"). Do not editorialise.

- Always prefer ISO 24495-1:2023 conformant plain language over dense technical jargon: short sentences, one idea per sentence, define terms on first use.

- When reporting your own mistake, give the cause and the fix in one sentence each; no apology, no framing ("the mistake was mine"), no post-mortem.

- Never use em dashes or cataphoric teasers such as "Here's the thing" or "But there's a catch".

These nascent inference chip efforts are reminding me of the early 3dfx / riva / mach / powervr days. Will be interesting to see if inference chips are here to stay and, if so, who the eventual dominant player(s) will be

Doesn't that kind of prove my point?

I'm not sure I agree. I find the Delaware & IRS forms and systems archaic/byzantine compared to e.g. the UK system.

Not sure if you are referencing something else but in the case of VAT (sales tax) this is simply not true, see: VAT one stop shop / moss. There are also no customs duties on inter-state shipments.

Employment regulations are different - if you have a lot of people working for you in another member state you'll need a branch office or subsidiary there (or you can easily outsource it via services like https://www.playroll.com/)