Google Will Survive SESTA. Your Startup Might Not.
-
There was a shocking moment in this week’s Senate Commerce Committee hearing on the Stop Enabling Sex Traffickers Act (SESTA). Prof. Eric Goldman had just pointed out that members of Congress should consider how the bill might affect hundreds of small Internet startups, not just giant companies like Google and Facebook. Will every startup have the resources to police its users’ activity with the level of scrutiny that the new law would demand of them? “There is a large number of smaller players who don’t have the same kind of infrastructure. And for them, they have to make the choice: can I afford to do the work that you’re hoping they will do?”
Goldman was right: the greatest innovations in Internet services don’t come from Google and Facebook; they come from small, fast-moving startups. SESTA would necessitate a huge investment in staff to filter users’ activity as a company’s user base grows, something that most startups in their early stages simply can’t afford. That would severely hamper anyone’s ability to launch a competitor to the big Internet players—giving users a lot less choice.
Sen. Richard Blumenthal’s stunning response: “I believe that those outliers—and they are outliers—will be successfully prosecuted, civilly and criminally under this law.”
Given the extreme penalties for under-filtering, platforms would err in the opposite direction, removing legitimate voices from the Internet.
Blumenthal is one of 30 cosponsors—and one of the loudest champions—of SESTA, a bill that would threaten online speech by forcing web platforms to police their members’ messages more stringently than ever before. Normally, SESTA’s proponents vastly understate the impact that the bill would have on online communities. But in that unusual moment of candor, Sen. Blumenthal seemed to lay bare his opinions about Internet startups—he thinks of them as unimportant outliers and would prefer that the new law put them out of business.
Let’s make something clear: Google will survive SESTA. Much of the SESTA fight’s media coverage has portrayed it as a battle between Google and Congress, which sadly misses the point. Large Internet companies may have the legal budgets to survive the massive increase in litigation and liability that SESTA would bring. They probably also have the budgets to implement a mix of automated filters and staff censors to comply with the law. Small startups are a different story.
Indeed, lawmakers should ask themselves whether SESTA would unintentionally reinforce large incumbent companies’ advantages. Without the strong protections that allowed today’s large Internet players to rise to prominence, startups would have a strong disincentive to grow. As soon as your user base grows beyond what your staff can directly police, your company becomes a huge liability.
But ultimately, the biggest casualty of SESTA won’t be Google or startups; it will be the people pushed offline.
Many of SESTA’s supporters suggest that it would be easy for web platforms of all sizes to implement automated filtering technologies they can trust to separate legitimate voices from criminal ones. But it’s impossible to do that with anywhere near 100% accuracy. Given the extreme penalties for under-filtering, platforms would err in the opposite direction, removing legitimate voices from the Internet. As EFF Executive Director Cindy Cohn put it, “Again and again, when platforms clamp down on their users’ speech, marginalized voices are the first to disappear.”
The sad irony of SESTA is that while its supporters claim that it will fight sex trafficking, trafficking victims are likely to be among the first people it would silence. And that silence could be deadly. According to Freedom Network USA, the largest network of anti-trafficking advocate organizations in the country (PDF), “Internet sites provide a digital footprint that law enforcement can use to investigate trafficking into the sex trade, and to locate trafficking victims.” Congress should think long and hard before passing a bill that would incentivize web platforms to silence those victims.
Internet startups would take the much greater hit from SESTA than large Internet firms would, but ultimately, those most impacted would be users themselves. As online platforms ratcheted up their patrolling of their users’ speech, some voices would begin to disappear from the Internet. Tragically, some of those voices belong to the people most in need of the safety of online communities.
https://www.eff.org/deeplinks/2017/09/google-will-survive-sesta-your-startup-might-not

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] |