YouTube archiving made simple. Contribute to Owez/yark development by creating an account on GitHub.
adr1an
link
fedilink
English
1224d

This is oooold. Like in, it was superseded long agooo.

@Darkassassin07@lemmy.ca
link
fedilink
English
524d

Yeah, 2.5+ years since the last release?

Somehow I don’t think this has survived youtubes client war…

@raldone01@lemmy.world
link
fedilink
English
222d

Take a look at tubearchivisit. Works great and is in development.

@Showroom7561@lemmy.ca
link
fedilink
English
1424d

“Made simple”, but it’s all command prompt with no UI 🙂

Not knocking it, as I’m sure it works great, but these things end up being a huge barrier to adoption and use by the regular people who might be “self-hosted curious”.

I use tubesync, works great

@Showroom7561@lemmy.ca
link
fedilink
English
224d

I’m using Tube Archivist. Works great, too.

I tried it but it’s pretty complex compared to tubesync and uses weird af filenames, unusable for media servers

@Showroom7561@lemmy.ca
link
fedilink
English
323d

Yeah, the weird filenames bothers me, too. It does take a hit to data portability, for sure. I’m not using it for some kind of long-term, bomb-proof YouTube archiving, but more to have offline access to instructional videos I might need in the near future. For that, the UI and integration with Jellyfin works well for me.

If I was actually collecting youtube videos, I would go with something else that generates human-friendly folders and filenames! I’ll bookmark Tubesync :)

@beeb@lemm.ee
link
fedilink
English
624d

And install python and install those dependencies before you can even run the thing

@Grunt4019@lemm.ee
link
fedilink
English
322d

To be fair it’s “made simple” not “made easy”

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.47K Posts
  • 69.3K Comments
  • Modlog