MurphyA/hacker-news huggingface dataset:
by tsycho | 2026-03-02 18:48:48+00:00
I agree that this would be an awesome feature, and it would also significantly enhance iPads' value for me.

That said, having worked on account/identity systems at another FAANG, I think that the commenters saying that Apple is holding this back purely to sell more iPads are underestimating the complexity of this feature.

This is not a feature that you just bolt on to the top. It will require a significant ground up rewrite of iOS' fundamentals if you want to support account switching without a full shut down of the device (and even with that, there are complications with shared storage).

There are likely tons of singletons across the iOS codebase for the "current account", and switching between users will easily lead to bugs where the new account shares/accesses state from the previous account.....and these "violations" are much harder to detect via static analysis than you might naively imagine.
by foxfoxx | 2026-03-02 18:48:56+00:00
We're early stage, but I believe there's a space between news and actual policy that no one's filling well. If you can show people that their representatives are making their lives better or worse, with real policy behind it, they'll care.

Right now, too many people are consuming misinformation from sources they believe are legitimate, and increasingly from social media where real people are getting their news. We need to connect the policy, the personal impact ("you're losing your insurance because of X"), the news, and what politicians are actually saying, all in one place, to bring real facts to the misinformation and make government more transparent.
by Terretta | 2026-03-02 18:49:05+00:00
> real trade-off … thankful for any feedback

Speaking as a tiny but regulated SMB that's dabbling in skill plugins with Cowork: we strongly appreciate and support this stance. We hope you don't relax your standards, and need you not to. We strongly agree with (1), (2), and (3).

If working outside the sandbox becomes available, Cowork becomes a more interesting exfil vector. A vbox should also be able to be made non-optional — even if MDM allows users to elevate privileges.

We've noticed you're making other interesting infosec tradeoffs too. Your M365 connector aggressively avoids enumeration, which we figured was intentional as a seatbelt for keeping looky-loos in their lane.* Caring about foot-guns goes a long way in giving a sense of you being responsible. Makes it feel less irresponsible to wade in.

In the 'thankful for feedback' spirit, here's a concrete UX gap: we agree approval fatigue matters, and we appreciate your team working to minimize prompts.

But the converse is, when a user rejects a prompt — or it ends up behind a window — there's no clear way to re-trigger. Claude app can silently fail or run forever when it can't spin up the workspace, wasn't allowed to install Python, or was told it can't read M365 data.

Employees who've paid attention to their cyber training (reasonably!) click "No" and then they're stuck without diagnostics or breadcrumbs.

For a CLI example of this done well, see `m365-cli`'s `auth` and `doctor` commands. The tool supports both interactive and script modes through config (backed by a setup wizard):

https://pnp.github.io/cli-microsoft365/cmd/cli/cli-doctor/

Similarly, first party MCPs may run but be invisible to Cowork. Show it its own logs and it says "OK, yes, that works but I still can't see it, maybe just copy and paste your context for now." A doctor tool could send the user to a help page or tell them how to reinstall.

Minimal diagnostics for managed machines — running without local admin but able to be elevated if needed — would go a long way for the SMBs that want to deploy this responsibly.

Maybe a resync perms button or Settings or Help Menu item that calls cowork's own doctor cli when invoked?

---

* When given IDs, the connector can read anything the user can anyway. We're able to do everything we need, just had to ship ID signposts in our skill plugin that taps your connector. Preferred that hack over a third party MCP or CLI, thanks to the responsibility you look to be iteratively improving.
by morgengold | 2026-03-02 18:49:20+00:00
I agree with you. Withdrawing into one’s own little world cannot be the answer. And saying it’s the only realm you can control isn’t really true.

For me personally, doing that would always feel like avoiding responsibility. It might bring a kind of shallow happiness, but not a real sense of meaning or connection.

That only comes from taking responsibility—not just for your own small world, but for the world around you as well.
by alexpotato | 2026-03-02 18:49:40+00:00
The first episode of the Surgeon's Cut [0] on Netflix shows a doctor:

- operating in utero

- while the mother is awake

- in an outpatient/doctor's office setting

