MurphyA/hacker-news huggingface dataset:
by imiric | 2026-03-02 06:39:45+00:00
Which users?

The future you're concerned with defending includes bots being a large part of this community, potentially the majority. Those bots will not only submit comments autonomously, but create these projects, and Show HN threads. I.e. there will be no human in the loop.

This is not something unique to this forum, but to the internet at large. We're drowning in bot-generated content, and now it is fully automated.

So the fundamental question is: do you want to treat bots as human users?

Ignoring the existential issue, whatever answer you choose, it will inevitably alienate a portion of existing (human) users. It's silly I have to say this, but bots don't think, nor "care", and will keep coming regardless.

To me the obvious answer is "no". All web sites that wish to preserve their humanity will have to do a complete block of machine-generated content, or, at the very least, filter and categorize it correctly so that humans who wish to ignore it, can. It's a tough nut to crack, but I reckon YC would know some people capable of tackling this.

It's important to note that this state of a human driving the machine directly is only temporary. The people who think these are tools as any other are sorely mistaken. This tool can do their minimal effort job much more efficiently, cheaper, and with better results, and it's only a matter of time until the human is completely displaced. This will take longer for more complex work, of course, but creating regurgitated projects on GitHub and posting content on discussion forums is a very low bar activity.
by m-schuetz | 2026-03-02 06:40:11+00:00
This is way more cumbersome than mmap if you need to out-of-core process the file in non-sequential patterns. Way way more cumbersome, since you need to deal with intermediate staging buffers, and reuse them if you actually want to be fast. mmap, on the other hand, is absolutely trivial to use, like any regular buffer pointer. And at least on windows, the mmap counterpart can be faster when processing the file with multiple threads, compared to fread.

But I agree that it's a bizarre article since mmap is not a C standard, and relies on platform-dependend Operating System APIs.
by rerdavies | 2026-03-02 06:40:22+00:00
Neural Amp Models are small neural nets that have been trained to emulate the sound of classic guitar amps and effects pedals. The neural networks are trained on amp inputs and amp outputs (or effect inputs and effect outputs). Neural Amp Modeller Core is open source, licensed under an MIT license. TONE300.com provides both free online training of Neural net Models, and a massive collection community-generated high-quality Neural Amp Models. NAM has a large and very active online community.

It is obviously not possible to run huge LLMs in realtime; but it's been known for some time that very small neural network ML models can run in realtime, and can produce absolutely stunning simulations of real amps. The models are typically in the order of thousands of weights, not billions of weights. (Not actually sure what the weight count is for the A2 pico models that are being discussed in the original post. OP may be able to help with that).

These tiny neural network models not only accurately reproduce the sound of the original amps, but also manage to reproduce the feel of playing the original amp as well. The quality is dramatically better than most previous amp simulations (and entirely competitive with really high-end amp simulation technologies like Kemperer). It is breakthrough technology, for guitar pedals and amp simulators particularly, that literally changes everything in the music industry. The models are also relatively easy to train. TONE3000.com provides free online services for training models, and currently host a massive library of thousands of high-quality NAM models that are downloadable, free of charge.

The particularly interesting part of this report is that a single NAM model will be able to run on ridiculously tiny embedded processors. OP claims to have a 2nd-generation Pico NAM model running on a 500Mhz Cortex M7. First-generation Standard NAM models typically require a much more beefy processor: an ARM processor in the Pi 4 or Pi 5 sort of range (2.0Ghz Cortex A72, and 2.4Ghz Cortex A76 processors), or on x64 processors (an N100-class intel processor would be a good choice).

(Author of an open source project that uses Neural Amp Modeler Core technology to run NAM models on Raspberry Pis)
by belZaah | 2026-03-02 06:40:35+00:00
I’m not sure you are familiar with the way some traditional communities treat, say, single mothers.

The system is, that if you make unfortunate choices (such as moving away from your support network and carrying your life savings where you can forget them) and do not have anything (such as skills or low morals) to compensate, life is going to be hard. That has always been the case, that will always be the case. What the consequential decisions are, differs. But the basic premise of “f around and find out” holds.
by measurablefunc | 2026-03-02 06:41:49+00:00
Thanks. Next time I'll do more research on what counts for LLM code artwork before commenting on an incomplete implementation w/ all sorts of logically inconsistent requirements. All I can really do at this point is humbly ask for your & their avant-garde forgiveness b/c I won't make the same mistake again & that's a real promise you can take to the crypto bank.
by D-Machine | 2026-03-02 06:42:49+00:00
Appreciate this very sane take. The actual code always is more important than the intentions, and this is basically tautological.

When dealing with a particularly subtle / nuanced issue, knowing the intentions is still invaluable, but this is usually rare. How often AI code runs you into these issues is currently unclear, and constantly changing (and how often such issue are actually crucial depends heavily on the domain).
Show HN: The OpenRouter for OpenClaw – Shellrouter.com
by rickboers | 2026-03-02 06:42:57+00:00
Hey HN, I built ShellRouter because i want everyone to use all the cool OpenClaw lobsters everyone built.

Please give me feedback on how to improve the product and make it useful for everyone and I even want to make it open-source but i need help with that since i never did that before
by CamperBob2 | 2026-03-02 06:43:28+00:00
Scott Alexander has a decent article (or rather a guest blog post) at https://www.astralcodexten.com/p/all-lawful-use-much-more-th... that brings up the subject in the context of Anthropic and OpenAI's dealings with the Department of War (sic), and how their contracts with the DoW might be interpreted with regard to mass surveillance of Americans.

Worth checking out. I'm not personally knowledgeable enough to vouch for the veracity, though.
by jumploops | 2026-03-02 06:43:38+00:00
I've been experimenting with a few ways to keep the "historical context" of the codebase relevant to future agent sessions.

First, I tried using simple inline comments, but the agents happily (and silently) removed them, even when prompted not to.

The next attempt was to have a parallel markdown file for every code file. This worked OK, but suffered from a few issues:

1. Understanding context beyond the current session

2. Tracking related files/invocations

3. Cold start problem on an existing codebases

To solve 1 and 3, I built a simple "doc agent" that does a poor man's tree traversal of the codebase, noting any unknowns/TODOs, and running until "done."

To solve 2, I explored using the AST directly, but this made the human aspect of the codebase even less pronounced (not to mention a variety of complex edge-cases), and I found the "doc agent" approach good enough for outlining related files/uses.

To improve the "doc agent" cold start flow, I also added a folder level spec/markdown file, which in retrospect seems obvious.

The main benefit of this system, is that when the agent is working, it not only has to change the source code, but it has to reckon with the explanation/rationale behind said source code. I haven't done any rigorous testing, but in my anecdotal experience, the models make fewer mistakes and cause less regressions overall.

I'm currently toying around with a more formal way to mark something as a human decision vs. an agent decision (i.e. this is very important vs. this was just the path of least resistance), however the current approach seems to work well enough.

If anyone is curious what this looks like, I ran the cold start on OpenAI's Codex repo[0].

[0]https://github.com/jumploops/codex/blob/file-specs/codex-rs/...
by i_think_so | 2026-03-02 06:43:47+00:00
I'm still looking for a good source of organic steel-cut oats, so I'm doing "regular" in an Instant Pot.

Life hack: put the measured water and oats inside a bowl, but put the bowl inside the Pot with half an inch of water. You're going to dirty the bowl anyway; no sense dirtying the Pot too. Just use gloves or a potholder to remove the bowl, unless you have very tough fingers.

