Yet all the browsers consider unencrypted connections more secure than connections encrypted with a self signed certificate.
No. They consider that entering or following a link to an 'https:' URL means that you expect a secure connection. In this context, a self-signed certificate that has not been whitelisted is an error.
MPEG set up the MPEG-LA that serves as a patent pool
No, they did not. There are a lot of the same players there, of course, but they have no formal relationship.
This is good news; I'm glad to see at least one misogynist leaving Wikipedia.
Sadly, it still seems to be run by a bunch of young white guys fighting for the importance of hosting porn and claiming the consensus of their privileged group is "neutral". ArbCom has censured admins for fighting back against lies spread by GamerGate, with a ban that may apparently prevent them fixing any abusive edits to articles about women.
99% of the resumes that HR sent me
Maybe part of the problem is letting HR filter them first. If they don't know how to spot bullshit then they may effectively favour the liars.
This is why I claim it's spyware. Sure, you can turn most of those things off, but the intent of turning them on by default is to capture that information from most users.
you know what I don't use every day? Debian, Do you know why? People like you. I've been using Linux for 20 years and it's people like you that get in the way of progress.
I'm not getting in the way of anything. The kernel is team-maintained and I've explained how this change can be made without my help.
I do dislike Chrome and I'm not going to pretend otherwise. Aside from its being spyware (in its default configuration), the Chrome/Chromium developers have previously added requirements that make Chromium unsupportable in Debian 7. We could add this kernel feature now, but I strongly doubt that will be sufficient to keep Chrome/Chromium running on Debian 8 until its EOL.
Please note that I am not NAKing the change, but I'm also not going to be the one to make it happen.
"When it breaks, you're fucked", just like anything you run as pid 1. Except you can still use the init= command line parameters to run something different (or possibly break= to stop in the initramfs).
"Obsoletes 20-30 years
"No real new features" because all its new features, are somehow not real according to some AC?
"Virtually untested" except by every major distribution?
Insightful, my arse.
or have a problem with it randomly flipping to headphones on loud parts on another machine
Because obviously broken jack detection is the fault of the daemon, not the hardware or sound driver.