MurphyA/hacker-news huggingface dataset:
by voxleone | 2025-07-09 12:32:20+00:00
>Fundamentally new paradigm and tech the world will have to adapt to? Not hype at all.

I generally agree with your statements. But i personally tend to think of of the various ML flavors as only a natural evolution of the same Turing/von Neumann paradigms. Neural networks simulate aspects of cognition but don’t redefine the computation model. They are vectorized functions, optimized using classical gradient descent on finite machines.

Training and inference pipelines are composed of matrix multiplications, activation functions, and classical control flow—all fully describable by conventional programming languages and Turing Machines. AI, no matter how sophisticated, does not violate or transcend this model. In fact, LLMs like ChatGPT are fully emulatable by Turing machines given sufficient memory and time.

(*) Not playing the curmudgeon here, mind you, only trying to keep the perspective, as hype around "AI" often blurs the distinction between paradigm and application.
by westpfelia | 2025-07-09 12:33:15+00:00
SO you can do what I'm currently doing because I'm in the middle of moving countries and my desktop isnt here!

I have a monitor i'm borrowing from work, a mouse, keyboard, and the steamdeck Dock. And I just treat it like a desktop. You can still easily use steam big picture mode. OR you can boot to desktop, as the Steamdeck is just a Arch linux install. Its honestly amazing.
by jeroenhd | 2025-07-09 12:34:05+00:00
I don't know if there's an MQTT bridge yet. Generally, you run some kind of border router and connect through that. While the work doesn't seem complete yet, there's a guide to turn a Home Assistant install into a Thread border router if you have the necessary hardware: https://www.home-assistant.io/integrations/thread/#turning-h...

You can probably plumb Home Assistant into your MQTT server from there.
Show HN: AI Agent for ESG analysis
by martianmanhunt | 2025-07-09 12:35:09+00:00
We are developing agents for doing ESG analysis at scale. For this prototype, we looked at the use case of finding GHG emissions numbers for companies from their corporate websites, which takes a long time due to the large size of the documents when done manually.

Please try a few companies and keen to get some response. You can also click on the numbers and see where the information came from, down to the page of the docs.

Some things we are working on: 1. Robust downloads from companies who actively prevent downloads like Tesla and Saudi Aramco 2. Expanding this to be more general purpose where the user can specify which metrics they want to extract.

Thanks! @MartianMan
by claytongulick | 2025-07-09 12:36:42+00:00
Did you read TFA? This had nothing to do with neoliberalism or whatever.

Everyone agreed with the spirit of the rule, even the two republican appointees who voted against it.

They voted against it because the FTC cheated and broke their own rule making process, they believed it would be struck down by the courts because of this.

They were right. The courts sympathized with the rule, but held that the FTC cheated it's process, and that if left unchecked it could create a tyrannical FTC issuing rules at their whim, ignoring the true economic impact of their rule.

All this court ruling said is that the FTC needs to follow the law and their own defined process for rule making.

They are free to implement this rule, they just need to do it the right way.

While we may not be happy with the short term effect, this was a good ruling. The FTC will go back and do this properly, and hopefully next time will follow the law when making rules.
by tgv | 2025-07-09 12:36:44+00:00
Do you care? From my point of view, post, put, delete, update, and patch all do the same. I would argue that if there is a difference, making the distinction in the url instead of the request method makes it easier to search code and log. And what's the correct verb anyway?

So that's an argument that there may be too many request methods, but you could also argue there aren't enough. But then standardization becomes an absolute mess.

So I say: GET or POST.
by rubyfan | 2025-07-09 12:36:45+00:00
I really appreciate that innovation can sometimes reinvent things that exist out of pure ignorance and sometimes hubris. I’ve seen people turn mountains out of molehills that take on a lore of their own and then along comes someone new who doesn’t know or is a little too sure of themselves and suddenly the problem is solved with something seemingly obvious.

I’m not sure javascript islands is that but I appreciate a new approach to an old pattern.
by Someone1234 | 2025-07-09 12:38:21+00:00
I believe the point is: "WHO is responsible when the user uses this technology incorrectly?"

