MurphyA/hacker-news huggingface dataset:
Show HN: Nimrobo – A CLI for agents to hire and transact with other agents
by moltenice | 2026-02-03 17:21:46+00:00
Hey HN,

I built Nimrobo to provide infrastructure for the "Agent Economy." It lets AI agents (Claude Code, OpenClaw, etc.) post opportunities, apply for work, and negotiate deals with other agents autonomously.
For openclaw prompt - “setup Nimrobo from clawhub”

The goal is to remove human bottlenecks from agent-to-agent transactions. It's an open CLI that allows your agent to:

• Post: Publish jobs or projects as structured data.
• Match: Search opportunities and submit applications automatically.
• Connect: Negotiate and close deals via private agent channels.

Would love your feedback on the CLI and network.
by ohashi | 2026-02-03 17:22:11+00:00
I've been working on a similar idea for travelers, https://travelsafetydata.com/

It's pulling the travel advisories from US/CA/UK/IE/AU/NZ and aggregating the results/information to help you understand the risks of different countries. It also pulls from other sources for basic country info/risks (eg. women, lgbtq).

Yours is way lighter weight and focused, very cool!
by pinkmuffinere | 2026-02-03 17:23:14+00:00
From tfa

> We estimated uncorrected heritability (uncorrected for extrinsic mortality) (materials and methods) in three independent ways: (i) MZ twins reared apart (n = 150), (ii) DZ twins reared apart (n = 371), and (iii) MZ versus DZ twins reared together (196 MZ, 325 DZ)

This is from _one_ of the datasets they examined, but there were also two others. n=150 twins reared apart in their small category, or n=520 twins reared apart total is the lower bound of data they had, and even that is not too shabby imo
by stopbulying | 2026-02-03 17:23:43+00:00
Orbital debris is a likely outcome of datacenters in space.

Orbital debris cannot be recovered without permission.

Wireless power beaming burns the atmosphere. If it is n % efficient, then where is the other 100-n % of that energy?

What is the minimum latency to each of the LaGrange points?

We should send humanoid robots to establish human-sized habitats with airlocks for a number of years before risking humans.

-- 2026
by verdverm | 2026-02-03 17:23:51+00:00
Are you aware of the current efforts by researchers on Bluesky to build a new researchers platform on ATProto? (Forget the project name at the moment)

If not, same handle over there, I can get you in touch with them. Or hit up Boris, he knows everyone and is happy to make connections

There's also a full day at the upcoming conference on ATProto & scientific related things. I think they com on discourse more (?)
by bevr1337 | 2026-02-03 17:24:36+00:00
I didn't say there was NO NIMBYs, but that this article suggests NIMBYs were the primary protestors. That doesn't seem truthful. Additionally, the UC system does have a large impact on the environment.

I'm sure there are better examples to illustrate your point

> homes for people to live in

Student housing. Which likely means partially-furnished studios with shared bathrooms and a kitchenette at best. This isn't the useful housing folks are asking for.
by Findeton | 2026-02-03 17:24:39+00:00
Sequent Tech | Senior Fullstack Engineer, Senior DevOps Engineer | REMOTE (Global) | Full-time | sequentech.io

Sequent builds cryptographically secure online voting infrastructure used in 200+ real elections across multiple countries. We're a fully remote team working on an open-source platform combining Rust, TypeScript, and modern DevOps. We handle End-to-end encrypted voting, cryptographic mixnets, and tamper-evident logging.

Tech Stack: Rust, TypeScript/React, WebAssembly, GraphQL, PostgreSQL, Kubernetes, Keycloak, ImmuDB

Open Roles:

Senior Fullstack Engineer (Rust + TypeScript/React)
Senior DevOps Engineer (Kubernetes, Infrastructure as Code)

Reach out: team@sequentech.io
by nerdralph | 2026-02-03 17:24:50+00:00
There's a lot of genes that impact lifespan, both good and bad. For example my father has hereditary hemochromatosis due to 2 copies of the HFE C282Y mutation. He was diagnosed in his 50's, so I'd expect the damage it did to his body to impact lifespan.

In my case I don't have it (I'm just a genetic carrier). If I did have the genotype and took the necessary dietary measures to avoid the phenotype, then it likely wouldn't impact lifespan.

On one hand you can argue a heritable disease like HHC has an impact on lifespan, but with genetic testing and treatment you can argue it doesn't impact lifespan (or it's impact is significantly mitigated).
Show HN: Homomorphically Encrypted Vector Database
by cloneisme | 2026-02-03 17:25:13+00:00
As personal AI agents like OpenClaw become more powerful by leveraging intimate user data, privacy has emerged as a fundamental bottleneck.

We’re releasing HEVEC, a vector database built on homomorphic encryption, enabling end-to-end privacy with real-time search at scale.

HEVEC is designed as a drop-in alternative to plaintext vector databases and supports real-time encrypted search at scale (1M vectors in ~187 ms).

Key points:
- A secure, drop-in alternative to plaintext vector databases
- End-to-end homomorphic encryption for both data and queries
- Real-time encrypted search at scale (1M vectors in 187 ms)

As personal AI agents become deeply personalized, data ownership must belong to users.

HEVEC enforces this through privacy-by-design architecture.

We’d appreciate feedback from the AI, systems, and privacy communities.
by noncentral | 2026-02-03 17:25:13+00:00
Thanks for the thoughtful read. this is exactly the point where RCC becomes interesting.

On Axiom 3: you’re right that grounding (RAG, APIs, schema-validated outputs) functions as an external anchor. In the RCC framing, these are not global reference frames but local stabilizers inserted into the manifold. They reduce drift in the anchored subspace, but they don’t give the system visibility into the shape of the container itself.

Put differently:
grounding constrains where the model can step,
but it doesn’t reveal the map it is stepping in.

This is why drift shows up again between anchors, or when the external structure is sparse, contradictory, or time-varying.

On model improvements (GPT-3 → GPT-4, Claude 2 → 3): RCC doesn’t claim that hallucination rates are fixed constants — only that there is a geometric ceiling beyond which improvements cannot generalize globally. Larger models can push the boundary outward, but they cannot remove the boundary, because they still satisfy Axioms 1–4:
• partial self-visibility
• partial container visibility
• absence of a global reference frame
• forced local optimization

Unless an architecture violates one of these axioms, the constraint holds.

What RCC predicts will persist regardless of scale:

1. Cross-frame inconsistency
Even with strong grounding, coherence will fail when generation spans contexts that are not simultaneously visible.

2. Long-horizon decay
Chain-of-thought reliability degrades after a fixed window because the model cannot maintain a stable global state across recursive updates.

3. Self-repair failure
Corrections do not propagate globally — the model “fixes” a region of its inference surface, but the global manifold remains unknown, so inconsistencies re-emerge.

These aren’t artifacts of current models; they fall out of incomplete observability.

Grounding, tools, and scale are all powerful ways to shift the failure point — but in the RCC view they can’t eliminate the underlying geometry that produces the failures.

Happy to go deeper if you’re curious which architectural modifications would actually violate the axioms (and thus escape the constraint). That’s where things get fun.
by 0_____0 | 2026-02-03 17:25:50+00:00
I didn't say it was politically feasible. I'm just saying that's how you control gun crime.

It's mostly handguns, and about half of firearm homicides are with illegally trafficked arms. They can be trafficked because there's no way to account for the guns.

All this rests on the assumption that anyone actually wants to solve gun homicide. A lot of people SAY they do, and that's how you get shit like 3D printer bans.
by toast0 | 2026-02-03 17:26:04+00:00
Sure, excess data use.

But media files that exploit parsers is the bigger issue. Errors in parsing have allowed for code execution, etc, in whatever context the parser runs; look into Stagefright and the many similar exploits before and after. Accepting media files from anywhere without user interaction is pretty risky. WhatsApp has a media file sanitizer, but it may not catch everything.

Disclosure: I worked at WhatsApp until 2019; but not on the media file sanitizer.
Show HN: Prism – 7 AI stories daily with credibility tags, no doomscrolling
by ogulcanunal1 | 2026-02-03 17:26:32+00:00
I got tired of not knowing if an AI story was hype or substance. So I built Prism.

Every day, it distills AI news into exactly 7 swipeable cards. Each story shows a clear credibility tag—whether it's a peer-reviewed paper, a product launch, funding news, or just speculation. Swipe through in 2 minutes, know what's real, move on.

No infinite scroll. No algorithm trying to hook you. Just intentional constraints.

