MurphyA/hacker-news huggingface dataset:
by vintagedave | 2026-03-04 15:56:50+00:00
I can't help feeling this is the size/weight that the Air should be targeting.

I have an Air (M2) and I use it where I once owned a Pro. No fans sold it to me -- that's a quality feature, tired of them getting dirty over time. But I have the 15" model and essentially use it as a pro laptop.

This? This is an Air.

But the Air has become the Pro, the Pro has become the one you get for ports and super power and I don't know if many people even need it, and now 'Air' has lost its meaning (light, entry-level, portable) so they need a new name. So they name it, literally, neo: New.

Steve Jobs would weep. What happens in five years when it's not new any more?
by Frannky | 2026-03-04 15:57:01+00:00
Damn I would love to buy it. In the past I tried different mods trying to get rid of google, the problem was always the same, lot of little annoyances making it very painful for daily usage. A de Googled phone without annoyances and security would be very cool.

Another interesting thing is that I haven't had any reason to buy a new phone in a very long time so we are probably in a time where the hardware is commodotized enough for motorola to be able to ship exactly what I need.

Never thought I would have think of routing for Motorola in 2026 but you never know!
by runjake | 2026-03-04 15:57:37+00:00
This doesn't compete with Chromebooks in schools at all.

- Chromebooks in EDU cost approximately $290 (+- $10) per unit.

- The Neo costs $499 per unit for schools.

- For the cost of 10 Neos, I can buy 17 Chromebooks. Yes, this is a numbers game. The goal is every student has a device.

- Schools using Chromebooks to log in. If you want reliable Google logins on macOS, you have an additional big spend up front, along with per-seat licensing costs.

- This doesn't even factor in MDM and app cost comparisons.
by mrweasel | 2026-03-04 15:57:52+00:00
There's also the operational cost of running whatever is churned out. I wouldn't exactly blame that on AIs, but a large contingency of developers optimize for popular tech-stacks and not ease of operations. I don't think that will change just because they start using AI. In my experience the AI won't tell you that you're massively overbuilding something or that if we did this in C and used Postgresql we'd be able to run this on an old Pentium III with 4GB of RAM. If you want Kubernetes and ElasticSearch, you'll get exactly that.
by mikepurvis | 2026-03-04 15:58:18+00:00
I like it just on principle for being something the Canadian banks collaborate on without involving Visa or Mastercard, unlike in the US where debit also goes through their networks.

From the consumer side, I don't use it all that often for purchases just because I'm aware of the interchange fee tax on cash purchases so I try to maximize the value of my credit cards: 3x Avion points for grocery spend on RBC ION+, 2 Aeroplan pts/$ for dining on Amex.

As far as a requirement to be online, given the nature of debit that doesn't surprise me; the whole point relative to credit is that no one has to trust you to pay a bill later. If offline transactions were possible then it would just be a credit card by another name.

The refund thing surprises me, but I expect that has to do with preventing some fraud scenario, maybe like an inside job where an employee issues remote refunds to a confederate? Overall it seems like the design of the system is fairly conservative and that's reflected in the much lower fees; the whole point is to not have to have whole armies of people answering the phones to help grandma get back $50.
by handedness | 2026-03-04 15:58:55+00:00
You still need to address this part: "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. Its great at making sure a browser exploit cannot steal your banking credentials you have open in a different virtual machine but cannot overcome the limitations of the platforms it builds off of."

That's the crux of it you blow past every single time it comes up, and then disparage others as having not stuck around long enough to educate you (as if that's their responsibility).
by mrkeen | 2026-03-04 15:59:51+00:00
It's the definition of simple that's the problem. For any definition of simplicity you might have, someone has an equal and opposite definition.

Take these two alternatives:

class UserService {
PostgresDatabase db;
}

class UserService {
IDatabase db;
}

There are some coworkers who will veto the first example for being too complex, because it brings Postgres (and its state and connections and exceptions and mappings) into the scope of what otherwise could have been a service concerning Users.

