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 atarchiveteam.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 theWayback 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.
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 athttp://www.archivebot.com.
ArchiveBot's source code can be found athttps://github.com/ArchiveTeam/ArchiveBot.

| Launch Date | Nov. 10, 1968 |
| Launch Site | Baikonur Cosmodrome, Kazakhstan, Russia | Launch Site 1 |
| Destination | Earth’s Moon |
| Type | Flyby (Circumlunar) |
| Status | Partial Success |
| Nation | Soviet Union |
| Alternate Names | 1968-101A, 03535 |
Fly around the Moon and return to Earth, taking photographs and testing the effect of space travel on a biological payload.
Zond was the second Soviet spacecraft to fly to the Moon and back. It took pictures of the lunar near and far sides, but crashed on re-entry. Though the picture film was salvaged, the biological payload was lost.
Nov. 10, 1968:Launch
Nov. 14, 1968: Lunar Flyby
Nov. 17, 1968: Return to Earth
Zond 6 was the second spacecraft that the Soviets sent around the Moon.
Soon after translunar injection, ground controllers discovered that the vehicle's high-gain antenna had failed to deploy. Given that the main attitude- control sensor was installed on the antenna boom, controllers had to make plans to use a backup sensor for further attitude control.
The spacecraft circled the far side of the Moon at a range of 2,420 kilometers, once again taking black-and-white photographs of the Moon.
During the return flight, temperatures in a hydrogen peroxide tank for the attitude-control thrusters dropped far below acceptable levels. Engineers attempted to heat the tank by direct sunlight, but as they later discovered, such a procedure affected the weak pressurization seal of the main hatch and led to slow decompression of the main capsule.
Despite the failures, Zond 6 successfully carried a fully automated guided reentry into the primary landing zone in Kazakhstan.
A radio altimeter, not designed for work in depressurized spacecraft, issued an incorrect command to jettison the main parachutes. As a result, the spacecraft plummeted to the ground and was destroyed. Although the main biological payload was lost, rescuers salvaged film from the cameras.
Launch Vehicle:8K82K + Blok D (Proton-K no. 235-01 / Blok D no. 19)
Spacecraft Mass:about 5,375 kg
Siddiqi, Asif A.Deep Space Chronicle: A Chronology of Deep Space and Planetary Probes 1958-2000, NASA, 2002.