839 captures
05 Jun 2010 - 28 Jan 2026
Nov DEC Jan
11
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
The Wayback Machine - http://web.archive.org/web/20201211210103/https://github.com/nodejs
Skip to content
Sign in Sign up
@nodejs

Node.js

  • Pinned repositories

    1. Node.js JavaScript runtime 🐢🚀

      JavaScript 75.3k 18.8k

    2. Node.js Release Working Group

      2.6k 372

    3. Need help with Node.js? File an Issue here. 🚀

      895 224

    4. Node.js native addon build tool

      Python 7k 1.3k

    5. Module for using N-API from C++

      C++ 1k 252

    6. The Node.js Community Committee (aka CommComm)

      217 85

    Language: All
    Select language

    Repositories

    JavaScript 18,775 75,304 994 (85 issues need help) 258 Updated Dec 11, 2020
  • remark preset to configure remark-lint with settings for nodejs/node

    JavaScript MIT 16 9 3 1 Updated Dec 11, 2020
  • The Node.js website.

    nodejs node
    JavaScript 3,543 1,618 53 (5 issues need help) 31 Updated Dec 11, 2020
  • Module for using N-API from C++

    nodejs node
    C++ 252 1,010 81 (1 issue needs help) 10 Updated Dec 12, 2020
  • `node debug` for `node --inspect`

    nodejs node cli-debugger
    JavaScript MIT 51 285 18 3 Updated Dec 11, 2020
  • Better build and test infra for Node.

    nodejs node
    Shell 133 306 86 (2 issues need help) 6 Updated Dec 11, 2020
  • Node.js snap source and updater

    Shell MIT 2 5 0 0 Updated Dec 11, 2020
  • A new Node.js resource built using Gatsby.js with React.js, TypeScript, and Remark.

    nodejs node hacktoberfest
    TypeScript MIT 394 1,356 37 (12 issues need help) 33 Updated Dec 11, 2020
  • Generating parsers in LLVM IR

    finite-state-machine llvm-ir
    TypeScript 18 414 8 3 Updated Dec 11, 2020
  • Official Docker Image for Node.js 🐳 🐢 🚀

    nodejs docker node docker-image docker-node
    Dockerfile MIT 1,410 6,095 54 (3 issues need help) 15 Updated Dec 11, 2020
  • The Node.js Internationalization Working Group – A Community Committee initiative.

    nodejs i18n node internationalization crowdin community-committee
    JavaScript MIT 38 104 20 (1 issue needs help) 4 Updated Dec 11, 2020
  • An HTTP/1.1 client, written from scratch for Node.js

    JavaScript MIT 33 498 37 (5 issues need help) 1 Updated Dec 11, 2020
  • @nodejs-github-bot's heart and soul

    nodejs javascript bot node github-bot
    JavaScript MIT 122 204 27 5 Updated Dec 10, 2020
  • A repository of runnable Node.js examples that go beyond "hello, world!"

    nodejs node examples
    JavaScript MIT 41 47 12 5 Updated Dec 10, 2020
  • Node.js Diagnostics Working Group

    nodejs node
    MIT 66 420 38 4 Updated Dec 10, 2020
  • Node.js Release Working Group

    nodejs node
    372 2,627 27 1 Updated Dec 10, 2020
  • Node.js C++ addon examples from http://nodejs.org/docs/latest/api/addons.html

    nodejs node
    TypeScript 471 1,647 33 5 Updated Dec 10, 2020
  • The Node.js Technical Steering Committee

    nodejs node
    104 288 21 2 Updated Dec 9, 2020
  • Port of http_parser to llparse

    llvm http-parser llparse
    TypeScript 58 769 6 0 Updated Dec 9, 2020
  • Node.js native addon build tool

    nodejs node-gyp node gyp node-addon
    Python MIT 1,305 7,043 49 24 Updated Dec 8, 2020
  • Experimental Node.js mirror on V8 lkgr 🐢🚀

    nodejs node
    JavaScript 50 247 9 2 Updated Dec 8, 2020
  • Repository for work for discussion of helping with maintenance of key packages in the ecosystem.

    147 365 62 (9 issues need help) 3 Updated Dec 8, 2020
  • Facilitating joint collaboration amongst the TSC and CommComm

    nodejs node
    138 59 45 (2 issues need help) 4 Updated Dec 8, 2020
  • Guidelines for the Node.js Twitter and automation through PRs to tweet.

    4 6 0 0 Updated Dec 7, 2020
  • 'string_decoder' module from Node.js core

    nodejs node
    JavaScript 17 22 5 1 Updated Dec 6, 2020
  • Repository for discussion on strategic directions for next 10 years of Node.js

    4 82 5 1 Updated Dec 4, 2020
  • A fork of the GYP build system for use in the Node.js projects

    Python BSD-3-Clause 19 30 10 (1 issue needs help) 5 Updated Nov 29, 2020
  • Node.js Benchmarking Working Group

    nodejs node
    Shell 51 156 39 (1 issue needs help) 0 Updated Nov 28, 2020
  • node.js 한국 커뮤니티

    nodejs node korean
    Stylus 69 237 20 4 Updated Nov 26, 2020
  • CLI tools for Node.js Core collaborators

    nodejs node
    JavaScript MIT 77 137 21 (1 issue needs help) 6 Updated Nov 24, 2020
  • Top languages

    JavaScript Shell C++ TypeScript HTML

    Most used topics

    nodejs node community-committee iojs javascript

    People

    @zeke @tdd @jdalton @dshaw @indexzero @rubys @AbeEstrada @watson @lance @hemanth @apapirovski @okuryu @rogeriopvl @Delapouite @ljharb @mcollina @hmalphettes @dougwilson @WebReflection @refack
  • Privacy
  • Security
  • Status
  • Help
  • Contact GitHub
  • Pricing
  • API
  • Training
  • Blog
  • About
  • You can’t perform that action at this time.
    Essential cookies

    We use essential cookies to perform essential website functions, e.g. they're used to log you in. Learn more

    Always active
    Analytics cookies

    We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task. Learn more