Wayback Machine
539 captures
28 Mar 2016 - 21 Jan 2026
Nov DEC Jan
04
2019 2020 2021
success
fail
About this capture
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
loading
The Wayback Machine - https://web.archive.org/web/20201204195912/https://slack.engineering/
Skip to content
Slack Engineering
Scaling Datastores at Slack with Vitess

Scaling Datastores at Slack with Vitess

Arka Ganguli Sr. Software Engineer, Infrastructure
Guido Iaquinti Sr. Staff Engineer, Infrastructure
Maggie Zhou Staff Engineer, Infrastructure
Rafael Chacón Staff Software Engineer, Infrastructure
Migrating Slack Airflow to Python 3 Without Disruption
@Ashwin Shankar

Migrating Slack Airflow to Python 3 Without Disruption

Last year, we migrated Airflow from 1.8 to 1.10 at Slack (see here) and we did a “Big bang” upgrade because of the constraints we had. This year, due …
Continue reading …
Creating a React Analytics Logging Library
@Konstantin Savransky@Fabio Canache@Justin Huddleston

Creating a React Analytics Logging Library

Part I
Continue reading …
Bridging the Gap Between Slack and Email Users
@Madhu Balakrishna

Bridging the Gap Between Slack and Email Users

Architecture of Email Bridge
Continue reading …
Building the Next Evolution of Cloud Networks at Slack
@Archie Gunasekara

Building the Next Evolution of Cloud Networks at Slack

At Slack, we’ve gone through an evolution of our AWS infrastructure from the early days of running a few hand-built EC2 instances, all the way to prov…
Continue reading …
The Unsuspecting Beauty & Complexity of Web Forms
@Frances Coronel

The Unsuspecting Beauty & Complexity of Web Forms

Together, we’ll explore the must-add features Slack uses to build web forms that generate leads for successful deals and reflect on the impact they’ve had.
Continue reading …
Starting an Initiative
@Josh Cartmell

Starting an Initiative

Thoughts on starting and continuing an engineering-driven initiative
Continue reading …
Tracing at Slack: Thinking in Causal Graphs
@Suman Karumuri

Tracing at Slack: Thinking in Causal Graphs

“Why is it slow?'' is the hardest problem to debug in a complex distributed system like Slack. To diagnose a slow-loading channel with over a hundred …
Continue reading …
Page1 Page2 Page3 … Page13 Next

@SlackEng how can I stay up-to-date on what's happening over there?

Follow us on Twitter

Most Recent

Scaling Datastores at Slack with Vitess

Scaling Datastores at Slack with Vitess

@Slack Engineering
Migrating Slack Airflow to Python 3 Without Disruption

Migrating Slack Airflow to Python 3 Without Disruption

@Ashwin Shankar
Creating a React Analytics Logging Library

Creating a React Analytics Logging Library

@Slack Engineering
Bridging the Gap Between Slack and Email Users

Bridging the Gap Between Slack and Email Users

@Madhu Balakrishna