- to implant a balloon in the upper respiratory tract of a fetus with a, I believe, cleft palate so that it's lungs can develop normally.

It really is wild what modern medicine can do these days.

0 - https://www.netflix.com/title/81004466
by 1vuio0pswjnm7 | 2026-03-02 18:50:07+00:00
"Tweaking user-hostile OSes into user-friendly ones is impressive, but not sustainable."

Not sure about the first claim but the second is obvious. Yet strangely ignored

The OS literally comes from Google. As such, the term "de-Googled" is quite strange

AFAICT, the most significant issue is "phoning home". Unwanted data transfer to third party. This is embedded in the OS. Google is the third party. Google operates as if it should be trusted as if it was a first party (why)

IMO, a user-friendly (cf. user-hostile) mobile OS would be one that does not phone home. But at times it seems like these projects are OK with the idea of phoning home to third party, as long as it isn't Google

Users will never have a mobile OS that does everything Android does, with the same polish, that isn't attached to a trillion dollar corporation. That "goal" results in projects where the majority of the Google-sourced code is unchanged instead of user-controlled source code

It isn't _that_ difficult to stop Android, i.e., system, pre-installed and user-installed "apps", from successfully phoning home (cf. trying to phone home) over WiFi. For example, this can be done by changing gateway and DNS settings. If the user installs an app that can forward ports nd use the the built-in VPN support, successfully phoning home over cellular data can be stopped, too

But a corporate-sourced OS like Android can change at any time for any reason. It changes often. Users have no control

I see some HN comments are starting to acknowledge the idea that control can be more important than performance. IMO, it can also be more important than "features"

Only if a user can embrace this idea can he begin to truly "break free" from the trillion dollar surveillance advertising company. Otherwise, sacrificing control for "performance", "features", etc., will always leave the user tethered to the company

With the corportate-sourced OS users have no control over these things. The corporation controls them

Until there is a user-controlled, open source mobile OS like other form factors
(HN commenters often claim this is not going to happen), then, IMHO, "mobile" sucks

Generally, we all have to use mobile, as least for some things, e.g., it's replaced residential landlines, paper maps, and so on. But none of this means it is a good choice for for so-called "general purpose computing". It's not a computer the user can control
by danaris | 2026-03-02 18:50:09+00:00
First of all, your timeline is off: A Game of Thrones was published in 1996, and the Game of Thrones series premiered in 2011.

Second of all, even if you were correct, that would only apply to the first book, not the subsequent ones, which were spread out across 1999-2011 (indeed, A Dance with Dragons came out the same year as the TV series premiered).

So perhaps you'd like to pick a different copyright maximalist strawman?
by afavour | 2026-03-02 18:50:09+00:00
An illustrative lesson to anyone who joins a startup with the promise of a ton of stock: the company can make it worthless whenever they feel like it. Always remember that.

As for Brewdog itself, there’s a lesson in VC mindset there as well I think. Everything doesn’t have to grow to be massive. You can stay a sustainable size if you want to. But alas the temptation to keep expanding is always too strong, and often leads to flameouts like this.
Show HN: license checker for npm projects
by chrillemn | 2026-03-02 18:50:31+00:00
Hey everyone,

How do you handle license risk in projects with a lot of dependencies?

Do you check licenses before installing packages, or only later when it becomes a problem?

I built this tool because I wanted a quick overview of what I had actually pulled into one of my projects. It turned out one dependency was AGPL-3.0, which would have required me to open source the entire project if distributed.

That wasn’t my intention, so I replaced it with an alternative. But it made me realize how easy it is to accidentally introduce strong copyleft licenses without noticing.

Do you actively monitor dependency licenses, or is it something you only think about when legal/security gets involved?
by petercooper | 2026-03-02 18:50:33+00:00
It may also depend on where you're from. I'm British, have travelled around the US, and never had problem engaging in chit chat with all sorts of people, big cities or not. But there's a strong disarming undercurrent of "oh wow, you're from England" through the whole experience that I expect most Americans never experience, at least within their own country.
by neuroelectron | 2026-03-02 18:50:39+00:00
Won't be long until Trump declares war on Motorola and takes out the head of Mototollah in a preemptive strike in order to protect competition and ensure market fairness. But most importantly of all, to ensure Palantir and national security can still be provided to our strongest allies. It's not a leadership change operation. Just a 72-hour operation.
by Groxx | 2026-03-02 18:51:05+00:00
I'm personally opposed to RCS (it's basically all Google / no real federation, horrifyingly complex because messages can have action buttons and whatnot, and DOES NOT have E2EE despite many implications for years - the newest spec this past year includes it, but nobody does it yet), but SMS and MMS are so incredibly terrible for basically every purpose that I'm entirely fine with attempting to replace it.

