starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #2116] Failsafe report is not clear #1420

New issue

Closed

opened 2026-02-25 22:39:58 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:39:58 +03:00

Owner

Originally created by @bernd-wechner on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2116

Which version of floccus are you using?

5.8.0

How many bookmarks do you have, roughly?

1000

Are you using other means to sync bookmarks in parallel to floccus?

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Edge

Which version of Nextcloud Bookmarks are you using? (if relevant)

15.2.1

Which version of Nextcloud? (if relevant)

31.0.9

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

I see this message:

E029: Failsafe: The current sync run would delete 100% of your links. Refusing to execute. Disable this failsafe in the account settings if you want to proceed anyway. | Last synchronized: 1 month ago

On the plus side, thank you enormously! Such fail safes are invaluable. No-one wants significant damage to their collection because of a mistaken configuration or software issue.

That said, what wasn't clear to me on this message is:

"would delete 100% of your links." at which end? My local links? Or the ones on the server. It is extremely important to me to be clear here, what I'm being saved from and what is at risk. Not least because, for example, I want no risk to myserver side bookmarks, but if it's the local ones and a total refresh fixes any issue, I'm up for it. I just want to know what I'm risking.
It's not clear why. And some "reason" might be helpful. because I see all the bookmarks on the server and on the web browser, I cannot see the problem. I see no messages in the Netxcloud log. The debug logs this very message offers me are empty. Something went amiss to be sure. But I can live with that if refreshing the local bookmarks (trusting the server side) is an option.

Expected Behavior

I would like clarity on 1 mainly. The message can at no costs be explicit about which end is being protected from blow away!

To Reproduce

Can't say what caused this failsafe to trigger alas. That is issue 2 above.

Debug log provided

I have provided a debug log file

Originally created by @bernd-wechner on GitHub (Dec 8, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2116 ### Which version of floccus are you using? 5.8.0 ### How many bookmarks do you have, roughly? 1000 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Edge ### Which version of Nextcloud Bookmarks are you using? (if relevant) 15.2.1 ### Which version of Nextcloud? (if relevant) 31.0.9 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug I see this message: > E029: Failsafe: The current sync run would delete 100% of your links. Refusing to execute. Disable this failsafe in the account settings if you want to proceed anyway. | Last synchronized: 1 month ago On the plus side, thank you enormously! Such fail safes are invaluable. No-one wants significant damage to their collection because of a mistaken configuration or software issue. That said, what wasn't clear to me on this message is: 1. "would delete 100% of your links." at which end? My local links? Or the ones on the server. It is extremely important to me to be clear here, what I'm being saved from and what is at risk. Not least because, for example, I want no risk to myserver side bookmarks, but if it's the local ones and a total refresh fixes any issue, I'm up for it. I just want to know what I'm risking. 2. It's not clear why. And some "reason" might be helpful. because I see all the bookmarks on the server and on the web browser, I cannot see the problem. I see no messages in the Netxcloud log. The debug logs this very message offers me are empty. Something went amiss to be sure. But I can live with that if refreshing the local bookmarks (trusting the server side) is an option. ### Expected Behavior I would like clarity on 1 mainly. The message can at no costs be explicit about which end is being protected from blow away! ### To Reproduce Can't say what caused this failsafe to trigger alas. That is issue 2 above. ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:39:58 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 22:39:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 8, 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! 💙

@github-actions[bot] commented on GitHub (Dec 8, 2025): Hello! :wave: 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! :blue_heart:

kerem commented

2026-02-25 22:39:58 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 9, 2025):

Hi @bernd-wechner
Good to hear from you again! Thanks for taking the time to open this issue. I'll definitely improve the wording there, that's a very good point!

@marcelklehr commented on GitHub (Dec 9, 2025): Hi @bernd-wechner Good to hear from you again! Thanks for taking the time to open this issue. I'll definitely improve the wording there, that's a very good point!

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

No description provided.

Rows
Columns