MurphyA/hacker-news huggingface dataset:
by yason | 2026-02-21 11:00:21+00:00
Next EU could mandate an attitude adjustment to the industry wishing to sell their products in the European Common Market.

Batteries are part of a device.

There are other parts that can be replaced by the owner or third parties if there are sufficient parts supplies, either first-part or third-party, and these parts aren't explicitly killed by the device's DRM even if they're sourced outside of the manufacturer's own "replacement assemblies" that cost half the phone eventhough it's just a $10 part that needs replacing.

Further there is the software which is probably the most disposable of all. First of all, the keys to a device should come with the device. The device can default to booting software signed by the manufacturer but the user should always be able to use a physical key to unlock the device and install his own keys and certificates instead.

Further, manufacturers should be forced to either keep supporting the device's software or release all the necessary blobs and parts as legal abandonware so that others can hack and reverse-engineer it further, allowing legal reimplementation of the software in open source.
by locknitpicker | 2026-02-21 11:00:25+00:00
> Why in the world would you do squash merges?

Why would you not want to squash merges? It's one of three options offered by GitHub in their PR merge buttons.

They create a linear commit history, which is what you want when you have to audit changes.

> except to clean up messy mini-branches written by total noobs.

Nonsense. You get a messed up commit history as easily as when you create a PR in GitHub, and after team members merge their commits, you click on GitHub's "update branch" button.

You also get a messed up commit history if you merge a PR after someone else merged theirs.

You will always mess up your pristine commit history if you have more than one person posting and merging branches. With one notable exception: squashed commits.
by audunw | 2026-02-21 11:00:57+00:00
Yeah, thank god. As long as it’s easy to remove and replacement batteries can easily be purchased by individuals, I want my phone and battery glued, thank you very much.

I like apples approach to removable battery glue. Though it needs an extra tool. These days it should be easy to make a cheap USB-C PD powered thing that supplies a good DC voltage.
by burnerToBetOut | 2026-02-21 11:01:04+00:00
The answer, my friendow, is blowing in the context window [1]…

_______

…LLMs already "know" these books deeply, but without a structured prompt scaffold they apply that knowledge inconsistently and at low confidence. Giving the model a explicit lens — "review this as if you're checking against Clean Code heuristics C1–C36" — concentrates attention and dramatically reduces hallucinated or off-topic feedback…

…

Where I'd push back or warn you:

Context collapse is your #1 enemy. Clean Code was written for Java in 2008. DDIA is about distributed systems at scale. If you apply the Clean Code reviewer to a 50-line Python script, you'll get pedantic nonsense about function length when the actual problem might be that the data model is wrong. Your skill selection logic needs to be domain-aware, not just "throw all skills at every file"…

…

_______

[1] https://g2ww.short.gy/ZLStasQ1
by codethief | 2026-02-21 11:01:59+00:00
> It cites specific sections of the DSA.

Just to be sure, by "it" you're referring to the committee report?

> Your previous claim was that DSA did not have hate speech provisions. Are you claiming DSA Article 22 does not exist, for example?

Please do quote the parts of DSA Article 22 that regulate hate speech or speech in general. It says absolutely nothing of the kind. It concerns itself with "illegal content" and defines procedures to handle it. What content is legal or illegal is defined by the laws already in place in the different member states. Also, procedures to handle illegal content already existed at a national level before DSA was enacted, so the only thing that DSA did was to harmonize them.
by michaelt | 2026-02-21 11:02:23+00:00
> I don't think this is Facebook playing 4D chess trying to hide content from politicians by detecting who is traveling internationally.

I agree the triggering criteria isn't international travel - but giving VIP treatment to VIPs isn't "4D chess" it's just business as usual.

You get elected to congress? The moment the list of winners comes out, someone from Comcast finds the accounts and marks them as VIPs. Someone at Uber does the same. Someone at Amazon does the same, and so on.

Typically this will limit who in Customer Services can view the addresses on your account and reset your password. But it can also mean you get free upgrades, put you at the front of the queue, assign your orders to highly-rated workers, etc - or for social media, a curated experience making the site look classy and enriching.
by Shmungus | 2026-02-21 11:02:29+00:00
The previous documented record for simultaneous Claude Code agents is 16, set by Anthropic's own engineering team building a C compiler.

