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.

JuliaBerry is an organisation that brings together various resources for using theJulia language for theRaspberry Pi.
The easiest way to install Julia is by downloading the 32-bit (ARMv7-a hard float) prebuilt binary fromthe JuliaLang website.
An older version of Julia (1.0.3) is also available viaapt in Raspbian, we hope to update this to the latest version in the near future. (This is the easiest way to install Julia and it adds Julia to PATH automatically.)
sudo apt install juliaPlease read below if you would like to compile Julia instead of installing Julia using the methods above.
If you have installed Julia following the instructions above, there is no need to compile Julia. This method takes a very long time and takes up a lot of storage.
For those who are interested in compiling Julia, instructions can be foundover here
This isoptional, and is only for those who needJupyter Notebook.
Jupyter will need to be installed manually, as the automatic Conda installer does not work on the ARM architecture. Generally, running
sudo apt install libzmq3-devsudo pip3 install jupyterat the shell should work. Then it should be sufficient to do
Pkg.add("IJulia")at the Julia REPL.
The JuliaBerry org provides several Raspberry Pi-specific packages:
To get started with Julia, please follow the linkhere to start learning!
We do not have a dedicated mailing list, however questions can be posted to theJulia discourse.
Issues should be filed with the relevant packages: if in doubt which package is appropriate, please ask on the above mailing list.
If you would like to contribute a new package to the JuliaBerry org, open an issue on the repository in question and ping@aviks or@simonbyrne.
If you have any comments or suggestions for the website, please open an issuehere.