Zero chance of the microwave under-cooking the oats or, worse, over-cooking and making a gawdawful mess in there.
by anonnon | 2026-03-02 06:44:05+00:00
To be frank, this just sounds like self-serving BS, likely from someone who's only ever done front-end stuff and hasn't ever cracked open Godbolt (or doesn't even know what that is). Describing system constraints at a high-level, whether to an AI prompt or subordinate devs, and letting them figure out the details is much more akin to system architecture than actual engineering.
by jedberg | 2026-03-02 06:44:08+00:00
The way I write code with AI is that I start with a project.md file, where I describe what I want done. I then ask it to make a plan.md file from that project.md to describe the changes it will make (or what it will create if Greenfield).

I then iterate on that plan.md with the AI until it's what I want. I then ask it to make a detailed todo list from the plan.md and attach it to the end of plan.md.

Once I'm fully satisfied, I tell it to execute the todo list at the end of the plan.md, and don't do anything else, don't ask me any questions, and work until it's complete.

I then commit the project.md and plan.md along with the code.

So my back and forth on getting the plan.md correct isn't in the logs, but that is much like intermediate commits before a merge/squash. The plan.md is basically the artifact an AI or another engineer can use to figure out what happened and repeat the process.

The main reason I do this is so that when the models get a lot better in a year, I can go back and ask them to modify plan.md based on project.md and the existing code, on the assumption it might find it's own mistakes.
by Ajakks | 2026-03-02 06:45:23+00:00
MAD is actually a myth - especially when it was invented in the 60s, its more so now, in theory, but in all practical sense - nobody can use the massive nukes, they would prolly melt the polar ice and screw the climate for sure... but, having them means something else: nobody without an equivalent number can actually engage with you.

Which is why tactical nukes will be used in the future - likely by the US, Russia, or later on, maybe China. The British and French only have enough if we support them - India and Pakistan hardly have enough for each other...

Essentially - if we did take out say half a city somewhere and Russia doesnt go to their "final at bat" forever, for some country that isn't Russia - nobody else will attack us directly either bc they can't destroy our capacity to entirely remove them from existing.

China would want to fire back - but do you waste a billion people to make your enemy really, really angry and determined to use all of their remaining capabilities - which is more than everyone else (cept Russia), with just what is outside of the US in subs...

I'm not actually joking here - trading a part of an iconic city, to be taught an unwanted lesson, is superior to losing all the skylines of all the cities and learning no more lessons ever.

That modern understanding is actually entirely different than Mao originally approached an exchange - he said he wasn't worried - bc China has enough people and cities.

This is the real reason America has so many - bc with our large sprawled out country and global distribution of nuclear capabilities - we will always be the last one pushing red buttons. That is all that matters in an actual nuclear war/exchange - being the last one left IS Winning.

I wont explain more, bc it clearly is uncomfortable to people, but essentially, if the US and Russia were to "allow" each other to use tactical nukes (with rules, they set for each other) - like my example with Kiev (which would accomplish sooo many things - I wont elaborate further in case the Pentagon has somehow that) - with that one move, condoning "limited tactical nukes" bc they are "so weak" compared to the "real ones" - we would immediately return to a bipolar world split between the US and Russia.

All those conversations about the end of NATO would immediately stop, for example.
by tzs | 2026-03-02 06:46:13+00:00
> A significant component of the price gap is indeed subsidy. It would be foolish to say otherwise. It's $4700 of a $9000 price gap and thats not nothing.

The article says the subsidies are 5% of $4700 [1].

[1] "The February 19 report found Chinese state subsidies account for just 5% of BYD’s $4,700 per-vehicle cost gap with Tesla, with scale, cheaper talent, and in-house manufacturing making up the rest"
by silth253 | 2026-03-02 06:46:50+00:00
The Problem: Traditional AI context windows are transient, "forgetful," and computationally expensive to scale.
The Solution: An architecture designed for persistent, associative context. Instead of just processing tokens, the Cortex Memory Complex creates a structured, addressable memory layer that allows for long-term data retention and rapid retrieval without bloating the primary compute cost.

Key Architectural Pillars:
Decoupled Memory: Separating the "thinking" (inference) from the "remembering" (storage) to allow for infinite-feeling context.

Sovereign Data Integrity: Built with the philosophy that the user's memory remains their own, immutable and defensible.

Zero-Latency Recall: Optimized for sub-millisecond retrieval of historical context to inform real-time generation.

The "One-Night" Sprint
Status: Prior Art Established.

Record: CERN-timestamped via Zenodo.

Cost: $0 (Pure engineering sweat).

DOI: 10.5281/zenodo.18831099

The Vision: This isn't just a paper; it's a flag planted in the ground. By establishing this as open prior art on March 2, 2026, we ensure the future of memory-augmented AI remains accessible to builders, not just patent holders.
by mrtksn | 2026-03-02 06:47:55+00:00
That's why decapitation attacks can be very efficient, as wars are actually just extra-election elite changes since regular people minding their own business don't actually intend to kill some other group of people even if they are outrage and propaganda filled.

The problem is, those decapitation attacks work when the institutions are weak or structured in a way that all the power is in the hands of one person. It's always funny to watch in Hollywood movies everybody scrambled to save the US president and the US president being extremeyly important. Even in real life Americans swear in a replacement ASAP when the president dies (i.e. Kennedy). That's very funny from European perspective, RIP to the guy but just elect someone else why you are making it a big deal?

Also, the wars in Europe all have stories about how soldiers pausing the fight one the frontlines and having a chat sharing meals exchanging cigarettes with the opponent etc.
by d675 | 2026-03-02 06:48:01+00:00
agreed. Of the two software teams I've been on everyone has been a "senior". Some were fresh seniors, and some more staff. I've always been the most junior on the team.

2 devs on teach team were truly 10x before AI; each has 15-25 yrs of exp on very small teams, great at so many things: code - infra - linux internals - networking - incredible debugging skills - keep up with good practices - great docs - and desire to do things the "right way" - IQ + horsepower.

The other good senior devs may do some of those things.

My title is Senior 2 b/c I negotiated a raise during interview, but am mid-level at best. Now laid off.
by fuzzfactor | 2026-03-02 06:48:09+00:00
Methane (CH4) is the simplest hydrocarbon and the primary constituent of natural gas.

Even though it is not waxy it is also considered a paraffin. Like other paraffins it is largely inert except for that one little reaction with oxygen where it burns readily releasing great energy. But that usually requires contacting a spark or flame or there is no reaction.

The silicon analog is silane (SiH4), it spontaneously combusts quite easily without any spark at all.
by dwd | 2026-03-02 06:49:00+00:00
The US has shown very quickly that it is not a spent power.
Compare what they have done recently in Venezuela and Iran to Russia's botching of taking Kiev and the mess ever since.

But to quote Fiona Hill in regards to China, Russia and iran.

--------------------

The Chinese have told the Europeans many times when they've been asked, 'Why are you continuing to support Russia? And why do you want Russia to win?' that, 'Well, if we wanted Russia to win, they would have won.'

Also, if they wanted Russia to lose, Russia would probably have lost.

China is, again, just gauging their support and playing all of this out, gaming it out, really, as to how it affects the United States one way or another.

The same is true of North Korea and Iran, she says: support for Russia has been built on antipathy towards the United States and their own beef with the United States.
by fwipsy | 2026-03-02 06:50:03+00:00
I see a lot of arguing over whether this is "good" or not. This seems like a subjective question. Some people enjoy it, if you don't, it wasn't written for you--don't read it.

Maybe the arguing is really over whether it's higher-status to enjoy longform content, or to criticize it for not being more efficient? By identifying the argument, I've revealed it as silly, and clearly proven myself to be higher status than either side. The arguing may stop now. You're welcome.
by st_goliath | 2026-03-02 06:51:16+00:00
I've seen a similar project a while ago and thought this was about the same thing at first: [1][2]

Both essentially built a DIY chip tester for a 286 and both built around a Harris 80C286.

If I understood it correctly, the goal behind this project seems simulating the rest of the PC, purely for the challenge and learning experience, documenting the process of building the chip tester (and getting mildly philosophical in the process).

The other project was more directly interested in the 286 itself, undocumented instructions, corner cases in segmentation behavior, instruction cycle timing, etc. and also trying to find out if there are any difference between the Harris and Intel variants.

[1] https://forum.vcfed.org/index.php?threads/286-cpu-experiment...

[2] https://github.com/dbalsom/arduinoX86
by vessenes | 2026-03-02 06:51:25+00:00
I’m on the other side of this - I’d like it to happen passively and in an automated fashion. Right now I’m playing around with porting concepts from zettelkasten (card based handwritten knowledge systems) to openclaw memory.

Rather than just coalescing to markdown files, the memory-zet plugin looks for actionable durable information and files it inside the existing zettelkasten system with embeddings - a quick no-LLM step (well 300m parameter query embed, it’s fast) is run against incoming chats or as a tool - this returns cards (zettels).

Zettels are somewhat unique in that the original methodology included a post-writing categorization and linking step - I have the system doing this as well. Result - cards can give you a (possibly cyclic) directed graph of connectivity. I built it for ‘centaur’ mode, so I can edit, link, unlink, move, etc through a nice little web interface.

The auto links are not the same quality I would make. But they are genuinely useful; upshot is for anything incoming, the LLM can see information directly about the query (if we have it), stuff that relates whether or not it embeds similarly, and can follow up links if they look promising with a fast tool call.

I made this memory system my daily driver yesterday; so far it is a significant improvement over the core memory extension (write to markdown files, don’t worry about compaction bro, it will be fine)!

It’s already building out people and organizational card bases for things that come in via email and whatsapp - this is a dream, basically. I think it will scale over time - but it’s at least scaling nicely over a few days of work right now.
by sherr | 2026-03-02 06:52:55+00:00
According to the Economist recently [1], Israel recently caught a couple of men who bet on the timing of the Iran attacks last year :

"Last summer one “ricosuave666” won more than $150,000 on Polymarket, a betting platform. Their true identity was not clear, but the source of the winnings was: ricosuave666 had bet, with suspicious accuracy, on the precise timing of Israel’s attacks on Iran."

So, these people can be found. Overall however, the magazine does not think that these markets should have a blanket ban.

[1] https://archive.is/W8Ga8 (Prediction markets are rife with insider betting)
by wahern | 2026-03-02 06:54:32+00:00
GCC supports specifying endianness of structs and unions: https://gcc.gnu.org/onlinedocs/gcc-15.2.0/gcc/Common-Type-At...

I'm not sure how useful it is, though it was only added 10 years ago with GCC 6.1 (recent'ish in the world of arcane features like this, and only just about now something you could reasonably rely upon existing in all enterprise environments), so it seems some people thought it would still be useful.
by perryraskin | 2026-03-02 06:54:43+00:00
Building upfile.sh because AI agents need a better, cleaner way to upload screenshots and files, in order to get a URL back instantly.