Tonight I ran 24.
What made this possible: I built a Tokio-native LLM orchestration pipeline in Rust that routes inference through a local Mistral 7B model running on an RTX 4070. The agents coordinate through governance docs (CLAUDE.md, AGENTS.md) that define module ownership and test ratios, they don't communicate directly, they communicate through the codebase.

The recursive part: the orchestrator was built using the same multi-agent workflow it enables. The MCP server that lets Claude call the pipeline natively.

Technical details:

683 tests, 0 failures
1.53:1 test-to-production ratio enforced by pre-commit hooks

9-stage deduplication pipeline with circuit breakers

Sub-millisecond pipeline overhead (inference dominates at 3.6s on Mistral 7B)

Repo: github.com/Mattbusel/tokio-prompt-orchestrator
by athrowaway3z | 2026-02-21 11:03:09+00:00
Every time i see some new orchestrator framework worth more than a few hundred loc i cringe so hard. Reddit is flooded with them on the daily and HN has them on the front page occasionally.

My current setup is this;

- `tmux-bash` / `tmux-coding-agent`

- `tmux-send` / `tmux-capture`

- `semaphore_wait`

The other tools all create lockfiles and semaphore_wait is a small inotify wrapper.

They're all you need for 3 levels of orchestration. My recent discovery was that its best to have 1 dedicated supervisor that just semaphore_wait's on the 'main' agent spawning subagents. Basically a smart Ralph-wiggum.

https://github.com/offline-ant/pi-tmux if anybody is intrested.
by varispeed | 2026-02-21 11:03:15+00:00
> The device can default to booting software signed by the manufacturer but the user should always be able to use a physical key to unlock the device and install his own keys and certificates instead.

This part is not going to happen, because security services need their backdoors intact. If you supply user with keys, they might flash the device with more secure operating system rendering any surveillance effort fruitless.
by sa-code | 2026-02-21 11:05:04+00:00
> every time you try something innovative the "policy people" will climb out of their holes and put random roadblocks in your way

This is so relatable. I remember trying to set up an LLM gateway back in 2023. There were at least 3 different teams that blocked our rollout for months until they worked through their backlog. "We're blocking you, but you’ll have to chase and nag us for us to even consider unblocking you"

At the end of all that waiting, nothing changed. Each of those teams wrote a document saying they had a look and were presumably just happy to be involved somehow?
by ColinWright | 2026-02-21 11:05:36+00:00
I used to have a LinkedIn account, a long time ago. To register I created an email address that was unique to LinkedIn, and pretty much unguessable ... certainly not amenable to a dictionary attack.

I ended up deciding that I was getting no value from the account, and I heard unpleasant things about the company, so I deleted the account.

Within hours I started to get spam to that unique email address.

It would be interesting to run a semi-controlled experiment to test whether this was a fluke, or if they leaked, sold, or otherwise lost control of my data. But absolutely I will not trust them with anything I want to keep private.

I do not trust LinkedIn to keep my data secure ... I believe they sold it.
by sergiomattei | 2026-02-21 11:05:47+00:00
This looks nice, congrats on the launch. I'm trying this at work on Monday, I suffer from this problem for tons of MCP tools that are MCP only, not CLI, and completely fill my context window.

First thoughts: it seems the broader community is moving towards Agent Skills as a "replacement" for MCPs to tackle the context pollution problem.

Agent harnesses like Pi don't ship with MCP support as an intentional design choice. MCP servers[0] are being rewritten as pure CLIs in order to support this new scenario.

Thoughts on this?

[0]: https://github.com/microsoft/playwright-cli
by thisislife2 | 2026-02-21 11:05:55+00:00
True. I didn't believe about houses not being rented to muslims, till I helped a muslim friend hunt for a house - a woman we contacted to rent a house said that her husband doesn't want to rent their flat to muslims. She was genuinely embarrassed by it when I asked why, and she honestly said she doesn't understand this kind of religious bigotry and her husband is has become a "khattar Hindu" who just doesn't like muslims.

