That list of proposed alternatives shows how bad "master/slave" and "blacklist/whitelist" terminology actually is for technical accuracy. You don't really know what they mean from the name alone. Perhaps over time a more accurate and descriptive conventions will be developed for kernel, and for general SW development use.

I mean, does "blacklist" mean "ignore and block request" or "deny request"? Does "master" in some context mean "controller" or "client"? Etc.

Trolling, or a real question? Oh well, in any case, this is about sea ice. Floating ice. Floating ice melting will not raise sea level, the melted water takes exactly as much volume as the submerged part of floating ice, per Archimedes's Law.

Also, sea ice is thin, measured in meters or at most tens of meters. The sea level rise problem comes from land ice, which is not floating and which has thickness measured in hundreds or thousands of meters. It'll take time for that to melt, so people living in places like large parts of Florida have time to move elsewhere, possibly even without creating a US internal refugee problem, much.

I for one am rather happy with Ubuntu. Can't stand Unity of course, and KDE has never been my cup of tea (have given it a few tries, given up every time, it just didn't do what I wanted). I was really happy when we got Ubuntu Mate, that just does what I want, and gets out of the way.

But with Ubuntu 16.10 I'm really looking forward to try Lubuntu again. The old LXDE is a bit too... lacking in small convenience features. I hope LXQt will improve on that (plus, I'm a Qt fan in general). If it's a let-down (beta 1 still has LXDE, I believe, so not trying it out yet), I suppose Ubuntu Mate will continue to give me the naughties UX.

Everything is redirected fusion, even including geothermal, because fusion is how radioactive elements in Earth were made. Only non-fusion energy production mechanism I can think of is gravity, in other words tidal power (also black hole accretion disks, but we don't have any, yet).

It only takes a tiny part of humanity to retain/rediscover that adventurous spirit. Moon was visited by combined science of nations with... I CBA to check so I'll say well under half a billion people, and with a lot less of accumulated knowledge than today. Humanity is not one collective, and I dare say it'll never be. 90% of people might embed themselves in VR and starve to death, but that still leaves almost a billion people who don't want to. Natural selection FTW.

And that is why geeks rarely make good marketing or management people. Because these soft people things matter, even when it doesn't seem to make logical sense. Things rarely succeed on technical merits, appearances (including such small things like file name extension and mime type) matter too.

Anyway, the cynical me suspects, that the extension was changed just to get publicity for the new format, and political correctness was just an excuse. Still, if this raises awareness of the format, I'm not going to blame them for doing it.

You're right, it's worse than just ironical. One camp is saying "we don't like this". Other camp is saying "we want this the way other camp doesn't like". I'm not sure how you go about compromising in a situation like that. So, a hint: When ever you notice the feminist/SJW/PC camp to have the more reasonable position, it's time to re-evaluate the situation. No matter how good "pro-bro movement" sounds, this is not the smartest battle to pick.

You don't have to check anything. But if someone does check something with someone, you should have some actual, concrete reason before you criticize them for checking and then changing something.

But if you are creating a word (or acronym/shortening which will be used like a word), which you wish to be universally used, I do think it is wise to think about existing meanings of the new word. Case in point, Gimp has probably suffered from the alternative meaning of the word (just a guess, no reference), with slightly less developers and users and positive publicity. It may be stupid, but it's the world we live in, and martyring oneself as opposer of excessive political correctness doesn't make much business sense.

Um, please re-read what I wrote. Because either you totally misunderstood my post (pointing out the hypocrisy of criticizing the change of extension), or I misunderstand your reply to it.

Looking at all the comments, I hope everybody realizes the irony here. You can't even change a file extension without a bunch of people getting their panties in a bunch :D

The rational thing is to change the extension to something neutral. It's just a technical detail and does not matter that much, so it's sensible to just be polite to those idi... humans who feel there is a problem.

Of course once you're polite, you get a bunch of other idi... humans saying they find the change of the extension without a technical reason offensive, and would like it changed back, failing to understand that they want it changed back for an equally non-technical "feel-good" reason.

Oh the irony.

Obviously it would be different if there was a good technical reason to demand just that one particular extension, but there isn't. It'd also be different if the new extension (instead of the act of changing it) was potentially as offensive.

It's open source and trivial to patch. And a distro which shipped something like that unpatched would be dead in a few days. Also it would result in immediate fork. Just observe what happened to MySQL and especially OpenOffice.

I recently switched to running an Ubuntu variant on my old work laptop (top-of-the line from 2013), and running Windows as VirtualBox guest for stuff like MS Office and Windows development. Works very nice, all you need is enough memory and an SSD and a decent processor.

I wouldn't even call it elaborate. But it is different, so it is distinct extra security layer which offers unique protection. Cracking it basically requires that attacker can sniff low level traffic between client and server, and knows to watch for port knocking sequences. The important property of port knocking is, attacker without privileged knowledge doesn't know if server expects port knocking sequence, and attacker doesn't know if they failed critically and got that IP blocked. So it effectively blocks even remote detection of a running ssh server, let alone actually trying to break into one, while still allowing authorized access from everywhere.