mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1066] Improve wording around sync strategies #706
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#706
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 @marcelklehr on GitHub (Mar 8, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1066
Describe the feature you'd like to request
Some of the terminology can be confusing for novice computer users. Terms like "Push" and "Pull" can come across too technical.
Describe the solution you'd like
I think it would be much better to replace as follows:
A) Instead of "Push Sync" replace with "Upload - Overwrite Nextcloud data"
B) Instead of "Pull Sync" replace with "Download - Overwrite Local data"
C) Instead of "Normal Sync" replace with "Merge - Merge Local and Nextcloud data"
D) Instead of "Push Sync Once" replace with "Upload Once" (overwrite Nextcloud data with local data)
E) Instead of "Pull Sync Once" replace with "Download Once" (overwrite Local data with Nexcloud data)
Describe alternatives you've considered
N/A
@pinpontitit commented on GitHub (Mar 15, 2022):
I agree. I never understood those push and pull terms before your post lol
@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.