report
Lecture Avery Dame-Griff
🔗 Click here to access the collaborative pad
Lecture Avery Dame-Griff
Gijs: This is a collaborative writing tool. If you write it will show up for others.
Each author has their own color. ( You can change your color if you prefer. )
Like this is me, Margarita
I’m Lilian
I’m Tommaso
Alex here
Jules
Avery
Gijs: to be clear. We ask you to take notes during the presentation in this shared document.
Avery is on the West Coast. It’s 6am local time.
Avery can talk about web archiving in the Q+A, but will focus more on digital communities in this presentation
Introduction
Avery Dame-Griff is a Lecturer in Women, Gender, and Sexuality Studies at Gonzaga University and author of The Two Revolutions: A History of the Transgender Internet (2023). He founded and serves as primary curator of the Queer Digital History Project, an independent community history project cataloging and archiving pre-2010 LGBTQ spaces online. Based on this experience, Avery shared his experience with the (collective) act of archiving online activity, why it matters, and what it means to archive typically private content like emails or messages on boards.
The Queer Digital History Project (QDHP)
The Queer Digital History Project (QDHP) archives queer web history. From the outset of the early internet, English was the primary language for communication.
Not always have been using the same internet. Minitel famous example of national video network.
–> What people talk about, how and why.
In early days of internet exhilirating to communicate long distance through email.
in the late 80s and early 90s, email offered a safe space for communication
CDForum example of mailing list where
archiving average user communcation, not well known people or activists
The archive is very complicated
People keep rights to their messages. List started in 1988. At time different ideas of privacy.
Messages posted to the list were expected to be private.
quoteit was very common to republish things that you encountered online in community newsletters
The Key issues:
* The collaborative nature of digital communities
* Question of publicness, privacy, access and right to be forgotten.
* questionPeople often change their mind over time - link with 'the right to be forgotten'? Is it okay to use what people have written a long time ago and interpret it as something they find important, even though now they might no longer have the same perspective? #ethics
* the way people felt about their messages might be very different today then when they first posted, and they might want them to be forgotten and erased completely
*
Messages have been archived by one of the members of the list
Yahoo Groups (launched in 1998) became very popular, especially among queer community. One of the reasons of its popularity was its accessibility. It has:
- Discussion Boards
- File Hosting
- Calendars
- Polls There were arond 10 million groups on Yahoo Groups
Mid 2000s, they were eclipsed by newer online services like Tumblr.
Became legacy platform. Not driving income for the company. But kept available.
Early 2020 Yahoo groups were (announced to be) taken down, how to preserve them? This project tries to answer this issue
Challenge 1 : Community as Collaboration
Locating individual posts within the ecosystem of the larger community/ Recognizing poster’s rights (I missed this part it was in the slides)
Authors keep copyright over their messages. While they are also responding to each other. (Can’t just archive a single message)
This is an ‘ecosystem’ problem. This makes it complex, because it is e.g. difficult to isolate single messages, or connect them to their wider context.
Web preservation is not only what is visible. It’s also the code, infrastrcture, people’s experiences. Authors have rights to their message, and the right to be forgotten.
Challenge 2: Privacy and Post Content
Yahoo groups had a variety of levels of privacy. Some groups required requests for access.
In (some of) their posts and groups there was very private information like full names and locations and images not meant for a wider audience. Also topics about surgery were discussed. It was not meant for a wider audience.
Posts were considered “publicly private”: Technically it is public. But it feels private (to the author).
How did Avery end up approaching it?
Decide scale, or collection scope: Avery decided to focus on message texts (and not images, etc.)
Avery discussed the idea of “tiered consent”. Identify:
- what are musts?
- what are wants? As a legacy platform, most users were no longer active on it.
Groups considered for collection: Public, Non-Active Groups: these are groups that Avery contacted and collaborated with to archive
Tried to find community partners > send an email to someone who was .. as moderator. Avery worked with the moderators.
quoteNo one checks their yahoo mail any more.
A way to do it was to use a donation form to collect things like background information
Also included a way to ask for material, like images or texts, to be excluded: right to be forgotten.
the community partner was expected to be able to reflect the wishes of the community
- This is based on best practices for archival practices for indigenous groups This is not an experimental approach in archiving per se but it is experimental when it come to indgenous gropus
Internet archive > rapid scraping. Getting as much as we can.
In order to address the scope, think about:
- What can you manage, in terms of time, infrastructure, funding, etc?
- What materials are ‘worth’ saving and why? Rhizome as example for video preservation, an archive of born-digital artworks from 1983 to the present day: https://artbase.rhizome.org/wiki/Main_Page
Avery commented on the tension between getting as much as we can before it all goes away (due to the fleeting nature of digital material, online communities, infrastructures etc.) vs. slower community-oriented practice.
challengesDefinition of public and private are not universal.
How to involve the community:
- plan perservation with community involvement from the start Personal Archives (the case of email)
In the process of defining the scope, think about the kinds of messages that should be saved and how they can be identified?
Important to think about defining public and private, what you are comfortable with being preserved and what private communication should be preserved? What sensitive information might be in your email inbox that should be excluded? When is it ethical to seek consent from other parties?
Example of the laptop of Susan Sontag. Researchers had access to it. But with it also her private emails with Annie Leibovitz.
Examples:
- https://lesbianherstoryarchives.org/a-queer-guide-to-personal-digital-archiving/
- https://literaturegeek.itch.io/diy-web-archiving-zine Questions ❓
- Have you gotten into contact with Yahoo to provide an export over a scrape.
- Answer from Avery: this kind of preservation technically violates terms of service. Do not work with the ‘corporate host’. They have little interest in the material being preserved. After announcing sunset Yahoo limited API-access to avoid people archiving material. As a user or community you made the thing, but the control is with the company.
- Lilian made the example from Aiden Walker about how the internet archive scrapes public information, but not the more private information, which is also important for understanding the ecosystems of community online and their interconnection
- (Repeated) LLM bot scraping has made it more expensive to keep legacy platforms online. Wondering whether same has happened to Typepad. Time between announcement and taking down was about a month.
- How do you decide what is worth saving? is it based on the stakeholders in the community? Could you give an example of this process for you?
- What do you mean with community involvement “from the start”? What is the start here? To what extent are you still ‘the leader’ of the project? (Thinking about co-creation for example)
- Avery: in an ideal world, try to go to a community from the very beginning of launching the project
- thinking about what is a community comfortable with and what the community wants to say
- ask these questions from the beginning about what preservation looks like for you: do we want to preserve this? what parts do we want to preserve? what do we want to not preserve? how do we want to preserve it?
- Plan for the decommissioning / disappearance of the platform from the start. Could be a form where participants indicate their desire for data-treatment on end of the platform: kept or deleted. reflectionAvery said: "Your community may not be here one day." –> Reflection: nowadays, people confide in chatbots a lot. But this is not public. But we know that these "personalized" chatbots also disappear (causing great upset for the user). Can we archive this? Or is that up to the individual? Also: it shows that sharing might be a lot more individualized instead of it happening in online communities.
- Avery: in an ideal world, try to go to a community from the very beginning of launching the project
- Thinking about digital communication (such as social media posts or emails), are these born-networked objects individually or collaboratively produced? How do we differentiate between these two categories?
- Follow-up: For collaboratively produced objects, what right do producers have to access these objects? What would that access look like?
- Think about your own email practices. How would you define a “public” email (one that could be archived) versus a “private” email?
- Can a communication be simultaneously public (so, not restricted in terms of who can access it) and private (not intended for all audiences)? If so, how do you make this determination?
- Follow-up: For these kinds of materials, how would you determine what should be archived and who should have access to it?
- Presentation Slides
- Useful practice-related texts:
- [Jace Steiner, A Queer Guide to Personal Digital Archiving]https://lesbianherstoryarchives.org/a-queer-guide-to-personal-digital-archiving/
- [DIY Web Archiving zine] (https://literaturegeek.itch.io/diy-web-archiving-zine)
- Katie Mackinnon, Early Internet Memories zine
- Organizations doing collaborative/participatory/interesting digital archiving