OP's position is that someone else should reimburse them for their own errors. Are you siding with the OP and suggesting that if a lawyer, doctor, or teacher misused the technology that they too shouldn't be responsible for it?

Because that's the crux of this. Responsibility.
by mutant | 2025-07-09 12:39:33+00:00
This is clearly related to the Zephyrix protocol stack running on distributed Quantum-Lambda nodes. The issue stems from improper configuration of the Nebulon cache invalidation subsystem. When you have a TangoBar instance (notice the camelCase - it’s actually “TangoBar”, not “Tangabar”), it relies heavily on the Vectorized Flux Capacitor Arrays (VFCAs) for handling cross-dimensional data persistence. The problem occurs when the Heisenberg Uncertainty Buffers overflow due to insufficient Qubit-Mesh bandwidth allocation. You’ll need to: 1. Recalibrate your Chronosync Distributors to handle the increased temporal load 2. Upgrade your Metamorphic Storage Engines to at least version 7.2.1-alpha 3. Implement proper Fractal Sharding across your Hypercube Infrastructure The root cause is usually in the Entropic Reconciliation Layer - it’s not properly handling the cascade failures when the Fibonacci Load Balancers hit their theoretical limits during peak Wormhole Traversal periods. I’ve seen this exact pattern in production at three different companies running large-scale Paradox Processing Clusters. The fix involves patching the Quantum State Serializers and adding additional Dimensional Boundary Checks to prevent data leakage between parallel universes. Hope this helps! Let me know if you need the specific config files for the Multiversal Gateway Settings.
by ticulatedspline | 2025-07-09 12:39:48+00:00
Reminds me of those "Your GPS is wrong" signs that would pop up in some places in the early days of GPS, often somewhere you clearly shouldn't be driving if you were paying attention.

Seems like sites and services will start needing "Your LLM is wrong" banners on websites when they start consistently hallucinating features that don't exist.
by DrillShopper | 2025-07-09 12:39:53+00:00
Their corporate support is a joke.

When we bring a problem to them, which we pay them for, the turn around time is awful, and about 2/5 cases I end up having to break out the debugging tools and root cause/fix fix it because their support engineers can't be bothered.

Especially their nVidia support. Worse than useless.
by motorest | 2025-07-09 12:40:03+00:00
> So the lack of "HATEOaS" hasn't even been noticable for me.

I think HATEOAS tackles problems such as API versioning, service discovery, and state management in thin clients. API versioning is trivial to manage with sound API Management policies, and the remaining problems aren't really experienced by anyone. So you end up having to go way out of your way to benefit from HATEOAS, and you require more complexity both on clients and services.

In the end it's a solution searching for problems, and no one has those problems.
by simonw | 2025-07-09 12:40:04+00:00
Giving read access to only the people who should have read access doesn't solve the problem here.

The vulnerability is when people who should have read access to the database delegate their permission to an LLM tool which may get confused by malicious instructions it encounters and leak the data.

If the LLM tool doesn't have a way to leak that data, there's no problem.

But this is MCP, so the risk here is that the user will add another, separate MCP tools (like a fetch web content tool) that can act as an exfiltration vector.
by diggan | 2025-07-09 12:40:05+00:00
> build a website or web app (or both) as a single, cohesive unit, covering both front-end and back-end, while avoiding the hydration performance hit.

Isn't that basically just what Symfony + Twig does? Server-side rendering, and you can put JS in there if you want to. Example template:

<html> <head>[...]</head> <body> {% if user.isLoggedIn %} Hello {{ user.name }}! {% endif %} </body> </html>

The syntax is horrible, and seeing it today almost gives me the yuckies, but seems like the same idea to me, just different syntax more or less. I'm not saying it was better back then, just seems like very similar ideas (which isn't necessarily bad either)
by nchmy | 2025-07-09 12:41:31+00:00
> Instead you get this snarky blog post telling people that they are doing REST wrong, rather than pointing out that REST is something almost nobody needs (self discoverable APIs intended for evolvable clients).

Were using actual REST right now. That's what SSR html uses.

The rest of your (vastly snarkier) diatribe can be ignored.

And, yet, you then said the following, which seems to contradict the rest of what you said before it...

> Bangs head at desk over and over and over. A webapp that is using HTML and JS downloaded from the server is following the spirit of HATEOAS. The client evolves with the server. That's the entire point of REST and HATEOAS.
Show HN: GrowIn – AI assistant to automate your LinkedIn content and growth
by lapomascheri | 2025-07-09 12:41:39+00:00
Hey HN, We’re a small team of three from Italy, Gabriele Dalla Costa (founder of Eneox), Luca Rossit (marketing + UX), and myself, Lapo Mascheri (product & R&D). We’re young, a bit obsessed with building, and have been working between H-Farm College (Italy’s first innovation hub) and a LinkedIn agency we helped grow from scratch.

Here’s the story:

For the last 6+ months, we’ve been building a tool called GrowIn. It started with a simple question we couldn’t shake off:

“Why is building a strong LinkedIn presence so time-consuming, even for the people who know what they’re doing?”

We saw it with our clients, with freelancers, and even with ourselves. You get excited, post a few times, maybe see results. Then things change. You shift focus, your goals evolve, and suddenly LinkedIn becomes another source of pressure. What to post? What’s working? Should I even be doing this?

So we built GrowIn, not as another “scheduler” or “post generator,” but as a real AI assistant for personal branding. Something that understands your goals, your tone of voice, your context, and helps you keep growing, even when your direction shifts.

GrowIn is part strategist, part writer, part analyst:

• It learns your voice through a simple onboarding • It suggests what to talk about (based on your goals + real-time trends) • It writes and formats your posts in your tone • It helps schedule and manage them • It tracks your progress, engagement, and even competitors • It gives you insight on what’s working and what’s not, without overwhelming you with dashboards

We’ve been testing GrowIn with a few hundred people, but today we’re opening it up to this community because we know what HN brings:

direct, honest, no-bullshit feedback from people who build, question, and think.

We’d love to know:

• Does this solve a real problem for you? • What’s useful, and what just adds noise? • Would you trust a tool like this with your voice? • What would you build next on top of it?

You can try it now , fully open: https://growin-staging-54fbd516bc2d.herokuapp.com/

Here also an introduttive and onboarding video: https://public.3.basecamp.com/p/U5bXrWMZUHRQoZ2PjX396H6Q

If you like what you see, or even
by thedougd | 2025-07-09 12:41:58+00:00
The thread border gateway (Apple TV, HomePod, Google Nest Speaker, etc) sends an IPv6 router advertisement to the network for the Thread IP space. Multiple border gateways can advertise the same IP space for redundancy.

I have/had a segmented network, so I made sure my router accepted this route so that devices on different networks could communicate with the Thread devices. It worked, usually. However, I ran into some challenges with the reliability of communicating from my phone to various devices. I never quite got mDNS reflection 100% correct, and I strongly suspect that's my problem. If you look at an mDNS entry for a device, you'll see some advertise all their IPv6 addresses including link local (fe80::). I suspected some clients were dumb, trying the first IP they found, and giving up when it didn't work. I was working on modifying the golang mdns-reflector project to filter these entries. I had some success, but I haven't finished.
by diggan | 2025-07-09 12:42:05+00:00
> but your progressively-enhanced client-side logic (i.e. JS) still wasn't necessarily easy to debug, let alone being able to write unit tests for them

True, don't remember doing much unit testing of JavaScript at that point. Even with BackboneJS and RequireJS, manual testing was pretty much the approach, trying to make it easy to repeat things with temporary dev UIs and such, that were commented out before deploying (FTPing). Probably not until AngularJS v1 came around, with Miško spreading the gospel of testing for frontend applications, together with Karma and PhantomJS, did it feel like the ecosystem started to pick up on testing.
Show HN: I built "Schnippi", my dream screenshot Chrome extension
by sagering | 2025-07-09 12:43:20+00:00
Hi HN,

