MurphyA/hacker-news huggingface dataset:
by thefern | 2026-03-05 19:42:19+00:00
I thought that was the default behavior. I think in terms of engineering, it sort of makes sense. Since a product can have multiple sellers. I am sure they could change it. My gripe was making a list for example, and wanting to see the total before adding to cart. It is PITA nevertheless. I am sure there is some psychology behing it like once you put it in cart, they give you a "cheaper" price you have nothing to compare it against. I've logged in with different accounts before and saw different prices. These days I try to buy local as much as I can.
by benleejamin | 2026-03-05 19:43:30+00:00
I don't think it's generally true that The Brand Age is as bleak as this essay might suggest.

Branding is not inherently unproductive, nor is it guaranteed to produce worse watches. They may be larger and less accurate, but consumers still (evidently) find value in the brand. A Grand Seiko or a Nomos or a Patek is perhaps now even more interesting & identity-productive than a watch from the 60s.

As technologists I think we're prone to dismissing improvements that aren't engineering-backed. But all life is storytelling, and labeling that work as "button-pushing" is… dismissive, to say the least.
by lenerdenator | 2026-03-05 19:43:46+00:00
The Cleveland Clinic would say you are right [0]

> Headaches.

> Persistent tiredness or sluggishness during the day.

> Disorientation.

> Confusion or altered mental state.

> Paranoia.

> Depression.

> Seizures.

No word from the Cincinnati Clinic though...

[0] https://my.clevelandclinic.org/health/diseases/24808-hyperca...
by logicchains | 2026-03-05 19:44:08+00:00
>It's the one you have access to with the top ~$200 subscription and it's available through the API for a MUCH higher price ($2.5/$15 vs $30/$180 for 5.4 per 1M tokens), but the performance improvement is marginal.

The performance improvement isn't marginal if you're doing something particularly novel/difficult.
by nailer | 2026-03-05 19:44:24+00:00
Got a source I can read without forking out? https://archive.is/tFzfZ

> > the Director General resigning over reports of bias across multiple issues including Israel/Hamas:

> a BBC editor resigning over an edit to a Trump documentary

Yes, as mentioned systemic bias is across multiple issues, including Israel/Hamas but not limited to that issue.

> I'm specifically looking for cases of BBC reporting disinformational Hamas statements as fact

Yes, the HonenestReporting critique mentioned does that.
by peteralbert | 2026-03-05 19:45:03+00:00
We validate tool calls with Pydantic models built directly from the JSON schemas, running inside the container. So the agent gets instant feedback if it passes the wrong type, misses a required field, or hallucinates a parameter — before anything hits the external API. You get the composability of code generation with the validation guarantees of structured calls.

In practice the self-correction rate is high. The agent writes a script, gets a traceback or validation error, reads it, and fixes the issue — usually within one retry. The skill files help a lot here because they contain the exact function signatures and known gotchas, so the model isn't guessing from memory. It's closer to a developer with good docs open than a model hallucinating API calls.

On the cron middle ground: the three-tier system is exactly that, and the conditional tier is where most automations end up. A typical example: "alert me when a competitor publishes a new blog post." The agent writes a Python script that checks the RSS feed every 30 minutes. If there's a new post, it spins up an LLM to summarize it and decide if it's worth alerting about. The check costs fractions of a cent. The LLM only runs when there's actually something to reason about.

The key insight we had is that the agent itself is often the best judge of which tier a cron should be. When a user describes what they want, the agent decides whether it needs reasoning every run or just a script with a conditional trigger. And if you ask it to audit its own crons, it'll often downgrade full-agent crons to conditional or scripted ones on its own. Turns out "look at this thing you're doing every hour and figure out if you actually need to think each time" is a prompt that works surprisingly well.
by Horos | 2026-03-05 19:46:15+00:00
Three real risks in your current approach before anything else. Shared references mutate silently — in JS, objects passed between your "tables" are aliases, not copies, so a mutation in one place propagates everywhere with no transaction and no rollback.
No atomicity — Node is single-threaded but async I/O means two callbacks can interleave writes on the same structure with no guarantee a multi-step update lands cleanly.
And everything disappears on crash — for socket/port/container state that's probably fine since it's observable from the system anyway, but you have no history.

