Comment system is not scalable

[RonMakesSystems]

Linked:

Entity-based versus native for Docs, Comments & References

Agreed and adding +1 about permissioning. Since comments are not exposed as a database, we cant limit who can or can not see the related comments. “UI will be quite bad, unintuitive, etc. And you will not gain much having comment as a database. BTW, what exactly you need?” What if you set create a “tread view” which is showing entities but in a thread view like comments, but in reality they are just entities, not comments under the hood?

Table view Comments field - sort and last N display option

I’d like to suggest: In a Table view… for the Comments field, you consider adding: ability to sort in reverse chronological, so the last comment shows up on the left ability to show just the “last N” comments in either chronological or reverse chronological order I hope you might consider.

What is the Upgrade plan of the Comments feature?

Yes! This would be absolutely amazing. I find myself resorting to comment fields just because it is so easy and fast add updates. But it lacks some functionality that I would get from doing it the “correct way” (Sorting by more recent comment, filtering entities which haven’t been commented on for over 2 weeks, etc) Specifically referring to the thread view within an entity, not the stand alone thread view. This could be game changing in terms of user input. Potentially even allowing you to set…

Comment fields and inline comments to be entities with fields (comments database)

Is there any update on this? I find the inline/richtext “resolution-comments” rather useful even if they are currently only available for entities’ description: However it would be nice to expose those separately, akin to displaying regular comment counts. Preferably with Open vs. Resolved states so we can streamline pending “Mini-Tasks” or information into top-level table views etc. Exposing the last true modification date on per-“property” level would also be awesome. I run time-based, hour…

Please make Whiteboard/Form/etc just fields, not isolated artefacts

This is what I see as a design mistake in the Fibery ecosystem, which is that currently it still holds on to artefacts like Document, Whiteboard and Form (and more to come?) that are relatively isolated and not a well integrated components like entities or fields. Other comparable modular fieldable entity based systems (e.g. Drupal) allows these artefacts, often called ‘media’, to just be a field that can be attached to any entity type, and has removed these to be created without entity fields. …

I think that the comments UX is lovely, and would love to see this as well. I haven’t seen it done in another system, but Fibery isn’t like any other system

Then imagine the Quick Add ui as the comment (with the extra fields you can add at the bottom of the comment).

Also for access templates comments can not be hidden / not given access to. They have a lot of limitations atm.

All in all, this could be a game changer and be great when it comes data entry as well.

I would love Fibery to be as “pure” as possible. Giving as much power to the admin to build and create based on their need. I think, @mdubakov, you notice this as well when (soon) depreciating documents. I see a future with depreciated comments (changed to thread view) and whiteboards as fields (just like a document, RTF, is a field), as well as a graph view (similar to the multi-entity relation in whiteboard now).

NOTE: I’m not sure about in-line comments and whiteboard though. You could bring back references and you could highlight then create a comment entity. Idk. And you could set any database as “comments” in a whiteboard and it will just then create the comment and be related to the entity. I’m less bothered about these, not sure about you Yuri?