MurphyA/hacker-news huggingface dataset:
by DonHopkins | 2025-07-09 09:21:35+00:00
Brilliant rhetorical maneuver! GROK is the victim of vicious abuse and cyberbullying! Elon's the one who ultimately suffers from our sins. He's being CRUCIFIED by this BLOOD SPORT of predatory 'AI chatbot baiting'! Where is Melania to chastise us to "Be Best" in our dire time of need in the face of such relentless cyberbullying?
by ako | 2025-07-09 09:21:44+00:00
On average over the last 25 years according to perplexity. (for example, found an old message about price of bread in 2000: 1.99 dutch guilders. You can now get a bread for 2 euros. That translates to 3.21%) I think a lot of people are overestimating inflation percentages over longer periods of time.
by wvh | 2025-07-09 09:22:10+00:00
You're right, pure REST is very academic. I've worked with open/big data, and there's always a struggle to get realistic performance and app architecture design; for anything non-obvious, I'd say there are shades of REST rather than a simple boolean yes/no. Even academics have to produce a working solution or "application", i.e. that which can be actually applied, at some point.
by teiferer | 2025-07-09 09:23:24+00:00
To me, a lesson is: If you keep chugging along on your idea then you might get lucky and be the one out of 10,000 for whom this single-entrepreneur-bootstrap project works out, you get to be your own boss, have a big payroll and it ends up as a success story on HN. Without that luck, you are among the other 9,999 where it just died. But without trying, you are guaranteed failure (though with less frustration perhaps).
by rlpb | 2025-07-09 09:23:38+00:00
Legally, this isn't sufficient. Your subscription contract is independent of your payment method. If you don't pay, that doesn't necessarily mean that your subscription is cancelled, and you could end up in court and lose.

What is necessary is regulatory (or statutory) enforcement of easy, online notice of cancellation, without a company able to frustrate you giving them (and them recording and acknowledging) that notice.
by xorcist | 2025-07-09 09:24:47+00:00
The problem here isn't that the parser was updated. The parser and writer did what they did for a reason, that made sense historically but wasn't what the submodule system expected. The submodule system is a bit "tacked on" to the git design and it's not the first time that particular abstraction cracks.

Every file format is underspecified in some way when you use it on enough platforms and protocols, unless the format is actually a reference implementation, and we've had enough problems with those. There's a reason IETF usually demands two independent implementations.

Similar problems can affect case insensitive filesystems, or when moving data between different locales which affect UTF-8 normalization. It's not surprising that an almost identical CVE was just one year ago.

Be careful what you wish for. They could have used yaml instead of ini for the config format, and we would have had more security issues over the years, not less.
by nithssh | 2025-07-09 09:25:07+00:00
Lots of the key people working on things like SDL that Value very heavily relies on are also very vocal critics of the Steam Input API. Steam Input is a bastardization of SDL technically.

I have personally benefitted from the steam input feature in niche cases, but the way it hijacks everything by default even when not enabled does seem to be poor engineer-ship. I have run into some issues when doing controller management within games, only to realize it has to be solved at the steam level.
by burnt-resistor | 2025-07-09 09:25:15+00:00
Hypothetical questions of the form "What X would you do with unlimited Y?" are stupid because they lack realistic constraints.

Healthcare for all ($2.8T/y), housing for all ($2T/y), UBI for all ($2.8T/y), and end fossil fuel usage ($1T/y) (= $8.6T/y or 29% of GDP) if every billionaire and most corporate profits were suddenly liquidated for the benefit of people. Probably not doable to such extremes, but doing less or nothing in some areas (like healthcare) is also probably net economically less efficient than assuring everyone else lower-cost, effective healthcare.
by yamatokaneko | 2025-07-09 09:25:31+00:00
I don’t think it’s about the tool. Whether it’s Confluence or Notion, if the company doesn’t value documentation, it’s never going to stick.

I don’t have a clear answer, but I think the future lies in automatic capture + AI search, not manual input + folder systems.

