mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #498] Sync delay on startup #363
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#363
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 @dsiminiuk on GitHub (Apr 21, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/498
Is your feature request related to a problem? Please describe.
When you open the browser, the floccus extension immediately starts syncing. In the event that you already are aware that there is an issue with the xbel file or corrupted bookmarks on the server, this action propagates the corrupted data to the local browser you just opened. You have to cancel sync manually and by that time some bookmarks may have been deleted/changed (too late).
Describe the solution you'd like
Add a delay of n seconds to the initial sync when the browser opens and the extension loads, configurable would be nice but not mandatory, to give the user time to disable the extension and change the settings to overwrite the server (this use case) to restore the bookmarks from the local copy and fix the server copy.
Perhaps two new buttons to appear while it is not syncing;
one to sync now and overwrite local (pull)
another to sync now and overwrite remote (push).
It would save having to change settings back and forth each time there is a sync issue.
@github-actions[bot] commented on GitHub (Mar 21, 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.