mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #155] Add way to list duplicate bookmarks #147
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#147
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 @bernd-wechner on GitHub (Aug 27, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/155
I have hundreds of bookmarks and had some inadvertent dupes. Some I actually want that way, stored in two different folders, most I did not. So I used a SQL query on my NextCloud server to seek and destroy these dupes. It looks like this:
Not everyone is going to have the skills or time to do that though, and it might be easy enough to do the equivalent in the browser add-on directly, from a link on the toolbar drop down and/or the config page, just throw up a list of links that are found more than once with their titles and folders and that's enough to hunt them down and fix them.
If it was fancy, it would have a check box beside each dupe to flag it as desired and hide it from subsequent searches. But bells and whistles and all that, enough just to provide a list like this query provides (which on the the server end not the client end).
@marcelklehr commented on GitHub (Aug 30, 2018):
Mmh. while this seems to be a useful feature, I'm not sure it is essential to syncing bookmarks. A quick search yielded the following extension which seems to provide the functionality you're looking for: https://addons.mozilla.org/en-US/firefox/addon/bookmark-deduplicator/
@jd666 commented on GitHub (Aug 30, 2018):
I rely on an extension that saves the current session as a bookmark tree. So a de-duplication would be detrimental, I think having it as a separate addon is the better idea.
@marcelklehr commented on GitHub (Aug 30, 2018):
@jd666 Ah, I understand. The question was whether floccus could simply list duplicates, which wouldn't delete them directly, of course. But in the interest of doing one thing and doing it well, I think letting other extensions handle this should be fine. What do you think @bernd-wechner ?
@bernd-wechner commented on GitHub (Aug 31, 2018):
I'd be fine with that. No drama at all. Part of me thinks it's nice to keep stuff well integrated and I do see dupe finding as part of the scope of syncing if only at the level of disaster recovery and debugging (if dupes happen to be created en masse). Bug totally agree non essential and in a world where the sync works flawlessly not any more important than having debug logs easily accessible is.
Alas the recommended add on is listed as "This add-on is not compatible with your version of Firefox." and seems unmaintained, but hey it's not a person issue as I have the SQL solution above anyhow (which is one reason I LOVE floccus/Nexctloud as a solution as it grants me access to the back end for diagnostics , fixes, backup and more).
@bernd-wechner commented on GitHub (Aug 31, 2018):
Here's another, also unmaintained and not working:
https://addons.mozilla.org/en-US/firefox/addon/bookmark-duplicate-cleaner/
@bernd-wechner commented on GitHub (Aug 31, 2018):
And here's one that is current and seems maintained:
https://addons.mozilla.org/en-US/firefox/addon/bookmark-dupes
@marcelklehr commented on GitHub (Sep 23, 2018):
I'll add a link to that addon in the readme.
@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.