MurphyA/hacker-news huggingface dataset:
by Veserv | 2026-03-01 17:43:41+00:00
While I appreciate more efficient and compact representations, I fail to see why this is particularly necessary. This article [1] on the same topic indicates a naive PQ chain is only ~40x the size of a current 4 KB chain. That means it is just ~160 KB.

If you have the legal minimum to be considered broadband in the US, you need ~100 Mbps, so that would add ~12 ms.

If you can stream one 4K video, you need ~20-40 Mbps, so that would add ~30-60 ms.

If you can stream one 1080p video you need to ~3-6 Mbps, so that would add ~200-400 ms.

Even on just a 1 Mbps connection, just barely enough to stream a single 480p video that would only add ~1 second.

And I doubt the weight of most of pages is lower than 160 KB. Many of them are probably dramatically higher, so the total effect of a extra 160 KB is just a few percent.

If there is a problem, it seems like it would be with poorly designed protocols and infrastructure which should be fixed as well instead of papering them over.

[1] https://arstechnica.com/security/2026/02/google-is-using-cle...
by regularization | 2026-03-01 17:43:58+00:00
> a tyrant who killed his own kind in masses with gas and started wars with neighbors

The US sent Saddam the Bell helicopters to gas the Kurds. US military aid increased after that happened.

The war with a neighbor was with Iran - the country the US just attacked, and which the US encouraged Iraq to fight. That's why Rumsfwld was over there shaking Saddam's hand.
by Flere-Imsaho | 2026-03-01 17:44:14+00:00
Sounds promising, as always fingers crossed these sorts of new techniques produce positive results.

However, here are the problems that Gemini 3.1 pro identified:

1. The Scale of the Human Body: A mouse is tiny, meaning nanoparticles injected into its bloodstream circulate quickly and have a high chance of hitting the tumor. In a human, the circulatory system is vast. The human liver, spleen, and kidneys act as massive, highly efficient filters (the reticuloendothelial system) that often trap and clear metal-organic frameworks (MOFs) out of the body long before they ever reach the tumor.

2. Tumor Architecture: The mouse models used in these studies are usually "xenografts"—tumors grown rapidly over a few weeks under the skin. Human tumors develop over years, building dense, fibrous, scar-like tissue (stroma) and highly pressurized cores. Even if the nanoparticles reach the outside of a human tumor, they often cannot physically penetrate deep enough into the dense human tissue to eradicate the whole mass.

3. Immune System Differences: To grow human tumors in mice for testing, scientists often have to use immunocompromised mice (mice bred without an immune system so they don't reject the tumor). When you inject foreign iron-based nanomaterials into a human with an intact, highly aggressive immune system, the body may attack the particles, causing severe systemic inflammation or immune toxicity.
by boh | 2026-03-01 17:44:19+00:00
Pretty much any claim by any company that they've somehow "figured out AI" and that's why they're cutting jobs has been proven as unsubstantiated by various financial firms. Most of these companies can no longer grow and are starting the dying process. AI is eating all their investment money so they're trying to pretend they're an "AI first" company while simultaneously gutting themselves.
Show HN: Spekkio: Reverse-engineer specs from vibe-coded apps
by tessier0ashpool | 2026-03-01 17:45:25+00:00
Hey HN,

I see vibe-coded apps as basically a working sketch from a domain expert who knows what they want, abdicating responsibility for the "-ilities" (e.g. maintainability, scalability).

They're valuable, working, partial specifications - but far from a production-worthy product.

Spekkio is an extension of the spec-kit approach that reverse-engineers a vibe-coded app to make best use of what we're given to bridge that gap.

Spekkio surfaces the kinds of rubbish that vibe-coded apps accumulate: missing validations, security gaps, inconsistent error handling, dead code, etc... and creates documentation + builds a BDD test suite through inference. From there, you can rebuild/regenerate a higher quality app from a known state, evolving it intentionally. It builds a (somewhat) interactive report to help you navigate all the findings.

The first example is the classic BDD ATM example that was generated naively from the book description. So pretty realistic :)

I'd love to see if this is something that resonates with other people. Lots of architectural and other considerations have been skipped, but I want to answer the biggest question first: is this useful to the community?

Would love feedback, especially from anyone dealing with "production vibe-coded apps".

https://github.com/paulkarayan/spekkio
by convolvatron | 2026-03-01 17:45:41+00:00
I don't know why we're getting mired in the details here. The administration certainly isn't. We all work for trump now. Lawyers, journalists, universities, tech companies, state, local and foreign governments. Anything trump or one of his designated people wants, you need to do. If you start sputtering about your agency or your rights or your sovereignty, then expect as much shit thrown at you as the trump organization can muster. That's it, there is no legal justification. There are no fine points to argue. Obey or be punished.
by kibwen | 2026-03-01 17:46:00+00:00
Depends on the bike. On some bikes the motor is mounted in the rear wheel, in which case there's no gear between the motor and the wheel. On other bikes the motor is mounted between the pedals and sent to the rear via the chain, in which case shifting works as you expect. But the latter style (a.k.a. mid-drive) demands custom frames (because mid-drive motors are nonstandardized), which increases costs and decreases repairability. In contrast, rear-wheel motors can fit on literally any frame, so they're much more accessible.
by thisisit | 2026-03-01 17:46:04+00:00
> Junior devs have always been useless

> The same ethos makes sense with AI, it's just that every company is trying to avoid paying that training tax.

Last time when a junior dev was added to my team I had a similar thought. But then talking with management I was informed that things went beyond just training.

The company had a social responsibility pledge and understanding with the local educational institutions. They had to pledge to be part of the internship and hiring activities every year. The company could not chose to be fair weather friends and try to recruit people only when they saw fit.

The other aspect was cost. A team made of only senior engineers was costly.

The last aspect was leveling up. Unless the company has lots of levels the team might end up lots of engineers at the same level. And with the inverted funnel nature of promotions it meant some engineers might end up waiting years for the promotion.

So, it was better to have teams with some junior, intermediate and experienced engineers. That way costs and promotion flows were controlled.

Now with AI the impact might go beyond junior devs. I see even the intermediate devs being impacted. It is more likely that companies think they can replace say 1 junior + 1 intermediate with 1 junior dev with AI. Or something along those lines.
Show HN: Aura-State – A Formally Verified LLM State Machine Compiler
by rohanmunshi08 | 2026-03-01 17:46:19+00:00
Over the last year, I've watched teams fail at enterprise LLM automation because they let the AI manage state and do math.

So I built Aura-State — an open-source Python framework that compiles LLM workflows into formally verified state machines.

Instead of hoping your agent does the right thing, Aura-State proves it does — using algorithms from hardware verification and statistical learning:

CTL Model Checking — proves workflow safety before execution (same technique used in flight control systems) Z3 Theorem Prover — formally verifies every LLM extraction against business rules Conformal Prediction — calibrated 95% confidence intervals on every field MCTS Routing — Monte Carlo Tree Search scores ambiguous transitions Sandboxed AST — zero-hallucination math, compiled from English rules

Live benchmark results (GPT-4o-mini, 10 transcripts): → 100% budget extraction accuracy → 20/20 Z3 proofs passed → 3/3 temporal properties proven → 65 unit tests passing

The gap between "it usually works" and "it provably works" is smaller than people think.

https://github.com/munshi007/Aura-State
by renewiltord | 2026-03-01 17:46:45+00:00
Very cool. Thanks for sharing. I have an ebike myself and have considered just strapping extra battery packs to the frame so that I can just swap when required. In the end, I mostly take shorter trips (I’ve had it since Dec and my odo only reads three figures).

Speaking of R&M, I have wanted to get one of their bikes that has the child container area in the front. I saw one guy with one and it looked pretty awesome. A large bike like that would benefit from some larger battery pack. And those have a flat area in front on the frame where you can host a few parallel to the floor (hard in a normal bike frame).

One annoying constraint is that it’s hard to find a place here in America where people won’t tacitly kill children. As more people here become online only child-free characters driving large EVs they don’t think too much about killing children and will only delay someone’s license for a couple of years for doing so.

The hard problem seems to be other people.
by conductr | 2026-03-01 17:47:18+00:00
As an alternative mode of transportation, that could/should replace car usage for many people, I think we need to separate the two completely as well. The throttle version needs to be regulated more like a motorcycle or moped. This would take it out of the hands of most kids and cause license suspension worries for young adults and other reckless users. I agree they are essentially death machines and governments generally have no sane approach to regulating them.

That said, I think the e-moto versions have more potential towards alleviating traffic or being an alternative mode of transportation as most people don’t want to peddle at all. E-bikes are great, but I don’t think it’s reasonable to assume that would ever be on the average Joe’s list of feasible alternatives.
by phpnode | 2026-03-01 17:47:35+00:00
I don't doubt that CLIs + skills are a good alternative to MCP in some contexts, but if you're building an app for non-developers and you need to let users connect it to arbitrary data sources there's really no sensible, safe path to using CLIs instead. MCP is going to be around for a long time, and we can expect it to get much better than it is today.
by sublinear | 2026-03-01 17:47:55+00:00
I think you're missing the point. My entire career has been looking up and reusing code written by humans who are objectively better at writing code than AI ever will be (please don't argue about this).

Your job has always been to be accountable for the technical decisions made. Sometimes I read comments like yours and wonder if the almost apologetic tone is an admission of guilt that you never really liked this job. You can speak for yourself, but I didn't get into this to just noodle around or work at unhinged startups where nobody gives a rat's ass about code quality.
by igornotarobot | 2026-03-01 17:48:11+00:00
> I run into bugs all the time so it’s probably not ready for anyone other than me to use, but I’ve managed to go pretty deep (if not wide) in just a few days of work.

Having similar experience with my experimental code generator to Rust. Every time a yet another example does not work, Claude fixes it. However, I am curious whether it would converge to a bullet-proof solution, or I have to carefully read the code and come up with proper abstractions.
by appreciatorBus | 2026-03-01 17:48:15+00:00
This. So tired of the idea that HN trying to stay relatively clear of politics is some great loss when every Israel Palestine submission that makes it through is just the same few dozen ppl shouting some variation of "US/West/Markets=BAD" and another dozen or so grappling with them. Nothing changes, no one learns anything. If ppl want that sort of interaction, it's available 24x7 on Bluesky. Every public web forum devolving into 24x7 culture war doesn't serve anyone's interests except the marxists.
by twoodfin | 2026-03-01 17:50:00+00:00
There was a cottage industry in elaborating the theory that Bush and his administration were unnecessarily caught flat-footed or even knew the attacks were imminent.

Richard Clarke is a good place to start:

https://en.wikipedia.org/wiki/Richard_A._Clarke

He seemed more interested in publicity and exaggerating his own bureaucratic importance than being objective—tendencies the political opposition and media were in no mood to criticize.

But YMMV.
by lateforwork | 2026-03-01 17:50:24+00:00
> The central view of ape coding proponents was that software engineered by AIs did not match the reliability of software engineered by humans

That's not the reason to do ape coding. AI generated code is innovative. If you want to build something that no one has built anything similar to then you have to ape code.

See Chris Lattner's blog where he explains the limitations of AI: https://www.modular.com/blog/the-claude-c-compiler-what-it-r...
by WarmWash | 2026-03-01 17:50:26+00:00
New Jersey just passed some of the most onerous and short sighted ebike laws in the world last month.

Basically anything that has two wheels and a non-human energy source drive is now a motorcycle, requiring a license, registration (including a license plate), insurance, and a DOT approved motorcycle helmet, as well as This law came on the back of two teens being killed on ebikes last year.

This is the exact kind of idiotic knee-jerk legislation that will come from the public and governments general ignorance on the state of electric tandem wheel transportation.

So now in New Jersey, Betsy with her class 1 250W pedal assist ebike must get her license and don her motorcycle helmet while only riding on roads with her insured, registered, and license plated 15 mph bicycle.

That's what happens when you get "think of the children" laws.
by xhrpost | 2026-03-01 17:51:03+00:00
>The engineers who thrive will be the ones who can resist the temptation to over-engineer when the marginal cost of adding complexity drops to near zero.

