[GH-ISSUE #233] Adjust time interval for periodic sync #225

Closed
opened 2026-02-25 22:36:31 +03:00 by kerem · 6 comments
Owner

Originally created by @steffenl82 on GitHub (Feb 16, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/233

Hi.
The description claims that floccus "will also sync periodically to pull the latest changes from the server". Is there a way to adjust the time interval for that periodic sync?

Originally created by @steffenl82 on GitHub (Feb 16, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/233 Hi. The description claims that floccus "will also sync periodically to pull the latest changes from the server". Is there a way to adjust the time interval for that periodic sync?
kerem closed this issue 2026-02-25 22:36:31 +03:00
Author
Owner

@marcelklehr commented on GitHub (Feb 18, 2019):

Hey,
Not currently, no. The hardcoded value is currently 15minutes. What do you hope to achieve by changing it?

<!-- gh-comment-id:464758535 --> @marcelklehr commented on GitHub (Feb 18, 2019): Hey, Not currently, no. The hardcoded value is currently 15minutes. What do you hope to achieve by changing it?
Author
Owner

@steffenl82 commented on GitHub (Feb 18, 2019):

15min is indeed a sensible value. However, I have observed several cases when the last sync was hours ago but no new sync was triggered (and I suspected the time interval being too long, which is why I was asking my question in the first place). So it seems that I may have a problem with my installation that the periodic sync is not correctly working. I have to do some more tests...

<!-- gh-comment-id:464909825 --> @steffenl82 commented on GitHub (Feb 18, 2019): 15min is indeed a sensible value. However, I have observed several cases when the last sync was hours ago but no new sync was triggered (and I suspected the time interval being too long, which is why I was asking my question in the first place). So it seems that I *may* have a problem with my installation that the periodic sync is not correctly working. I have to do some more tests...
Author
Owner

@bernd-wechner commented on GitHub (Feb 18, 2019):

I'd love to see such a setting. In general:

  1. It empowers me and I feel warm and fuzzy ;-)
  2. It makes it clear and in my face it's an interval based periodic check not a change triggered sync

Just my 2c worth I guess.

<!-- gh-comment-id:464920087 --> @bernd-wechner commented on GitHub (Feb 18, 2019): I'd love to see such a setting. In general: 1. It empowers me and I feel warm and fuzzy ;-) 2. It makes it clear and in my face it's an interval based periodic check not a change triggered sync Just my 2c worth I guess.
Author
Owner

@steffenl82 commented on GitHub (Feb 20, 2019):

I think I know what the "problem" is: I guess that the 15 min are counted from the start of the browser? In my tests I had to leave the browser open for at least 15 min to get an automatic sync - even if the last sync was a long time ago.

I was hoping that the time of the last sync (as can be seen when clicking in the floccus icon) was also taken into consideration, such that when you open your browser after a "long time" (i.e. >15 min), an automatic sync is immediately triggered after startup.

Would it be worthwhile to implement such a check?

<!-- gh-comment-id:465726532 --> @steffenl82 commented on GitHub (Feb 20, 2019): I think I know what the "problem" is: I guess that the 15 min are counted from the *start* of the browser? In my tests I had to leave the browser open for at least 15 min to get an automatic sync - even if the last sync was a long time ago. I was hoping that the time of the last sync (as can be seen when clicking in the floccus icon) was also taken into consideration, such that when you open your browser after a "long time" (i.e. >15 min), an automatic sync is immediately triggered after startup. Would it be worthwhile to implement such a check?
Author
Owner

@marcelklehr commented on GitHub (Feb 22, 2019):

@bernd-wechner Well 2. is not completely true, as local changes do trigger a sync, just not server-side changes... I see your point, though. I strive to only introduce config options when there's no other way, though.

when you open your browser after a "long time" (i.e. >15 min), an automatic sync is immediately triggered after startup.

That sounds like a good idea to me!

<!-- gh-comment-id:466276448 --> @marcelklehr commented on GitHub (Feb 22, 2019): @bernd-wechner Well 2. is not completely true, as local changes do trigger a sync, just not server-side changes... I see your point, though. I strive to only introduce config options when there's no other way, though. > when you open your browser after a "long time" (i.e. >15 min), an automatic sync is immediately triggered after startup. That sounds like a good idea to me!
Author
Owner

@github-actions[bot] commented on GitHub (Mar 20, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1476410902 --> @github-actions[bot] commented on GitHub (Mar 20, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#225
No description provided.