NAFTA's Digital Trade Chapter Could Be Finalized Next Month

  • The fifth round of negotiations over a modernized North American Free Trade Agreement (NAFTA) wound up last week in Mexico. Following conclusion of the round, Mexican Trade Minister Ildefonso Guajardo told reporters that he hoped that the next round, to be held in Washington, DC in the week of 11 December, could see sufficient progress made that the agreement’s Digital Trade chapter could be closed… all before the public has seen a single word of it.

    The history of such predictions leads us to suspect that this may be an optimistic timeline, but the fact that the Minister made it at all does go to confirm that the Digital Trade chapter is seen as being uncontroversial in the negotiations. But it isn’t unimportant. The provisions likely to be found in this chapter include some topics that are critical to the digital economy.

    Some of these rules, depending on how they are worded, could be beneficial for the rights of users online. In particular, harmonizing at a higher level of safe harbor protection for platforms would boost protection for freedom of expression and human rights online, at the same time as helping online innovators and startups. In a joint letter sent to the USTR earlier this month, startup advocacy group Engine made a case for the inclusion of broad intermediary liability rules in NAFTA’s Digital Trade chapter:

    Modern technology allows millions of people worldwide to reach even the smallest of online platforms. This model only works because U.S. law enables companies to host or serve as a platform for huge volumes of transactions, communications and other activity by third parties. NAFTA modernization should include provisions to prohibit governments from forcing online services to be gatekeepers for content on the Internet.

    But other rules proposed for NAFTA’s Digital Trade chapter are more troublesome. For example, rules on domain names belong at ICANN and should be kept out of trade agreements. Rules on issues such as the circumstances in which countries can limit the flow of data across their borders or can require the placement of servers on domestic soil, and rules limiting regulators from requiring access to the source code of imported products are being set through trade agreements.Rules on critical areas such as data localisation and transfer should be included after careful consideration and only following public input into the development of those rules.

    While limitations on data flows and demands for source code can be used for protectionist purposes that don’t merit our support, there are also legitimate reasons why banning them outright would be a bad idea. In particular, it is important that countries retain the flexibility to make and enforce personal data protection laws, even if these do to some extent inhibit the free flow of such data in commerce. We should also think twice about preventing countries from reviewing the source code of imported products, when this could be used to address the real problem with insecure devices posing security and privacy risks to users.

    The NAFTA negotiating countries shouldn’t rush in to closing the Digital Trade chapter of the agreement before these nuances have been addressed in an inclusive, balanced, and accountable way. That includes receiving input on these provisions from those who know their subject better than trade negotiators do—including privacy experts, cybersecurity professionals, and representatives of Internet users. But unfortunately this is not possible while text proposals and consolidated drafts remain secret, and while the Trade Advisory Committees conduct their work behind closed doors, subject to confidentiality obligations.

    EFF and other public interest advocates are doing the little that we can in these difficult circumstances to inform negotiators of our concerns, but we have no way to know for sure whether they are listening. If it is announced during next month’s negotiation round that the Digital Trade chapter of NAFTA has been closed before we’ve even seen it, the negotiators and their political masters will stand accountable to the public for any bad choices that they have made.

Tmux Commands

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
re-attach a detached session tmux attach OR
tmux attach-session
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]
  • Use the same script for updating/ upgrading

    Make sure to change the versions to the latest releases:

    #!/bin/bash set -e bpcver=4.2.1 bpcxsver=0.57 rsyncbpcver=

    Scroll through the script, know what you are doing.

    Uncomment the upgrade section(s) and comment out the install section(s)

    read more
  • Again running smartctl after all is said and done:

    smartctl --all /dev/sda

    ddrescue-smartctl-after-rescue.png ddrescue-smartctl-2.png

    Yet an old drive in itself, I run the wheels off of them, and monitor regularly as anyone should.

    read more