I also think that categories have more freedom of use through tags, rather than through folders. I give my thousandth vote :)

I hope this feature gets implemented soon. This would be a lifesaver to have like a hyperlink of sorts to have a single bookmark in multiple folders. The reason for this is many times I end up preferring two ways to get to certain things. For example let’s say I have a “PC” and “Tools” folder. I like to put all tools in the tools folder but also would like to put the PC specific tools on the PC folder.

Also can we make this feature work for both individual bookmarks as well as entire folders?

This is also very similar to the feature request for favorite tags.

Yes, please, please, please!

What takes you so long to achieve this?

I think a lot of people would be grateful for this feature.

I personally lose time and effectiveness having to do this, manually saving duplicates for each link and then... I even don't want to hav it as duplicates, it should be the same link into different collections.

Thanks.

Somebody mentioned using tinyURL as a workaround. A more convenient workaround is just to add an anchor link (e.g. "example.com#sometext") or a query string (e.g. "example.com?sometext") to the duplicate url you want to save.

So long as you choose an anchor or query string that isn't actually used by the webpage the page will be uneffected and Raindrop will treat it as a new bookmark.

Isn't this very similar to hierarchical tags, which would allow to add a bookmark to multiple tags and then categorize them in sections?

Feature request here: https://better.raindrop.io/feature-requests/p/hierarchical-tags

Yes, please, make it so!

Yes this would be huge!

IMHO. I would prefer this feature to be implemented as bookmarks share on a tag basis with hierarchical tag support.

This reminds me of the folder first vs tag first storage approach in Evernote. A bookmark can be treated as an asset stored in a bare minimum amount of folders and tags, being its live status or categories in many forms. Tag, in this case, is the main trigger for data finding relative to the folder. Ex. We can tag a bookmark of bicycle planned for future summer camp as #bicycle_collection, #stuff_to_buy, #summer_camp_plan, #action_urgent, #kids_birthday_gift_idea all share to different people. The tag as asset status could easily come in go in time if needed vs the folder storage approach. And the bookmark should remain as a single asset entry in the entire system for easy management in principle.

Although bookmark pinning could work for the above. However, the mutually exclusive folder storage fashion seems not in favor of this. How to manage a large amount of bookmark cross pining to multiple collections is in question when someone’s usage reaches to a certain level of complexity.

This! I would love to be able to have general, topical collections that I can later gather projects from into project-focused collections without removing them from the original collections.