Noisebridge - User contributions [en]

Aaron projects

2013-11-09T22:35:02Z

192.54.222.3:

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Aaron's writings, history, timeline ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting related projects included where appropriate on Wikipedia
*: James (user:dervorquil, Cambridge)

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Mozilla: Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:34:46Z

192.54.222.3: /* Aaron's writings, history, timeline */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Aaron's writings, history, timeline ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting related projects included where appropriate on Wikipedia
*: James (user:dervorquil, '''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Mozilla: Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:34:31Z

192.54.222.3: /* Aaron's writings, history, timeline */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Aaron's writings, history, timeline ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting related projects included where appropriate on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Mozilla: Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:34:15Z

192.54.222.3: /* Personal archive */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Aaron's writings, history, timeline ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Mozilla: Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:33:53Z

192.54.222.3: /* Essence */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Mozilla: Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:33:40Z

192.54.222.3: /* Essence */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.

Aaron projects

2013-11-09T22:33:26Z

192.54.222.3: /* Essence */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Essence ===
* Mozilla is working on many new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users. There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're proposing to fill this gap with an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model "[https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9 '''Essence''' (project details)]"
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.
* For more information:

Aaron projects

2013-11-09T22:32:01Z

192.54.222.3: /* Transparency */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* '''SecureDrop''' (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Essence ===
* Mozilla is working on a number of awesome new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users!
* There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're looking to fill this strategic gap by proposing an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model 'Essence'
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.
* For more information: https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9

Aaron projects

2013-11-09T22:31:47Z

192.54.222.3: /* Transparency */

==Continued work==
First call is 11/11 at 18:30 EST. worldtimebuddy.com for time translation
: (213) 493-0352 OPEN PIN 38453
Platform for continued engagement coming soon

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]
** Timeline visualization is in a state to share (still needs detail added in) : http://prezi.com/9r2agd3u8ule/aaron-swartz-timeline/

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* SecureDrop (yan/micah/garrett?/james?, SF, samthetechie, Berlin): a platform for whistleblowers to transfer documents to newspapers directly. See [https://pressfreedomfoundation.org/securedrop Press Freedom page] + [https://github.com/freedomofpress/securedrop GitHub trunk].
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

=== Essence ===
* Mozilla is working on a number of awesome new projects (Webmaker, FirefoxOS, Firefox Accounts, etc) that together are greater than the sum of their parts and will (hopefully) help the web leapfrog traditionally native platforms in ways that restore sovereignty to users!
* There's but one major thing missing in Mozilla's current tech roadmaps: an approach to wrangling control of personal data across the web back into the hands of users.
* We're looking to fill this strategic gap by proposing an extensibility model for Mozilla's [https://developer.mozilla.org/en-US/docs/WebAPI WebAPI project] that would enable RESTful API ecosystems to align with Mozilla's user-centric values. We are calling this extensibility model 'Essence'
* In nutshell, we are Mozilla volunteers aiming to influence the Firefox development roadmap. To do so, we are building a prototype that demonstrates the UX of Essence that also acts as a forward polyfill for future potential prototypes that can demonstrate the implications of a WebAPI extensibility model for products across Mozilla as well as the API ecosystems across the web.
* Needs: Developers interested in creating Firefox Add-ons, modeling APIs using [http://raml.org/ RAML], or hacking the about:permissions UI in Firefox.
* For more information: https://jwilde.hackpad.com/Essence-Project-Summary-b9vSK8NkuQ9

Aaron projects/CFAA

2013-11-09T21:25:13Z

192.54.222.3: .

<center>''Work in progress; please link to other work here'' 
[https://pad.textb.org/p/CFAA '''Draft of Principles'''] being edited online 
Draft outline of replacement law underway</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Guiding principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
(''see the draft'')

; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Points of consensus ===
Based on conversations with folks at the '''Cambridge/Boston''' hack, these principles emerged as points of agreement. Other groups feel free to chime in as well.

==== Reasonable defenses ====
* '''Scope should be limited''' - the law should not run to the boundary of what we find ethical or moral. We want people to have freedom to "mess around" with the web (perhaps with some negligence-based liability if they cause actual damage). As with media law and "bad journalism", copyright and "plagiarism," the law should leave the edge cases for the community to set up a moral/normative/shame-oriented punishment scheme.
** we feel as though there is sufficient persistent identity in the community that even pseudonymous hackers care about their reputations.

* '''focus on bad ''access'', leave ''use'' to other laws''' - laws on copyright, trade secret, identity theft, espionage, extortion, and fraud govern most of the "scary" use cases.
** In this way, we are leaving the "hats" (black/white/grey/green) discussion for the community norms or existing law.

* '''Consent should always be a defense''' - server owners ask members of the public to do some weird stuff against their systems, but as long as they ask for it, it should never be a crime to access one's computer in that way.

* As to code-based vulnerabilities and authentication measures, '''some level of technical effectiveness should be considered.''' A "reasonable" standard may not be appropriate, as defining what is "reasonable" may lead to unnecessary confusion. But some consideration should be made to ensure that trivially-overcome measures are not considered within the scope.

==== What should be unlawful ====
* '''hold the party intending to do the bad behavior culpable''' - don't track liability to a person whose computer was unwittingly used to commit the crime.

* '''Circumvention of a code-based authentication measure''' should be unlawful (leaving proportionality for another discussion). This includes cracking, password guessing, or human-engineering password disclosure.

* '''Exploiting a code-based vulnerability to obtain information''' should be unlawful (leaving proportionality for another discussion). We are thinking of things like a SQL injection hack.

* '''Knowingly deleting or impairing the integrity of the work''' should be unlawful if done intentionally or recklessly. Moving down to negligence or strict liability at a certain damage threshold is harder to say.

==== Uncertain areas ====
* '''penetration testing''' is squishy - an open call for bug bounties should be treated like consent to access the site (again, using laws govern bad uses)

* '''"accidentally open" sites are squishy''' - e.g., sites that were supposed to be behind an authentication layer but are not. To a certain extent, it may be best to place the fault of this onto the coder of the site, with the comfort that certain uses by the obtainer of information may still be unlawful.

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.
: Not the worst thing to do; it's not the same as impersonating a real person

* Circumventing the auth process altogether?
: This tends to be pretty bad. It's clearly defeating the system, when it requires finding a subtle exploit
: Can be less bad when a system has an auth system but doesn't use it (e.g. it's never checked)

; What's the ECTF doing? Who could provide oversight?
: (cf [http://www.technewsdaily.com/16445-fix-hacking-laws.html fix-hacking-laws essay] and Robert Graham's comment)

== Active proposals ==

=== Aaron's Law ===
''Lofgren & Wyden''

* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
*: Amend the Wire Fraud Act
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.
*: Limit scope of "exceeding authorized access"

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T21:24:57Z

192.54.222.3: /* Points of consensus */

Aaron projects/CFAA

2013-11-09T21:18:45Z

192.54.222.3:

<center>''Work in progress; please link to other work here'' 
[https://pad.textb.org/p/CFAA '''Draft of Principles'''] being edited online 
Draft outline of replacement law underway</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Guiding principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
(''see the draft'')

; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Points of consensus ===
Based on conversations with folks at the '''Cambridge/Boston''' hack, these principles emerged as points of agreement. Other groups feel free to chime in as well.

* '''Scope should be limited''' - the law should not run to the boundary of what we find ethical or moral. We want people to have freedom to "mess around" with the web (perhaps with some negligence-based liability if they cause actual damage). As with media law and "bad journalism", copyright and "plagiarism," the law should leave the edge cases for the community to set up a moral/normative/shame-oriented punishment scheme.
** we feel as though there is sufficient persistent identity in the community that even pseudonymous hackers care about their reputations.
* '''focus on bad ''access'', leave ''use'' to other laws''' - laws on copyright, trade secret, identity theft, espionage, extortion, and fraud govern most of the "scary" use cases.
** In this way, we are leaving the "hats" (black/white/grey/green) discussion for the community norms or existing law.
* '''hold the party intending to do the bad behavior culpable''' - don't track liability to a person whose computer was unwittingly used to commit the crime.
* '''Consent should always be a defense''' - server owners ask members of the public to do some weird stuff against their systems, but as long as they ask for it, it should never be a crime to access one's computer in that way.
* '''Circumvention of a code-based authentication measure''' should be unlawful (leaving proportionality for another discussion). This includes cracking, password guessing, or human-engineering password disclosure.
* '''Exploiting a code-based vulnerability to obtain information''' should be unlawful (leaving proportionality for another discussion). We are thinking of things like a SQL injection hack.
* As to code-based vulnerabilities and authentication measures, '''some level of technical effectiveness should be considered.''' A "reasonable" standard may not be appropriate, as defining what is "reasonable" may lead to unnecessary confusion. But some consideration should be made to ensure that trivially-overcome measures are not considered within the scope.
* '''Knowingly deleting or impairing the integrity of the work''' should be unlawful if done intentionally or recklessly. Moving down to negligence or strict liability at a certain damage threshold is harder to say.
* '''penetration testing''' is squishy - an open call for bug bounties should be treated like consent to access the site (again, using laws govern bad uses)
* '''"accidentally open" sites is squishy''' - e.g., sites that were supposed to be behind an authentication layer but are not. To a certain extent, it may be best to place the fault of this onto the coder of the site, with the comfort that certain uses by the obtainer of information may still be unlawful.

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.
: Not the worst thing to do; it's not the same as impersonating a real person

* Circumventing the auth process altogether?
: This tends to be pretty bad. It's clearly defeating the system, when it requires finding a subtle exploit
: Can be less bad when a system has an auth system but doesn't use it (e.g. it's never checked)

; What's the ECTF doing? Who could provide oversight?
: (cf [http://www.technewsdaily.com/16445-fix-hacking-laws.html fix-hacking-laws essay] and Robert Graham's comment)

== Active proposals ==

=== Aaron's Law ===
''Lofgren & Wyden''

* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
*: Amend the Wire Fraud Act
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.
*: Limit scope of "exceeding authorized access"

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T21:18:26Z

192.54.222.3:

<center>''Work in progress; please link to other work here'' 
[https://pad.textb.org/p/CFAA '''Draft of Principles'''] being edited online 
Needed: Draft outline of replacement law, good law to emulate</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Guiding principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
(''see the draft'')

; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Points of consensus ===
Based on conversations with folks at the '''Cambridge/Boston''' hack, these principles emerged as points of agreement. Other groups feel free to chime in as well.

* '''Scope should be limited''' - the law should not run to the boundary of what we find ethical or moral. We want people to have freedom to "mess around" with the web (perhaps with some negligence-based liability if they cause actual damage). As with media law and "bad journalism", copyright and "plagiarism," the law should leave the edge cases for the community to set up a moral/normative/shame-oriented punishment scheme.
** we feel as though there is sufficient persistent identity in the community that even pseudonymous hackers care about their reputations.
* '''focus on bad ''access'', leave ''use'' to other laws''' - laws on copyright, trade secret, identity theft, espionage, extortion, and fraud govern most of the "scary" use cases.
** In this way, we are leaving the "hats" (black/white/grey/green) discussion for the community norms or existing law.
* '''hold the party intending to do the bad behavior culpable''' - don't track liability to a person whose computer was unwittingly used to commit the crime.
* '''Consent should always be a defense''' - server owners ask members of the public to do some weird stuff against their systems, but as long as they ask for it, it should never be a crime to access one's computer in that way.
* '''Circumvention of a code-based authentication measure''' should be unlawful (leaving proportionality for another discussion). This includes cracking, password guessing, or human-engineering password disclosure.
* '''Exploiting a code-based vulnerability to obtain information''' should be unlawful (leaving proportionality for another discussion). We are thinking of things like a SQL injection hack.
* As to code-based vulnerabilities and authentication measures, '''some level of technical effectiveness should be considered.''' A "reasonable" standard may not be appropriate, as defining what is "reasonable" may lead to unnecessary confusion. But some consideration should be made to ensure that trivially-overcome measures are not considered within the scope.
* '''Knowingly deleting or impairing the integrity of the work''' should be unlawful if done intentionally or recklessly. Moving down to negligence or strict liability at a certain damage threshold is harder to say.
* '''penetration testing''' is squishy - an open call for bug bounties should be treated like consent to access the site (again, using laws govern bad uses)
* '''"accidentally open" sites is squishy''' - e.g., sites that were supposed to be behind an authentication layer but are not. To a certain extent, it may be best to place the fault of this onto the coder of the site, with the comfort that certain uses by the obtainer of information may still be unlawful.

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.
: Not the worst thing to do; it's not the same as impersonating a real person

* Circumventing the auth process altogether?
: This tends to be pretty bad. It's clearly defeating the system, when it requires finding a subtle exploit
: Can be less bad when a system has an auth system but doesn't use it (e.g. it's never checked)

; What's the ECTF doing? Who could provide oversight?
: (cf [http://www.technewsdaily.com/16445-fix-hacking-laws.html fix-hacking-laws essay] and Robert Graham's comment)

== Active proposals ==

=== Aaron's Law ===
''Lofgren & Wyden''

* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
*: Amend the Wire Fraud Act
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.
*: Limit scope of "exceeding authorized access"

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:40:04Z

192.54.222.3:

<center>''Work in progress; please link to other work here'' Draft of Principles being drafted online Draft replacement law underway later today</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.
: Not the worst thing to do; it's not the same as impersonating a real person

* Circumventing the auth process altogether?
: This tends to be pretty bad. It's clearly defeating the system, when it requires finding a subtle exploit
: Can be less bad when a system has an auth system but doesn't use it (e.g. it's never checked)

; What's the ECTF doing? Who could provide oversight?
: (cf [http://www.technewsdaily.com/16445-fix-hacking-laws.html fix-hacking-laws essay] and Robert Graham's comment)

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:35:25Z

192.54.222.3: /* Open questions */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.
: Not the worst thing to do; it's not the same as impersonating a real person

* Circumventing the auth process altogether?
: This tends to be pretty bad. It's clearly defeating the system, when it requires finding a subtle exploit
: Can be less bad when a system has an auth system but doesn't use it (e.g. it's never checked)

; What's the ECTF doing? Who could provide oversight?
: (cf [http://www.technewsdaily.com/16445-fix-hacking-laws.html fix-hacking-laws essay] and Robert Graham's comment)

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:26:33Z

192.54.222.3: /* Open questions */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where do the following edge cases fall?
* 'sockpuppeting' authentication where it's assumed you have one-account-per-user?
: This is rarely prevented clearly.

; Circumventing the auth process?

; What's the ECTF doing?
: (cf fix-hacking-laws essay)

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:22:43Z

192.54.222.3: /* Open questions */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

; Where does 'sockpuppeting' fall in the spectrum of decent of authentication?

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:20:46Z

192.54.222.3: /* Open questions */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authentication' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.
: Is feigning authentication fraud? (when simply making up a new account; impersonating yourself, and not someone else)

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:19:51Z

192.54.222.3: /* Principles */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

=== Open questions ===
Feel free to suggest brief answers, pointers to where this is discussed.

; Does 'authorization' make sense as the basis for such a law?
: As opposed to other corollaries re: trespass and access. Compare historical ways of handling these issues.

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

=== Additional needed resources (1 hour projects) ===

* mapping out where the CFAA overlaps with existing law; identifying areas left untouched.

Aaron projects/CFAA

2013-11-09T17:14:48Z

192.54.222.3: /* Open questions */

<center>''Work in progress; please link to other work here''</center>

;Goal: Let's prepare for a full repeal of the CFAA and replacement with sane law.
;Questions: How would we construct good law in these areas, from scratch?
: How do different areas of law, policy, and internet governance view the law and its impact?
: What would it take to generate support for a [repeal + replace] action, in each area?
: What are the professional and philosophical circles for each of these areas, where these issues are discussed?

== Overview ==
The CFAA was developed over time as a merger of ~7 different areas of law. It has developed in an aggregate way, and few groups are happy with the current law. It is so broad that prosecutors like it because they can use it to force plea bargains, since it applies to almost everything in its sphere of action (relying on prosecutorial judgement).

Different parts of the story: National defense, cyber war, data sec, corporate law, contracts online. Authorization based on code, contract, social norms. Legal frameworks used to push political means. Career standards for prosecutors defined in political ways.

=== Background ===
; Aaron's Law
* [http://www.dmlp.org/blog/2013/impact-aarons-law-aaron-swartzs-case Analysis from January], [https://www.eff.org/document/eff-cfaa-improvements EFF suggested changes]
*[http://www.slate.com/blogs/crime/2013/06/20/aaron_s_law_zoe_lofgren_s_new_bill_would_help_reform_the_cfaa_will_congress.html June update via Lofgren], [https://www.eff.org/deeplinks/2013/07/critics-aarons-law-emerge-agree-statute-has-problems July update via Wyden]
* [https://action.eff.org/o/9042/p/dia/action/public/?action_KEY=9005 EFF action page] - '''send a letter''' to your senators

; Govtrack updates
* [https://www.govtrack.us/congress/bills/113/hr2454#overview H.R. 2454] (Lofgren bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1196#overview S. 1196] (Wyden bill; referred to Senate Judiciary)
* [https://www.govtrack.us/congress/bills/113/hr2077 H.R. 2077] (Perlmutter bill; referred to House Judiciary subcommittee on Crime, Terrorism, Homeland Security, and Investigations)
* [https://www.govtrack.us/congress/bills/113/s1426 S. 1426] (Blumenthal bill; referred to Senate Health, Education, Labor, and Pensions Committee)

=== Comparative Law ===

== Details ==
;Aspects of the search:
* "Advanced technical crime" -- The deployment of the SS was a bit peculiar; but they were the only fed. agents trained in what they were looking for.

;Civil rights concerns
* Part of the prosecution that was particularly troubling: at one point in the invest., it felt that they were keeping the prosecution going b/c they'd spent so much time bringing it along. There was no will from victims to keep it going, and not necc. any other desire, but the prosecutors for their own reason wanted conclusion.
*: Suggestion: ''employ economists to remind people of sunk costs''

;Three levels of problem
* Occlusion of different agendas and sets of laws
*: Compare pre-computer to post-computer laws for identical crimes.
* Problems with prosecution as it happens today
*: Motivations for initiating/closing cases
* The nature of CFAA as it's been employed
*: Failure of proportionality

=== Legal elements ===
There are 7 planks to [http://www.law.cornell.edu/uscode/text/18/1030 18 U.S.C. § 1030]

# Knowingly accessing a computer without access or exceeding access, and obtaining security, foreign relations, atomic info
#: rarely used, as it is substantively overlapped by other ares
# Intentionally accessing a computer without access or exceeding access, and in so doing obtaining "information," financial records, or U.S. government info.
#: the biggest and most frequently used for access-and-downloading type offenses
# Accessing without authorization (not "exceeding") a US government owned or controlled computer
# Equivalent to the statute on [http://www.law.cornell.edu/uscode/text/18/1343 wire fraud], but replacing "wire" with "computer" and tweaking the details
#: Overlap with WFA, rather irrelevant in current environs
# Computer damage
#: three separate crimes ("damage" = impairment to integrity and availability of data; "loss" = reasonable cost of responding to offense, including costs of damage assessment)
#:: knowingly cause transmission of program and intentionally cause damage
#:: intentionally access a computer and as a result recklessly cause damage
#:: intentionally access a computer and as a result cause damage and "loss"
# Password Trafficking
# Extortion through use of computer

== Proposed solutions ==

=== Aaron's Law ===
* Lower some of the penalties for crimes that produce little or no harm,
* Delete a provision that is repeated elsewhere in the statute
* Clarify once and for all that violating terms of service agreements is not a crime.
*: NB - Chin in US v. Drew - precedent that an individual, violating a TOS without a script, is pretty clearly not a crime. But it is still always used as a threat to amplify perceived risk.

; current status
* referred to the Committee on Crime, Terr, Homeland Security subcomm of Judiciary Committee (chair: Sensenbrenner)

== Principles ==
: compare [https://necessaryandproportionate.org/text Necessary and Proportionate] principles

What substantive things should be in a rational computer crime law?

=== Positive principles ===
; Parallelism with non-computer crime law

; Proportionate punishment

=== Negative principles ===
; Avoid confusion/overlap between different parts of the government : in terms of means and ways
* b/t different parts of the government
* b/t different phil and pol goals
* b/t social-good and infosec goals

== Active proposals ==

=== Patching existing law ===
; EFF proposals and ideas
* Limit scope of "exceeding authorized access"
: Say: contractual violation can't be the basis for this
* Amend the Wire Fraud Act
: Say: contractual violation can't be the basis for this
* lower penalties for crimes that produce little or no harm
* cleanup: delete repeated provision, delete provision repeated in WFA
* clarify once and for all that violating TOS is not a crime (nb: it can still be prosecuted civilly)

; Fork the Law page, listing legal history and proposed changes
* [http://forkthelaw.org/node/9 From mid-2013]

=== Creating something new ===
; Manifesto
*A la necessary and proportionate manifesto created after PRISM: https://necessaryandproportionate.org/text
* Hack on this version: [https://pad.textb.org/p/CFAA CFAA replacement]
; Drafting example legislation?

Aaron projects/CFAA

2013-11-09T15:05:43Z

192.54.222.3: /* EFF proposals */

Aaron projects/CFAA

2013-11-09T15:03:34Z

192.54.222.3: /* Legal issues */

Aaron projects/CFAA

2013-11-09T15:01:16Z

192.54.222.3: /* Details */

Aaron projects

2013-11-09T14:32:44Z

192.54.222.3:

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ (Cambridge), JamesGrimm

* Abelson Report ''TL;DR'' (Cambridge). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* SecureDrop (yan/micah/garrett?/james?, SF): a platform for whistleblowers to transfer documents to newspapers directly. See https://github.com/freedomofpress/securedrop.
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
* SecureDrop (samthetechie, Berlin) https://pressfreedomfoundation.org/securedrop + https://github.com/freedomofpress/securedrop.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is

Aaron projects

2013-11-09T14:31:59Z

192.54.222.3: /* Personal archive */

=== TOR ===
* tor2web and jot2tor (virgil, SF)(oliver, BOS) : Tor2web makes it possible for internet users to view content from Tor hidden services. It's online in a (mostly) functioning form at http://tor2web.org . Jot2tor is an extension of this allowing users to use Aaron's jottit.com framework to easily create pages hosted on hidden services. Naturally, pages created via jot2tor are accessible from tor2web. Aaron and I actually worked on both of these projects until his death.
*: OliverDay ('''Cambridge''')
More information about what help we need is at: https://tor.jottit.com

=== Access ===
* Fork the Law ([[User:Christie|Christie]] ([[User talk:Christie|talk]]), SF) Fork the Law has spent the last few months working out what ordinary people need to know in order to effect legislative change. We're now working on condensing this down to a set of technical design requirements. We'd like to dig into turning the requirements into code, integrating existing open source applications and other services wherever possible. The repository for the development effort is https://github.com/fork-the-law/hancock.

* [http://freelawproject.org Free Law Project] - non-profit providing free access to primary legal materials, developing legal research tools, and supporting academic research on legal corpora. Creators of CourtListener and Juriscraper. Easiest project for new contributor would be to extend juriscraper to cover another state court website not yet covered. See code on bitbucket.org.
*: Free Law Machine is a virtual machine containing all dev tools and code one needs to get started.
*: See also the "Free the Law" project @ HLS

* [http://peerlibrary.org/ PeerLibrary] is a new open source project and a service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications, but could be deployed for any other field (a StackExchange-like family is envisioned).
*: [https://github.com/peerlibrary/peerlibrary source code] (build with [http://meteor.com/ Meteor])
*: [https://archive.org/details/PeerLibraryPreview screencast of a prototype]
*: [http://okcon.org/2013/09/12/okcon-2013-guest-post-peerlibrary-open-scientific-knowledge/ OKCon blog post about the ideas behind the project]
*: [https://twitter.com/PeerLibrary @PeerLibrary]

=== Personal archive ===
*Archiving Aaron's writings (psawaya, '''SF'''). I think it'd be helpful to produce an archive of Aaron's writings, as the formatting on his blog isn't well-organized or good for reading on mobile devices. Some projects might include producing ePub and MOBI versions, organizing and tagging his writing, making it searchable, and perhaps even making it annotatable. It may be possible to build off of [https://github.com/joshleitzel/rawthought this project]. I recall not finding a Creative Commons declaration on Aaron's blog, though this project certainly seems to be in alignment with his ideals. Yan suggested talking about it with Noah Swartz.
*: Interest: JoshL, SJ ('''Cambridge'''), JamesGrimm

* Abelson Report ''TL;DR'' ('''Cambridge'''). Distillation and restating the Report to the President, such that more people can join in the conversations around the issues specific to MIT. [https://hackpad.com/TL-DR-lSAvXSwRYpH Ongoing project page]

* Getting projects their own articles on Wikipedia
*: James ('''Cambridge''')

=== Legal Fixes ===
* [[/CFAA|'''Repeal the CFAA''']]: SJ, Andy (Cambridge). The CFAA is broken; noone but prosecutors like it. Building a constructive, normative replacement, and strategies for getting support at all levels: executive, policy, law, prosecution, activists, cyberwar. Cooperating with Aaron's Law and EFF work; but also tackling.
*: Most discussions of "CFAA reform" have been incremental, in a framework of discussing what changes to current law are possible and would help fix recent problems; as opposed to describing why CFAA is broken and what proportionate and moral laws in that space wold look like.
*: We're trying to describe what effective policy would look like, starting from scratch. Policy, Legal, Social, Tech/Security, and Prosecutorial norms which make sense.
*: [[/CFAA|Project details]] and analysis

* Prosecutorial Overreach/Underreach: The DOJ turns a blind eye to war criminals and Wall St crooks yet throws the book at activists like Aaron. I've registered 14 domains that are variations of the three main prosecutors in Aaron's trail (i.e. carmenortiz.org, stephenheymann.org, etc.) The names Carmen Ortiz and Stephen Heymann are already synonymous with abuse of power. Let's cement that while drawing attention to other activists/whistleblowers who are being prosecuted for non-crimes. While we're at it, let's give prosecutors something useful to do by highlighting well documented but unprosecuted crimes (I'm looking at you John Yoo/Jamie Dimon/James Clapper).

* Restore the Fourth placeholder. We'll know more closer to the date about which of our projects would benefit the most from this. Options include the various encrpytion/meshnet/other coding aspects, blog posts and other content development, or drafting policy documents and researching for coalition-building.

=== Privacy and other software tools ===
* Mailpile (brennan, Berlin): https://github.com/pagekite/mailpile

* Indie Box: Set up our own web applications on cheap Linux devices (like the Raspberry Pi) in our own homes: http://indieboxproject.org/

* Client-side encryption (Daniel, SF): a library for creating web apps that encrypt user data before sending it to the server. This is an attempt at keeping the convenience of cloud storage while retaining data privacy.

=== Transparency ===
* SecureDrop (yan/micah/garrett?/james?, SF): a platform for whistleblowers to transfer documents to newspapers directly. See https://github.com/freedomofpress/securedrop.
*: Our ongoing documentation / q&a site is https://securedrop.hackpad.com. You can also find us on oftc #securedrop-dev.
* SecureDrop (samthetechie, Berlin) https://pressfreedomfoundation.org/securedrop + https://github.com/freedomofpress/securedrop.
*: Is there a place for people to publish already?

* Transparency Toolkit (shidash, ?): Unfortunately Shidash is unavailable, but maybe someone else could do it?

* Overview Project (Ian, SF): an open-source tool to help journalists (or anyone!) find stories in large sets of documents, by automatically sorting them according to topic and providing a fast visualization and reading interface. It's a way to quickly make sense of huge leaks, FOIA responses, and document dumps using a combination of clever algorithms and human intuition. Remember, transparency is meaningless if nobody's watching. Homepage: http://overview.ap.org/ Source: https://github.com/overview

=== Activism tools ===
* Taskforce (Sina, SF): https://taskforce.is are a group of developer volunteers working on a range of different activism tools and campaigns, aiming to improve the tools available to citizens and organizations advocating for better technology policy.
** Two projects we'd love to collaborate on are:
*** '''An SMS campaigning tool''' - Similar to MobileCommons, but open source. We have funding from Twilio that will enable this to exist as a "warning broadcast system" for people interested in tech advocacy. How it should work: The system would allow a user to sign up (either via SMS or via a web form) to receive SMS updates about tech advocacy projects. When a user signs up they immediately receive a text confirming their signup, and they can opt out any time. Admins can send messages to all subscribers via an admin interface.
*** '''Crowdsourced anti-apathy platform''' - There's quite a bit of apathy with regards to surveillance in both the tech community and in the general public. We've been brainstorming to try and figure out how we can effectively convince people that it matters. Our best proposal thus far is to create a system to crowdsource the most convincing content, videos, photos and articles from around the web. Users would then be able to upvote the things that they found the most convincing.
**Feel free to hack away. If you have any questions, feel free to email me (Email: [mailto:sina.khanifar@gmail.com], SMS: 949-878-8202). Also see https://github.com/tfrce and https://taskforce.is