You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have the ability to store user-specified metadata on the feeds when they're persisted to disk. This would allow for things like an external downloader (for example.. :-)) to look at the Feed object and see if the user has set a custom schedule (why try to download new data 4 times a day when it's a weekly podcast that almost always comes out on mondays, or something).
Possibly also we could allow for some notes to be set that might optionally also show up in the UI, based on user configuration, or any number of other prospective use cases. You could imagine also wanting this for Episodes, if users wanted to take their own notes per episode, or subject-matter tags, etc. Even if the UI didn't really show these things, then you could write some custom scripts to find episodes based on a tag later when you wanted to dig them up.
The text was updated successfully, but these errors were encountered:
This is a good idea, there's plenty of metadata we may want to work with in the future (either user-set ones like reload period as you said, or automatic things like number of plays per episode or percent listened). This would probably be easy enough with something like a "user-data" object in each Episode/Feed in the feeds data file, although I'd be careful with backwards compatibility.
We could preserve the current Feeds file (although I'd like to get rid of it for other reasons), and just make a parallel store where we store metadata, tied back to the feeds through their URLs perhaps.
It would be nice to have the ability to store user-specified metadata on the feeds when they're persisted to disk. This would allow for things like an external downloader (for example.. :-)) to look at the Feed object and see if the user has set a custom schedule (why try to download new data 4 times a day when it's a weekly podcast that almost always comes out on mondays, or something).
Possibly also we could allow for some notes to be set that might optionally also show up in the UI, based on user configuration, or any number of other prospective use cases. You could imagine also wanting this for Episodes, if users wanted to take their own notes per episode, or subject-matter tags, etc. Even if the UI didn't really show these things, then you could write some custom scripts to find episodes based on a tag later when you wanted to dig them up.
The text was updated successfully, but these errors were encountered: