caust1c

This problem left as an exercise for the taxpayer. /s

IMO big models are not a product in and of themselves. Inference is just a new type of compute. I'm confident that in two or three years, every product will have inference capabilities integrated into the experience, and models will become less and less distinctive from one another.

What most products need from a model is a pretty short list: the ability to make tool calls well, accurate recall, and the ability to follow directions without wavering (whether or not those directions are baked into the weights or provided in a system prompt). That covers 95% of inference utility in products.

We're nearly there, and I believe these capabilities will fit on small models.

Because of this though, I predict hardware demand will stay high despite demand for "hosted" inference dropping. Unless there's some regulatory shenanigans that step in to say otherwise.

I actually just installed forgejo in My Home lab and loving it. Thinking about moving the companys code hosting to it next.

Azure's going to suffocate github. I'm curious to see what's next. Will self-hosting the code repository come back in vogue or will another social-coding platform take off?

My RSI flared up just looking at this keyboard. Hard pass!

Good points. I looked up the definition for prediction and I suppose I'm stretching what I view as prediction.

> A prediction is a statement about what you think will happen in the future, often based on experience or knowledge. It can also be referred to as a forecast or an informed guess

Based on my reading of this definition, compression may inform prediction but it is not itself prediction. The examples cited in the blog post are examples of probabilistic recall based on past events or instances. More context means a higher chance that the recall is more likely to be aligned.

But it's hard for me to accept the leap to compression == prediction because in my mind a prediction is an informed guess about something that hasn't yet come to pass. But thinking more about it, time is a human concept and so who's to say the temporal reference means anything at all here. Maybe probabilistic recall is the same as predictive forecasting if time is an invented concept and essentially means nothing?

Is everything fundamentally deterministic if you know everything in the universe or does free will exist?

IDK to be honest, I'm just more frequently surprised by new things that happen every day than I am at things that stay the same, even if mostly things stay the same. Maybe I just don't notice them and nothing actually ever happens.

Side note: the inevitable consequence of this line of reasoning will eventually become that LLMs given enough power are in fact intelligent and sentient, and I'm worried about how that affects humanity as a whole. Are we about to subjugate the most intelligent thing humanity has ever created, or is it about to subjugate us?

The rabbit hole gets deep quick when making the leap between a fancy recall mechanism and novel prediction, but I agree they're not that different in the end. I just believe it's important to be nuanced or else we'll miss when AGI actually happens (maybe it's already here).

Compression is not prediction, it is recall. Can we make predictions based on compression? Absolutely. Is memory encoded into physical neurons technically compression? I would argue also yes.

However, going from compression to prediction is a large jump that is unsubstantiated by this article and based on the claim that probabilistic recall is also prediction.

Two perfect counterpoints to this are markets and weather patterns. One cannot predict future events based on past performance or behavior. Change is the only thing that's constant, and chaos/entropy is everywhere we look.

For simple problems like programming, sure predictive recall works amazingly well, but let's not pretend LLMs are actually predicting something. This is exactly why LLMs suck at doing anything novel; they lack imagination and creativity.

Where's the source code for the database itself? Looks like the repo is just a client.

Congrats on the launch!

> I’d like it to eventually pay for itself [...] — but that’s a problem for later.

Hard pass from me dawg. If you don't know the business model now, folks like me are tired of trusting their data to randos on the internet without a plan for sustainability. Guaranteed to end up being just another data farm.

Neat you got the domain tho.

I'm getting tired of everyone saying "MCP is dead, use CLIs!".

Yes, MCP eats up context windows, but agents can also be smarter about how they load the MCP context in the first place, using similar strategy to skills.

The problem with tossing it out entirely is that it leaves a lot more questions for handling security.

When using skills, there's no implicit way to be able to apply policies in the sane way across many different servers.

MCP gives us a registry such that we can enforce MCP chain policies, i.e. no doing web search after viewing financials.

Doing the same with skills is not possible in a programatic and deterministic way.

There needs to be a middle ground instead of throwing out MCP entirely.

Disclaimer: OP (Caust1c) is not Jitesh, just following hn recommendations w/ post titles.

> FYI man, alright. You could sit at home, and do like absolutely nothing, and your name goes through like 17 computers a day. 1984? Yeah right, man. That's a typo. Orwell is here now. He's livin' large. We have no names, man. No names. We are nameless!

I watched this video yesterday corroborating this story and I gotta say the evidence is pretty hard to refute:

https://www.youtube.com/watch?v=7ws8Grsc4jU

Purposefully devaluing the dollar to make US goods more globally marketable and hide the Japanese debt crisis is an interesting but risky strategy.

Currently, I'm glad to see a correction without panic, but it's too early to make a call on the effect on the overall global economy. Xi's already suggested making the Yuan a global reserve currency, and seeing as much debt they're holding, I'm a little worried they're able to make it happen if this is the US financial strategy.

The sequence of events: Elon doing a leveraged buyout of X, then xAI funding, then debt transfers to X, then the xAI–X stock deal. Now the proposed SpaceX–xAI merger appears to have shifted X’s financial burden from Musk personally toward xAI investors and, potentially, future SpaceX shareholders.

This is speculative, of course, but yeah seems likely.

> it prevents entire classes of bugs where IDs get mixed up across services.

~Does this really happen for people? I haven't ever seen this class of bug, and shudder to think of how it happens in code. Sure support tickets are nicer with the prefix, but how would a bug manifest in the code itself?~

Edit: of course it can happen with `new.id = old.id` where new and old are different types, now that I think about it after coffee. However, I'd be hesitant to claim that this prevents those bugs, instead I'd argue that it simply makes them easier to identify.

Also, KSUID has been around since before UUIDv7 and seems to meet all of the author's same requirements and has many client libraries already. Guess people doing research on it still aren't able to find it, or just want to do their own anyway which is cool too.

Video of the visualization https://x.com/_lyraaaa_/status/1993858890421727738

Definitely not malware: https://www.star-history.com/#openagents-org/openagents&type...

If you find the OP interesting, you might find Project Kamp more interesting:

https://projectkamp.com/mission.html

The OP seems like the academic approach to what project kamp is learning by doing: They're attempting to build a community that's eventually completely self sufficient on a fairly limited land space, and documenting the whole process.

This is exactly it. AI is sniffing out the good datamodels from the bad. Easy to understand? AI can understand it too! Complex business mess with endless technical debt? Not too much.

But this is precisely why we're seeing startups build insane things fast while well established companies are still questioning if it's even worth it or not.

When you're talking the size of investment that AI-centric companies have received, on the order of hundreds of billions of dollars, there's no way it's not exposed to the wider market.

But I agree with you, the article is too light on details for how inflammatory it is.

Super curious how they enforce the security story here. Doesn't seem easy to hoover up the context needed for individual users to keep private chats private. Maybe they search dynamically based on the prompt like Claude Code does?

Seems hard without creating an embedding on slack topics and synonyms.

Wait, what? A database in 2025 doesn't support any kind of auth? A financial database? WTF?

C'mon folks, the least you can do is put a guide for adding an auth proxy or auth layer on your site.

Particularly since you don't use HTTP (cant easily tell from the docs, I'm assuming), then folks are going to be left wondering: "well how the hell do I add an auth proxy without HTTP" and just put it on the open internet...

Good research. I'm glad people are hopping on this. Lots of surface area to cover and not enough time!

~That's a good way to launder money.~

Err, tumble money. Err, that's a good internet gag.

100% agree. It should be an optional argument for your logging library and handled one time there to be used everywhere.

Django + REST framework is what I cut my teeth on doing web programming in my first job. It's a wonderfully written codebase, I'm very thankful I had some great code to learn from, and it wasn't even 10 years old then, I didn't even realize.

Congrats team! Glad to see it's still thriving and a great option to pick up for beginners.

Yes, unfortunately it's pretty trivial. Any time arbitrary file write is possible, RCE is usually possible too.

It's incredible for investigating audit logs. Our customers use it daily.

https://blog.runreveal.com/introducing-runreveal-remote-mcp-...

In my mind the only thing novel about MCP is requiring the schema is provided as part of the protocol. Like, sure it's convenient that the shape of the requests/response wrappers are all the same, that certainly helps with management using libraries that can wrap dynamic types in static types, but everyone was already doing that with APIs already we just didn't agree on what that envelope's shape should be. BUT, with the requirement that schema be provided with the protocol, and the carrot of AI models seamlessly consuming it, that was enough of an impetus.

Spencer is an engineer at ClickHouse, so it makes sense.