I don't have any choice. If I give my friend my WiFi password, and he happens to be running a Windows 10 phone, suddenly my WiFi password is shared with all of his contacts. So now every time someone is over my house and asks for the WiFi I'll have to ask them if they currently own, or ever intend to own a windows phone. And then, assuming they understand the question, I have to sound like a paranoid asshole and say "no" if they answer in the affirmative. My other option is to rename mySSID to end in _optout and update all of my devices because Microsoft chose to implement a ludicrous, criminally insecure, "feature"?

Apple's encryption is end-to-end. They do not hold the encryption keys and thus can't share your passwords with anyone: Even if some brain dead middle manager had the idea to clone this feature, it would be impossible for them to implement without totally changing their security model.

While not drones per se, there are ground based weapons systems that are capable of automatically engaging human targets. Whether they are deployed in this configuration is probably something that the users aren't advertising.

I just bought a season of Archer from Amazon (I am also a Prime subscriber), and I was dismayed to find out that each episode is bracketed by 2-5 minutes of trailers for other FX shows.

It's only been since Java 1.8 that you've been able to inline a default implementation along with an interface declaration. Before 1.8, the only legal members of interfaces were abstract method declarations and static final constants.

Everyone who's ever typed:

int main(int argc, char* argv[])

Better get their check books out and start sending royalties to Dennis Ritchie and/or AT&T.

Assuming you already have svn installed and copy of Apache httpd with mod_dav_svn and you are are running on some flavor of *NIX.

Create an svn repository somewhere, eg.

# svnadmin create /opt/svn-repo

Create a password for your repo, replace username and password as appropriate

# htpasswd /opt/svn-repo/conf/htpasswd USERNAME PASSWORD
# chmod 640 /opt/svn-repo/conf/htpasswd

Fix the permissions of the repo so that the user that httpd runs as can write to the repo database. Replace www with whatever the appropriate user is:

# cd /opt/svn-repo
# chgrp -R www .
# chmod -R g+r .
# chmod -R g+rwX db locks
# find db locks -type d -exec chmod g+s '{}' ';'

Open httpd.conf and add/uncomment the following lines in the LoadModule section:

LoadModule dav_module modules/mod_dav.so
LoadModule dav_svn_module modules/mod_dav_svn.so

At the very bottom of your httpd, add a location for your repository:

<Location /repo>
    DAV svn
    SVNPath /opt/svn-repo
    SVNAutoversioning on

    AuthType Basic
    AuthName "Subversion repository"
    AuthUserFile /opt/svn-repo/conf/htpasswd

    Require valid-user
</Location>

Restart apache and then test your config:

    # svn ls http://localhost/repo --username USERNAME --password PASSWORD --no-auth-cache
    #

No errors means everything is working.

See the manual for instructions on mounting the WebDAV share with various clients. Note that Windows is kind of problematic for this out of the box and you may need to use a third party file system driver such as NetDrive.

The Declaration of Independence is a piece of rhetoric and not a legal document.

But we do it for other products. We poison industrial ethanol so the government doesn't tax it at the recreational rate. We spike opioid analgesics with non-therapeuticly high levels of acetaminophen to discourage recreational use. If we're willing to poison things that are sold legitimately, why wouldn't we poison something that is illegal? I'm not saying it wouldn't work for other reasons you cited, but we've already stepped over the line as a society of intentionally poisoning things to discourage their use.

It's not that strange. More risk means there is a higher threshold for committing violence.

No it's not true. The FDA forced a walnut distributor to remove some unsubstantiated health claims from the packaging of their products: http://www.fda.gov/iceci/enforcementactions/warningletters/ucm202825.htm. People making false claims about the health benefits of their products (e.g. selling grain alcohol mixed with an emetic as cure-all) was the whole reason the FDA was created.

Walnuts are not classified as a drug, but if you claim they cure cancer without a good double blind study to back you up, you will be called on your bullshit. This is a good thing and is an example of a government agency exercising it's regulatory authority within the appropriate ambit. There are plenty of other real government conspiracies both covert and flagrant to worry about without inventing more.

If you download the "server" JRE (actually it's a full JDK, I don't know why they label it that way), it comes as a simple tarball. It doesn't interact with the registry, doesn't install the browser plugin -- it's just full JDK distribution. I'm guessing they are locked into a multi-year co-marketing deal with Ask for the consumer distribution. I always just download the server version, unzip, and add C:\jdk1.x.y_z to my PATH and I'm done.

Was he walking through the school grounds or just passing by on the sidewalk? Big difference.

You have no idea what goes into an SF86 form, do you? It's your whole life for at least the past 7 years, including SSN, bank account numbers, past addresses, KAs, relatives. It'd be one-stop shopping for stealing every cleared persons identity if it were public. Also, not all cleared personnel are employed by the government.

Those are local cops, for the most part. If the local and state PDs were as thorough as the feds, we might have fewer issues as they might catch more potential problems through psych screening.

Using the API doesn't invoke the GPL -- it's actually the linking process. When you link against the kernel, your binary becomes a derivative work partially based on the kernel. Since the kernel is covered by the GPL, creating any derivative work from it requires you abide by the terms of the GPL. I doubt any FSF lawyer would have anything negative to say about cloning a project's public API in order to create a completely new implementation under a different license.

Another example: If I created a GPL program with an API that did not make it necessary to link against a library to use - e.g. you talked to my program via IPC or a wire protocol like SOAP, then you could utilize my API all you wanted without triggering the GPL. You could distribute your program that uses my API under whatever license you want.

This is why it's common for software that has a GPL server component to distribute the client driver libraries under the LGPL. Modifications the the server or the client driver itself must be shared, but programs that merely link to the driver may remain proprietary.

It's not that weird. The IOS messaging app shows messages organized by sender with the most recent message summarized under each sender's name. If a message is being cropped incorrectly and causing the crash, then wh3n another message comes in from that sender, the new message will replace the problematic one in the summary.