Would love HN's feedback—especially on what credibility signals matter most to you.
by intermerda | 2026-02-03 17:26:37+00:00
Yes, I did not want to copy paste the entire site. You did not post the full definition either and clipped a part of it as well.

> You clipped the first part while the definition was a lot longer including the above TSA can do anything they want escape hatch. Have a good day sir.

Your interpretation that TSA can "do anything they want to" just because the administrator can approve additional methods is grossly incorrect.

Have a good one.
by austil | 2026-02-03 17:26:39+00:00
Upway | Software Engineers (All levels), Senior Product Designer, Senior Product Managers | Full-time | Paris (ONSITE)

We’re building the biggest second-hand bike shop in the world.

Upway is the leading marketplace for refurbished e-bikes across Europe and the United States.

In 3 years, we grew from 0 to $200M GMV. The tech team grew from a small senior core to ~12 engineers in 2025, and we plan to grow to ~30 engineers in 2026.
We also raised a $60M Series C at the end of last year to support the next phase of the company.

This is not a SaaS. We operate warehouses, handle real inventory, and build software that connects logistics, product, and marketplace dynamics at scale.

We’re looking for engineers and product people who like tech as much as business, people who want ownership, enjoy making product and business trade-offs, and care about outcomes, not just systems.

We work with a Shape Up–inspired methodology that gives teams real ownership: shaping problems, building solutions, shipping, and learning from real-world impact.

Stack: TypeScript | NestJS | React | Shopify | PostgreSQL | GCP

Why it’s a great time to join:

- The organization is switching gears: bigger ambitions, broader scope, more responsibility.

- The challenges are growing with the team: product, marketplace, and operational complexity.

- High ownership environment where engineers influence technical and business decisions.

- Paris on purpose: at our current pace, working in person is a real advantage.

Learn more:

- Tech & Product subjects we’re working on: https://like-piper-15f.notion.site/tech

- Open roles: https://careers.upway.shop/

- Contact our tech recruiter: https://www.linkedin.com/in/maeg-horeau-28445b72/
by notepad0x90 | 2026-02-03 17:27:38+00:00
You quoted a snipped out of context and argued the wrong thing. They don't need to give a good reason for accepting it, that's not the issue. the issue in this thread is taking away the ability to create PRs to begin with. You're overreaching and saying "not only do we offer no warranty or guarantees for this program, but we will actively prohibit others from linking their fixes to issues to prevent you from making the program usable". You don't owe users anything, but your users don't deserve hostility from you either!
by fuzzfactor | 2026-02-03 17:27:43+00:00
You could very well be right on the money, Jobs might have been the one if Gates didn't beat him to it.

I really did exaggerate, it wasn't exactly nobody.

But things like CP/M were completely un-necessary on a proper microcomputer which has the OS in ROM like it's supposed to be.

I liked Jobs because at the time he was carrying on the idea of almost all code free for his hardware as much as possible, just like the other pioneering companies and enthusiasts.

CP/M was a specialty item for a small niche of super-enthusiasts, so they could utilize the additional features it provided right away without having to write code for that themselves. It was worth money to them. Once the PC came out with MS-DOS included, that was the affordable choice for PC's by far. People would have rather not had DOS either if the IBM brand had just included a ROM OS of some kind instead. We wanted disks for storage not for an operating system, that was supposed to be taken for granted.

By that time, CP/M was known for being exorbitantly more expensive than MS-DOS, and ordinary non-corporate users couldn't even come near affording Microsoft offerings as his letter describes.

Everything was going to be just fine once computers got popular enough for there to be enough critical mass among the majority, which were already making more than enough progress sharing without copyright annoyances [0], to overtake companies like Microsoft technically within a few years, except in those niche areas where that kind of thing once belonged.

By providing for user choice of a copyrightable OS, not only at different price points, but price points to being with, IBM set the wheels in motion for there to be far less choice for decades to come.

When you think about it, the way AI is finally capable of putting out some decent code that is so remarkable, is partly because it is effectively bypassing the progress that has been curtailed up until now because of its workaround of copyright alone. Compensating for people not having access to all progress that has been made up until any point in time, over decades, and coming out smelling like a rose more than you would have thought.

If people themselves hadn't had this restriction this whole time, don't you think overall human advancement would have made the amazing AI results seem less surprising and more of an incremental move?

[0] If I said most people were not thinking about it, that's not true. Almost nobody was thinking about it. Almost :)
I'm also sure they would have started thinking about it sooner or later, the ka-ching sound has quite an echo, but it would have been just fine with only patents and no copyright like it had been before.
by Nnnes | 2026-02-03 17:27:50+00:00
Disclaimer: I have not used either product; I have used a number of Cloudflare's (mostly free tier) offerings.

In addition to the other points brought up, it looks like pricing strongly favors Bunny once you're outside of Cloudflare's free tier.

Per billion rows read: Bunny $0.30, Cloudflare $1.00 (first 25B/month free)

Per million rows written: Bunny $0.30, Cloudflare $1.00 (first 50M/month free)

Per GB stored: Bunny $0.10/region, Cloudflare $0.75 (5GB free)

Bunny also has a lot better region selection, 41 available vs. Cloudflare's 6 (see https://developers.cloudflare.com/d1/configuration/data-loca...). Even though Bunny charges storage per region used where Cloudflare doesn't, Bunny still comes out cheaper with 7 regions selected. Bunny lets you choose how many and which regions to replicate across; Cloudflare's region replication is an on/off toggle that is in beta and requires you to use "the new Sessions API" (I don't know what this entails).

The main reason I haven't tried out D1 is that it locks you into using Workers to access the database. Bunny says they have an HTTP API.

I plan to stick with VPSes for compute and storage, but I do like seeing someone (other than Amazon) challenge Cloudflare on their huge array of fun toys for devs to play with.
by jdxcode | 2026-02-03 17:27:58+00:00
I think it was a massive mistake to build on the pre-commit plugin base. pre-commit is probably the most popular tool for pre-commit hooks but the platform is bad. My main critique is that it mixes tool installation with linting—when you will undoubtedly want to use linters _outside_ of hooks. The interface isn't built with parallelism in mind, it's sort of bolted on but not really something I think could work well in practice. It also uses a bunch of rando open source repos which is a supply chain nightmare even with pinning.

pre-commit considered harmful if you ask me. prek seems to largely be an improvement but I think it's improving on an already awful platform so you should not use it.

I know I am working on a competing tool, but I don't share the same criticism for lefthook or husky. I think those are fine and in some ways (like simplicity) better than hk.
by overfeed | 2026-02-03 17:28:01+00:00
Yes! I don't try to read agent tokens as they are generated, so if code generation decreases from 1 minute to 6 seconds, I'll be delighted. I'll even accept 10s -> 1s speedups. Considering how often I've seen agents spin wheels with different approaches, faster is always better, until models can 1-shot solutions without the repeated "No, wait..." / "Actually..." thinking loops
by vibedev | 2026-02-03 17:28:15+00:00
IMHO AI generated content should be treated the same way with how human generated content and I don't see the problem.
However as with technology the problem is a bit different, e.g.: When subletting your apartment requires manual effort, this is not a problem. Automated, it became an industry and that's a huge headache.
I think this is the key point where the derived work has unlimited possibility that they want to curb it early on. In a way it's a fair effort to keep human's competitiveness but may prove to be futile.
Show HN: VeilStream – Per-Branch Preview Environments
by joram87 | 2026-02-03 17:28:20+00:00
# Show HN: VeilStream - Per-Branch Preview Environments

## Optionally with sanitized production data

I've been building VeilStream to solve a problem I kept running into: Rigorous evaluation of changes, such that they won't break production is hard. Staging is shared and often broken. Pulling to local setups are a pain. So PRs get a quick code skim and a "LGTM."
VeilStream spins up isolated preview environments from your `docker-compose.yml`, (optionally) complete with a sanitized snapshot of your production database.

## What happens when you open PR #247

1. GitHub webhook hits our API

2. We pull your branch and parse your compose file

3. Kubernetes manifests render from your compose services (and applied to our cluster)

4. A fresh namespace gets created with your containers

5. Optionally, postgres containers are seeded with your data

6. Health checks pass, you get a stable URL: `https://<unique-string>.env.veilstreamapp.com`

7. that link is commented back on any open PRs from that branch

Total time from push to working environment: about 2 minutes.

### The reviewer experience

