[GH-ISSUE #2088] Add Raindrop.io sync #1399

Open
opened 2026-02-25 22:39:54 +03:00 by kerem · 3 comments
Owner

Originally created by @henryxrl on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2088

Describe the feature you'd like to request

Raindrop.io is another popular bookmark manager, which even has an extension for Safari. Being able to sync browser bookmarks with and via Raindrop.io will be awesome!

Describe the solution you'd like

Raindrop.io has pretty good API documentation, and there are already many services that integrate with it. Check them out here.

Describe alternatives you've considered

NA

Originally created by @henryxrl on GitHub (Oct 31, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2088 ### Describe the feature you'd like to request Raindrop.io is another popular bookmark manager, which even has an extension for Safari. Being able to sync browser bookmarks with and via Raindrop.io will be awesome! ### Describe the solution you'd like Raindrop.io has pretty good [API documentation](https://developer.raindrop.io/), and there are already many services that integrate with it. Check them out [here](https://raindrop.io/integrations). ### Describe alternatives you've considered NA
Author
Owner

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

<!-- gh-comment-id:3474670408 --> @github-actions[bot] commented on GitHub (Oct 31, 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:
Author
Owner

@subhead commented on GitHub (Jan 7, 2026):

So could this be possible to implement? Would be handy to have a way to sync with Safari on macOS.

<!-- gh-comment-id:3718378482 --> @subhead commented on GitHub (Jan 7, 2026): So could this be possible to implement? Would be handy to have a way to sync with Safari on macOS.
Author
Owner

@marcelklehr commented on GitHub (Jan 8, 2026):

Yes, it's very possible and until I get to it myself, I'd accept pull requests for this.

<!-- gh-comment-id:3723177001 --> @marcelklehr commented on GitHub (Jan 8, 2026): Yes, it's very possible and until I get to it myself, I'd accept pull requests for this.
Sign in to join this conversation.
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#1399
No description provided.