However as this was South India, things aren't as bad - when I shared this incident with a Hindu friend of mine, he immediately offered to rent his flat out, if I would vouch for the tenant. I did.

Sometimes it is hard to wrap your mind on why Sanghi self-esteem is so tied to putting down other religion / culture to feel great about their own religion / culture (while the ordinary majority Hindus in India have no problem in feeling pride for their history, as they don't confuse religious and political actions).
by yason | 2026-02-21 11:06:08+00:00
That looks exactly like an office app should look like. Basic interface patterns, clear distinctive visual areas and borders, all in the tradition of a classical graphical user interface. And yes, classical GUI more or less peaked in the early 2000's and it has generally been a downhill from there because the irresistible need of the industry for offering "something new" every few years.
by xen0 | 2026-02-21 11:06:09+00:00
I want every commit to represent a buildable state in which I have confidence automated tests pass. Bisecting is made unnecessarily difficult otherwise, and it's nice to be able checkout any commit and just build something for testing.

This constraint is usually enforced by code review.

On Github, the unit of code review is the PR.

Therefore, I prefer squashing.
by ho_schi | 2026-02-21 11:06:37+00:00
It looks nice. Less nice but very good in Germany is DWD Warn Weather:

https://apps.apple.com/de/app/dwd-warnwetter/id986420993?l=e...

Yes. We pay for it with taxes! And again with our money in the App Store. But the app success is build upon the lawsuit from WetterOnline which is a private company.

https://www.bundesgerichtshof.de/SharedDocs/Pressemitteilung...

The lawsuit backfired and made the state funded app well known. WetterOnline attacked the DWD because the state funded app is superior :)

I think in Italy they have some similar app. Would be nice if the EU helps us to unify the app. And add offline capabilities, bad or no internet happens. The weather radar is offline of less use but the forecast still helps.

They release videos for dangerous weather on YouTube. We’ll know for regular people, in regular cloths, speaking like regular Germans. Everyone loves it :)

I like it when important services are provided by the state and private companies. Save foundation! In worst case the state is always better. In best case they compete and public benefits. In this case the private company just sucks. But they made a good job in advertising for DWD ^^

PS: If someone would implement a nice weather for Linux (best Gtk) based upon DWD public data? DO IT!
by Terretta | 2026-02-21 11:07:04+00:00
Has EU weather sources per credits (DWD, ECMWF, EUMETSAT -- roughly what it's doing is graphing multiple models), but if you are into weather apps you're likely best off with Carrot that (a) lets you design your own UI including matching this (more or less), and (b) lets you choose among weather sources and flip among them with a tap.

If it's about cute UI and key notifications, try Hello Weather. For microcell notifications on anything, Tomorrow weather. For much better maps, WeatherMap.

For comparing multiple models, try Windy.app. For coastal barrier island use, I have 8 graphed at once, most of them EU models.

Very little reason for any weather app beyond Carrot, though Apple Weather is surprising evolved from the app of 20 years ago, no longer the 4th app to replace after messaging, maps, and browser).

Carrot is the only weather app with a vicious weather control AI singing an entire Broadway concept album about your destruction at you though.
by Longwelwind | 2026-02-21 11:07:35+00:00
Trunk-based development fits nicely when you have a single deployment product like a SaaS and you don't need to maintain old versions of your software. You only have one prod environment.

If you build a software that you distribute so people can deploy it themselves (a library, a self-hostable solution, ...), then you most likely semantic versioning. In that case, the best model is to use what semantic release offers.
by jjtwixman | 2026-02-21 11:07:46+00:00
Typical American arrogance. You assume you can treat everyone around you like shit and we'll just put up with it.

Don't you understand? You're threatening to invade us, China isn't. So no matter how bad China may be, you're still worse at the moment.

You're so blinded by arrogance. You cannot imagine a world in which you are hated, but it's already here.
by password54321 | 2026-02-21 11:07:48+00:00
Not claiming anything to be false, just a reminder that you should question ones opinion a bit more and not claim they "know what they are talking about" because they worked with Fei-Fei Li. You are outsourcing your thinking to someone else which is lazy and a good way of getting conned.

