Maybe I‘m completely stuck but can somebody please explain the usecase of self hosting TubeArchivist?

https://github.com/tubearchivist/tubearchivist

Why would I rather download the content and watch it locally instead of watching it directly on YT?

      • EleventyTwatWaffles@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        it took up like a gig of memory before i even had even logged into it. i think it’s because the author uses elasticsearch which just felt like overkill for what i thought it aimed to accomplish

        • PhuriousGeorge@alien.topB
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          There’s definitely some overhead. ES is used as a DB to integrate search functionality. I know you can do close or similar with other DBs, but that’s what they went with. It works pretty good on my archive (as far as the team is aware, I’m the heaviest user). I’ve got comments, subtitles in ES as well, all searchable.

          You can limit the RAM ES has available to it with Java arguments if you care.