Your security on GitHub, as well as every other account you have on the Web, is best served with a strong password that isn't shared with any other person, service, or site.
| May | JUN | Jul |
| 04 | ||
| 2017 | 2018 | 2019 |
COLLECTED BY
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.
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.
Your security on GitHub, as well as every other account you have on the Web, is best served with a strong password that isn't shared with any other person, service, or site.
When you create a password for your GitHub user account, we automatically disallow some things that can make your password insecure, such as:
However, there are additional things you should consider that we can't control. You have the power to protect yourself!
You probably already know that a good password is a word or sequence of at least 12 characters with a combination of lower- and upper-case letters, numbers, and special characters.
However, a much better password is a passphrase with at least 16 characters. For example, "canaries baseball clock dreams" (with a hat tip to XKCD) is very strong and difficult to guess, but also easy for you to remember.
"Sharing" your password can be intentional or unintentional.
Telling anyone your password--even a potential collaborator on a repository--makes you vulnerable to security breaches. GitHub has a few different ways to let you collaborate with others and keep your account private.
If your password is tricky to remember, writing it down somewhere, such as on a piece of paper near your computer, is like not having a password at all. If anyone were to see that piece of paper, you'd be in big trouble.
Instead, use a personal password manager such as LastPass, 1Password, or Keeper.
Your GitHub password should not only be unique to you, it should be unique to GitHub. Attackers know that people tend to reuse the same password for multiple accounts because they're easier to remember that way. If your password is guessed on another service, it could be guessed here on GitHub.
Warning: Security incidents at other companies have provided criminals with vast lists of valid user names, email addresses, and passwords that are used in attempts to access your encrypted data all over the internet.
Unless you have an award-winning memory, it can be very difficult to remember unique passwords for all accounts and services you use. To keep track of your passwords, use a personal password manager such as LastPass, 1Password, or Keeper.
Think of two-factor authentication as a second metal door an intruder has to work hard to bust through after they've successfully picked the lock on the first one. For more information, see "About two-factor authentication."
© 2018 GitHub Inc. All rights reserved.