COLLECTED BY
Organization:
Archive Team

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.
ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).
To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.
There is a dashboard running for the archivebot process at http://www.archivebot.com.
ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.
The Wayback Machine - https://web.archive.org/web/20190921223921/http://www.catb.org/~esr/BROWSER/index.html
The BROWSER project
What comes next after the classic Unix environment variables
PAGER
, MAILER
, and
EDITOR
?
This is the BROWSER
project page -- an effort to
promulgate a convention for expressing your browser preference to
programs which must call browsers to view URLs. Nowadays many
programs must do this; mailer user agents and on-line help systems
are just two of the most obvious application classes.
How BROWSER works:
The value of BROWSER may consist of a colon-separated series of
browser command parts. These should be tried in order until one
succeeds. Each command part may optionally contain the string "%s";
if it does, the URL to be viewed is substituted there. If a command
part does not contain %s, the browser is to be launched as if the
URL had been supplied as its first argument. The string %% must be
substituted as a single %.
Rationale: We need to be able to specify multiple browser
commands so programs obeying this convention can do the right thing
in either X or console environments, trying X first. Specifying
multiple commands may also be useful for people who share files
like .profile across multiple systems. We need %s because some
popular browsers have remote-invocation syntax that requires it.
Unless %% reduces to %, it won't be possible to have a literal %s
in the string.
For example, on most Linux systems a good thing to do would
be:
BROWSER="netscape -raise -remote \"openURL(%s,new-window)\":lynx"
Who observes this convention?
In the near future, any Python program that uses the
standard-library webbrowser.py module. This module, which debuted
in Python 2.0, was taught how to interpret BROWSER
in
CVS on 23 Jan 2001, and will be released in Python 2.1a2.
On 24 Jan 2001, a BROWSER
patch against the 0.9 version was sent to
the maintainers of urlview.
On 24 Jan 2001, a BROWSER
patch was sent to the maintainer of the
browser-launch code in GNU Emacs.
On 24 Jan 2001, a patch against the
environ(5) man page was sent to Andries Brouwer, the Linux man page
maintainer, adding BROWSER
to the set of documented
environment variables. Andries merged in an edited version within
hours.
On 25 Jan 2001, Pavel Roskin told me "I hope to be able to
implement $BROWSER support in xpdf but I cannot promise it."
What still needs to be done?
Key people in the Perl and Tcl communities (including Larry
Wall) have agreed that it would be a good thing for the URL-viewing
facilities in their language libraries to interpret
BROWSER
, but this has not been done yet.
If you implement BROWSER
support somewhere, please
let me know for this page.
Eric S. Raymond <esr@thyrsus.com>