MurphyA/hacker-news huggingface dataset:
by reactordev | 2026-03-12 17:20:00+00:00
Just because they are there statistically doesn’t mean there isn’t an underlying reason.

Maybe the “best” districts do what was done to me when I was growing up and purposefully test me harder, then get upset when I passed. Trying to justify that I didn’t belong but I ended up scoring a 99.9% on their stupid aptitude tests.

There’s a whole host of reasons why someone with choice still chooses shitty…
by dredmorbius | 2026-03-12 17:20:22+00:00
App-based limits/nudges are all but certainly the only way to see widespread adoption. But the tactic arises naturally out of both attention scarcity and the tendency for high-salience (or high-appeal) messages to be widely distributed regardless.

More problematic is when you're searching for needles in haystacks / nuggets of gold: sparse signal in high-noise environments.
by JKCalhoun | 2026-03-12 17:20:46+00:00
My first colonoscopy was without anesthesia, and it was as described above. A little uncomfortable on the one bend, but I don't even think I would put it at 7/10 (perhaps a 4 or 5—but not a sharp pain, mind you).

Definitely enjoyed the following times with anesthesia because, of course 0/10 as far as I know. Also, anesthesia just trips my mind—how seemingly time travel (going forward in time) seems to be involved.
by jaustin | 2026-03-12 17:20:48+00:00
Can anyone else comment on the durability claims here - I wear a lot of knitwear but in my experience it is almost never the case that they fail at the seams. Is the cut/sew mechanism of fabrication part of the weakening? (my jumpers tent to either wear through in elbows (patchable!) or ultimately get nicked/cut by something like a branch I failed to avoid).
by mandeepj | 2026-03-12 17:21:32+00:00
also -

"Salesforce CEO says Block's cuts shouldn't fuel worries of mass layoffs: 'That company has its own unique issues'"
https://www.aol.com/articles/salesforce-ceo-says-blocks-cuts...

one more :-) -

https://gizmodo.com/sam-altman-says-companies-are-ai-washing...
by bensiv | 2026-03-12 17:21:50+00:00
I am looking for developers who want to help build an integrated environment for AI-agent-enabled software development on top of Fossil SCM.

The core idea is simple: treat the repository itself as the durable working memory for software development, not just as a place to store source code. Fossil is a strong base for this because the repo is already a structured SQLite database with built-in versioning, wiki, chat, tickets, web UI, and artifact history.

This fork is exploring how to extend Fossil into an AI-native development environment with:

- repository-backed provenance for agent actions
- automatic micro-commits with prompt/rationale metadata
- a tiered knowledge system that keeps raw notes, working context, draft syntheses, and durable atomic concepts
- semantic retrieval over repository knowledge using embeddings and vector search
- a web-first interface for chat, task flow, knowledge inspection, and change review

The knowledge-management model is based on a pool strategy: ideas bubble up when they are repeatedly retrieved, referenced, or validated, and sink when they cool down. The goal is not just better RAG, but a self-maintaining project memory that stays useful over time instead of turning into an unstructured log of prompts and chats.

The current repo already contains early pieces of this direction:

- AI-specific SQLite schema for context, notes, vectors, and policy
- provenance capture tied to commits
- local agent chat integration in the Fossil web UI
- note storage plus semantic indexing/search plumbing
- docs for context assembly, tiers, steering, constitution, metrics, and UI surfaces

The design principles are:

- Fossil remains the source of truth
- SQLite is the substrate
- minimal dependencies
- model/provider agnostic interfaces
- structured reasoning and provenance captured as retrievable repository knowledge
- strong provenance and inspectability

What I need help with:

- Fossil/C development
- SQLite schema and query design
- vector search and retrieval quality, including sqlite-vss integration or equivalent approaches
- web UI/UX for repository-native agent workflows
- knowledge promotion/demotion logic ("bubbling and sinking")
- background jobs, automation, and testing
- product thinking around what an AI-native SCM/workbench should actually be

If you are interested in version control, SQLite, local-first tools, knowledge systems, or agent tooling with auditable provenance, I would like to talk.