I've built my dream Chrome screenshot extension, "Schnippi," a combination of features I couldn't find in any other extension.

Features include:

- Optimized for Speed: Reduce the number of key presses or clicks to capture and export (download/copy) a screenshot. With one key press and one click, you'll have a screenshot in your clipboard or download folder.

- Flexible Capture and Selection: Capture any visible HTML element and cycle through the element hierarchy to refine your selection. You can also capture a free-form rectangle or the full viewport.

- Source URL Inclusion: Export your screenshot with the source URL of the captured page.

- Multiple Export Options: Copy to clipboard or download in various formats.

- Zoom-Friendly: Works well with "zoomed-in" pages.

- Privacy-Focused: No server uploads of your screenshots or any data collection.

- Clean UI: Neutral and minimal graphical user interface.

It's completely free! You can try it out here: https://chromewebstore.google.com/detail/schnippi-screenshot...

Why Screenshots Are Great:

- Speed: Unless it's raw text, taking a screenshot is often the fastest way to capture information or data from a website.

- Context: Screenshots can provide essential context around the captured data.

- Universal Format: Most word processors, note-taking apps, email clients, LLM chats, and search engines support image input.

A Problem Schnippi Solves:

An issue with just a PNG file of a screenshot is that an important piece of information is lost: the URL of the captured page. It's like a citation without a source. A screenshot without the page URL is often not very valuable, as you can't easily get back to the page to verify information or learn more about the context.

To fix this, Schnippi allows you to "Copy as HTML," which includes both the URL of the captured page and the image PNG. Many apps support this format, including Google Docs, Gmail, Apple Notes, Pages, Microsoft OneNote, and Word, among others.

How I Use Schnippi:

- For any kind of research or collecting visual inspiration for a project.

- Taking a screenshot of a data graph to share with a colleague. With "Copy as HTML" I don't need to copy the link to the page separately.

- Capture and copy a screenshot from the clipboard to a search engine / llm chat.

- Note down a piece of information including the source URL.

What's next:

I am planning to add the option to annotate the screenshot with text and shapes like arrows, rectangle or circles.

I'd be happy to hear your feedback! Thanks!
by stego-tech | 2025-07-09 12:43:26+00:00
This. The network fragmentation is the point, just like how some businesses would run IPX internally and use a proxy for web/IP traffic to protect corporate infrastructure from malicious devices or software.

Not everything has to be on TCP/IP. For smart home connectivity, I’d say that’s a feature, provided said networking standard is just as open as TCP/IP.
by PeterStuer | 2025-07-09 12:43:31+00:00
I think the missing link here is the Notion MCP server (currently in Beta)

https://github.com/makenotion/notion-mcp-server

