MurphyA/hacker-news huggingface dataset:
by PhilippGille | 2025-11-19 07:27:42+00:00
You can push to any other Git server during a GitHub outage to still share work, trigger a CI job, deploy etc, and later when GitHub is reachable again you push there too.

Yes you lose some convenience (like GitHub's pull requests UI can't be used, but you can temporarily use the other Git server's UI for that.

I think their point was that you're not fully locked in to GitHub. You have the repo locally and can mirror it on any Git remote.
by hulitu | 2025-11-19 07:27:57+00:00
> Why Not POSIX? > If Ion had to follow POSIX specifications, it wouldn't be half the shell that it is today, and there'd be no solid reason to use Ion over any other existing shell, given that it'd basically be the same as every other POSIX shell.

I thought the reason was that "it is more secure" because "rust".

So basically, it cannot be used for anything except its own scripts.
by BriggyDwiggs42 | 2025-11-19 07:28:53+00:00
My logic is pretty simple. If it’s hard or impossible to do something by placing a high conductivity sensor on the surface of a person’s skin, then it’s probably not possible to do it from a long distance right now. Doing this with telecom towers, which are randomly positioned relative to people, would be an absolute technological marvel, sci fi stuff.
Show HN: SimplyToast – A simple Linux startup and background process manager
by toast1599 | 2025-11-19 07:29:43+00:00
Hey folks, I'm a student dev and built a small tool for Linux called SimplyToast.

It’s a lightweight app for viewing background processes, managing startup apps, and checking their system impact. No root required, works on Ubuntu/GNOME out of the box, and comes with .deb + AppImage builds.

This isn’t meant to be some big “optimizer” app — just a clean, simple way to see what’s running and control what launches at startup.

Would love feedback regarding this. contact me on discord: toast.1599 regarding anything about this project. thanks!
by npteljes | 2025-11-19 07:29:51+00:00
Commendable action! If feel like it's a different case though. Two points:

1. Working for someone, even through a large company, is a much more directly supportive relationship, than using someone's free project. Especially since the project has a lot of large contributors.

2. A company is interchangeable, a skill is much less so. You can do the same, or very similar thing at the next company, but moving to a different language involves a lot of learning, even though both are programming languages.

For these reasons, if talking about a lot of people, I can see many of them leaving a problematic company, and only some of them changing their primary language. I'm sure there's someone out there throwing away two decades of experience for an ideal, but I don't think it's realistic, especially not for 1 problematic blog entry.
by conartist6 | 2025-11-19 07:30:59+00:00
Yeah, but pay them how much?

There's about to be a huge glut of GPU capacity and we still haven't figured out anything to actually do with all those GPUs that creates value at the scale of society.

Everything they do now steals value. Takes it from artists and bloggers and puts their money in the hands of CEOs and investors. Super efficient idea theft isn't creating new value for society because the value gained is always offset by the destruction of value we already had...
by brianpan | 2025-11-19 07:32:06+00:00
You're right. A good postmortem/root cause analysis would START from "unwrap" and continue from there.

You might start with a basic timeline of what happened, then you'd start exploring: why did this change affect so many customers (this would be a line of questioning to find a potential root cause), why did it take so long to discover or recover (this might be multiple lines of questioning), etc.
by antonvs | 2025-11-19 07:32:48+00:00
> Saying whatever you do is right or no need to strive for improvement etc just for the sake of keeping them happy, is more harmful than telling them that they are doing it bad.

I notice you don’t say why this should be true. It’s easy to see why one might consider it true for someone’s profession - but when it comes to hobbies, or people trying something they’ve never done before, your perspective is less obviously correct.
by mittensc | 2025-11-19 07:33:42+00:00
> In the 60s it was possible for a man to work an ordinary job, buy a house, settle down with a wife and support two or three children.

That wasn't true in the rest of the world.

The US had a unique position due to ww2 that was bound to errode.

I find it funny to compare horror stories from my parents/grandparents to this...
by underscoremark | 2025-11-19 07:33:54+00:00
> constantly changing API that doesn’t allow for the extensibility

You pick a (stable) version, and use that API. It doesn't change if you don't. If it truly is a _major_ project, then constantly "upgrading" to the latest release is a big no-no (or should be)!

And these "most people" who are scared of a Python API? Weak! It should have been a low level C API! ;-)
by danieltanfh95 | 2025-11-19 07:34:42+00:00
This would generally just discourage open software in general. Rebble is a non-profit and should not pretend to "own" any software or content. Eric didn't do things the polite way, but either way there's nothing to discuss here. Claiming that someone can steal something that is open source implies that they own said open source code / content. that's not how any of this works.

Reselling open source content is always going to be bad taste.
by d_e_solomon | 2025-11-19 07:35:01+00:00
Looking at aircraft manufacturing, semiconductors, cloud computing, and even smartphones, some sectors seem to settle into a stable duopoly, often for decades.

In other industries, competition stays fragmented, even when the products appear simpler or less capital intensive.

I’m curious how HN thinks about this: – What specific conditions cause a market to converge into two dominant players?

1. Is it mostly capital intensity, switching costs, regulation, or something else? 2. And which industries today are showing early signs of heading toward a duopoly?

I’m trying to better understand the mechanics behind “natural” industry consolidation.
by dwattttt | 2025-11-19 07:35:08+00:00
> It looks like changing the permissions triggered creation of a new feature file, and it was ingestion of that file leading to blowing a size limit that crashed the systems.

That feature file is generated every 5 minutes at all times; the change to permissions was rolled out gradually over the clickhouse cluster, and whether a bad version of that file was generated depended on whether the part of the cluster that had the bad permissions generated the file.
by zdragnar | 2025-11-19 07:35:42+00:00
Early adopter syndrome strikes again. None of my friends or family have Whatsapp, Whatsapp doesn't (currently) work with other services, and all of us have had SMS for nearly as long as we have had cell phones.

Slow cable Internet and 120v residential electricity are two more examples. I fortunately have fiber now, but I'll be stuck dreaming of 240v outlets and appliances for the rest of my life.
by thecaspercraft | 2025-11-19 07:37:39+00:00
I haven't used it myself but a few of my colleagues used it saying it is good and they completed a huge chunk of work with Antigravity, mind you I am very skeptical of this.

The don't seem to be getting any rate limiting issue which I don't understand, maybe a bug in Antigravity allowing them to use it for more. They are really confident in the IDE after a few hours and the output given is really good.
by Lapsa | 2025-11-19 07:38:08+00:00
and you need to take into account the background I have. (synthetic?) telepathy is what I'm forced to deal with every day (and yes - with nearly no way to prove it to you). radiomyography and microwave auditory effect is the best and most suitable explanation I've managed to find at least somewhat backed up with public scientific papers. no real contradictions, certainly seems more truthful than "evil shamans hate you and your astral implants". I don't have a hard evidence in a form of working device nor can I afford it. keep your pills to yourself
by spyridonas | 2025-11-19 07:39:20+00:00
As a European solo developer, I’ve switched entirely to European alternatives for all my infrastructure since the beginning of the year.

Cloudflare > Bunny.net

AWS > Hetzner

Business email > Infomaniak

Not a single client site has experienced downtime, and it feels great to finally decouple from U.S. services.
by YarkYao | 2025-11-19 07:39:47+00:00
Hey everyone,

I built a simple web tool to solve a personal pain point: getting stuck when trying to write reviews for products, movies, or just generating sample content.

It's called Review Generator.

What it does: AI-Powered: Generates a review from a simple prompt. Fully Customizable: You can choose the tone (Professional, Casual, Friendly, Critical, Humorous, etc.) and the length (100-500 words). Free & No Login: No sign-up required. Just go to the site and use it. It's pretty fast. Link: https://www.reviewsgenerator.org/

I built this for myself but thought others might find it useful for e-commerce, content creation, or just overcoming writer's block when leaving feedback.

