[SPRINT] Next meeting: 29th September 2014
Doug Belshaw
For the benefit of everyone else, the Google Doc is here: http://goo.gl/40byub. Please do give your feedback on the following badge criteria below (based on the skills underpinning the 'Privacy' competency of the Web Literacy Map)
1. Identifying rights retained and removed through user agreements
Name: Privacy: Terms of Use
Criteria:
Link to an example of a user agreement
Describe how a user’s rights are affected (retained/removed) by a particular user agreement
Compare and contrast user agreements of similar services (e.g. using https://tosdr.org)
2. Taking steps to secure non-encrypted connections
Name: Privacy: Secure Connection
Criteria:
Link to descriptions of different ways to secure your internet connection
Describe the opportunities and drawbacks to various secure methods (e..g, VPN, HTTS, TOR)
Change the way your device connects to a website (e.g. VPN, SSH, HTTPS)
3. Explaining ways in which computer criminals are able to gain access to user information
Name: Privacy: Hacker safe
Criteria:
Link to an example of a computer criminal getting access to user information through weak passwords
Describe motivations that computer criminals have for stealing personal information
Change your passwords to stronger, unique ones (e.g. using LastPass / 1Password) and/or utilize two-factor authentication.
4. Managing the digital footprint of an online persona
Name: Privacy: Persona
Criteria:
Trace your digital footprint using a tool such as myshadow.org
Describe what the ‘anti-you’ would look like as an online persona
Take control of a web profile to share a level of detail with which you’re appropriate (e.g. https://www.google.com/settings/accounthistory)
5. Identifying and taking steps to keep important elements of identity private
Name: Privacy: Identifier
Criteria:
Link to a well-known example of someone over-sharing private information.
Describe which elements of identity are best kept private, and offline entirely
- Take steps to keep private information accessible only to trusted parties
marc
One other note: it took me some time to process things as I was catching up on the conversation, so apologies for reaching back to a closed issue. I agree with Carla that maybe descriptions can help add some whimsy to badge titles but that for now straightforward is a good goal considering the various contexts where they might be issued. Looking back to this last post though, i might suggest a tiny bit more discussion on three specifically: the "Persona" badge, the "Hacker Safe" and the "Identifier." Sorry to miss an opportunity to bring up during the call, but these three feel less straightforward than the first two. Total respect if already consensus and we just need to move along at this point but without too much explanation, here are some ideas that might help make these three more straightforward (of course, with my k12 context in mind).
3. i've always found using the word "hacker" to be problematic given mulitiple meanings...how about something like "Crime Safe," or "Safeguarding data" or just using "Passwords" given that most of the current criteria is about passwords
4. how about just "Digital Footprint," or "Data Trail"
5. how about "Protecting ID" or "Private ID" or "Managing Identity"
Not hardcore about any of the suggestions so please do riff, nix, or stand ground on what's already there. I realize that some of the suggestions are longer than the single word, but I guess (while i love shorter where it works) i'm favoring more words if it helps clarify. Again, just wanted to offer the .02 in case helpful - want to be sure that we're using a nomenclature that, if not fun/whimsical, does the different important job of being clear to different kinds of learners.
Thanks all,
Marc
Doug Belshaw
I've added those suggestions as comments to the Google Doc: http://goo.gl/40byub
Doug