[Kavita] Idea / Feature Submission: Reading List Details Page Improvements #4530
Replies: 5 comments 2 replies
-
This is already possible with the continue button. We already have a reading list mode for the readers to follow the reading list order rather than series order.
Yes, I'll add this.
Hide meaning make them invisible in the list? I can't grasp where the value behind this is. |
Beta Was this translation helpful? Give feedback.
-
|
For hiding issues:
The idea being that if a list is promoted, the other users reading it can't
"remove" the issues they've already read (like the list creator) but may
want to "hide" the issues they've read to achieve the same effect and pare
it down to just stuff they haven't read yet. Similarly, even the list
creator may want to hide these for the same reason without permanently
removing the issues (to not permanently alter it for other users).
…On Fri, Apr 3, 2026 at 3:20 PM Joe Milazzo ***@***.***> wrote:
Some way to "jump to"/highlight the "next issue" up based on where they
last read the list?
This is already possible with the continue button. We already have a
reading list mode for the readers to follow the reading list order rather
than series order.
For the "remove read issues" it would be a bit safer to have a
confirmation dialogue pop up for that. It would be good to have it explain
"this removes the issues from the list permanently/can't be undone" etc
Yes, I'll add this.
Adding an option for any user to "hide read issues" based off their own
reading states to promoted lists. This would be akin to the "remove read
issues" but not actually delete them and also be available to any user, not
just the list owner
Hide meaning make them invisible in the list? I can't grasp where the
value behind this is.
—
Reply to this email directly, view it on GitHub
<#4530?email_source=notifications&email_token=A5DSAFNXXDVPWXSMBU3Y2I34UAFHFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRUGQYTONBTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16441743>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5DSAFMYNYEZYROZ5X7CN734UAFHFAVCNFSM6AAAAACWR5D4ZSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBUGE3TIMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
and to be clear this would be a "Hide Read Issues" feature for both the
creator and the other users, in addition to the "Remove Read Issues" for
just the creator
…On Fri, Apr 3, 2026 at 3:28 PM Danielle Mendus ***@***.***> wrote:
For hiding issues:
The idea being that if a list is promoted, the other users reading it
can't "remove" the issues they've already read (like the list creator) but
may want to "hide" the issues they've read to achieve the same effect and
pare it down to just stuff they haven't read yet. Similarly, even the list
creator may want to hide these for the same reason without permanently
removing the issues (to not permanently alter it for other users).
On Fri, Apr 3, 2026 at 3:20 PM Joe Milazzo ***@***.***>
wrote:
> Some way to "jump to"/highlight the "next issue" up based on where they
> last read the list?
>
> This is already possible with the continue button. We already have a
> reading list mode for the readers to follow the reading list order rather
> than series order.
>
> For the "remove read issues" it would be a bit safer to have a
> confirmation dialogue pop up for that. It would be good to have it explain
> "this removes the issues from the list permanently/can't be undone" etc
>
> Yes, I'll add this.
>
> Adding an option for any user to "hide read issues" based off their own
> reading states to promoted lists. This would be akin to the "remove read
> issues" but not actually delete them and also be available to any user, not
> just the list owner
>
> Hide meaning make them invisible in the list? I can't grasp where the
> value behind this is.
>
> —
> Reply to this email directly, view it on GitHub
> <#4530?email_source=notifications&email_token=A5DSAFNXXDVPWXSMBU3Y2I34UAFHFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRUGQYTONBTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16441743>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A5DSAFMYNYEZYROZ5X7CN734UAFHFAVCNFSM6AAAAACWR5D4ZSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBUGE3TIMY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
say I get a list from the repo but I've read some but not all of the
issues. I don't want to read all of it, I want to hide the issues I've read
and either then a) export that as a list file just for me to reimport or b)
start reading from those non-hidden issues as a pseudo-list
Say we have items A-F in positions 1-6:
1 A
2 B etc
If I've read A, B and D, I want to see just C, E, F and then click on C,
start reading, and when it gets to the end, jump to E (not D)
…On Fri, Apr 3, 2026 at 3:37 PM Joe Milazzo ***@***.***> wrote:
But what functionality are you trying to achieve with hiding items? If
you've read items, it might not be in the order of the list. We don't track
reading against lists, just individual reading of the underlying
chapter/issue.
—
Reply to this email directly, view it on GitHub
<#4530?email_source=notifications&email_token=A5DSAFPK3AKMBNQHYQDVQDL4UAHIDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRUGQYTSMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16441929>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5DSAFIB7S26BQ55ULQGX3D4UAHIDAVCNFSM6AAAAACWR5D4ZSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBUGE4TEOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
put aside the exporting (which if you're not into making this a reading
list manager at all, I don't know why that exists). the macro problem here
is: for very large lists, many of which you provide or at least enable
passing on via the repository, it's hard to figure out what you've read and
what you haven't read and/or read in a way that doesn't make you plow
through a lot of issues already marked as read. whatever you think is a
reasonable, in-scope way to help with that would be greatly appreciated
…On Fri, Apr 3, 2026 at 3:51 PM Joe Milazzo ***@***.***> wrote:
This seems outside the scope of what Kavita is meant to be. It is not an
organizer for Reading Lists. If you hid items, you wouldn't be able to
export without those items. What you're also asking for is not a "hide
read", it's a "Ignore already read".
This is something I'm not interested in bringing into Kavita. The scope is
too large.
—
Reply to this email directly, view it on GitHub
<#4530?email_source=notifications&email_token=A5DSAFIVFE2QRASHM7TIF3L4UAI5JA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRUGQZDANRXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16442067>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5DSAFIAAWMJZLLRUT2LKCT4UAI5JAVCNFSM6AAAAACWR5D4ZSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBUGIYDMNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Idea Description
For the reading list detail page:
Adding an option for any user to "hide read issues" based off their own reading states to promoted lists. This would be akin to the "remove read issues" but not actually delete them and also be available to any user, not just the list owner
For the "remove read issues" it would be a bit safer to have a confirmation dialogue pop up for that. It would be good to have it explain "this removes the issues from the list permanently/can't be undone" etc
Some way to "jump to"/highlight the "next issue" up based on where they last read the list? i suppose this would require maintaining a "last read" for each list which you may or may not be doing
Idea Category
Web UI
Duration of Using Kavita
No response
Before submitting
Beta Was this translation helpful? Give feedback.
All reactions