recyclarr VS tubearchivist

Recyclarr (GitHub) to automatically update custom formats per the TRaSH Guides. This took some tweaking to get just right, because it also changed my quality definitions, which I didn't want (YTS releases are fine for most of my users, lol).

(Sidenote - this is so I can utilise Recyclarr to sync profiles and formats from Trash guides - https://github.com/recyclarr/recyclarr)

There's also Recyclarr to automatically sync from the trash guides

[https://github.com/recyclarr/recyclarr.

It's also quite automateable: https://github.com/recyclarr/recyclarr

Capable of using TRaSH-Guides profiles for quality definitions and release profiles, similar to Recyclarr. If the TRaSH-Guides profile is updated, Buildarr will sync those updates to your instances.

I follow the TRaSH Guide, for the most part. I have custom formats set up using Notifiarr, and at this point, either using Notifiarr or Recyclarr custom formats is a necessity for any user. If you don't, your searches with Sonarr and Radarr are going to be all over the place.

I use https://github.com/recyclarr/recyclarr/pkgs/container/recyclarr which loads https://trash-guides.info/.

On point 3, I use Recyclarr to keep my release profiles synced up to Trash's current recommendations.

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.