They also know that just a tiny tiny percentage of users will go into settings, and even less actually change something.

I used (g)Vim on windows back when I used that

That is good advice, however sadly a lot of install scripts are basically: download this script from us, and pipe it to a root shell.

Imagine if it did get that kind of funding

Sounds like CMOS battery dying/dead on the motherboard. It stores BIOS settings, including password and clock. (Though you really should be using ntpd)

It highly depends on their contract and if they are a big name or not. There is a reason a lot of bands tour though as they make a lot of more money from it than CD sales.

Aha, did not know that the id was unique to that instance. But makes sense as it is just a number and not an uuid or similar so it would have to be synced.

I don’t know anything about the source but couldn’t you just open it in anonymous mode or something via the host’s api? Would be better than browser

WSL is good though, whenever I am forced to use windows I install it.

Sure, but in Perl and other languages there is a difference between "$foo" and '$foo'. In that the first expands the value of foo, while the other doesn’t.

But usually if you need to write stuff in noisy strings, just use printf/sprintf. Or a <<HERE block.

Yeah, you could very well argue that JS and others that use it for weird interpolated strings are the weird ones here.

Yes, it annoys me to no end as well. However it is a hard problem to solve as normally you register a domain to be opened in the app. But due to the fediverse nature of loads of different servers, the list would be very long.

I would be happy if you at least had an option of opening it in Jeroba on longclick or someting

Unless you have . in your $PATH

Having a single centralized source will always give those issues. It can go down either temporarily or permanently. It is all part of the conveniance/single-point-of-failure scale.

In the short run it going down will cause some issues, which can be mitigated by having local mirrors of critical repos. However, moving to another place should in theory be as easy as replacing github.com with gitlab, codeberg, your-local-git-server url, etc (and auth info of course)

Actually testing what will happen if github and/or other services are down and see how your product or build pipeline handles it, is a very good thing to do, but very rarely is it done. It can be easily accomplished by for example adding a drop rule in iptables. Testing for bad things never seems to happen though, and then when it really is a problem nothing works and everyone panics.

I dont like having 90%ish of all git repos all in one handbasket. Even if MS was benevolent, its not good to have all things in one place. A bad actor could take down all of GH and we would be screwed.

That is not how git works though. If github disappeared today it would be a lot of confusion, but the code exists everywhere it is checked out. The owner/maintainer (or anyone really) can just add a new remote and push it. If they use github specific features like issues, they would be lost though.

Something like dpkg -l '*linux-image*' and then see which are installed (ii), and then do a dpkg remove <package name from above> on some, but don’t remove the one you are running now, check uname -a to see.

Keep in mind this is all from memory, so might be wrong

Edit: now I see others replied as well with better ways

For some reason the Debian installer likes to make a tiny /boot so you can only fit 2-3 kernels at most. Try removing some old ones first.

It doesn’t really matter how you measure it, number of flights, duration, distance traveled, etc… No matter which, air travel is by far the safest option. The only other that comes anywhere near is trains. Going by car is bad (though motorcycle is even worse), but so many are afraid of flying that they instead takes the car. Which is among the worst things you could do from a safety point of view.

Humans are awful at accessing risk and chance, one of the reasons casinos and lotteries thrive.

Look at fear of flying for an example, all statistics say you are many many many times over more likely to get into a car accident on your way to the airport, than during the flight. Even when the ride to the airport is usually short and the flight very long. Yet people are afraid of flying, but not going by car. By percentage, there are of course those, rightly so, afraid of cars as well.

Boink! Right into the pillar, again

https://xkcd.com/435/