I thought I’d mention this again, and curious if others who are using the new “Threads” Experiential feature might also find this now more needed, wondering about you @helloitse (although I wasn’t sure based on your comments in CHANGELOG: Nov 10 / New Terms (App → Space, Type → Database), New Space Editor, Actions in Headers in Table View, Phone field that you are actually using Threads yet 
), and @YvetteLans ,and of course others…
Since it appears the approach of Threads is to roll up references to entities that come from the thread as a way to track mentions and updates - I’m referring to the comments here in the guide:
I highlighted in pink the point about the value of the thread in updating the progress of work.
I’m also pointing out with the arrows in that screenshot that you can see only the most recent comment’s time is shown. So if you are chatting about something, in particular of bigger scope, like a project, and all the comments are from the same entity, in this case the Thread entity, you will only see the time of the most recent one. So you can’t really see when most of the commentary took place, which is needed for the best context.
And this also shows how I think it would be useful if you could see comments and references in a chronological stream for the best information on the history of an entity’s activity, which is a feature request at that link. If we had this feature, you’d have even more flexibility in where you talk about something in Fibery - so if I want to quickly mention a project while I’m typing in a thread, and I “#” tag it, I know that will show up at the top of the updates for the rest of the team. Without this feature, I have to take a moment, go to the actual comments area of the project, then write my note - if I want to make sure it’s seen at the very top, and the time of what I’m writing is preserved.
Thanks for listening!