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/20200916083316/https://github.com/mmarchini

mmarchini Follow

mmarchini Follow

mary marchini mmarchini

BPF and stuff; @nodejs TSC; http://pronoun.is/she

Follow

121 followers · 13 following · 146

Highlights

Arctic Code Vault Contributor

Organizations

Pinned

sthima/libstapsdt

Create Systemtap's USDT probes at runtime

C 61 12
iovisor/bpftrace

High-level tracing language for Linux eBPF

C++ 3k 400
nodejs/llnode

An lldb plugin for Node.js and V8, which enables inspection of JavaScript states for insights into Node.js processes and their core dumps.

C++ 871 90
nodejs/node

Node.js JavaScript runtime ✨🐢🚀✨

JavaScript 73k 18k
v8/v8 Mirror

The official mirror of the V8 Git repository

C++ 16k 3.1k
mmarchini-oss/node-linux-perf

C++ 29 6

1,754 contributions in the last year

Activity overview

Contributed to nodejs/node, mmarchini-oss/llnode-v8-tester, mmarchini-oss/automated-merge-test and 5 other repositories

Contribution activity

September 2020

mmarchini/email JavaScript Sep 5

Created a pull request in nodejs/admin that received 7 comments

doc: require main default branch before transfer

Our org default branch is set to main, so it makes sense to also require new repositories being transferred to the org to follow the same pattern.

+3 −0 • 7 comments

doc: split supported platforms table Sep 16
meta: notify slack when someone force pushes Sep 9
meta: add links to OpenJSF Slack Sep 9
doc: change requirements for objection dismissal Sep 3

feat: reduce gthub app/secret requirements Sep 14

chore: add link to OpenJSF Slack channel Sep 9

feat(charter): introduce emergency and async votes Sep 5

aliases: add mmarchini to build alias Sep 5

chore(ci): add release-please and npm publisher Sep 4

build: add Commit Queue actions url to failure comment Sep 15
process: Change default --unhandled-rejections=throw Sep 14
build: add build artifact to CI Sep 13
meta: update my collab entry Sep 12
build: filter issues & PRs to auto close by matching on stalled label Sep 11
doc: update contact info for Ash Cripps Sep 10
v14.10.1 proposal Sep 10
Revert "build: require "allow edits" to be checked" Sep 7
util: add util.parseArgs() Sep 3
build: use purple merge instead of close on CQ Sep 3
doc: revise commit-queue.md Sep 1

chore: release 4.0.0 Sep 4
chore: release 4.0.0 Sep 4

build,infra: onboard mmarchini and richardlau to build/infra Sep 15

chore(git-node): avoid dealing with patch files for landing Sep 10

GitHub Actions: Test Python 3.9 release candidate 1 Sep 9

doc: add minutes for meeting 2 Sep 2020 Sep 2

Created an issue in nodejs/node-v8 that received 12 comments

Automatic V8 DEPS detection

I'm trying to find a way for us to auto sync V8 dependencies without needing to manually list them and without having to manually parse the DEPS fi…

12 comments

What trade-offs are we willing to have with our next meta build system? Sep 1
Re-evaluate our approach to in-tree dependencies Sep 1
Devise a migration plan for native addons Sep 1
Infrastructure plan Sep 1
GN an Ninja platform support Sep 1
Investigate feasibility and challenges hybrid builds Sep 1

Don't require full CI when `.github/` is the only change (and others) Sep 13
Collect analytics, logs, capture errors Sep 10
ncu-ci broken Sep 6

Add SLACK_WEBHOOK secret to nodejs/node-v8 Sep 14
Add SLACK_WEBHOOK secret to nodejs/node Sep 9

Restructure repository branches Sep 13
Move `node-update-v8-canary` to GitHub Actions Sep 13

The penguin is not showing Sep 6
Paste behavior should be better Sep 6

Reaching a decision on "drop minimum wait time" Sep 10

Next 10 years for collaborators Sep 1

You can’t perform that action at this time.