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/20190423220350/https://github.com/veggiemonk

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

veggiemonk Follow

building something useful without building it alone

Julien Bisconti veggiemonk

Block or report user

Report or block veggiemonk

Contact Support about this user’s behavior.

Learn more about reporting abuse

Citizen of the world. Software Engineer / Site Reliability Engineer. Scalable distributed systems. Writing YAML and googling errors

Stockholm, Sweden
https://veggiemonk.github.io/

Organizations

Pinned

awesome-docker

🐳 A curated list of Docker resources and projects

14.7k 1.7k
kubernetes-vagrant

Spin up a single kubernetes node in a VM and use kubectl to manage it

Shell 2
presentation

Presentation

JavaScript 3
skip-commit

GitHub Action: skip based on the last commit message containing a string

Dockerfile
go-submodules-example

Go 1
redis-data-estimation

Estimate how much data you will use in redis to choose the right size DB / instance on the cloud

JavaScript 1

1,120 contributions in the last year

Activity overview

Contributed to veggiemonk/awesome-docker, veggiemonk/blog, veggiemonk/veggiemonk.github.io and 5 other repositories

Contribution activity

April 2019

veggiemonk/cloud-builders-community Dockerfile Apr 12
veggiemonk/terraform-google-iam Apr 12

Created a pull request in terraform-google-modules/terraform-google-iam that received 1 comment

Fix subnet example

The variable subnet_two was not used for defining the locals subnet_full_two

+1 −1 • 1 comment

Update docker-compose to 1.24.0 on bionic Apr 12
Update docker-compose to 1.24.0 on bionic Apr 12

Fix redirect Apr 6

You can’t perform that action at this time.