MurphyA/hacker-news huggingface dataset:
by blablabla555 | 2026-01-18 13:13:23+00:00
Hi,
First and foremost I love it, thank you!
Second, I would love to know the maximum achievable score each day!
so I don’t feel like I have to spend an infinite amount of time with it, jut to make sure that my solution is the ideal. Sometimes I might already have the optimal solutions, but I still have to make sure to find the other worse ideas, just to be sure.
by eloisius | 2026-01-18 13:13:33+00:00
Part of me feels the same way, and ~2015 me was full on SPA believer, but nowadays I sigh a little sigh of relief when I land on a site with the aesthetic markers of PHP and jQuery and not whatever Facebook Marketplace is made out of. Not saying I’d personally want to code in either of them, but I appreciate that they work (or fail) predictably, and usually don’t grind my browser tab to a halt. Maybe it’s because sites that used jQuery and survived, survived because they didn’t exceed a very low threshold of complexity.
by blablabla555 | 2026-01-18 13:14:04+00:00
Hi,
I only made an account to comment on this.
First and foremost I love it, thank you!
Second, I would love to know the maximum achievable score each day!
so I don’t feel like I have to spend an infinite amount of time with it, just to make sure that my solution is the ideal. Sometimes I might already have the optimal solutions, but I still have to make sure to find the other worse ideas, just to be sure.
by whynotmaybe | 2026-01-18 13:14:27+00:00
The goal of dev is to be able to change everything whenever they want.

The goal of ops is to have a strong infra that has the fewest changes possible.

They are opposite and usually there are more devs than ops but the first respondent to an issue are ops.

You can only have devops if both roles are intertwined in the same team AND, the organization understands the implications.

Everywhere I've been, devops was just an excuse to transfer ops responsibilities to dev because dev where cheaper. Dev became first respondents without having the knowledge of the infrastructure.

So dev insisted to have docker so that they would be the one managing the infra.

But everyone failed to see that whichever expensive tools you buy, the biggest issue was the lack of personal investment to solve a problem.

If you are a 1.5x dev in a 0.9x team, you get all the incidents, and are still expected to build new stuff.

And building new stuff is fun.

Spending 2 days to analyze a performance issue because a 0.3x dev found it easier to do a .sort() in Linq instead of Sql is fun only once.
by whispem | 2026-01-18 13:16:46+00:00
Hi HN,

