catball
@catball

You can run an Archive Team container on your computer! It'll help crawl the web and putting stuff into archive.org, based on the current projects.

You don't have to be super technical to do this, but a little computer skill will help you out.

Walkthrough below the cut (tl;dr docker compose + this config, or a vm from here):


catball
@catball

also it's using links fetched from other archived public webpages (as opposed to guessing all imgur urls), so its less likely to pick up anyone's secret images they don't wish to be archived

if you missed it, imgur got bought out and announced that they'll be deleting old images and also any NSFW content starting May 15

...

EDIT: if you feel adventurous and want to spin up some freebie cloud machines to do more archival, here's some free trials from cloud providers:

(not affiliated, just want to enable you to go make a bunch of extra archivers if you want)


atomicthumbs
@atomicthumbs

Edit/bump for those who saw this earlier: I just checked in with people on the archive team IRC before embarking on plan "spin up one trillion Azure container instances;" they're backend-limited right now and don't need any more workers on imgur specifically. if you think it would be fun to do this, set SELECTED_PROJECT to "auto"

i came up with a cloud-init script that configures a Hetzner Cloud server (using the Ubuntu Docker CE cloud image) and starts a Warrior. It may also work with other cloud providers that use cloud-init.

#cloud-config
packages:
  - docker-compose
package_update: true
package_upgrade: true

write_files:
- encoding: b64
  content: [BASE64 ENCODED DOCKER-COMPOSE.YML GOES HERE]
  owner: root:root
  path: /root/docker-compose.yml
  permissions: '0777'
 
runcmd: 
  - docker compose -f /root/docker-compose.yml up -d bind watchtower at_warrior

Edit catball's docker-compose file with your chosen settings, and drop the base64 in place of the bracketed part. A Warrior seems to fit comfortably in 2GB of RAM.


You must log in to comment.

in reply to @catball's post:

It's a little more lightweight / faster, plus watchtower updates are nice.

I mainly used docker since I already have some containers running on my closet server, but didn't already have virtualbox installed

both are reasonable choices!

in reply to @catball's post:

I ended up downloading the .ova, extracting the .vmdk from it (by renaming it to .7z and extracting it lol), and then converting it to .vhdx using qemu-image! runs perfectly under hyper-v, albeit as a gen 1 vm only.

The container only seemed to support amd64 when I tried on my oracle freebie. :( Is there an easy way to modify the base image to run on arm64? I'm honestly that that experienced with docker!

in reply to @atomicthumbs's post: