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.
The Y-wing is a workhorse starfighter has been in use since the Clone Wars. Used for dogfights and for bombing runs against capital ships and ground targets, Y-wings are often overshadowed by newer models such as the X-wing and the A-wing. But the Y-wing's historical importance is remarkable, and it has reliably served multiple generations of star pilots.
Y-wings were a useful addition to theRepublic starfighter ranks during the Clone Wars, serving primarily as bombers. Their relative lack of speed and maneuverability made them ill-suited for dogfighting, though skilled pilots could overcome these limitations, pushing the ungainly fighters to their limits while onboard gunners targeted enemies.
AtReklam Station, an Imperial salvage yard, 14 Republic Y-wings were set to be turned to scrap. Coming upon this intel, the Ghost crew attempted to steal the starfighters for the rebellion’s growing fleet. While the mission was not easy, they did come away with the Y-wings, and the station was destroyed in the process.
Y-wings saw service during the Galactic Civil War, withrebelpilots respecting their ability to take a beating in combat and still return home. But these starfighters were showing their age by the time of the struggle against theEmpire – many had been stripped of hull plating and engine nacelles to make maintenance easier, and models that eliminated the gunner’s turret had been introduced. Y-wings took part in the attacks on the Empire’sDeath Stars atYavin andEndor, and were mainstays of the Alliance starfighters corps in the years between those epic battles.
Please upgrade your browser to experience the site.