But since RCS has become such a mess, and is so anti-competition (you can't make your own app, or servers), I think the answer is now extremely clear: don't use your telecom's messaging system at all, they are all by far the slowest, least reliable, and least private option. App-based messaging is better in almost all practical cases, and I think it's also a healthier future to head towards.
by jmholla | 2026-03-02 18:51:23+00:00
Far narrower is doing a lot of heavy lifting in your response.

> (c) “Application” means a software application that may be run or directed by a user on a computer, a mobile device, or any other general purpose computing device that can access a covered application store or download an application.

If your device can connect to a covered application store, every application on your computer must follow this.
by win311fwg | 2026-03-02 18:51:32+00:00
It is simpler than that. Go hasn't added "try" because, much like generics for a long time, nobody has figured out how to do it sensibly yet. Every proposal, of which there have been many, have all had gaping holes. Some of the proposals have gotten as far as being implemented in a trying-it-out capacity, but even they fell down to scrutiny once people started trying to use it in the real world.

Once someone figures it out, they will come. The Go team has expressed wanting it.
Show HN: 58% cost by replacing file reads with a dependency graph on AI Coding
by nicola_alessi | 2026-03-02 18:52:03+00:00
I got tired of watching Claude Code read entire files when it needed one function. Built an MCP server that pre-computes a dependency graph with tree-sitter and serves only the relevant code nodes to the agent.

Ran a proper benchmark to see if it actually matters.

Setup: FastAPI codebase (800 Python files), Claude Sonnet 4.6, 7 tasks (bug fixes, features, refactors, code understanding), 3 runs per task per arm, 42 total executions. Both arms run in full isolation with --strict-mcp-config. Results collected via headless claude -p with --output-format stream-json.

Results:

Cost per task: $0.78 → $0.33 (-58%)
Duration: 170s → 132s (-22%)
Output tokens: 504 → 189 (-63%)

Savings by task type:

Code understanding: -57%
New features: -53%
Refactoring: -48%
Bug fixes: -29%

The pattern: baseline Claude makes ~15 Read + 4 Grep + 4 Glob calls per task, accumulating context incrementally. With the graph, it averages 2.3 run_pipeline calls that return pre-ranked context in one shot. Less cache creation, fewer round trips, and the agent writes more concise responses because it already has the right context.

Code understanding benefits the most because that's where the agent spends the most tool calls exploring. Bug fixes benefit the least because the scope is usually narrow enough that a few Read calls get you there anyway.

The graph is built with tree-sitter (functions, classes, types, imports, call references), stored in SQLite, updated incrementally on file save. Also does cross-session memory — observations linked to graph nodes, auto-flagged stale when the code changes.

Single Rust binary, everything local, zero network calls except an optional license check.

https://vexp.dev — free tier, no account needed.

Happy to answer questions about the approach, the benchmark setup, or where it breaks down.
by saidinesh5 | 2026-03-02 18:52:44+00:00
It might be developer fantasy but half of the giants in the mobile market really did take off this way:

* xiaomi with their miui skin/custom ROM - "bringing iOS like polish to Android" back then

* oneplus with their initial devices with cyanogenmod - clean aosp interface without any bloat and lots of features.

In fact, when my brother was buying phones for my mom (neither of them were really that technically inclined), he bought a Motorola mostly because "it doesn't have all those ads like redmi at the same price"
by pfannkuchen | 2026-03-02 18:53:19+00:00
I don’t really see how a near infinite corpus which occasionally contains that pattern could end up with it so highly represented in the output.

I could see this being an argument for why it ends up being bland or having an inconsistent style (for example).

So I suppose that could be a theory, that what happens naturally has a structure that needs to be corrected for, and right now the mechanism that produces the structural correction is overly simplistic and heavily overweights examples of that structure, but that this structure does not actually occur naturally from the model.
by eagerpace | 2026-03-02 18:53:39+00:00
I've been wondering about this failed Apple Intelligence project, but the more I think of it, Apple can afford to sit and wait. In 5 years we're going to have Opus 4.6-level performance on-device, and Apple is the only company that stands to benefit from it. Nobody wants to be sending EVERY request to someone else's cloud server.
by mark_ge | 2026-03-02 18:53:42+00:00
Halfpricesoft | Founding Engineer | Berkeley, CA | ONSITE | $175k - $210k + Equity
Halfpricesoft has quietly dominated the small business payroll and tax compliance space for 20 years. We are a profitable, bootstrapped company with thousands of customers and a massive track record of stability.

We are entering a new era and transitioning our proven legacy solutions into a modern, cloud-native suite. We are looking for a Founding Engineer to serve as our technical partner in this expansion. You will report directly to the Founder, own the technical roadmap, and help build the team.

The Role:

Architect & Build: Lead the transition from legacy systems to a modern cloud architecture.

Infrastructure: Manage and scale our Kubernetes deployment.

Leadership: Set hiring standards and mentor future engineers.

Tech Stack: Python (Django), React, Kubernetes, Cloud-native.

Why join?

Real Impact: You aren't a cog in the machine; you are building the machine.

Stability + Upside: Competitive salary plus a Phantom Stock Plan with a transparent, revenue-based valuation formula (no VC dilution).

Autonomy: High-level ownership over the tech stack and product direction.

Apply here: https://www.halfpricesoft.com/career/founding-engineer/
by dismalaf | 2026-03-02 18:53:42+00:00
https://e.foundation/legal-notice-privacy/

Read this. They still collect much of te data Google does. Why should I trust them over Google? And even if they might be morally better, it's basically impossible for them to have better security than Google.

If I were to want a Google-free phone, I'd want it to be everyone-free. Not replacing Google with some French corporation (even if it's non-profit).
by fc417fc802 | 2026-03-02 18:53:45+00:00
> If you are worried about the slippery slope, then you are really worried that democracy does not work as intended.

