Difference between revisions of "Tech Tools for Activism"

From HacktionLab: A UK-wide network tech-activists providing meet-ups, events, workshops, national skillshare gatherings and hacklabs

Jump to navigation Jump to search

Latest revision as of 10:30, 6 December 2013

STOP PRESS: The main landing page for version 2 of the booklet is at the Tech Tools for Activism Web site

The second Hacktionlab tech tools project. These minutes from Hacklab Manchester 2011 contain some of the results of the discussion there.

Resource List

Tech tools for activists - Version one of the booklet
Tech Tools resources links
Why_we_are_not_using_booki_for_TTFA2 (actually we did use booki for TTFA2 - haters gonna hate!)
Content Comments on TTFA2

Participants List

Co-ordinator/slave driver (Ben G)
Illustrator
- Penguin: spoken to an artist and a graphic designer - both up for doing some illustrations / designs / cartoons. Yay! Have suggested they hold off until we make more progress on the content.
Design Consultant

First IRC Meeting

IRC logs for TTFA2 meeting

Sorting out how links to web documentation. (MH)
Review of current quality levels. (BG)
Agree / restate what the target audience is for TTfA (penguin)
Agree / restate what we are trying to convey (e.g. why to do something, how do do something) (penguin)
Should each article have a common structure? If so, what? (penguin)
Should there be more kittens in the booklet? (tabby)
Develop task list to move forward & assign roles as far as possible (penguin)

Second IRC Meeting

IRC logs for TTFA2 meeting 2

This was a meeting between 3 of us meant as a brief precursor to the Booksprint at the end of May, but some important decisions were made:

We should no longer use Booki as it is very unpopular for editing and use mediawiki (on this site) to edit Ben Green will prepare some ground rules
Mick requests that by way of a booki post mortem we write to the developers and say why we are not using it, please add comments on why we are not using booki for TTFA2
This book sprint will be bring a non-techy friend - we will make sure they get us to write in a non-tech friendly way, their understanding of our text is to be our gold standard - get your persuading out and get someone to come with you. You may wish to bribe them, some suggestions are: the illusion of kudos, cake, badges, mini-internship for your CV
We also need good proof readers, same deal applies
Penguin will sort crash space for the booksprint
the booksprint will be at the end of May: Saturday 26th to Sunday 27th May (plus Monday if we want)
People are welcome to sort other stuff for the sprint let us know
The sprint will be at the end of May
editors could work form home on the booksprint days - giving us extra-venue support
something about raveoke

TTFA 2

TTFA2 - don't edit anything yet, under construction by Ben Green

Cover versions

Retrieved from ‘https://hacktionlab.org/index.php?title=Tech_Tools_for_Activism&oldid=4743’

