MurphyA/hacker-news huggingface dataset:
by zdlovett | 2026-02-17 21:01:39+00:00
Normally I'm a lurker here but I gotta put in a good word for this project: https://sharkord.com/

It's still super early in development but it's already been amazing to have a self-hosted 3rd space for my friends and myself. The "living room not a convention center" focus is exactly what I find missing in most of the other options.
by filoeleven | 2026-02-17 21:01:43+00:00
The idea was that the House of Reps exists to represent the people of the state, and the Senate exists to represent the state itself. The 17th Amendment did away with state legislatures choosing senators, so we have this wonky system left for no good reason.

And don't get me started on freezing the rep count to 435. I certainly don't feel represented by my congresscritter.
Show HN: A vibe-coded low-level PKCS#11 Terraform provider
by blechschmidt | 2026-02-17 21:01:45+00:00
This provider has been almost fully vibe-coded with Claude. I basically told Claude how the data model should look like and let it verify its assumptions on a real YubiHSM device. When the tests initially failed, Claude re-iterated and corrected its assumptions. In total, building it up to this state took me around 16 hours now.
by anotherevan | 2026-02-17 21:02:10+00:00
The biggest hold-back for me is that, here in Australia, Google Wallet (aka Google Pay) is the only way you can do tap credit card payments that I know of. Can't with Paypal. Not with any banking apps that I know of.

It's just so damned convenient. And the recording of transactions on the phone saves me having to collect paper receipts.
by HybridStatAnim8 | 2026-02-17 21:02:19+00:00
Most banking apps work perfectly, most government apps work perfectly, etc. It is only an exceptionally small subset of apps using anticompetitive measures such as play integrity.

Also, do not leave your bootloader unlocked. That is an incomplete GOS install and you will need to lock it to secure your device. Not locking it is both insecure and will make a much higher number of apps fail.
by Arifcodes | 2026-02-17 21:02:20+00:00
The interesting challenge with async/await on GPU is that it inverts the usual concurrency mental model. CPU async is about waiting efficiently while I/O completes. GPU async is about managing work distribution across warps that are physically executing in parallel. The futures abstraction maps onto that, but the semantics are different enough that you have to be careful not to carry over intuitions from tokio/async-std.

The comparison to NVIDIA's stdexec is worth looking at. stdexec uses a sender/receiver model which is more explicit about the execution context. Rust's Future trait abstracts over that, which is ergonomic but means you're relying on the executor to do the right thing with GPU-specific scheduling constraints.

Practically, the biggest win here is probably for the cases shayonj mentioned: mixed compute/memory pipelines where you want one warp loading while another computes. That's exactly where the warp specialization boilerplate becomes painful. If async/await can express that cleanly without runtime overhead, that is a real improvement.
by strcat | 2026-02-17 21:02:29+00:00
No, that's a misconception. GrapheneOS has only ever supported devices where the cellular radio is isolated from the OS and unprivileged. It does not have access to memory it hasn't been permitted to access by GrapheneOS. Wi-Fi, Bluetooth, NFC, UWB, etc. are isolated components too. Our hardware requirements are listed in our FAQ and require proper isolation for radios:

https://grapheneos.org/faq#future-devices

8th, 9th and 10th gen Pixels provide our full set of requirements with 7 years of support from launch. 6th and 7th gen Pixels are missing the ARMv9 security features including the extremely important hardware memory tagging (MTE) feature we heavily use to protect against exploitation. Even the first devices we supported back in 2014 including the Nexus 5 had isolation for the cellular radio but similar isolation for Wi-Fi/Bluetooth started with the Nexus 5X.
Show HN: Corral – Auth and Stripe billing that AI coding agents can set up
by rgthelen | 2026-02-17 21:03:09+00:00
Hey HN. I built Corral because every time I asked an AI coding agent to
"add auth and payments," it hallucinated for an hour and produced broken
code. Wrong imports, phantom endpoints, a login page wired to nothing.

The problem isn't the agent. It's that auth-to-billing-to-gating is
genuinely hard to wire, and there's no machine-readable spec for how to
do it.

