Youtube Support #124

Closed
opened 2025-05-04 23:20:35 -04:00 by rainbownapkin · 6 comments
rainbownapkin commented 2025-05-04 23:20:35 -04:00 (Migrated from gitlab.com)

Youtube is a mainstay of the TTN community, and must be treated as a first-class media source. Unfortunately, it's also a pain in the ass to work with, and it seems like it's on purpose.

Youtube is a mainstay of the TTN community, and must be treated as a first-class media source. Unfortunately, it's also a pain in the ass to work with, and it seems like it's on purpose.
rainbownapkin commented 2025-05-04 23:23:00 -04:00 (Migrated from gitlab.com)

added #126 as child task

added #126 as child task
rainbownapkin commented 2025-05-04 23:30:58 -04:00 (Migrated from gitlab.com)

added #127 as child task

added #127 as child task
rainbownapkin commented 2025-05-04 23:32:50 -04:00 (Migrated from gitlab.com)

added #129 as child task

added #129 as child task
rainbownapkin commented 2025-05-05 05:13:21 -04:00 (Migrated from gitlab.com)

Looks like piped instances are nearly as useless as invidious ones, except at least some of the remaining invidious instances disabled API access and made rotating IP's to at least server their human friendly front-end

Piped seems completely dead for non-selfhosters.

Maybe if YTDLP ends up having serious unworkable flaws, we might use a local piped instance, potentially off of a different IP, to run things. However for now YTDLP alone may be a better choice.

Otherwise if the issue is merely with the scraper and not our IP getting banned by google, we could, in the future, grab data from piped-backend or NewPipeExtractor directly.

Also google can eat shit for working on turning youtube into an un-scrapable Library of Alexandria, and also actively contributing to a fucking genocide.

Looks like piped instances are nearly as useless as invidious ones, except at least some of the remaining invidious instances disabled API access and made rotating IP's to at least server their human friendly front-end Piped seems completely dead for non-selfhosters. Maybe if YTDLP ends up having serious unworkable flaws, we might use a local piped instance, potentially off of a different IP, to run things. However for now YTDLP alone may be a better choice. Otherwise if the issue is merely with the scraper and not our IP getting banned by google, we could, in the future, grab data from piped-backend or NewPipeExtractor directly. Also google can eat shit for working on turning youtube into an un-scrapable Library of Alexandria, and also actively contributing to a fucking genocide.
rainbownapkin commented 2025-05-10 12:30:27 -04:00 (Migrated from gitlab.com)

added #148 as child task

added #148 as child task
rainbownapkin (Migrated from gitlab.com) closed this issue 2025-05-10 18:51:33 -04:00
rainbownapkin commented 2025-05-10 18:51:35 -04:00 (Migrated from gitlab.com)

Youtube support complete.

Youtube support complete.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#124
No description provided.