"New" status clear logic does not match lanraragi

[nspitko]

In the Lanraragi web UI, opening an archive removes the "new" tag

in LRReader, it only appears to get removed when viewing the last page

LRReader's behavior requires you to read through the entire book (including credits pages and possible variant pages/no text versions which may be included) to clear the flag, which makes it kind of bad for the use case of "Show me stuff I haven't looked at".

If LRReader wants to have a better stance than the web UI that's fine, but I think comic rack's model is probably better:

• If you complete the archive, it's marked as read
• If you read more than 25% of the archive, it's marked as read
• If you've read at least 10 pages, it's marked as read

These three checks catch all of the edge cases, like one page archives, small books, long books, etc. and cover the general intent of "I looked at this intentionally" without the overly aggressive behavior of marking them from a misclick.

Best case would be for this to be configurable between the current behavior, the web UI behavior, and the "smart" behavior.

[Guerra24]

Hello!

Yup, this seems like a better way of handling it. The current logic somewhat matches Ichaival which is the android client but letting the user pick whatever they want is better, specially now that I have options to give to the user 👀

[Guerra24]

So... I have one question.

The % based conditions are absolute to the page count i.e. read to the 25% point of pages (page 25 or more of 100) or relative to the currently open page i.e. have moved at least 25% of the pages forward (opened at page 5, count 25 pages ahead (30)), is it the former or the latter?

[nspitko]

I think it's just absolute page number, but I've not looked at their code. I'm not sure the exact algorithm matters much though.

To be clear on the actual user facing annoyance:

• If I read a book which contains a textless version at the end, I need to advance through this to mark the book as read.
• If I read a very long book which I decided I'm not very interested in right now, I need to page through the rest of it to get it off the new list

the above proposal is trying to resolve this while avoiding overly aggressive marking for a book you saw the cover or first few pages of and decided to come back to later, or opened by mistake. I don't have particularly strong feelings on the exact algorithm as long as it covers these cases generally. The main goal is just to deal with edge cases like very long/short books, and books with many versions, as no single metric can cover every case I suspect.

The other useful function here would just be the ability to mark/unmark the new status from the archives page and archive details page, as sometimes you maybe stopped halfway through and legitimately want to come back. These exceptions always exist, so being able to have the final say is always good. (for example, maybe I'm reading a tank and didnt' get to the last few chapters, I want this to stay on New, so I'll re-mark it as unread; but this is the exception.

And perhaps the final annoyance: when I DO have to skip through a book for any reason (be it to just complete it, or maybe there's just a chapter I'm not interested int), I can't hold down the arrow keys to move fast, I either have to open the thumbnail view or press the key many times.

[Guerra24]

The feature is implemented, I just wanted to confirm that.

ability to mark/unmark

The api only lets you unmark stuff.

A similar feature is the bookmarks stuff, which asks you if you want to bookmark it with the current progress.

skip through a book for any reason

If you have the thumbnail map enabled, you can hover over the bottom edge and a list of thumbnails will appear so you can scroll and skip without closing the reader, but that might not be ideal so ⬇️

I can't hold down the arrow keys

Not handling pressed keys was done for a reason, but I don't remember why... I will test adding back that.

[Guerra24]

I can't hold down the arrow keys

Not handling pressed keys was done for a reason, but I don't remember why... I will test adding back that.

Tested it and restored the feature... I have no idea why I removed it in the first place. Probably something whack going on with images back then.