Hey, appreciate the response. I have been meaning to respond to this comment of yours:
I can see where this might not be for everyone, but I actually like the ability to look in on an activity stream around an entity and see all the activity being done - status changed, comments made, due dates adjusted, and in the case of Fibery - references. In the case of Fibery though it’s harder for the average user to see this since you have to hit the “clock” icon and some of my users cannot get it in their head to remember that is what that icon is for. When the activity stream is right next to the entity and “hits you in the face,” you are forced to look at it, and thus see what’s been going on. This is actually useful in my case as I have a lot of project-type db’s and have found it would be better for those juggling multiple projects if they could see the activity right away, because what happens is they will at times go in and repeat stuff that’s already been done around an project entity, then have to be reminded that it’s already in the activity stream. For example, a due date was updated, with a comment as to why the change was made, but another user comes in and questions that because they can’t see at a glance the update in the first place. The original person changing the due date has to go in and comment back, reminding the person of the original change.
If there was a customizable way to display different types of activity on the entity card with quick filtering, so in the case of my request that you cited of Merge Comments and References in one common Stream for better flow, then yes this would be very good! Just to explain the use case once more, with Fibery’s excellent # tagging, which means you can type and reference anything else in Fibery in one click, you get a kind of “shortcut” to making updates when you reference an entity in another entity. An example - I have three tasks assigned to me of similar nature. I comment in the one task that I finished this task, and the other 2 while I was at it. I reference those other 2. If References and Comments were in one chronological stream, the other 2 tasks I did would pick up these references at the “top” of their stream, so anybody coming to read them would see the reference as the most recent update. Now in Fibery, my users are conditioned to reading comments to try to see if there’s an update, because this is the default way you look for updates in just about any app that supports comments - GitHub, SalesForce, Jira, etc. etc. If the reference I just did shows up right there at the top of the area where comments are, they will see that I updated all three tasks in one fell swoop, and you have a very effective tool here that only Fibery offers among all the other apps out there! Right now though, with Comments their own separate element on entities, I can’t get this benefit without having to say again and again to my users to “always read both comments and references on your entities,” but they still don’t do that, I think because it’s simply unnatural to them!
I feel like there is support for this (in the public roadmap among other places) so I look forward to seeing what the team will be doing. Evolving references like this really give Fibery an added edge when looking at the Roam/Notion/Coda environment and pulling together some of what those tools offer in isolation.