I think this isn't being discussed enough in the SWE world. It wasn't too long ago that engineers on HN would describe a line of code as "not an asset but a liability". Now that code is "free" though, I'm seeing more excessively verbose PRs at work. I'm trying to call it out and rein it in a bit but until engineers on average believe there is inherent risk here, the behavior will continue.
by analog31 | 2026-03-01 17:51:50+00:00
I don't know if this figures into the engineering formulas, but an e-bike needs to be stronger due to the higher speeds and power levels. On a human powered bike, if you're hauling 150 pounds, you're probably going pretty slow.

My friends who have e-bikes go through a lot more "consumable" parts such as chains, tires, brakes, cogs, and bearings.
Show HN: I Built Context+ AST and Embeddings for Codebase Understanding
by forloopcodes | 2026-03-01 17:52:09+00:00
I cant believe i just made a permanent solution to context bloat and open sourced it all!

when we tested this tool (Context+) for solving an issue on the OpenCode repository, the agent using this tool used ~6.5k fewer tokens, found the code and fixed it in half the time!

the results were surprising: 6 to 10k tokens saved per prompt, completed task in ~2 minutes while the agent running without the tool took ~4 mins for the same and got stuck in loops

built an entire beast by using all the modern tools that we could think of: undo trees, semantic search by meaning (by haskellforall), advanced refactoring, blast radius, advanced file context trees, restore points... i can keep going on

semantic code search and context trees are the future of agentic coding and this tool proves it

the feature i loved the most is semantic search and how it gets things done 2x faster with least possible tokens

it makes an agent that actually knows what it’s doing and not just guessing, it makes meaning from your code similar to RAG. if you aren't optimizing your context, you are just burning money

this tool is still under development, it can have unexpected behavior and the docs need updates but the video shows the reality of how fast it can be

github: https://github.com/ForLoopCodes/contextplus
get here: https://contextplus.vercel.app
youtube: https://www.youtube.com/watch?v=2YKQPzQFvvg
x: https://x.com/forloopcodes/status/2027745057483460757
by p3lending | 2026-03-01 17:52:23+00:00
I’m building P3, a reputation-based lending marketplace where borrowers earn portable trust from verified actions and repayment history.
Stack: React + TypeScript, Supabase (Postgres + RLS), Node backend, Ethereum smart contracts.
The idea is to give lenders more underwriting signals beyond a traditional credit score.
I’d appreciate feedback on architecture (hybrid on-chain/off-chain scoring), anti-Sybil design, and API structure.
by cmrdporcupine | 2026-03-01 17:52:29+00:00
While I agree with the tone of the article: It would help if the article itself wasn't clearly at least partially LLM written. It has many of the shibboleths:

"This is not a minor adjustment. It is a fundamental shift in professional identity. "

"That is not empowerment. That is scope creep without a corresponding increase in compensation"

Honestly, it's lazy. At least edit the bloody thing.
by CuriouslyC | 2026-03-01 17:52:29+00:00
There's been an anti-MCP pro-CLI train going for a while since ~May of last year (I've been personally beating this drum since then) but I think MCP has a very real use case.