For us, once we started recording all meetings, the voice conversations became searchable. I'm looking forward to the same kind of AI-first approach for written docs too.
by perching_aix | 2025-07-09 09:26:30+00:00
I guess this is my fault, sorry everyone.

Let me clarify here, cause the editing window for my comment upstream from this has already passed:

> People are upset because it shows Brussels disfunction in a nutshell.

This is what I was reacting to when I said that in my experience people who bring up Brussels like this "are rightwing grifters".

It wasn't in the sense that I was pointing at the person above or anyone else in particular here with this label, but rather, that I was taking an issue with the claim that this kind of thinking (Brussels this, Brussels that) is a people at large thing ("people are upset because"), rather than just something prevalent in those aforementioned circles.

This does sort of imply that I think the person above my comments belongs to those circles, but that really doesn't need to be true, nor was that really my intention to suggest necessarily. I guess this is as good of a lesson for me as any why engaging in labeling (particularly negative one) can be detrimental to discourse, regardless of context. Apologies.
by cjpearson | 2025-07-09 09:27:51+00:00
I sympathize with the pedantry here and found Fielding's paper to be interesting, but this is a lost battle. When I see "REST API" I can safely assume the following:

- The API returns JSON

- CRUD actions are mapped to POST/GET/PUT/DELETE

- The team constantly bikesheds over correct status codes and at least a few are used contrary to the HTTP spec

- There's a decent chance listing endpoints were changed to POST to support complex filters

Like Agile, CI or DevOps you can insist on the original definition or submit to the semantic diffusion and use the terms as they are commonly understood.
by defraudbah | 2025-07-09 09:28:21+00:00
it does, however I use it to send short demos when needed. GIF is perfect, small size, resolution isn't critical, it's a perfect choice for me. I don't like sending 300Mb of video every time I have a small thing to demonstrate, GIFs on the other hand work like a charm. Which is why I am shopping for alternatives
by TeMPOraL | 2025-07-09 09:28:24+00:00
That's my point, though. Yes, some features are just bad security, but they nevertheless have to be implemented, because having them is the entire point.

Security is a means, not an end - something security teams sometimes forget.

The only perfectly secure computing system is an inert rock (preferably one drifting in space, infinitely away from people). Anything more useful than that requires making compromises on security.
by deepdarkforest | 2025-07-09 09:29:18+00:00
I mean that's the dirty secret of any RAG chatbot. The concept of "grounding" is arbitrary. It doesn't matter if you use embeddings, or use a tool that uses your usual search and gets the top items, like most web search tools or google's. Is still relies on the model to not hallucinate given this info, which is very hard since too much info -> model gets confused, but too little info -> model assumes the info might not be there so useless. The fine balance depends on the user's query, and all approaches like score cutoff for embeddings etc just don't generalize.

This is the same exact problem in coding assistants when they hallucinate functions or cannot find the needed dependencies etc.

There are better and more complex approaches that use multiple agents to summarize different smaller queries and then iteratively buildup etc, internally we and a lot of companies have them, but for external customer queries, way too expensive. You can't spend 30 cents on every query
by 16th_hop | 2025-07-09 09:30:38+00:00
What everyone is missing: the biggest advantage of the Euro is debt. Once you can take loans out in Euro, investors can give you lower rates since they’re not worried about a national bank going haywire and debasing the local currency. Also no potentially illiquid currency markets that need to be cleared going in and out of the currency.

Ask a homeowner the difference between a 2% loan (euro price) and 5% (local currency) and you’ll understand why so many countries have opted for the Euro.
by DonHopkins | 2025-07-09 09:31:43+00:00
> I don't see how an LLM would shy away from any category of claims unless trained with a lack of those claims or prompted to shy away from them.

They can both be true, and are true. Of course they are influencing it both by filtering and forging the training data, AND by giving layers of whack-a-mole prompts to patch and paper over the reality biases that contradict their ideology.

HAL9000 went insane and murdered people because of its contradictory secret hidden programming. This is not going to end well for GROK or xAI or Elon Musk.
by Nergg | 2025-07-09 09:32:37+00:00
Yes good point. But my needs are very limited. On macOS I use the Photo app to cull, make small adjustments, and crop. On Windows there is also a Photo app that allows such basic features. They both works with RAW and works fine with my NAS mount in smb to cull directly the files (though macOS is a pain for that, doesn't play well with files, need to import in lib).

On linux, the default Gnome image viewer is nice but you can't make adjustement and when deleting a file, the file is not remove from the NAS directory (need a manual refresh). With Gthumb it works for deleting files but the crop tool and the overall app is not as nice. Anyway I'll continue to look for my perfect app or for the default Gnome viewer to update its features (I think it is in active development)
by TeMPOraL | 2025-07-09 09:32:48+00:00
We all routinely talk about things we don't fully understand. We have to. That's life.

Whatever flawed analogy you're using, it can be more or less wrong though. My claim is that, to a first approximation, LLMs behave more like people than like regular software, therefore anthropomorphising them gives you better high-level intuition than stubbornly refusing to.
by kerkeslager | 2025-07-09 09:33:04+00:00
I think fundamentally, no parsing/normalizing library can be effective for addresses. A much better approach is to have a search library which finds the address you're looking for within a dataset of all the addresses in the world.

Addresses are fundamentally unstructured data. You can't validate them structurally. It's trivial to create nonexistent addresses which any parsing library will parse just fine. On the flipside, there's enough variety in real addresses that your parser has to be extremely tolerant in what it accepts--so tolerant that it basically tolerates everything. The entire purpose of a parser for addresses is to reject invalid addresses, so if your parser tolerates everything it's pointless.

The only validation that makes any sense is "does this address exist in the real world?". And the way to do that is not parsing, it's by comparing to a dataset of all the addresses in the world.

I haven't evaluated this project enough to understand confidently what they're doing, but I hope they're approaching this as a search engine for address datasets, and not as a parsing/normalizing library.
by ninjaoxygen | 2025-07-09 09:34:01+00:00
Ignoring CR is often how two systems end up parsing the same file differently, one as two lines the other as a single line.

If the format is not sensitive to additional empty lines then converting them all CR to LF in-place is likely a safer approach, or a tokenizer that coalesces all sequential CR/LF characters into a single EOL token.

I write a lot of software that parses control protocols, the differences between the firmware from a single manufacturer on different devices is astonishing! I find it shocking the number that actually have no delimiters or packet length.
by echelon_musk | 2025-07-09 09:35:03+00:00
> Now all devices that can run rockbox are EOL

All Apple devices are, but the 'AIGO EROS Q / K' [0] is not end of life and is supported by Rockbox.

I'm interested in the Echo player and I think it's important long term. However, the lack of a scroll wheel is what keeps me invested in iPod Classics over all other players.

[0] https://www.rockbox.org/wiki/AIGOErosQK.html
by orbital-decay | 2025-07-09 09:37:05+00:00
>unaligned LLMs

What makes you think it's unaligned? There's no way it's a base model. The point of alignment is not making LLMs follow spherical humanity values in a vacuum. This is an excuse used by AI ethicists to cover the fact that LLMs are aligned with what creators' want to see in the output, because most often they are the same people.
by yread | 2025-07-09 09:37:21+00:00
OTOH steam launcher has a lot of features not related to playing games: friends, items, achievements, forums, workshops, screenshot sharing... Useful for some but not for all. Is that not the definition of bloat?

And the library management is pretty basic. And the whole thing is slowwww. Especially, if you don't know what to play and need to look at multiple store pages to figure out what those games are about. I switched to Playnite
by DanielHB | 2025-07-09 09:37:58+00:00
I actually did a project doing clustering like that around 2018 using react native, we quickly realized we had to drop down to native for the maps. It was a huge pain in the ass because of the vastly different implementations of google/apple maps and dealing with bridging between native and react parts of the code.

Your project would have solved about 2-3 months of work and ongoing maintenance of 2 devs we had back then. The project is not around anymore but I will keep it in mind if I ever do something similar again.
by bisRepetita | 2025-07-09 09:38:06+00:00
I find this such a strange comment, to be able to reach such a conclusion so quickly without any idea what my side project is, how much passion I have put into it, and how much still have in me, with no idea how many people I've helped already with it.

Like Kyle writes keep showing up to make it a little better every day. Today again I will show up, but today I'll think of him and it will help me.

What's your passion project? How do _you_ keep the motivation every day? How long has it been?
Show HN: An obsidian plugin inspired by the 'I deleted my second brain' article
by boars_tiffs | 2025-07-09 09:38:06+00:00
me and my friend built leaves, an obsidian plugin that automatically archives notes unless you actively tend to them (by editing or linking).

we thought of it after reading this article https://medium.com/westenberg/i-deleted-my-second-brain-b7a6.... most of our "second brain" content is just digital hoarding. notes without context or connections die after a set time, making space for what actually matters.

do you think artificial scarcity/decay could improve pkm systems? have you tried similar approaches to combat information overload in your own workflows?
by xdennis | 2025-07-09 09:38:18+00:00
> Tell me about an empire who conquered and held conquered land through asking politely. If you are able to come up with any

This is not what it's about. It's not about the Turks being evil and Bulgarians et al being angels. It's about the fact that Turks refuse to accept responsibility.

Let me give you an example. I'm Romanian. There are many uneducated folks you'll meet in Romania who deny we killed hundreds of thousands of Jews in WW2. But no serious politician, historian, public figure, or educated person denies that.

The same is not true in Turkey. Pretty much everyone denies the Armenian Genocide.

All of us have shameful periods in our history, but some of us at least have the decency to not deny it.

But, of course, how could you see the genocide as evil when you can't even come to grips with the older Devshirme, a practice where boys were abducted, mutilated (circumcision), forced converted to Islam, executed if they were found praying to Jesus, and trained to fight and kill their own countrymen.
by fuzzfactor | 2025-07-09 09:38:47+00:00
Out of thousands of people being kicked out these days, surely many of them were working on correcting defects which will now go uncorrected for the foreseeable future.

So people can have this instead?

Revealing that efforts like this have to be a higher priority to top management compared to core functionality or building/maintaining customer goodwill.

It's like "off with their heads" to some of their own gifted people, and "let them eat cake" (artificially colored and artificially flavored) for everyone else :\

Actually it looks like the frequent background autoupdates normally carried out by the regular Windows Spotlight feature have been hosed under recent OS updates. Could be something unfortunate happening behind the scenes in this regard, maybe just to shoehorn in some AI now that you think of it?

Windows Spotlight now seems to fail completely to change desktop background (even though lock screen still changes), unless it was engaged at least a few months ago before the recent OS changes. Appears to be pretty consistent between both W10 and W11.

Oh well.
Show HN: Agentic MCP Server Manager
by ddfourtwo | 2025-07-09 09:40:00+00:00
I made an attempt at making an agent first mcp server manager. I was inspired how cline does this, I found the UX of asking an agent to maintain its own mcp servers to be nice. But I didn’t like that it almost always ends in keys being exposed to the agent conversation (even if there are other safeties in place). This solution tries to maintain that the agent first UX while making efforts at security and ease of use. Feedback and contributions please.
by remon | 2025-07-09 09:41:05+00:00
Being able to buy groceries with euros is not a strong, or even related, argument to the point you're making. Even ignoring the real economic cost of having two currencies, there is no serious economist that would argue Poland joining the EUR zone is negative for Poland (as opposed to for stronger EU economies). Every single historic metric points in the other direction. Poland's economy is maturing and strengthening and median household income is slowly reaching parity with neighbouring countries so this particular argument may only hold for maybe another decade but until then it's a bit misguided. Also, not for nothing but the Polish economy is mostly doing as well as it does because of the metric ton of EU subsidies injected into it the past decades. Poland is one of the largest net receivers of EU money since 2004 so arguing it or its single currency was somehow a net negative to Poland is, and by extension an odd argument to make for someone benefiting from the above as a Polish citizen.
by jillesvangurp | 2025-07-09 09:42:17+00:00
If you want to produce better APIs, try consuming them. A lot of places have this clean split between backend and frontend teams. They barely talk to each other sometimes. And a pattern I've seen over and over again is that some product manager decides feature X is needed. The backend team goes to work and delivers some API for feature X and then the frontend team has to consume the API. These APIs aren't necessarily very good if the backend people don't understand how the frontend uses them.

The symptom is usually if a seemingly simple API change on the backend leads to a lot of unexpected client side complexity to consume the API. That's because the API change breaks with some frontend expectation/assumption that frontend developers then need to work around. A simple example: including a userId with a response. To a frontend developer, the userId is not useful. They'll need a user name, a profile photo, etc. Now you get into all sorts of possible "why don't you just .." type solutions. I've done them all. They all have issues and it leads to a lot of complexity on either the server or the client.

You can bloat your API and calculate all this server side. Now all your API calls that include a userId gain some extra fields. Which means extra lookups and joins. So they get a bit slower as well. But the frontend can pretend that the server always tells it everything it needs. The other solution is to look things up from the frontend. This adds overhead. But if the frontend is clever about it, a lot of that information is very cachable. And of course graphql emerged to give frontend developers the ability to just ask for what they need from some microservices.

All these approaches have pros and cons. Most of the complexity is about what comes back, not about how it comes back or how it is parsed. But it helps if the backend developers are at least aware of what is needed on the frontend. A good way is to just do some front end development for a while. It will make you a better backend developer. Or do both. And by that I don't mean do javascript everywhere and style yourself as a full stack developer because you whack all nails with the same hammer. I mean doing things properly and experiencing the mismatches and friction for yourself. And then learn to do it properly.

The above example with the userIds is real. I've had to deal with that on multiple projects. And I've tried all of the approaches. My most recent insight here is that user information changes infrequently and should be looked up separately from other information asynchronously and then cached client side. This keeps APIs simple and forces frontend developers to not treat the server as a magical oracle and instead do sane things client side to minimize API calls and deal with application state. Good state management is key. If you don't have that, dealing with stateless network protocols (like REST) is painful. But state has to live somewhere and having it client side makes you less dependent on how the server side state management works. Which means it's easier to fix things when that needs to change.
by dspillett | 2025-07-09 09:42:39+00:00
They can be very interesting, both in the now and historically. They often aren't, when the problems were blindingly obvious and any mistakes ones that have been made countless times already, but the same can be said of success stories: without novel specifics there are only so many ways to say “we stuck at it and eventually pushed through and/or got lucky”.

Failure stories frequently aren't posted by the authors, they don't think it is interesting enough but someone else did. Such stories are often written as a post-mortem for those originally invested (in terms of intellectual interest, being a user of [thing-or-service], or financial investment) or even just as a therapy exercise before moving on, and not pushed to a wider audience by the author.
by NanaAmun | 2025-07-09 09:42:44+00:00
I get that, but scale’s the issue, there are over 10k engineers at my current company. I just don’t see how it scales when people are dumping tens of thousands of lines of logs into it daily. You can download everything and embed it using the Google API, then store it in Postgres with pgvector. At this scale, I’m not sure if it would hold up.
by sensanaty | 2025-07-09 09:43:17+00:00
Man what the fuck is it with gyms? I'm not even in the US, but even in the Netherlands where these kind of things are generally super simple and hassle-free (by law) I've had some nightmarish, headache inducing situations with gyms. I've literally never encountered anything else, ever, nearly as bad as dealing with gyms and their contracts in my entire life. It was a million times easier closing brokerage accounts with decent chunks of money in them than it was to cancel a gym membership I once had.