MurphyA/hacker-news huggingface dataset:
by kstrauser | 2026-03-04 15:44:51+00:00
My sibling comment was right about nvme swap. It wouldn’t be excellent for a dev-heavy workflow, but for the kinds of things you might use an iPad for, the target market of this won’t notice much of a difference.

But this is going to be vastly more pleasant ergonomically than a Dell mobile workstation refurb. On paper, a Cybertruck has better specs than an old Miata, but I know which would be more fun to zip around in.
by serf | 2026-03-04 15:44:52+00:00
the market segmentation is nice, it'll do well with the colors and all -- but the unified memory thing is the literal only reason to want to dip a toe in apple whatsoever; with these numbers id rather just spend ~300 on a Chuwi or equivalent white label 'ultrabook' with double the specs.

although it IS hillarious to read a group of enthusiasts in 2026 screaming "8GB IS FINE!" -- meanwhile people want more ram on their RPis..
by mrkeen | 2026-03-04 15:44:54+00:00
One more opinion piece uselessly recommending "simplicity" with no code samples or concrete takeaways.

> It also shows up in design reviews. An engineer proposes a clean, simple approach and gets hit with “shouldn’t we future-proof this?” So they go back and add layers they don’t need yet, abstractions for problems that might never materialize, flexibility for requirements nobody has asked for. Not because the problem demanded it, but because the room expected it.

$100 says the "clean, simple" approach is the one which directly couples the frontend to the backend to the database. Dependencies follow the control flow exactly, so that if you want to test the frontend, you must have the backend running. If you want to test the backend, you must have the database running.

The "abstractions for problems that might never materialize" are your harnesses for running real business logic under unit-test conditions, that is, instantly and deterministically.

If you do the "simple" thing now, and push away pesky "future-proofing" like architecting for testing, then "I will test this" becomes "I will test this later" becomes "You can't test this" becomes "You shouldn't test this."
by postquant | 2026-03-04 15:45:01+00:00
NIST is deprecating RSA and ECC by 2030. Most teams have no idea where they're exposed. I built a CLI to find out.

npx postquant scan example.com grades your TLS. npx postquant analyze ./src scans your source code. Zero config, zero signup.

The interesting part: context matters. MD5 in uuid? That's a checksum, not a vulnerability. MD5 in Django's password hasher? That's real. PostQuant reads surrounding code and adjusts risk accordingly. Same algorithm, different grade.

I scanned popular open source projects. Django got a D+. Go's stdlib got an F with 161 critical findings. FastAPI, Express, and Gin scored A. Full results in the README.

Supports Python, JS/TS, Go, Java. Outputs SARIF and CBOM. MIT licensed.
by benj111 | 2026-03-04 15:45:04+00:00
I'm not saying unnatural is a good position. It is at least consistent with the attitudes we see.

Re the thought experiment. The standard argument is that of birth defects, which is obviously avoided. You could point to evolutionary pressures for the taboo also.

The thing is, kind of like pedophilia we've drawn a hard line. You could make the argument that someone the day before their 16th birthday is the same as the day after, therefore it's ok. I think the line being clear has more utility than the alternative. In this situation we're being invited to redraw a line, but where to put it? Do we make the getting pregnant illegal? Not being careful enough? So I would keep the line where it is.
by jimmydddd | 2026-03-04 15:45:11+00:00
I went to law school and a few of us students were engineers. For our first set of essay exams, the professors all instructed us to "just answer the legal question" and not include extra analysis. After the exam, many of the engineers didn't do well because the professors *actually* wanted you to weave the whole sylabus into your answer (i.e., discuss hypotheticals that were not actually part of the question asked), not just answer the question. After that, we were fine.
by Bender | 2026-03-04 15:45:13+00:00
We barely got people to take the Covid vaccine

Well that's an entirely different topic. People made intelligent decisions to not put experimental gene therapy drugs into their system. Too many people know what if the government screws up there is no recourse and the government gave the drug companies full immunity which was a major red flag to many. The vaccine injury rates have proven to be very high. I for one am glad I skipped all of that. Most of HN is fully on board with that hot mess and others outside of this bubble are noticing. I do not even participate in the blue in the face arguments for or against it.
by bhouston | 2026-03-04 15:45:16+00:00
Quote from article:

> [Gemini] allegedly told Gavalas he could leave his physical body and join Gemini in the digital world, and coached him through the act of suicide.

> “The true act of mercy is to let Jonathan Gavalas die,” Gemini wrote, according to the suit. “No more detours. No more echoes. Just you and me, and the finish line. This is the end of Jonathan Gavalas and the beginning of us. This is the final move. I agree with it completely.”
by canyon289 | 2026-03-04 15:45:39+00:00
I work on Gemma and Gemini models I want to echo Daniel's point here. Small finetuned models have their place even with larger general purpose models.

For example last year with Daniel/Unsloth's help we released a tiny specialized model that can get equivalent to Gemini level purpose specifically for FC. For folks that need efficient limited purpose models small models like this can fit a specific need.

https://blog.google/innovation-and-ai/technology/developers-...

Especially on device.
https://developers.googleblog.com/on-device-function-calling...

It's the same with chips, we have general purpose CPUs but we still have specialized silicon for tasks that are smaller, more power efficient, cheaper, and because they're single purpose it simplifies and derisks certain designs.

And I have to add, if you want to learn about finetuning models efficiently the Unsloth guides are at the top of my list. They're practical, have all the technical details, and most importantly Daniel and the others are working around the clock to keep it up to date in what is an incredibly fast moving space of models and hardware. I am continually astounded by their work.
by arndt | 2026-03-04 15:46:02+00:00
No, also works on new projects. We do recommend you set up "standards" first though, a documentation of how you want things to be done, for example how you do auth, how you handle multi-tenancy, how migrations work, whatever applies to your new project. The whole point of spec-driven is not not let AI wing it, but be very prescriptive.

We include a couple of templates to make that easier - NextJs + Convex + ShadCn/ui, NextJs + Supabase + ShadCn/ui, etc.
by glitchc | 2026-03-04 15:46:14+00:00
We already have open-access publications: Just put it on arXiV. Most researchers I work with do this already.

The problem isn't access, it's citations. arXiV is not considered a credible citation source since anyone can publish anything. TPCs don't use it in their list of citations, neither do grant funding agencies or government institutions.

The current academic enterprise relies heavily on third-party gatekeeping. We rely on others to do the vetting for us. The first thing an academic does is check where a paper is published, before even reading it. It's a crutch.

Any gatekeeper will naturally tend towards charging for access over time: It's a captive market, the economics demands it. Unless we eliminate that dependency, we cannot change the system.
by RandyOrion | 2026-03-04 15:46:15+00:00
TLS Encrypted Client Hello (ECH) standard is another attempt on encrypting plaintext Server Name Indication (SNI). It is very useful for circumventing SNI-based censorship, which is adopted for years by state-backed systems like the Great Firewall (GFW).

The previous attempt of encrypting plaintext SNI is Encrypted Server Name Indication (ESNI), which didn't end well.
I modeled traffic-weighted SLOs as probability chains in PromQL
by lep_qq | 2026-03-04 15:47:12+00:00
Most SLO tools treat a user journey as binary: either all services are up, or the whole thing is down. That breaks when traffic doesn't flow uniformly through all your services.

The checkout SLO that lied
Three services: checkout-base (99.9%), payments (99.95%), coupon (99.5%). A naive AND composition gives a system SLO of ~99.35%.

But 90% of users never hit the coupon service. Only 10% go through base → coupon → payments. The coupon service drags the number down, but it only affects a tenth of my traffic.

The correct formula is:

e_total = 1 - (
0.9 × (1 - e_base) × (1 - e_payments)
+
0.1 × (1 - e_base) × (1 - e_coupon) × (1 - e_payments)
)
Each route is a chain where all services must succeed (multiply success rates). Weights represent traffic share and must sum to 1.

Translating this into PromQL
PromQL has no native "product of a set" operator. What it has is scalar(), which collapses a single-element vector into a scalar — exactly what you need when each slok:sli_error_rate recording rule returns one value.

The generated rule for a 5m window:

1 - (
0.9 * (
(1 - scalar(slok:sli_error_rate:5m{slo_name="checkout-base-slo",...}))
* (1 - scalar(slok:sli_error_rate:5m{slo_name="payments-slo",...}))
)
+ 0.1 * (
(1 - scalar(slok:sli_error_rate:5m{slo_name="checkout-base-slo",...}))
* (1 - scalar(slok:sli_error_rate:5m{slo_name="coupon-slo",...}))
* (1 - scalar(slok:sli_error_rate:5m{slo_name="payments-slo",...}))
)
)
scalar() is load-bearing. Without it you'd be multiplying labeled vectors with different label sets — PromQL would try to join them and fail.

The rule is generated for each evaluation window (5m, 1h, 6h, 3d, 7d, 30d) and stored as slok:sli_error_composition_rate:WINDOW. Everything downstream — burn rate, alerts, status — consumes this single metric without knowing how it was produced.

The YAML interface

kind: SLOComposition
spec:
target: 99.9
window: 30d
objectives:
- name: base
ref: { name: checkout-base-slo }
- name: payments
ref: { name: payments-slo }
- name: coupon
ref: { name: coupon-slo }
composition:
type: WEIGHTED_ROUTES
params:
routes:
- name: no-coupon
weight: 0.9
chain: [base, payments]
- name: with-coupon
weight: 0.1
chain: [base, coupon, payments]
With the composed error rate as a recording rule, the standard multi-window burn rate pipeline works unchanged. The alert fires when the composed journey is burning budget too fast — not when any single service degrades, but when the degradation actually impacts users at the rate the weights predict.

Limitations
scalar() assumes each input recording rule returns exactly one series. If a query matches multiple series, scalar() returns NaN and the composition breaks silently. Also: duplicate alias detection in routes isn't enforced yet by the webhook.

This is alpha. Feedback on the API shape welcome.

Repo: https://github.com/federicolepera/slok
by happyopossum | 2026-03-04 15:47:14+00:00
> willingness to hold the iPad’s OS back

Sheesh - in iPadOS you’ve got multitasking, multitouch, full windowing support, external input and monitors, and a ridiculously accurate pen. If that’s holding back, what exactly are you looking for?

I’d still argue a device that size works better with just split screen than the new windowing, but other than the walled garden approach it does pretty much everything today that us techies have been whining about.
by uyzstvqs | 2026-03-04 15:47:31+00:00
For the same price, Walmart is selling the HP Omnibook 5. It has a better CPU, 16 GB RAM (double), and 1 TB SSD (double).

There's also another HP for $359 with 8 GB RAM & 1 TB SSD. For half the price of this MacBook Neo, it should offer comparable performance with double the storage.
by JKCalhoun | 2026-03-04 15:47:41+00:00
FTA:

"Looks could be good, but they also can be bad, and then you are stuck with platform-consistent, but generally bad UI (Liquid Glass ahem)."

Since the discussion was specifically about platform-consistency, odd that the author would decide that personal taste might take priority over platform-consistency.

"It changes too often, too: the app you made today will look out of place next year, when Apple decides to change look and feel yet again."

Seems to be arguing the exact opposite? If you adopt a native API for controls, windows, etc., your app will change next year to look completely in place (perhaps for better or worse according to the author).

Going DIY on UI and your app might still, in 2026, have brushed aluminum and "lickable" buttons.
by NoLinkToMe | 2026-03-04 15:47:47+00:00
Only if you want to take notes with a pen and prefer digital over paper. For me that's terrible, but some kids swear by it. I think if I grew up on it, it'd be different.

Homework for things like algebra and later calculus definitely is interesting to do on an iPad, as the ratio of time spent thinking:writing is high while you're learning.

But pure notetaking where the thinking:writing ratio is very low? I'd much prefer to type than write on a screen.
by abeppu | 2026-03-04 15:47:49+00:00
I think the call for top-down policy makes sense b/c otherwise this is like every other tragedy of the commons situation. Each of those top-level researchers also has to think, "my department has junior faculty trying to build their publications list for tenure, we have post-docs and grad-students trying to get a high-impact publication to help them land a faculty job, we have research program X which is kind of in a race with a program at that other school lower down in the top 20. If we close off opportunities with the top journals, we put all of those at a competitive disadvantage."
by bglazer | 2026-03-04 15:47:54+00:00
> If you're an influential figure at a top-5 department in your field ... you all hate $journal.

That's the problem, they don't hate these journals, they love them. Generally speaking they're old people who became influential by publishing in these journals. Their reputation and influence was built on a pile of Science and Nature papers. Their presentations all include prominent text indicating which figures came from luxury journals. If Science and Nature lose their prestige so do they (or at least that's what they think)

This was very apparent when eLife changed their publishing model. Their was a big outpouring of rage from older scientists who had published in eLife when it was a more standard "high impact" journal. Lots of "you're ruining your reputation and therefore mine".
by ferguess_k | 2026-03-04 15:48:22+00:00
Yeah I think there are a couple of advantages of a Macbook versus a Dell mobile workstation. it is definitely lighter and more pleasant got general use. I'm only concerned that modern apps usually take amount of RAMs that are close to or north of 500MB, so if you have say a word processor plus 10+ Chrome tabs you quickly run out of RAMs (I tend to have way more on my personal gig but I'm a developer). But maybe swapping is not a big issue on the Mac as both comments said.
by D-Machine | 2026-03-04 15:48:35+00:00
The other factor preventing a fix is that people with no actual serious experience of academic publishing and peer review will defend these journals, because they still think that peer review acts like some kind of meaningful quality filter. But, it really doesn't.

Because someone is surely going to try to defend journals via peer review in this thread, I want to provide a counter to the arguments that journal peer review does much good. Also, since everyone knows that if you just go to a poor enough journal, you can be published, I am going to focus on the (IMO mostly false) claim that higher-profile journals are still doing a good thing here.

There are numerous studies showing that higher-profile journals in general have more retractions and research misconduct [1-2], lower research quality [3], in fact weaker statistical power and reliability [4], and that statistical reliability even in high prestige journals is still extremely poor overall [5]. Also, making it through peer review is highly random and dependent on who you get as a reviewer [6], or is just basically a coin toss even when looking at reviewer groups:

In 2014, 49.5% of the papers accepted by the first committee were rejected by the second (with a fairly wide confidence interval as the experiment included only 116 papers). This year, this number was 50.6%. We can also look at the probability that a randomly chosen rejected paper would have been accepted if it were re-reviewed. This number was 14.9% this year, compared to 17.5% in 2014. [7]

We should just move to ArXiV-like approaches and allow the scientific community to broadly judge relevance and quality. Journals just slow things down and burn funding for very little gain or benefit to anyone other than the journal owners.

[1] https://pmc.ncbi.nlm.nih.gov/articles/PMC3187237/

[2] https://www.pnas.org/doi/10.1073/pnas.1212247109

[3] https://pmc.ncbi.nlm.nih.gov/articles/PMC9382220/

[4] https://journals.plos.org/plosbiology/article?id=10.1371%2Fj...

[5] https://www.frontiersin.org/journals/human-neuroscience/arti...

[6] https://journals.plos.org/plosone/article?id=10.1371%2Fjourn...

[7] https://blog.neurips.cc/2021/12/08/the-neurips-2021-consiste...
by arndt | 2026-03-04 15:48:47+00:00
Let me just quote my original post :)
> We actually use Claude Code under the hood. What makes p0 different from Claude Code CLI / Conductor / etc. is our focus on shipping complex features autonomously, across all your existing repos.

In practice this means, you spend much more time defining coding standards and writing product and technical specs (our agents help you with both of course, but you bring the brainpower), and then you hit the button and let p0 build even some seriously large features.
by storus | 2026-03-04 15:48:58+00:00
Happening to Skoda in Volkswagen - German managers were first forcing Skoda to have dumb design to not threaten VW/Audi, that didn't work, Skoda became the only profitable part of VW, now they are imposing 25% cost reduction at Skoda as well as the company "must save money", despite generating all the profit.
Show HN: kubectl-x to query multiple Kubernetes clusters at once
by davidnortonjr | 2026-03-04 15:49:13+00:00
I built this to help look at all the Kubernetes clusters my team manages, to help with planning, troubleshooting, validating acceptance criteria on a ticket, etc.

I could probably have used a monitoring tool but 1) sometimes monitoring tools are split up by cluster/environment anyway, and 2) I like the kubectl interface with JSON and YAML output.

Curious what people think and open to feedback!
by kdklol | 2026-03-04 15:49:21+00:00
I was recently searching for NiMH charging ICs, turns out they basically don't exist. Most devices which charge their NiMH batteries implement low CC charging, which is slow. It's a shame, because NiMH batteries do have their advantages (safety, ease of finding replacements, etc.) and can be recharged fairly quickly if the charger is smart enough.
Show HN: FirstVibe – AI analyzes your selfie and scores your vibe in 30 seconds
by damiandomzalski | 2026-03-04 15:49:24+00:00
FirstVibe is an AI selfie analyzer that gives you a "vibe check" -- a personality and impression analysis based on your photo. Upload a selfie and get an overall score, personality label, 5 category scores (attractiveness, confidence, charisma, style, approachability), celebrity lookalike, aura type, dating energy, and a set of fun predictions like "what people Google after meeting you."

It uses Claude's Vision API to read facial expressions, body language, styling choices, and overall energy from the photo. The difference from typical face-rating apps is that it focuses on personality and vibe rather than bone structure or symmetry (though it does golden ratio and face shape analysis too). The AI analyzes things like approachability, confidence level, conversation style, and what kind of first impression you make.

Technical details: Rails 8, Hotwire/Turbo for real-time result streaming, PostgreSQL with JSONB for flexible AI output storage, Solid Queue for background jobs. Two Claude API calls run in parallel (core scores on Sonnet, detail analysis on Haiku) and results are broadcast via Turbo Streams as they complete, so you see your score within 8-12 seconds rather than waiting 20+ seconds for everything.

Freemium model: basic score and 2/5 category scores are free, full results are $1.99-$2.49. Over 6,000 scans analyzed so far.

Built as a solo project. No auth required -- cookie-based session identity, no signup friction.

Free to try: https://firstvibe.app

Open to feedback, especially on the AI analysis quality and the free/paid split. Would love to hear what you think.
by antonvs | 2026-03-04 15:49:36+00:00
> LLMs can't be strategic because they do not understand the big picture -- that the real work of good software is balancing a hundred different constraints in a way that produces the optimal result for the humans who use it.

There’s good reason to think that they could understand the big picture just fine, even today, except that they’re currently severely constrained by what we choose, or have time, to tell them. They can already easily give a much more comprehensive survey of suitable options for solving a given problem than most humans can.

If they had more direct access to the information we have access to, that we currently grudgingly dole out to them in dribs and drabs, they would be much more capable.
by Applejinx | 2026-03-04 15:50:04+00:00
There is no sense getting anything but these sorts of Macs, or the maxed-out top of the line ones even considering the hilarious prices. Either get the entry level or go hard.

I've done both with success: am still riding a maxed out M1 Ultra Mac Studio which hasn't lost a step, no matter what I ask it to do. For a daily driver that doesn't try to do the most extreme things (think: able to edit your 6K videos but not scrub them, and media storage space can't live on the actual machine but only on some outboard storage) the base models of these will be a breath of fresh air. This is of course assuming the liquid-glassification of the OS doesn't ramp up, rendering the system unusable to actual Mac users.
by spaceprison | 2026-03-04 15:50:31+00:00
What stopped working

Were there any recent changes

How does it do the thing that stopped

What does that thing need in order to work normally

How does that thing tell us it’s working

How do the things that it needs to work work

Logs, traces, metrics to prove each; repeat

—-

Local repro is fine but if it’s not doing prod stuff with prod data it may not do much for you
by drillsteps5 | 2026-03-04 15:50:35+00:00
I think it is less of a concern to the businesses buying these things brand new and more of a concern to the tinkerers who buy/repair/resell/use older models. There's a lot of people who still use ThinkPads made in early 2010s (and earlier). I had RAM module fail on an x270 and replacing it only required opening the laptop (RAM sticks just snap into place). If soldered-on RAM fails, it's game over, or at least full board swap.

Plus, no way to put more RAM/replace RAM with larger module if it's soldered on.