For this week, we focused on finalizing our images and design elements. Alvaro from Neo should have a working site up by this Friday, so once he does, we’ll start to actually implement the site. Hopefully, we’ll be done with that by next Wednesday (last class!). Again, the mockup of the website design is here.
In the meantime, we’ve made an interactive mockup that shows where the GIFs go inside the written content (for the finalized content sections).. We also have a mockup of an interactive flowchart here. Any and all feedback is welcome!
This week we made some more prototypes and worked on the case study – now that we have another iteration of the website, we’re hoping that someone at Neo can make us a Drupal template into which we could send all of the information. Up next – hopefully we’ll be meeting with someone at Neo soon, and since Jillian sent us a few more final versions of the text, we’ll be making some more animations.
Last week the EFF (Jillian & Eva) led a discussion on threat modeling and how and why we might want to make threat models. Afterwards, as a class, we split into groups and worked through some of the different modules, thinking through interactive and visual elements. We talked about doing anything from flow charts to inserting animated GIFs.
We also got some feedback from Hugh and this is the next iteration of the design (it’s cat-free!).
At the moment, we’re going to start thinking more critically about design elements and ask Neo for help with a framework for the website. Here are a few of the design elements (in various draft-y states).
This past week, we met up with Eva. Going over the threat model workshop and the personae together really helped us to understand what kinds of people might access the website. We also discussed the “Being an Ally” component of the site, as well as how someone might want to access the site (ie. what are they looking for? Why would they use this site? How will they navigate through it? What are the specific countersurveillance measures certain people might need?)
Moving forward, we’ve started to think really critically about how to visualize all of the complicated text in smaller, more interactive pieces, and we’ve also started wireframing a few things and talking through our design likes/dislikes (we’re anti-carousels, but they may be our best option?). We’ll be meeting with Jillian this week, so we should have some visuals to share soon.
We learned a lot at this past weekend’s DiscoTech! It was great to see people from a lot of different backgrounds discussing stories about and problems with surveillance.
To help with our project with the EFF, we held a threat model workshop, allowing people to map their assets and what threats may target those assets as well as the level of risk associated with threats gaining access to assets.
We also provided people with potential scenarios to create threat models if they did not want to make their own.
We envisioned this as a way to gauge what types of asset/threat combinations people are aware of as well as what level of action people are willing to take on their high-risk assets. Since we are hoping to make the EFF’s Surveillance Self-Defense website more accessible to more people, this is important information for us to have about our target user population. Moving forward, we want to make the information more visual and bite-sized, and we’re excited to start wireframing and designing this week!
On Thursday, we had our first Skype meeting with Jillian from the EFF (Eva and Jillian are both going to be our point people). We thought it went really well – we’re excited for the semester!
The Electronic Frontier Foundation (EFF) is an organization devoted to fighting for our (by which we mean internet users’) rights online, which can include, among other things, free speech, privacy, innovation, and consumer rights. Founded in 1990, the EFF is made up of a mix of lawyers, activists, and technologists, who work together to defend the general public’s digital rights.
The project we’re working on is an update and extension to their Surveillance Self Defense project, which aims to educate users about electronic government surveillance and how to properly defend themselves against possible threats. Although the project was initially addressed at an American audience, they’re hoping to make it more international, with the work translated into several different languages. Additionally, the hope is, in conjunction with various partners, to create content “playlists” for specific audiences. A college student in California, for example, might not want/need the same level of surveillance self-defense as a journalist working in Syria.
Our goal, therefore, is to work with them to create this online resource. One of the challenges for us is that the website needs to be easily accessible/modifiable, and since the EFF is already using Drupal, it makes sense for us to build on that. Although we’re feeling pretty good about our website design skills, neither of us have worked with Drupal before, so we’ll see what we can do.
For the Discotech this coming weekend, we’ll be running a Threat Model workshop, working on building visual representations of threat models. Stay tuned for details!
Hi! I’m Paulina, an Ed.M. student in the Technology, Innovation, and Education cohort at the Harvard Graduate School of Education. I’m also an RA with Youth and Media at the Berkman Center for Internet & Society. My background is in classroom education and digital literacies, although lately I’ve been interested in libraries, museums, and other places of informal learning. Although my work deals with young people and their privacy, it is often construed as a concern for social privacy, and I’m curious about some of the questions around surveillance and privacy relating to institutions and corporations.
On The Day We Fight Back, I emailed my legislators and circulated the notice among my social media networks (Fight for the Future makes it very easy to do so). I also have the Internet Defense League‘s “cat signal” installed on websites I manage, which is an easy way to be an activist (or “slacktivist,” as it were). I remember being involved with the SOPA/PIPA debate, and in comparison, “The Day We Fight Back” seemed much quieter. Given that we have visualizations of the media generated around SOPA/PIPA, I’m wondering how visualizations of “The Day We Fight Back” would look like, in comparison.