MurphyA/hacker-news huggingface dataset:
by jmathai | 2026-02-05 05:03:09+00:00
It’s great advice.

If you can be intentional going in to a conversation then I think the chances to serving the other person through listening becomes much higher.

It’s truly a gift…offering someone your time and attention. Possibly the most valuable gift you can give - I don’t mean that facetiously.

The Gottmans talk about bids for attention. It’s random comments inviting the other person to engage.

This sounds really similar.
by gwking | 2026-02-05 05:03:43+00:00
I wrote a very rudimentary schema and automatic migration system for SQLite. One problem that I ran into recently was deploying changes that spanned two migrations, because the tool doesn’t know how to step through commits to do successive auto-migrations between schema versions. I guess there are rather obvious ways to handle this if you generate and then commit the full migration sql for each schema change. Nonetheless I’m curious if this is a problem you have had to think about, if you find it interesting or if it sounds like a bad path to go down, and if atlas does anything smart in this department. Thanks in advance!
by exodust | 2026-02-05 05:03:45+00:00
> How about you come back when your daughter has a fake AI nude passed around school.

Like any bad behaviour, the grown-up response should be discipline and education.

There's a million ways kids can misbehave. The idea is to get kids ready for the real world, not pretend there's nothing bad out there.

Obviously we don't want "point and click" AI nudes in the hands of minors, or kids having their own AI accounts in the first place. Parents and educators pay for their kid's devices and internet connections. If they're not being responsible, you take away the privilege until they learn about respectful behaviour.

If the kid is allowed to stay out after dark but ends up doing crime at those times, we don't ask the government to impose a curfew on every kid. We discipline the kids involved. And that's my last comment in this thread thank God, what a struggle.
by what | 2026-02-05 05:05:21+00:00
Again, you still have to put in way more work. You have to somehow know the weight of the container, otherwise it will never register as empty. Or you have to know the volume and the density of its contents (or worse, think about a jar of olives or pickles, how would a weight tell you it’s empty with the brine in there?). You still don’t know the expiry date. There’s no chance of automatically tracking this stuff.
by seanhunter | 2026-02-05 05:06:48+00:00
It’s two sentences for goodness sake. Why on earth should anyone spend their time reading your “thoughts” when you don’t think it’s worth spending your time to write them?

More substantively, I don’t believe it is true, but hypothetically why would “the real” problem be having 100 distros on distrowatch with little to choose between them? The benefit of open source for the individual is supposed to be the opportunity to learn by doing and to have the freedom to do things however you want, and the benefit to the community is this extreme Darwinian process where lots of crazy people try all sorts of things and the community as a whole picks results they like. All of these benefits arise precisely because there are a lot of projects, many of which don’t achieve mass adoption.
by omneity | 2026-02-05 05:07:23+00:00
It’s a trivial calculation to make (+/- 10%).

Number of params == “variables” in memory

VRAM footprint ~= number of params * size of a param

A 4B model at 8 bits will result in 4GB vram give or take, same as params. At 4 bits ~= 2GB and so on. Kimi is about 512GB at 4 bits.
by gsf_emergency_6 | 2026-02-05 05:07:35+00:00
Short answer is no.

(Your two Cat's are presumably, "listenable now" and "listenable later"?)

Mid-answer is.. (depending on how _useful_ it appears to be ;) I'll find out which case(s) from Mumonkan that was soon enough..

Btw, Hiroyuki concluding "1% Perspiration" (apologetic to Edison?), calls himself "Ronin".. so.. Takuan or Musashi?

https://youtu.be/SoHxYBMuegE?t=2m09s

Ps: "weaponized kernel-bugs" (personal translation from preface:)
by EGreg | 2026-02-05 05:08:52+00:00
That’s exactly what Vladimir Feltsman said about me when I was like 8 LOL. He is on video here saying it… “I want him to start playing concerts 3-4 years later but be in business 40 years longer!”

https://youtu.be/lf2DWzQ-5zk

Spoiler: I got into computers as a teenager and my piano career took a nosedive, from Carnegie Hall and Juilliard to like… playing for friends at a house party :)
by rl3 | 2026-02-05 05:08:59+00:00
Best practices usually call for not exposing the SSH endpoints to the public internet. The principal risk is vulnerabilities in the underlying SSH server implementation. Historically, critical flaws that can compromise you are few and far between. However, these days AI is already starting to become adept at reverse engineering.

If you must, you'd typically use a bastion host that's configured just for the purpose of handing inbound SSH connections, and is locked down to a maximal degree. It then routes SSH traffic to your other machines internally.

I'd argue that model is outdated though, and the prevailing preference is putting SSH behind the firewall on internal networks. Think Wireguard, Tailscale, service meshes, and so on.

With AWS, restricting SSH ports via security groups to just your IP is simple and goes a long way.
by burnt-resistor | 2026-02-05 05:10:03+00:00
> It made sense in an age of print.

Reading books is still important. That has nothing to do with the CIA factbook website edition.

Archiving copies of internet-published information is important, especially when a regime lies, tries to rewrite history, and destroys knowledge and public resources regularly.

> So let's just cherish it as another print tradition that would inevitably end

Self-fulfilling prophecy, learned-helplessness doomer fallacy. It only ended because some assholes ended it.
by pmontra | 2026-02-05 05:10:11+00:00
The article is very well written but is somewhat lacking at the end.

The conclusion lists pgbouncer as one of the solutions but it does not explain it clearly.

> Many pieces of wisdom in the engineering zeitgeist are well preached but poorly understood. Postgres connection pooling falls neatly into this category. In this expedition we found one of the underlying reasons that connection pooling is so widely deployed on postgres systems running at scale. [...] an artificial constraint that has warped the shape of the developer ecosystem (RDS Proxy, pgbouncer, pgcat, etc) around it.

The artificial constraint is the single core nature of postmaster.

Other points at the end of the article that can be improved:

> we can mechnically reason about a solution.

Mechanically as in letting an AI find a solution, or as in reasoning like a mechanic, or? Furthermore:

> * Implementing jitter in our fleet of EC2 instances reduced the peak connection rate

How? Did they wait a random amount of milliseconds before sending queries to the db?

> * Eliminating bursts of parallel queries from our API servers

How?
by JKCalhoun | 2026-02-05 05:10:13+00:00
Interesting, there are a handful of PDFs in the drop that appear to be an email with a Base64 encoded attachment—inline.

OCR is so bad of course that decoding the Base64 seems futile without a lot of effort.

Example: https://www.justice.gov/epstein/files/DataSet%2011/EFTA02609...