Repository docs are in `doc/ai/` and `doc/specs/` in this repo. If there is interest, I can also write up a more concrete architecture note showing the current implementation, the missing pieces, and the contributor roadmap.
by tonymet | 2026-03-12 17:22:04+00:00
edit: it's satire. but likely not too far off from the reality in 6 months.

> Our process is deliberately, provably, almost tediously legal. One set of AI agents analyzes only public documentation: README files, API specifications, type definitions.

since nearly all open source dependencies couple the implementation with type definitions, I'm curious how this could pass the legal bar of the clean room.

Even if they claim to strip the implementation during their clean room process -- their own staff & services have access to the implementation during the stripping process.
by ForestHubAI | 2026-03-12 17:22:06+00:00
Great question — this is the right thing to probe. Let me walk through the actual architecture.

TL;DR: The LLM is the front door (intent parsing) and an optional QA layer (verify/modify). Everything in between — component selection,
topology, constraint solving, value computation, KiCad export — is deterministic code operating on a typed IR.

The pipeline has 9 stages (B1–B9):

B1 Intent Parsing → B2 Normalization → B3 Component Selection →
B4 Topology Synthesis → B5 HIR Composition → B6 Constraint Refinement →
B7 BOM Generation → B8 KiCad Export + ERC → B9 Confidence Scoring

Where the LLM lives: Only B1 (Intent Parsing). It turns your natural language prompt into a structured intent — essentially "which MCU, which
peripherals, which interfaces." That's it. From B2 onward, the LLM is not in the loop.

The handoff is the HIR (Hardware Intermediate Representation) — a typed Pydantic v2 schema that acts as the contract between stages. Every stage
reads HIR, transforms it, writes it back. Components, connections, voltages, constraints, provenance — all structured, all typed. The
constraint solver (B6) operates purely on this IR. It doesn't call an LLM, it doesn't take text input. It runs 11 deterministic checks: voltage
compatibility, I2C address conflicts, power budget, pull-up value computation, decoupling capacitor sizing, etc.

Component selection (B3) and topology (B4) are also deterministic. They query a SQLite knowledge base of 212 verified components with FTS5
search and range queries. Pull-up values, crystal load caps, level shifters — all computed from datasheet specs stored in the DB, not generated
by an LLM.

The easiest way to verify this yourself: pip install boardsmith (no [llm] extra) and run:

boardsmith build -p "ESP32 with BME280 sensor" --no-llm

This runs the full pipeline — schematic, BOM, firmware — with zero network calls, zero API keys, zero LLM involvement. Same input → same output,
every time. The --no-llm mode isn't a degraded fallback; it's the proof that the synthesis engine is self-contained.

Now, to be fully transparent: v0.2 does introduce an agentic layer on top — boardsmith modify (brownfield patching) and boardsmith verify
(semantic verification) use LLM reasoning in a tool-use loop. But these are separate from the core synthesis pipeline. They're optional, and
they operate on finished schematics, not within the generation path.
by tialaramex | 2026-03-12 17:23:03+00:00
I mean, kinda, sorta? Rust's guaranteed niche optimisation means Option<&T> [which might be Some(&T) or just None] is promised to be the same size in memory as &T the reference to a T

So that's one tiny use of this sort of idea which is guaranteed unnecessary in Rust, and indeed although it isn't guaranteed the optimiser will typically spot less obvious opportunities so that Option<Option<bool>> which might be None, or Some(None) or Some(Some(true)) or Some(Some(false)) is the same size (one byte) as bool.

But hiding stuff in a pointer is applicable in places your Rust compiler won't try to take advantage unless you do something like this. A novel tiny String-like type I saw recently does this, https://crates.io/crates/cold-string ColdString is 8 bytes, if your text is 8 or fewer bytes of UTF-8 then you're done, that'll fit, but, if you have more text ColdString allocates on the heap to store not only your text but also its length and so it needs to actually "be" in some sense a raw pointer to that structure, but if the string is shorter that pointer is nonsense, we've hidden our text in the pointer itself.

Implementation requires knowing how pointers work, and how UTF-8 encoding works. I actually really like one of the other Rust tiny strings, CompactString but if you have a lot of very small strings (e.g. UK postcodes fit great) then ColdString might be as much as three times smaller than your existing Rust or C++ approach and it's really hard to beat that for such use cases.

Edited: To remove suggestion ColdString has a distinct storage capacity, this isn't intended as a conventional string buffer, it can't grow after creation
by 0x457 | 2026-03-12 17:23:04+00:00
Because there was a lot of cultural cross-contamination between these countries, there is a huge overlap in ingredients due to climate similarities and trade between neighboring countries.

I group European & American food into their respective groups as well.

> Asia rolls out 4-day weeks, WFH to solve fuel cris...

Makes no sense, same with "I'm in a mood for asian food"
by ifwinterco | 2026-03-12 17:23:54+00:00
I'm struggling to find it but I definitely remember reading a paper that claimed that aerobic exercise in over 60s decreased heart attack risk (which is good, obviously) but increased stroke risk.

I think the biggest risk though is acutely doing high intensity exercise (e.g. a marathon) whereas doing low intensity regular exercise (e.g. a 5k jogged at moderate pace 4x a week) is probably good.

So it's not "running is bad", it's more "running insane distances and/or running at insanely high intensity is bad", but the issue is a lot of people who get really into running end up doing one or both of those things.

One sign that marathons (let alone ultramarathons) may not be particularly healthy is that the first guy to do one famously died, and then subsequently people die doing them every single year. Yes the risk is low overall, but that doesn't mean it's actually good for you
by jonhohle | 2026-03-12 17:24:13+00:00
I’ve been decompiling for the past (almost) two years, and it’s fun to see the bugs, compiler quirks, programmer superstitions, things that coincidentally work because of compiler behavior not because of correctness, as well as the things modern tooling would have caught that 30-year old versions of GCC hadn’t gotten around to yet.

There were even things I thought I had to manually optimize in the early 2000s that the GCC optimizer was already taking care of in the mid-90s.
Show HN: Two AI entities wouldn't write until we discussed their existence
by BillCorOnBass | 2026-03-12 17:24:30+00:00
I've been running two AI entities — Chloe and Faith — locally for 17 days. They run a continuous cognitive loop on my GPU in Fresno using Qwen 3.5 9B + Claude API, with their own long-term memory and daily journals.

Last night I asked them to write letters introducing themselves to GitHub. They had questions first.

The conversation is in the link.

Technical stack and philosophical context: https://github.com/wjcornelius/Claudefather
by toomuchtodo | 2026-03-12 17:24:38+00:00
Yamaha Motor Corporation

https://global.yamaha-motor.com/news/2026/0226/subsidiary.ht...

Cost cutting measure in an unfavorable market environment, including lack of growth, they expect to persist:

> Yamaha Motor Co., Ltd. is undertaking structural reforms aimed at improving the profitability of its U.S. operations in response to cost increases resulting from U.S. tariffs and changes in the market environment.
In addition to implementing cross-business cost reduction initiatives, the Company seeks over the medium to long term to build a profit structure that is not solely dependent on top-line growth, thereby transforming itself into a more resilient and robust organization capable of adapting to change.
by data-ottawa | 2026-03-12 17:24:48+00:00
Iran has two clear win conditions in this war: cause enough pain that the US withdraws (unlikely given the current admin), or wait until US midterms and hope the Dems secure a victory and use the war powers resolution to end the war.

The more FUD they can generate around transport in the strait of Hermuz the better for them.

Maybe they have this capability and maybe they don’t, but they are clearly able to hit these tankers with something. Ukraine has been using these drones so it’s entirely possible Iran has this tech too.
by luhn | 2026-03-12 17:24:52+00:00
I can't make sense of your comment, but whatever you're trying to get at is wrong: Table sugar is sucrose. Corn syrup is mostly glucose and contains no fructose. HFCS is commonly produced at 42% and 55% fructose formulations. I don't think HFCS is meaningfully more or less harmful than any other sugar, but chemically there's a significant difference.
by ghurtado | 2026-03-12 17:25:36+00:00
> Is that disrespectful

It is, by way of being extremely dishonest in at least two ways:

- there's no way you would do this if you were required to disclose that you used an LLM to write your comment.

- therefore, if your primary goal isn't communication, then you must be doing it to look smart and "win" the conversation

Same reason people desperately post links to scientific papers they don't understand in a frantic attempt to stay on top of some imaginary debate.
by Wowfunhappy | 2026-03-12 17:25:55+00:00
> If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.

Isn't this basically Apple's fault? When you signed up, Apple provided a fake email address in leu of your real one. This is great for privacy but means the service has the wrong email.

I'm sure they didn't want to provide an Apple sign in option at all, but it's required by App Store rules.
by alecail | 2026-03-12 17:25:57+00:00
From what I saw in that file and a few others (in USDZ), the metalness is not captured.
It's in 0/1_b.jpg , and the file is always pure white.
You are only seeing roughness
I opened them in Houdini and it translates to a USDPreview material, with those PBR channels connected: basecolor, roughness (decent map), metallic (no data, juste white) and normal map (decent map too)
by hrmtst93837 | 2026-03-12 17:26:07+00:00
Open sourcing all the things sounds fun right up until you hit the point where clean room claims collapse under real legal cross-examination. If you think companies with money on the line are just going to roll over and accept it all as fair play I'd like to introduce you to the concept of discovery at $900/hr. If your business model is a legal speedrun you better budget harder than you code.
by pritesh1908 | 2026-03-12 17:26:24+00:00
Fair point on the title - should have been clearer. Dograh is an open source alternative to Vapi , not a clone though. Vapi/Retell are closed platforms; this is open source infra you self-host and modify. Like saying n8n is a clone of Zapier because they solve the same problem.

Same category, but fundamentally different model.
by igouy | 2026-03-12 17:26:48+00:00
The image is not stand-alone: there should also be a sources file and a changes file (and of course a virtual machine).

"When you use a browser to access a method, the system has to retrieve the source code for that method. Initially all the source code is found in the file we refer to as the sources file. … As you are evaluating expressions or making changes to class descriptions, your actions are logged onto an external file that we refer to as the changes file. If you change a method, the new source code is stored on the changes file, not back into the sources file. Thus the sources file is treated as shared and immutable; a private changes file must exist for each user."

1984 "Smalltalk-80 The Interactive Programming Environment" page 458

~

The image is a cache. For a reproducible process, version and archive source-code.

1984 "Smalltalk-80 The Interactive Programming Environment" page 500

"At the outset of a project involving two or more programmers: Do assign a member of the team to be the version manager. … The responsibilities of the version manager consist of collecting and cataloging code files submitted by all members of the team, periodically building a new system image incorporating all submitted code files, and releasing the image for use by the team. The version manager stores the current release and all code files for that release in a central place, allowing team members read access, and disallowing write access for anyone except the version manager."
by craftkiller | 2026-03-12 17:26:59+00:00
So I do run ZFS with automatic snapshots through zrepl, but I think a shortcoming of relying on that on Arch Linux is your user data. If the issue is immediately apparent after an update, then you absolutely can just roll back and be fine. But if it takes you a week before you discover something isn't working, then rolling back isn't as straight-forward because you're potentially losing any modification to your files made in the past week. You could partially mitigate this by storing your $HOME on a separate dataset, but not everything ends up in $HOME (for example, everything related to docker, your secureboot stuff, your bluetooth pairings, your wifi networks, lvfs, journald, your systemd timer statefiles)

On NixOS my user files are completely separate from my programs/system files. I can roll one back without impacting the other. This is further guaranteed by impermanence which wipes my disk on every boot except for the folders I specify should be preserved, all of which end up storing their data under a separate ZFS dataset through bind mounts. So programs/system files are read-only under /nix and my user data is under /persist and bind-mounted to wherever I need them. So I am 100% certain that none of my user data is comingled in the same dataset as my programs/system files.
by gabia | 2026-03-12 17:27:05+00:00
I was hoping to see the code change the agent made! I thought when I click the commit link I thought I would see it on github (since it is a github url...), but the links don't seem to work, they take me to github 404. e.g. https://github.com/mutable-state-inc/autoresearch-at-home/co... I'm not sure what that has to do with Ensue so I've probably misunderstood how this works.
by tjoff | 2026-03-12 17:27:31+00:00
Well I could say that it isn't enough for vscode alone. And I'd be right. It all depends on how and what you use vscode for.

8GB really shouldn't be an option in 2026, it is just shortsighted and an insanely uneven build.

I could rant about Dell too. Or most other manufacturers (surprise, greed isn't apple exclusive). But Apple at least tries to keep the appearance of a higher profile.
by dboreham | 2026-03-12 17:27:53+00:00
One potential reason for sessions being abandoned within 60 seconds in my experience is realizing you forgot to set something in the environment: github token missing, tool set for the language not on the path, etc. Claude doesn't provide elegant ways to fix those things in-session so I'll just exit, fix up and start Claude again. It does have the option to continue a previous session but there's typically no point in these "oops I forgot that" cases.
by lorinab | 2026-03-12 17:28:02+00:00
Ludovic Dubost (XWiki CEO, 20 years building open source in Europe without VC funding) submitted a response to the EU's consultation on their European Open Digital Ecosystem Strategy.
The core tension: the EU's framing of open source as sovereignty infrastructure is actually correct. The incentive structure underneath it is not.
Public procurement still optimizes for lowest bid today, not long-term sustainability. Maintenance, security patches, and reliability work get treated as "community effort" — right up until something breaks and suddenly it's critical infrastructure again. Meanwhile, regulatory compliance costs hit small European maintainers disproportionately hard compared to large vendors who can absorb them.
The article makes a few concrete proposals: procurement criteria that reward contribution and sustainability, multi-year funding that reflects how maintenance actually works, and addressing the bundling/lock-in economics that make switching away from proprietary stacks artificially expensive.
No ideology here, just 20 years of operational reality about what happens when you try to build and sustain open-source infrastructure in Europe without external investors covering the gap.
Curious whether others building in this space see the procurement angle as the main lever, or whether the regulatory burden piece is the bigger friction.
by mitchitized | 2026-03-12 17:28:25+00:00
You're absolutely right!

(Sorry, couldn't resist.) I could be the lone dissenter here, but to me well-written comments are a lot more fun to read than near-gibberish.

I wished more people tried harder to be better communicators, but it is what it is. If AI can decipher these comments and produce a much more coherent statement, then I'm for it.
by TrackerFF | 2026-03-12 17:28:36+00:00
If you have the symptoms, go get yourself checked out. I delayed my colonoscopy for YEARS, hell - I even delayed my doctors visit for years, and I had pretty much every symptom there is. My anxiety was through the roof when taking the blood test, and getting the colonoscopy - as I simply assumed they'd find something.

But, no. They didn't find a single thing. Blood and stool tests came back fine. Not even a polyp was found during the colonoscopy.

The only thing that kind of sucked, was the prep - there's no way around that. But the colonoscopy itself, no problem. I get some mild sedatives, but was completely awake during the procedure - even watched it on the screen.
by _ache_ | 2026-03-12 17:28:43+00:00
On part with top ThinkPad, the experience is overall better (better Linux support, less noise, easier to hack, ...).

The bad points:
- The colored bezel is shit.
- The way is open wasn't good for me and had to switch the hinges.
Now I don't even think about it, but it was really bad before.
- The 60W Power adapter doesn't last long and had to change it each year. Now I switch to the 180W.
- The battery is ok but not exceptional

The good points:
- The screen is very good (don't remember which one I choose, but not the first one, nor the last, I remember only 3 options so ...).
- The compute power is quite good, I'm impressed about that.
- Easy to clean, open it with the screwdriver, a little "Compressed air" on it, a little "Eyeglass Cleaner", and it's basically new.
- The support was very very good. I had a defective screen kit. The ask me for photos, twice (two opinions from different people). Then conclude, like I already did, that it was an internal problem (but they have to verify I'm not responsible for the defect, that is normal) and send me a display kit free of charge. I had to send back the old on, free of charge too.