@@ Line 1: / Line 1: @@
+<big>'''STOP PRESS: The main landing page for version 2 of the booklet is at [https://techtoolsforactivism.org/booklet the Tech Tools for Activism Web site]'''</big>
 The second Hacktionlab tech tools project. These [[Hacktionlab_Manchester_2011_Notes#Tech_Tools_for_Activists_Booklet_v_2.0 | minutes from Hacklab Manchester 2011]] contain some of the results of the discussion there.
@@ Line 5: / Line 7: @@
 __TOC__
-== ToDo list ==
-* Decided on a new format/style guide (IRC meeting)
-* Make a resources list
-* Make a participants list
-* write up workflow plan (Ben G)
-* Organize IRC meeting (Ben G)
-* Enhance the Style Guide
-* Go through and check your own original contribtions - take out what you think isn't relelvant. Link out to more information and reduce the word count. (can we have a meeting about style and aims before we do this? Ben Green 20th Sep 2011)
 == Resource List ==
 * [[Tech tools for activists]] - Version one of the booklet
-* http://booki.flossmanuals.net/tech-tools-for-activists-2/_edit/ - editable live version of the document
-* Booki User manual - http://en.flossmanuals.net/Booki-User-Guide/
-=== Resources we can link out to ===
 * [[Tech Tools resources links]]
-=== Booki Developer Interaction ===
+* [[Why_we_are_not_using_booki_for_TTFA2]] (actually we did use booki for TTFA2 - haters gonna hate!)
-IRC interaction is recommended and happens at:
+* [[Content Comments on TTFA2]]
- server: freenode.net
- channel: #flossmanuals
 == Participants List ==
@@ Line 35: / Line 22: @@
 * Design Consultant
-== First IRC Meeting Agenda ==
+== First IRC Meeting ==
 [[IRC logs for TTFA2 meeting]]
@@ Line 47: / Line 34: @@
 * Develop task list to move forward & assign roles as far as possible (penguin)
-= Content Review =
+== Second IRC Meeting ==
-Please tag any comments and suggestions as your own.
-We should remove the user journeys, this was pretty much agreed at the Manchester meet up. (BenG) We should replace them with popout info boxes. (BenG)
-== Secure Communication ==
-=== An Introduction to this Booklet ===
-=== Browsing the Internet anonymously ===
-=== Hiding Stuff on your Computer ===
-=== Organising Online ===
-=== Securing your Email ===
-First Thought
--------------
-I'm not too chuffed with booki - see discussion tab for this page.
-I will now review this chapter in its current form, then proceed to make suggestions about how it might be changed to fit with the new style as discussed at [[IRC_logs_for_TTFA2_meeting]]
-Content review
---------------
-'''''Para 1'''''
-The user story is '''grand''' but the use of bold face seems '''a bit''' random.
-'''''Paras 2-6'''''
-We jump into addressing the specific example raised in the user story, in the way that I would probably talk about it to someone in the pub. That's OK for chatting in the pub, but maybe in this setting we could be more systematic about how we broach these matters? The advantage of doing so would be that the reader would then have a conceptual framework on which to hang all the many different issues that arise, so facilitating their learning.
-So in this case, instead of diving in to the example, we could start by explaining the informatic nature of an email transaction, then expand. For example:
-* What is the structure of a transaction, and who are the parties to it?
-* What information is available to each party?
-** What is stored on your machine, should anyone care to look (link to chapter on safe data storage)
-** What your ISP and 'public networks' can see
-** What your email provider can see
-** What your (CC'ed) recipients can see
-* How can the mail user control what information is available to whom?
-** Hard drive hygiene
-** Choice of MUA (or browser for webmail)
-** Use of secure tunnels to protect against ISP snooping
-*** link to chapters on personal VPNs and ad-hoc ssh tunneling
-** Use of trusted email providers [current paras. 7-8 goes here]
-** Use of encrypted email [current paras. 9-end here]
-*** Certification
-*** PGP
-* Why would the user wish to do all this?
-** General desire for privacy
-** Avoiding targetted advertising
-** Protecting campaigns against specific threats
-*** Corporate surveillance - e.g. EDF snooping on GreenPeace
-*** Government surveillance - network profiling, keeping yourself out of their sights
-*** Pigs that want to nick you for doing what needs to be done - minimising exposure of your most sensitive information
-* etc...
-'''''Paras 7-end'''''
-This is clearly written and accessible. I don't think the current text needs any changes, but would benefit from contextualisation as above.
-New Format
-----------
-Having said all that, we're now looking at writing "Noddy and Big-Ears Send Rad Emails and Plod Doesn't Know", so most of the above detail will have to be lodged somewhere on-line (this wiki?) and referred to in a shortened footnote. So what can we do in the new form, on paper, for TTfA2?
-I'd suggest keeping the same user story, followed by a paragraph that introduces the idea that what one types as an email might reach many different eyes, then list who those eyes might belong to. Then the 'action' section would link to a page on this wiki, structure something like I suggest above, and actions the reader can take:
-* Control on-line identity (needs a seperate chapter) and limit exposure
-* Use trusted email providers
-* Use SSL and VPN if available
-* Use PGP and control local storage
-Anyhow, thanks to everyone who wrote the current page - I couldn't have thought of all this without reading what was there already [[User:MaRk|MaRk]] 09:28, 3 December 2011 (UTC)
-=== How to get pages removed from Google Cache ===
-== Using Open and Decentralised Services ==
-=== Free as in Freedom ===
-=== Secure Updates using Status.net ===
-=== Publishing your News ===
-=== Blogging Anonymously ===
-== Creating our own Media ==
+[[IRC logs for TTFA2 meeting 2]]
-=== Uploading Media to the Internet  ===
-I came across a linux musician's [http://www.louigiverona.ru/?page=projects&s=music&t=ashwood&num=1 website] where the author tells a funny story in which he creates an alter-ego for publishing his music, but his identity gets exposed by IP logging. Perhaps we could use this as a user story about how anonymity can be lost? It has the side-benefit of introducing people to some free music made with free software. [[User:MaRk|MaRk]] 10:31, 14 January 2012 (UTC)
+This was a meeting between 3 of us meant as a brief precursor to the Booksprint at the end of May, but some important decisions were made:
-== Green Computing ==
+* We should no longer use Booki as it is very unpopular for editing and use mediawiki (on this site) to edit Ben Green will prepare some ground rules
-This is a a title section with no contents, why? (BenG)
+* Mick requests that by way of a booki post mortem we write to the developers and say why we are not using it, please add comments on [[why we are not using booki for TTFA2]]
+* This book sprint will be '''bring a non-techy friend''' - we will make sure they get us to write in a non-tech friendly way, their understanding of our text is to be our gold standard - get your persuading out and get someone to come with you. You may wish to bribe them, some suggestions are: the illusion of kudos, cake, badges, mini-internship for your CV
+* We also need good proof readers, same deal applies
+* Penguin will sort crash space for the booksprint
+* the booksprint will be at the end of May: '''Saturday 26th to Sunday 27th May''' (plus Monday if we want)
+* People are welcome to sort other stuff for the sprint let us know
+* The sprint will be at the end of May
+* editors could work form home on the booksprint days - giving us extra-venue support
+* something about raveoke
-=== Further information and links ===
+== TTFA 2 ==
-=== The Author ===
-== Images ==
+''' [[TTFA2]]''' - don't edit anything yet, under construction by Ben Green
-=== Cover versions ===
+== Cover versions ==
 [[File:TechToolsColourSmall.JPG|300px]] [[File:TechTools2Colour.png|300px]]