MurphyA/hacker-news huggingface dataset:
by AndrewDucker | 2025-07-09 11:17:07+00:00
I am hoping that this is the thing that triggers Matter/Thread to go mainstream.

I'm currently blocked because Google and Amazon don't support "Generic Switches". Which means that if I switch over a light-bulb to being a smart one I can't use something like the Arre Smart Button to control them. Which seems like such a standard requirement that I do not understand why it's not supported.

If Ikea will let me set that up then I'll be delighted.
by fzeroracer | 2025-07-09 11:17:26+00:00
This is stuff that companies already handle with their current cancellation pipelines. Hooking up a short circuit that flags whatever user in their DB as having cancelled is something that I would absolutely toss a junior engineer at and expect them to finish in three or so working days, maybe slightly longer.

The only way it's more onerous than that is if companies have an absolutely shit design under the hood, or they're using malicious compliance to argue that this feature specifically needs eight weeks of planning poker and at least five senior engineers to sign off on each iteration of the design phase.
by MoreQARespect | 2025-07-09 11:17:28+00:00
>No regular developer will carefully review 50 changed snapshots.

If you follow a habit of making small, incremental changes in your pull requests (which you should anyway), those 50 snapshots will generally all change in the same way. A glance across all of them to see that (for example) a box moved to the left in all of them.

>The problem with snapshots is that it's doing the exact same thing. It asserts on lots of completely unimportant stuff.

A problem more than made up for by the fact that rewriting it, eyeballing it and approving it is very quick.

>Unlike proper unit tests however I can't make it better

If the "then" part of a unit test "expects" a particular error message or json snippet, for instance, it's a giant waste of time to craft the expected message yourself if the test can simply snapshot the text from the code and you can eyeball it to see if the diff looks correct.

I have written thousands of unit tests like this and saved a ton of time doing so. I've also worked with devs who did it your way (e.g. craft a whole or part of the json output and put it in the assert) and the only difference was that they took longer.

>and personally do a good job of only asserting relevant things

If, for example, you're testing a dashboard and the spec is a hand scribbled design that shows roughly what it looks like, all the other ways to assert the relevant things are vastly more expensive and impractical to implement.

In practice most devs (and you too i expect) will simply leave the design untested and design regressions by, say, some gnarly css issue would be undetected except by manual test.

>Snapshots are a blunt no-effort tool for the lazy dev

95% of devs don't use snapshot tests because they're super sensitive to flakiness and because ruthlessly eliminating flakiness from code and tests requires engineering discipline and ability most devs don't have.

For those who can, it massively accelerates test writing.
by danielroe | 2025-07-09 11:17:38+00:00
the best guarantee I have is that Nuxt is still independent - it's (some of) the core team who are employed by Vercel. you can see this is the case for svelte/sveltekit.

plus, as an open source project, no one _can_ shutter Nuxt. as long as we have a community, we are alive.

from another point of view, any open source project is ultimately accountable to the community, and I think that's especially true for nuxt.

at the end of the day, if sebastien isn't happy with my leadership he can replace me. (and that's _good_ - I wrote about it here: https://roe.dev/blog/governance-and-abuse)

and equally if the community aren't happy with the direction of nuxt, they can always fork it. (and that's _good_)

in fact, I think I'd say that accountability is always good.
by fc417fc802 | 2025-07-09 11:17:53+00:00
To the same extent that you need to prove the correctness of the compiler and the language runtime I guess. Arbitrary width integers are a core feature of quite a few languages.

Given Lean's raison d'etre it wouldn't surprise me if the relevant library code was verified. If using another language such as Python I think it would be fairly reasonable to take the underlying implementation on faith. If we're going to start questioning whether a core part of the runtime that implements basic arithmetic operations has bugs then why are we not also suspecting the operations provided by the CPU and other hardware?

We probably should suspect those things, but as a matter of practicality we're going to need a boundary at present.
by npteljes | 2025-07-09 11:17:57+00:00
>A copy of a book isn't a travesty, so why should a copy of a painting be one?