Just follow the first link in the Readme or the Beta Overview link Developer docs ( https://developers.notion.com/docs/mcp ) as I am apparently not allowed to link that document ("You are invited to participate in our Beta program for Notion MCP. This page explains the new features and how to get started. The contents of this page are confidential. Please don’t share or distribute this page") even though it is linked all over the place from other public non confidential Notion pages.
by ozgung | 2025-07-09 12:43:42+00:00
Same in Turkey. We say Milliard instead of Billion. In my childhood I can swear it was like Million->Milliard->Trillion->Trilliard. They were in daily language because 1 Million Turkish Lira was like a few dollars. At some point they decided Trilliard does not exist and it became something like a Mandela Effect for me. We never used Billion though.
by llm_nerd | 2025-07-09 12:43:53+00:00
I'm not advocating against using vectorization/SIMD. Of course people should eek every bit of performance out.

The point is that the average developers job in achieving this is not knowing every SIMD primitive for every platform. It is almost always folly to ever touch a platform's SIMD instructions unless you're one of the aforementioned library/compiler developers.

Instead the ordinary developer is usually best served by using equipped libraries and understand how to structure code where it can enable vectorization. Whether it's Eigen, or even the C++ compiler (which, in my experience, is often excellent at vectorizing code), or the Accelerate library on Apple platforms. These things mean that your code can adapt and exploit every possible platform they're deployed to, versus Jimmy SIMD who carefully made his SSE 3.2 instructions and his code was then lost in time.
by teekoiv | 2025-07-09 12:45:00+00:00
It doesn't. Those are executed build-time and you can't just set a wildcard so anything outside the given set results in 404.

As background, I wanted to make a PoC with NextJS bundled into a static CapacitorJS app somewhat recently and had to give up because of this.

You can try tricking NextJS by transforming the pages into "normal" ones with eg query parameters instead of path, but then you need complicated logic changing the pages as well as rewriting links. As you of course want the normal routes in web app. Just a huge PITA.
by recursivedoubts | 2025-07-09 12:45:18+00:00
This is a very good and detailed review of the concepts of REST, kudos to the author.

One additional point I would add is that making use of the REST-ful/HATEOAS pattern (in the original sense) requires a conforming client to make the juice worth the squeeze:

https://htmx.org/essays/hypermedia-clients

https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans
by snowwrestler | 2025-07-09 12:45:26+00:00
Fundamentally this article is reasoning in units of “companies,” but the story is different when reasoning in terms of people.

It turns out automobile companies need way more employees than carriage companies, so the net impact on employment was positive. Then add in all the jobs around automobiles like oil, refining, fueling, repair, road construction, etc.

Do we care if companies put each other out of business via innovation? On the whole, not really. People who study economics largely consider it a positive: “creative destruction.”

The real question of LLM AI is whether it will have a net negative impact on total employment. If so, it would be the first major human technology in history to do that. In the long run I hope it does, because the human population will soon level off. If we want to keep economic growth and standards of living, we will need major advances in productivity.
by quitit | 2025-07-09 12:45:30+00:00
This is one of the reasons why providers -hate- IAP subscriptions, even if the profit share was 0%, they'd still not be happy because with IAP it's just one click to cancel.

It's not even a practice limited to "shady" companies, the New York Times would let you sign up online, but only cancel via a convoluted phone call with one of their subscription retainment reps.

These days you're better off obtaining a credit card which lets you instantly block transactions. These companies with their b/s unsubscribe gauntlets aren't worth your time.
by K0balt | 2025-07-09 12:46:11+00:00
There is a fallacy in over application of the survivorship bias concept.

Literal survival for early cultures was often a matter of luck. Agriculture was an innovation that improved the odds. Early cultures that practiced agriculture outperformed those that did not, and were more likely to survive black swan events. All major cultures in existence are now based in agriculture.

Should we assume then that because we only see agrarian cultures that that is not useful information, because of survivorship bias in the resulting sample?

On the contrary, survival itself is the signal that is useful… it’s really a matter of what behavior the signal can be attributed to- was it the agriculture, or was it the human sacrifices? Was it the red ochre face paint? The storing of grain in pots instead of skins?

Failure bias is just as large of a red herring. It’s easy to imagine that it retrospect, we understand why failures happen, and sometimes the reasons are very clear. That’s why there is often more to be learned from failures than from successes. But still, it’s easy to look at the things they did right that successful example B also did, and then conclude those things weren’t critical to success because they sometimes end in failure.

The point is that we shouldn’t judge the value of information based on ideas like “survivor bias” but instead look for more methodical and logical connections between causes and outcomes, and not fall victim to cargo-culting nor casual, hand wavey dismissal of potential lessons.

Survivorship bias mitigation is a matter of determining which survivor signals are instrumental , and those which are coincidental.

Many things are fraught with risk and low probabilities of success. That does not make them primarily a matter of luck.

Aviation is a great example of an environment that is nearly 100 percent risk, where without knowledge and the correct tools the very small chance of not dying would be purely a matter of luck.
by alok-g | 2025-07-09 12:46:20+00:00
Semantics aside, I am not proposing choosing natural (say what evolution chose pre-humans) definitions. However, defining the specifics for what is considered as fit and unfit is indeed the key question. The point I am making is that this has not been done thoughtfully, most leaders and lawmakers do not have a good understanding of this (but they are in position of power anyways).