Next Update Time Error


No matter what I set the update interval to for a feed, when I let it update, the next update gets scheduled much later than it should be. The most common 'next update' date that pops up is in 2017. I'm not at all sure why this is happening and haven't been able to remedy it. I wanted to switch to the new beta now that most of things are working, but having my feeds not update prevents such.

I hope I'm not simply missing something obvious. Screenshots of the problem can be found Here and Here

-Jeff

This should be fixed now...

...and appear in next release of Feedreader. Till this time you could use intelliupdate (it should work better than 2017 kind of updatetime;)).

Greetings
Toomas

Good to hear

Good to hear that it will be fixed. I am curious as to what the cause was, though.

May I ask, though, how the IntelliUpdate works? I'm curious as to how it decides when to update the feed.

Does it use TTL? If so, then what if the feed doesn't have TTL Specified? If not, then what does it use?

Cause....

Hi!

Unfortunately there is no interesting answer to this "cause" question ;). We are just humans and had one programming mistake in code. One variable was accidentally rewritten.

IntelliUpdate - It does not use any TTL fields. It uses .... well... Intelligence ;). Anyway - it checks for specific number of headlines in current feed and their dates and then computes new update time according to this median and current time... It's not that basic and easy as it sounds. We reworked algorithm multiple times to get the quality of results what we wanted.

I see

I see - thanks for the answer :) It's nice to have a developer that actually talks back to the consumer. I'll eagerly await the next beta and continue to use this program. If you ever cease to develop it, I may just go insane ;)