MurphyA/hacker-news huggingface dataset:
by neya | 2026-02-05 05:22:56+00:00
I can relate to this so much. When I was a newly joined Google consultant at a partner firm, we went to their office - some 13 different types of cuisines, different types of game rooms, lounges and what not. A luxury star hotel experience. We were waiting for our meeting on behalf of this one particularly large media client who was bleeding money on Wordpress.

3 engineers arrived - fashionably late. We explained them the situation and all we wanted from them was some GCP offering that would cure our woes and one that would cut our bills. The senior consultant - and presumably the only tech guy (rest seemed to be salesy) wasted our time like a used car salesman - he didn't even understand Google's own product portfolio and recommended us to use something like Spanner - which was totally not the solution to the problem, not to mention, expensive.

My boss and I left the meeting pissed off and he told me - "Neya, you probably know more about the product portfolio than these guys. Let's leave". That weekend, I went with my tried and trusted favorite Db - PostgreSQL - CloudSQL with a custom Elixir middleware based an old CMS I wrote a decade ago. After some trial and error, the solution worked flawlessly (and still does till date on auto-pilot). My client still has the lowest cost in the region - 1/3rd the cost of their competitors...7 years later. Back then, there was no vibe-coding, no AI, no auto-completion. Just pure thinking and experimentation.

All this just to say I agree that the new guy sometimes can make the best solutions to a problem and not always screw up. I always listen to new hires these days (now I'm a fractional / CTO) because you never know who could pull off that 1/3rd cost cutting framework move.
by iTest-NDT | 2026-02-05 05:22:56+00:00
Partner with iTest NDT for reliable, professional, and cost-effective testing and inspection services. Contact us today to learn more about how we can support your welding and inspection needs.
#we sell weld procedures #non destructive inspection #ndt testing #destructive and non destructive #pmp professional #ultrasonic testing #Third party inspection #welding inspection
by kqr | 2026-02-05 05:23:08+00:00
The reprint of the Byrne edition of Euclid is the most beautiful book I have, and I have more shelf-metres of books than I have fingers and toes. It will always have a prominent place in my home. This website day have been what got me into it -- I don't remember.

It's also fun to try to replicate the proofs!
by lfittl | 2026-02-05 05:24:11+00:00
Specifically on the cost of forking a process for each connection (vs using threads), there are active efforts to make Postgres multi-threaded.

Since Postgres is a mature project, this is a non-trivial effort. See the Postgres wiki for some context: https://wiki.postgresql.org/wiki/Multithreading

But, I'm hopeful that in 2-3 years from now, we'll see this bear fruition. The recent asynchronous read I/O improvements in Postgres 18 show that Postgres can evolve, one just needs to be patient, potentially help contribute, and find workarounds (connection pooling, in this case).
by kayleighb1 | 2026-02-05 05:24:13+00:00
SEEKING WORK

Fractional Project & Operations Manager

I help founders and teams get time back in their week by taking over the delivery and ops work that slows everything down. I plug in part-time or fractional, work fully remote, and keep execution moving so you can focus on growth and the work that actually matters.

Location: Remote

Remote: Yes (fully remote - ideal timezones APAC & Australia, can also align to Americas)

Willing to relocate: No, fully remote support only.

Technologies: Project Management, Risk Management, SailPoint IdentityNow, IAM, RBAC, Access Governance, Cybersecurity Programs, Identity Controls, Agile / Hybrid delivery, Jira, MS Office Suite, MS Projects, Confluence

Résumé/CV: Available on request

LinkedIn: https://www.linkedin.com/in/kayleigh-beahan-9b4666198/

Email: kayleighmbeahan@gmail.com
Show HN: Anoncast: Turn Blogs into Podcasts
by nbaronia | 2026-02-05 05:24:25+00:00
There are a ton of blogs I'm always meaning to read, and I never get around to them. Somehow I always have time for podcasts, though. So I built Anoncast, which goes end to end from a link to a blog post all the way to a link to a podcast episode. It's all RSS based, so anyone can view the podcast through any popular podcast viewer. Great to turn your own blogs into audio, or listen to others. https://www.anoncast.net/

The stack is pretty simple actually, mainly relying on ElevenLabs for the audio creation and then some light Cloudflare and Supabase work to actually store and propagate the files. This tool hopefully obviates the need for writers to make their own eleven labs accounts and worry about podcast tooling. I charge a small fee to cover the generation costs, but other than that listening is all free, and the generation fee is only paid once by the generator.

I'd love it if you check it out and tell me what you think!
by goosejuice | 2026-02-05 05:24:40+00:00
I agree with the sentiment about the post. I'm not a person who fills my life with busy though.

I quite like tactile buttons. That said, I've never been annoyed by my model 3s glove box, I use the pin. I have both stalks but the lack of other buttons seems just fine. I thought they did a pretty damn good job with the UX of the car beyond the auto wipers.

How often does one go in the glove box? It's so small and he center console is very spacious and more accessible. It's two quick taps on the screen for a passenger. If you wish to lock your glove box, many do, the solution is much better than a key.
by jamesgill | 2026-02-05 05:24:41+00:00
“In fact, the weight of evidence from recent large and well-controlled studies, systematic reviews, and meta-analyses of both observational studies and randomized controlled trials indicates that full-fat dairy products, particularly yogurt and cheese, do not exert the detrimental effects on insulin sensitivity, blood lipid profile, and blood pressure as previously predicted on the basis of their sodium and saturated fat contents; they do not increase cardiometabolic disease risk and may in fact protect against cardiovascular disease and type 2 diabetes.”
by lern_too_spel | 2026-02-05 05:24:51+00:00
No, it behaves like a speculative asset. The price goes up as long as the number of people who believe it will go up increases, causing more people to buy it. Once the supply of greater fools is exhausted, there is no reason for anybody to hold it because it's price isn't going up, so they sell to find something else that goes up. This causes more people to sell so they don't lose more until the price falls to the non-speculative utility of the asset, which is 0.
by burnt-resistor | 2026-02-05 05:26:04+00:00
You appear to be asking a trick question, disingenuously.

There's a vast continuum between grossly-unequal homeless everywhere like many corrupt, third-world countries with masked, paramilitary disappearance squads and a large, happy middle-class paid well that can afford to buy things, take vacations, and enjoy life where corruption is lesser.
by seanhunter | 2026-02-05 05:26:38+00:00
If a loan is supported by a known lease it is more attractive to investors than a regular loan, so I somewhat doubt they are thinking about it like this.

The real reason they will be doing this is this is what they do in general. They don’t hold on to huge amounts of risk with predictable returns (because it consumes their operating and regulatory risk capital inefficiently) they will instead find buyers for that risk, which frees up capital they can then use on their next thing. That basically gives up some of the long term, low return, low volatility risk for shorter term, higher return, higher volatility risk.
by larusso | 2026-02-05 05:26:51+00:00
Also in the good old days if you sealed the wrong number you had some time to just hang up without harm done. Today the connection is made the moment you pressed the button or in this case when Siri decided to call.

Happened to me too while being in the car. With every message written by Siri it feels like you need to confirm 2 or 3 times (I think it is only once but again) but it calls happily people from your phone book.
by bigstrat2003 | 2026-02-05 05:27:06+00:00
> Ageism is just a dick move in general.

It's also self-defeating. Yes, there are greybeards who are stuck in their ways and refuse to learn anything new. But more often than not, the greybeards are super good team members in ways that the younger employees can't hope to compete with, because all that experience has taught them a ton about what works and what doesn't. But rather than trying to harness that valuable knowledge, companies shoot themselves in the foot by ignoring it. It's ridiculous.
by nilkn | 2026-02-05 05:28:24+00:00
My read:

Sam's goal is to create viral products. This has always been his goal. While his interest in and passion for AI are almost certainly genuine, he famously hedged his bets before committing to OpenAI up to the point of being ambiguously fired from his previous job. ChatGPT was one of the greatest viral products of all time. His subsequent attempts to create virality haven't been working in any real, durable way.

Enter Claude Code. It went viral, not in the awe-inspiring world-changing way that ChatGPT did, but in a way that allowed it to decisively overwhelm OpenAI's advantage in some very valuable niches. It wasn't born out of a search for a viral product, but rather out of an intellectual obsession with safe, steerable AI systems -- an obsession that could've just as easily ended up producing no products at all. It's the kind of obsession that can't be replicated if the only motive is virality.

So yeah, this is going to bother him a lot. He's defending ads while his competitor's product is having its "iPhone moment." You know this is part of the raw emotional driver because he ends his defense of ads by talking about Codex app downloads and saying he "believe[s] Codex is going to win," implying that significant doubt exists that he feels the need to correct.
We built a serverless GPU inference platform with predictable latency
by QubridAI | 2026-02-05 05:29:02+00:00
We’ve been working on a GPU-first inference platform focused on predictable latency and cost control for production AI workloads.

Some of the engineering problems we ran into:

- GPU cold starts and queue scheduling
- Multi-tenant isolation without wasting VRAM
- Model loading vs container loading tradeoffs
- Batch vs real-time inference routing
- Handling burst workloads without long-term GPU reservation
- Cost predictability vs autoscaling behavior

We wrote up the architecture decisions, what failed, and what worked.

Happy to answer technical questions - especially around GPU scheduling, inference optimization, and workload isolation.
by seanhunter | 2026-02-05 05:29:45+00:00
That’s exactly the same as going into a furniture shop and going “if this furniture was so good, then why would they want to sell it so badly”. They’re a furniture shop - they make and sell furniture. There’s only so much furniture you need for yourself after all no matter how good it is.

Investment banks make investment products for investors. They do keep risk for themselves so you will find when they sell these loans they will often keep a slice, but they only need so much Oracle datacenter loan risk - they want to have free capital to find other opportunities to fund.
by junaid_97 | 2026-02-05 05:29:52+00:00
This is not the ideal solution, I know. But, this is what I do:

- I own a Kindle. I also have the Kindle chrome extension.
- Anytime I came across an interesting article/blog, I use the extension and send the article to my kindle
- Pro: I end up actually reading the articles
- Con: My library is filled with hundreds of articles
by aspectrr | 2026-02-05 05:29:55+00:00
Yo, fluid is built with on-prem in mind, specifically VMs. This is my initial use case for it. I am currently working on a remote version of fluid, where instead of CLI tool, it would be more of a codex/claude code app with a UI where you can install a server and then command hundreds of agents at once to work on infrastructure. Is this what you had in mind?
by tim-tday | 2026-02-05 05:30:21+00:00
They probably mean leaving ssh open to all ips. Take a look at your auth failure logs to see the thousands of daily attempts to compromise your server using default passwords. Most of those are low effort and low risk. Sometimes the bots will try password stuffing. Disabling password auth in sshd config is good practice.
Fail2ban also helps block repeated attempts like that.

There’s also the risk of a zero day RCE vulnerability in ssh (though I’ve not seen one in the 20 years I’ve been paying attention )

I tend to not expose ssh to the world and log in with some other method to pass the perimeter (VPN, IP whitelist, tailscale) and the ssh from inside.
by Groxx | 2026-02-05 05:30:34+00:00
SSH in and you have access to basically everything. The stock setup has two partitions for the OS (it toggles between them when you update, or toggles back if it fails to boot a few times) so you can:

Dual boot (disable updates and install any two you like): https://remarkable.guide/tech/dualboot.html

Some lower level details here: https://github.com/ddvk/remarkable-hacks/issues/304

And installing a specific release is largely automated: https://github.com/ddvk/remarkable-update

Last time I did it, I just did it manually - back up the OS version you want over ssh, then restore it whenever you want (on the non-active partition). And screwed it up the first time, and had to do a recovery: https://github.com/ddvk/remarkable2-recovery (requires using the contact pads on the spine for USB access - not too hard to solder up a pogo pin thing, but might take some time to get the parts).

So I'd recommend the automated way, though I haven't tried it yet :)

