Editing LFI 2024/Month 3

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
=== Month 3: Privacy in the Library 2 ===
+
=== Month 3: TOPIC ===
* Real time lecture: Friday July 19 at 2:00-4:00 Eastern / 11:00-1:00 Pacific on Zoom
+
* Real time lecture:  
  
 
==== Overview ====
 
==== Overview ====
  
This month, we'll dig deeper into privacy best practices and explore how we talk about privacy in an accessible and personal way. We will talk about gaps in technical literacies and how we as library workers can bridge those gaps with patron and staff trainings, policy reviews and audits, and more.
+
RENAME THIS WEEK TO PRIVACY IN THE LIBRARY 2
 +
 
 +
MOVE TALKING POINTS TO THIS WEEK
 +
 
 +
START COVERING:
 +
 
 +
- privacy best practices in depth
 +
- access v privacy issues
 +
- how privacy is talked about
 +
- how we want to talk about privacy - communicating in an accessible and personal way  
 +
- how to talk through people's fears about technology that does exploit them 
 +
- privacy rights
 +
- getting people on your side about privacy
 +
- Huge tech literacy gaps in general public
 +
- Defeatist attitudes or “nothing to hide” attitudes vs privacy paranoia/fear about institutions, and how this plays out on racial, gender, age, urban/rural, and class lines
 +
- Dealing with surveillance of patrons by library staff
 +
- Personal data exploitation 101 level
 +
- scams and fraud
 +
- Pushing back against libraries collecting data “just in case we need it”
 +
- privacy on public computers, issues - will address privacy tech in the next class
 +
- ways that library surveillance and policies are used against patrons
 +
- Explaining why not to collect data
  
 
==== Readings ====
 
==== Readings ====
  
No readings for this month. Instead, answer the discussion questions in Discord.
 
  
 
==== Guest lecturer ====
 
==== Guest lecturer ====
Line 15: Line 35:
 
==== Discussion ====
 
==== Discussion ====
  
Threat modeling framework:
 
* Assets: What do you want to protect?
 
* Adversaries: Who might want your assets?
 
* Capabilities: What can your adversary do?
 
* Consequences: What could happen if your adversary succeeds? What is the likelihood of this happening?
 
 
Threat Modeling Discussion Questions: What resonated about the threat modeling framework? How can you picture using this in a library environment? Are there threat models/personas that feel particularly relevant to your work?
 
 
Privacy Policies Discussion Questions: How does your library privacy policy measure up to the best practices discussed in month 2? Does your policy match the library's practices? Does it address the data lifecycle in libraries? If not, what needs to change for these conditions to be met?
 
 
Vendor Issues Discussion Questions: What resonated about the vendor discussion, and our conversation with Sarah Lamdan? What vendor issues are you most concerned about? What do you think about the advocacy and reform efforts that have taken place in libraries? What still needs to happen? What would need to shift to create real vendor accountability and change? What power do we currently hold to make this change, and what power do we need to build?
 
  
 
==== Tasks ====
 
==== Tasks ====

Please note that all contributions to Library Freedom Wiki Page may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Library Freedom Wiki Page:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)