Difference between revisions of "GPG guide/Textual Draft"

From LibrePlanet
Jump to: navigation, search
Line 17: Line 17:
 
* Next steps section
 
* Next steps section
  
−
==Infographic breakdown==
+
===Infographic breakdown===
−
* Narrative structure, like a comic. I imagine the story it tells is: there are two people trying to communicate, but they are being surveilled. Then they go through the process of setting up GPG, and they they communicate securely. This give us a a good way to explain keys, keyservers, encryption and sisgning.
+
[[GPG_guide/Infographics|See separate page]]
−
*** First  panel explains the problem and has a picture of many characters (or  maybe just the original two) sending email to each other that's getting  intercepted and little expressions, symbols or speech bubbles that shows  all the ways this hurts them. Text refers to the problems inherent with  unencrypted meail (surveillance, insecrutiy, chilling free speech, repressing dissidents etc).
 
−
*** Then  some kind of thing that's like "you can do something about it" You  don't have to use it all the time, but knowing how is important, and  here are some times to use it. Makes you more secure from surveillance  and private companies and in general.
 
−
* Prominently features URL of the guide, which we haven't determined yet
 
−
* Explains the basics elements of the GPG system: two people communicating, keyserver, keys, imaginary attacker who wants to surveil
 
−
* Makes sense as a standalone sharable infographic, also makes sense as the introduction to the guide and a visual aid to understanding the basics of how the GPG system works.
 
−
* Should grip people into wanting to participate and show them why this is important, in addition to (or instead of?) just showing them how encryption works. Overall message is "you've heard of this problem, but did you know you can do something about it? Here's how. People will share because it feels like (part of) a solution to a problem that is weighing on them
 
−
* This is the closest thing I've seen to what I'm imagining: <http://flossmanuals.net/thunderbird-workbook/>, but it is of course less comprehensive. There's another one a few pages in to this guide, too.
 
−
* If we have extra time, we should make an infographic to help people understand the Web of Trust
 
−
* Would be good to have something that gives a visual impression of the network effect of people using GPG (which causes it to make more sense for still more people to join), like an expanding network.
 
−
* A big part of this is that we want people to incorporate their GPG key into their online identity. Perhaps at some point in the infographic, it shows a drawing of a person's social media profile or website or email signature in which it shows that they are publicly displaying their GPG key.
 
  
−
==Guide breakdown (based loosely on <https://www.enigmail.net/documentation/quickstart.php>)==
+
===Guide breakdown (based loosely on <https://www.enigmail.net/documentation/quickstart.php>)===
 
* _The idea is for the guide to be broken down into concise steps, with a focus on the actual steps, rather than in-depth explanations of why or how things work. The guide will have a series of steps, each with a number and concise but descriptive name, to make it easy to refer to different parts of it. Each step will have an FAQ-style troubleshooting section, and each entry in the troubleshooting will have a name and a body, which consists of help text. We need to think about the visual presentation of the versions for different operating systems and of the troubleshooting. One possibility is tabs for the operating system and expanding boxes that start collapsed for troubleshooting. Troubleshooting could also be in a separate section at the bottom of the page that looks like an FAQ._
 
* _The idea is for the guide to be broken down into concise steps, with a focus on the actual steps, rather than in-depth explanations of why or how things work. The guide will have a series of steps, each with a number and concise but descriptive name, to make it easy to refer to different parts of it. Each step will have an FAQ-style troubleshooting section, and each entry in the troubleshooting will have a name and a body, which consists of help text. We need to think about the visual presentation of the versions for different operating systems and of the troubleshooting. One possibility is tabs for the operating system and expanding boxes that start collapsed for troubleshooting. Troubleshooting could also be in a separate section at the bottom of the page that looks like an FAQ._
  
Line 50: Line 40:
 
** For users of OSs other than GNU/Linux, a note or sidebox encouraging them to switch to a free operating system if they want to protect their privacy as much as possible.
 
** For users of OSs other than GNU/Linux, a note or sidebox encouraging them to switch to a free operating system if they want to protect their privacy as much as possible.
  
−
==Next steps breakdown==
+
===Next steps breakdown===
 
** Attend or host a keysigning party (is there a good way to find them?)
 
** Attend or host a keysigning party (is there a good way to find them?)
 
** An encrypted email group where people talk about encryption: <http://groups.yahoo.com/neo>/groups/PGPNET/info
 
** An encrypted email group where people talk about encryption: <http://groups.yahoo.com/neo>/groups/PGPNET/info
Line 62: Line 52:
 
* Link to dedicated keyserver for people to use, run by us, so that we can track who is getting started through our campaign.
 
* Link to dedicated keyserver for people to use, run by us, so that we can track who is getting started through our campaign.
  
−
==Designers' feedback and ideas==
+
=Designers' feedback and ideas=

Revision as of 16:59, 8 May 2014

Random Notes

  • Really think about ways that this will be about making the fact that you use GPG part of your online identity, and make this a vector for driving people to the guide. For example, have people put their GPG key up on their blogs and social media sites, with a link (perhaps with logo, graphic, embed code, something cool) to our guide. Is there a good standard way to list this on your FB? Twitter? We can get people to do this even if they are already using GPG.
  • Audience: People who are excited about technology and involved in movements like ours, but don't already know how to use GPG.
  • Think about licensing
  • How do we visually do the troubleshooting? The different operating systems?
  • Name ideas
    • Safe email 101
    • Encryption 101
    • Encrypt your email
    • Safe email

Page elements

  • Infographic
  • Intro paragraph
    • Says it's great to do this with a friend, but we designed it so that it also works fine for one person.
  • Step-by-step guide
  • Next steps section

Infographic breakdown

See separate page

Guide breakdown (based loosely on <https://www.enigmail.net/documentation/quickstart.php>)

  • _The idea is for the guide to be broken down into concise steps, with a focus on the actual steps, rather than in-depth explanations of why or how things work. The guide will have a series of steps, each with a number and concise but descriptive name, to make it easy to refer to different parts of it. Each step will have an FAQ-style troubleshooting section, and each entry in the troubleshooting will have a name and a body, which consists of help text. We need to think about the visual presentation of the versions for different operating systems and of the troubleshooting. One possibility is tabs for the operating system and expanding boxes that start collapsed for troubleshooting. Troubleshooting could also be in a separate section at the bottom of the page that looks like an FAQ._
  • Section 1: Installation (for GNU/Linux users, assume they have GnuPG and Thunderbird, but tell them how to get them if they don't have them)
    • Get GnuPG if you don't already have it
    • Get Thunderbird
      • Configure Thunderbird for your email account
    • Get Enigmail
  • Section 2: Set-up
    • Make a keypair
    • Test signing and encrypting with Adele the keybot, or with a friend
    • Publish your key, with explanation of GPG ID
  • Section 3: Use

_Somehow work in doing this with your friends_

    • How to send encrypted messages and decrypt people's messages
    • How to send signed messages and verify signatures
    • Last step add your key ID to your email signature, along with a link to this guide for getting started. Start signing all your messages and publish your key ID wherever you publish your email address (business cards, Web site, bios, other examples), since this is the best way to advertise that you are using encryption.
    • Point to external resource about Web of Trust, or include our own? Perhaps a sidebox?
    • For users of OSs other than GNU/Linux, a note or sidebox encouraging them to switch to a free operating system if they want to protect their privacy as much as possible.

Next steps breakdown

    • Attend or host a keysigning party (is there a good way to find them?)
    • An encrypted email group where people talk about encryption: <http://groups.yahoo.com/neo>/groups/PGPNET/info
    • Try other encryption technologies: OTR, encrypting your hard drive, Tor
    • Link to surveillance collection in directory, or prism-break with free software filter, if that has been set up
    • Donate to the FSF or GnuPG, Thunderbird or Enigmail!

Things that should be considered for inclusion in the guide

  • RSA versus DSA
  • Saving unencrypted drafts to servers, as per Micah Lee's email to liberationtech
  • Link to dedicated keyserver for people to use, run by us, so that we can track who is getting started through our campaign.

Designers' feedback and ideas

Retrieved from "https://libreplanet.org/wiki?title=GPG_guide/Textual_Draft&oldid=34772"