Rustem Mussabekov: imho, it would be better to keep auto-populating the description (while allowing overwriting it, as you currently do) and adding a separate notes field. A description is a quick introduction to a page, notes could be quite lengthy. I think it'd be a loss for the description field to be replaced.

Rustem Mussabekov: Rustem, you promised last year that you would add a notes field for bookmarks with markdown support. We all got super excited about that.

Now you are proposing that we use the existing “description” field and hide the actual auto filled descriptions. This is totally different and . First, I do want to keep seeing the auto filled descriptions as I get a lot of value from them. And second, we do need rich formatting for the bookmark notes to be able to, for example, capture a link to a site where we found the bookmarked link, keep notes as to why we saved it, etc. That has nothing to do with competing with note taking apps as thats a totally different job.

What made you change your mind? And how can we keep this conversation open to continue to make Raindrop the best bookmarking app?

Rustem Mussabekov:

The description field is helpful to me. If a notes field is going to be added, I think it should be a new separate field.

Also, for those of us that have already written custom descriptions, those would be gone if this field is hidden. Please make notes a new separate field.

Rustem Mussabekov: I love Raindrop! I completely agree with other people here, please do NOT remove or hide the current behavior of auto-populating the description field, but add an extra field for notes if necessary. I personally use the addon daily on Twitter and other sites that have a plain or useless Title, and the auto-added description is the only thing making bookmarks useful in these circumstances. Being unable to see the description with each bookmark, or having to manually add a description every single time, would make using Raindrop on those sites a nightmare. It would be great if the auto-add description could be improved, it doesn't seem to work all the time on Facebook.

Rustem Mussabekov: Happy to see some attention on this long-desired feature (7 years!). It does seem that there's a bit of confusion about what we are wanting.

First, we LOVE the automatic population of site name, favicon, image, description, and full page content when we save a link. It makes sense for those fields to be editable by us, but also we could "refresh" and have raindrop re-ping the site to pull the current content of that website metadata.

We ALSO want to be able to make our own notes about the item, that would need to be a separate field. Currently we can sort of add our notes to the description field, but that's just a workaround. We really need an additional field.

We don't want descriptions invisible.

We don't want descriptions replaced with a Note field.

We want a note field in addition to the description field.

Rustem Mussabekov:

This would be counter to how most would use raindrop to add value and I think is partly based in a misunderstanding in how note apps are used by many.

Ex ante: A description is auto-prefilled to make bookmark it findable / identifiable.

Es post: Notes for a bookmark are something users add once you WORKED with on the site with/out highlights. Be it a summary, remarks, collecting views from across the team or simply a copy of the reference text used for citation. My personal self from the future I (and any team) knows: the knowledge from highlights and thoughts on this page are in this raindrop reference. I do not need to look further.

It is not the actual production of NEW content which happens in note apps. NEW work only happens on a fraction of bookmarks and mostly likely across multiple bookmarks at the same time. This raindrop cannot serve and I think no one is asking this.

From UI perspective. Without highlights there is tons of space for it. Highlights can still be below.