413 karma · joined September 9, 2010
From this and other assertions made in the Bloomberg piece, it seems very fair not to read this as conventional patch management, but as a special arrangement with intelligence agencies. And to read this as, yes, from time to time Microsoft's help does get the NSA into Windows boxes.
Now, we all know that tech reporting often leaves something to be desired. If you're saying the officials were wrong or quoted out of context, then that's fine. But it's not reasonable to dismiss this out of hand as some outlandish Alex Jonesian conspiracy theory.
BTW, obviously I'm not saying that Microsoft's bug bounty program is an NSA plot. It's a good program that every major company should have. I'm also not saying that they don't share bugs with other partners ahead of time, they obviously do. Just that from what the sources in this article (which again, did not originally appear on infowars.com) say, Microsoft does have a special arrangement with intelligence agencies and from time to time has shared bugs knowing they might be exploited by said agencies. The bug bounty program could find the sort of bugs that would (incidentally) be shared as part of this arrangement.
[edit]Link for reference, if anyone missed that particular news: http://www.bloomberg.com/news/2013-06-14/u-s-agencies-said-t... [/edit]
The fact that it's very unlikely it was created as part of some conspiracy doesn't mean that it's impossible to compromise a Tor user's anonymity. I'm not an expert but as far as I know the most credible large-scale attack against it is still the one described in this paper: http://wesscholar.wesleyan.edu/cgi/viewcontent.cgi?article=1... . To be successful, it requires controlling a very large proportion of Tor's entry and exit nodes.
But even on a simple blog, bounce rate is a useful stat. Many bloggers don't just want people to come from Hacker News and stay for one article, they want these visitors to click around to related entries after they are done reading. Bounce rate gives a good idea of whether this is happening or not (unless you automatically count almost all visits as non-bounce by triggering an event after a brief time interval).
Although Mailchimp has a lot of users, it doesn't make sense to generalize conclusions from one SaaS business to the whole web. A private SaaS dashboard is a different use case from most consumer websites, where the goal of logging in with Twitter or Facebook is generally to attach your public identity to your posts or profile on the site, not merely to expedite login. And frankly, a private dashboard is a very strange place to add social login buttons in the first place. Although the "what login did I use?" issue comes up on consumer websites that make good use of social auth, it does so less often, because if you connected a third-party account to one of these sites, you did it for a reason and are more likely to remember.
The British call drunk driving "drink driving", which is nonsensical. Based on this fact alone, the rest of the English-speaking world should disregard their writing patterns when determining correct usage.
I don't want to just hate on open-source graphics software - a lot of amazing work has gone into GIMP, it had fun things like content-aware resizing before Photoshop did, but Adobe has 1000X the resources to invest in usability and they've used those resources well.
The advice people are giving to just jump in the cab applies in the case where the driver's off-duty light is not on, but the rider looks like they're going to some part of Brooklyn (or wherever) that the driver doesn't want to go, and the driver is wrongly being selective. The situation of having to just jump in the car has never come up for me in Manhattan with an on-duty car, it has before in Brooklyn though.
This is definitely more hairy to use than if the language supported it natively, but not so bad, and can be implemented in a very lightweight way (this approach http://daemon.co.za/2012/04/simple-async-with-only-underscor... is a few lines of code on top of Underscore.js which a lot of sites are using already).
(PS: sorry if OP's article already mentioned this stuff, I can't load it at the moment)
If you sign in to Klout, you'll get fairly in-your-face pitches to invite friends to it. Should you choose to send such an invite, the friend you sent it to would have to respond to this and manually OAuth their account. Similarly, sharing an action taken on Klout to Facebook or Twitter is a manual process. I don't remember seeing any "dark patterns"* at work at all here - nothing is sent automatically, there's no sneaky small print or prefilled checkbox, etc.
It seems the author is also confusing account creation with the service requesting and storing public data from Twitter. Twitter's own privacy policy (https://twitter.com/privacy) is clear re: content being available to search engines and via API. If people do not want their Tweets to be available to search engines and third-party sites that comply with Twitter's policies, they can set their Twitter profiles to private, or can use a service that does not have such an open ecosystem.
The potential privacy compromise here is that people who might've not wanted the user to know that they had them in their synced-to-Facebook phonebook, or may have a secret profile connected to said phonebook, could be unwittingly exposed to the user. As your example of the friend with the hidden gay profile shows, that can have alarming results. I'd say that example's bad enough and worth addressing (even if the answer is just better messaging about how synced phonebooks can be used) and that the PI/law enforcement talk is just muddying the waters.