This is because of how humans appreciate where the spirit of a work is. In case of a book, most of the essence is in the words, not in the paper or the ink - although, people do appreciate the print itself too to a great deal. But because the words carry the most meaning, the work gets copied, translated, even modernized, and agreed to not lose much of its meaning. After the mass printing era, there is no such thing as "a single master book" when referring to a work. There can be drafts, a manuscript, generations of copies referred to as different editions, etc. It's a mass production affair with a blueprint and products, whereas in case of a painting, there is a single, final version original usually, and subsequent reproductions are copies and modifications of that.

The other thing is that a copy of a painting is not a travesty at all. Many appreciate and decorate with replicas, prints, view them online, use them as wallpaper on their device, etc. I don't think people think of any of this as a travesty. The issue here is to present a copy as the original, in which case the replica becomes a fake. This is a lie, and a betrayal, and these evoke strong feelings in humans.
by hnlmorg | 2025-07-09 11:18:08+00:00
Why would ignoring CR lead to problems? It has nothing to do with line feeding on any system released in the last quarter of a century.

If you’re targeting iMacs or the Commodore 64, then sure, it’s something to be mindful of. But I’d wager you’d have bigger compatibility problems before you even get to line endings.

Is there some other edge cases regarding CR that I’ve missed? Or are you thinking ultra defensively (from a security standpoint)?

That said, I do like your suggestion of treating CR like LF where the schema isn’t sensitive to line numbering. Unfortunately for my use case, line numbering does matter somewhat. So would be good to understand if I have a ticking time bomb
by gorgoiler | 2025-07-09 11:18:13+00:00
My first reaction here was horror: Home Assistant and Zigbee integrate perfectly with IKEA’s devices, and the devices are beautifully designed! Please don’t take these away! Only the other day did I marvel at how a low battery indicator flashes on one of my remotes when I use it. A design flourish that I really appreciated.

But I read that Thread supports IPv6 via mesh networking. It did always feel a bit awkward having Zigbee networking and IP networking competing over the same site. It would be very nice to issue commands from any peer to any other peer, using standard networking. Can anyone here confirm that Matter/Thread will be a bright, open, and happy new future?

A lot of people I know would scoff at “smart home” stuff. I used to. Having a programmable house is incredibly useful though. When all your lights and sensors are available for programming you can do stuff that’s cool not because it is particularly innovative but because it is incredibly easy to implement:

- my partner can control a “do not enter, call in progress” red light bulb;

- my outside lights trigger off PIR, door sensors, or Ring motion detection;

- I have a series of indoor lamps come on in succession if motion is detected outside at night;

- we programmed a push button to turn a light green on one tap and red on a double tap for a fun game of twenty questions;

- and my indoor Ring cameras shut down unless both my partner and I are out of the house.

All of these things were trivial to do given that everything is available on one Home Assistant instance!
by dingi | 2025-07-09 11:18:30+00:00
At some point, we built REST clients so generic they could handle nearly any use case. Honestly, building truly RESTful APIs has been easy for ages, just render HTML on the server and send it to the browser. That's 100% REST with no fuss.

The irony is, when people try to implement "pure REST" (as in Level 3 of the Richardson Maturity Model with HATEOAS), they often end up reinventing a worse version of a web browser. So it's no surprise that most developers stop at Level 2—using proper HTTP verbs and resource-based URIs. Full REST just isn't worth the complexity in most real-world applications.
by mort96 | 2025-07-09 11:18:45+00:00
So your view is that the person who coins a term forever has full rights to dictate the meaning of that term, regardless of what meaning turns out to be useful in practice and gets broadly accepted by the community? And you think that anyone who disagrees with such an ultra-prescriptivist view of linguistics is somehow a "mediocre programmer"? Do I have that right?
Show HN: OpenRouter-SDK – A Type-Safe Rust Client for OpenRouter AI APIs
by the_plug | 2025-07-09 11:19:00+00:00
I've built a production-ready Rust SDK for OpenRouter.ai that makes it trivial to work with 100+ LLMs (Claude 3, GPT-4, Mistral, etc.). Key features:

Zero-Cost LLM Orchestration – Automatic request batching and model fallback

Multi-Modal First – Clean API for text+image prompts (e.g., GPT-4 Vision)

Streaming Done Right – Tokio-based async with backpressure support

Why Rust? After wrestling with Python's GIL in production, we needed:

Memory safety for long-running inference servers

Easy WASM compilation for edge deployments

Fearless concurrency for parallel model queries
by mft_ | 2025-07-09 11:19:28+00:00
Huh... anyone know what this will mean for people with legacy Ikea lightbulbs and hub?

e.g. if I add future Ikea lightbulbs or other equipment, will this mean managing them via a different system?

(By the by, I've been very happy with Ikea bulbs so far; while other people complain of LED bulbs with a short lifespan, [touches wood] I've not had a single failure with Ikea smart bulbs, with ~7 years and counting on one of mine.)
by threetonesun | 2025-07-09 11:20:00+00:00
I think since they used [todoId] in the example they mean a static page which does not exist at build time. Which both can do, it’s called ISG (or on-demand in the Astro docs), but it requires a server to work, or you can create a static route that accepts any parameters and pass those to JavaScript to run on the client.
by SePP | 2025-07-09 11:20:23+00:00
Prezly | Europe Timezone , REMOTE | https://www.prezly.com

We’re looking for curious, hardworking people to join our team, to help us do the best work of our lives. Together we’ll create a product that helps people, organizations and brands share their stories with the world. Prezly is a profitable, bootstrapped company fully owned by its founders.

1. Typescript/React Developer - https://careers.prezly.com/senior-tsreact-developer 2. PHP Developer - https://careers.prezly.com/senior-php-developer
by fnordian_slip | 2025-07-09 11:20:25+00:00
Sorry if it wasn't obvious, my reply was meant as an analogy. The parent comment said "The sole reason Russia invaded Ukraine was that it was flirting too much with NATO."

So I wanted to show that people have also used cheap excuses like this in the past, and that we shouldn't give Russian propaganda the benefit of the doubt.

Of course there weren't any atrocities commited against the Sudetendeutsche population, I just assumed everyone knew that, but that's due to my German-centric view of history.

I should have expected this, as sarcasm doesn't translate well over text, especially if people don't share the same cultural background.
by rjmunro | 2025-07-09 11:21:01+00:00
This looks really cool. I'd see it being useful as a headset to talk to camera people and others during a live stream. We already have hardware for this, but if we didn't it would be great.

For my use, I'd like to be able to join and monitor multiple groups at once (cameras, presenters, certain others individually), and select which I talk to (including being able to talk to several or all groups at once).

Another feature idea, if you are out of range, it would be good if there was an option to save the message until you come back and replay it.
by paulcole | 2025-07-09 11:21:11+00:00
There is quite a big gap between $100k and $250k.

If you happen to find yourself in that gap you can become moderately rich over a period of several decades by living frugally and investing in index funds with excess cash.

Or don’t do that and don’t become moderately rich. That is fine, too! It’s not impossible but you must prioritize the goal of becoming moderately rich over other goals.
by senko | 2025-07-09 11:21:28+00:00
Independent consulting (as in, I tell you what to do, not you tell me what to do) for AI integrations (whether and how to add AI to your product/systems, and how to effectively use AI for coding).

There's so much BS in AI that there's value in someone you trust telling you what does and doesn't work. Of course, there's no shortage of people doing exactly that, so the clients come through extended network (word of mouth, purely inbound).
by ninkendo | 2025-07-09 11:21:49+00:00
> Where this kind of API design is useful is when there is a user with an agent (e.g. a browser or similar) who can navigate the API and interact with the different responses based on their media types and what the links are called.