There are some coworkers who will veto the second example for being too complex, because Postgres is all you use for now, and if you really need to use a second database, you can change the code then (YAGNI). Also the Interface gives you a pointless indirection that breaks IntelliSense so you can't just 'click-through' to follow the code flow.
by kace91 | 2026-03-04 15:59:52+00:00
I haven’t been able to see actual results that match those tests in the Motorolas sadly. Maybe it’s more accurate in technical terms but I haven’t found good results in practice.

>Pixels have fantastic camera hardware and software which is fully functional on GrapheneOS which isn't something we need to lose on a Motorola flagship.

This is very interesting to me! Does graphene OS manage to keep google’s processing? How does that work?
by Aachen | 2026-03-04 15:59:58+00:00
> Why such a restriction?

Sorry, that wasn't clear: I meant any phone that I can purchase as of 2025. I was looking for several months and made a decision about 2 months ago. A second-hand Pixel was a big compromise but I don't see another option

> https://puri.sm/posts/the-danger-of-focusing-on-specs/

Do you also have thoughts to add or am I supposed to respond to an entire blog's worth of material here?

I'm not focusing on specs because I don't know any better. Not sure if there's another possible reading or if you insinuated that. The software I use (e.g.: OsmAnd) is not noticeably faster on more modern systems and was downright sluggish on my previous phone. I could buy my current chipset again, it's doable for now, but neither great nor future-proof. The chip's inefficiency also means it's completely empty after 2.5 hours of use (while I'm out mapping, taking notes, recording positions and sometimes pictures, listening to music... I ask a lot of the battery), so newer chips can do the same work with less energy

> Except there is also a microphone.

Respond to OP. Hardware toggles wasn't my argument but theirs. Great that your librem has this but the thread is about GrapheneOS
by chasd00 | 2026-03-04 15:59:58+00:00
look at the stats of what the UAE has defended against, what is the purpose of those attacks? They make no sense to me.

Iran attacks on the UAE
186 ballistic missiles
812 drones

this article even states that the UAE has been attacked more than Israel itself which, again, blows my mind. The UAE is, wisely IMO, choosing to stay out of it but i mean how much can they take?

https://www.axios.com/2026/03/03/uae-iran-missiles-strike-is...
by D-Machine | 2026-03-04 16:00:00+00:00
> How does that have anything to do with peer review?

I already addressed this. People know peer review can be bad, but some think "good journals" still do good peer review. This is not so clear.

> In what world does the arxiv system moderate this discrepancy?

Open systems allow the scientific community to figure out ways to properly assess research quality and value more cheaply, and without passing through (often arbitrary and random) small numbers of gatekeepers that don't even do a reliable or good job gatekeeping in the first place.
by jlongo78 | 2026-03-04 16:00:07+00:00
running claude with --dangerously-skip-permissions in k8s is actually a smart move for isolation. the container boundary does alot of the permission work for you. one thing i'd watch though: ephemeral pods mean lost session context. the real workflow pain isnt the permissions, its picking up where you left off after a pod restart. stateless infra and stateful agent conversations dont mix well without something managing session persistence externally.
by jlongo78 | 2026-03-04 16:00:15+00:00
honestly respect the restraint here. most apps are engineered to hijack your dopamine loop indefinitely.

counter-intuitive take: this "one thing then leave" model is actually how i use my agent sessions. one focused task, close it, context switch deliberately. treating attention like a finite resource instead of something to be monetized changes how you build tools entirely.

the apps that respect your time end up being the ones you actually trust.
by mehulkalia | 2026-03-04 16:00:27+00:00
Mehul here. One thing that surprised me while building this was how creative the defender agent became. It runs Claude Haiku on a timer and can choose from prebuilt disruptions like fake “Session Expired” popups, or generate custom JavaScript injections based on what the attacker is doing, like inserting fake “Search disabled” buttons. Digging through the traces and seeing the before/after screenshots of what the defender agent came up with was pretty funny, and kind of mind-blowing.
by gtowey | 2026-03-04 16:00:31+00:00
> Not to rain on our hopes, but AI can give us some options and we can pick the best.

But that's kind of my point. A bunch of decisions like that tend to end up with a "random walk" effect. It's a bunch of tactical choices which don't add up to something strategic. It could be, but it takes the human in the loop to hold onto that overall strategy.
by nixon_why69 | 2026-03-04 16:00:47+00:00
It sounds like you were one of the actual Principal Engineers, then. In my experience, there are some who had done some of that in the past but now had to maintain their position by generating "cross-team impact" which was mostly just a PITA to actual practitioners.

One case in particular, there was a re-org and the new org lacked principals but we had a common vision. We needed a new vision that was led by the new principal, for obvious reasons. Whole thing was set back by a couple years while this was figured out.
by rs545837 | 2026-03-04 16:00:52+00:00
Interesting idea. Tree-sitter's trade-off (speed + incrementality over completeness) makes sense for editors but you're right that for merge/diff a more thorough parser could be worth the cost since it's a cold path, not real-time. We only parse three file versions at merge time so spending an extra 50ms on a better parse would be fine. Worth exploring, thanks for the pointer.
by elxr | 2026-03-04 16:01:19+00:00
I can think of at least 1 major improvement to so many of the apps I use day to day.

Desktop software is nowhere near good enough to consider random usecases "already done". Not that glaze looks particularly special, but there's so many improvements the desktop experience begs for.

An easy to use cross-platform GUI builder for one. Even something as basic as a calendar app doesn't have a clear obvious winner today.
by vladich | 2026-03-04 16:01:22+00:00
The emphasis on compilation time there is because the JIT provider that comes with Postgres (LLVM-based) is broken in that particular area. But you're right, JITed code can be cached, if some conditions are met (it's position independent, for one). Not all JIT providers do that, but many do. Caching is on the table, but if your JIT-compilation takes microseconds, caching could be rather a burden in many cases. Still for some cases useful.
by skydhash | 2026-03-04 16:01:42+00:00
I’m not self-hosting much. My server is more of a file server with compute at the top. I have Jellyfin for Infuse on my AppleTV, gonic for my music library (with minidlna to play on my AVR), and Calibre for ebook. Everything else is backups or some random experiment (the main point is that it’s an always on linux computer with wired connection). I have a VPS for stuff I want online.
by jcranmer | 2026-03-04 16:01:58+00:00
Yes, break, continue, and return are all "just" gotos in disguise. But they restrict the power of the goto enough to not cause the problems that goto causes while providing a good deal of semantic power to users. Namely, all of these are essentially variations on early return (you can also throw in the logical && and || operators here, albeit they are slightly different in having two exit points rather than one--they're a fusion of if and break, essentially). And it sort of turns that there are a lot of cases where "return when any of these conditions, tested in a particular order, holds" turns out to be the most natural way to express an algorithm, and these goto-like constructs are the most natural way to write them.

(FWIW, this is essentially the argument that Knuth makes in his defense of goto paper)
by foobarchu | 2026-03-04 16:02:10+00:00
This viewpoint isn't a slippery slope, it's a runaway train.

"You moved into a neighborhood with lead pipes? That's on you, should have done more research"
"Your vitamins contained undisclosed allergens? You're an adult, and it didn't say it DIDN'T contain those"
"Passwords stolen because your provider stored them in plaintext? They never claimed to store them securely, so it's really on you"
by JoshTriplett | 2026-03-04 16:02:25+00:00
If you have a device you don't trust, don't allow it on your network, or have an isolated network for such devices. Meanwhile, devices are right to not allow MITMing their traffic and to treat that as a security hole, even if a very tiny fraction of their users might want to MITM it to try to do adblocking on a device they don't trust or fully control, rather than to exploit the device and turn it into a botnet.

Along similar lines, a security hole you can use for jailbreaking is also a security hole that could potentially be exploited by malware. As cute as things like "visit this webpage and it'll jailbreak your iPhone" were, it's good that that doesn't work anymore, because that is also a malware vector.

I'd like to see more devices being sold that give the user control, like the newly announced GrapheneOS phones for instance. I look forward to seeing how those are received.
by crazygringo | 2026-03-04 16:02:34+00:00
> But the base model has no Touch ID which seems terrible to me.

But that's the point. If you're super price conscious and a student, it's only $499! Typing a password is not a big deal compared to $100 for some people.

But if you want convenience, it's $599. Which helps subsidize the $499 price.

Product differentiation like this is what enables the cheaper price to begin with.
by allreduce | 2026-03-04 16:02:36+00:00
Are there more security disadvantages besides the obvious when giving one app like Termux root access?
The obvious being that you trust Termux and all binaries running in it with total access to your system.

I am mainly looking to access my filesystem.
Currently a lot of things I want to do (backing up app data, scripting, mounting network drives) are hobbled by the bad wrappers around the same.

I know this might be out of scope, but is there any plan to re-enable direct filesystem access in a more secure way?
Even via ADB it would be useful.
It just seems like madness to me that a lot of basics tasks are impossible or incredibly convoluted, because everything has to go through weird wrapper interfaces and Java/Kotlin code someone has to write (instead of just using the filesystem and OS which is right there).

Thanks for the great work by the way.
by busymom0 | 2026-03-04 16:03:02+00:00
EDIT: With education discount, in Canada, it's good price: $679 for base, $849 for Touch ID + 512 SSD.

--

$799 in Canada for the base model & $999 for the one with touchID & 512 GB ssd.

Looks like both models only come with 8gb ram.
by Frannky | 2026-03-04 16:03:05+00:00
I love it. I still use a 2020 M1 since I had not had a reason to change it. So smooth and fast and silent and thin. I don't really have a reason to buy a new one but if it broke or I lost it I would for sure buy this new one. Pros are too bulky for me. The only thing I miss I the ability to run local big models at high token rate.

Taking into account Tesla chips deliver way more intelligence on smaller hardware maybe we will get there, a glm5 model running locally at 100 tokens/sec would be really dope!
by legierski | 2026-03-04 16:03:06+00:00
This is perfect for folks looking to buy a brand new laptop.

For the rest of us, happy with gently used 2nd hand devices, the original M1 MacBook Air and the M1 Pro/Max MacBook Pro are a *much* better deal for the same price, pretty much across the board, especially the Pro: bigger, brighter, 120Hz screen, beefy specs, ports.

That citrus colour, tho...
Show HN: SprintPulse – AI-powered retrospectives that drive action
by SkyLinx | 2026-03-04 16:03:28+00:00
Hi HN,

I am the founder of SprintPulse. Like many of you, I used to dread retrospective meetings. They often turned into a repetitive cycle where we wrote down the same issues every sprint but never actually fixed them. "Better communication" was on our action item list for months.

I built SprintPulse to fix that loop. It is a tool designed not just to collect feedback, but to make sure it leads to real change.

When I looked at the tools available, I found they fell into two camps.

On one side, you have generic whiteboards like Miro or FigJam. They are great for free-form drawing, but they are too open-ended for structured retros. They don't help you track history or remind you of what you promised to fix last month.

On the other side, you have specialised retro tools. I found that while these solve the problem, they often feel outdated. The UX can be clunky, they are often loaded with complex settings you don't need, or they are just too expensive for smaller teams to justify.

I wanted to build something in the middle. A tool that has the structure and insights you need (for which AI isn't just a "me too" buzzword), but with a modern interface that doesn't require a tutorial.

- AI Analysis: Instead of just counting votes, the AI reads the feedback to spot trends and suggest action items. If the team is getting burnt out or if specific topics keep appearing without resolution, the system flags it.
- Accountability: This was the main thing I wanted. SprintPulse tracks your action items from previous sprints. If you ignore a problem for three weeks, the tool brings it up. It forces you to either fix it or consciously drop it.
- Clean UX: I focused on keeping it fast and lightweight, and enjoyable to use. You just log in and start the meeting.

I believe smaller teams shouldn't have to pay just to run a basic retro.

- Free Plan: We have a solid free plan for teams up to 10 users. It includes 3 retros and the core features. No credit card required to sign up.
- Paid Plans: If you have a larger team or want deep historical analytics and insights, integrations with Linear, Jira and Slack, we have paid tiers.

For the HN community, I am offering 40% off any paid plan (recurring, forever) with the code HACKERNEWS.

I would love for you to take a look and tell me what you think.

Link: https://sprintpulse.io/

Thanks!
by simonw | 2026-03-04 16:03:35+00:00
> Agree with everything else you said except this.

Yeah, I'm not sure I agree with what I said there myself!

> Incorrect, but not visibly incorrect, code will sit in place for years.

If you let incorrect code sit in place for years I think that suggests a gap in your wider process somewhere.

I'm still trying to figure out what closing those gaps looks like.

The StrongDM pattern is interesting - having an ongoing swarm of testing agents which hammer away at a staging cluster trying different things and noting stuff that breaks. Effectively an agent-driven QA team.

I'm not going to add that to the guide until I've heard it working for other teams and experienced it myself though!
by NoLinkToMe | 2026-03-04 16:04:00+00:00
No it isn't. It's 1.08kg vs 1.23kg, or 13% heavier.

And indeed it's 13 inch but the dimensions are quite similar, there is a 0.8% difference in width (with the 11 inch being wider surprisingly, due to the bezels) and a 7% difference in height (11 inch being shorter). At its thickest point the 11 inch is. 33% thicker. In terms of volume the 13 inch isn't any bigger.

Just look up the specs.
by palmotea | 2026-03-04 16:04:11+00:00
>> What if your CEO went politically rogue and started openly supporting Trump? Would you quit? I doubt that.

> Yes. I would. Trump is a uniquely dangerous president with uniquely unrestrained power.

Even if it meant you could lose your house? Even if you were 6 months pregnant (meaning it could put your health insurance in jeopardy at a pretty critical time, as well as your parental leave)? Even if you quitting would accomplish absolutely nothing?

Any maybe you're such a zealot that you'd rather end up homeless than working for a company managed by a CEO that supports Trump. But don't punish other people for not being willing to do the same. Other people have other priorities, and other situations going on in their life, and that's fine.
Show HN: Modeled healthcare de-identification as longitudinal RL control problem
by vkatganti | 2026-03-04 16:04:12+00:00
Most PHI de-identification pipelines are stateless: detect identifiers, remove them, done. The problem is that re-identification risk doesn't work that way in practice.

A name fragment that's harmless in record #1 becomes identifying when it co-occurs with a location in record #47 and a timestamp in record #203. Static masking can't see that.

This project treats de-identification as a stateful control problem instead. The system maintains a per-subject exposure graph across time and modalities, computes rolling re-identification risk, and dynamically escalates masking strength only when cumulative exposure justifies it.

The core idea: privacy protection as a feedback loop, not a preprocessing step.

A few things I found interesting building this:
- Cross-modal linkage (text + ASR + image proxy + waveform headers) creates non-obvious re-ID surfaces
- Pseudonym versioning on risk escalation lets you contain linkage continuity without global reprocessing
- The privacy–utility tradeoff is actually controllable if you model exposure state explicitly

All experiments run on synthetic streaming data (no real PHI). Reproducible from source. Colab demo included.

Repo: https://github.com/azithteja91/phi-exposure-guard

Happy to discuss the architecture, the RL policy design, or the tradeoffs vs. existing de-ID approaches.
by wanderr | 2026-03-04 16:05:01+00:00
This is the norm at large tech companies and, IMO, a huge problem and major detriment to productivity within organizations as the cost of that added complexity is paid by everyone.

BUT, at least very occasionally I have seen people get promoted for simplicity, I've even successfully made the case myself. With a problem that was itself so complex that it was causing fires on a regular basis, and staff & principal engineers didn't want to touch it with a ten foot pole. When a senior eng spent a couple of weeks thinking about the problem and eventually figured out a way to reframe it and simplify the solution, melting away months of work, making the promo case was actually quite easy.

The problem is, the opportunities to burn down complexity like that don't present themselves nearly as often as the opportunities to overcomplicate a thing, which are pretty much unbounded.
by cillian64 | 2026-03-04 16:05:15+00:00
Two advantages for me: It's nice that you don't break the connector if you trip over the cable or put the laptop down on a soft surface, and it's nice being able to charge while still using both USB-C ports (although I guess 3x USB-C would also solve that).

I don't really see any downside to a proprietary connector if you also have the option to charge over USB-C as well.