X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/582e52d3ca79d0d5d0335486718fe2167d6304cd..b8851008f1047fe884705c7698785e87a9e72b69:/doc/todo/fancypodcast.mdwn

diff --git a/doc/todo/fancypodcast.mdwn b/doc/todo/fancypodcast.mdwn
index 7ffff6252..e26893e48 100644
--- a/doc/todo/fancypodcast.mdwn
+++ b/doc/todo/fancypodcast.mdwn
@@ -30,8 +30,12 @@ Episode enclosure  |(./)      |(./)       |(./)        |(./)
 
 * [iTunes-specific tags](https://www.apple.com/itunes/podcasts/specs.html)
   appear to be RSS-only
-    * If they work in Atom, teach `inline` to optionally iTunesify RSS/Atom.
-    * Else, add `itunes` as a third kind of feed (RSS plus more stuff).
+    * Can we always include them in RSS feeds, or would that break
+      some feed readers?
+    * Is it even valid to include them in Atom feeds? If so, do
+      Atom podcasts look any better in podcatchers?
+    * Avoid adding a third kind of feed (`itunesrss`), or options
+      to the existing `rss` and `atom` feeds, unless we have to.
 * Notable tags for feeds:
     * `itunes:subtitle`
     * `itunes:author`
@@ -47,6 +51,9 @@ Episode enclosure  |(./)      |(./)       |(./)        |(./)
         * [ffprobe](http://ffmpeg.org/ffprobe.html) is reasonably fast
         * [mediainfo](http://mediainfo.sourceforge.net/) is way slower
         * Cache computed durations as pagestate
+* [Podcast Feed Best
+  Practice](https://github.com/gpodder/podcast-feed-best-practice/blob/master/podcast-feed-best-practice.md)
+  from the gPodder folks
 
 ### Fancy podcast aggregating
 
@@ -56,12 +63,6 @@ Episode enclosure  |(./)      |(./)       |(./)        |(./)
 
 ### Other ideas
 
-* Don't render template text (e.g., "Use this template to insert a
-  note into a page") in feeds.
-    * [[schmonz]] observes this in a dual-feed (one for enclosures,
-      another for browsers) scenario, but not in the typical case.
-      Remaining to be verified: that once migrated to fancypodcast,
-      this stops being a problem.
 * Optionally specify the enclosure's:
     * MIME type, in case `File::MimeInfo` guesses wrong.
     * Duration, in case `ffprobe` guesses wrong.