38 captures
26 Jun 2017 - 22 Aug 2025
Aug SEP Oct
16
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/20200916092850/https://github.com/4Catalyzer/javascript
Skip to content
Sign in Sign up
  • Star
  • Fork 2
  • 4Catalyzer JavaScript Tooling

    MIT License
    12 stars 2 forks
    Star
    Watch
    master
    6 branches 251 tags
    Go to file
    Code

    If nothing happens, download GitHub Desktop and try again.

    If nothing happens, download GitHub Desktop and try again.

    If nothing happens, download Xcode and try again.

    If nothing happens, download the GitHub extension for Visual Studio and try again.

    Latest commit

     

    Git stats

    Files

    Permalink
    Failed to load latest commit information.
    Type
    Name
    Latest commit message
    Commit time
    packages
     
     
    tools
     
     
    .eslintrc
     
     
    .gitignore
     
     
    .travis.yml
     
     
    LICENSE
     
     
    README.md
     
     
    lerna.json
     
     
    package.json
     
     
    renovate.json
     
     
    yarn.lock
     
     

    README.md

    4Catalyzer JavaScript Style Guide

    An utterly unreasonable JavaScript style guide, mostly for trolling @jquense.

    Use the Airbnb JavaScript style guide, except where it conflicts with how prettier would handle it. Also use prettier.

    Exceptions

    This guide is intended to present general guidelines. Most modules should follow this style guide and pass the associated lint checks. However, specific modules should freely disregard specific guidelines and use corresponding ESLint pragmas whenever necessary. Disable the relevant rule or rules with eslint-disable, and enable them again with eslint-enable when you're done.

    function renderApp() {
      /* eslint-disable global-require */
      const ClientApplication = require('./ClientApplication');
      /* eslint-enable global-require */
    
      ReactDOM.render(
        <AppContainer>
          <ClientApplication />
        </AppContainer>,
        document.getElementById('app'),
      );
    }

    Directory layout

    Follow the React Router huge-apps example. Use shared/ at the deepest possible level for shared modules.

    Line width

    79 characters, because @taion doesn't want to have to resize the width of his buffers when switching between JavaScript and PEP 8-compliant Python.

    About

    4Catalyzer JavaScript Tooling

    Resources

    Readme

    License

    MIT License

    Releases

    251 tags

    Packages

    No packages published

    Contributors 12

  • Languages

  • Privacy
  • Security
  • Status
  • Help
  • You can’t perform that action at this time.