starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #169] Reset cache: Explicitly select which side to keep or whether to merge #162

New issue

Closed

opened 2026-02-25 22:36:20 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 22:36:20 +03:00

Owner

Originally created by @jlbprof on GitHub (Sep 7, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/169

I do not believe there is a way to do this now, so correct me if I am wrong.

I am looking at the recent option you added "reset cache". I am not totally sure what that is intended to do so let me explain one of the features I liked from Xmarks.

You could select normal syncing, or you could say keep what is on the server and throw away what is on the browser, or you could say keep what is on the browser and throwaway what is on the server.

I believe "reset cache" is probably equivalent to "keep what is on the browser, and throw away what is on the server".

So am I correct in what "reset cache" does?

What do you think about the other options I listed?

Right now if I want to throw away what is on the browser, I have to first delete my local bookmarks and then sync. Or if I want what is on the browser, I would delete my bookmarks.xbel file on the server and sync.

Thanx

Julian

Originally created by @jlbprof on GitHub (Sep 7, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/169 I do not believe there is a way to do this now, so correct me if I am wrong. I am looking at the recent option you added "reset cache". I am not totally sure what that is intended to do so let me explain one of the features I liked from Xmarks. You could select normal syncing, or you could say keep what is on the server and throw away what is on the browser, or you could say keep what is on the browser and throwaway what is on the server. I believe "reset cache" is probably equivalent to "keep what is on the browser, and throw away what is on the server". So am I correct in what "reset cache" does? What do you think about the other options I listed? Right now if I want to throw away what is on the browser, I have to first delete my local bookmarks and then sync. Or if I want what is on the browser, I would delete my bookmarks.xbel file on the server and sync. Thanx Julian

kerem

2026-02-25 22:36:20 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@marcelklehr commented on GitHub (Sep 7, 2018):

I believe "reset cache" is probably equivalent to "keep what is on the browser, and throw away what is on the server".

Not quite. Reset cache causes floccu to sync from scratch the next time, merging both server and browser. If youonly want to keep the local bookmarks, delete the ones on the server and reset the cache (so that the already linked local bookmarks won't get removed, too, on the next sync). And vice versa if you only want to keep the server bookmarks.

The functionality you lay out would be a nice to have, IMO, as you can emulate it with the features already available, but it shouldn't be too hard to clear the browser/server before syncing if the user selects that I'm thinking, it could be a dropdown after the reset cache option.

Do you want to give it a try? :)

@marcelklehr commented on GitHub (Sep 7, 2018): > I believe "reset cache" is probably equivalent to "keep what is on the browser, and throw away what is on the server". Not quite. Reset cache causes floccu to sync from scratch the next time, merging both server and browser. If you*only* want to keep the local bookmarks, delete the ones on the server and reset the cache (so that the already linked local bookmarks won't get removed, too, on the next sync). And vice versa if you *only* want to keep the server bookmarks. The functionality you lay out would be a nice to have, IMO, as you can emulate it with the features already available, but it shouldn't be too hard to clear the browser/server before syncing if the user selects that I'm thinking, it could be a dropdown after the reset cache option. Do you want to give it a try? :)

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@jlbprof commented on GitHub (Sep 7, 2018):

I may look into it, thanx Marcel

On Fri, Sep 7, 2018 at 9:05 AM Marcel Klehr notifications@github.com
wrote:

I believe "reset cache" is probably equivalent to "keep what is on the
browser, and throw away what is on the server".

Not quite. Reset cache causes floccu to sync from scratch the next time,
merging both server and browser. If youonly want to keep the local
bookmarks, delete the ones on the server and reset the cache (so that the
already linked local bookmarks won't get removed, too, on the next sync).
And vice versa if you only want to keep the server bookmarks.

The functionality you lay out would be a nice to have, IMO, as you can
emulate it with the features already available, but it shouldn't be too
hard to clear the browser/server before syncing if the user selects that
I'm thinking, it could be a dropdown after the reset cache option.

Do you want to give it a try? :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/169#issuecomment-419450070,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJS39Z7BnWcCGzpCf3zp6TQ1YDZ6wFgTks5uYn0jgaJpZM4WetXc
.

@jlbprof commented on GitHub (Sep 7, 2018): I may look into it, thanx Marcel On Fri, Sep 7, 2018 at 9:05 AM Marcel Klehr <notifications@github.com> wrote: > I believe "reset cache" is probably equivalent to "keep what is on the > browser, and throw away what is on the server". > > Not quite. Reset cache causes floccu to sync from scratch the next time, > merging both server and browser. If you*only* want to keep the local > bookmarks, delete the ones on the server and reset the cache (so that the > already linked local bookmarks won't get removed, too, on the next sync). > And vice versa if you *only* want to keep the server bookmarks. > > The functionality you lay out would be a nice to have, IMO, as you can > emulate it with the features already available, but it shouldn't be too > hard to clear the browser/server before syncing if the user selects that > I'm thinking, it could be a dropdown after the reset cache option. > > Do you want to give it a try? :) > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/169#issuecomment-419450070>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39Z7BnWcCGzpCf3zp6TQ1YDZ6wFgTks5uYn0jgaJpZM4WetXc> > . >

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@raxetul commented on GitHub (Feb 27, 2019):

Also better to rename "Reset" option as "Merge" and it should be acivated by default to keep user on the safe side. "Reset" makes people think it will reset all bookmarks and resync and with the "Tick this box to ...... local bookmarks together" explanation it is confusing.

@raxetul commented on GitHub (Feb 27, 2019): Also better to rename "Reset" option as "Merge" and it should be acivated by default to keep user on the safe side. "Reset" makes people think it will reset all bookmarks and resync and with the "Tick this box to ...... local bookmarks together" explanation it is confusing.

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

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

@raxetul Thanks for the input! Renaming the option definitely makes sense. I think activating the merge/reset option by default is not a good idea, because deletions will not be propagated if this is the case.

@marcelklehr commented on GitHub (Feb 28, 2019): @raxetul Thanks for the input! Renaming the option definitely makes sense. I think activating the merge/reset option by default is not a good idea, because deletions will not be propagated if this is the case.

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 20, 2019):

Closing in favor of #244, which is essentially the same, I think.

@marcelklehr commented on GitHub (Jul 20, 2019): Closing in favor of #244, which is essentially the same, I think.

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 2, 2019):

Feel free to try our this feature in the latest beta

@marcelklehr commented on GitHub (Aug 2, 2019): Feel free to try our this feature in the [latest beta](https://github.com/marcelklehr/floccus/issues/338)

kerem commented

2026-02-25 22:36:20 +03:00

Author

Owner

@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.

@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.

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#162

No description provided.

Rows
Columns