| Aug | SEP | Oct |
| 09 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Collection: Archive Team: The Github Hitrub
$ npm install @github/query-selector
query(context, selector, klass)
●querySelectorAll(context, selector, klass)
●closest(element, selector, klass)
●namedItem(element, name, klass)
●getAttribute(element, name)
import {closest, getAttribute, namedItem, query, querySelectorAll} from '@github/query-selector' // Find an element by selector and type, or throw if not found. const image: HTMLImageElement = query(document, '.avatar', HTMLImageElement) image.src = '/hubot.png' // Find the parent by selector and type, or throw if not found. const parent: HTMLDetailsElement = closest(image, '.container', HTMLDetailsElement) parent.open = true // Filter all children by selector and type. const inputs: Array<HTMLInputElement> = querySelectorAll(document, 'input', HTMLInputElement) for (const input of inputs) { input.value = '' } // Retrieve the attribute's value or throw. const url: string = getAttribute(image, 'data-url') // Find the form's `input[name=login]` field or throw if not found. const form: HTMLFormElement = query(document, 'form', HTMLFormElement) const input: HTMLInputElement = namedItem(form, 'login')
const el = document.querySelector('.expected-element') // el may be null! el.classList.add('selected') el.setAttribute('title', 'hello')A safer alternative is to guard against null values with a conditional statement.
const el = document.querySelector('.expected-element') if (el) { el.classList.add('selected') el.setAttribute('title', 'hello') }Even if found, the element may be of the wrong type.
const el = document.querySelector('.expected-element') if (el) { // Element might not have a value property! el.value = 'hello' }Adding an
instanceof test would verify the element has the properties and
methods we expect.
const el = document.querySelector('.expected-element') if (el instanceof HTMLInputElement) { el.value = 'hello' }Because
document.querySelector is so frequently used in web applications,
and it's tedious to guard every element query with null checks, these tests
are most often omitted. When using Flow, however, these tests become
required to pass the type checker.
The combination of null tests and subclass type refinements feels like we're
working against the type system, rather than with it. So, typed query functions
consider a missing element, or an element of the wrong type, to be failed
assertions and throw an exception to fail as early as possible.
npm install
npm test