I'd love to hear any feedback if you give it a try. What other tones or features would be useful?
by duskdozer | 2025-11-19 07:39:54+00:00
I can't say I find them 100% useless - though I'd rather they not pop up by default - and I understand why people like them so much. They let people type in a question and get a confident and definitive answer all in natural language, which is what it seems like the average person has tried to do all along with search engines. The issue is that they think whatever it spits out is 100% true and factual, which is scary.
by kettlecorn | 2025-11-19 07:40:26+00:00
I don't think 'unwrap' is inherently the problem.

Any project has to reason about what sort of errors can be tolerated gracefully and which cannot. Unwrap is reasonable in scenarios you expect to never be reached, because otherwise your code will be full of all sorts of possible permutations and paths that are harder to reason about and may cascade into extremely nuanced or subtle errors.

Rust also has a version of unwrap called "expect" where you provide a string that logs why the unwrap occurred. It's similar, but for pieces of code that are crucial it could be a good idea to require all 'unwraps' to instead be 'expects' so that people at least are forced to write down a reason why they believe the unwrap can never be reached.
by koito17 | 2025-11-19 07:40:33+00:00
> I don't think I've ever seen a crate or production codebase that documents infallibility of every single slice access.

The smoltcp crate typically uses runtime checks to ensure slice accesses made by the library do not cause a panic. It's not exactly equivalent to GP's assertion, since it doesn't cover "every single slice access", but it at least covers slice accesses triggered by the library's public API. (i.e. none of the public API functions should cause a panic, assuming that the runtime validation after the most recent mutation succeeds).

Example: https://docs.rs/smoltcp/latest/src/smoltcp/wire/ipv4.rs.html...
by toast0 | 2025-11-19 07:41:42+00:00
> So if one region is currently cloudy... spin it down and transfer load to a different region, where it's sunny? It's kind of like the "wide area grid" concept without actually needing to run power lines.

> Yes, I know that in reality the capex of building and equipping a whole DC means you'll want to run it 24/7, but it is fun to think about ways you could take advantage of low cost energy.

There's some balance between maximizing capex, business continuity planning, room for growth, and natural peak and trough throughout the day.

You probably don't really want all your DCs maxxed out at the daily peak. Then you have no spare capacity for when you've lost N DCs on you biggest day of the year. N might typically be one, but if you have many DCs, you probably want to plan for two or three down.

Anyway, so on a normal day, when all your DCs are running, you do likely have some flexibility on where tasks run/where traffic lands. It makes sense to move traffic where it costs less to serve, within some reasonable bounds of service degradation. Even if electricity prices are the same, you might move traffic where the ambient temperature is lower, as that would reduce energy used for cooling and with it the energy bill.

You might have some non-interactive, non-time sensitive background jobs that could fill up spare DC capacity... but maybe it's worth putting a dollar amount on those --- if it's sunny and windy and energy is cheap, go ahead ... when it's cloudy and still and energy is expensive, some jobs may need to be descheduled.
by jll29 | 2025-11-19 07:42:05+00:00
Thanks for sharing some of the methodology and code for how you put your book together.

Are you comfortable speaking about the financial side? What does an editor get per copy sold, what does an author get? (In the science world, for instance, editors tend to get money often, but authors never get paid for articles or book chapters.)

Hopefully, now that you have experience in the process and all your code ready, you can repeat the exercise with higher efficiency and profitability.
by dev_l1x_be | 2025-11-19 07:42:40+00:00
Exactly the right take. Even when you want to have rapid changes on your infra, do it at least by region. You can start with the region where the least amount of users are impacted and if everything is fine, there is no elevated number of crashes for example, you can move forward. It was a standard practice at $RANDOM_FAANG when we had such deployments.
by kosinus | 2025-11-19 07:44:05+00:00
Author here.

You're right, it's very much a trade-off and preference where you put control, NixOS or Kubernetes. I'm not so much torn, but more believe you always have to weigh pros and cons.

