HN user

mqus

1,285 karma

https://github.com/mqus

Posts13
Comments401
View on HN

I guess it depends on what you expect. If you expect the train to be on time .. yes, India is much better than Germany. ~80% trains delayed 15 min or less vs Germany 36% trains delayed 15 min or less.

I won't defend DB too much here but saying that 64% of trains in germany are delayed more than 15min is just plain wrong. The official statistics put it at 40% for 6min or more for long distance trains and 11% for regional trains in 2025[1]. I think if there would be 15min statistics, DB would be on a sinilar level to India for long-distance. Not something to be proud of, but not as desastrous as you paint it. Though, maybe I misunderstood? Do you have sources for the indian numbers?

[1] https://eisenbahn.de/geramond-vgb/jahresbilanz-2025-puenktli...

they did not "just announce" that, it was a rather technical decision several layers down, made a while ago. Sure, some things are not easily created without US companies but the overall tendency is pretty clear and it is: reduce absolute dependencies.

It's probably only funny because the commenting germans are aware that there is a much simpler "UG" (without the &co KG), which is pretty much a LLC, which you can open on your own, a bit faster, much cheaper. But apparently OP didn't do that for tax reasons (in a normal UG, if you want to pay yourself, you gotta pay income tax and all the other stuff)

If an american comes and says they founded a public company (with stocks and all), and complained about the fuzz involved, you would also tell them that it's their own fault, right?

That said, maybe the US/Delaware LLC has this component as well, I'm not a lawyer :D

As someone who tried rerere and didn't see the point:

How? Usually I rebase the same branch multiple times onto different, but successive commits of the master branch. But after I solved a bunch of conflicts of the first rebase, I shouldn't have the same conflicts again in a second one, since the rebased branch contains the merged conflict. Rebasing again could only turn up new conflicts (with newer, other commits on the master branch).

How can I have the same conflict again for repeated rebases?

At what point will you draw the line between "the user wants to do this because of his/her free will" and "the user wants to do this because someone else told them to"? Where will you stop?

All of this is just a bandaid, so why not stop at the state we are at _right now_, without some kind of 24h-long process to enable sideloading and let people be people? Yes, people make mistakes. But that is not your responsibility, especially if it comes at the cost of freedom. The most secure android device would probably be a brick, but you won't sell these, right?

Please instead take these resources and invest them into the app verification process in the play store. Way too many scams are right under your nose, no need to search in places where people are happy with the status quo.

Re your last paragraphs: I think RMS really meant just the Linux kernel when he wrote that(the topic is drivers, after all), not GNU/Linux, the OS or GNU/Linux, "the system". So it can be argued that he isn't really contradicting himself

Ok, then I don't pay you for advertising. On an entirely unrelated note, could I buy a spot on your website(e.g. at the top) to put a piece of my own website on it? You have a news website, right? And I also have some news to share.

But what if I rent a space on your website that I can fill however I want? And then, coincidentally, I praise my products on that rented space. How is that different from... other hosting offers?

I "solved" this by adding a fail2ban rule for everyone accessing specific commits (no one does that 3 times in a row) and then blocking the following ASs completely (just too many IPs coming from those, feel free to look them up yourself): 136907 23724 9808 4808 37963 45102. And after that: sweet silence.

How to block ASs? Just write a small script that queries all of their subnets once (even if it changes, its not so much to have an impact) and add them to a nft set (nft will take care of aggregating these into continouus blocks). Then just make nft reject requests from this set.

As the article states, its usually 2:1 women to men so there is also a kind of shortage of basses, its just not as severe.

Its not "building a new package management system", "alpm" is literally the foundation of the pacman ecosystem. They are improving this so they _can_ catch up on packaging tasks.

I'm the same as the sibling commenter, I don't want to have another deb or rpm distro. The AUR wouldn't exist without pacman&makepkg.

Integrity. TLS does prevent man-in-the-middle attacks. For a personal blog, that may not be important but you _do_ get a benefit, even if the encryption is not necessary.

Yeah, everyone in the EU is just working on this one law case. The guy next to me just cooked the meals for the guy that made the paper the case was filed on and now has to take an extended break. /s

People can and will do many things at once, like actually pursuing monopoly issues AND trying to improve the situation for everyone else. Its almost like there is only limited amount of one thing: space on page 1 of media outlets.

Great, now I can compare it with other Zsomethings. But as the post shows, thats just one branch of many naming schemes HP employs. Also: This already is a workstation, how could it _not_ be "ultra"? Why the doubling? Or does "workstation" just mean "something I can work with", including office stuff? In that case, I am very interested what other letters they use and what they're for.

which is done for IPv4-NAT, and for IPv6 firewalls

Are internet routers that do ipv4 NAT usually also doing an IPv6 firewall (meaning they only let incoming connections in if they are explicitly allowed by some configuration)? Maybe thats the point where the insecurity comes from. A Home NAT cannot work any other way(it fails "safely"), a firewall being absent usually means everything just gets through.

Could you share your numbers as well? According to [1], the UK currently needs about 300TWh per year. Lets say we go entirely solar+wind+battery(whatever that means) and assume that battery has to bridge a gap of at most 7 days (meaning no wind and no solar at all during this time, which is at most a few days at a time). This adds up to 300/365*7= 5,8TWh of max capacity. Lets take it safe, round up and say we need 10TWh (which is already not "tens of TWH", but "ten"). [2] Says that grid-scale batteries come at around 350$ per kWh right now. kWh -> TWh is factor 1 billion (10^9), meaning if we want to build 10TWh of storage, it will cost 3,5 Trillion Dollars. Impressive number indeed. But there are multiple asterisks here.

1. This calculation takes into account that there is no exchange with mainland europe and no gas power plants or other sources of power (e.g. hydro or hydro storage). This sharply reduces the need for batteries. 2. Battery costs will fall in the next decades, compared to nuclear, which will take a long time (if ever) until costs will fall.

[1] https://www.statista.com/statistics/322874/electricity-consu... [2] https://docs.nrel.gov/docs/fy25osti/93281.pdf