Specifically, MCP is a great unit of encapsulation. I have a secure agent framework (https://github.com/sibyllinesoft/smith-core) where I convert MCPs to microservices via sidecar and plug them into a service mesh, it makes securing agent capabilities really easy by leveraging existing policy and management tools. Then agents can just curl everything in bash rather than needing CLIs for everything. CLIs are still slightly more token efficient but overall the simplicity and the power of the scheme is a huge win.
by pmvpeter | 2026-03-01 17:52:43+00:00
I can’t speak for everyone but it seems to me to be a very human drive to want to be useful to others.

If you are good at something that you enjoy doing and that is valued by others, that’s the ideal scenario. And that’s what writing software looked like for many people for a long time.

That doesn’t mean you should do things just to please others. And it also doesn’t mean you can’t do something just because you enjoy doing it. But it means that these people now have a diminished ability to employ their unique skills to help others while doing something they love doing. That can sting, understandably.
by bredren | 2026-03-01 17:52:50+00:00
Why not just write a skill and script that calls crawl4ai or similar and do this using Claude code?

You can store the page as markdown for future sessions, mash the data w other context, you name it.

The web Claude is incredibly limited both in capability and workflow integration. Doesn’t matter if you’re dealing with bids from arbor contractors or researching solutions for a DB problem.
by stugreen13 | 2026-03-01 17:53:37+00:00
MCP

> learn new protocol

> bloat your context with unnecessary tools

> decision overload for agents

> spin up new server, more code to document and maintain

> pain to debug

> constantly changing

CLIs

> 0 context bloat

> one-line install

> on-demand discovery via --help commands

> fast and lightweight

> every model knows bash, even dumb ones

> composable, can chain commands (massively underrated, e.g. cli users list --output json | jq '.[].id' )

> save $$$ on tokens

> no new servers or docs

> can use tools like https://instantcli.com to generate one for any API
by lelanthran | 2026-03-01 17:53:54+00:00
You said

> you're so delighted

Then you said

> lol

Okay, I get it - for you this is a laughing matter; your goal is something other than discussion.

But I gotta know - you are talking about a regime that had no problem gunning down thousands of innocent citizens in the streets just a month ago, why are you so sure that they won't use other innocents as shields for their soldiers?

Where is this confidence coming from?
by exmadscientist | 2026-03-01 17:53:57+00:00
Which, as the article and other comments here make clear, has been changing back and forth over the decades.

In a situation like that, I think you kind of have to acknowledge the original drawings as the preferred state for things. Especially when just about anyone with training in this area would readily agree that that design aligns with what they'd all consider usual or correct.
by Analemma_ | 2026-03-01 17:54:23+00:00
Since terminal capabilities are handled by the remote machine instead of the client, for things to work out-of-the-box you need an up-to-date terminifo database on the remote. The bug is that nobody updates their terminfo databases anymore, and nobody has ever bothered proposing some kind of negotiation protocol in ssh to do this automatically (which admittedly would probably be a huge can of worms), so if you want any capabilities in your terminal beyond xterm-256color from 2003, you have to set them yourself.
by yawnxyz | 2026-03-01 17:54:44+00:00
I have a similar problem - AI is making building products easier, but it's made "shipping" a product 100x harder.

I was always a mediocre engineer, and stopping out on a personal usually happened bc "feature XYZ is way too hard to build and I won't spend another three weeks on it". Nowadays anything can be built in a couple of days, scope creep plus "would be cool if it could also do XYZ" makes it harder to walk away from a project and call it done.

But ofc these are personal projects, and I use them daily (like a personal workout system and tracker which I run w/ Claude Code, which love to call Claude Co-Workout). It doesn't "work" as a standalone app. It's mostly a "display system" for whatever CC outputs to me, so I can take the daily workout to the gym.

I got into software bc I liked to put out fun products and projects; I never really liked the process of writing software itself. But either way I'm still running into the "it's harder to put projects out than ever" dilemma, even though the projects are way easier to make, and higher quality than ever.

I'm wondering if it'd be fun to have a "Ask HN: Show us what you've build with (mostly) AI" thread?
by rnimmer | 2026-03-01 17:54:45+00:00
My immediate reaction was, "Only 7?" but that may not be a fair thing to think, depending on what the constraints were.

The shift I've experienced is something akin to being able to finally focus on the aspects I've always enjoyed most: architecture and user experience. I review all the code, but through iteration my prompts have gotten better, and for the most part my automated codemonkey 'employee' produces good code. It's not reasonable to expect complex things to be one-shot; UX improvements always require follow-ups, and features need to be divided and conquered one at a time. Engineers who lack those higher level skills will struggle. You are leading a small team now, not just plugging away at implementing user stories.
by recursivedoubts | 2026-03-01 17:55:43+00:00
MCP has one thing going for it as an agentic API standard: token efficiency

The single-request-for-all-abilities model + JSON RPC is more token efficient than most alternatives. Less flexible in many ways, but given the current ReAct, etc. model of agentic AI, in which conversations grow geometrically with API responses, token efficiency is very important.