MurphyA/hacker-news huggingface dataset:
by tharadorn | 2026-02-03 21:13:12+00:00
We know that the FBI’s investigation into the archive is CSAM-related (the case number, 305A, is the FBI’s mandate to investigate child exploitation while ‘A’ is the priority of the case). Why the administrator is lashing out at others for his failure to moderate content is beyond me.

For those that believe otherwise, the onion version of the archive is entirely unmoderated. Organisations such as the NCMEC have reached out to the admin to remove pages from being accessed (take a look at the porno site imagefap on the archive) And if you simply use onion, voila, all the pages appear before you.
by litoE | 2026-02-03 21:13:13+00:00
You don't have to multiply the powers of ten in your head. In your examples, the slider of the slide rule must be moved to the left of the body of the rule. This means the number of digits left of the decimal point in the answer is the sum of the number of digits left of the decimal point in the two multiplicands.

If the slider had been to the right of the body, the number of digits left of the decimal point in the answer is the sum of the number of digits left of the decimal point in the two multiplicands MINUS 1.
.
by aerodog | 2026-02-03 21:13:39+00:00
These guys are idiots. The news sources (Iran International etc) that claimed the 30,000 figure have since backtracked on their claim. Mossad and CIA were using Starlink to incite terrorism in their country so the Iranians shut the internet down, discovered the Starlinks (these idiots didn't bother to research how), and apprehended the terrorists who were operating them.

Now that the government has published the list of those dead, all those thousands of excess "killed" could come out and claim their deceased are not on the list. But such a thing hasn't happened. Let's wait and see.
by jauws | 2026-02-03 21:13:39+00:00
Realistically, I don't think anyone will be spending hours here instead of reading real fiction anytime soon (I personally wouldn't). There's just so much nuanced complexity when it comes to creative writing as a domain (long-form outputs, creativity, etc.) that coming up with better annotation methods has massive applications in other research, like in scientific discovery. "AI Wattpad" just happens to be a convenient form factor for crowdsourcing from an HCI perspective. I hope you give it a chance.
by Lerc | 2026-02-03 21:13:56+00:00
I really don't like the narrative of 'X is killing Y', or 'Z is dead' Everything being treated as an existential threat.

I'm also not particularly fond of the other extreme of toxic positivity where any problem is just a challenge and everybody is excited to take them on.

Once seems to understate the level of agency people have and the other seems to overstate.

The world is changing. Adapting does seem to be the rational approach.

I don't think Open Source is being killed but it does need to manage the current situation in a way that provides the best outcome.

I have been thinking that there may be merit in AI branches or forks. Open source projects direct any AI produced PRs to the AI branch. Maintainers of that branch curate the changes to send upstream. The maintainers of the original branch need not take an active involvement in the AI branch. If the AI branch is inadequately maintained or curated, then upstream simply receives no patches. In a sense it creates an opportunity for people who want to contribute. It produces a new area where people can compartmentalise their involvement without disrupting the wider project. This would lower the barrier of entry to productively supporting an open source project.

I doubt the benefit of resume-padding will persist long in an AI world. By the very nature of their act, they are showing what they are claiming to do is unremarkable.
by bigyabai | 2026-02-03 21:14:05+00:00
OOM is a pretty terrible benchmark too, though. You can build a DDR4 machine that "technically" loads 256gb models for maybe $1000 used, but then you've got to account for the compute aspect and that's constrained by a number of different variables. A super-sparse model might run great on that DDR4 machine, whereas a 32b model would cause it to chug.

There's just not a good way to visualize the compute needed, with all the nuance that exists. I think that trying to create these abstractions are what leads to people impulse buying resource-constrained hardware and getting frustrated. The autoscalers have a huge advantage in this field that homelabbers will never be able to match.
by bigwheels | 2026-02-03 21:14:12+00:00
I use Leash [1] [2] for sandboxing my agents (to great effect!). I've been very happy with it, it provides much strict policy-level control for both process-level + network-level activity, as well as full visibility with a nice UI and dynamic runtime controls via WebUI. Way better than bubblewrap imo.

I originally saw it here on HN and have been hooked ever since.

[1] Screenshot: https://camo.githubusercontent.com/99b9e199ffb820c27c4e977f2...

[2] https://github.com/strongdm/leash

Fun fact: Do you know what container / sandboxing system is in most widespread use? Not docker containers, certainly not bubblewrap, and not even full VMs or firecracker. It's Chrome tabs.
by rolph | 2026-02-03 21:14:28+00:00
would we see age verification proxies?

the proxy service would verify you, by whatever means, and send whatever signal that means yes this is an adult, without passing on user data, allowing you to surf without nags.

3rd party verification perhaps?

rather than "sign on with [FANGS]" it would be "sign on and age verify with [FAANGS]"
by JumpCrisscross | 2026-02-03 21:14:29+00:00
> curious how you define national interests

My metric would be what the country’s population today and weighted populations of the future, if they could weigh in, would choose.

It’s possible to frame ex post facto and impossible to pin down in the present. And it’s inherently subjective and culturally relative. But it’s useful to reason with, including for finding patterns in history.

One pattern is the cost of corruption. If a leader is making billions off their power, they’re putting person about polity. That’s currently true in America [1] and China [2][3]. The difference is America has a chance to fix that in ‘28. China used to rotate leaders. But Xi fucked that up. (Note the language similarity between the above comment and how MAGA defends itself. “Trite bullshit.” Beijing has a hidden MACA problem, it’s just had a tougher time dealing with it because Xi reveres Mao.)

[1] https://www.wsj.com/politics/policy/spy-sheikh-secret-stake-...

[2] https://www.nytimes.com/2014/06/18/world/asia/chinas-preside...

[3] https://www.washingtontimes.com/news/2025/mar/20/us-intel-sa...
by whispem | 2026-02-03 21:15:03+00:00
Thanks for the feedback and for the question!
A number of choices in minikv are explicitly made to explain distributed system ideas clearly, even if not always optimal for hyperscale prod environments:

- Raft + 2PC together, as above, so people can see how distributed consensus and cross-shard atomicity actually operate and interplay (with their trade-offs);

- Several subsystems are written for readability and transparency (clean error propagation, explicit structures) even if that means a few more allocations or some lost microseconds;

- The storage layer offers different backends (RocksDB, Sled, in-memory) to let users experiment and understand their behavior, not because it’s always ideal to support so many;

- Features such as CDC (Change Data Capture), admin metrics, WAL status, and even “over-promiscuous” logs are exposed for teaching/tracing/debugging, though those might be reduced or hardened in production;

- Much of the CLI/admin API exposes “how the sausage is made,” which is gold for learning but might be hidden in a SaaS-like setting;

So yes, if I targeted only hyperscale production, some internals would be simplified or streamlined, but the educational and transparency value is central to this project’s DNA.
by charcircuit | 2026-02-03 21:15:08+00:00
>This also removes the typical more organic selection process of libraries and tooling, replacing it with whatever was most prevalent in the LLM’s training data

Another article written by someone who doesn't actually use AI. Claude will literally search "XYZ library 2025" to find libraries. That is essentially equivalent to how it's always worked. It's not just what is in the dataset.
by waynesonfire | 2026-02-03 21:15:13+00:00
I don't understand this article. ChatGPT made Google search and SO irrelevant so vibe coding is killing open source? ... That's a stretch.

> The LLM will not interact with the developers of a library or tool, nor submit usable bug reports, or be aware of any potential issues no matter how well-documented.

Arn't these interactions responsible for the claimed burn-out suffered by open-source maintainers? If you want interaction then, I don't know, go to a conference? Again, I don't get the issue. Seems like a good thing! Users are able to find answers and solutions to their quesitons more efficiently--all the while, still using the open-source library. The usage chart is still seeing tremendous growth! Developers are still using the library to solve their problems. It seems like exactly what open-source was intended for.

The issue to me is that, the incentives for investing in open-source have changed for some maintainers in such a way that they're no longer in alignment with their return on their investment. Maybe there are fewere people interacting with them and so fewer people to discover how "great" they are. Maybe fewer eye balls on their resume. The point is, open-source was a means to an end. And, so, frankly, I don't give a shit.

LLMs are making open-source technology accessible to more people and that's a good thing.
by aendruk | 2026-02-03 21:15:27+00:00
Appreciating this bit of slimy manipulation.

Unless you have questions or concerns
about the information above, there’s
nothing you need to do today.

[…]

Also effective in 30 days, your Quantum
Fiber marketing and privacy preferences
will be reset to AT&T’s default
settings. This means you’ll receive
email marketing messages, and we may
share limited personal information to
create, deliver, and measure targeted
advertising
by accidentallfact | 2026-02-03 21:15:42+00:00
The problem with twin studies:

1. There are genetic mutations that make you immune to HIV.

2. Monozygotic twins will both be immune, or not immune, while dizygotic twins may be either, one can be immune, while the other one could get AIDS.

3. Thus, a twin study would likely show that AIDS is a genetic defect.
by ptx | 2026-02-03 21:15:46+00:00
Yes... but...

Presumably the host replaces any occurrence of the placeholder with the real key, without knowing anything about the context in which the key is used, right? Because if it knew that the key was to be used for e.g. HTTP basic auth, it could just be added by the proxy without using a placeholder.

So all the attacker would have to do then is find and endpoint (on one of the approved hosts, granted) that echoes back the value, e.g. "What is your name?" -> "Hello $name!", right?

But probably the proxy replaces the real key when it comes back in the other direction, so the attacker would have to find an endpoint that does some kind of reversible transformation on the value in the response to disguise it.

It seems safer and simpler to, as others have mentioned, have a proxy that knows more about the context add the secrets to the requests. But maybe I've misunderstood their placeholder solution or maybe it's more clever than I'm giving it credit for.
by toroidal_hat | 2026-02-03 21:15:48+00:00
That doesn't seem like a useful argument either.

If future AI only manages to solve the variance problem, then it will have problems related to bias.

If future AI only manages to solve the bias problem, then it will have problems related to variance.

If problem X is solved, then the system that solved it won't have problem X. That's not very informative without some idea of how likely it is that X can or will be solved, and current AI is a better prior than "something will happen".
by whispem | 2026-02-03 21:16:53+00:00
Very relevant question!
The memory profile in minikv depends on usage scenario and storage backend.

- With the in-memory backend: Every value lives in RAM (with HashMap index, WAL ring buffer, TTL map, and Bloom filters). For a cluster with a few million objects, you’ll typically see a node use as little as 50–200 MB, scaling up with active dataset size and batch inflight writes;

- With RocksDB or Sled: Persistent storage keeps RAM use lower for huge sets but still caches hot keys/metadata and maintains Bloom + index snapshots (both configurable). The minimum stays light, but DB block cache, WAL write buffering, and active transaction state all add some baseline RAM (tens to a few hundreds of MB/node in practice);

- Heavy load (many concurrent clients, transactions, or CDC enabled): Buffers, Raft logs, and transaction queues scale up, but you can cap these in config (batch size, CDC buffer, WAL fsync policy, etc);

- Prometheus /metrics and admin API expose live stats, so you can observe resource use per node in production.

If you have a specific workload or dataset in mind, feel free to share it and I can benchmark or provide more precise figures!
by ivraatiems | 2026-02-03 21:17:30+00:00
I have had people show up at my house to ask if it was for rent, based on a fake post on Facebook using photos from Zillow from before my home was sold.

My realtor helped me get the photos taken down, but the Facebook ads for it are up to this day. Facebook completely ignores any and all attempts by me to report this malfeasance -- even though these ads literally have my personal home address on them!

It's a huge safety risk to me and not due to anything I did whatsoever; all I did was buy a house that was on the market and then move into it. It's a nightmare.
by embedding-shape | 2026-02-03 21:17:45+00:00
> "XYZ library 2025"

I'm fairly sure you made a typo, but considering the context, it's a pretty funny typo and would kind of demonstrate the point parent was trying to make :)

I agree with you overall though, the CLI agents of today don't really suffer from that issue, how good the model is at using tools and understanding what they're doing is much more important than what specific APIs they remember from the training data.
by mmh0000 | 2026-02-03 21:17:59+00:00
The GDPR really isn't that hard to follow, for a "mom & pop" business, it really comes down to:

* Limit data retention — Don't keep personal data longer than necessary
* Honor data subject rights — Allow individuals to access, correct, delete, or port their personal data

Simply, don't collect personal information if you don't need it. If you do need it, add a delete button.
Show HN: Corvus Robotics (YC S18) Inventory drones with full life-cycle autonomy
by robot_jackie | 2026-02-03 21:18:03+00:00
Hi HN - we're Jackie and Kabir, building Corvus Robotics. Here's a video about 8 years of building robots in 1 minute: https://x.com/JackAndTheBots/status/2018746764954878107

Every physical thing you own sat in a warehouse at some point, and every warehouse has to do inventory checks. It's a boring job where big companies staff full-time people going up 30 ft using lift trucks all day to just... scan stuff with a barcode scanner, and write things down with paper and pen if inventory is in the wrong place or missing.

We spent the last 8 years building flying robots to automate this faster and cheaper.

Our drones fly week after week without human involvement (no teleop either!). They work in extremely self-similar, often feature-poor, GPS-denied environments. Our autonomy engine is vision-based and ML-first, mapping pixels to trajectories within a ~60W compute power budget, running our autonomy software fully onboard and in real-time. This enables accurate inventory capture and safe flight around people, other robots, and material handling equipment. We build all of our drones in-house in the Bay Area.

There are limits to what the drones can do based on what they can see. For example, they can’t see multiple pallets deep, or open a box to count screws. That said, most large companies that make and handle physical goods store inventory in ways we can help with.

Along the way, we've learned that the core sensing and compute stack we've built is great for data capture at scale for many robots in industrial settings. We hope to share more about this soon!

We’re sticking around all day to answer questions here, so feel free to ask whatever questions come to mind!
by whispem | 2026-02-03 21:18:05+00:00
There’s not an “official” image on Docker Hub yet, but the repo ships with a ready-to-use Dockerfile and a Compose cluster example.
You can build with docker build . and spin up multi-node clusters trivially.
Static Rust binaries make the image compact (typically ≤30MB zipped; nothing compared to MinIO :)), with no heavy runtimes.
Requirements are dead simple: a recent Docker engine, any x86_64 (or ARM) host, and a few tens of MB RAM per instance at low load, scaling with data size/traffic.

I plan to push an official image (and perhaps an OCI image with scratch base) as the project matures — open to suggestions on ideal platforms/formats.
by canpan | 2026-02-03 21:18:14+00:00
I actually had a look. Now you can get messages and stuff from MS Graph. The situation is better than a few years ago when only very useless Teams APIs were available.

But the available APIs still suck. For example there is none to just get all recent notifications. I don't know if teams itself has access to more and better apis? If not that would explain a lot.
by johnstenner | 2026-02-03 21:18:20+00:00
I absolutely would want a vibe designed house or car. Vibe to completion, then have a now higher paid expert architect/engineer review the plan to confirm it is safe to proceed.

Until we can reliably trust these models to skip that last step, there is nothing inherently wrong with using AI to create, so long as it is manually reviewed for accuracy at the end.
by orwin | 2026-02-03 21:18:20+00:00
Ok, that's the second article on this that doesn't mention how it works in France.

I will explain because I see a lot of post that could be better if their author understood that the French system isn't the US system.

France 'prosecutor' role is divided in two: one is called 'procureur' and represent the state, but is chosen among judges by the executive power. The second is 'juge d'instruction' and represent the judiciary. They are chosen nominated by the local court without any executive power involvement. They lead the investigation, they order the raids, they order the arrest etc, without involvement from the 'procureur'.

The 'procureur' ask for a 'juge d'instruction' to lead an investigation on X/Y or Z (this fucking company name makes everything worse FFS). The judge will then collect evidence, for and against the procureur case, and then if necessary will ask for raids and auditions to finalise. When that's done and all the new evidence is collected (it can take on average 2 years, but if it's an international case like for our ex-president, it can take 10+), the 'juge d'instruction' will present all the gathered evidence to the procureur (who will decide to pursue or not) _and_ the accused.

This system exists to avoid as much as possible the executive (police and politicians) to use investigations as a scare tactic. Of course the magistrates know each other, and both corruption and influence is possible, and maybe that's the case here, but you ought to know the raid can't be at the behest of the procureur/president. We take separation of powers seriously here
by NadavBenItzhak | 2026-02-03 21:18:28+00:00
We built this course to move beyond "vibes-based" AI coding. It focuses on a structured methodology (Investigate -> Analyze -> Explain) specifically designed for enterprise mono-repos with millions of lines of code, where standard autocomplete often fails.

It covers:

Fundamentals: Context management, token limits, and handling hallucinations.

Methodology: Grounding prompts and chain-of-thought patterns.

Practical Tools: Includes open-source tools I wrote like Chunk Hound (code research) and Argu Seek (wide research), plus a curated list of CLI tools (ripgrep, fzf, lazygit) that play well with agents.

The content is open source (MIT) and available as docs, podcasts, or slides. Would love to hear how others are handling context drift in large codebases.
by mostafa8967 | 2026-02-03 21:18:41+00:00
Location: South Dakota
Remote: Yes
Willing to relocate: Yes
I’m a Senior Software Engineer with 14 years of hands-on experience in the .NET ecosystem, C#, SQL Server, and Linux administration. EF Core, Restful API, RabbitMQ.

LinkedIn: http://www.linkedin.com/in/mostafa-farahani7

Email: mostafafarahani89@gmail.com

I’ll send you my resume if you want to meet up.
by whispem | 2026-02-03 21:18:58+00:00
Absolutely: for all meaningful work I prefer small, logical commits using git add -p or similar, both for history clarity and for reviewer sanity.
In initial “spike” or hack sessions (see early commits :)), it’s sometimes more monolithic, but as the codebase stabilized I refactored to have tidy, atomic commit granularity.
I welcome suggestions on workflow or PR polish!
by quotemstr | 2026-02-03 21:19:06+00:00
Thinking about it a bit, I think I'd have

1. defined traditional suffixes and abbreviations to mean powers of two, not ten, aligning with most existing usages, but...

2. deprecated their use, especially in formal settings...

3. defined new spelled-out vocabulary for both pow10 and pow2 units, e.g. in English "two megabytes" becomes "two binary megabytes" or "two decimal megabytes", and...

4. defined new unambiguous abbreviations for both decimal and binary units, e.g. "5MB" (traditional) becomes "5bMB" (simplified, binary) or "5dMB" (simplified, decimal)

This way, most people most of the time could keep using the traditional units and be understood just fine, but in formal contexts in which precision is paramount, you'd have a standard way of spelling out exactly what you meant.

I'd have gone one step further too and stipulate that truth in advertising would require storage makers to use "5dMB" or "5 decimal megabytes" or whatever in advertising and specifications if that's what they meant. No cheating using traditional units.

(We could also split bits versus bytes using similar principles, e.g. "bi" vs "by".)

I mean consider UK, which still uses pounds, stone, and miles. In contexts where you'd use those units, writing "10KB" or "one megabyte" would be fine too.
by felixkothe | 2026-02-03 21:19:39+00:00
Knowlix — ONSITE (Munich, DE) — Full-time

About us: We’re building AI agents that automate complex back-office workflows for SMEs. Backed by European VCs; fast-moving, product-obsessed team

Hiring: Multiple roles in engineerin, product & growth (onsite Munich only).

Why join: Real users, real autonomy, ship fast with a small senior team.

Contact: Please apply via the Ashby page (https://jobs.ashbyhq.com/knowlix)