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/20231124172540/https://docs.github.com/de/[email protected]/github/authenticating-to-github/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key

Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen findest Du in unserer englischsprachigen Dokumentation.

Deutsch

Diese Version von GitHub Enterprise wurde eingestellt am 2021-06-09. Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für eine bessere Leistung, verbesserte Sicherheit und neue Features nimm ein Upgrade auf die neueste Version von GitHub Enterprise vor. Wende Dich an den GitHub Enterprise-Support, um Hilfe beim Upgrade zu erhalten.

Artikelversion: Enterprise Server 2.21

See all Enterprise releases

Artikelversion: Enterprise Server 2.21

See all Enterprise releases

Eine verifizierte E-Mail-Adresse in Deinem GPG-Schlüssel verwenden

Bei der Verifizierung einer Signatur überprüft GitHub Enterprise Server, ob die E-Mail-Adresse des Beitragenden oder des Taggers mit einer E-Mail-Adresse aus den Identitäten des GPG-Schlüssels übereinstimmt und ob es sich dabei im Konto des Benutzers um eine verifizierte E-Mail-Adresse handelt. Dadurch wird sichergestellt, dass der Schlüssel zu Dir gehört und dass Du den Commit oder das Tag erstellt hast.

Wenn Du eine E-Mail-Adresse aktualisieren oder zu Deinem GPG-Schlüssel hinzufügen musst, findest Du weitere Informationen unter „Eine E-Mail-Adresse mit Deinem GPG-Schlüssel verknüpfen.“

Commits und Tags können verschiedene E-Mail-Adressen enthalten. Für Commits gibt es den Autor (die Person, die den Code geschrieben hat) und den Beitragenden (die Person, die den Commit zur Struktur hinzugefügt hat). Wenn Du mit Git einen Commit signierst, wird unabhängig davon, ob es sich um einen Merge, um Cherry-Picking oder um einen normalen git commit handelt, die Beitragender-E-Mail-Adresse Deine eigene sein, auch wenn die Autoren-E-Mail-Adresse eine andere ist. Tags sind einfacher. Die Tagger-E-Mail-Adresse ist immer der Benutzer, der das Tag erstellt hat.

Wenn Du Deine Beitragender- oder Tagger-E-Mail-Adresse ändern musst, findest Du weitere Informationen unter „E-Mail-Adresse für Commits festlegen.“

Weiterführende Informationen

„Informationen zur Verifizierung einer Commit-Signatur“

Still need help?

Ask the GitHub community Support kontaktieren