Idea: Automatically convert Comment to Highlight

Ideas & Features
1

The current Comments are not entities, Highlights are.
Highlights however require a lot of clicks, not userfriendly for rapid commenting, and have no thread functionality.

Let’s work around that and create a script to automatically conver comments to highlights?
We need to think how to display a thread in a Highlight then, ideally not using Comments :wink: but another db ‘Comment’ that can be nested.

2

I don’t mean to sound rude, but this sounds like a bad idea. Highlights have very specific functionality (e.g. they require a source, can have a target, and are limited in the number of dbs they can relate to). I suspect that using them for comments will give a really bad UX.

3

Thanks for the response—your point is valid. To clarify my intent:

1. Not advocating for misusing Highlights

  • I agree Highlights aren’t meant for commenting.
  • My suggestion was a workaround, not a proposed model.

2. Real issue: Comments are not entities

  • Cannot be filtered, queried, related, or extended.
  • Cannot appear in views or participate in automations.
  • No ability to tag, track decisions, or link across contexts.

3. Threading alone isn’t enough

  • Current Threads group comment chains, but the comments themselves remain UI-bound.
  • Lacks metadata, traceability, and cross-contextual insight potential.

4. Bigger picture

  • Serious teams need structured collaboration tools.
  • Current Comments system blocks this.
  • A future model where Comments = Entities would align better with Fibery’s data-first vision.

Would love to see this discussed as part of a broader “collaboration primitives” roadmap.