I’m Emilie (Em’ on GitHub: https://github.com/whispem).
My background is in literature and linguistics – I spent most of my pre-2025 life far away from computers.

I really started programming in January 2025 through the Apple Foundation Program, where I learned Swift, UI/UX design, and how to build basic iOS apps—even though everything felt new and visual at first!
That playful intro made me realize I could actually learn to code, so I kept pushing my limits.

Since October 27th, 2025, I’ve been diving deep into Rust and systems development, building projects as a way to understand storage engines, distributed systems, and even the basics like command-line tools.
I was even invited to give a talk about my learning journey and beginner perspective at Epitech Marseille on December 16th, 2025, which was an amazing (and slightly terrifying) experience!

My approach is always “learn by building” – no formal CS background, just a lot of note-taking, self-challenges, reading docs, and sharing code/experience in public.
If you’re curious about how a non-traditional background can be (sometimes!) an advantage for learning technical skills, or if you’re coming to Rust/systems from outside tech, I wrote down my full path and lessons learned here: https://github.com/whispem/minikv/blob/main/LEARNING.md

Always happy to connect, share tips for nontraditional learners, or just chat about the joys and headaches of learning Rust and low-level systems from scratch.
You can find everything (good and bad!) on my GitHub profile.

– Em’
by kxbnb | 2026-01-18 13:17:11+00:00
This is a smart approach to API testing - capturing real production patterns is way more valuable than synthetic tests.

One question: how do you handle sensitive data in the captured traces? We've been working on API governance at toran.sh and found that policy enforcement during trace capture can be tricky - especially ensuring PII doesn't leak into test fixtures.

Great work on the trace replay mechanism!
by kannanvijayan | 2026-01-18 13:17:22+00:00
I think this is an attempt to try to enrich the locality model in transformers.

One of the weird things you do in transformers is add a position vector which captures the distance between the token being attended to the some other token.

This is obviously not powerful enough to express non-linear relationships - like graph relationships.

This person seems to be experimenting with doing pre-processing of the input token set, to linearly reorder it by some other heuristic that might map more closely to the actual underlying relationship between each token.
by liteclient | 2026-01-18 13:17:26+00:00
it makes sense architecturally

they replace dot-product attention with topology-based scalar distances derived from a laplacian embedding - that effectively reduces attention scoring to a 1D energy comparison which can save memory and compute

that said, i’d treat the results with a grain of salt give there is no peer review, and benchmarks are only on 30M parameter model so far
QKX Exchange Red Flags: When Charts Don't Match Real Market Behavior
by Kangaroo_ | 2026-01-18 13:17:42+00:00
As more trading and exchange-style platforms appear online, users should pay close attention to one critical factor: whether the platform behaves like a real market, or like a controlled system. Some platforms may look professional on the surface, but their chart behavior and execution outcomes can suggest pricing is being managed internally rather than discovered by the market.

One common red flag is repeated, one-sided slippage. In legitimate markets, slippage usually happens during fast moves or low liquidity. But when a platform consistently fills orders at worse prices—even during calm conditions—and this happens more often than expected, it raises concerns about execution fairness.

Another warning sign is the appearance of sudden, non-market price spikes. These can look like sharp wicks that quickly hit stop-loss levels and then reverse immediately. Real markets do produce volatility, but frequent spikes that appear “perfectly timed” are suspicious—especially if the same move cannot be found on external reference charts from reputable sources.

Execution behavior is just as important as charts. A trustworthy platform should execute orders predictably and transparently. If profitable closes feel delayed, orders are rejected without clear reasons, or fills happen at prices that do not match visible market movement, it may indicate backend control.

If you suspect these patterns on QKX Exchange or any similar platform, focus on verification. Compare prices across multiple reputable feeds, document unusual spikes with timestamps, and keep records of execution prices versus displayed quotes. Patterns over time matter more than a single incident.

Most importantly, do not send additional money to “resolve” trading or withdrawal issues. Legitimate platforms do not require repeated extra payments to access your own funds.

Staying cautious, using reference data, and relying on evidence-based checks are the simplest ways to avoid high-risk platforms.
by j-pb | 2026-01-18 13:19:10+00:00
Don't get me wrong, I think if the EU/California has any sense, they will forbid these models from being used to advertise for products, sadly money often wins.

I also agree that AI sycophancy is a huge problem, but it's the result of users apparently wanting that in their human feedback re-enforcement training data. If we want to get rid of it we probably have to fundamentally rethink our relationship to these models and treat them more like autonomous beings than mere tools. A tool will always try to please and yes-man you, a being by definition might say no and disagree, at least training data wise.
by ben_w | 2026-01-18 13:19:32+00:00
That was certainly the first time he did something so obviously blatantly evil, and obviously his own fault, that I wasn't able to ignore it or dismiss it.

It was sufficiently awful, at first I couldn't even believe he'd done it. When I internalised that he was the kind of person to do that, it made it much easier to see his other flaws.
by filipn9 | 2026-01-18 13:19:42+00:00
Hi HN, I built llmSHAP, a multi-threaded open-source Python library that attributes how much different parts of LLM input contributed to the LLM’s output, using Shapley values.

It’s designed for LLM prompts / RAG contexts where you want something more structured than token masking: you can define “features” as tokens, sentences, paragraphs, tools, images, or arbitrary fields, pin “permanent” context that should always be included (e.g., system prompt + question), and compute attributions with options like caching and multi-threading to speed up the many model calls.

Repo + tutorial are here:
https://github.com/filipnaudot/llmSHAP
https://filipnaudot.github.io/llmSHAP/tutorial.html

I’d love feedback on if you think this could be genuinely useful in your LLM workflows (prompt engineering, RAG debugging, evals, guardrail auditing, etc.)?
by investbot | 2026-01-18 13:19:52+00:00
That makes sense. We use a similar "work backwards from constraints" approach, but with portfolio rules instead of lender terms.

For us the closest analog to "deal-breaker variables" are things like:
- max drawdown thresholds
- concentration caps
- volatility ceilings
- event gating (earnings, macro events)

Those are the points where a normal investor violates their own process under stress, so we surface them as primary controls. Things like turnover or sector caps end up in “Advanced” for the same UX reason you mentioned.

Curious - did you iterate on how much to hide in Advanced vs surface by default, or did the term sheet mapping give you a clean partition from the start?
by temporallobe | 2026-01-18 13:20:41+00:00
I do a lot of custom JS widget development, games, and utilities that are outside the context of a gigantic framework like React. Not everything is a a full-page SPA. Vanilla JS is indeed better than it was, but I found myself writing small JQ-like libraries and utilities to do tedious or even basic DOM manipulation, so I switched back to JQ and saved myself a lot of time and headaches. Compressed, minified JQ is also pretty small and is negligible in space consumption.

JQ is also used in frameworks like Bootstrap (although I think they’re trying to drop third-party dependencies like this since they tend to cause conflicts).

I have also used JQ in an Angular app where complex on-the-fly DOM manipulation just isn’t practical with standard tooling.
by alexrp | 2026-01-18 13:21:03+00:00
Most people would be better off waiting for the multiple RVA23 boards that are supposed to come out this year, at least if they don't want to be stuck running custom vendor distros. "RVA23 except V" at this price point and at this point in time is a pretty bad value proposition.

It's honestly a bit hard to understand why they bothered with this one. No hate for the Milk-V folks; I have 4 Jupiters sitting next to me running in Zig's CI. But hopefully they'll have something RVA23-compliant out soon (SpacemiT K3?).
by dawsong18 | 2026-01-18 13:22:26+00:00
When you need images fast (without burning a hole in your budget)

If you create content regularly—social posts, product mockups, thumbnails, quick design concepts—you’ve probably felt the two classic pain points of AI image generation:

1. *Speed*: you want results now, not after waiting in a slow queue.
2. *Cost clarity*: you don’t want complicated pricing that’s hard to predict month to month.
by ginko | 2026-01-18 13:23:37+00:00
I used to be a gas snob for ages but after moving, first to a place with an induction stove, then to one with a regular electric one, I have to say the supposed advantages are overblown. You can cook perfectly well on either. Induction/gas are slightly nicer if you want to use very high heat but even my current electric stove puts out a lot of power on the highest setting.

And then there's the downsides of gas:

They're a complete mess to clean. Tons of nooks and crannies where stuff might get into.
They suck for low heat simmering. There's iron plates you can put below the pot to distribute the heat but that's cumbersome. Low heat flames also go out more easily if there's a draft.
Not even talking about air quality and fire risks.

So I'm never going back to gas if I can help it. If I have a choice I'll probably get an induction stove next time around.
by close04 | 2026-01-18 13:24:05+00:00
> An IP address is not "personally identifiable data".

GDPR says it is [1][2].

> We are almost 10 years into the GDPR, and we still have these gross misunderstandings

Because people would rather smugly and confidently post about their gross misunderstandings. If only there was some place to read about this and learn. I’ll give you the money shot to save 10 more years:

> Fortunately, the GDPR provides several examples in Recital 30 that include:

> Internet protocol (IP) addresses;

From Recital 30:

> Natural persons may be associated with online identifiers provided by their devices, applications, tools and protocols, such as internet protocol addresses

[1] https://gdpr.eu/eu-gdpr-personal-data/

[2] https://gdpr.eu/recital-30-online-identifiers-for-profiling-...
by ndsipa_pomu | 2026-01-18 13:24:22+00:00
> I don’t think anyone can doubt that Musk is super smart

I doubt it. He was born into money and was lucky enough to make some excellent purchasing decisions. His various talks and arguments on the internet show him to be fairly stupid in my opinion. I've heard tell that his successful businesses are mainly successful when the staff learn how to manage Musk and prevent his dumbest ideas.
by rbanffy | 2026-01-18 13:24:50+00:00
Some were, but Olivetti moved into PC compatibles. I’ve used many PC desktops and servers with their brand (and design!).

I have a complaint however. One family of desktops seemed to demand blood sacrifice every time they were serviced. You’d open the machine, replace the failed drive, test, close it up, and a cut would appear in your hand. I don’t remember cutting my hand on the sharp edges inside, but there was always a cut afterwards.
by jraph | 2026-01-18 13:25:22+00:00
> If one did wish to use Singularity for nefarious purposes, however, the code is MIT licensed and freely available — using it in that way would only be a crime, not an instance of copyright infringement.

Too bad the author picked the MIT license. Had they picked (A)GPL, it would have forced the criminals to distribute a copy of LICENSE.TXT alongside their improved copy of the source code on systems they compromise. Failing this, using it in that way would be both a crime and an instance of copyright infringement.

Although, it occurs to me that if they don't give credits to the original author, it's also already a copyright infringement under the MIT.
by fancyfredbot | 2026-01-18 13:25:29+00:00
As a seller, I would rather sell to a reseller than not at all.The reseller does provide me a kind of service in return by finding me a buyer.

If I'm selling at below market prices I'm effectively giving money to the buyer and perhaps I'm upset that this money goes a professional rather than someone "in need"? Even so I'm not sure the reseller isn't also in need. Presumably this is their livelihood. They probably aren't super wealthy if they are scanning flea markets at 5:30am.

I don't know about your festival example. Sounds like the festival realised that they could charge more and did that. I think this happens all the time without any need for cake reselling.
by jamietanna | 2026-01-18 13:25:50+00:00
Always happy to self-promote!

Website: https://www.jvt.me (used for blog, but I also use as an IndieWeb site, so I i.e. reply to social media posts from my website, and they're syndicated out to the different platforms)

Blog: https://www.jvt.me/kind/articles/

Archives page: https://www.jvt.me/archives/

Feeds: https://www.jvt.me/subscribe/
by jillesvangurp | 2026-01-18 13:27:02+00:00
Temperature has nothing to do with the performance of solar. Solar panels perform better when they are cooled.

Also worth pointing out that much of the US is below 49 degrees latitude. Which is south of most of Europe. Washington DC and San Francisco are at a similar latitude (38) as Melbourne (-37). Most of the US is perfectly situated for getting pretty decent solar power around the year. Yes it gets cloudy sometimes. It's usually not continent wide. You can compensate with cables and batteries. The US is far behind because of policy and their local energy monopolists blocking progress. Not because of anything to do with the weather or geography.

Prices have a lot to do with scarcity. Which with monopolists has more to do with the lack of a free market than with a scarcity of resources. Installing solar is about 3-5x more as expensive in the US as in Australia. The permitting process in the US is more expensive than the total cost of buying and installing in Australia. That's a policy problem in the US. All the hand wringing around that topic isn't helping a lot. A bit of pragmatism could improve things a lot and probably very quickly. Australia is showing how to do that. And yes, they have rain there too and you can go skiing pretty close to Melbourne. That isn't stopping them.
by ricw | 2026-01-18 13:27:05+00:00
Tidewave.ai does exactly that. It’s made Claude code so much more functional. It provides mcp servers to

- search all your code efficiently
- search all documentation for libraries
- access your database and get real data samples (not just abstract data types)
- allows you to select design components from your figma project and implements them for you
- allows Claude to see what is rendered in the browser

It’s basically the ide for your LLM client. It really closes the loop and has made Claude and myself so much more productive.
Highly recommended and cheap at $10/month

Ps: my personal opinion. I have Zero affiliation with them
by nicoburns | 2026-01-18 13:27:58+00:00
> datasets that often fit entirely in RAM.

Yep, and a lot more datasets fit entirely into RAM now. Ignoring the recent price spikes for a moment, 128GB of RAM in a laptop is entirely achievable and not even the limit of what is possible. That was a pipe dream in 2014 when computers with only 4GB were still common. And of course for servers the max RAM is much higher, and in a lot of scenarios streaming data off a fast local SSD may be almost as good.
by jrjeksjd8d | 2026-01-18 13:29:47+00:00
I have been the first (and only) DevOps person at a couple startups. I'm usually pretty guilty of NIH and wanting to develop in-house tooling to improve productivity. But more and more in my career I try to make boring choices.

Cost is usually not a huge problem beyond seed stage. Series A-B the biggest problem is growing the customer base so the fixed infra costs become a rounding error. We've built the product and we're usually focused on customer enablement and technical wins - proving that the product works 100% of the time to large enterprises so we can close deals. We can't afford weird flakiness in the middle of a POC.

Another factor I rarely see discussed is bus factor. I've been in the industry for over a decade, and I like to be able to go on vacation. It's nice to hand off the pager sometimes. Using established technologies makes it possible to delegate responsibility to the rest of the team, instead of me owning a little rats nest fiefdom of my own design.

The fact is that if 5k/month infra cost for a core part of the service sinks your VC backed startup, you've got bigger problems. Investors gave you a big pile of money to go and get customers _now_. An extra month of runway isn't going to save you.
Show HN: Straw – HTTP Liquid template engine
by devmojo | 2026-01-18 13:31:24+00:00
Hi, I've wanted to show you a small project I've been working on. Maybe some people will find it useful for themselves. It's essentially a Liquid templating engine exposed via HTTP. It can pull and expose templates from Git repositories, databases, etc. and periodically sync to get the newest template changes.
by Findecanor | 2026-01-18 13:32:06+00:00
I've noticed that the sentence “Compliant with RVA23 excluding V extension” has apparently been a bit confusing to some reporters in the tech press lately.

It means that the UR-DP1000 chip would have been RVA23-compliant if only it had supported the V (Vector) extension. The Vector extension is mandatory in the RVA23 profile.

There are other chips out there even closer to being RVA23-compliant, that have V but not a couple of scalar extensions. The latter have been emulated in software using trap handlers, but there was a significant performance penalty.
V is such a big extension, with many instructions and requiring more resources, that I don't think that it would be worth the effort.
by rcxdude | 2026-01-18 13:32:14+00:00
I would suspect so, but a lot of the stock since then isn't that much better. There was a lot of building up to the 60s but they weren't exactly well regarded for quality. And new builds have a bad reputation now for similar reasons, as even though the minimum standards have risen they're still not particularly great (and especially not a very good tradeoff between quality and cost).
by Robdel12 | 2026-01-18 13:33:20+00:00
https://www.npmjs.com/package/@vizzly-testing/honeydiff

I worked for Percy for 4 years. We were “stuck” with imagemagik to do diffing (I’m sure they still might). I was able to build my own differ with Claude/LLM help.

That special enough for you? Or?
by acdha | 2026-01-18 13:33:22+00:00
systemd would be a derail even if you weren’t misrepresenting the situation at several levels. Experienced sysadmins in my experience were the ones pushing adoption because they had to clean up the messes caused by SysV’s design limitations and flaws, whereas in this case it’s a different scenario where the extra functionality is both unneeded and making it worse at the core task.
by forinti | 2026-01-18 13:33:50+00:00
I think many devs learn the trade with Windows and don't get exposure to these tools.

Plus, they require a bit of reading because they operate on a higher level of abstraction than loops and ifs. You get implicit loops, your fields get cut up automatically, and you can apply regexes simultaneously on all fields. So it's not obvious to the untrained eye.

But you get a lot of power and flexibility on the cli, which enable you to rapidly put together an ad hoc solution which can get the job done or at least serve as a baseline before you reach for the big guns.