Not really. That's a well established failure mode. People's perceptions can gradually shift as they become accustomed to the new way of doing things.

Personally I'd be less concerned about a slippery slope and more concerned about abrupt changes in policy. All infrastructure should be designed with the worst case scenario in mind. It's naive to assume that things will never get worse suddenly or that we will have plenty of warning or even a meaningful opportunity to react.
by sunaookami | 2026-03-02 18:53:46+00:00
Newer Pokémon games have way more quality-of-life such as EXP share and way faster animations so it's not a slog anymore. Recently finished Scarlet and enjoyed it very much. Currently replaying SoulSilver and I couldn't play it without cheats that make the game a bit faster (cutting repetitive animations, making the game run at 60 FPS, etc.) since everything is so slow.

I'm nearing 30 and have played a lot of JRPGs in my life.
by needlesslygrim | 2026-03-02 18:53:47+00:00
While Swift now has the `borrowing` and `consuming` keywords, support for storing references is nonexistent, and the only way to return/store `Span`s, etc, is only possible through using experimental `@lifetime` annotations.

Swift is a nice language, and it's new support for the bare necessity of affine types is a good step forward, but it's not at all comparable with Rust.
by jcmfernandes | 2026-03-02 18:54:05+00:00
I just read the article and I didn't get away with that rationale. Now, this isn't to say that I agree with the author. I don't see why go would *have* to add typed error sets to have a try keyword.

Yes, mimicking Zig's error handling mechanics in go is very much impossible at this point, but I don't see why we can't have a flavor of said mechanics.
Cartly: An iOS Receipt Tracking Demo Built on Mnexium
by Mnexium | 2026-03-02 18:54:16+00:00
Just published a new case study on Cartly, an iOS app that uses Mnexium to power a full receipt-tracking AI workflow. We really wanted to see what it would take to get a demo like this up and running.

In the post, we walk through how Cartly uses:

