The link acceptor endpoint remembers the last used podcast and episode and topic (per user)
We currently dont have topics. Questions: should this information be stored in the database? This is a session info . But a re-sign in should not reset this I guess.
from my point of view the last uses podcast (show) and episode should be remembered for each user. currently i'm unsure about topics, but it should be stored in the database to ensure that the "last used" info is kept in sync across user-devices.
Is it really that easy? The last episode might be published already then it would be natural to take the next one, or, what do you think?
maybe this behavior depends on the user preferences. one could argue that you want to switch to ne next/new episode once the current episode gets published. another user may prefer "staying" in the published episode to add shownotes and additional links later on. maybe the user is just a guest in this episode but not in the upcoming one ...