What even happened to https://eurekalabs.ai/?
by mrweasel | 2026-02-21 11:07:50+00:00
One thought I've had is that it has to do with your level of engangement. If like me you doesn't really use social media for more than a few minutes a day (in my case I count Snapchat and YouTube Shorts, because that's what I have), then you start seeing some a lot of boobs.

It seems like the algorithm panics, because you don't engange with anything much, or because your interests shifts to often and it can't deal with it. So it falls back to boobs.

There's also a sad trend of assuming that because you're into lifting, your also misogynistic. The more you engange with fitness content, even if it's training programs or how to correctly do certain exercises, platforms like YouTube will start flinging misogynistic content at you and it's incredibly hard to remove.
by haute_cuisine | 2026-02-21 11:07:55+00:00
I think the main problem is tech workers finally became a commodity. It was a brief time when hiring was hard and it was possible to get some sense of power because you could freely walk away or because you were a craftsmen.

Over the years, power slowly returned back to management and the industry figured out how to slice the creative role into small cogs: QAs, FEs, BEs, SREß, OPSs, POs, PMs. It's ten people now instead of three crafsmen. They can now follow a very strict process to produce average software with a lot of overhead. Customers don't care because one half is forced to use it and the other don't have a taste of what good software is. Partially, because they use abysmal MS products. Apple briefly showed to an average Joe what is possible when people care, but they're slowly losing it.

Now it's node/js everywhere and fierce competition being a ticket taker. People with no passion who are here just for the money and who don't care about the code. People who are here to play promotion politic games. Coding is a regular job now which pays decent and has low barrier to entry. You can fake it very far now with AI assistance.
by PaulKeeble | 2026-02-21 11:10:05+00:00
I replaced a battery in my (quite aged now at 6 years) old mobile last month. The original one puffed up and damaged the case holding the mobile together, incidentally it tested as 100% good in capacity! Took about an hour to replace the battery with an aftermarket replacement, quite fiddly work involving pludgers and tiny screws, cost more than double the price of the battery just for the specialist tools to get into it.

I miss the days of that first google phone where I could just pop the back and replace the battery, I used it quite a bit with a second battery. My modern phone lasts a bit longer so its less of a concern but batteries are a consumable we know they age out faster than the devices themselves and they ought to have been replacable.
by everdrive | 2026-02-21 11:10:43+00:00
But here's the thing I don't get. I can see the argument for AI endangering our jobs. But why does this also mean that rapid adoption of AI on a personal level of is so important? In an AI world, there could be a new bell curve of talent and a fight to stay ahead. So ... adopt early so you're the one not left behind. (and implicitly, most other people are left behind?)

If AI tightens down the job market I just don't see why there would need to be this frantic urgency to adopt it. Getting a small head start might not mean very much once the dust has settled. Employers will still be cutting, and there will still be new blood who will adapt to new technology faster than you can.
by summarity | 2026-02-21 11:11:20+00:00
No engine can be 100% perfect of course, the original comment is broadly accurate though. CodeQL builds a full semantic database including types and dataflow from source code, then runs queries against that. QL is fundamentally a logic programming language that is only concerned with the satisfiably of the given constraint.

If dataflow is not provably connected from source to sink, an alert is impossible. If a sanitization step interrupts the flow of potentially tainted data, the alert is similarly discarded.

The end-to-end precision of the detection depends on the queries executed, the models of the libraries used in the code (to e.g., recognize the correct sanitizers), and other parameters. All of this is customizable by users.

All that can be overwhelming though, so we aim to provide sane defaults. On GitHub, you can choose between a "Default" and "Extended" suite. Those are tuned for different levels of potential FN/FP based on the precision of the query and severity of the alert.

Severities are calculated based on the weaknesses the query covers, and the real CVE these have caused in prior disclosed vulnerabilities.

QL-language-focused resources for CodeQL: https://codeql.github.com/
by eqvinox | 2026-02-21 11:11:33+00:00
> What if you want a library that isn't available in every distro? Or a specific version of a library?

Then your wrapper builds a native package for that first. After all it is building a native package for your application next, why would it be unable to also build a package for that library?

> I don't think anyone follows your "rule" because it would be such a mess.

Everyone offering distro repos is building packages like that, and that's a lot of projects.
by JumpCrisscross | 2026-02-21 11:11:34+00:00
> strongly doubt that this company runs their own weather stations or meteorological models. Their only recurring cost is API access to the companies that provide weather data

No. But I'd suspect a tabula rasa approach to weather–particularly given it hasn't been rolled out globally in one go–incorporates satellite data, local measurements, et cetera.

Again, that may not take constant subscriprtion. But it does take constant expert monitoring and awareness.

> Considering that there are many free weather APIs

If you're a glorified viewport into these APIs' data, you may be able to stick with their most-static data and fire and forget. In reality, what those outputs mean change as the models and techniques evolve. There are new APIs with new data constantly coming out, and they're often adding connectors.

> a weather app shouldn't have large maintenance costs that couldn't be covered by a one-time payment

The only way I see this working is if the user is explicitly aware the app can break at any time if one of the APIs change anything, which they often do, and that this may not cause any obvious failures, just a decay in the app's accuracy or usefulness.
by fweimer | 2026-02-21 11:11:41+00:00
How does LibreOffice handle ODF standardization? If they want to add a new feature that result in changes how things are formatted visually, write they papers to update the ISO standard for ODF, working with other office suite implementers to achieve interoperability, wait a couple of years for the new standard with the changes getting published, and finally turn on the feature for users?

My impression is that this is more or less how ISO standards are supposed to work. Personally, I don't want to work in such an environment.
by homebrewer | 2026-02-21 11:11:44+00:00
I take it you haven't had the pleasure of working with your average ("dark matter" as they're called here) developers. I wouldn't call myself an "advocate" of squashes, but it's often the only practical way of keeping git history somewhat usable when working with people who refuse to learn their VCS properly.

I chunk my changes into tiny commits ("linter"/"tmp"/"wip"), but then rebase aggressively, turning it into a set of logical changes with well-formed commit messages. git bisect/revert work great with history written in this way even years layer.

But: most of the people I've been interacting with also produce lots of "wip"/"tmp", but then skip the rebase. I can only offer my help with learning git rebase for so long before it starts taking too much time from the actual work. So squash it is: at least it produces coherent history without adding thousands of commits into `--ignore-revs-file`.
by artk42 | 2026-02-21 11:12:30+00:00
I think it’s opposite. The general population always has nothing with outstanding engineers thru the history. It’s hard to say that VC bubbles of recent decades really drove the amount of outstanding engineers, it’s just an overall increase of prosperity, while hot capital in addition incentivesed quite terrible ways to get rich quick, effectively balancing back this freshly activated dev capital. So now ai takes back monopoly on dev capital from bigbiz, and general youth population is weird like it always has been, but in reality doing less drink/smoke/drugs, and sometimes their values are better than ours, just need some more time to polish. I think we are not doomed.

P.S. but these chinese robots are really scary
by fxj | 2026-02-21 11:12:47+00:00
He also talks about picoclaw which even runs on $10 hardware and is a fork by sipeed, a chinese company who does IoT.

https://github.com/sipeed/picoclaw

another chinese coompany m5stack provides local LLMs like Qwen2.5-1.5B running on a local IoT device.

https://shop.m5stack.com/products/m5stack-llm-large-language...

Imagine the possibilities. Soon we will see claw-in-a-box for less than $50.
by stubish | 2026-02-21 11:12:52+00:00
People are already annoyed, which is why society is demanding the stuff already age restricted for decades or even centuries actually be restricted on the Internet. The battle has never and will never be about allowing kids free access to porn. The battle is about restricting it in a way that doesn't endanger them or their privacy. Failing to do that is what ends in a dystopia, where tech and governments use society's demands as an excuse to move us further into a surveillance state. Like the proposed laws being discussed, centralizing data in an easily subpoenable location.