Weird line of questioning by Sen Graham.
-
-
Replying to @pwnallthethings @senjudiciary
The answer to Sen Graham's question is "no".
1 reply 0 retweets 9 likes -
Replying to @pwnallthethings @senjudiciary
But he's really confusing the issues.
2 replies 0 retweets 8 likes -
Replying to @pwnallthethings @senjudiciary
Brooker from ODNI saying they'll explain why they technically can't provide a count of a USP incidental comms in closed setting
1 reply 2 retweets 5 likes -
Replying to @pwnallthethings @senjudiciary
Sen Cornyn making the fair point that even if the number were easy to compute, it would be a widely misunderstood metric in any case.
2 replies 0 retweets 4 likes -
Replying to @pwnallthethings @senjudiciary
A lot of this misunderstanding stems from the widespread (wrong) assumption that all incidental info necessarily implies a privacy invasion
2 replies 3 retweets 12 likes -
Replying to @pwnallthethings @senjudiciary
From: Alice, in France To: Bob, in Syria [US Actor 1] was good in that film Is [US Actor 1]'s privacy really impacted by this collection?
3 replies 3 retweets 16 likes -
Replying to @pwnallthethings @senjudiciary
This is a strawman. Privacy advocates aren't complaining about that. They're complaining about things like this: https://www.washingtonpost.com/world/national-security/in-nsa-intercepted-data-those-not-targeted-far-outnumber-the-foreigners-who-are/2014/07/05/8139adf8-045a-11e4-8572-4b1b969b6322_story.html?utm_term=.29311367ad0f …
1 reply 0 retweets 1 like -
Replying to @JakeLaperruque @senjudiciary
There are certainly cases where incidental USP collection relates strongly to the privacy of the USP. But bulk of them (by volume) don't.
1 reply 0 retweets 3 likes -
Replying to @pwnallthethings @senjudiciary
I don't know how you can make that assertion about quantity, and even if it's *only* hundreds of thousands that's still highly problematic
2 replies 0 retweets 0 likes
Bulk, by volume, will be US company names (tho cases like a star are true too).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.