That said, you may not need to leave your stack at all. V8's native Map is already a key-value store — O(1) reads, no overhead, typed in TypeScript. Your "tables" are just Maps and cross-referencing is composite string keys:

sockets.set(serverId:{serverId}:
serverId:{socketId}
, socketData).
No library, no dependency, no SQL. This covers your use case as described.

If you want ACID transactions and persistence without SQL, look at lmdb-js — a Node binding on LMDB, the fastest embedded KV store in existence, zero-copy reads, used in production for 20 years. Your tables become named databases, your records are typed values, your cross-references are composite keys. Same mental model you're building, with 20 years of correctness guarantees underneath.

What's the actual reason for building from scratch rather than using native Map for the in-memory case?
by zealtrace | 2026-03-05 19:46:18+00:00
This poem also owes its existence to W.H.R. Rivers. He was a notable individual. His early research was in anthropology and neurology. He was a key figure in the early treatment of what is now called PTSD, and a lead medical officer at Craiglockhart.

Another poem from Craiglockhart is Sassoon's "Repression of War Experience." It is one of the relatively uncommon works, both as literature and clinically, that depicts the sensory experience associated with PTSD. https://www.poetryfoundation.org/poems/57267/repression-of-w...

Incidentally, Rivers himself also wrote a paper titled "The Repression of War Experience." It was published in The Lancet around the same time. https://archive.is/EZerl

A century later, I believe the poet's attempt was more successful than the scientist's in sharing the data.
by tgarrett | 2026-03-05 19:46:20+00:00
Plasma physicist here, I haven't tried 5.4 yet, but in general I am very impressed with the recent upgrades that started arriving in the fall of 2025: for tasks like manipulating analytic systems of equations, quickly developing new features for simulation codes, and interpreting and designing experiments (with pictures) they have become much stronger. I've been asking questions and probing them for several years now out of curiosity, and they suddenly have developed deep understanding (Gemini 2.5 <<< Gemini 3.1) and become very useful. I totally get the current SV vibes, and am becoming a lot more ambitious in my future plans.
by vladich | 2026-03-05 19:46:24+00:00
You can't get a plan cache without a prepared statement, but you can get a prepared statement without a plan cache. It's not the same thing, and in most cases in Postgres prepared statements _do_not_ give you plan caching, because they are created for custom plans. "Custom plan" is a misnomer - having a "custom plan" means the query is replanned on each execution. It's a common misconception - even a sizeable portion of articles you can find on the internet miss this. But if you have a good reading comprehension, you can read, and, possibly, understand, this:

> A prepared statement can be executed with either a generic plan or a custom plan. A generic plan is the same across all executions, while a custom plan is generated for a specific execution using the parameter values given in that call.

here
https://www.postgresql.org/docs/current/sql-prepare.html

You're also mixing up parsing and planning for some reason. Query parsing costs like 1/100 of planning, it's not nothing, but pretty close to it.

Even though you're just a rude nobody, it still may be useful for others, who may read this stupid conversation...
by julianpye | 2026-03-05 19:47:01+00:00
Actually in many cases it is for social KPI storytelling. I know some wealthy people and at gatherings they love to tell 5-10min long stories of exclusive processes that they followed to gain something exclusive while dropping names and numbers. The processes are easy to understand for the entire social circle (i.e. not technical or business achievements which they can't easily disclose).
by dzink | 2026-03-05 19:47:04+00:00
Hoping to add to this perspective:

The ability to transfer a lot of money in the physical shape of brand watches costing 200k per piece may have added to their appeal. AppleTV’s show Friends and Neighbours upselling their value as Jon Hamm tries to steal them from neighbours may be product placement. But these were all tactics from the 50s and 60s where relatively few media sources meant you could buy your way into the hearts of the masses with an ads campaign.

Today we have a massively accelerated pace of society burning through fads and information - largely due to social media. The artificial scarcity trick is no longer an MBA secret. A brand, especially an AI brand, can burn in and out of favor in days. Transparency in society helps maybe bring out authenticity. Advertising of the past was often “advertising to your weaknesses” and that game is over.

If we can structure the transparency and apply it to politicians and other less transparent institutions that count on “Brand” to the list (especially ones with high margins and large networks) maybe the world will see true competition that benefits everyone more. Lack of transparency (and liqidity, and availability) are what make trust bubbles that distort markets.
by j45 | 2026-03-05 19:47:28+00:00
It's not, application logic exposed on the client side is always an attack vector for figuring out how it works and how attack vectors could be devised.

It's simply a calculated risk.

How much business and application logic you put in your Javascript is critical.

On your second unrelated comment about Wikipedia needing to use 2FA, there's probably a better way to do it and I hope mediawiki can do it.
by chrisweekly | 2026-03-05 19:47:45+00:00
Wow, that's a strong opinion and harsh words that come across as really entitled, and probably unfair. From my PoV, they're a tiny, scrappy, transparent and likeable company who built and maintain a fantastic software application that radically improved ~everything about my daily workflow and PKM. I get more value out of Obsidian in a day than most other apps in their entire lifespan. The core app is free! They have to eat. I'd probably throw $ at them even if they didn't charge a few bucks / month for Sync. (Which works flawlessly.) Sure it'd be cool if you could self-host their Sync module -- but many Obsidian users use other DIY approaches for sync; in the end it's markdown files on a local disk, do with it what you will.
Show HN: FreshLimePay – Generate PayPal and Stripe checkout buttons
by powerwild | 2026-03-05 19:47:50+00:00
Hi HN,

I built FreshLimePay to make accepting payments with PayPal or Stripe simpler for small projects and indie makers.

The idea is straightforward:
- Connect your PayPal or Stripe API keys
- Generate a checkout button or link
- Copy the snippet into your website or app

Payments go directly to your PayPal or Stripe account — FreshLimePay does not process or hold funds.

There are two versions:

• Self-Hosted version – install on your own server and run it with your own credentials.
• Cloud version – managed SaaS if you don't want to host anything.

The goal was to create something lightweight compared to full billing platforms when you just need simple payment buttons.

I'd really appreciate feedback from the HN community:
- Is this useful for your projects?
- What features would you expect next?
- Would you prefer self-hosted or SaaS for something like this?

Happy to answer questions.
by twitchard | 2026-03-05 19:47:52+00:00
Not sure DORA is that much of an indictment. For "Change Failure Rate" for instance these are subject to tradeoffs. Organizations likely have a tolerance level for Change Failure Rate. If changes are failing too often they slow down and invest. If changes aren't failing that much they speed up -- and so saying "change failure rate hasn't decreased, obviously AI must not be working" is a little silly.

"Change Lead Time" I would expect to have sped up although I can tell stories for why AI-assisted coding would have an indeterminate effect here too. Right now at a lot of orgs, the bottle neck is the review process because AI is so good at producing complete draft PRs quickly. Because reviews are scarce (not just reviews but also manual testing passes are scarce) this creates an incentive ironically to group changes into larger batches. So the definition of what a "change" is has grown too.
by zplizzi | 2026-03-05 19:47:52+00:00
i'm excited to try this - i'm finding that often when claude struggles with something i asked for, it'll often just quietly modify the tests to avoid having to actually solve the problem. which is especially annoying if i left it alone for a while hoping to come back to my problem being solved, and it actually just took a shortcut and quit. i'm hoping vet help can help provide some discipline lol.
by exceptione | 2026-03-05 19:48:30+00:00
Asymmetric warfare, a concept that costed the USA a few trillions before. A patient observer of the war in Ukraine could have updated some war doctrines. If you are an American tax payer, I would understand it if you were banging your head on the table right now. These flying lawn mowers are perfect for a Denial of Dollar (DoD) attack.
by KerrickStaley | 2026-03-05 19:48:31+00:00
Tried this out today and it feels half-baked unfortunately. I can't get auth working (https://github.com/googleworkspace/cli/issues/198).

The decision to pass all params as a JSON string to --params makes it unfriendly for humans to experiment with, although Claude Code managed to one-shot the right command for me, so I guess this is fine. This is an intentional design per https://justin.poehnelt.com/posts/rewrite-your-cli-for-ai-ag...
by creamyhorror | 2026-03-05 19:48:48+00:00
I've only used 5.4 for 1 prompt so far (reasoning: extra high, took really long), and it was to analyse my codebase and write an evaluation on a topic. But I found its analysis and writing thoughtful, precise, and surprisingly clearly written, unlike 5.3-Codex. It feels very lucid and uses human phrasing.

It might be my AGENTS.md requiring clearer, simpler language, but at least 5.4's doing a good job of following the guidelines. 5.3-Codex wasn't so great at simple, clear writing.
by johnnyanmac | 2026-03-05 19:49:07+00:00
Democratic ones do. But for 95% of causes it's hard to become so loud that they are forced to respond.

That's exactly why orgs like EFF exist. Most laws also aren't passed because of overwhelming consumer feedback. It's lobbied by special interests. Which sadly took a negative connotation over the last few decades, but lobbies can be for the people too.
by jawns | 2026-03-05 19:49:43+00:00
The consequence is that any company that does business with the U.S. military, and potentially any company that does business with the government in general, must stop using Anthropic's products.

Anthropic has vowed to fight this designation in court.

Without weighing in on the constitutionality or legality of the move, I think it's obvious that this kind of retaliation power is unmatched by any private business that has a contractual dispute.

If a private business doesn't like Anthropic's terms, it can walk away from the deal, but it can't conduct coordinated retaliation with other companies before ending up in antitrust territory or potentially violating the Sherman Act.

The fact that Pete Hegseth is willing to apply this type of designation against a U.S. company simply because he doesn't like its terms is pretty chilling. It's all the more scary once you consider which terms he objects to.
by pranshu-raj-211 | 2026-03-05 19:50:06+00:00
Location: Gwalior, India
Remote: true
Willing to relocate: Not until july 2026
Technologies: Python, Go, Docker, FastAPI, Redis, AWS
Résumé/CV: https://blog.pranshu-raj.in/resume/
Email: pranshuraj65536@gmail.com

I've worked as a SWE intern at Nector, building transactional voice agents and multi tenant backends, at Qlink building backend systems and handling deployments to AWS.

The best thing I've ever done is scale a real time leaderboard to 150,000 concurrent SSE connections on a single Linux machine, and I'm trying to improve on that still - https://github.com/pranshu-raj-211/leaderboard

Looking for internships or early full time roles, preferably with backend engineering oriented scope.

I write a bit on my blog, which I post here sometimes- https://blog.pranshu-raj.in
by ck2 | 2026-03-05 19:50:08+00:00
Good thing this isn't actually a war according to everyone in the administration

and they just annouced it's likely going through September (which means until end of year)

and they are now dropping 2000 pound bombs on targets next to civilians

https://www.politico.com/news/2026/03/04/evacuation-middle-e...

> "U.S. Central Command, meanwhile, is asking the Pentagon to send more military intelligence officers to its headquarters in Tampa, Florida, to support operations against Iran for at least 100 days but likely through September, according to a notification obtained by POLITICO"

(billion dollars a day and that's before replacing all the weapons)
Show HN: Reconlify – local-first reconciliation CLI for CSV/TSV and text logs
by testuteab | 2026-03-05 19:50:53+00:00
I built Reconlify, a local-first reconciliation CLI for comparing CSV/TSV and text logs with a structured audit report (not just raw diff).

Typical uses: QA regression checks after refactors, data migration validation from exports, finance/ops reconciliation of transaction files.

Features: key-based row matching, normalization rules (trim/case/nulls), row filtering/exclusions, line-by-line + unordered text modes, JSON report output.

Data never leaves your machine (offline-friendly).

Repo: https://github.com/testuteab/reconlify-cli

I’d love feedback on missing features for real-world reconciliation workflows (esp. Excel/DB connection next).
by j45 | 2026-03-05 19:50:59+00:00
Oh, for sure, rewrites generally do fail especially if the incoming lessons from the existing version aren't clear.

Finding a middle ground of building a roadmap to refactoring your way forward is often much better.

Appreciate the Joel link, nice to see that kind of stuff again.

With that being said if it's the same small team that built the first version, there can be a calculated risk to driving a refactor towards a rewrite with the right conditions. I says this because I have been able to do it in this conditions a few times, it still remains very risky. If it's a new or different team later on trying to rewrite, all bets are off anyways.

We have to remember 70% of software projects fail at the best of times, independent of rewrites.
by cedws | 2026-03-05 19:51:05+00:00
Yes, this has been an issue for so long and GitHub just doesn't care enough to fix it.

There's another way it can be exploited. It's very common to pin Actions in workflows these days by their commit hash like this:

- uses: actions/checkout@378343a27a77b2cfc354f4e84b1b4b29b34f08c2

But this commit doesn't even have to belong to the preceding repository. You can reference a commit on a fork. Great way to sneak in an xz-utils style backdoor into critical CI workflows.

GitHub just doesn't care about security. Actions is a security disaster and has been for over a decade. They would rather spend years migrating to Azure for no reason and have multiple outages a week than do anything anybody cares about.
by Rendello | 2026-03-05 19:51:10+00:00
If anyone is genuinely curious about this, they were indeed letting Russian gas through and stopped in 2025:

> On 1 January 2025, Ukraine terminated all Russian gas transit through its territory, after the contract between Gazprom and Naftohaz signed in 2019 expired. [...] It is estimated that Russia will lose around €5bn a year as a result.

https://en.wikipedia.org/wiki/Russia%E2%80%93Ukraine_gas_dis...
by woodruffw | 2026-03-05 19:51:26+00:00
Yep, this is essentially it: GitHub could provide a secure on-issue trigger here, but their defaults are extremely insecure (and may not be possible for them to fix, without a significant backwards compatibility break).

There's basically no reason for GitHub workflows to ever have any credentials by default; credentials should always be explicitly provisioned, and limited only to events that can be provenanced back to privileged actors (read: maintainers and similar). But GitHub Actions instead has this weird concept of "default-branch originated" events (like pull_request_target and issue_comment) that are significantly more privileged than they should be.
by mindslight | 2026-03-05 19:52:05+00:00
Perhaps I'm in the wrong thread but there is no part of me that wants to DIY my own power electronics design. I've designed a few bucks and boosts professionally and chasing down those failure modes was a pain. Victron = solid hardware, openly-documented protocols, no cloud? Fahgettaboudit.

(then again maybe someday I'll hit some wall with off the shelf MPPTs and find myself wanting to go down that rabbit hole lolol. but honestly AC coupling seems cleaner in terms of things like fault protection on longer runs - fault on a stiff mains circuit -> breaker will trip. Fault on a circuit where the current/power is intrinsically limited to what the solar panels can supply -> ???)

I asked about the transfer switch / monitoring because I've looked at the same problem here, first with a generator now with solar. Incoming power service is on the complete opposite side of the house from where I really want the power handling gear. The manual two breaker thing is practical (for a generator at least), but not code compliant here (no positive lockout).

I would think Victron would have an option for a remote transfer (/disconnect) switch, but I haven't really looked into it yet. It would still have to get the grid phase timing somehow to line them up before connecting, so something more than merely a dumb contactor.
by dmos62 | 2026-03-05 19:52:32+00:00
I guess a lot hinges on what kind of work you need to do while travelling. I've been on tmux and vim for the longest time which works great over mosh, so almost any device worked for me, as long as I had an ok internet connection. Spent a summer working in a park, on an epaper tablet and a bluetooth keyboard. Good times.
by scuff3d | 2026-03-05 19:52:37+00:00
The solution to this whole situation seems pretty simple to me. LLMs were trained on a giant mix of code, and it's impossible to disentangle it, but a not insignificant portion of their capabilities comes from GPL licenced code. Therefore, any codebase that uses LLM code is now GPL. You have a proprietary product? Not anymore.

Not saying there's a legal precedent for that right now, but it's the only thing that makes any sense to me. Either that or retain the models on only MIT/similarly licenced code or code you have explicit permission to train on.