MurphyA/hacker-news huggingface dataset:
by nadirollo | 2026-03-03 20:52:06+00:00
This is a must when your systems deal with critical workloads. At Fastly, we process a good chunk of the internet's traffic and can't afford to be "down" while waiting for the CI system to recover in the event of a production outage.

We built a CI platform using dagger.io on top of GH Actions, and the "break glass" pattern was not an afterthought; it was a requirement (and one of the main reasons we chose dagger as the underlying foundation of the platform in the first place)
by rtkwe | 2026-03-03 20:52:09+00:00
You can see an unofficial tracker [0] of the Starlink downlink network and see how outside of some areas your data is only moving a few tens of miles away most of the time before it's sent down to a ground system. Their sats have 3 200 Gbps laser communicators for intra constellation routing which is pretty small for the task of replacing fiber optic links.

[0] https://www.google.com/maps/d/viewer?mid=1805q6rlePY4WZd8QMO...
by MayeulC | 2026-03-03 20:52:12+00:00
I'm curious, what is the powe draw for such a system? Of course, it heavily depends on the disks, but does it idle under 200W?

I personally feel like I will downscale my homelab hardware to reduce its power draw. My HW is rather old (and leagues below yours), more recent HW tends to be more efficient, but I have no idea how well these high end server boards can lower their idle power consumption?
by anematode | 2026-03-03 20:52:15+00:00
As someone who's worked on bits of collaborative software (and is currently helping build one at work), I'd caution people from using CRDTs in general. A central server is the right tool for the job in most cases; there are certain things that are difficult to handle with CRDTs, like permissions and acquiring locks on objects.

That makes CRDTs great for building rich collaborative apps, like Google Docs and Figma — without requiring a central server to sync changes.

As far as I'm aware, this is false. Google Docs and Figma don't use CRDTs, and iirc Figma wrote a whole article on their syncing system, which resists clean categorization.
by derefr | 2026-03-03 20:52:32+00:00
I think these aren't meant to be representative of arbitrary userland-workload LLM inferences, but rather the kinds of tasks macOS might spin up a background LLM inference for. Like the Apple Intelligence stuff, or Photos auto-tagging, etc. You wouldn't want the OS to ever be spinning up a model that uses 98% of RAM, so Apple probably considers themselves to have at most 50% of RAM as working headroom for any such workloads.
by DivingForGold | 2026-03-03 20:52:39+00:00
Witness as GP transfers out any remaining assets through crypto (we got hacked !), declares bankruptcy, and comes back with a new name, and Big Oil gets HOSED.

