Skip to content

Support description text, tags for backends that support it #1962

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tomtom opened this issue May 25, 2025 · 1 comment
Open

Support description text, tags for backends that support it #1962

tomtom opened this issue May 25, 2025 · 1 comment

Comments

@tomtom
Copy link

tomtom commented May 25, 2025

Describe the feature you'd like to request

Many browsers (e.g., Firefox, Vivaldi) support text annotations or tags for bookmarks. It would be excellent if those plugins for browsers that do so, would also sync such text annotations and if the Android app would support it. For browsers (e.g., Chrome) that don't support these features, the text annotations should be ignored (but not overwritten/deleted) on updates.

Describe the solution you'd like

Plugins for browsers like firefox, vivaldi etc., and the Android app should support text annotations/tags. This info should be included in the master file on the server. Other plugins should ignore this info but never overwrite and delete it.

Describe alternatives you've considered

Tags could be added to the bookmark name but this would quickly become cumbersome and bookmark names could grow very big.

Copy link

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 💙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant