yoink

After they perma-extended Fable into including it into the max plan, I'm willing to give them the benefit of the doubt with this one.

At some point they may be indistinguishable from human-produced work, so the only way to verify if a site is someone's genuine opinion or AI-generated narrative is through some form of authority (or something else that is very difficult for AI to fake, but that protection can be broken by advancing technology).

If that happens, then in turn AI chatbot makers would in turn need to look for these kinds of authority to continue to provide accurate information, and said authority websites can use their privileged position to charge for access of their data.

The fact that we have a GLM 5.2-class model that can run on two 3090's comfortably at Q8 is absolutely insane. It wasn't long ago that GLM 5.2 was considered amazing for open weight models.

(I run a first-person shooter Minecraft server, and for this and other fast-paced gaming in general pause times under a millisecond or so is generally good.)

I find that to be a much more promising route than Delta's straight-up multiplayer development on the same task. (Vibe-kanban did fail but I don't think their idea was wrong, but rather the execution- they didn't differentiate enough from straightup Github and Jira boards when that was easily possible, just centralize the agents along with the board.)

Not that two people being able to look at the same agent at the same time is bad though, it's probably amazing for pair programming especially in a remote work setting. It just shouldn't be the main point of a product.

I also think that Delta's codebase replication approach is just flawed in general. Why would you build a remote server just to sync the codebase between multiple developer's laptops when you can just put said codebase on said server in the first place? No expensive sync is needed and all you need is to do remote multiplayer access at the UI level, and everyone gets to work happily on the same codebase and talk to the same agent at the same time.

The existing Claudisms like "smoking gun" and "it's not x it's y" evidently haven't impacted the model's agentic capabilities much, and i doubt the new ones will either.

it might already be time to start burning the best small models onto hardware since it's possible they can't get much better at many tasks like knowledge recall due to the inherent information density limits for models at a given size.

Claude Code is still using haiku 4.5 from ages ago for explore subagents for instance. Not to mention production uses like customer service that only need to be "good enough"

Sure, they'll keep it internal for a while to make sure their knowledge bank is more thorough than everyone else's, and because oftentimes discoveries can be far more convincing internally than externally (you need fewer sigmas for it to update your belief in a certain direction). But then how do they intend to profit from it in the end?

Do you have more sources/info on this?