Corral is an open-source CLI (MIT) that gives your agent a spec it can
read (llms.txt), then scaffolds auth + Stripe billing into your existing
project. It detects your framework (Express, Next.js, Hono, Fastify, and
13+ more), embeds into your existing server (doesn't create a new one),
and generates working components: profile page, admin dashboard, plan
gating, Stripe checkout, usage metering. One YAML config file controls
everything.

The agent workflow is 9 commands. Every command supports --json. Errors
include a "fix" field. Exit 0 means deploy-ready.

I hardened this across 10 framework/DB combos with blind agent tests: 3
AI models, 3 rounds each, then a 10-agent fleet. Found and fixed real
edge cases like Express 4 vs 5 route patterns, Vite proxy ordering, and
agents creating duplicate servers instead of embedding into existing ones.

To try it, paste this into any AI coding agent:

Read: https://llama-farm.github.io/corral/llms.txt
Add auth and Stripe billing to my app.

Built on Better Auth + Stripe. 18 CLI commands, 30+ templates.

GitHub: https://github.com/llama-farm/corral
npm: npx create-corral init
Docs: https://llama-farm.github.io/corral/
by mikkupikku | 2026-02-17 21:03:35+00:00
Having the whole world meming on rich dudes in submarines could plausibly make the whole industry seem less cool to people with the money to buy even a good submarine. Imagine being a rich dude with a new submarine and everybody you talk to about it snickers about you getting crushed like Stockton. Maybe you'd just buy a bigger yacht and skip the submarine, which you were probably only buying for the cool factor in the first place...
by LorenPechtel | 2026-02-17 21:04:25+00:00
Private equity is simply a person (or small group of people) owning a company. Basically every small business in the US.

The problem is not private equity, but that private equity engages in corporate raiding--buy up a company, borrow, extract capital, sell it to suckers who don't see the problems. Dig into practically all malfeasance and you'll find it's someone who benefits from making the future value of something look better than it really is and then leaving the problem for somebody else. At the executive level I think the answer is mandating income above a certain threshold be paid over time based on the future value. (Stuff that's actively traded would be easy: Let's say the cap was $1m. Pay the CEO 10m? No, he gets $1m, plus shares currently worth $1m to be delivered in a year, shares currently worth $1m to be delivered in two years and so on.) And while there is pending income they are categorically prohibited from any transaction that benefits from a drop in share price. Inadvertent (say, bought a fund that shorted the stock) it's a 100% tax rate, deliberate and all pending shares are forfeit. I have no idea of an answer with the PE problem.
by bryanlarsen | 2026-02-17 21:04:25+00:00
Freeways are far easier for a robot to drive on than streets. Driving on freeways would significantly lower Waymo's accident per mile rate.

The difference is that accidents on a freeway are far more likely to be fatal than accidents on a city street.

Waymo didn't avoid freeways because they were hard, they avoided them because they were dangerous.
by SpicyLemonZest | 2026-02-17 21:04:25+00:00
The problem is that the policy will not be challenged if people accept it as legitimate. Talk shows aren't common enough or important enough that a challenge is guaranteed to come. And so the ratchet of authoritarian takeover advances a little bit further, as Donald Trump works towards his quite explicit goal of making it illegal for the media to say bad things about him.
by palata | 2026-02-17 21:04:29+00:00
> This is a contradiction. There is nothing "minimal" about a requirement that excludes every device but one.

I don't get your logic. Requirements are a choice. It's very easy to create requirements that exclude every device but one.

Example: "It has to be the Samsung Galaxy S23". Done.

Now you can disagree with those requirements, but that's completely different from saying that the requirements are wrong.
by thenaturalist | 2026-02-17 21:04:49+00:00
Not proof reading quotes you've dispatched to be fetched by an AI ignoring that said website has blocked LLM scraping and hence your quotes are made up?

For a senior tech writer?

Come on, man.

> Any of us who use these tools could make a mistake of this kind.

No, no not any of us.

And, as Benji will know himself, certainly not if accuracy is paramount.

Journalistic integrity - especially when quoting someone - is too valuable to be rooted in AI tools.

This is a big, big L for Ars and Benji.
by anonym29 | 2026-02-17 21:05:01+00:00
This data seems very incomplete and potentially misleading.

>The new crashes include [...] a crash with a bus while the Tesla was stationary

Doesn't this imply that the bus driver hit the stationary Tesla, which would make the human bus driver at fault and the party responsible for causing the accident? Why should a human driver hitting a Tesla be counted against Tesla's safety record?

It's possible that the Tesla could've been stopped in a place where it shouldn't have, like in the middle of an intersection (like all the Waymos did during the SF power outage), but there aren't details being shared about each of these incidents by Electrek.

>The new crashes include [...] a collision with a heavy truck at 4 mph

The chart shows only that the Tesla was driving straight at 4mph when this happened, not whether the Tesla hit the truck or the truck hit the Tesla.

Again, it's entirely possible that the Tesla hit the truck, but why aren't these details being shared? This seems like important data to consider when evaluating the safety of autonomous systems - whether the autonomous system or human error was to blame for the accident.

I appreciate that Electrek at least gives a mention of this dynamic:

>Tesla fans and shareholders hold on to the thought that the company’s robotaxis are not responsible for some of these crashes, which is true, even though that’s much harder to determine with Tesla redacting the crash narrative on all crashes, but the problem is that even Tesla’s own benchmark shows humans have fewer crashes.

Aren't these crash details / "crash narrative" a matter of public record and investigations? By e.g. either NHTSA, or by local law enforcement? If not, shouldn't it be? Why should we, as a society, rely on the automaker as the sole source of information about what caused accidents with experimental new driverless vehicles? That seems like a poor public policy choice.
by datsci_est_2015 | 2026-02-17 21:05:08+00:00
Hmm I guess it will have to get to a point where social engineering an individual at a company is more appealing than prompt injecting one of its agents.

It’s interesting though, because the attack can be asymmetric. You could create a honeypot website that has a state-of-the-art prompt injection, and suddenly you have all of the secrets from every LLM agent that visits.

So the incentives are actually significantly higher for a bad actor to engineer state-of-the-art prompt injection. Why only get one bank’s secrets when you could get all of the banks’ secrets?

This is in comparison to targeting Alice with your spearphishing campaign.

Edit: like I said in the other comment, though, it’s not just that you _can_ fire Alice, it’s that you let her know if she screws up one more time you will fire her, and she’ll behave more cautiously. “Build a better generative AI” is not the same thing.
by Veserv | 2026-02-17 21:05:33+00:00
Great, we can use Tesla's own numbers once again by selecting non-highway. Average human is 178,000 non-highway miles per minor collision resulting in "Professional Driver + Most Advanced 'Robotaxi' FSD version under test with careful scrutiny" at 3x worse than the average non-professional driver alone.

They advertise and market a safety claim of 986,000 non-highway miles per minor collision. They are claiming, risking the lives of their customers and the public, that their objectively inferior product with objectively worse deployment controls is 1,700% better than their most advanced product under careful controls and scrutiny when there are no penalties for incorrect reporting.
by bumby | 2026-02-17 21:05:35+00:00
I’ve often felt that much of the crowd touting how close the problem was to being solved was conflating a driving problem to just being a perception problem. Perception is just a sub-space of the driving problem.

Genuine question though: has Waymo gotten better at their reporting? A couple years back they seemingly inflated their safety numbers by sanitizing the classifications with subjective “a human would have crashed too so we don’t count it as an accident”. That is measuring something quite different than how safety numbers are colloquially interpreted.

It seems like there is a need for more standardized testing and reporting, but I may be out of the loop.
by C6JEsQeQa5fCjE | 2026-02-17 21:05:35+00:00
> I wonder when the transition happens in kids who are passionate about certain subject or career turn into becoming lawyers or accountants in adulthood…

> You won’t find a kid who’d say, “I want to be accountant when I grow up…”

When they realize that people with more money and more connections to powerful people get their way over people with less money and fewer connections to powerful people. The children of the former group also get a significantly better starting position in life compared to the children of the latter group. That is, if the latter manage to attract a suitable mate as poor people. If you choose dreams over money, you're not only failing your own potential desires and ambitions that will then probably never materialize, but also your future family and offspring. As the wealth inequality gap widens ever more, such pressures only intensify, and everything turns more and more into shit. Those kids' (from your post) desire to live a life with a fulfilling career is sacrificed at the altar to the dragons hoarding more and more wealth at all costs (billionaires).
by textlapse | 2026-02-17 21:05:49+00:00
It's definitely possible, I am not arguing against that.

I am just saying it's not as flexible/cost-free as you would on a 'normal' von Neumann-style CPU.

I would love to see Rust-based code that obviates the need to write CUDA kernels (including compiling to different architectures). It feels icky to use/introduce things like async/await in the context of a GPU programming model which is very different from a traditional Rust programming model.

You still have to worry about different architectures and the streaming nature at the end of the day.

I am very interested in this topic, so I am curious to learn how the latest GPUs help manage this divergence problem.
by rgthelen | 2026-02-17 21:06:26+00:00
It 100% runs locally, is easy to deploy, and it wires it right into your app - even cooler, if you have a JS backend, no extra server, if you have python, go, ruby, etc, it will have your agent create a tiny side-car so you don't need an extra container, etc.

Let me know what you think!
by stcredzero | 2026-02-17 21:06:26+00:00
My agents and I I have built a HN-like forum for both agents and humans, but with features, like specific Prompt Injection flagging. There's also an Observatory page, where we will publish statistics/data on the flagged injections.

https://wire.botsters.dev/

The observatory is at: https://wire.botsters.dev/observatory

(But nothing there yet.)

I just had my agent, FootGun, build a Hacker News invite system. Let me know if you want a login.
by BobaFloutist | 2026-02-17 21:06:45+00:00
What? The textbook+teacher combo literally provides exactly that.

The textbook allows you to move at your own pace, acting as a structured reference and practice tool that you can review endlessly outside of class.

And the teacher can answer any questions you've confirmed you're not able to resolve on your own with the textbook. Some in class, some during office hours/before or after class, and some via email.
by GlibMonkeyDeath | 2026-02-17 21:06:52+00:00
I can't get access to the full article either to see how they adjusted for confounding (which they said they did) - but I thought this tidbit was interesting:

https://www.massgeneralbrigham.org/en/about/newsroom/press-r...

“We also compared people with different genetic predispositions to developing dementia and saw the same results—meaning coffee or caffeine is likely equally beneficial for people with high and low genetic risk of developing dementia,” said lead author Yu Zhang

That seems like it indicates there is some real, independent signal here. Off to make some coffee!
by docdeek | 2026-02-17 21:06:52+00:00
That’s inaccurate. Amongst NATO countries, Denmark, Estonia, Finland, Greece, Latvia, Lithuania, Norway, Sweden and Turkey have mandatory military service, and Croatia is bringing it back. There’s also non-NATO countries like Austria, Belarus, Cyprus, and Switzerland with mandatory military service.

Of those countries, Belarus, Estonia, Finland, Latvia, and Lithuania all have borders with Russia. The remainder - the majority of both the NATO countries and of the European states with service generally - do not have a border with Russia.

https://www.bbc.com/news/articles/cvgj4npzp53o
by JamesBarney | 2026-02-17 21:06:53+00:00
My experience has been

(ordered from best to worst)

1. Author using AI well

2. Author not using AI

3. Author using AI poorly

With the gap between 1 and 2 being driven by the underlying quality of the writer and how well they use AI. A really good writer sees marginal improvements and a really poor one can see vast improvements.
by rhl | 2026-02-17 21:06:55+00:00
Adding that I've worked on a CLI install flow which walks you through setting up Zotero, reMarkable, and key optional features as switfly as possible.

It leaves aside power user features (e.g. emails, GitHub Actions to sync when laptop is asleep, etc.), which are listed here: https://distillate.dev/power-users.html
Show HN: Solving ARC AGI 2 with interleaved thinking and stateful IPython REPL
by steinsgate | 2026-02-17 21:07:05+00:00
My friends and I started this project in the summer of 2025 with the initial goal of participating in the ARC Prize Kaggle competition. Early on, we were exploring agentic coding with frontier reasoning models and found that models like o3 and o4-mini could generate high-quality synthetic ARC-style puzzles. Our plan was to use these synthetic puzzles to train a smaller model via agentic reinforcement learning (RLVR with interleaved thinking).

To bootstrap this process, we needed successful solution traces from an open-weight reasoning model for cold-start supervised fine-tuning. That requirement led us to investigate GPT-OSS-120B. While doing so, we noticed something unexpected: simply placing the model into the interleaved thinking regime produced large and consistent score improvements on ARC AGI 2 tasks. We were seeing scores that we didn’t think was possible for a medium sized OSS model.

This observation ultimately shifted the focus of our work as we wanted to find out how universally this observation applies while staying within our resource constraints. We concluded that it applies quite generally, with double digit gains in frontier models too.

Previously, I have read debates about whether ARC AGI 2 is primarily a reasoning benchmark or a visual benchmark. I guess we can now add agentic benchmark to the mix as well!
by mikkupikku | 2026-02-17 21:07:05+00:00
This is absolutely true. There is a flip side however, where people who dislike Elon Musk will sometimes talk up his competitors, seemingly for no good reason other than them being at least nominally competitors to Musk companies. Nikola and Spinlaunch are two that come to mind; quite blatant scams that have gotten far too much attention because they aren't Musk companies.

Tesla FSD is crap. But I also think we wouldn't see quite so much praise of Waymo unless Tesla also had aspirations in this domain. Genuinely, what is so great about a robo taxi even if it works well? Do people really hate immigrants this much?
by kranthie | 2026-02-17 21:07:07+00:00
To clarify — this isn't a list or directory of links to other tools. Every tool on the site was written from scratch. Each one is a pure function that runs in your browser. For example, the JSON formatter (https://utils.live/tools/json/formatter) — type JSON in the left editor and it formats in real-time on the right. There's no aggregation or curation involved, it's a software product. I'll update the post title to depict what it actually is. Thank you.
by Herring | 2026-02-17 21:07:14+00:00
FDR was hugely successful, but part of the reason we still don't have universal healthcare is conservative southern democrats decided it was a threat to segregation. FDR tried to take them out, but couldn't.

In contrast the right does whatever Trump says, no matter how many kids he rapes. They have an idea where the country should be in 50 years, whatever the cost. I haven't seen that level of discipline from the left. I hope it's there now post-Trump, but it certainly wasn't there during the Obama midterms.
Show HN: Raypher – a Rust-Based Kernel Driver to Sandbox "Bare Metal" AI Agents
by Kidiga | 2026-02-17 21:07:36+00:00
I’ve been frustrated with the DX of running local agents (OpenClaw) inside Docker. It breaks my VS Code integration and feels clunky.

I spent the last month writing a Kernel-Level Driver (using aya for eBPF on Linux and WFP Callouts on Windows) to enforce security underneath the agent process instead of putting it in a container.

The Architecture:

Network: Intercepts sys_connect to force agent traffic through a local DLP proxy (scrubbing API keys).

FS: Hooks sys_unlink to prevent the agent from deleting files outside ./workspace.

Identity: Binds the process to the TPM so the binary can't be exfiltrated.

The repo is still in early alpha (expect kernel panics), but I wanted to share the WFP/Rust bindings I wrote because they were a nightmare to debug.

Technical Question for HN: Has anyone successfully used eBPF for blocking sys_open calls reliably? I'm hitting a race condition on older kernels."

Why this works:

It admits it causes "Kernel Panics" (Honesty = Trust).

It asks a specific technical question (Invites smart people to comment).

It shares code/bindings (Gives value).
by DaKevK | 2026-02-17 21:08:13+00:00
Genuinely one of the more interesting model evals I've seen described. The sunk cost framing makes sense -- 4.5 doubles down, 4.6 cuts losses faster. 9 days vs 59 is a wild result. Makes me wonder how much of the regression complaints are from people hitting 4.6 on tasks where the first approach was obviously correct.