[Reading Lists] OPDS Reading Lists: Virtual TPBs

[falo2k]

Idea Description

This addresses a similar goal to having a OPDS unread-only / continue from issue view. What if reading lists could be presented to the OPDS feed as one single TPB with a huge page count, and then a reader never needs to return to the list to move onto the next issue, they just turn a page. Reduces navigation, list reloading, etc.

I appreciate there will be some challenges to be solved here with tracking read status.

• Is it derived from the read status of component issues? If so, what happens in scenarios where the read status change of component issues does not occur at exactly one point (e.g. if you had constituent issues of a list that had a status of [read, read, unread, 50%, unread, read, unread] where is the line?
• Would these virtual TPBs need to track their own read status, and then should that status reflect back on top of the underlying issue read status. For the latter, I'd argue yes, or that it should only apply a read status, not an unread status (i.e. in the scenario above, if I started reading the TPB from scratch, it would not set all of the subsequent issues to unread, but would start to make changes as I reach the pages of the third issue).
• What happens if the constituent members of the list change? Issues are added or removed, whether automatically or through end user intervention.

Idea Category

Feature Enhancement

Duration of Using Kavita

No response

Before submitting

• I've already searched for existing ideas before posting.