Page 1 of 2

Auto mark read delay

Posted: 24 May 2016, 12:12
by Dees7
I have 2 instance tt-rss. The old one (v1.12) and the new (v16.1 (94d425f)). Both of them run on the same mssql (different database) and the same web server. The old instances marks articles as read immidiatly, but the new one does delay ~2-3 sec.
I compared settings and saw nothing.
What should I do to made the new to mark immidiatly (as the old)?

Re: Auto mark read delay

Posted: 24 May 2016, 13:23
by fox
>What should I do to made the new to mark immidiatly (as the old)?

analyze the differences between the code and figure it out

good luck, have fun

Re: Auto mark read delay

Posted: 24 May 2016, 13:41
by Dees7
Is marking with delay normal for v16.1?

Re: Auto mark read delay

Posted: 24 May 2016, 14:05
by fox
i'm not seeing any delays except for when you auto mark as read while scrolling, which is done intentionally (articles are collected and sent in batches)

there's a bunch of ways to mark articles as read in tt-rss so unless you decide to be more specific i'm going to assume its a pebkac situation of some kind

Re: Auto mark read delay

Posted: 24 May 2016, 15:00
by Dees7
There is the check in preferences:
Automatically mark articles as read [x]

I'm use hotkey Ctrl+Down to jump a next article. After I press CtrlDown the next is selected, waits 2-3sec and marked as read.
The trouble is when I scroll too fast some articles stay unread

video

Re: Auto mark read delay

Posted: 24 May 2016, 15:22
by fox
like i said, you don't need to wait, everything you scroll past is going to get marked eventually

if that is not acceptable to you, use older version or switch to something else, this is not going to change

>The trouble is when I scroll too fast some articles stay unread

if you scroll so fast that you literally break your web browsers DOM handling maybe you should take a step back and figure out why you are subscribed to tons of shit you never actually read

Re: Auto mark read delay

Posted: 24 May 2016, 15:25
by Dees7
Thanks )

Re: Auto mark read delay

Posted: 24 May 2016, 21:52
by disconn3ct
fox wrote:like i said, you don't need to wait, everything you scroll past is going to get marked eventually


My frustration with the delay is from the other side - if I want to mark something unread (for example, something I opened by accident) I have to wait several seconds for it to cycle to "read" or it will just mark itself read anyway. (This even happens when the initial state is 'read' and I open it, push 'u' and try to move on.. after a few seconds, it will go back to 'read'.)

Re: Auto mark read delay

Posted: 24 May 2016, 22:46
by fox
i think we already went through the whole marking unread thing a year ago :p

Re: Auto mark read delay

Posted: 24 May 2016, 23:15
by disconn3ct
fox wrote:i think we already went through the whole marking unread thing a year ago :p


Indeed. I tried starring, etc, and it just meant I never went back. Unread is like leaving it out on my desk - I may not pick it up as soon as I sit down, but it isn't going to end up in a drawer with old grocery receipts and a random shoe. :D

Re: Auto mark read delay

Posted: 24 May 2016, 23:53
by fox
i understand the frustration i guess but there are i think pretty good reasons for batching instead of spamming the server in onscroll or w/e so this is definitely going to stay as it is now

Re: Auto mark read delay

Posted: 25 May 2016, 00:51
by disconn3ct
fox wrote:i understand the frustration i guess but there are i think pretty good reasons for batching instead of spamming the server in onscroll or w/e so this is definitely going to stay as it is now


What about those of us not using onscroll marking? There couldn't possibly be anything wrong with bunches of nearly-identical use-case-specific code paths :)

Re: Auto mark read delay

Posted: 25 May 2016, 07:46
by fox
if you're not using auto mark as read there shouldn't be any delays?

Re: Auto mark read delay

Posted: 25 May 2016, 17:48
by disconn3ct
Just want to make sure I'm seeing expected behavior.

I've got:
Automatically mark articles as read: Off
Automatically expand articles in combined mode: Off
Show content preview in headlines list: On

As I understand it, that prevents the "huge list of expanded articles, automatically marked read as they scroll off the top" mode. Or am I mixed up?

Opening a feed, I get a list of unread headlines. When I expand an article (click or keyboard) there is a delay and then it is marked as read. Often the delay is short (1-2 seconds) but occasionally it is 5s or more.

Re: Auto mark read delay

Posted: 25 May 2016, 18:37
by fox
there shouldn't be any delay if you click on an article, it should mark as read immediately

unless you mean counters which are not updated in real time (which is deliberate)