> 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.
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.
> 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!
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.
RunReveal (https://runreveal.com) | Systems Software Engineer | Austin, SF (US Work Auth required) | Full-time
RunReveal is the Security Data Platform that's building tools to help companies detect and respond to threats in their network. We're a team that values speed, quality and curiosity. Our stack is Go, NextJS (TS), Postgres and ClickHouse. We believe that companies should be able to own their security data and get value out of it too and so we've built a platform that can be deployed anywhere. SIEM sucks, so we're here to fix it.
If you're into self hosting or running a homelab, or you're using LLMs to enhance your development workflow and extend your knowledge and not just regurgitate slop, or you're always looking for opportunities for self improvement, you're in good company at RunReveal.
We've got phenomenal customers like Cursor, Harvey, Temporal, Linear, DigitalOcean, ClickHouse and AngelList among many others that we work with on a daily basis to improve the product.
We're especially interested in folks that have experience working with petabyte scale databases. We use ClickHouse, but experience with other similar large scale data technologies like Iceberg, Flink, Spark, ScyllaDB, Cassandra, InfluxDB, TimescaleDB, BadgerDB etc would also be valuable.
Reach out to me via alan at the company domain and mention hn who's hiring January '26 in the subject line.
> 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.
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...
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.
Congrats on the launch!