(More mentioned here: https://old.reddit.com/r/Epstein/comments/1qu9az2/theres_unr...)
by deaux | 2026-02-05 05:10:36+00:00
I disagree, based on having used it extensively over the last week. I find it to be at least as strong as Sonnet 4.5 and 5.2-Codex on the majority of tasks, often better. Note that even among the big 3, each of them has a domain where they're better than the other two. It's not better than Codex (x-)high at debugging non-UI code - but neither is Opus or Gemini. It's not better than Gemini at UI design - but neither is Opus or Codex. It's not better than Opus at tool usage and delegation - but neither is Gemini or Codex.
by btown | 2026-02-05 05:10:49+00:00
You don't need multiple postmasters to spawn connection processes, if you have a set of Postgres proxies each maintaining a set pool of long-standing connections, and parceling them out to application servers upon request. When your proxies use up all their allocated connections, they throttle the application servers rather than overwhelming Postgres itself (either postmaster or query-serving systems).

That said, proxies aren't perfect. https://jpcamara.com/2023/04/12/pgbouncer-is-useful.html outlines some dangers of using them (particularly when you might need session-level variables). My understanding is that PgDog does more tracking that mitigates some of these issues, but some of these are fundamental to the model. They're not a drop-in component the way other "proxies" might be.
by krackers | 2026-02-05 05:11:57+00:00
If one truly believed in LLMs being able to replace knowledge workers, then it would also hold that they could replace managers and execs. In fact, they should be able to do it even better: LLMs could convert every company into a "flat" one, bypassing the manangement hierarchy and directly consuming meeting notes from every meeting to get the real status as the source of truth, and provide suggestions as needed. If combined with web-search capability, they would also be more plugged into the market, customer sentiment, and competitors than most execs could ever be.
by speleolinux | 2026-02-05 05:12:57+00:00
If your private key has a good passphrase and is suitably encrypted, say with ed25519, then that's probably as good as you can do other than physically going into work and storing everything in your head :-) Politely ask the client to suggest what they consider would be a suitable alternative.
I also setup git hooks to prevent accidentally checking in private keys or passwords into git or other version control systems. And if I'm travelling into or from work I also encrypt some stuff just in case I have a problem and the laptop is stolen.
by coppsilgold | 2026-02-05 05:13:17+00:00
> I recommend reading the AES-XTS spec, in particular the “tweak”. Or for AES-GCM look at how IV works.

What does this have to with anything? Tweakable block ciphers or XTS which converts a block cipher to be tweakable operate with an actualized key - the entropy has long been turned into a key.

> Your password/fingerprint/whatever are just adding a little extra entropy to that already cryptographically sound seed.

Correct. The "cryptographically sound seed" however is stored inside the secure enclave for anyone with the capability to extract. Which is the issue I referenced.

And if what you add to the KDF is just a minuscule amount of entropy you may as well have added nothing at all - they perform the addition for the subset of users that actually use high entropy passwords and because it can't hurt. I don't think anyone adds fingerprint entropy though.
by bruce511 | 2026-02-05 05:13:17+00:00
You've hit the nail on the head. Immediate gratification.

AI is like sugar. It tastes nice, gives you energy quickly - what's not to like?
The gratification is immediate, and if "today is all that matters" it's brilliant.

The problem with sugar (and AI) is medium term. So sure, that junior dev whipped up the whole framework in ClaudeCode, and it's humming nicely. Junior dev gets credit, and after a couple years moves on somewhere else.

Then something changes. Windows. TLS. Code Signing, whatever. We need to update the program to the change. Just a small tweak. Junior Dev has gone (or is otherwise occupied) so we'll get new-Junior-dev to do it. Is he expected to do the change at the code level? Or at the prompt level? Will ClaudeCode in 2029 be able to maintain ClaudeCode Code from 2026? Or will it want to rewrite everything? Will new-junior-dev have the skillset to prompt as well as first-junior-dev? Was the code good enough that a dev could just "take it over"? Or was it "it works, let's use it" standard?

AI makes everyone look good in the short term. But it worries me for what happens in 5 years, 10 years, and so on.
Sugar is great, but you can't live (long term) on sugar. Sometimes you need a proper meal plan.
by gg582 | 2026-02-05 05:15:06+00:00
Visualizing medical records that are difficult for the general public to understand is an excellent idea. The thorough explanations and diagrams make it an excellent educational resource. If its UX was designed with an educational website in mind, it's honestly a huge success. However, the lack of a light mode and the absence of search functionality for specific cases are a bit disappointing. If it's meant to function well as supplementary material for students, having those features would be great. But the decision is yours, and I also respect the choice to maintain the current style while considering other directions.
by somenameforme | 2026-02-05 05:15:41+00:00
You're imposing your own ideological conditions that literally do not exist. It's like a supporter of e.g. imperial systems saying that the emperor is supposed to represent all of society. In society's opinion? Sure, but there is no such condition in reality. Some did, some didn't.

The problem with democracy is that we don't get anywhere even remotely near the best. It tends to promote people that are highly charismatic and highly corrupt. The latter trait is not a coincidence, but a part of getting ahead in democracy. Give corporations what they want and your election coffers will be full, refuse and they'll instead fund your opponent and their media will frame you as unelectable, a threat to democracy, or whatever new FUD phrase focus tests best at the time. And that corruption tends to correlate strongly with a complete vacancy of morals or ethics - see: how our entire political class, globally, flocked to pedo island like flies to shit.
by abrookewood | 2026-02-05 05:16:02+00:00
I wish more applications would adopt the "H" option that Jenkins uses in it's cron notation - essentially it is a randomiser, based on some sort of deterministic hashing function. So you say you want this job to run hourly and it will always run at the same minute past the hour, but you don't know (or care) what that minute that is. Designed to prevent the thundering herd problem with scheduled work.
by seanmcdirmid | 2026-02-05 05:16:56+00:00
I have a M3 max 64GB.

For VS Code code completion in Continue using a Qwen3-coder 7b model. For CLI work Qwen coder 32b for sidebar. 8 bit quant for both.

I need to take a look at Qwen3-coder-next, it is supposed to have made things much faster with a larger model.
by seanhunter | 2026-02-05 05:17:46+00:00
Speaking from personal experience which is admittedly quite old at this point, but it used to be the case that Debian definitely didn’t go out of its way to try to pull in devs. When I had a few small open source things myself I packaged them for RedHat (this is pre-fedora when RedHat didn’t have a commercial and free version, they just had “RedHat Linux”) and looked to package them for debian, given I was actually using debian for a few of my personal servers. I made the .deb packages just fine but found the Debian community were definitely not trying to attract devs[1]. I couldn’t get anyone from Debian to sign my gpg keys which if I recall correctly was a necessary part in getting my package upstreamed[2] and in the end I just gave up on it because I’m really not interested in joining a community that is so unwelcoming.

[1] although it was maybe specifically just me they weren’t trying to attract.

[2] to the point where I actually worked with someone in my day job who was a debian dev and he wouldn’t sign my key without me producing physical official ID like a passport or something. Just really bizarre level of paranoia like a government kyc process or something.
by vdqtp3 | 2026-02-05 05:17:48+00:00
> Hell, Trump even said in response to the Pretti shooting that only criminals walk around carrying guns in public.

If you were paying any attention at all, you'd see pretty much every 2A community, advocate and lobbying group was outraged by that statement and made statements against it.

Having said that, it is actually illegal to carry a firearm to go commit crimes like destroying government property, assaulting federal officers and obstructing them in carrying out their constitutional duties.
by tombert | 2026-02-05 05:18:12+00:00
People really underestimate how even small amounts of friction can discourage you from doing things.

I started using Typst instead of Pandoc Markdown->LaTeX->PDF recently. I had a reluctance to change because I didn't really see the point, it looked like Markdown, and who cares if Typst compiles faster, how much time is really spent compiling? I had a watch script set up to start recompiling on a change and it worked well enough.

But eventually I decided to give it a try, and it sort of changed my entire perspective. Large LaTeX compilations could take upwards a minute, which doesn't sound that long, but similar documents could compile in milliseconds, from scratch, and it also supports incremental compilation. It was categorically faster and it wasn't really any harder than Markdown and if you use the Latin Modern font it doesn't look significantly different than LaTeX. [1]

Suddenly I found myself experimenting with and tuning my formatting way more than I did with LaTeX. I make my documents look nicer, make sure that the spacing look nicer, have better-placed page breaks, move text around more frequently to make my writing flow a bit nicer and better. I keep Evince open to the right, tmux with Neovim and `typst watch` on the left and my changes automatically load instantly, and as such I end up making my documents nicer.

I still use LaTeX for stuff that has a lot of math formatting, but for everything else I use Typst and I find myself doing a lot more as a result.

[1] Before you say "Use MS Word or LibreOffice", yeah you're not necessarily wrong but I really hate "hidden formatting" that you get with rich text. Also I almost never like the way that documents end up looking with MS Word.
by kayleighb1 | 2026-02-05 05:20:07+00:00
*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 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
by AnotherGoodName | 2026-02-05 05:20:53+00:00
Oh dear. The ad doesn’t directly reference openai at all and for those of us out of the loop on all of this we wouldn’t have read it as such. I had no idea openai were considering this.

I think Sam would have been far better off to let this lie. I’m not at all sure of the nature of the ads coming in chatgpt but by responding so personally and aggressively to what appears to be sillyness feels like they hit a bit close to home?
by bschwindHN | 2026-02-05 05:20:53+00:00
Some notes because I weirdly just went through almost the exact same project for work:

* I also started with an RP2040 because the PIO is such a good Swiss Army knife for working with custom digital protocols. An RP2040 with a faster USB PHY would be killer!

* The STM32U5 series has variants with built-in High Speed USB PHYs, along with 2.5 megabytes of SRAM, along with easily solderable footprints (down to LQFP64) if you want to solder at home instead of having a PCB fab do it.

* JLCPCB and/or PCBWay can assemble boards for quite cheap these days

* ESD protection would be good to add to the board, as others have noted and as you mention in the post

* Ideally all routed traces which have fast rise/fall times (most digital signals) should have a solid reference plane under them along the entire trace, to avoid cross-talk and EMI, along with vias for your reference plane if your signal changes layers.

* If you control the rendering, and color banding is still an issue, look into Interleaved Gradient Noise

* I hadn't heard of GUD before. I just made a simple USB Bulk Out endpoint in the firmware and in my application code, took less than a day. Sometimes a custom solution is quicker and easier but it depends on where it's running and who you're distributing it to. Obviously my custom solution isn't interoperable with other things, but for now it doesn't need to be.

I plan to write up a blog post on the project I worked on, I'll be sure to post it to HN when I do.

https://blog.demofox.org/2022/01/01/interleaved-gradient-noi...
by NIKHILFP | 2026-02-05 05:22:05+00:00
When we first started building AI-heavy products, pricing felt like the easy part. Just charge for usage. It’s fair. It maps to cost. Everyone understands it.

Then people started shipping slower.

I kept hearing the same thing from teams using UI-first AI tools.
“I feel like I’m spending money just by exploring.”

Every click feels billable. Every experiment feels risky. So people try less. That’s why Replit's move away from raw usage toward prepaid credits matters more than it looks. The economics didn’t really change. The psychology did.

Credits turn invisible anxiety into something people can budget, plan, and mentally control. That alone increases how much people actually use the product.

The second shift is even more important. Per-seat pricing breaks down completely in AI-first workflows. The value doesn’t come from how many people are logged in. It comes from how much work the agent can do for you. Charging per person starts to feel arbitrary very quickly.

Team-wide credit pools are a better reflection of reality. They align with outcomes instead of headcount.
Replit removing pay-per-seat is a quiet admission of this truth.

But there’s also a tradeoff that isn’t talked about enough.

As agents run longer and become more autonomous, pricing becomes harder to explain. Replit moved from a fixed price per checkpoint to effort-based pricing. Add credits on top and now users see a balance going down without fully understanding how time, compute, or tokens map to cost.

The most interesting part of this change isn’t the plans. It’s the strategy.
Pooled credits. Budget controls. Longer data retention. Collaboration built into Core.

This is a clear push from individual builders toward real org workflows.

The bigger takeaway for you is simple.
AI pricing isn’t about picking usage, seats, or credits anymore. It’s about managing trust while the product itself is still evolving and most teams still underestimate how much pricing is product infrastructure, not a checkout page.

If you're struggling with your pricing, would be more than happy to help :)
by eviks | 2026-02-05 05:22:25+00:00
> will just get it by some other means, like having someone attend the class.

Not really, they don't have sufficient time budget and a network of agents to do that as comprehensively as with a simple "google search" some bureaucrat/activist can perform in a few minutes

> And they have tons of money behind them.

Sure, and each dollar has plenty competing uses
by kernelvoid | 2026-02-05 05:22:31+00:00
The comment sounds "polished" because I've probably described this project dozens of times at this point.

When you repeat the same thing over and over you naturally end up with a tight version of it. That's not an LLM, that's just how it works when you talk about something a lot.

And honestly even if I did use an LLM to write a comment on HN, so what? The code is what matters.

Go run the benchmarks, read the source, open an issue if something breaks.

That's the part that actually counts.