iEvil? Or perhaps in this case XEvil One, the perfect gift for someone stll using XEvil 360.

I don't care about whether you can prevent sharing with your friends on FB it whatever, what I care about is me not having to alter my network settings so that if I give you access to my WiFi network, you sharing MY network information with the pwoe you're "friends" with.

There's a doodad on my AP that let's me disable a feature on a connecting WiFi client?

So, instead of posting multiple times hire they article misrepresents the feature, quit being a shill and explain how exactly it works.

That isn't the issue. The issue is YOU being able to share MY WiFi key because I was dumb enough to let a Windows 10 user on my WiFi network. This is akin to me giving you the keys to my house so you can housesit, and you getting a hundred copies cut and distributing them to a bunch of people you know.

This is from the company that thought having users run as root user using a browser that would automatically install unsigned executables and libraries from the Internet was just the bestest idea ever.

Thank you for being a friend,
And sharing WiFi passwords there and back again.
You're giving me the WiFi key of your favorite restaurant.

And if they came to your dorm,
Invited everyone you knew,
You would see the ugly guy at the back downloading kiddie porn,
And the FBI would raid you singing "Thank you for filling our jail!"

Inflammatory Mode On: Why in the fuck would even want to opt-in to such a service? If it's private WiFi, it's likely to be at my home or my workplace, and in either case I absolutely do not ever want to share that over fucking Fuckbook, Twatter or whatever stupid lame-ass soshial neshworking crap site becomes the next biggest and greatest.

Rational Mode On: Now let's imagine that my organization has a private WiFi hotspot available for employees and a few others. I do not ever want to have those keys shared outside that group, nor should I have to change MY network with an "_optout" on the end of an SSID. I would consider that a breach of security. Sure, I'll probably be able to disable Windows devices that are domain members via GPO, but if they're not actually devices belonging to the organization, or "Pro" versions of Windows where it even knows what the hell Active Directory is, then MY network is being compromised by this service.

This is just a plain bad idea, whether you're being reasonable or inflammatory.

You also don't have to worry as much about massive storms with 300km/h winds. I don't know about you, but I'm not sure I'd want to be hanging out in a large zeppelin when a wind like that nailed me.

And here's somebody who doesn't think solipsism is utterly pointless and nihilistic philosophy, and actually thinks researchers should adopt it.

That's not the new Microsoft, that's the Microsoft of the last decade.

Also consider that in most markets, Windows Phone is closer in phone marketshare to iOS than iOS is to Android. That's not saying a lot. But WP is definitely at the #3 spot, and the way this market is... if they can find that itch to scratch, things could change within the course of two or three years.

Which is like bragging about Pluto because it's closer to the Sun than to Proxima Centauri.

Third place in the mobile market is a dubious distinction, at best. In reality, Windows phones are irrelevant, but only slightly less irrelevant than, say, BlackBerry.

Because moving from one proprietary language/library ecosystem to another proprietary language/library ecosystem is somehow an improvement.

Fuck them both. We have truly open ecosystems like C++, and I would encourage any sensible developer going forward to move away from the likes of Java and the .NET ecosystems, now that the Supreme Court has essentially turned them into perpetual litigation machines.

But cleanroom implementations are meaningless if copyright can be asserted over the API. Clean room implementations only work because it has been generally understood that an API itself is essentially a directory listing, like a phone book, that in and of itself does not constitute some sort of creative work. Before the Oracle case, it was assumed that it was the code itself that constituted the intellectual property. But that is now apparently no longer true, and thus the Win32 API has gained the same level of protection as the source code.

If this stands, and is not corrected either by a lower court or by Congress, no one will every try a clean room implementation of any non-free library again, because there's a real likelihood that you would find yourself sued into oblivion for breach of copyright.

Wine may be safe because MS is being constrained by future potential anti-competitive suits, and of course Samba is protected because of a deal cut with the EU. But from this day foreward, clean room implementation of proprietary APIs, and I assume any other software spec (document format, communications protocol, etc.) will have absolutely no protection under the law.

Would you contribute to a future project like Samba or Wine now?