horahora VS tubearchivist

doing beta test of horahoradev/horahora: Self-hosted media server and community youtube-dl/yt-dlp archival manager (github.com) . This is the prelude to the public beta. You can comment here or message me if you're willing to test the current version.

it's: https://github.com/horahoradev/horahora/tree/revolt (the revolt branch) then https://github.com/horahoradev/revite (my fork of Revite)

I'll just host an instance of horahoradev/horahora: Self-hosted media server and community youtube-dl/yt-dlp archival manager (github.com) on OVH with Backblaze as the source of video storage. I'll appoint a few people I trust as admins, who can add URLs to archive.

Maybe someone knows of something like horahora except with gallery-dl/image support. (or does it support images? I don't use it)

Try with one of the images under his/her packages. https://github.com/horahoradev/horahora/pkgs/container/horahora

holy hell I hadn't come across archivebox as of yet, I'll definitely be spinning this up this eve. Is the UI comfortable enough to use as a "bookmark manager"? just been setting up tubearchivist for essentially this purpose, wondering if ArchiveBox would essentially do the same

I'm using TubeArchivist to maintain this VERY large collection.

There appears to be a patch in Tubearchivest at https://github.com/tubearchivist/tubearchivist/issues/587

Personally, I use Tubearchivist.

There are others though.

https://github.com/tubearchivist/tubearchivist

I've been seeing TubeArchivist posted a lot recently.

It has been some time since the last release, but v0.4.0 is finally wrapped up. This brings a wide range of fixes and changes, particularly stability improvements, with our new file system naming convention, this should solve a bunch of previously unsolvable compatibility issues. I highly recommend reading the release notes carefully, as the filesystem migration could be a breaking change if you made changes manually there: https://github.com/tubearchivist/tubearchivist/releases/tag/v0.4.0

I saw this was a Django app so I dug around to look at their models. As far as I can tell this is all they have: https://github.com/tubearchivist/tubearchivist/blob/master/t... - just a `Account` model.

It looks like Django + SQLite is used for user accounts, but all other data storage happens in Elasticsearch.

It's an interesting design decision. I would have gone all-in on the database, and used SQLite FTS in place of Elasticsearch for simplicity, but that's my own personal favourite stack. Not saying their design is bad, just different.

Oh, so it is. I happen to run a TubeArchivist at home that grabs the videos and subtitles. Then I can search through the subtitle files for key phrases. I must have grabbed it while it was still public.

You probably want Tube Archivist. The only problem is that it’s naming convention doesn’t work with the Jellyfin YouTube Metadata Plugin.