MurphyA/hacker-news huggingface dataset:
by Samueedwards1 | 2026-03-04 16:55:53+00:00
Hey HN —
Here’s the exact intent I tested with Apcher.dev

Stripe customer.subscription.created → verify → idempotency → Postgres → provision workspace → SendGrid → Slack → monitoring.

Once expanded to production-safe logic, it became 19 steps.

First 6:
Verify webhook signature (STRIPE_WEBHOOK_SECRET)
Extract event.id, subscription.customer, price.id
Ensure price.id === pro_annual_price_id
Check processed_events for event.id
Insert event.id before side effects
Fetch full customer via Stripe SDK
Snippet:

Js id="j3m4zl"

if (!Stripe.verifyWebhookSignature(req.body, signature, process.env.STRIPE_WEBHOOK_SECRET)) {
return { success: false, error: 'Invalid webhook signature' };
}

const [existingEvent] = await PostgreSQL.query(
'SELECT * FROM processed_events WHERE id = $1',
[eventId]
);

if (existingEvent) {
return { success: true, message: 'Event already processed' };
}
Generated structure:
Id="s2x9pq"

my-workflow/
├── integration.js
├── scripts/
├── .env.example
├── apcher.lock
├── github/
└── README.md

The surprising part wasn’t the API calls — it was how much production scaffolding each “simple webhook” really needs.

Curious how others here handle idempotent webhook pipelines in production.
by bityard | 2026-03-04 16:55:56+00:00
They are pretty clearly targeting DIYers and enthusiasts who like tinkering with off-grid solar.

Grid-connected is an entirely different ball game. You will not see any open source projects there, or at least not any that anyone will want to use.

Let's think about why not. Anything grid-connected, you REALLY want a licensed electrician to plan and install. And competent electricians will NOT go anywhere near a piece of equipment that is not UL certified. A company producing equipment is NOT going to go through the expense of getting UL certified and then just release their design, PCB, and schematics for free.

And I want to be clear that I am a strong proponent of open source hardware, there are just certain situations where the incentives in reality just don't line up. This is one of them.
by Twirrim | 2026-03-04 16:55:59+00:00
I've been testing the same with some rust, and it's has spent a fair bit of time going through an infinite seeming loop before finally unjamming itself. It seems a little more likely to jam up than some other models I've experimented with.

It's also driving itself crazy with deadpool & deadpool-r2d2 that it chose during planning phase.

That said, it does seem to be doing a very good job in general, the code it has created is mostly sane other than this fuss over the database layer, which I suspect I'll have to intervene on. It's certainly doing a better job than other models I'm able to self-host so far.
Show HN: Secure Agent Starter – A minimal template for building safer AI agents
by timbucto2 | 2026-03-04 16:56:01+00:00
I’ve been exploring how to make AI agents safer to use in real applications, especially as they start interacting with tools, APIs, and real systems. One recurring problem is that agents can hallucinate actions, call tools they shouldn’t, or over‑reach in ways that make them hard to trust in production.

To experiment with better patterns, I put together a small starter repo:
Secure Agent Starter
https://github.com/timbuctoo/secure-agent-starter

It’s intentionally minimal — not a full SDK — but it demonstrates a simple structure for:
- Capability‑based permissions
- An “action firewall” pattern
- Example capability + policy files
- A tiny agent example
- A mock authorization step (no backend required)
- A folder layout you can drop into any agent project

The goal is to give developers a mental model for agent security before wiring up real tools or APIs. Think of it as a conceptual starting point for designing safer agent architectures.

I’d love feedback on:
- What security patterns you’d want to see next
- Whether this structure makes sense for real‑world agent projects
- Any missing pieces that would make this more useful

Thanks for taking a look.
by hbn | 2026-03-04 16:56:08+00:00
When Jobs announced the iPhone in 2007 he said it was running OSX but what that actually means is anybody's guess. iOS is closer to macOS in functionality today than the iPhone's first OS.

I personally liked iOS and macOS being separate things because making a desktop OS also work on a touchscreen has wider implications than it sounds. That's why these days everything in Windows is blown up like Fisher Price software and way bigger than necessary for a mouse cursor. Seems like that's the direction Apple is headed in anyway with Tahoe.
by heyitsgarrett | 2026-03-04 16:56:25+00:00
I love asesprite, procreate, pico8 and had this idea for programmable brushes bonking around my head for years now. Recently took some time between projects to put it together.

MOSS is a drawing toy where each brush is a tiny script that knows about every pixel on the canvas. You define how it paints with noise, randomness, patterns, stroke speed, pressure, and every touch executes the code.

So you can have a brush that scatters pixels like a real spray can or one that stamps shapes that mutate as you drag. Or perspective lines that actually converge. Or a fill bucket with smart gap awareness (I called it "Fill of my Dreams" and added to the brush list).

Happy to share brush code in the comments or explore ideas together. There's a (?) in the bottom right toolbar with API docs, and a prompt copy at the bottom if you wanted to work with the API through an agent.
by light_hue_1 | 2026-03-04 16:56:49+00:00
This defeatist attitude is why we can't have nice things anymore.

Fun fact, all of those things happened and this is already government policy for any NSF grant: https://www.nsf.gov/policies/document/faq-public-access

So maybe consider that when you give up on obvious things that are good based on some conspiracy theory that the "man" is trying to keep you down, what you're actually doing is being part of the system and endorsing it. Changes like this do happen, they just happen despite you.
by danlitt | 2026-03-04 16:57:06+00:00
Not answering my question!

> Police cannot access your E2EE DMs with a warrant.

They can and do, regularly. What they can't do is prevent you from deleting your DMs if you know you're under investigation and likely to be caught. But refusing to give up encryption keys and supiciously empty chat histories with a valid warrant is very good evidence of a crime in itself.

They also can't prevent you from flushing drugs down the toilet, but somehow people are still convicted for drug-related crimes all the time. So - yes, obviously, the police could prosecute more crimes if we gave up this protection. That's how limitations on police power work.
by dlisboa | 2026-03-04 16:57:08+00:00
A solution to a problem that doesn't change the current state of affairs, which by your definition makes it a simple solution, is not an actual solution.

There are plenty of simple solutions to real problems whose only blocker is upsetting the status quo. "We have no housing...let's build more housing" is, in fact, a very simple solution. That it doesn't happen has nothing to do with it the solution itself.
by aspectrr | 2026-03-04 16:57:12+00:00
In the land of infrastructure, servers are sacred. Humans are barely allowed to SSH into these servers, and LLMs are not even in the picture.
This is for good reason, one misspelled command and production is down. This is the reality that I saw working in infrastructure. However, I believe that the jump that Claude Code gave software engineers will happen to sys-admins, platform engineers, and dev ops people alike. I wanted to let LLMs onto these servers, and let them do my boring debugging work, safely. So that's what I built with Fluid.

A safe, auditable way to let LLMs debug and manage Linux Servers. Redact secrets, IP addresses, and keys from LLM inputs, have custom allowlists without completely hindering the LLMs performance, and audit logs. And once you are ready, give the LLMs sandboxes of your Linux Servers, allowing them to fix issues all on their own, safely.

Give it a shot and lmk what you think!
by SiempreViernes | 2026-03-04 16:57:23+00:00
Yeah, they seem to have been quite sloppy with these vignettes.

Thought note that in the situation of the mislabeled real case, the formal solution is could be a retraction of the entire highlight article since it is against the (poorly implemented) policy to have a real case study.

Don't know how patient consent for being used in a case study works, did this author get a perpetual license, did they just copy something from another article they wrote, or from an article someone else wrote?
by timbucto2 | 2026-03-04 16:57:34+00:00
Thanks for checking this out. A quick note: this repo is intentionally lightweight. It’s not trying to be a framework — just a starting point for thinking about agent security in a more structured way.

The next steps I’m considering:
- Adding a real capability‑token validator
- A more complete “action firewall” example
- A Python version
- A few real‑world tool integrations (email, DB, file ops)
- A diagram of how this fits into an agent stack

If you have thoughts on what would be most valuable, I’d love to hear them.
by btown | 2026-03-04 16:57:34+00:00
> The second time the same (or similar) input is used these states are already created and it is linear.

Does this imply that the DFA for a regex, as an internal cache, is mutable and persisted between inputs? Could this lead to subtle denial-of-service attacks, where inputs are chosen by an attacker to steadily increase the cached complexity - are there eviction techniques to guard against this? And how might this work in a multi-threaded environment?
by heyitsgarrett | 2026-03-04 16:57:40+00:00
Oh thanks for sharing this! I love asesprite, procreate, pico8 and had this idea for programmable brushes bonking around my head for years now. Recently took some time between projects to put it together.

MOSS is a drawing toy where each brush is a tiny script that knows about every pixel on the canvas. You define how it paints with noise, randomness, patterns, stroke speed, pressure, and every touch executes the code.

So you can have a brush that scatters pixels like a real spray can or one that stamps shapes that mutate as you drag. Or perspective lines that actually converge. Or a fill bucket with smart gap awareness (I called it "Fill of my Dreams" and added to the brush list).

Happy to share brush code in the comments or explore ideas together. There's a (?) in the bottom right toolbar with API docs, and a prompt copy at the bottom if you wanted to work with the API through an agent.
by RiverCrochet | 2026-03-04 16:57:42+00:00
I mean literally offline.

Computers were quite prevalent and useful before the notion of cloud computing, or the Internet.

Before the public was unleashed upon the Internet in 1992-1994, there were methods of information storage, indexing, searching, and exchange that didn't rely on real-time communications mediums operated by third parties. Example: CD-ROMs looked promising, the early 90's was smack in the middle of the "Multimedia" hey-day and gobs and gobs of data on nearly any subject was available and browseable at your perusal.

Of course it wasn't globally searchable, but there wasn't anything stopping anyone from making a master global index of CD-ROMs, selling it, and perodically updating it. Somebody (multiple somebodies) probably did. Libraries have been doing that for many decades. Replace chat with in-person meetups. Computer clubs were a thing in the 70s and 80s. DVDs still exist. DVD drives are $20 at my local Wal-Mart. SD cards are cheap and massive (1.5TB SD cards are a thing now).

Operating systems didn't always support TCP/IP. It's still something you can just turn off on a few of them.
by notepad0x90 | 2026-03-04 16:57:42+00:00
You can sell simple solutions as complex by focusing on what they solve. No one has to know your solution is simple unless they're looking under the hood.

And complexity doesn't always sell better. A lot of times it might look like the whole thing is messy, or too hard to maintain, tech burden nightmare. Things that are simple might look complex and vice versa too, I think anyone who had to implement requirements from people who don't understand the implementation complexities will know this very well.
by nfriedly | 2026-03-04 16:58:02+00:00
Fullstory | Atlanta | https://www.fullstory.com/

Fullstory offers privacy-preserving session replay and analytics for websites and mobile apps. Our session replays are nothing short of magical - they look almost like a video of the user's screen (with private details redacted) - and the combination with analytics creates eye-opening insights.

Our current engineering roles are all semi-onsite in Atlanta, USA (1 day per week in office):

* Software Engineer, Digital Experience Analytics - Go (golang), TypeScript, GCP - https://www.fullstory.com/careers/jobs/a786962d-68c1-48fa-8b...

* Senior Software Engineer, Web Capture - JavaScript/TypeScript, React, Go (golang) - https://www.fullstory.com/careers/jobs/76e583a9-74c0-42d4-ae...

* Software Engineer, Subtext - AI agents, Go, TypeScript - https://www.fullstory.com/careers/jobs/073bfc41-0ac6-4e59-a5...

It looks like we don't have pay ranges on any of the software engineer roles, but I'm guessing that the senior role might start at around $160~170k, and then the non-senior roles would be a touch below that.

We have additional roles for sales, consulting, product design, product management, and customer support open in Atlanta, Seattle, London, and Czechia as well as some Remote (US) options. See the full list at https://www.fullstory.com/careers?ashby_jid=bce3fcba-6b80-43...

For US roles, you can expect regular raises & bonuses, equity, and benefits including: health insurance, 401k matching (Vanguard), annual learning stipend, unlimited PTO, parental leave, and more. I take about 4-5 weeks vacation a year, in addition to ~3 weeks worth of company holidays (federal holidays + the week of Christmas to New Years.)

Folks in other countries can also expect a strong benefits package, but I'm not as versed on the details.

Additionally, you get a 5-week sabbatical after 5 years of employment - I took mine about a year ago, and it was fantastic.

To apply, please submit your info on the website, and our recruiting team will get in touch with you. If you have questions, feel free to reply here or contact me directly. (I'm an engineer on the iOS team, but I'll do my best to answer questions.)
by darkwater | 2026-03-04 16:58:05+00:00
Honest question: did you really not read the room there?
I mean, if I were on the interviewer side, asking that question, and getting an initial answer "Well, to be honest I would tell them to use GSheets because given the current situation is the highest benefits/costs solution, but for the sake of a system design interview I would also think about designing a bespoke internal solution that would use blah blah blah". You would get a "strong hire" evaluation and you would still be able to turn down the offer if you wanted because that question might have been a red flag to you.
by Ajakks | 2026-03-04 16:58:06+00:00
I have extensively used AI - its not as capable as you think it is. I frequently run into hard limits of its ability - I understand what recursive means in the sense of an AI, I can see it folding into itself pieces of this and that of what I've said or has been discussed to create the appearance of depth, growth or progress - none of that is real. The AI does not change.

I use AI as feedback - but only after setting almost 50 variables/conditions for that feedback, because AI is an automatic sycophant 100% - but it doesnt have to be that.

I occasionally use AI to transfer what I am saying to a person, into words that don't offend them - as I have absolutely no patience for people's insecurities when I find myself in a position where I need to teach them something, which happens often.

Let me be very clear - you are not capable of identifying AI content any longer, nobody is.

I extensively tested that by having a broad conversation with some of the smartest people on a platform (on earth in general really) whom all have very real credentials - I engaged with two sides of the AI coin regarding AI being self-aware or not, which is actually being debated, by some of the smartest people.

Half of my comments, I ran thru AI - or just completely generated from a prompt - my most liked comment was not mine - liked by people whose professional occupations is literally AI.

I'm sure this disturbs you - that an AI can create a Wikipedia page with more accuracy, better quality of writing, and in a more engaging way than 99% of human people - that is our actual reality tho.

Now all those little chat bots running around the internet, low level AI - they are creating slop, in exactly the same places and ways that humans do, their very words are modeled after the words people have literally written.

So, an AI can create a 100% perfectly written article for a major publication - and then AI can also fill the comments on that "perfect" article with absolute garbage - very similar to how things have always functioned online.

You need to interact with AI more , so you actually understand it and are not afraid of it, or imagining it with more ability than it has, or giving it human agency - AI is literally not capable of having agency at all.

Right now, there are tens of millions of millennials who are functionally identical to Boomers with smartphones.

You can't prevent AI from changing every aspect of human life - nobody can. You can be the boomers who refuses to adopt a smartphone - they all have smartphones now.
by andai | 2026-03-04 16:58:26+00:00
| Model | DocType% | Year% | Subject% | In $/MTok |

|----------------|----|-----|----|-------|

| llama-70b -----| 83 | 98 | 96 | $0.72 |

| gpt-oss-20b ---| 83 | 97 | 92 | $0.07 |

| ministral-14b -| 84 | 100 | 90 | $0.20 |

| gemma-4b ------| 75 | 93 | 91 | $0.04 |

| glm-flash-30b -| 83 | 93 | 90 | $0.07 |

| llama-1b ------| 47 | 90 | 58 | $0.10 |
by timbucto2 | 2026-03-04 16:58:30+00:00
A lot of agent frameworks focus on reasoning, planning, or tool orchestration — but very few focus on security boundaries. Right now, most agents can call any tool they’re given, and the only guardrail is “hope the model behaves.”

This repo is an attempt to explore a different pattern:
- Agents request actions
- A separate layer authorizes or denies them
- Capabilities are explicit, not implicit
- Policies are external, not baked into prompts

Even a simple mock version helps clarify the architecture. My goal is to make this pattern easier to adopt before agents start touching real systems.
by JumpCrisscross | 2026-03-04 16:58:41+00:00
> and still carry water for Trump?

I’m doing nothing of the sort. I’m carrying water for the truth that Iran was absolutely not negotiating in good faith regarding giving up their nuclear programme, that Israel was encouraging but not boxing in American decision making and that Witkoff and Kushner were (a) genuinely trying to strike a deal and (b) against kinetics when they started.

> Where do you, personally, draw the line?

Where the evidence does. If that winds up being pro- or anti- whatever party, I’ll look at that second. Facts aren’t partisan.
by dkargatzis | 2026-03-04 16:58:42+00:00
Hi HN!

Maintainers are increasingly dealing with large volumes of low-context PRs, especially as AI coding tools make it easier to generate changes without the surrounding intent.

Many repos already define contribution expectations in places like .cursorrules, CONTRIBUTING.md, or internal guidelines but those rules rarely translate into something enforceable during review.

We built Watchflow to bridge that gap: an open-source GitHub check that translates repository guidelines into enforceable validation logic that runs on every PR.

The model is intentionally hybrid:

- ~95% deterministic validators (fast, predictable, pure Python)
- Optional LLM checks for semantic cases like description / diff alignment
- LLM layer fails open so merges never block on model issues

Example rules:

- Require a linked issue
- Require CODEOWNERS review
- Block PRs above a LOC threshold
- Ensure PR descriptions align with code changes
- Validate contribution patterns defined in .cursorrules or agent guidelines

The goal is to close the loop between repository intent -> code diff -> enforceable governance.

Repo: https://github.com/warestack/watchflow

If there are review patterns you’re seeing that aren’t covered yet, happy to turn them into new validators!
by Sohcahtoa82 | 2026-03-04 16:58:55+00:00
Yeah, I had no training on being an interviewer before I started doing interviews. My manager gave me some tips, and I came up with two security bug-hunt exercises (was hiring AppSec engineers), but that was it.

Now, I wonder if I had rejected earlier candidates that I would have passed if I was a better interviewer.
by kkfx | 2026-03-04 16:58:57+00:00
Science has never been free, and it isn't mostly progressive; like the bulk of the population, it is hyper-conservative without admitting it. So, the first flaw lies in the very social structure of those who practice science.

The second problem, however, is a modern one: the pure, naked, and raw commercialization of science through "publish or perish", whereby the researcher is a Ford-style assembly line worker to be managed and who must be replaceable.

Without a MENTAL paradigm shift, even before a material one, we will only be able to plug small leaks on a ship with a torn hull.
by fsflover | 2026-03-04 16:59:03+00:00
> "Qubes is great but at the end of the day cannot protect against evil maid attacks to the level that pixel or apple phones can"

Yes, it can. Heads, TPM with a hardware key do exactly that, don't they? I'm not sure what you mean by "level".

> but cannot overcome the limitations of the platforms it builds off of

Yes, it can, if you use it correctly. Tell me your threat model, and I will explain how Qubes can protect you.
by mafuy | 2026-03-04 16:59:10+00:00
No joke: 15 years ago, when I was riding DB trains regularly, I got whole packs of refund forms. Took a while to find someone who would not refuse this request. I built a rudimentary transparent template in latex that had my name, address, etc. Pushed a whole pack into a printer to fill out most of the forms, leaving only the date and train to be manually inserted. My trains were always delayed, so this saved a lot of time.
by hsaliak | 2026-03-04 16:59:37+00:00
I'd like to plug https://github.com/hsaliak/std_slop/blob/main/docs/mail_mode... my coding harness (std::slop)'s mail model (a poor name i admit). I believe this solves a fundamental problem of accummulating errors along with code in your project.

This brings the Linux Kernel style patch => discuss => merge by maintainer workflow to agents. You get bisect safe patches you 'review' and provide feedback and approve.

While a SKILL could mimic this, being built in allows me to place access control and 'gate' destructive actions so the LLM is forced to follow this workflow. Overall, this works really well for me. I am able to get bisect-safe patches, and then review / re-roll them until I get exactly what I want, then I merge them.

Sure this may be the path to software factories, but it scales 'enough' for medium size projects and I've been able to build in a way that I maintain strong understanding of the code that goes in.