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/20190424051540/https://github.com/ofrobots

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

ofrobots Follow

Ali Ijaz Sheikh ofrobots

Block or report user

Report or block ofrobots

Contact Support about this user’s behavior.

Learn more about reporting abuse

Google Inc.
SF Bay Area, CA
Sign in to view email

Pinned

nodejs/node

Node.js JavaScript runtime ✨🐢🚀✨

JavaScript 60.4k 13.5k
v8/v8

The official mirror of the V8 Git repository

C++ 12.2k 2.4k
GoogleCloudPlatform/nodejs-docker

The Node.js Docker image used by Google App Engine Flexible.

TypeScript 346 92
googleapis/cloud-trace-nodejs

Node.js agent for Stackdriver Trace: automatically gather latency data about your application

TypeScript 195 84
googleapis/cloud-debug-nodejs

Node.js agent for Stackdriver Debugger: investigate your code’s behavior in production

TypeScript 132 41
v8/node

Forked from nodejs/node

Node.js JavaScript runtime ✨🐢🚀✨

JavaScript 121 44

1,247 contributions in the last year

Activity overview

Contributed to nodejs/node, google/gts, googleapis/nodejs-logging-bunyan and 5 other repositories

Contribution activity

April 2019

ofrobots/js-green-licenses TypeScript Apr 10
ofrobots/ivy-perf TypeScript Apr 2

Created a pull request in googleapis/nodejs-logging that received 9 comments

Release @google-cloud/logging v4.5.2

This pull request was generated using releasetool.

+11 −2 • 9 comments

feat: build on top of module pprof Apr 23
doc: remove experimental from docs Apr 23
feat: get data in DevTools format Apr 23
chore(deps): update dependencies Apr 23

build: test on node 12 Apr 23
deps: switch to @npm/types for package.json types Apr 15
[DO NOT REVIEW] chore(deps): lock file maintenance Apr 15

feat: auto-detect service context Apr 5
fix: proper signature for _write[v] Apr 2

chore(deps): update deps Apr 16
feat: ability to get heap profile in V8 format Apr 4

docs: update README/samples to target winston@3 Apr 18
refactor!: only support winston3 Apr 10

fix: export render function Apr 2

meta: move ofrobots to TSC emeritus Apr 3

fix: audit fix Apr 4

fix(types): improve types for LogEntry Apr 10

build!: drop support for Node 6 Apr 10

feat: introduce a new API for consumer tests Apr 11

Avoid pathological out of memory on large datasets Apr 23

Release @google-cloud/logging-winston v0.11.1 Apr 10
fix: only copy timestamp metadata if it is a date Apr 9
refactor: use execSync for tests Apr 4

Feature (closes #312) : template code at init Apr 22
chore(deps): lock file maintenance Apr 15

chore(deps): update dependency nyc to v14 Apr 16
chore(dep): update mocha to 6.1 Apr 11

docs: update the README badges Apr 12
refactor: prefer promisify to pify Apr 12

chore(dep): update mocha to 6.1 Apr 11

test: simplify os mocking Apr 10

docs: update badges on the README Apr 10

Updated h2-auto-push to 0.4.1 Apr 9

fix: in Koa2 interface await `next` as a function Apr 9

test: better return type for typescript 3.4.0 Apr 5

fix: don't let trace context injection throw Apr 2

Created an issue in googleapis/nodejs-logging that received 2 comments

Signature for `log.write`

Log.prototype.write has the following signatures: write(entry: Entry|Entry[], options?: WriteOptions): Promise<ApiResponse>; write( entry: Entry|E…

2 comments

Wrong types for `Entry` Apr 2

express middleware doesn't allow user to configure custom transports Apr 23

You can’t perform that action at this time.