Fonts seems to be what does it. With many programs coming with extra/special fonts, it quickly narrows the users down based on what they have installed.

Of course, for fonts that only come as part of a software package but install fonts as system fonts (why?), it also tells remote sites what you have installed, which is an additional privacy concern.

If i could see a reasonable use for one at home, I might consider buying one, but I don't, so I don't.

3D printer owners: What is the most useful thing you've printed, how long did it take, and how much did it cost (factoring in the purchase price of the printer divided by how many successful prints you have actually done)?

I don't think you understand how evolution work. It's not a synonym to evolving. How strong we are now does not say anything about how strong our descendants are going to be unless we have predation.
Each generation introduces new mutations - a small number of mildly beneficial, somewhat more mildly detrimental, and most of all highly detrimental. The latter are usually not carried to term. The mildly detrimental, on the other hand, are those that are of concern. Unless they get culled, they will propagate, and accumulate with more mildly detrimental mutations from the next generation, and even more from the next, and so on. The net result is a population evolving into degeneration.
How strong we are as a species now does not ensure that the following generations will be as strong. They will be adapted to a life with reliance on medical technology and medicines to counter that they are unable to survive on their own. A few massive solar flares, and we are back to the stone age. Except that we may not have a population that can survive those conditions, because there has not been any predation, and detrimental genetic mutations have been allowed and encouraged to spread through the population.
Much unnecessary suffering in the future is the result of avoiding it now. What we're doing is peeing our pants to keep warm. It feels good right now.

Someone better tell BMW that, then.
Mine has a row of buttons 1-6 that can be reassigned to whatever is on the screen by holding it in for a couple of seconds. So for me, 1 means "Take me home" and 3 means "NIght view on/off". Handy, and especially so because they're physical buttons, right next to my fingertips on the gear shift.
Operating a touch screen, on the other hand, requires you actually looking and stretching. Not good.

And there is where "play ball" comes in.
For example, xfs is, as far as I can tell, the only file system for Linux that supports realtime, and even that took about a decade to be ported from SGI to Linux. If you need to have your commit done within a certain time span, it doesn't help much if the OS can't fulfill that because it has to do a callout to a device that isn't rt capable.
Similar for IO devices - Serial and Firewire can play ball, but USB cannot. Most HDDs with a fixed rotational speed can, and while SSDs theoretically can, in practice they do not (an infrequent shuffling of blocks and re-initializing a sector can take a second or more, so even though the average speed is immensely faster than a HDD, most of them are unusable for rt unless placed behind a battery backed disk controller.)

Yeah, I would like to see more effort going in to LinuxRT. For now, I think QNX is probably the best bet, but I hope LinuxRT would gain more traction. What we do not need is even more non-predictable behavior (pulseaudio, anyone?), but consistency. Let Moore's law and good programming take care of speed, not tweaks that increases the average speed at the cost of even less predictable worst case.

We have - they're called "cars".

Yes, QNX has been around for a long time.
\What most people don't get is what a realtime OS is, and why it matters. Other multitasking OSes are generally "best-effort" OSes, but in a realtime OS, the whole scheduling system is based on giving guarantees, making sure that things happen within a certain time frame or a certain order.
The overhead is huge, which is why you don't se RT on any normal desktops or servers, but in something like a car, airplane or hospital device, you would rather know that 100% of the requests get served in 100 ms, than having an average time of 10 ms, but a worst case time of 1000+ ms.
If you know the worst case, you can program your systems to operate within them.

Linux does have a RT version, in part supported by Ingo Molnar and Theodore Ts'o, but it does not see heavy use. In part, this has been because for a realtime OS to be successful, all the parts have to play ball, not just some. And in part it is because a realtime OS is quite a bit slower on average, and most regular users would rather have improved average speeds than improved worst-case.

But for a car? Give me a realtime OS any day. I don't want traction control to cut in a tenth of a second too late because the kernel was busy doing garbage collection, time synchronization, and handling an urgent warning that the oil temperature was too high.

You're saying that as if it's purely a bad thing. Sure, it's a tragedy when a parent loses a child, but it's a boon to the herd when the weakest is culled, and their genes leave the gene pool before they get to procreate.
If we allowed diseases to cull, say, 10% of children, future generations would be stronger.

As it is, vaccination is a means to allow more bad mutations to survive and cause pain and suffering in the future. I think everyone who do give their children vaccines are selfish bastards who wants to increase the odds of their own children surviving even if it means that their children or grandchildren might suffer. People are concerned about the here and now, and refuse to think generations ahead.

Think of future children, not just the present ones. Let predation happen, to ensure that the good mutations are rewarded and the bad ones are not.

How about Depeche Mode's "Jerome, Percival, Jesus"?

It also includes the famous line "Recharge and suck face!".

I remember when Americans thought pre-WWII German security was outrageous. Papieren, bitte (Papers, please)!

Americans were proud that they could go anywhere they wanted without being stopped and harassed or even asked who they were, and made fun of those not so lucky.

These days, if Americans were only asked for papers, they would be confused.
It has become a land of chickenshit cowards who shiver in fear, and behave like cattle being prodded.

No, the terrorists have not won, but we have lost far more than what the terrorists could have hoped for: Our hearts.

What I don't get is that she changed from a first name that was a surname to a place name which by definition is unisex in nature. It's like changing your first name from Davis to Islington.

Anyhow, the point of a statue would, I presume, be to depict what people remember and recognize. We don't see many statues of Rosa Parks, Elvis, Jo DiMaggio and Neil Armstrong from their latter years, for example.

No, it cannot. You probably think it does because of files that save both the private key and public key in the same file, like your typical .ssh/id_dsa file does.

A cert does not have to include the public key. It is often included for convenience, but it is enough that it contains a signature for the key and description on how to get it.
For large keys, or repeated traffic, including a short URI can be far more bandwidth friendly and time saving than including it - if the recipient already has the key, it does then not need to be re-sent.

I see what you're trying to tell him, but you make it sound like there is a technical difference between private and public keys.
They are really just two keys of a key pair, and anything locked with one can only be unlocked by the other. Which one is named "private" and which one is named "public" does not really make a technical difference.
It's customary to have the shorter of the two keys be designated the public key, and also common to store a copy of the public key with the private key for convenience, so it can be extracted on need. But that's not a technical difference.

A certificate is just a piece of data signed with a private key.
A key chain is just a bunch of public keys with certificates, one of which you're supposed to trust, and then you let that trust be inherited to anything below it. Inherited trust has always had its flaws, and signing does not change this. Just because you trust Anna and Anna vouches for Bridget, doesn't mean you should trust whoever Bridget vouches for, and whoever those in turn vouches for. That's like betting that friends of friends of friends will always be good people (or even who they claim to be).

It depends on what kind of people they have hired. Those who actually take an interest and read underground news multiple times a day are more likely to have fixes in place long before the need is evaluated, determined and requested up and down the corporate chain.
Even if it should break with policies to patch without permission, a halfway decent sysadmin would invoke emergency powers in cases like this, and do the paperwork later.

I can understand that.
What I do not understand is NASA having a need to know who I am and whether I have been treated for hemorrhoids, dog bites and male pattern baldness, or why my girlfriend visited Planned Parenthood.