Domain would be too broad. Every YouTube link would have a warning, then, and one of the more impactful candidates for this feature is YouTube links.

I think the more useful solution would be to allow a droplet to have multiple URLs which it treats as aliases, possibly with some pattern matching rules to help recognize matches.

For example, I've written a script that gets all of my YouTube links in the mobile format and updates the droplet link to match the desktop format for YouTube URLs. This doesn't help for preventing duplication when using mobile, but it does on desktop. Being able to have both URLs in the droplet would resolve this.

There could even be some simple logic for major sites like YouTube which generated link aliases based on the bookmarked URL, possibly specified or modifiable by the user.

A link aliases list would also open up opportunities for "merging" droplets, where one link becomes an alias and all other properties are combined. This would help when unifying the tagging of duplicates before deleting one of them.

Zach Laster: pattern matching would require a priority analysis eg when using #anchor urls vs $/&parameters.

Not to mention there are times when having such duplicate bookmarks is actually useful. Search results and longtext scrolling jumps come to mind.

kiwi: The pattern matching was an additional thought, and can be discarded.

My primary suggestion is "aliases", which is essentially allowing a droplet to have more than one link associated with it. All links, including aliases, would need to be checked for existing droplets, but that's the only "hard" part.

Anything on top of that is bonus. Automatically generating aliases would be valuable, but can be left to the user.

spirit: this is the correct response. You currently cannot upload duplicates. When you try it will just route you to the folder that bookmark already exists in.

dwoodman596@gmail.com: it would be great if you could multi-select collections for a particular bookmark rather than only having the option to single-select

spirit: Why not use tags for usecase like that instead of collections?

Soumyajit Pathak: let’s say I have a bookmark about how to re-build a car engine. Maybe I want to bookmark under a collection called “General Car Maintenance” and a collection called “My Weekend Engine Rebuild”.

Tags alone can’t achieve this kind of use case.

spirit: this is a personal preference ofc. But I would use tags for things like that while keeping collections for broader topics. In your example, I will save the link under say “Automobile Essentials” or something and then add those two tags.

The way I see the difference between collection and tags is the cardinality aspect. Collection - link is a 1 - N relation while Tag - link is a N - N. And I like that differentiation.

Soumyajit Pathak: The only problem is that you can’t share tags whereas you can share collections.

Thats the biggest reason that tags don’t work for this use case. If I want to share a set of links with someone only about “How to Replace a Catalytic Coverter”, I can’t because I’m only allowed to have the bookmark in one collection titled “Automobile Essentials”.

Caution: It would also prevent users from accidentally overwriting the previously cached site, which happens if you have auto-save enabled and click the extension button on a previously saved link (destroys the "permanent copy" you previously saved, which is pretty bad design with the current implementation).

Rustem Mussabekov: I was thinking that might be ideal - I end up adding a lot of my links manually in different folders so it's rather easy to end up with duplicates. How it's implemented in the extension is great, I was thinking that for web/desktop it could show you all the locations where that bookmark is duplicated, then give you the option to add regardless or perform a duplicate merge right there

Rustem Mussabekov: For Android

Rustem Mussabekov: I'd particularly wish for it in the Android app.

Rustem Mussabekov: I think it should be viewable at a glance.

The extension icon should show the page is bookmarked when you visit it. That would be huge.

Rustem Mussabekov: Before creating a new feature request, I would like to ask what you think about this feature: I would like to have quite an opposite - to be able to create duplicate links in various collections, but ideally without creating actual duplicates or copies of the link.

I mean, the link would exist in a single instance only and collections I assign the link to would contain just a reference to it. So when I edit such link, I always edit the single instance of it, no matter in what collection I'm editing it. When I unassign it from a collection, it disappears just from that collection, the reference is deleted. When I delete the link, it disappears from all collections, obviously.

I'm aware that it may be quite a lot of work to implement and it may be complex, but it would greatly improve the UX. What do you think, please?

Pickle Rick: yes please this would be SO helpful!!!

Pickle Rick: I second this. Having an indicator that the page has already been bookmarked would be a huge help.