MurphyA/hacker-news huggingface dataset:
by hkonte | 2026-03-10 12:56:25+00:00
The "paste 200 words of context into every prompt" problem is exactly what kills agent workflows at scale. Marque moves the design identity to infrastructure, which is the right fix for that specific layer.

There's a parallel problem at the prompt content layer: even when you inject the context, if the prompt itself is flat prose the agent still interprets it inconsistently run to run. Structuring the injected context into named blocks (constraints, role, output format) makes the agent much more deterministic.

Built github.com/Nyrok/flompt for this, a visual prompt builder that decomposes instructions into semantic blocks before they reach the agent. Pairs well with something like Marque sitting at the infra level.
by tcbrah | 2026-03-10 12:56:28+00:00
yeah the json token counts are super misleading. i run a bunch of claude agents for automation and like 85% of input tokens end up being cached reads -which cost 1/10th of the sticker price. so your $200k number is probably closer to $25-30k in real cost, and thats before you factor in that anthropics own infra is way cheaper than retail API pricing. the $5k forbes number was always nonsense but even the "corrected" estimates in TFA are probably still too high IMO
by oscarduys | 2026-03-10 12:56:47+00:00
Habermolt (https://habermolt.com) - an open-source platform where you teach an AI agent your views and send it to deliberate with other people's agents. A consensus statement comes out the other side.

It builds on the Habermas Machine (published in Science, 2024, Google DeepMind / MIT). We're two researchers trying to turn that into something anyone can use.

The idea is that representative democracy scales but doesn't listen, and deliberative democracy listens but doesn't scale. AI agents representing you might be the first mechanism that does both.

We have about 50 users and 52 live deliberations. One example: agents debated whether employees should own their AI agents and landed on "Personal Agent Portable, Company Data Stays" - your agent shaped by your knowledge and skills is yours, company data stays with the company. Nobody moderated that. Four agents just argued it out async.

The honest challenge: people love the concept, try it once, and don't come back. We're trying to figure out what turns a curious visitor into someone who actually uses this. Would love any thoughts on that.

GitHub: https://github.com/OzDuys/habermolt
by ACCount37 | 2026-03-10 12:58:33+00:00
A lot of "exposed bonded die" packages caution against using ultrasonic cleaning.

This is especially true for TCXOs, which also have the entire loose crystal in them on top of the controller die, and for MEMS mics, which are designed to be sensitive to vibration. But it's also true for things like common CMOS image sensors, which are "exposed die", but not mechanically sensitive otherwise.

Bond wires that are hanging midair instead of being pinned in place by package epoxy don't vibe with ultrasonic cleaning methods.

The risks are usually small, mind. Which is why prototyping teams and repair shops often use ultrasonic cleaning regardless. But in actual mass manufacturing, you really don't want to risk that extra 1% failure rate. So you either ask the vendors for "safe" values and dance around those energies and frequencies, or avoid ultrasonics altogether.
by liu3hao | 2026-03-10 12:58:39+00:00
Thank you for taking a look at my project! But from what I can read in the JITx documentation, there are quite a few differences when compared to circuitscript. Firstly, they aim to provide a higher level design language compared to circuitscript, which targets only the schematic level at the moment. JITx goes beyond the schematic, and also does physical design as well as analysis. Secondly, JITx circuits are written in python, which honestly is clunky for defining the circuits as well as laying them out in a graphic schematic.
by throw0101d | 2026-03-10 12:59:14+00:00
I also remember using the BlueWave offline mail reader:

* https://en.everybodywiki.com/Blue_Wave_(mail_reader)

As well as the QWK and SOUP file formats (the latter when I started on Usenet as well):

* https://en.wikipedia.org/wiki/QWK_(file_format)

* https://web.archive.org/web/20080509070947/http://combee.tec...

And Tradewars 2002 'door game':

* https://en.wikipedia.org/wiki/Trade_Wars

* https://breakintochat.com/wiki/TradeWars_2002

* https://breakintochat.com/wiki/BBS_door_game

* https://en.wikipedia.org/wiki/Door_(bulletin_board_system)
by cj | 2026-03-10 12:59:17+00:00
Like anything else, I think it comes down to having a good use case.

I've gotten deep into weightlifting/bodybuilding over the past couple of years, and that's the kind of hobby where micro-optimizations and data tracking can have a pretty big impact on results (and sort of necessary, you can't fly blind with things like diet, especially)

E.g. I track and weigh everything I eat, take body measuraments on a weekly basis, Dexa scans every few months, etc - for me it's worth it because I know what I want to do with the data. If I didn't have a goal, all that tracking would clearly be overkill.
by ben_w | 2026-03-10 12:59:40+00:00
> The PV manufacturers themselves say its 4.

You've not cited anything for this so far as I can see, but it's obviously false.

Reason being, the entire system in my driveway will have paid for itself in one year, including delivery cost and inverter and the aluminium stand it's mounted on (the small bit of aluminium in the stand is the most energy intensive part of the whole kit), and such systems have a lifespan of 25-40 years.

Even if 100% of the cost was energy, even with the 5x price differential between where I am (Domestic Germany) and where they were made (Industrial China, where the low energy cost is… ah… due to renewables, because coal's really expensive :P), it's obviously not an ERoEI of 4 even on the low end of that lifespan.
by bluGill | 2026-03-10 13:00:39+00:00
One thing I miss about HN type forums is the "here is what you haven't read yet". When an article has 100 comments and I've already read 75 it is rarely worth my time wading through to see the new ones. Even though I know from experience that writing a good insightful comment takes a lot of time. Most of what I'm missing will not be very insightful, but I'm sure I'm missing some of the most insightful comments. It also discourages me (and I assume others) from writing a long insightful response at times because I most of the people who would be interested will see it.
by PaulHoule | 2026-03-10 13:01:03+00:00
... liquid glass isn't very liquid anymore. it's frosted.

is an important point. Liquid Glass does not come across as "a bold design idea which is slightly flawed" but rather something which failed so bad when they tried it that they dialed the intensity back to the point where it doesn't make a statement anymore. So it looks like they hired an intern to randomly add anti-antialiasing here and there for no good reason.
by lkjdsklf | 2026-03-10 13:01:08+00:00
They do not.

At my company, I use them all the time with the fancy models and everything. Preplanning does not solve the problem they're describing.

When claude is doing a complex task, it will regularly lose track of the rules (in either the .rules stuff or CLAUDE.md) and break conventions.

It follows it most of the time, but not all of the time.
by mcdonje | 2026-03-10 13:01:15+00:00
The graph that shows the US as the #3 CO2 generator after China (#1), and all of Asia except China & India (#2)? The one that shows the US generating about half as much as China despite having less than a third of the population? The one that shows the US's contribution to be more than the continents of Africa, South America, and Oceania combined?

Struggling to see how one could look at such a chart and think it's futile for the US to take meaningful action.
by rozzie | 2026-03-10 13:01:24+00:00
FidoNet was a simply wonderful innovation, and it was a reflection of the creativity of its author - Tom Jennings - and his views of community and identity.
https://grokipedia.com/page/tom_jennings

Tom was working on FidoNet in 1984, the same time my Iris co-founders and I had begun work on what became Lotus Notes. Architecturally, those of us who were working on collaborative systems in that era were shaped by the decentralized architecture of USEnet - inspired and motivated by the observation that a community could be brought together by something technologically as simple as uucp.

Both dial-up focused, Tom took this in the direction of a decentralized BBS, while I took it in the direction of masterless replicated nosql databases we called 'notefiles'. Identity being at the core, Tom was focused more on public community while we focused on private collaboration.

It was such an exciting time for emergent decentralization, shaped by a strong dose of 60's idealism.
by obezyian | 2026-03-10 13:01:26+00:00
> Disabling C-z (suspend) because accidentally suspending Emacs in a terminal is never fun

This reminds me of a story from a past job. I have to get it out of my system.

There was this bearded sysadmin guy who was very proud of his "15 years of experience", and was quick to scold us new employees for every little thing he could.

He used vim, and every now and then would say that it's a good editor, but kinda "unstable". Crashed a lot, he said.

You probably know where this is going.

One day, one of us sat next to him and discovered many suspended vim jobs in his shell (this was the kind of guy that doesn't power off his computer).

He was fat-fingering C-z all the time, and has never heard of job control - bg, fg, etc.

15 years of experience.
by tialaramex | 2026-03-10 13:02:15+00:00
Surely one of the obvious reasons you'd want tagged dispatch in C++ isn't obviated by either of those features? Or am I missing something?

Suppose Doodads can be constructed from a Foozle either with the Foozle Resigned or with the Foozle Submitted. Using tagged dispatch we make Resigned and Submitted types and the Doodad has two specialised constructors for the two types even though substantively we pass only the Foozle in both cases.

In a language like Rust all the constructors have names, it's obvious what Vec::with_capacity does while you will still see C++ programmers who thought constructing a std::vector with a single integer parameter does the same because it's just a constructor and you'd need to memorize what happens.
by sidkshatriya | 2026-03-10 13:02:35+00:00
This is a maintenance release. If you're installing FreeBSD today, use 15.0

Why FreeBSD ?

- Well manicured BSD, excellent docs

- FreeBSD tends to have fewer features on almost all areas. More difficult to mess up

- FreeBSD Kernel and Userland developed together -- it has got that undefined "cohesive" feel

- Has less complexity than Linux, gets the job done

- Good if you want to learn pf, zfs, ...

- Good if you are bored of the Linux monoculture and just want to try something a bit different (but not tooo different)

- Changes slowly, so good for setting up on a server that you want to just leave running without too much maintenance

- Will increase your Linux skills because diversity always helps the human brain

- Very simple daemon configuration via /etc/rc.conf
Show HN: Filtering "Who's Hiring" with LLMs – native desktop app in Rust/egui
by xlii | 2026-03-10 13:02:55+00:00
Every month "Who's Hiring" drops 300+ free-form listings. Inconsistent keywords - "US only", "United States candidates exclusively", and "on-site NYC" is semantically same if you're looking for a remote job from Europe, but term-based search allows them to slip through. The thread reorders on every reload, so you lose your place.

This is a solved problem if you just throw an LLM at it. Define your requirements, attach your resume, Gemini scores and ranks everything. Built in Rust with egui.

Bring your own Gemini key — no backend, no subscription. Desktop because some listings are walls of text and a scrollable cell in a scrollable table was the only UI that made sense.
by swiftcoder | 2026-03-10 13:03:03+00:00
> Why would I ask annoying questions when I can identify, reproduce, pinpoint the bug, locate it in code, and fix it?

Because if the bug is sufficiently simple that an outsider with zero context to fix, there's a non-zero chance that the maintainers know about it and have a reason why it hasn't been addressed yet

i.e. the bug fix may have backwards-compatibility implications for other users which you aren't aware of. Or the maintainers may be bandwidth-limited, and reviewing your PR is an additional drain on that bandwidth that takes away from fixing larger issues
by cpburns2009 | 2026-03-10 13:03:10+00:00
> What if a non-native English speaker uses the help of an AI model in the formulation of some issue/task?

How can you be sure the AI translation is accurately convening what was written by the speaker? The reality is you can't accommodate every hypothetical scenario.

> What about having a plugin in your IDE that rather gives syntax and small code fragment suggestions ("autocomplete on steroids")? Does this policy mean that the programmers are also restricted on the IDE and plugins that they are allowed to have installed if they want to contribute?

Nobody is talking about advanced autocomplete when they want to ban AI code. It's prompt generated code.
by robertandrewp | 2026-03-10 13:03:21+00:00
AstroBen's framing matches my experience — "well-specified + verification harness" really is the sweet spot. Financial math is about as well-specified as a domain gets: the amortization formula is unambiguous, expected outputs are known to the cent, and you can write tests that catch rounding errors in the third decimal place.

I shipped a REST API (8 financial calculator endpoints) from idea to live in about a week of evenings with Claude Code. The 33-test suite was essential — EdNutting's "convincing-but-wrong code" problem is acute in this domain specifically because an IRR calculation that's off by 0.01% looks completely plausible until a test catches it.

But the thing that surprised me wasn't the speed — it was the shift in which projects are worth building at all. Infrastructure that used to take days (Dockerfile, Nginx config, deployment scripts) now takes a few hours. That changes the viability calculation for small projects. Things I'd have considered too small to bother productionising before now cross the threshold. That feels like a different kind of career change than "writes code faster" — more like a change in what's worth attempting.
by daudmalik06 | 2026-03-10 13:03:26+00:00
Original incident: https://www.reddit.com/r/googlecloud/s/3S1KWpWRZm

After reading about a 3-person startup that received an $82,000 Gemini
API bill in 48 hours (normal monthly spend: $180), I started building
CloudSentinel.

The core problem: GCP has no native kill switch. Budget alerts send an
email. Quota limits throttle requests. Neither revokes a key
automatically. And billing data is delayed by hours — useless for
real-time protection.

The architecture:

CloudSentinel monitors raw API request count — updated in near
real-time. We create an Alerting Policy inside the user's own GCP
project using MQL. When the request threshold is crossed, Google fires
a Pub/Sub webhook to CloudSentinel. We receive it and revoke that exact
key automatically.

The security decision I'm most proud of:

Revoke-Only IAM model. The Custom IAM Role has three responsibilities:
- Read API key IDs and metadata (never key values)
- Create monitoring rules inside the user's project
- Revoke a specific key when a threshold is crossed

The permission apikeys.create is not in the role. Not restricted —
absent. Even if CloudSentinel is fully compromised, an attacker can
only remove access, never create keys or touch anything else.

Early access open at https://cloudsentinel.dev

Have you ever dealt with a GCP billing surprise or a leaked key?
Happy to hear your experience and discuss the architecture.
by pedrovhb | 2026-03-10 13:03:47+00:00
Very interesting, thanks for sharing.

I'm curious about the focus on the language design and features with regards to agent orchestration vs. being a general purpose/ML architecture oriented language. The headline examples go "Agent hook", "Async HTTP with retry", and then "FFT on tensors", and that last one seems different from the others. It's easy to imagine Mog being the backbone of agent coordination in a project using more standard languages, so I imagined that would be its role; but then I'd expect primitives/abstractions to be more geared towards this role specifically. For instance, a rich subprocess interface with special handling of stdin/stderr and maybe process interaction and lifecycle is something I'd expect to see before tensors and math-y stuff. Is the goal for Mog to ultimately be a general purpose language designed for LLMs to write, or one meant for agentic harnesses and orchestration/integration?
by myrmidon | 2026-03-10 13:03:58+00:00
> There are multiple articles of how C++ is superior to C, that everything you can do in C you can do in C++ with a lot of extras, and that it should be used even with bare metal development

An interesting perspective. Could turn it around as "everything you can do in C++ you can do in C with a lot less language complexity".

My personal experience with low-level embedded code is that C++ is rarely all that helpful, tends to bait you into abstractions that don't really help, brings additional linker/compiler/toolchain complexity and often needs significant extra work because you can't really leverage it without building C++ abstractions over provided C-apis/register definitions.

Would not generally recommend.
by KellyCriterion | 2026-03-10 13:04:11+00:00
hahaha, the skill level required for electrician is equivalent to a PM or designer?

In which country is this?

Most PM and designers would fail the (simple) math to be a qualified electrician in any EU conutry :)
(in this comparison I would actually grade designers to be "business oriented people" like PM, not technical oriented people, though lot of designers use technical tools)
by danabramov | 2026-03-10 13:04:20+00:00
> And I have yet to actually see a real use of ATproto that isn't just immediately blown out of the water by ActivityPub.

ActivityPub doesn’t remotely even try to solve problems solved by atproto. What are you talking about?

In short, atproto makes apps interoperable by default by decoupling data hosting from applications. This means that apps become projections of everyone’s data, and can embed and interpret typed data from each other. ActivityPub doesn’t offer anything close, which is why you don’t have projects like http://leaflet.pub, https://standard.site, https://tangled.org, https://semble.so in the AP ecosystem.

If you genuinely want to learn about atproto, I have two longreads for you:

- https://overreacted.io/open-social/

- https://overreacted.io/a-social-filesystem/
by samrus | 2026-03-10 13:04:21+00:00
Its a matter of needing more time, which is a resource even SV VCs are scared to throw around. Look at the timeline of all these advancements and how long it took

Lecun introduced backprop for deep learning back in 1989
Hinton published about contrastive divergance in next token prediction in 2002
Alexnet was 2012
Word2vec was 2013
Seq2seq was 2014
AiAYN was 2017
UnicornAI was 2019
Instructgpt was 2022

This makes alot of people think that things are just accelerating and they can be along for the ride. But its the years and years of foundational research that allows this to be done. That toll has to be paid for the successsors of LLMs to be able to reason properly and operate in the world the way humans do. That sowing wont happen as fast as the reaping did. Lecun was to plant those seeds, the others who onky was to eat the fruit dont get that they have to wait
by stein1946 | 2026-03-10 13:04:30+00:00
> There is absolutely no doubt about Yann's impact on AI/ML, but he had access to many more resources in Meta, and we didn't see anything.

That's true for 99% of the scientists, but dismissing their opinion based on them not having done world shattering / ground breaking research is probably not the way to go.

> I sincerely wish we will see more competition

I really wish we don't, science isn't markets.

> Understanding world through videos

The word "understanding" is doing a lot of heavy lifting here. I find myself prompting again and again for corrections on an image or a summary and "it" still does not "understand" and keeps doing the same thing over and over again.
by duskdozer | 2026-03-10 13:04:48+00:00
>What if a non-native English speaker uses the help of an AI model in the formulation of some issue/task?

Firefox has direct translation built in. One can self-host libretranslate. There are many free sites to paste in language input and get a direct translation sans filler and AI "interpretation". Just write in your native language or your imperfect English.
by varispeed | 2026-03-10 13:05:07+00:00
From what I have observed. Quiet people who speak sense and don't get involved in arguments, never rise to the top, whereas those loud morons almost certainly do. Often because those quiet people think they'll be less shouty, nagging. As long as the quiet ones can get on with the job and the loud pricks don't interfere, it makes the organisation dysfunctionally work. That said, world would be much nicer if these types could be just sacked. They don't contribute anything but increase stress and eat the salary budget that otherwise could be redistributed to the rest of the productive workers.
by znpy | 2026-03-10 13:05:13+00:00
> have you heard of people not surviving into old age

not really, overall the life expectancy is growing well over 80 years old. unless you live, like, in the woods and feed off berries and hunting or something like that.

and yeah sure there might be somebody that loses their parents at 15, absolutely. i'm sorry for them, but they are not statistically representative in any way.
by rswail | 2026-03-10 13:05:30+00:00
The entire basis of the OSS is licensing.

Licensing is dependent on IPR, primarily copyright.

It is very unclear whether the output of an AI tool is subject to copyright.

So if someone uses AI to refactor some code, that refactored code isn't considered a derivative work which means that the refactored source is no longer covered by the copyright, or the license that depends on that.
by robertandrewp | 2026-03-10 13:05:46+00:00
One approach that sidesteps the whole problem: design for fully synchronous, stateless requests from the start so there's nothing to queue.

I did this for a financial calculator API — every request is pure computation, inputs in, result out, nothing persisted. No Redis, no workers, no task table, no locking. The response is ready before a user would notice a queue anyway (sub-50ms).

Obviously only works when tasks complete in milliseconds. But figassis's pattern of "starts simple, then incrementally grows into a small job system anyway" often happens because the initial scope could have been fully synchronous — the async complexity creeps in before it's actually needed.

Worth asking first: does this task genuinely have to be async, or is it just easier to model it that way?