Supports public (permanent CDN), expiring (TTL-based), and private (auth-gated) uploads. --json flag for scripting/agents.

Built on Cloudflare Workers + R2. Currently waitlist, happy to give HN folks early access.

https://upfile.sh
Show HN: Greens – mirror private GitHub activity to your public graph
by yuvrajangads | 2026-03-02 06:56:35+00:00
I built greens because most of my day-job work is in private org repos, so my public GitHub graph looked inactive.

The tool runs locally, scans repos you choose in read-only mode, extracts commit timestamps for your author email, and creates empty commits with those timestamps in a public mirror repo. No source code, diffs, or filenames are copied.

If `gh` is configured, it can also mirror PR/review/issue activity. It's a bash CLI, installable via Homebrew (`brew install yuvrajangadsingh/greens/greens`).

I know some people view this as graph-gaming, fair point. My intent is not to imply public OSS output, only to make private work volume visible. Also worth noting: check your company policy before using it.

Feedback welcome, especially on edge cases or failure modes.
Show HN: Workz–Git worktrees with zero-config dep sync and a built-in MCP server
by rohansx | 2026-03-02 06:56:47+00:00
I built workz to solve a daily frustration: git worktree add drops you into a directory with no .env, no node_modules, and 2GB of disk wasted per branch if you reinstall.

workz does three things:

Auto-syncs — symlinks heavy dirs (node_modules, target, .venv) and copies .env files into every new worktree
Fuzzy switching — skim-powered TUI to jump between worktrees, with shell cd integration like zoxide
MCP server — workz mcp exposes 6 tools so Claude Code/Cursor can create and manage worktrees autonomously without human intervention
Written in Rust, single binary, zero config for Node/Rust/Python/Go/Java projects.

cargo install workz or brew install rohansx/tap/workz

https://github.com/rohansx/workz