Memory for user preferences and continuity

Records for structured receipts and receipt_items storage

A single mnx runtime object to control identity, history, recall, and record sync

Request trace packets for auditability and debugging in production

The demo flow covers schema setup, receipt image capture, AI extraction, record persistence, and record-aware chat responses.

Blog: <https://mnexium.com/blogs/introducing-cartly>

Docs: <https://mnexium.com/docs>

iOS code: <https://github.com/mnexium/cartly>
by sarkarsh | 2026-03-02 18:54:36+00:00
Most of this thread is debating MCP as a CLI wrapper, and for that it's clearly worse. More tokens, no piping, another process to manage.

But the real use case for MCP isn't replacing git or jq. It's giving agents persistent state across sessions. When I close the terminal my agent forgets everything. What it was working on, what it decided, what it tried that failed. Next session starts from zero.

An MCP server that holds structured project state -- tasks, decisions, context -- lets the agent pick up where it left off. It queries what happened last session, updates progress, records new decisions. That's fundamentally different from running a CLI command and parsing stdout. You need a server that maintains state and exposes typed operations on it.

The framing should be: CLI for stateless operations (builds, git, file manipulation). MCP for stateful integrations where the agent needs memory that outlives the session.
by cosmic_cheese | 2026-03-02 18:54:36+00:00
I don’t see Android making big inroads until there’s more of a presence from Android manufacturers that fill Apple’s niche in smartphones and tablets.

Samsung desperately wants to be this but misses the part where iPhones don’t come with third party junkware even if they’re entry level models and don’t allow carrier junkware either. Google could be it but they’re too married to midrange hardware and underwhelming physical designs.

All it would take is for a manufacturer to commit to their whole lineup being built with reasonably capable hardware (no ancient or weak SoCs as seen in budget Android devices), to completely jettison third party junkware, and have top end flagships with hardware that actually matches that description, but none thus far have managed this.
by jtbayly | 2026-03-02 18:55:00+00:00
Rant incoming...

My wife and I live near a park. When we go on walks, we see people who have driven to the park, where they drive slowly around the parking lot, frequently stopping and starting, cars running the whole time. Rarely do they get out of their car. They are, I believe, playing Pokemon Go. Yesterday there were over 2 dozen cars driving around. Nobody was walking. They don't talk to anybody. They are like zombies. I don't get it. Yesterday I did see one dad with his kid, and they were out actually walking on the trails. I can understand that. But driving to the park to drive around?! Argh!

end rant. Thanks for listening.
by wetchicken | 2026-03-02 18:55:20+00:00
Location: Orlando, FL
Remote: Yes

Willing to relocate: No

Technologies: JavaScript, TypeScript, React.js, Redux, TanStack, Astro, Git, Node.js, NestJS, Express, MongoDB, Jest, Storybook, styled-components, Tailwind, Vite

Resume: Available on request

Website: https://yagmurtas.com

GitHub: https://github.com/cakebatterandsprinkles

LinkedIn: https://www.linkedin.com/in/yagmur-tas/

Email: yagmurcetin@gmail.com

I am a frontend / full stack developer with ~5 YOE and a background in medicine and neuroscience. Hoping to find opportunities that involve problem solving and strong teamwork.
by sarkarsh | 2026-03-02 18:55:34+00:00
The library choices are the visible part. React, Tailwind, Drizzle -- you see those in the imports and catch them early.

The scarier version is the invisible architectural decisions. When the agent decides to skip input validation because "the frontend handles it," or collapses your middleware chain because it doesn't understand why the rate limiter was there. You find those weeks later when something breaks, and there's no record of why the agent made that call.

The AGENTS.md approach helps for known preferences, but it only covers what you thought to specify upfront. The agent makes dozens of micro-decisions per session that nobody anticipated. Which error handling strategy, whether to denormalize, how aggressively to cache. Those are just as opinionated as the library picks -- they're just harder to audit from a diff.

What's missing is the agent documenting its own decisions as it works. Not what code it wrote, but what it decided, what it considered and rejected, and what it simplified. That way when you find the rate limiter is gone you can trace back to the decision instead of reverse-engineering intent from git blame.