. . . She apparently will not go to jail because she is old, and it would be “sentencing her to die within the state prison system.” And hey, while she is accused of moving millions of dollars and various properties she owns to third parties to avoid financial penalties -- this Green Peace story the same take as the "70M Boomer" title below . . .
by onyxblade | 2026-03-03 20:52:50+00:00
I made a Rails demo that sends and receives [DIDComm](https://identity.foundation/didcomm-messaging/spec/v2.1/) messages — a decentralized messaging protocol based on W3C DIDs (Decentralized Identifiers).

An server implementing DID(did:web more precisely) will serve an identity document at `/.well-known/did.json`, including the public keys for encryption and available service endpoints(DIDComm). For example, my demo server has its document here https://dc.mbkr.ca/.well-known/did.json . This server amounts to the DID `did:web:dc.mbkr.ca`. To send a message to me, you only need this DID and the message itself.

I also set up a public demo server at https://dc-public.mbkr.ca/ which can be logged in using `public` as password.

When implementing, I first tried to generate a Ruby implementation of DIDComm specification, it kind of works but I have no confidence on it since I'm not expert on encryption. Then I think it's better to reuse the [Rust reference implementation](https://github.com/sicpa-dlab/didcomm-rust) . The Rust implementation emits a wasm module, but `wasmtime-rb` seems not mature enough to use it. Eventually I made a sidecar HTTP server to wrap the wasm library, and expose HTTP endpoints that can be called by Ruby or any language. https://github.com/onyxblade/didcomm-http

Hope you find it fun!
by matheist | 2026-03-03 20:52:54+00:00
Right, I was taking it as given that the problem of choosing a hemisphere canonically for a point meant "such that the argument works in the same way as for the circle".

Bertrand paradox just doesn't apply here, there's a natural measure on the circle and all higher dimensional spheres. I wouldn't expect an article on this subject to need to make that clarification unless it's dealing with chords or some other situation without a natural measure.
by throwup238 | 2026-03-03 20:53:01+00:00
> even the internal talent to know whether they are hiring a good infrastructure engineer or not during the interview process.

This is really the core problem. Every time I’ve done the math on a sizable cloud vs on-prem deployment, there is so much money left on the table that the orgs can afford to pay FAANG-level salaries for several good SREs but never have we been able to find people to fill the roles or even know if we had found them.

The numbers are so much worse now with GPUs. The cost of reserved instances (let alone on-demand) for an 8x H100 pod even with NVIDIA Enterprise licenses included leaves tens of thousands per pod for the salary of employees managing it. Assuming one SREs can manage at least four racks the hardware pays for itself, if you can find even a single qualified person.
Show HN: TrAIn of Thought – AI chat as I want it to be
by two-sandwich | 2026-03-03 20:53:06+00:00
My conversations with LLMs branch in many directions. I want to be able to track those branches, revert to other threads, and make new branches at arbitrary points. So I built my own solution to it.

It's essentially a tool for non-linear thinking. There's a lot of features I'd love to add, and I need some feedback before I take it anywhere else. So, I'm listening to whatever you're thinking is broken.

Basic feature set:
- Branching conversations: follow up from any node at any time, not just the latest message

- Context inheritance: when you branch off a node, the AI gets the full ancestry of that branch as context, so answers are aware of the whole conversation path leading to them.

- Text-to-question: highlight any text in an answer to instantly seed a new question from it.

- Multi-provider AI: compare and adjust responses from OpenAI, Anthropic, and Google Gemini.

- Visual graph: the conversation renders as a React Flow graph with automatic layout, so you can see the whole structure at a glance.

- Shareable links: your entire chat is compressed and stored in the URL. Everything is local (well, except the API calls).

- Branch compression: long branches can be collapsed into a summary node to keep the graph tidy.
by matsemann | 2026-03-03 20:53:22+00:00
Is that personnel cost more than running on someone else's infra? Just counting the amount of people a company now need just to maintain their cloud/kubernetes/whatever setup, paired with "devops" meaning all devs now have to spend time on this stuff, I could almost wager we would spend less on personnel if we just chucked a few laptops in a closet and sshed in.
by carefree-bob | 2026-03-03 20:53:50+00:00
Correct, most mathematicians, at least the ones I know, do not actually spend time thinking about Good Will Hunting, but it's the kind of stuff that science writers eat up.

If you want to know a movie that I actually heard mathematicians discussing, it would be "A Beautiful Mind", and then only because some people were complaining about how the minor characters misrepresented the mathematicians and especially how the Princeton Math department was unfairly caricatured in order to create dramatic tension (you need an antagonist, after all).

In reality Nash was treated with incredible generosity and kindness, and was given extreme affordances. For example, he visited Nirenberg at Courant and gave him a stack of hundreds of pages of dense, hand written notes that were the proof of the embedding theorem, and Nirenberg took enormous time to go through it and try to understand what Nash did, and then championed the proof. With no renumeration or credit, just as a professional courtesy and desire to see if the proof is correct. Nash was not easy to work with, but because so many people were willing to devote time to reviewing and correcting the proof -- which took 5 years -- it was eventually published. Moser, Gromov, Chern, and Kuiper all played a massive role, donating huge amounts of their personal time in order to help Nash.

But, as is usually the case with real life, it doesn't make for a good 2 hour dramatic story. It's a shame, because the real story is a great story.
by philistine | 2026-03-03 20:54:14+00:00
Unfortunately, Apple is not one to revisit their previous decisions very often. With the move to Apple Silicon, the capabilities of the bootloader were locked in (chain-of-trust, ability to load other OS and keep chain-of-trust on macOS) and that was it. Apple is telling you what they support; there's never any damning secret with them. You want to run Linux? Run it in a VM on macOS. That's what marketing has been saying since day one of the M1.

Them's the breaks.
by cs02rm0 | 2026-03-03 20:54:27+00:00
The very concept they've been trying to sell is wrong headed.

Kids are trying to access XYZ which isn't safe (where XYZ may as well be "the internet") -> verify the ages of all adults, because we can't verify the age of a kid.

Meanwhile kids, like adults, can just find another route to access what they want. So some subset of adults hands over their identity information to an untrustworthy third party of dubious security.

I can't see how that does anything other than make the situation worse.
by Estuary | 2026-03-03 20:54:40+00:00
Estuary | US-Based / Remote | Full-time – https://estuary.dev/

Estuary is a VC-backed, post–Series A startup powering right-time data replication and transform — from sub-second CDC replication to terabyte-scale OLAP data flows.

We’re open-source, developer-first, and focused on making data movement radically simpler across both our Platform and Applications layers.

We’re hiring for:

Senior & Staff Backend Engineers

5+ years backend experience; Go required, Rust a plus. Own core systems powering real-time data pipelines. Build complex API/database integrations, improve connector frameworks, and tackle deep challenges in performance, reliability, and developer experience.

Backend Engineer (Integrations) – 2–4 years of backend experience. Help expand and maintain our catalog of real-time data connectors to SaaS tools using Python. You’ll work closely with experienced engineers to build and optimize integrations with third-party systems, while deepening your skills in infrastructure and stream processing.

Solutions Engineer - Work with the founding team to help customers use Estuary effectively. Collaborate closely with engineering and product, shape how users integrate real-time data, and feed insights back into product development.

What we’re looking for: Engineers who care about building reliable, maintainable systems and enjoy working with complex APIs and data flows. We value curiosity, clear communication, and a willingness to learn.

Bonus points for experience with CDC tools, open source contributions, or fast-paced startups.

To apply: Email your resume to careers@estuary.dev
by ElevenLathe | 2026-03-03 20:54:45+00:00
Workers ultimately have a job because they are useful to management, and management have a job because they are useful to ownership. Top management has insane levels of compensation as a strategy by ownership to alight management's interests with their own, by turning them into owners. If there is going to be a management layer at all, for example the proposed "A-suite", then their compensation will balloon for exactly the same reasons.

CxO salary isn't the market clearing price for the labor these people perform, it's more like power-leveling your friends in an RPG so that they can quest with you. Owners want their managers' interests to be with capital, so they have to give them some.
by MostlyStable | 2026-03-03 20:55:05+00:00
I've heard it claimed that the era of being able to do this (buy slightly old used server hardware cheap on ebay) is coming to an end because, in the quest for ever more efficiency, the latest server hardware is no longer compatible with off-the-shelf power supplies etc. (there was more but that's the part that I remember) and therefore won't have any value on the second hand market.

I hope it was wrong, but it seems at least plausible to me. I'm sure that probably fixes could be made for all these issues, but the reason the current paradigm works is that, other than the motherboard and CPU, everything else you need is standard, consumer grade equipment which is therefore cheap. If you need to start buying custom (new) power supplies etc. to go along, then the price may not make as much sense anymore.
by cloverich | 2026-03-03 20:55:48+00:00
> They want your real ID. They do not need it.

I think that is exactly backwards. Many of the companies integrating with KYC/AML providers (such as my company) definitely don't want to be dealing in ids, just like most companies don't want to be dealing in storing credit card numbers (and the compliance that goes along with it). Its why Stripe exists, and its why ID verification companies exist.
by jijji | 2026-03-03 20:55:51+00:00
The way that it would make sense for age verification is if there was some federal system that verifies your identity and then it would use a public key crypto system to allow a third party to check whether or not this person is over the age or not.... common systems I see being used right now that could be integrated for this purpose would be login.gov or id.me... they could allow a token-based authentication system for verification of age without having to divulge any other information about the person. these systems are already being used by the IRS, VA, SSA and other Federal systems.
by homarp | 2026-03-03 20:56:11+00:00
eg https://en.wikipedia.org/wiki/Mondragon_Corporation (discussed on HN https://news.ycombinator.com/item?id=22287794 and https://news.ycombinator.com/item?id=22287794)

or https://en.wikipedia.org/wiki/Igalia (can't find any discussion related to their coop model - there is https://news.ycombinator.com/item?id=37799973 without any comment )
by 1970-01-01 | 2026-03-03 20:56:14+00:00
That's not it. There is 2 parts 2 fraud.

Part 1: misrepresentation of fact

Part 2: harm or loss due to that misrepresentation

You must prove both.

https://definitions.uslegal.com/f/fraud/#:~:text=and%20upon%...
by twhb | 2026-03-03 20:56:14+00:00
Apply the same logical test to freedom of speech, and you’ll get the same result.

You’re not missing anything about what’s likely to happen to you personally. What you’re missing is the manner in which rights shape your life and your society even when you don’t exercise them, and sometimes even when nobody is currently exercising them, and that significant harm can be built out of a vast number of smaller harms that aren’t individually that bad.
by adventured | 2026-03-03 20:56:15+00:00
Nobody was desperate to invade North Korea prior to their acquisition of nukes. It's a horrific war field and combat prospect. Iraq and Afghanistan were each a cakewalk next to going into North Korea (again). North Korea was safe as they were.

The primary threat to Gaddafi over time was internal, nukes would not have protected him. What was he going to do, nuke his own territory? The same was true for Assad.

The primary threat to Iran's regime is internal. Nobody is invading Iran. It's a gigantic country with 93 million people. It can't be done and it's universally understood. Trump won't even speculate about it, even he knows it can't be done. What would nukes do to protect Iran's regime? Are they going to nuke their own people? Are they going to nuke Israel and US bases if the US bombs them?

So let me get this straight: the US bombs Iran, Iran nukes Israel and some US bases, maybe even a regional foe - then Iran gets obliterated.

That's not what would happen in reality at all. Don't take my word for it, ask Pakistan: the US threatened to bomb them [0] - despite their possession of nukes - after 9/11 if they didn't cooperate. Why would the US do that? Because the US knows that MAD doesn't work like the online armchair crowd thinks it does.

[0] https://www.aljazeera.com/news/2006/9/22/us-threatened-to-bo...
by gritzko | 2026-03-03 20:56:33+00:00
Heh. Find how to grant permissions/ acquire lock in git. You can not. That is fundamental to distributed systems.

Downside: harder to think about it all.

Upside: a rocket may hit the datacenter.

From what I remember about Figma, it can be proclaimed CRDT. Google Docs got their sync algorithm before CRDT was even known (yep, I remember those days!).
Show HN: X402drop – Temporary file sharing paid in USDC via the x402 protocol
by easylearnai | 2026-03-03 20:56:44+00:00
I built a temporary file sharing service where payment happens through HTTP 402 status codes and USDC on Base/Arbitrum.

The idea: HTTP 402 ("Payment Required") has existed since 1997 but was never really used. The x402 protocol (https://x402.org) finally gives it a real implementation — server responds 402 with a payment challenge, client signs a gasless USDC transfer (EIP-3009), facilitator settles on-chain, client retries with a payment header. No API keys, no OAuth, no accounts.

x402drop uses this as the payment layer for temporary file storage:

- Connect wallet (SIWE), drag-and-drop files (up to 5 GB each, 10 GB per drop)
- Pick a duration (1 hour to 90 days), see a quote ($0.0003/MB/day, $0.01 minimum)
- Sign one USDC transfer — gasless, facilitator pays gas
- Get a share link — recipients download for free, no wallet needed
- Files auto-delete from R2 within ~15 minutes of expiry via cron

There's also an Agent API — AI agents and scripts can create drops programmatically using the same x402 payment flow. No API key, the 402 payment header is the auth.

Stack: Next.js (App Router), SIWE + RainbowKit, Drizzle ORM + Neon Postgres, Cloudflare R2, @x402/next, Vercel.

Pricing is deterministic: max(fileSizeMB × durationDays × 0.0003, 0.01) per file.

Known limitations:
- Mainnet only (no testnet mode yet)
- USDC only (no ETH or other tokens)
- No email notifications for expiry warnings

The part I find most interesting technically is using HTTP 402 as a real protocol primitive rather than a payment wall gimmick. The facilitator model means the payer never touches gas, and the whole flow is just HTTP request → 402 → signed header → 200.

Live at https://x402drop.com. Docs at https://x402drop.com/docs.

Happy to answer questions about the x402 protocol implementation or the architecture.
by keeda | 2026-03-03 20:57:06+00:00
Here's how I see it: Ideally a manager / reportee relationship is a symbiotic relationship. A manager becomes more successful by making their reportees more successful, and both roles grow together. And repeating this across teams, the whole company grows as well.

There's a lot of nuance but here's a simplistic overview: a manager tries to land a big project for their team, which lets the team stretch their abilities and grow, which over multiple successful deliveries results in promotions / raises for everyone involved AND the cachet to ask for bigger projects (and more headcount!)

The manager's role is the hustling and jockeying in landing the project, ensuring their team is executing and getting any mentorship needed (directly or indirectly) and protecting them from disruptions ("shit umbrella") -- which includes managing everything around the team including stakeholders and dependencies and escalations -- and then making the case for promotions / raises / PIPs based on their performance.

I've never been a manager, but having been involved in all these aspects, I can tell you none of this is easy. All of these can get very contentious, even in the best-run of companies; in the rest, a lot of pathologies spring up (like politics and empire-building) that cause even more nastiness.

So it may seem like they're taking credit for your work, but that's literally part of the arrangement, and it's only unfair if you're not seeing any upside. If you feel that way, this is 100% something you should bring up (very tactfully!) in a 1:1 or (even more tactfully!!!) a skip-level.
by overfeed | 2026-03-03 20:57:07+00:00
Why the restriction to laptops? I don't get why prosumers would marry themselves 24/7 to a single portable device, when their conflicting requirements vary by task and circumstances: portability, high performance, low energy usage, and low noise aren't permanent requirements.

Sure, there's no single device that has Apple's blend of attributes, but who need that in this age of VMs and broadband Internet? My 32-core HEDT workstation outperforms anything Apple branded. I have a Chromebook when I need to be unplugged (<10% or the time)
by johnmaguire | 2026-03-03 20:57:44+00:00
I don't quite follow - are you describing an issue with the way your team has structured PRs? IMO, a PR should contain just enough code to clearly and completely solve "a thing" without solving too much at once. But what this means in practice depends on the team, product, velocity, etc. It sounds like your PRs might be broken up into too small of chunks if you can't understand why the code is being added.
by KinanNasri | 2026-03-03 20:57:50+00:00
I built PRScope because most AI PR review tools felt noisy or shallow.

PRScope reads a pull request diff, sends it to your chosen model (OpenAI, Anthropic, Ollama, or any OpenAI-compatible endpoint), and posts a structured review comment directly on the PR.

Instead of spamming inline comments, it generates:

Risk assessment summary

Findings table (severity, category, file)

Detailed explanations + suggested fixes

Positive feedback where appropriate

Key design decisions:

You bring your own API key

No hosted dashboard

No vendor lock-in

Works with local models via Ollama

GitHub Actions integration

The goal wasn’t to replace human reviewers — just to give teams a strong first-pass review in under a minute.

Would love feedback, especially on:

Signal vs noise ratio

Prompt structure

What real teams would need for adoption
by user5994461 | 2026-03-03 20:58:17+00:00
> I wonder whether the next bottleneck becomes software scheduling rather than silicon

Yep, the schedule has been a problem for a while. There was an amazing article few years ago about how the Linux kernel was accidentally hardcoded to 8 cores, you can probably google and find it.

IMO the most interesting problem right now is the cache, you get a cache miss every time a task is moving core. Problem, with thousands of tasks switching over hundreds of cores every few milliseconds, we're dangerously approaching the point where all the time is spent trashing and reloading the CPU cache.
by JeremyNT | 2026-03-03 20:58:18+00:00
I'm not sure this is really true, since copyright applies to distribution.

If you have a substantial amount of backend code (as with most SaaS projects) you're never actually distributing the code, and copyright is never at play. Computer generated artifacts are already in this boat and are protected by virtue of being trade secrets not by copyright.

This could maybe be true of shipping javascript to the browser, which presumably is not going to qualify as a trande secret, but I don't think that's where most companies derive value.