For CoreDNS specifically, this setup adds CoreDNS to every node, and every node does DNS locally, so there's no redundancy benefit to using a Kubernetes deployment for CoreDNS. It does become a benefit as soon as you can't have a CoreDNS per node. I guess the obvious downsides to CoreDNS per node are that cache becomes very spread out in larger setups, and you may end up hammering your API server and upstream DNS servers more.
by anal_reactor | 2025-11-19 07:44:54+00:00
Honestly... everyone shit themselves that internet doesn't work, but next week this outage will be forgotten by 99% of population. I was doing something on my PC when I saw clear information that Cloudflare is down, so I decided to just go take a nap, then read a book, then go for a walk. Once I was done, the internet was working again. Panic was not necessary on my side.

What I'm trying to say is that things would be much better if everyone took a chill pill and accepted the possibility that in rare instances, the internet doesn't work and that's fine. You don't need to keep scrolling TikTok 24/7.

> but my use case is especially important

Take a chill pill. Probably it isn't.
by kenhwang | 2025-11-19 07:45:22+00:00
My previous employer already had a product offering that could do this for a better part of a decade by triangulating with WiFi/BLE and cross referencing with surveillance footage. It was deployed in malls and retail chains.

It generated interesting information, but not interesting enough to be profitable.

We weren't the only ones with this capability either, most major retailers had this level of analytics through surveillance footage that previously existed for loss prevention purposes. Then simply link the data to a rewards number or credit card and you got a stable tracking identity.
by dev_l1x_be | 2025-11-19 07:46:36+00:00
Than they are going to write None | Err => yolo() that has the same impact. It is not the syntax or the semantic meaning is the problem here but the fact that there is no monitoring around the elevated error counts after a deployment.

Software engineers tend to get stuck in software problems and thinking that everything should be fixed in code. In reality there are many things outside of the code that you can do to operate unreliable components safely.
by semi-extrinsic | 2025-11-19 07:47:44+00:00
Not the protocol, the group chat UX. iMessage gives kids easy access to a place where they can create groups, name them, invite and kick out other kids at will, and send messages + audio/video. It's minimally different from Snap or Discord - except that those actually have parental controls, and there is no easy way to disable iMessage group chats.

The equivalent is simply lacking from Android due to RCS group chat being a broken mess.
by griffzhowl | 2025-11-19 07:47:49+00:00
It does seem an unlikely place for a market:

13°42′59.9″S 75°52′28.46″W

If there really were baskets of corn there, it seems more likely it was used for storage, and situated along the ridge not too far from the valley floor to protect the crops from floods and perhaps raids. Picture (a) in the article has a defensive settlement marked nearby.

Still, a very enigmatic site
by mk89 | 2025-11-19 07:48:00+00:00
Mastodon is a bubble worse than when you enable all the activity/history/etc on Google and get always "things related to what you search".

The community is so "conforming" on certain topics that you will rarely find different opinions and those get flagged etc. I was in one of the main instances, and I noticed a change at the end (like when a tiny 1% becomes 1.1% and then 1.2%, or let's say more outspoken, but it wasn't enough) before I decided not to be there anymore.

About the influencers: They are there too, it's just different how it works. But one way or another I always stumbled upon their posts, although I really disliked them because they basically foster that bubble. They are just there to be the first in a less saturated market, like the first influencers of YouTube or so. And while you believe they are not there to influence you, watching the same crap every day passively influences you, even if you don't feel it.

This made me go "back" to X, whose main issue is for me the huge amount of bots or repetitive content, which you cannot just fight with manual tooling.

And X made me go back to no social media, except for time to time to see fun stuff or (very likely) unrealistic videos. Which is ok sometimes to decompress a bit.

So in a way I have to thank Mastodon for making me see that I am just not cut out for social media.
by yetihehe | 2025-11-19 07:48:12+00:00
I think that free will ends up in that randomness of neurons firing. That can't be really predicted and steered. Free will is essentially freedom from manipulation/overriding external to the entity having free will. Theoretically that doesn't even need randomness.

And I don't think those fish free willed themselves. They just grew more random due to randomness inherent in our universe, despite us trying to force them into being exact. This was example of randomness of complicated biological processes, not of free will.
by toast0 | 2025-11-19 07:50:02+00:00
> I also think you would need more than 24 hours battery. You have to prepare for freak weather events that reduce system capacity.

