From e690da0174be80e66fbde2dc97b0d9fe39ce8918 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2018 16:23:51 -0400 Subject: [PATCH] followup --- ..._aef7c172d485f8f6570ada5756446480._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/importfeed_does_not_work_with_youtube_anymore/comment_3_aef7c172d485f8f6570ada5756446480._comment diff --git a/doc/forum/importfeed_does_not_work_with_youtube_anymore/comment_3_aef7c172d485f8f6570ada5756446480._comment b/doc/forum/importfeed_does_not_work_with_youtube_anymore/comment_3_aef7c172d485f8f6570ada5756446480._comment new file mode 100644 index 0000000000..42b42f9eac --- /dev/null +++ b/doc/forum/importfeed_does_not_work_with_youtube_anymore/comment_3_aef7c172d485f8f6570ada5756446480._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2018-11-12T20:17:31Z" + content=""" +There is actually a way to construct a rss feed url that will work, +but nowhere in youtube can you find the url. +[[tips/downloading_podcasts]] discusses how the url looks like; finding the +`channel_id` value for a given youtube page tends to involve grepping the +html or some third-party tool. + +If youtube-dl had a way to extract the `channel_id`, I suppose I might make +git-annex use it. Although leaving the user to jump through the absurd +hoops google has set up to find an rss feed does highlight just how +user-hostile and standard-hostile Google is being here; it sends some +important signals to the user about the entity they're interacting with, +their business model, and how likely the rss feed is to break in the +future. +"""]]