mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #1988] Bookmarks disappear when added during sync run #1330
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stok17 on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1988
Describe the feature you'd like to request
I like to add bookmarks one by one, with auto sync on, I may add bookmarks when auto sync is working, which causes some bookmarks are added first but get deleted by floccus later.
But when I use manual sync, because I have 50000 bookmarks, sometimes 1000 bookmarks change can fail the merge.
I hope to have a option to sync every 5 min so I don't need to force overwrite while it won't be triggered by bookmark changes so I don't need to wait sync process to end to add another bookmark
Describe the solution you'd like
Separate Time Based and Change Based Auto Sync Feature into 2 options
Describe alternatives you've considered
Don't have another idea for now
@github-actions[bot] commented on GitHub (Jul 11, 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 💙
@marcelklehr commented on GitHub (Jul 11, 2025):
Hi @stok17
So, you want to be able to disable the change-based auto-sync, but keep the time-based auto-sync.
Which version of floccus are you currently on (please check in the floccus dropdown)? I think this should be fixed in v5.5.x
@stok17 commented on GitHub (Jul 11, 2025):
On Firefox it's 5.4.5. dk when it could be updated tho...
@marcelklehr commented on GitHub (Jul 11, 2025):
Yep, I'm in the process of rolling out v5.5.x. Let's leave this open for now until v5.5.x is released on firefox. I'd then appreciate your feedback on whether that fixes the issue of bookmarks disappearing.
@stok17 commented on GitHub (Jul 14, 2025):
I test 5.5.6 on chrome. I can see that based on my 50000 bookmarks, when I add one bookmark and trigger auto syncing, and then I add one more bookmark during the sync process, one bookmark will disappear after sync done.
Not every time, but sometimes
@marcelklehr commented on GitHub (Jul 19, 2025):
the bookmark added during the sync run disappears directly after the sync run, or on the next sync run?
@marcelklehr commented on GitHub (Jul 20, 2025):
I cannot reproduce this on chrome or firefox with v5.5.6. Are you perhaps syncing your bookmarks additionally via other means than just floccus? Like the browser-built-in bookmarks sync?
@stok17 commented on GitHub (Jul 20, 2025):
Im keeping watch on this too, so far firefox looks fine and im trying to reproduce it on chrome. Maybe you can lower prio until I find that corner case. Thanks,
@marcelklehr commented on GitHub (Aug 11, 2025):
Any news on this? :)
@stok17 commented on GitHub (Aug 14, 2025):
Some times I can still see this bug but Im not sure how to reproduce it. Seems like randomly
@marcelklehr commented on GitHub (Aug 15, 2025):
It may have to do with interrupted syncs, such that an interruption (like closing the browser during a sync) causes my fix for this issue to not work, perhaps.
I will try to test: