@electrospaces What do you mean? It falls under 12333, considered out of US bc both sides are (supposed to be) out of US.
-
-
Replying to @emptywheel
@emptywheel Like here: http://3.bp.blogspot.com/-EwQeboJP_Ac/UloR5CIy4bI/AAAAAAAAAzg/VUr-6yYnvCc/s1600/upstream-silverzephyr.jpg … Yes, but Transit authority is for collection inside the US, unlike EO 123331 reply 0 retweets 0 likes -
Replying to @electrospaces
@electrospaces Oooh. Which is that one from? Transit is loophole created at or before 2001 based on claim of 2 outside US participants2 replies 0 retweets 0 likes -
Replying to @emptywheel
@emptywheel A presentation about Upstream collection, shown on brazilian television, I have all the slides here: http://electrospaces.blogspot.com/2014/01/slides-about-nsas-upstream-collection.html …1 reply 0 retweets 0 likes -
Replying to @electrospaces
@electrospaces Hmm. Maybe I'll have to revisit that one.1 reply 0 retweets 0 likes -
Replying to @emptywheel
@emptywheel I also think we have to make a cut between the legal authorities and the term Upstream3 replies 0 retweets 0 likes -
Replying to @electrospaces
@electrospaces But that says w/in "Upstream" there are 3 legal regimes (2 which are 12333), right? Curious whether XKeyscore used on Transit3 replies 0 retweets 0 likes -
Replying to @emptywheel
@emptywheel Yes, but I think Transit is seen different from EO 12333, like it's in this slide: http://3.bp.blogspot.com/-jnjXwXAZCRk/UloTMQOmFZI/AAAAAAAAA0Q/w4Z9p9EFGLI/s1600/fairview-corpport-raw.jpg …2 replies 0 retweets 0 likes -
Replying to @electrospaces
@electrospaces Do you know date or do I have to check w/people in Brazil? ;-p Since at least 2011 they've been XML tracking data source1 reply 0 retweets 0 likes -
Replying to @emptywheel
@emptywheel Assuming this slide is from the same presentation, it must be as late as March or April 2013... http://2.bp.blogspot.com/-56yPTi4bLv0/UtX7QOxGBsI/AAAAAAAABN0/DyJU5g0sv3Q/s1600/upstream-russia-transit.jpg …1 reply 0 retweets 0 likes
@electrospaces Alright thanks.
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.