![]() This approach, however, leads to not very pretty APIs since everywhere where episodes or podcasts are referenced, two separate identification fields have to be available, URL and guid. Our approach is to make GUID in both cases optional and use URLs for identification if they are missing, but use GUIDs for identification if possible. Subscription GUID is rarely used, but may be used more in the future, if I understand it correctly. identifies subscriptions by feed url and episodes by media url, which lead to many duplicates in the past since both of them can change.Įpisode GUID is quite common, but not each podcast supports it and sometimes (Tagesschau) even guids change. ![]() Since no internal IDs can be used, publicly available information about these podcasts have to be used. It's about how podcasts and episodes are identified across different podcast clients. I think this topic deserves its own thread. And since the most common settings could be published, this could lead to nice interoperability between podcast clients. ![]() ![]() Nearly every config could be synced this way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |