[GH-ISSUE #2049] Syncing Tabs syncs on every change #1369

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

Originally created by @sklknn on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2049

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

10-30

Are you using other means to sync bookmarks in parallel to floccus?

Yes, I also sync via Mozilla account

Sync method

Git

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Zen Browser 1.14.11b (Firefox 141.0.3)

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

in my configuration autoupdate interval is set to 30 min, but after update i can see git commit in my sync repo every minute. This behavior results in 567 commits just for today. My average before update was 40-70 commits per day before. This is 10x more than expected

Expected Behavior

commit every commit interval, not every minute

To Reproduce

to be honest - i don't know. this may be firefox/zen workspaces/pinned tabs problem. i use floccus primarily for tab sync
redacted log -

floccus-5.7.0-2025-09-02-redacted.log

Debug log provided

  • I have provided a debug log file
Originally created by @sklknn on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2049 ### Which version of floccus are you using? 5.7.0 ### How many bookmarks do you have, roughly? 10-30 ### Are you using other means to sync bookmarks in parallel to floccus? Yes, I also sync via Mozilla account ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Zen Browser 1.14.11b (Firefox 141.0.3) ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug in my configuration autoupdate interval is set to 30 min, but after update i can see git commit in my sync repo every minute. This behavior results in 567 commits just for today. My average before update was 40-70 commits per day before. This is 10x more than expected ### Expected Behavior commit every commit interval, not every minute ### To Reproduce to be honest - i don't know. this may be firefox/zen workspaces/pinned tabs problem. i use floccus primarily for tab sync redacted log - [floccus-5.7.0-2025-09-02-redacted.log](https://github.com/user-attachments/files/22095145/floccus-5.7.0-2025-09-02-redacted.log) ### Debug log provided - [x] I have provided a debug log file
kerem 2026-02-25 22:39:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Sep 2, 2025):

Hello! 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙

<!-- gh-comment-id:3245376701 --> @github-actions[bot] commented on GitHub (Sep 2, 2025): Hello! :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! :blue_heart:
Author
Owner

@sklknn commented on GitHub (Sep 2, 2025):

there is some screenshots of commit statistics in my gitlab sync repo
Image

Image
<!-- gh-comment-id:3245421286 --> @sklknn commented on GitHub (Sep 2, 2025): there is some screenshots of commit statistics in my gitlab sync repo <img width="675" height="326" alt="Image" src="https://github.com/user-attachments/assets/4e76a536-30a4-46e6-8493-6a480b6035e7" /> <img width="787" height="328" alt="Image" src="https://github.com/user-attachments/assets/7e8f9f90-6288-42ab-a564-34e8eeddb6e5" />
Author
Owner

@marcelklehr commented on GitHub (Sep 2, 2025):

Hi @sklknn
Thank you for taking the time to give feedback! I appreciate it :)
This behavior is sort of expected as floccus (also for bookmarks) always syncs immediately when it detects local changes. Previously, this was not done for tabs, but I think it's more intuitive if tabs are synced immediately. The sync interval is there to catch wind of updates from other browsers.
However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen". Would this solve the issue for you?

<!-- gh-comment-id:3245432474 --> @marcelklehr commented on GitHub (Sep 2, 2025): Hi @sklknn Thank you for taking the time to give feedback! I appreciate it :) This behavior is sort of expected as floccus (also for bookmarks) always syncs immediately when it detects local changes. Previously, this was not done for tabs, but I think it's more intuitive if tabs are synced immediately. The sync interval is there to catch wind of updates from other browsers. However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen". Would this solve the issue for you?
Author
Owner

@sklknn commented on GitHub (Sep 2, 2025):

Thanks for quick reply!
I think sudden change in behavior confused me there.

However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen". Would this solve the issue for you?

This sounds awesome! Is there any way to disable on change sync for now, before this will happen?

<!-- gh-comment-id:3245700212 --> @sklknn commented on GitHub (Sep 2, 2025): Thanks for quick reply! I think sudden change in behavior confused me there. > However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen". Would this solve the issue for you? This sounds awesome! Is there any way to disable on change sync for now, before this will happen?
Author
Owner

@marcelklehr commented on GitHub (Sep 2, 2025):

The only way to disable sync on local changes, is to disable auto sync, which also disables interval-based sync, right now. But you could still sync manually with the sync button then.

<!-- gh-comment-id:3245831712 --> @marcelklehr commented on GitHub (Sep 2, 2025): The only way to disable sync on local changes, is to disable auto sync, which also disables interval-based sync, right now. But you could still sync manually with the sync button then.
Author
Owner

@marcelklehr commented on GitHub (Nov 16, 2025):

However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen".

This is live now in v5.8.0, happy syncing :)

<!-- gh-comment-id:3538495916 --> @marcelklehr commented on GitHub (Nov 16, 2025): > However, there is a proposal to decompose the Auto-sync setting into "Enable interval sync" and "Enable sync when local changes happen". This is live now in v5.8.0, happy syncing :)
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#1369
No description provided.