At the end of the day, comments are a database, even in Fibery, just not a user-made one. They are shown as a to-many relation in automations.
I agree that if done in this way, it needs just as good UX, but I donāt think having them as a user-made database will hinder UX in any way if built correctly.
It would need to be a feed view with non-editable text unless a user pressed on the edit button. As currently done in comments. An additional reaction field. And then the part that would be the most different is the āReply to commentā, this would probably need to be two databases. One with comments, and one with sub-comments. This behaviour of opening a text field would be unique to the discussion view, instead of opening a popup for input, it would open right under the parent entity for input. I donāt see why changing the underlying database to be a user-made database would affect the UX. Maybe Iām missing something though? @Michael_Ichter? Could it not look and feel the exact same way but be a user-made database? Then we could even add attributes to comments like assignee, etc. The comments UX is the most clean way of data input at the moment (especially for rich text, looking at you, feed view), but its limited to comments unfortunately.
Ohh and one feature needed for this to work correctly is to have āstrong relationsā where the related one-to-many relations are deleted and restored together. As this is the way comments currently work: On delete setting/strong relations for relation settings