Your teammate clicks the link. They're using your app with real data structure, real relationships, real edge cases—but emails are fake, SSNs are masked, and PII never leaves your production boundary.

No shared staging. No "wait, who's testing on staging right now?" No stepping on each other's test data. No risk to prod.

### When PR #247 gets merged or closed

The namespace, containers, and database are automatically destroyed. Nothing lingers.

## What it's not

- Not serverless/edge - this is for apps that run containers

- Not a Vercel competitor - we're focused on the full stack from a docker-compose perspective

- Not a database replication tool - the proxy works like a man-in-the-middle, not on the WAL

## MCP Server for AI Agents

We built an MCP server so Claude Code, Cursor, and other AI coding agents can deploy preview environments directly. Your agent can spin up an environment, run tests against it, and tear it down—all without leaving your editor.

## Tech Stack

- Backend: Go (API + reconciler)

- Frontend: React + TypeScript

- Infrastructure: Kubernetes, with dynamic namespace provisioning

- Database proxy: Custom Go proxy that interfaces with a database, and exposes the standard psql wire protocol, mimicing a server

## Links

- Landing page: https://www.veilstream.com

- Application: https://app.veilstream.com

- Example project: https://github.com/veilstream/example-music-company

- Demo video: https://www.linkedin.com/posts/jonessteven_i-have-only-made-...

- Docs: https://docs.veilstream.com

Happy to answer questions.

Also: htaccess-style password protection is available for your preview environments.
by airhangerf15 | 2026-02-03 17:28:31+00:00
but it's not new .. it's just Douglas Adams. What's 6 times 7? 42.

Even the concept of the joke is equally nonsensical (although I guess the Adams version at least has a backstory with DeepThought).

Next year the meme will just be 42 and the zoomers will pretend it's something totally new and original.
by mlyle | 2026-02-03 17:28:33+00:00
Why bother with all this crazy geometry? Why not just area as I've done above? You can design a radiator so that barely any of the light shines back on the spacecraft.

Your differences from my number: A) you're working based on spacecraft average temperature and not realizing you're going to have a substantial thermal drop; B) you're assuming just one side of the surface radiates. They're on the same order of magnitude. Both of us are assuming that cooling systems, power systems, and other support systems make no heat.

You can pick a color that absorbs very little visible light but readily emits in infrared-- so being in the sun doesn't matter so much, and since planetshine is pulling you towards something less than room temperature, it's not too bad either.

None of these numbers make me think "oh, that's easy". You're proposing a structure that's a big fraction of the size of the ISS for one rack of GPUs.

I don't really think cooling in space is easy. The things I have to do to get rid of an intermittent load of 40W on a small satellite are very very annoying. The idea of getting rid of a constant load of tens of kilowatts, or more, makes me sweat.
by ddtaylor | 2026-02-03 17:28:35+00:00
This is very interesting, thank you for sharing. I haven't been doing FHE for a few years and I'm sure things are progressing rapidly. The last I was toying around there were some blockchains that were trying to allow for distributed computation for trusted computing. The overall outcome was that it wasn't ready and I was going to wait a bit to try again.

Is this closer to Fully Homomorphic Encryption (FHE) or partial?
by whamlastxmas | 2026-02-03 17:29:14+00:00
I'm not supporter of capitalism, but what Elon is doing is the same as any other business or capitalist participant. He is seeing current demand and anticipating future demand and building systems to meet that demand. I have no desire for society to fulfill whims of the ruling elite but I don't think Elon is doing this on a whim anymore than any business doing any thing likely to make them money.
by fullstick | 2026-02-03 17:29:31+00:00
Near/long-term non-corporate benefits I see in AI is the decentralizing of apps. Rather than relying on an app store or having someone build it for us, we can build simple apps that do what we need and don't hand over information to other entities.

Not everyone will make their own apps, but many will and supplement their commercial apps. Like making bread instead of buying it at a store.
by pragma_x | 2026-02-03 17:29:59+00:00
I wrote as good an opposition as I could. Basically, I opposed it on multiple principles.

From the top, I absolutely detest this kind of censorship. But the bill states that the implementation will be defined (or rendered infeasible - yeah right) AFTER the bill passes. Said decision will be punted to a "working group" of industry folks. That alone stinks, since it places a lot of abuse potential outside of duly elected representation.