In general, yes. Not really in the context of utility generation for a DC, though. A DC should have onsite backup generation, at least to supply critical loads. If your contracted utility PV + storage runs out, and there's no spare grid capacity available (or it's too expensive) you can switch to onsite power for the duration. The capex for backup power is already required, so you're just looking at additional spending for fuel, maybe maintenance if the situation requires enough hours on backup.
by zwnow | 2025-11-19 07:50:26+00:00
Yea because the average Joe totally has a university title. However in Germany a lot of poor people have many children while a lot of academics have less [0]. It's "doable" also doesn't mean its pleasant. I have checked the rural housing market recently and for a somewhat acceptable house you will have to pay easily ~3k per month given you have a somewhat big start capital. Not sustainable if one person loses their job for a while. Not to say it was that much easier back in the day, the housing market is just beyond fucked for most ordinary people.

[0] https://en.wikipedia.org/wiki/Demographics_of_Germany
by Groxx | 2025-11-19 07:50:42+00:00
Yeah... I just started getting back into building sms/mms/rcs apps on Android and oh boy. It's much more of a mess than I expected, and much more "oh so it's basically just Google now, and they seem to be trying to lock it down further" than I expected (or hoped).

And you can't even implement it yourself because it requires special permissions on Android, which you can only get if you're a carrier/oem-blessed app. And the early "you'll be able to build other apps, there will be an API like this: https://github.com/android-rcs/rcsjta" promises (which would put it on par with sms/mms) never materialized, despite a reference implementation that did exactly that over a decade ago.

At this point I'm just totally against RCS and I'm intentionally turning it off. Why hand all of your messaging communications over to Google, when they've got such a consistent history of being hostile? We're much better off going back to telling people not to use sms (or mms or rcs) at all because it's insecure.
by Nevermark | 2025-11-19 07:50:49+00:00
I want to breed octopus to live longer.

Then identify the "morph", the gene cluster, that did the trick in the initial species, to speed up the uplift for the rest of them.

But given how intelligent they are, and how much they learn in their short lifetimes, completely self-directed and self-learning highly curious autodidact geniuses from the moment they escape their tiny egg, a race of long lived octopuses without learning brakes might be an existential threat for us.

Or they might create a magical ocean civilization. There are octopus species everywhere. Deepest ocean floor, under the polar cap, even a "land" species that lives on the beach. Everywhere from sea level down.
by user34283 | 2025-11-19 07:51:15+00:00
One would think this would have been obvious when it fails on the first or second request already, yet people here all complain about rate limits.

When I downloaded it, it already came with the proper "Failed due to model provider overload" message.

When it did work, the agent seemed great, achieving the intended changes in a React and python project. Particularly the web app looks much better than what Claude produced.

I did not see functionality to have it test the app in the browser yet.
by AuryGlenz | 2025-11-19 07:51:29+00:00
Increased production has always just lead to more stuff being made, not more people unemployed. When even our grandparents were kids a new shirt was something you’d take care of, as you don’t get a new one very often. Now we head on to Target and throw 5 into our cart on a whim.

Were there less weavers with machines now doing the job (or whatever?). Sure. But it balances out. It’s just bumpy.

The big change here is that it’s hitting so many industries at once, but that already happened with the personal computer.
by avidiax | 2025-11-19 07:52:44+00:00
Just realize that the sort of people that move to fill the space are not the sort to leave even 2 seconds of following distance.

So once you restore your following distance, that person has cost you less than 2 seconds.

Is it a bit annoying? Sure. But it's not a reason to start tailgating (not that you were necessarily claiming that).
by jamesbelchamber | 2025-11-19 07:55:27+00:00
I think the attitude here was "you've publicly accused me of impropriety, so here come the receipts". Specifically the accusations that he's not communicating with them (the messages prove he is).

You could argue the extent to which this was necessary but he's got to publicly defend himself against accusations ("Core Devices Keeps Stealing Our Work") that appear to be false.