There's a (single) relatively active discord server if you want specific Q&As with other people too, or to double check whatever the current recommendations are (probably do that, as I'm somewhat out of date): https://discord.com/invite/nQ6nHwfDfc

And do definitely back up your data partition before making any major version movements tho, in case something doesn't work right and you need to roll back. I forget if/when that's necessary, but it's a good safety net just in case. And <8GB isn't much to store just in case.
MLM Software Development
by sonniya | 2026-02-05 05:30:44+00:00
An MLM software development company delivers powerful digital solutions for direct selling and network marketing businesses. It designs customized platforms with automated commission calculations, genealogy tracking, e-wallets, and analytics. By focusing on scalability, security, and ease of use, these companies help MLM organizations streamline operations and improve distributor engagement. A strong MLM software system reduces manual work, increases transparency, and supports long-term business growth in an ever-evolving market.
by mym1990 | 2026-02-05 05:30:46+00:00
The "service" part can still come from internal sources. Plenty of companies have internal support for internal tooling. With a good foundation of infrastructure and a lean team that knows how to build, not just vibe code, there is most definitely some ROI there.

But yes, this brings us back to the point that simply building the tool is only a small part of the process...and it has often been one of the most expensive parts of the process.
Ask HN: Is OpenAPI enough for LLM-based API integrations?
by chilarai | 2026-02-05 05:31:36+00:00
We've been running into a recurring issue while using LLMs (Cursor, agents, etc.) to build real API integrations.

OpenAPI is excellent at describing request/response shape, but it doesn't capture execution semantics that matter in production, such as:
- retries and backoff rules
- idempotency guarantees
- auth and token refresh behavior
- SDK-specific constraints
- "what must not be done" during execution

In addition, large OpenAPI specs tend to be hard for LLMs to consume incrementally: they don't chunk cleanly by operation or behavior, and important constraints get lost when context is truncated.

We've open-sourced an experiment called "Wreken spec": a small, explicit file that lives alongside OpenAPI / SDKs and encodes execution rules and constraints in a way that's intentionally:
- operation-scoped
- chunkable / retrievable independently
- designed for machines (LLMs), not humans

This is very early, and we're not confident this is the right abstraction.

We'd love feedback on:
- whether this should exist as a separate file at all
- if this belongs as OpenAPI extensions instead
- whether we're reinventing something that already exists
- failure modes or scaling issues we may be overlooking

Spec + examples:
https://gitlab.com/swytchcode/wrekenfile

Context / motivation:
https://wreken.com

Genuinely looking for critique—happy to be told this is the wrong direction.
by usernomdeguerre | 2026-02-05 05:33:24+00:00
> ICE says it is attempting to better understand how commercial big data providers and advertising technology firms might directly support investigative activities, while remaining sensitive to “regulatory constraints and privacy expectations.”

That's rich and i'll believe it when they respect the written law.

To be clear, I fully expect other departments have been investigating these sorts of things in past and present, but ice have conducted themselves differently now and should be treated accordingly.
by featherlark | 2026-02-05 05:34:39+00:00
Honestly, I'm surprised by how people are pushing back against this idea. I feel like vibe coding is just in its earliest moments of actual viability, and my mind is totally blown by it, and it strikes me that it's exactly what I've always wished software could be. Plastic, flexible, personalized, effective, responsive, organic.

As an anecdote, I've been vibe coding an accounting system that perfectly matches with my own expectations of accounting software, i.e., it's intimately connected to CSVs, imports and exports from CSVs, but acts as a kind of enrichment and reporting and file association layer. If there was anything like this, any kind of SaaS that I could have and download as software and run on my own computer offline and be able to inspect and trust and version control so they wouldn't add or remove some kind of feature that I wanted down the line, then I would have gone with that.

But now I have essentially my absolute ideal solution, written with a Python backend and Vue and JavaScript frontend, and it's radically improved my ability to maintain accounting for our business account.

And I think there's something really important to point out here, which is that the feeling of lock-in is very seriously reduced when you are Vibe coding your own software, because if you don't like the way that it works or you realize that there's something missing, you can add it pretty painlessly. Like, that's always been a huge challenge with choosing vendors for a SaaS platform, is you think, oh no, well, what if their conceptual model for what I'm trying to do doesn't quite map onto our own internal systems or understanding of what's being done? Well, when you have your own Vibe-coded SaaS, you can just add that information. So there's something incredibly organic about it. I used to work at a startup in Redmond where we built this large internal system to manage a scientific process with lots of machinery and data, and it was incredibly empowering and actually became one of the core values of the business that was able to be licensed to other businesses in the same industry. And it seems like we're just improving that capacity from here.

Now obviously, if Vibe Coding magically were to go away or became much more expensive, then I'd have this legacy piece of software, which I couldn't improve, and that would be a dead end. But my expectation is that the functionality that we have today will only improve. And in several years, the scope of changes that I'll be able to make, the level of professionalism, modularization, maintainability, code quality, will only improve. And so this has me thinking in general that software is kind of undergoing a step change where we're moving into the so-called age of intent beyond the age of the interface. And that's tremendously exciting to me, and I just couldn't be more stoked about it.
by rl3 | 2026-02-05 05:35:31+00:00
>One authoritarian company won't get us there on their own, to say nothing of the other obvious risks. It is a dark path.

It warms my heart to hear that Sam is against authoritarianism. Hopefully he doesn't hang out with anyone that supports that kind of thing.

https://www.wsj.com/tech/ai/the-real-story-behind-sam-altman...
by rswail | 2026-02-05 05:35:42+00:00
How does this compare to Entity Framework (for dotnet) migrations or sqitch/liquibase.

I get the declarative nature of this, but migration of schemas is not purely declarative, particular on large production databases. An ideal schema manager would understand the costs of particular migrations (perhaps by using the table stats and EXPLAIN) and apply that back to the migration strategies so that downtime is minimized/eliminated.

Adding or remove columns or indexes can trigger major database table scans and other problems, especially when partitioning conditions change.
by gg582 | 2026-02-05 05:36:08+00:00
I believe the problem with Debian and many open source projects is that communities outside the US, Greater China, India, and some advanced European countries are relatively weak, making it difficult for project leader-level figures to emerge. I was born and raised in South Korea, a virtual open-source wasteland. Listening to testimonies from developers working here, many say, “I was captivated by the GNU spirit and wanted to contribute, but the Korean community's operations were poor, and clique-based territorialism was severe.” Ultimately, many open-source projects paradoxically miss out precisely because of their idealism and open management culture. I'd like to summarize it this way:

- Combining open source developers outside the core development regions and major cultural spheres could potentially secure roughly as many contributors as the entire US.
- Funding shortages for non-profit foundations are deeply entrenched. Denying or attempting to fix this immediately becomes greed.
- It is possible to manage language barriers, cultural barriers, and guidelines for distant countries without becoming a greedy for-profit entity.
- This does not mean holding DebConf in every country. However, if the awareness is simply that ‘there used to be no borders, but now it's different from the 90s’ regarding the shortage of personnel, then improvements should be more proactive.
- The 2020s are no longer an era of romanticism where one flies from Angola to Germany just for the sake of romance.
- Especially as Debian has established itself as an invisible system, becoming the backbone of countless cloud services, there is less room for romanticism to intervene.

I've used Debian since 2015 and have had no complaints during that time. Korea also had ‘administrators’ who spared no expense on plane tickets for GNU since the 90s, but most have now stepped down due to age, or, exhausted from trying to salvage communities torn apart by toxic members, have turned around and declared ‘BSD was right’. However, the project's sustainability deteriorating due to a ‘lack of administrators’ is definitely something that needs to be considered. If sufficient people cannot be recruited, and given that we cannot extend the freeze cycle like Slackware at present, communication between upstream and downstream and the active recruitment of multinational developers are important to resolve the complaints of ‘dependent families’ like Ubuntu.