|
AO3 isn't going to be the same, but QQ, SV and SB all share code in FFF.
If QQ is behaving differently, it's going to be because the site is different in some way, or you use QQ differently.
I don't think I've ever paid any attention to how FFF affects 'reading location' on xenforo sites. As a general rule, I've only cared about 'read' status on sites that won't notify you for new updates unless you're 'caught up', eg TtH. And that's to ensure it's been marked read, which seems to be the opposite of what you want.
I assume it's only affected when downloading while logged in. In fact, I suspect the difference is that you always have FFF log in to QQ. So the site assumes that anything FFF has seen, you have seen.
By default, the adapter uses xenforo's reader mode to get the most 'chapter' posts per network request. So I don't have an explanation why QQ would mark posts past the thread marked ones 'read'--other than maybe the site marks all posts that would be on the same page 'read'.
OR "jump to new" on QQ doesn't mean what you think it means. IE, new to you. Because I just went and looked at the first two pages of thread I'd never looked at before (in browser), the clicked 'jump to new' expecting to get page 3 and got page 79.
That suggest pretty strongly it's actually new=='recent', not new=='I haven't see'.
|