MurphyA/hacker-news huggingface dataset:
by refactor_master | 2026-03-02 05:54:52+00:00
If A vibes, and B is overwhelmed with noise, how does B reliably go through it? If using AI, this necessarily faces the same problems that recording all A's actions was trying to solve in the first place, and we'd be stuck in a never-ending cycle.

We could also distribute the task to B, C, D, ... N actors, and assume that each of them would "cover" (i.e. understand) some part of A's output. But this suddenly becomes very labor intensive for other reasons, such as coordination and trust that all the reviewers cover adequately within the given time...

Or we could tell A that this is not a vibe playground and fire them.
by crazylogger | 2026-03-02 05:54:59+00:00
MCP solves a very specific problem: how do you ship a LLM’s tool/function so that it is callable by an LLM in an inter-process manner (so that you don’t need to modify OpenAI’s code to make your tool available in ChatGPT)? CLIs concern what happens inside such tools, namely a `bash` tool. As you can see they are different layers of the same stack.

> LLMs don’t need a special protocol ... LLMs are really good at using command-line tools.

The author's point only makes sense if LLMs all have a computer built-in - they don't. LLMs will only have a commandline if it is provided with commandline tools, and MCP is the standard way to provide tools.

If I have to find an analogy for this (nonsensical) MCP vs. CLI framing, it's like someone saying “ditch the browser, use html instead” - what is that supposed to mean?
by Imustaskforhelp | 2026-03-02 05:55:08+00:00
100% absolutely but its a bit worrying if in the future multiple AZ/datacenters could be start to get targeted?

attacking datacenters within a particular region so that service would have a hard time.

I guess someone can use some other regions DC to have more than (regional?) AZ but for mission critical infra, I can see that having sometimes issue too and you genuinely can't predict any of all of this.

That being said, There should be more than one AZ reliance but IMO also off-site or multi-cloud backups should also be preferred/used as well.
by tomhow | 2026-03-02 05:55:24+00:00
We need you to stop with this style of commenting, or we'll have to ban the account. HN is for curious conversation, not for this kind of ideological battle and inflammatory rhetoric. We want this to be a place where difficult topics can be discussed among people with different views. This kind of belligerence is not the way to discuss difficult topics. The overall effect of your style of commenting is to poison HN, and we have to ban accounts that do that.

Please read the guidelines and show a sincere intent to observe them if you want to participate here.

https://news.ycombinator.com/newsguidelines.html
by micw | 2026-03-02 05:55:36+00:00
IMO it depends a bit, but in most cases: No!

If you do proper software development (planing, spec, task breakdown, test case spec, implementation, unit test, acceptance test, ...) implementation is just a single step and the generated artifact is the source code. And that's what needs to be checked in. All the other artifacts are usually stored elsewhere.

If you do spec and planing with AI, you should also commit the outcome and maybe also the prompt and session (like a meeting note on a spec meeting). But it's a different artifact then.

But if you skip all the steps and put your idea directly to an coding agent in the hope that the result is a final, tested and production ready software, you should absolutely commit the whole chat session (or at least make the AI create a summary of it).
by yieldcrv | 2026-03-02 05:55:51+00:00
Mixer needs other people using the mixer with that asset, so no mixer available for tokens

But you can send the tokens to a virgin address, which is not what happened here, and sell them on decentralized exchanges where there is liquidity. Most popular one is uniswap, all tokens have liquidity there, usually the projects set up the liquidity pool on launch.

Virgin address can then do what it needs to do to launder the proceeds after sale.

But people tend to just go to a centralized exchange from there.

My go to would be swapping to Monero. It’s more foolproof.

But Tornado Cash is off of the OFAC list again, so you can just use that.
by gopalv | 2026-03-02 05:56:47+00:00
> The story isn’t “MCP was a fake marketing thing pushed on us”. It’s a story of how quickly the meta evolves.

The original take was that "We need to make tools which an AI can hold, because they don't have fingers" (like a quick-switch on a CNC mill).

My $job has been generating code for MCP calls, because we found that MCP is not a good way to take actions from a model, because it is hard to make it scriptable.

It definitely does a good job of progressively filling a context window, but changing things is often multiple operations + a transactional commit (or rename) on success.

We went from using a model to "change this" vs "write me a reusable script to change this" & running it with the right auth tokens.
by TimTheTinker | 2026-03-02 05:57:18+00:00
> If you generate PDFs with headless browsers or HTML-to-PDF tools, you've accepted a compromise: heavy dependencies, memory leaks, and "approximate" layout that shifts across environments

Absolutely not true with Prince[0]. It's an HTML/CSS-based typesetter built by the creator of CSS (Håkon Wium Lie [1]) that is lightweight, cross-platform, requires no dependencies, has no memory leaks, is 100% consistent in its output, is fully compliant with the relevant standards, and has a lot of really great print-oriented features (like using CSS to control things like page headers/footers, numbering, etc.). Prince has been used to typeset a lot of different print output types, from posters to books to scientific papers. It's even a viable alternative to LaTex. I've used it in the past, and can attest that it is outstanding.

[0] https://www.princexml.com/

[1] https://en.wikipedia.org/wiki/H%C3%A5kon_Wium_Lie
by notepad0x90 | 2026-03-02 05:58:53+00:00
that's what the MCP server is, except I don't always want a cli.

If I need to call API on top of a cli tool, i don't have to have a second wrapper, or extend my existing wrapper. You're suggesting I recreate everything MCP does, just so..it's my own?

MCP is just a way to use use wrappers other people have built, and to easily manage wrapping "tools", those could be cli tools, api calls, database query,etc..

cli tools aren't aware of the context window either, they're not keeping track of it. I might want my cli tool to output lots of useful text but maybe I don't want some of that for the LLM to save on tokens. Sure, I could create another cli tool to wrap my cli tool, now i have two cli tools to maintain. I'd prefer to do all the wrapping and pre-llm cleanup done in one consistent place. The instructions for the LLM letting it know what tools, parameters,etc.. are available is also defined in a consistent way, instead of me inventing my own scheme. I'd rather just focus on getting a usable agent.

I don't get the issue people in this thread have with MCP, is there some burden about it I haven't ran into? It's pretty easy to set one up.
by kenjackson | 2026-03-02 05:58:58+00:00
So interesting! There was a level of creativity back in those days that we seem to not have as much nowaydays. Now things seem to be based more on math and things like signing.

As a C64 user a kid one thing I didn't realize was this:

"The serial bus connecting the 1541 to the C64 has a famous bug. Commodore designed it to run at ~16,000 bytes/second, but a timing error in the Kernal ROM's ATN (Attention) line handling caused it to insert extra delays between every single byte — dropping the real-world speed to around 400 bytes/second. That's roughly one-fortieth the intended speed. Commodore never fixed it in the C64's lifetime. (A workaround was eventually added for the 1571 drive, but the 1541 remained slow throughout its production run.)

Fast loaders worked around this by downloading replacement code into both the drive's RAM and the C64's RAM, then communicating over the C64's User Port parallel pins instead — bypassing the serial bus completely. This gave transfer rates around 10,000 bytes/second (25× faster). "

I recall the "fast loaders" and always wondered how they could get data off a disk any faster. It seemed like magic. But now I know.
by Intermernet | 2026-03-02 05:59:38+00:00
That really just increases the processing power required to automate it. VM running Chrome to a virtual frame buffer, point agent at frame buffer, automate session. It's clunky, but probably not that much more memory intensive than current browser automation. You could probably ditch the frame buffer as well, except for giving the browser something to write out to. It can probably be /dev/null.
by dvt | 2026-03-02 05:59:43+00:00
Had the same thought. Also confused at the backhanded compliment that pickle got:

> Just look at Python's pickle: it's a completely insecure serialization format. Loading a file can cause code execution even if you just wanted some numbers... but still very widely used because it fits the mix-code-and-data model of python.

Like, are they saying it's bad? Are they saying it's good? I don't even get it. While I was reading the post, I was thinking about pickle the whole time (and how terrible that idea is, too).
by WA | 2026-03-02 06:00:30+00:00
Same. Lack of search and lack of scrollbars make me wonder why this project got so much attention in the first place. iTerm2 seems way more capable.

I suspect it is "just" the very nice-looking default theme in Ghostty. I updated my iTerm2 colors with colors I picked from Tailwind‘s excellent color palette and iterm2 now feels fresh and has all the features I want.
by ForOldHack | 2026-03-02 06:00:56+00:00
Yes, the original film for moon explorer has been stuck in orbit around the moon for decades. The world had a large network of satellite communications, and there was Arciebeo, but if it's not done here ... A few microwave dishes on all the NSF buildings should easily take are of it. Oh we had those ... But... What about streaming tape? Just ask Uncle Vint.
by cosmiciron | 2026-03-02 06:01:05+00:00
As someone who has spent decades in the lucid dreaming community researching consciousness (and created the SSILD technique), I could give you a very long, highly philosophical answer about the nature of the self, LOL.

But in the context of this repository: 'I' is the carbon-based entity that designed the layout architecture and takes full responsibility for the bugs.
by nilofer99 | 2026-03-02 06:01:12+00:00
Hey, I know it's Monday and I am at a transition period for this product, and I want to leave this upto you. How much should I charge for the product? I built this for my frustration but I noticed the same with other researchers. Also, there are tons of Latex AI stuff on reddit, which I feel every other day someone is making but I'm not deterred by since mine took 6-8 months to make with ethics. Not taking digs at OpenAI prism, but if anyone wants to try out and give feedback, I will enable more usage for them to write their papers :)
by raw_anon_1111 | 2026-03-02 06:02:31+00:00
Well I was 46 years old and married at the time (still married). It helped when I could tell my wife she could stop working and getting up early and I was working remotely. It made those late nights and early morning much more enjoyable.

“Whoever said money can’t solve your problems
Must not have had enough money to solve them”

(Partially joking, I make the same post BigTech as a “staff consultant” as an L5 I did mentor as an intern and when they first came back as an L4. Nothing eye popping. But decent)
by ffsm8 | 2026-03-02 06:02:55+00:00
LLMs frequently hallucinate and go off on wild goose chases. It's admittedly gotten a lot better, but it still happens.

From that perspective alone the session would be important meta information that could be used to determine the rationale of a commit - right from the intent (prompt) to what the harness (Claude code etc) made of it. So there is more value in keeping it even in your second scenario
by majormajor | 2026-03-02 06:03:16+00:00
You can leave commit messages or comments without spamming your history with every "now I'm inspecting this file..." or "oops, that actually works differently than I expected" transcript.

In fact, I'd wager that all that excess noise would make it harder to discern meaningful things in the future than simply distilling the meaningful parts of the session into comments and commit messages.
by neverkn0wsb357 | 2026-03-02 06:03:25+00:00
I think the person requesting to access the data was doing the right thing and I agree with the judge’s ruling.

The fact that they’re gonna shut it down, implies the scale of indiscriminate nature of data capture and the volume of data being captured.

These cameras are popping up all over the nation and if people realize how much data is being captured and where that data is going (or who it’s being sold to) and how it’s being used by government and private entities they would be appalled.

There’s been exposés about these cameras, everything from AI misidentification of “stolen” (not) vehicles and erroneous arrests and police encounters, to analysis of shopping patterns being sold back to private entities for better ad targeting. It’s wild.
by matrixgard | 2026-03-02 06:03:45+00:00
The multi-file iteration problem is the exact wall most people hit after the first demo works. Generating a single feature in isolation is easy; keeping context coherent across 10+ files while iterating on user feedback is where things fall apart.

Curious what you landed on for state management across sessions — that tends to be where phone-first tools lose fidelity fast when the project grows beyond 3-4 components.
by messe | 2026-03-02 06:04:03+00:00
The TH3 test suite is proprietary, but the TCL test suite that they refer to is public domain.

I'm not sure where they get their 90k CLOC count though, that seems like it might be an LLM induced hallucination given the rest of the project. The public domain TCL test suite is ~27k CLOC, and the proprietary suite is 1055k CLOC.
by messe | 2026-03-02 06:04:15+00:00
The TH3 test suite is proprietary, but the TCL test suite that they refer to is public domain.

I'm not sure where they get their 90k CLOC count though, that seems like it might be an LLM induced hallucination given the rest of the project. The public domain TCL test suite is ~27k CLOC, and the proprietary suite is 1055k CLOC.
by willbeddow | 2026-03-02 06:04:30+00:00
Increasingly, I'd like the code to live alongside a journal and research log. My workflow right now is spending most of my time in Obsidian writing design docs for features, and then manually managing claude sessions that I paste them back and forth into. I have a page in obsidian for each ongoing session, and I record my prompts, forked paths, thoughts on future directions, etc. It seems natural that at some point this (code, journal, LLM context) will all be unified.
by matrixgard | 2026-03-02 06:05:01+00:00
The survival rate metric is the one I find most telling — how much of what Claude wrote actually made it past code review unchanged. In practice it hovers around 30-40% for anything non-trivial, which reframes the whole cost calculation.

Have you noticed patterns in which types of tasks have the highest token burn but lowest line survival? Curious if it's test generation or refactoring that kills the ratio most.
by colbyn | 2026-03-02 06:05:03+00:00
Design can go a long way when reading long form text. If someone here is in contact with the author please tell them to improve the typography; most notably smaller and justified text for mobile phones. Other designers could probably weigh in. I’m not an expert, but well designed text goes a long way towards comfortable reading.

Apart from that, content wise a preliminary abstract is nice to have. I do like how the author provides a table of contents.
by matrixgard | 2026-03-02 06:05:14+00:00
The predefined schema dependency is a real constraint — most integrations I've seen break the moment an app updates its UI or adds a new flow. Dynamic discovery sidesteps that maintenance problem entirely.

The comment about major apps adding MCP natively is worth taking seriously though. The window where third-party discovery layers have an advantage is probably 12-18 months before the platform locks it down. What's your read on the moat once that happens?
by anon291 | 2026-03-02 06:05:33+00:00
I'm not sure that's true. Randomness has a well-defined meaning for me: unable to be computed by a finite program. The vast majority of real numbers are thus composed of truly random digits. Suppose the universe has a constant that is a real number. The overwhelmingly vast majority of real numbers are non-computable and cannot be described by a finite descrition of any kind. Thus, if the universe were simply sampling numbers from this real constant (or simply the answer to the math is this real constant as it is undergoing some dynamics), then the numbers would appear random because the true underlying constant is non-computable, and thus appears random.

There is no possible finite way to describe if this were the case or not.
by matrixgard | 2026-03-02 06:05:36+00:00
The "use common sense" policy is basically no policy, and it tends to get companies into trouble exactly when they need documentation most — during a SOC2 audit or an incident investigation. The specific gap I see most often isn't engineers using AI wrong, it's that there's no way to reconstruct what data went to which model when, so if a customer asks "did my PII go to OpenAI?" you're stuck guessing.

The AI Act angle is trickier than SOC2 because it depends heavily on what the AI is actually doing. Are engineers using it for internal tooling or in anything customer-facing that influences a decision? Most teams I've talked to genuinely don't know where their usage falls on that spectrum, and that uncertainty is exactly what auditors poke at.

What's the split in your context between AI for internal dev productivity vs. AI that touches actual product or customer workflows? That changes what "compliance" even means here.
by Ajakks | 2026-03-02 06:05:42+00:00
Very well said.

Your whole comment I kept recalling "The Art of War" - which is of course, mostly about how not to go to war, how if you must go to war, it needs to be efficient, bc the war will decimate the State faster than the enemy ever could, but be really smart about it, bc not only is it incredibly expensive, you could also lose, and its very hard to recover from.

Best to avoid warring if you at all can - thousands of years later, still true.
by matrixgard | 2026-03-02 06:05:48+00:00
Schema drift in Firestore is a pain because there's no enforcement layer by default — you're basically hoping your app code is the schema guardian, which breaks the moment multiple services write to the same collections. The security rules side is where things usually get dangerous; I've seen teams ship reasonable Firestore rules that quietly became wrong after a product pivot added new access patterns nobody updated the rules for.

The approach that's held up best is treating security rules like code: a proper test suite using the Firestore emulator, PR reviews on any rules change, and a CI gate that runs the rule tests on every deploy. For drift itself, a lightweight Cloud Functions trigger (onCreate, onUpdate) that emits alerts on unexpected field shapes is ugly but gives you eyes on what's actually landing in prod.

Are you dealing more with unexpected data shapes creeping in, or access patterns that shouldn't exist, or both tangled together?
by amluto | 2026-03-02 06:05:57+00:00
Lots of reasons:

The code is not portable between architectures.

You can’t actually define your data structure. You can pretend with your compiler’s version of “pack” with regrettable results.

You probably have multiple kinds of undefined behavior.

Dealing with compatibility between versions of your software is awkward at best.

You might not even get amazing performance. mmap is not a panacea. Page faults and TLB flushing are not free.

You can’t use any sort of advanced data types — you get exactly what C gives you.

Forget about enforcing any sort of invariant at the language level.
by Imustaskforhelp | 2026-03-02 06:06:17+00:00
> I’ve done some light game theory reading - but this isn’t covered - if they’re gone, who are they getting better terms for?

I think the idea can be that they are getting worse terms for America. Saddam Hussein from Iraq lost as well but the war was so messy that so so many americans died in bloodshed and gruesome ways and there was a whole gulf war syndrome within Army with severe PTSD.

This makes the people highly unreceptive of war and the govt should have more pressure from people. So in theory, America should've thought twice before attacking the same region.

I also think, that its hard to ever really remove an ideology. You definitely see ideologies of the past spring up in future and I think that sure they might lose the govt power but they would still have some influence for what its worth.

Also, Ayatollah was killed by these forces. Atleast the highly religious of people of Iran/politicians might spin the story to become religious which does have such ideas of inflicting maximum damage to the opponent at times.

I don't think that game theory can be applicable for religious/personal matters at times
by usefulcat | 2026-03-02 06:06:29+00:00
It’s also great for when you have a lot of data on local storage, and a lot of different processes that need to access the same subset of that data concurrently.

Without mmap, every process ends up caching its own private copy of that data in memory (think fopen, fread, etc). With mmap, every process accesses the same cached copy of that data directly from the FS cache.

Granted this is a rather specific use case, but for this case it makes a huge difference.
Show HN: Steward – an ambient agent that handles low-risk work
by 867762462f | 2026-03-02 06:06:35+00:00
I built Steward because most AI assistants still have to be summoned.

The idea here is different: Steward runs in the background, watches signals from tools like GitHub, email, calendar, chat, and screen context, and tries to move low-risk work forward before the user explicitly asks.

The core mechanism is a policy gate between perception and execution. Low-risk and reversible actions can be handled automatically with an audit trail. Higher-risk or irreversible actions must be escalated for explicit approval. Instead of constant notifications, the system is designed to brief the user periodically on what was done, what is pending, and what actually needs judgment.

Right now it is an early local-first prototype. It runs with a simple `make start`, opens a local dashboard, and uses an OpenAI-compatible API key.

I’d love feedback on a few things:

* whether “policy-gated autonomy” is the right abstraction for this kind of agent
* where the boundary should be between silent automation and interruption
* how people would structure connectors and context aggregation for a system like this
by KnuthIsGod | 2026-03-02 06:07:14+00:00
From a utilitarian viewpoint, I find that the Kurds, Croatians, Finns, Hungarians, Hebrew speakers, Tamilians, Malayalis, Hindi speakers come across appreciate it when I make an effort to use the little Kurmanji, Suomi, Magyar and Ivrit, Tamil, Malayalam and Hindi that I know.

More importantly languages are interesting !

I am back to working on my Finnish now and the grammar and sentences are fascinating !