tubeup VS heritrix3

If you want to provide an option to upload artifacts to the Internet Archive, you could crib off of https://github.com/bibanon/tubeup

ArchiveTeam recommends the use of TubeUp.py, which acts as a wrapper for yt-dl to use for comprehensive archival, in addition to automatically uploading the content to the Internet Archive.

What I do is use a tool called tubeup. It will download a YouTube link you give it and automatically upload it to archive.org. It can take single videos or even whole playlists. That way, if it gets removed from YouTube, I know where to find it again, and I don't have to manage local copies or use up own cloud storage.

This can automate a LOT of the manual work: https://github.com/bibanon/tubeup

You could pass a playlist of your liked videos to https://github.com/bibanon/tubeup

I have tried the tubeup project but I spent most of the day trying to make that work but to no avail (I am working on macos Big Sur). I have also seen this post from what seems to be one of the staff, but it seems like a very long and complicated process to take just to archive YouTube videos.

If anyone's interested in web crawling technology, check out Heretrix [1], been around since 2004 and while not the most performant it has incorporated many responsible disciplines in the design and as this article pointed out, WARC format.

1. https://heritrix.readthedocs.io

I've considered running my own IA (https://github.com/internetarchive/heritrix3), which only archives my chrome history, which is stored in a local sqlite db.

I haven't had the time to figure out the details of how the pieces should be glued together.

You can go all the way and use the same tools as the Internet Archive: https://github.com/internetarchive/heritrix3

By the way, the technical side of this is very interesting. If you look at the tools mentioned (the wayback machine, but also perma.cc and other archival solutions), almost all of them rely on a single semi-modern tech stack that produces WARCs (web archives - ISO - ISO 28500:2017 https://iipc.github.io/warc-specifications/specifications/wa...).

The main crawler still seems to be heritrix3 (https://github.com/internetarchive/heritrix3), but there's a great little ecosystem with tools such as webrecorder and warcprox.

Still, I've read through the code of these tools and am feeling that they are failing in the face of the modern web with single page apps, mobile phone apps and walled gardens. Even newer iterations with browser automation are getting increasingly throttled and blocked and excluded from walled gardens.

Perhaps the time has come for a coordinated, decentralized but omnipresent approach to archival.