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.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

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.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20190424075023/https://github.com/lizrice

Create your own GitHub profile

Join the platform over 31 million developers call home for hosting code, managing projects, and building their best software.

Sign up for free See pricing for teams and enterprises

lizrice Follow

Liz Rice lizrice

Block or report user

Report or block lizrice

Contact Support about this user’s behavior.

Learn more about reporting abuse

Popular repositories

containers-from-scratch
Writing a container in a few lines of Go code, as seen at DockerCon 2017 and on O'Reilly Safari

Go 415 58
strace-from-scratch
As seen at Gophercon 2017

Go 214 16
debugger-from-scratch

Go 75 4
secure-connections
Simple client and server for showing what's happening with certificates during TLS setup

Go 48 4
running-with-scissors
Resources from my KubeCon + CloudNativeCon keynote

27 1
no-meltdown
Resources for "Don't Have A Meltdown"

Go 26 1

639 contributions in the last year

Contribution activity

April 2019

Created a pull request in aquasecurity/kube-bench that received 3 comments

Json & YAML config, continued

Building on the work that @Pluies did in #239

+880 −39 • 3 comments

Add possibility of SIG assessment Apr 12
Update about community / project presentations Apr 12
Add link to new SIGs doc Apr 3

Add OCP info into the README Apr 23
Don't assume master if 0 master binaries specified Apr 11

update files Apr 23
Add ":" as a valid flag-value separator for tests Apr 11
WIP: Rationalize and document config Apr 10
JSON & YAML tests Apr 2

Bugfix: Tests with multiple values evaluate the first value instead of all Apr 12

.gitignore: Add the built binary to the list Apr 10

Created an issue in cncf/foundation that received 3 comments

RFC: Code of Conduct should be requirement for all CNCF projects

According to this criteria doc, the CNCF code of conduct appears to be required only at Graduation. Is there any reason not to require this of all …

3 comments

Clearer output for failed audit commands Apr 23
RFC: retire federated checks Apr 10

You can’t perform that action at this time.