Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The link acceptor endpoint remembers the last used podcast and episode and topic (per user) #507

Open
sorax opened this issue Dec 12, 2023 · 3 comments
Assignees

Comments

@sorax
Copy link
Collaborator

sorax commented Dec 12, 2023

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.

@sorax sorax converted this from a draft issue Dec 12, 2023
@sorax
Copy link
Collaborator Author

sorax commented Dec 12, 2023

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.

@electronicbites
Copy link
Collaborator

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?

@sorax
Copy link
Collaborator Author

sorax commented Dec 22, 2023

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 ...

@electronicbites electronicbites moved this from Todo to In Progress in Radiator: Collaborator / Composer Jan 9, 2024
@electronicbites electronicbites moved this from In Progress to Todo in Radiator: Collaborator / Composer May 28, 2024
@electronicbites electronicbites moved this from Todo to In Progress in Radiator: Collaborator / Composer Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants