About integrations - User Documentation

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/20180604120953/https://help.github.com/articles/about-integrations/

Customizing your GitHub workflow / About integrations

[[#entries]] [[title]] [[/entries]]

About integrations

Integrations are tools and services that connect with GitHub to complement and extend your workflow.

You can install integrations in your personal account or organizations you own. You can also install GitHub Apps from a third-party in a specific repository where you have admin permissions or which is owned by your organization.

Differences between GitHub Apps and OAuth Apps

Integrations can be GitHub Apps, OAuth Apps, or anything that utilizes GitHub APIs or webhooks. For more information, see "Differences between GitHub Apps and OAuth Apps" in the GitHub Developer documentation.

Discovering integrations in GitHub Marketplace and Works with GitHub

You can find an integration to install or publish your own integration in GitHub Marketplace and Works with GitHub.

GitHub Marketplace contains GitHub Apps and OAuth Apps. For more information on finding an integration or creating your own integration, see "About GitHub Marketplace."

You can find other types of approved integrations on Works with GitHub.

Note: You can also submit an integration for inclusion on Works with GitHub. For more information, see "Adding integrations to Works with GitHub" in the GitHub Developer documentation.

Integrations purchased directly from integrators

You can also purchase some integrations directly from integrators. As an organization member, if you find a GitHub App that you'd like to use, you can request that an organization approve and install the app for the organization.

If you have admin permissions for all organization-owned repositories the app is installed on, you can install GitHub Apps with repository-level permissions without having to ask an organization owner to approve the app. You must have When an integrator changes an app's permissions, if the permissions are for a repository only, organization owners and people with admin permissions to a repository with that app installed can review and accept the new permissions.