My intent is eventually to use the taste profile API to provide the feedback in not-realtime. (I have no interest in writing a GUI at this point.) I realize there is a limitation with dynamic stations disappearing after a day of idleness, so it seems that the taste profile API (one per station) should work around that. Is that correct?
The lifecycle would be create dynamic station with seed, produce a playlist and a taste profile, save the profile id (and probably a list of song name, artist, track id) somewhere, go back and update the taste profile after some interval of listening, then create a new dynamic station seeded with only the taste profile, or possibly the original seed(s) plus the taste profile, and generate another big playlist, repeat.
Will this work? If so, should the new dynamic station be seeded with the taste profile only, or the original seeds plus the taste profile?
Thanks for the prompt responses by the way.