EFF, Access Now, CDT, and OTI Fight Back Against “Secret” Search Warrants
-
Can the government stop you from finding out it’s been looking through your private Facebook content as part of a “secret” investigation that’s not actually secret? That’s the question raised by an alarming case pending in the Washington D.C. Court of Appeals. Facebook has described the investigation as “known to the public,” and the timing and venue match the January 20th, 2017 Presidential Inauguration protests (known as “J20”), the investigation of which is indeed quite public. But even if the warrants pertain to another investigation, the government should not be allowed to impose gag orders with respect to any information that is already publicly known.
Last week, EFF led a group of civil society organizations that included Access Now, the Center for Democracy and Technology, and New America’s Open Technology Institute in filing a brief demanding that the court apply a stringent constitutional test before enforcing gag orders accompanying a number of secret search warrants. We argued that the First Amendment rarely if ever allows gag orders in such cases, where the government seeks to limit public scrutiny of high-profile and potentially politicized investigations.
Here’s what we know: Facebook is fighting gags associated with several search warrants for user content. The company thinks this case is so important that it sent out a kind of bat signal to groups like EFF. Although the case is under seal, Facebook petitioned the D.C. Court of Appeals (the District’s highest court) to open the proceeding up to amicus briefs and to reveal that Facebook argues that “neither the government’s investigation nor its interest in Facebook user information” is a secret.
Although we can’t be sure, we have a hunch the search warrants are related to the J20 protests. On January 20, the day of President Trump’s inauguration, police in D.C. arrested hundreds of protesters, charging many with felony rioting. Over the last several months, the press has reported on the controversial and wide-ranging investigation into the protests, which apparently included police infiltration of planning meetings. Additionally, in late January, some defendants received notice from Facebook that their non-content account information had been subpoenaed by law enforcement. Their attorneys sought to quash those subpoenas, and we believe the timeline in this case suggests the government sought to get even more private information, including account content, using warrants to Facebook accompanied by gag orders.
Whether or not this case involves the J20 protests, the fact that Facebook says the underlying investigation is already public is almost certainly enough to strike down the gag orders. Government gags that prevent a provider from notifying its users are an example of prior restraints, which are the “most serious” and “least tolerable” infringement on First Amendment rights. As a result, the Supreme Court has said they are only constitutional if they meet the most “most exacting scrutiny.”
But despite the strong presumption against prior restraints, the government gets gag orders all the time. Two of the most commonly used gag authorities are National Security Letters, which EFF continues to challenge on appeal in the Ninth Circuit, and nondisclosure orders issued under the Stored Communications Act, 18 U.S.C. § 2705, at issue in this case.
There are strong arguments that Section 2705 nondisclosure orders are unconstitutional all or nearly all of time. Just in the last several months alone, Microsoft has sued to have Section 2705 declared unconstitutional on its face, while Adobe succeeded in convincing a court to strike down an indefinite Section 2705 gag.
But the apparently public nature of the investigation here makes the gags even more egregious. In order to uphold a prior restraint, a court must be satisfied that is necessary to protect against a “a clear and present danger or a serious and imminent threat” to an important government interest. As we point out in our brief, if the government’s investigation into the Facebook accounts is already known, there’s no way that a gag can prevent any harm flowing from notifying the users and allowing them to challenge the search warrants. We point to examples from two cases in which the Supreme Court struck down gags that prevented the press from reporting sensitive information that had already been revealed in open court.
Although the docket is sealed, it’s our understanding that the court has set this case for oral argument in September 2017. We have requested an opportunity to address the court to represent the public’s interest in ensuring that prior restraints such as this don’t issue without the most exacting scrutiny our court system is prepared to provide. We will keep you informed of any updates we receive.

screen and tmux
A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.
The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road. Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here). |
||
Action | tmux | screen |
start a new session | tmux OR tmux new OR tmux new-session |
screen |
re-attach a detached session | tmux attach OR tmux attach-session |
screen-r |
re-attach an attached session (detaching it from elsewhere) | tmux attach -d OR tmux attach-session -d |
screen -dr |
re-attach an attached session (keeping it attached elsewhere) | tmux attach OR tmux attach-session |
screen -x |
detach from currently attached session | ^b d OR ^b :detach |
^a ^d OR ^a :detach |
rename-window to newname | ^b , <newname> OR ^b :rename-window <newn> |
^a A <newname> |
list windows | ^b w | ^a w |
list windows in chooseable menu | ^a " | |
go to window # | ^b # | ^a # |
go to last-active window | ^b l | ^a ^a |
go to next window | ^b n | ^a n |
go to previous window | ^b p | ^a p |
see keybindings | ^b ? | ^a ? |
list sessions | ^b s OR tmux ls OR tmux list-sessions |
screen -ls |
toggle visual bell | ^a ^g | |
create another window | ^b c | ^a c |
exit current shell/window | ^d | ^d |
split window/pane horizontally | ^b " | ^a S |
split window/pane vertically | ^b % | ^a | |
switch to other pane | ^b o | ^a <tab> |
kill the current pane | ^b x OR (logout/^D) | |
collapse the current pane/split (but leave processes running) | ^a X | |
cycle location of panes | ^b ^o | |
swap current pane with previous | ^b { | |
swap current pane with next | ^b } | |
show time | ^b t | |
show numeric values of panes | ^b q | |
toggle zoom-state of current pane (maximize/return current pane) | ^b z | |
break the current pane out of its window (to form new window) | ^b ! | |
re-arrange current panels within same window (different layouts) | ^b [space] | |
Kill the current window (and all panes within) | ^b killw [target-window] |