Enhancement request: Per channel polling frequency

[jasonkgreen]

Some feeds, like social media, are busy enough to make frequent polling desirable. Others, like blog feeds , could be polled less frequently. This might also reduce overhead since not all channels would be polled each time

[jackjamieson2]

Thanks for this suggestion.

Yarns already has a feature that accomplishes some of this in the background, though you just made me realize it's not documented or visible to users, which is not ideal

Basically, Yarns automatically updates its polling frequency on a per-feed level. Feeds that regularly have new content are polled more often, and feeds with less frequent updates are polled less frequently.

Does that accomplish more or less what you're thinking of?

I think it would be nice to actually indicate this the admin screen somewhere since it just happens invisibly in the background

[jasonkgreen]

Yes, that's exactly the kind of thing I was thinking of. I just didn't know it was happening. Thanks for your prompt reply.

…

________________________________ From: Jack Jamieson <[email protected]> Sent: Wednesday, December 4, 2019 4:14 PM To: jackjamieson2/yarns-microsub-server <[email protected]> Cc: jasonkgreen <[email protected]>; Author <[email protected]> Subject: Re: [jackjamieson2/yarns-microsub-server] Enhancement request: Per channel polling frequency (#97) Thanks for this suggestion. Yarns already has a feature that accomplishes some of this in the background, though you just made me realize it's not documented or visible to users, which is not ideal Basically, Yarns automatically updates its polling frequency on a per-feed level. Feeds that regularly have new content are polled more often, and feeds with less frequent updates are polled less frequently. Does that accomplish more or less what you're thinking of? I think it would be nice to actually indicate this the admin screen somewhere since it just happens invisibly in the background — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#97?email_source=notifications&email_token=AB66G4LJXT6O46TJFOU7UBDQXATTBA5CNFSM4JVPVQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6VXGY#issuecomment-561863579>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB66G4OM5DNODGSH4NNBYLTQXATTBANCNFSM4JVPVQSA>.

[jackjamieson2]

Great! I'll leave this issue open as a reminder to think about how to best convey this to users (through documentation, UI, or both)