The funny thing is, that perfectly describes HTML. Here’s a document with links to other documents, which the user can navigate based on what the links are called. Because if it’s designed for users, it’s called a User Interface. If it’s designed for application programming, it’s called an Application Programming Interface. This is why HATEOAS is kinda silly to me. It pretends APIs should be used by Users directly. But we already have that, it’s called a UI.
by hennell | 2025-07-09 11:22:32+00:00
So because you got a good response the conclusion is invalid? How does the user know if they got a good response or a bad one? Due to the parameters passed most LLMs are functionally non-deterministic, rarely giving the same answer twice even with the same question.

I just asked chatgpt "whats the best database structure for a users table where you have users and admins?" in two different browser sessions. One gave me sql with varchars and a role column using:

role VARCHAR(20) NOT NULL CHECK (role IN ('user', 'admin')),

the other session used text columns and defined an enum to use first:

CREATE TYPE user_role AS ENUM ('user', 'admin', 'superadmin'); //other sql snipped role user_role NOT NULL DEFAULT 'user',

An Ai Assistant should be better tuned but often isn't. That variance to me makes it feel wildly unhelpful for 'documentation' as two people end up with quite different solutions.
by pradn | 2025-07-09 11:22:36+00:00
You have to be careful to make a distinction being in the EU and using the Euro as your currency. You can benefit from the EU common market, with its uniform rules/standards, easy capital flows, subsidies, and industrial policy. All without using the Euro as your currency, and being subject to the monetary policy of the ECB.

Being in the EU without using the Euro has been pretty good for Poland.
by nickcoury | 2025-07-09 11:23:17+00:00
A lot of watches now have Bluetooth music playback, both smart watches and sport watches.

I can also still manage to fit an iPhone 12 Mini comfortably in many running shorts in the small rear key pockets or back zipper pockets. Some running waistbands also work well. But it's hit and miss vs old mp3 players that weighed next to nothing.
by api | 2025-07-09 11:23:28+00:00
Isn’t this the history of home automation? The money is in getting people locked into a “system,” but the systems are things that tend to rapidly become dated. So people will invest in a system and either get disillusioned due to the downside of lock in or the system goes obsolete and the newer stuff is not compatible because it’s a whole new system. Rinse, repeat.

There have been many attempts at industry standards but they fray around the edges. Nobody understands that a protocol and a spec is not a user experience, so the standards just become the basis for closed walled garden “systems.”

It’s why I stay away from it.
by alsko | 2025-07-09 11:24:20+00:00
Matter was created by the Connectivity Standards Alliance (CSA), formerly known as the Zigbee Alliance! Basically, Matter is the next generation Zigbee. Thread as a protocol predates Matter, and it is just one of the supported transports, together with Wifi and Ethernet (for now).

Edit: One thing Matter adds that was not in Zigbee is Bluetooth provisioning, letting you use your phone to add a device to your network without QR codes or numbers to type in.

Also fun fact; Homeassistant is part of the CSA and apparently, Google, Apple and others use HA for testing!
by jdlshore | 2025-07-09 11:25:13+00:00
REST on the WWW only works because humans read and interpret the results. Arguably, that’s not an API (Application Programming Interface) but a UI (User Interface).

I have yet to see an API that was improved by following strict REST principles. If REST describes the web (a UI, not an API), and it’s the only useful example of REST, is REST really meaningful?
by inti_bug | 2025-07-09 11:26:05+00:00
Intigriti is the trusted leader in crowdsourced security, empowering the world’s largest organizations to find and fix vulnerabilities before cybercriminals can exploit them.

Since 2016, the company has helped its customers reduce risk with the expertise of 125,000+ global security researchers, enabling real-time vulnerability detection and preventing costly breaches.

Intigriti's flexible platform offers a full suite of solutions, including Bug Bounty, PTaaS, Vulnerability Disclosure Programs (VDP), Focused Sprints, and Live Hacking Events, tailored to your evolving digital needs and delivered through a pay-for-impact model, meaning you only pay for valid vulnerabilities submitted, optimizing budget and resource use while reducing operational noise.

With industry-leading triage, commitment to legal compliance, and exceptional customer service, Intigriti is the go-to choice for organizations like Coca-Cola, Microsoft, and Intel to secure their digital assets and stay ahead in a changing world.
by vidarh | 2025-07-09 11:26:49+00:00
I agree with almost all of this.

You could allow unconstrained selects, but as you note you either need row level security or you need to be absolutely sure you can prevent returning any data from unexpected queries to the user.

And even with row-level security, though, the key is that you need to treat the agent as an the agent of the lowest common denominator of the set of users that have written the various parts of content it is processing.

That would mean for support tickets, for example, that it would need to start out with no more permissions than that of the user submitting the ticket. If there's any chance that the dataset of that user contains data from e.g. users of their website, then the permissions would need to drop to no more than the intersection of the permissions of the support role and the permissions of those users.

E.g. lets say I run a website, and someone in my company submits a ticket to the effect of "why does address validation break for some of our users?" While the person submitting that ticket might be somewhat trusted, you might then run into your scenario, and the queries need to be constrained to that of the user who changed their address.

But the problem is that this needs to apply all the way until you have sanitised the data thoroughly, and in every context this data is processed. Anywhere that pulls in this user data and processes it with an LLM needs to be limited that way.

It won't help to have an agent that runs in the context of the untrusted user and returns their address unless that address is validated sufficiently well to ensure it doesn't contain instructions to the next agent, and that validation can't be run by the LLM, because then it's still prone to prompt injection attacks to make it return instructions in the "address".

I foresee a lot of money to be made in consulting on how to secure systems like this...

And a lot of bungled attempts.

Basically you have to treat every interaction in the system not just between users and LLMs, but between LLMs even if those LLMs are meant to act on behalf of different entities, and between LLMs and any data source that may contain unsanitised data, as fundamentally tainted, and not process that data by an LLM in a context where the LLM has more permissions than the permissions of the least privileged entity that has contributed to the data.
by api | 2025-07-09 11:26:59+00:00
Wasted effort reinventing things and rediscovering their limits and failure modes is a major downside of the ageism that is rampant in the industry. There is nobody around to say “actually this has been tried three times by three previous generations of devs and this is what they learned.”

Another one: WASM is a good VM spec and the VM implementations are good, but the ecosystem with its DSLs and component model is getting an over engineered complexity smell. Remind anyone of… say… J2EE? Good VM, good foundation, massive excess complexity higher up the stack.
by glaucon | 2025-07-09 11:27:06+00:00
What makes me laugh (sardonically) is that I would have hoped that, as well as considering what the costs are to the suppliers, the law might also have taken into account the size of the injury being suffered by consumers. And that if that injury was large enough then that problem should override concern the cost to the companies that have chosen to use sharp practices in maintaining their revenue flow.

Maybe you saw something in the quoted text that I didn't but I understood the USD100M to mean the costs that would arise due to companies who are currently utilising these practices stopping those practices. There's not an ongoing cost to those companies unless you call the deprivation to them of the revenue they shouldn't be receiving because their customers no longer wish to buy the service a cost.

> After all, those costs are eventually going to be passed down to consumers

And when they are the consumers will be able to stop buying off those companies, well, I mean, as long as they can cancel their subscription.
Show HN: ByteWise Search: 90% Lighter than DDG Lite – open-source Privacy Search
by FerkiHN | 2025-07-09 11:27:25+00:00
After 1 months of development, I’ve built an open source privacy-focused search engine designed for ultra-low bandwidth usage. It loads in ~200ms even on 2G networks.

Key features:

24KB initial load (DDG Lite is ~45KB)

Fully static, runs on GitHub Pages (zero-cost hosting)

Uses DuckDuckGo API with local fallback

Text-only mode (saves ~90% of traffic)

Works offline (via Service Workers)

Technical highlights:

Adaptive low-data mode (EDGE support)

Hybrid client-side caching

Category-based traffic optimization

100% client-side, no server dependencies

Would love feedback on:

Bugs or rendering issues

UI/UX suggestions or feature ideas

Additional search APIs worth integrating

Live demo: https://ferki-git-creator.github.io/bytewise-search/ GitHub: https://github.com/Ferki-git-creator/bytewise-search

Thanks for checking it out!