# Oct 19, 2023 / šŸ˜… Browser notifications, modify reference selection, experimental new comments **URL:** \ **Category:** Changelog\ **Created:** [October 19, 2023, 12:30pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307 "2023-10-19T12:30:31Z")\ **Posts on this page:** 18\ **Page:** 2
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [October 20, 2023, 2:06pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/21 "2023-10-20T14:06:34Z")
> [@aoe](#): > > As it is right now, the litte icon to the side is a distraction from what is usually a less important link if you look at the document as a whole. > [@aoe](#): > > This is especially important for us when putting extra effort in making the rich text fields as beautiful as possible (e.g. onboarding documents/documents shared with clients/wiki etc). Yes thatā€™s exactly our use case. For team occasions, it doesnā€™t matter. But in our wiki for clients we link to other wikis and there itā€™s quite disturbing. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 20, 2023, 3:48pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/22 "2023-10-20T15:48:56Z")
> [@YvetteLans](#): > > Give the option to collapse (helpful when the thread is very long) Agree here. I think collapsing and expanding is nice when needed. e.g., we put the comment section at the top of some of our entity types (specific entity types we work in are comment heavy or we want context quickly, so having them at the top makes things easier). For long-running chats, having collapsible and expandable comments would be nice since we still want to see other related entities and references below, without comment section taking up the whole screen and pushing down other items (like rich text fields, lookups, related entities, references, etc). Initial thoughts are that embedded comments UI should show last 3-5 comments and can be expandable or allow users to select the default view (previewed or expanded). Furthermore, I think the ability to open them in side-panel is also nice so that comments can be read while reviewing entity, rather than ā€œeither-orā€. > [@mdubakov](#): > > And while we are here mostly speak about comments, I want to share a potential **Thread View** concept (to have Channels-like thing in Fibery) that we quickly created to test internally, maybe you will give valuable feedback here as well šŸ™‚ @JoelH @Illusory I think this is a great idea and I can only imagine other potential scenarios this unlocks (e.g. AI automation on entity comments, filtering, lookups, maybe adding other fields to the ā€œThreadsā€ type). The only concern (for myself, maybe not for others) at first glance is ensuring comment/thread type is differentiated well from other types in places like Search and References. Example: In the preview of threads that @mdubakov provided when Channel ā€œDailyā€ was referenced, I noticed the entity badge is ā€œDā€. There should be some sort of indicator or icon that reflects that it is a channel and of thread type/feature, and not just a random entity. I think Threads has the ability to be a great addition, but Iā€™d hate for it to get lost within all of the other views and types (if itā€™s meant to foster meaningful interaction, influence use and compete with a dedicated chat app like Slack, it should stand out as a core feature of Fibery spaces and entities, not just another database). ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 20, 2023, 3:56pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/23 "2023-10-20T15:56:39Z")
> [@Illusory](#): > > I think Threads has the ability to be a great addition, but Iā€™d hate for it to get lost within all of the other views and types (if itā€™s meant to foster meaningful interaction, influence use and compete with a dedicated chat app like Slack, it should stand out as a core feature of Fibery spaces and entities, not just another database). This, exactly this! On the one hand I love the potential that ā€œThreadsā€ _would_ be ā€œjust another databaseā€ under the hood, and thus perhaps more powerful/flexible (e.g. being able to run automations on its contents, summarize with AI, auto-create tasks even, or create Fibery Reports to analyze it, etc.). But I think there is already too little meaningful differentiation between some aspects of Fibery (by design as itā€™s a ā€œLego boxā€) and this one seems more critical to make clearly different. As someone who hates Slack, especially its use in situations where a ā€œlighterā€ solution would be better, I would love having Threads in Fibery. But the question of course is how many people would actually use it and would its long-term development and maintenance be worth it. The experiment is fantastic to see, and the progress shown here from Fibery team after discussion is amazing, the quick iteration is šŸ‘šŸ‘šŸ‘. But will such a feature be worth long-term maintenance and improvement for Fibery? I guess that depends on how you scope it (and how much effort is involved in maintaining it). My hope is that it can be a ā€œgood enoughā€ feature (that is surprisingly good!), with Slack for heavier users and thus without falling into scope creep, etc. to drag down the dev team on maintaining it. A ā€œjust good enoughā€ chat-like feature integrated with Fibery could be brilliant. That said, the question is how you get people to use it instead of Slack (or _if_ you even want that, and if not, who are the target users?). Others have tried before you, and adoption seems low (Quip, ClickUp, probably more). Iā€™m rooting for you, Slack is a fragmenting, stress-making disease IMHO! But people are addicted to it, soā€¦ itā€™s a challenge. šŸ˜… ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 20, 2023, 4:00pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/24 "2023-10-20T16:00:33Z")
Yeah, we understand all challenges, that is why we wanted to keep scope minimal and just replace few use cases, like discussions around Fibery entities (features, tasks, etc) and **some** generic channels like Daily. Note that Thread View is just a view, so it is possible to create Thread View for Feature, for Product, for Task, for anything. In my demo I created a special Database that I called Channel, but there are no restrictions. Actually, we donā€™t want to spend more than 2 additional weeks on that and that is why I said that it is unlikely we will release it in public. But weā€™ll seeā€¦ ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 20, 2023, 4:12pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/25 "2023-10-20T16:12:44Z")
> [@mdubakov](#): > > Actually, we donā€™t want to spend more than 2 additional weeks on that and that is why I said that it is unlikely we will release it in public. But weā€™ll seeā€¦ _Do_ release it in public if maintenance for it can be light (due to small feature set for this area/function)! Then you can really see whether and how people actually make use of it. šŸ™‚ ---
**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\ **Post date:** [October 22, 2023, 7:33pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/26 "2023-10-22T19:33:33Z")
Release as an experimental feature and gather feedback. Thread View is a very interesting feature. šŸ•¶ ---
**Author:** ![Nevil\_Hulspas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nevil_hulspas/32/4703_2.png) [@Nevil\_Hulspas](https://community.fibery.io/u/Nevil_Hulspas)\ **Post date:** [October 23, 2023, 10:15am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/27 "2023-10-23T10:15:51Z")
> [@mdubakov](#): > > After all feedback we decided to simplify comments and get rid of panels. > Here is how it will work > > We are also considering get rid of collapsing, but here we are less sure. Jep, this is it!! Donā€™t get rid of collapsing, itā€™s much cleaner that way. Now when will this be released?! We have experimental enabled but are not seeing this yet. Also I like the threads idea (but only with unread notifications). I can imagine we might eventually not have to use Slack anymore. The less tools the better. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 23, 2023, 12:04pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/28 "2023-10-23T12:04:51Z")
I agree as well that it should be released. Love the idea and am sure weā€™ll adopt it. @mdubakov ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [October 23, 2023, 10:22pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/29 "2023-10-23T22:22:51Z")
Hmm, Iā€™m considering using this thread function to replace all Standup meeting or even personal tracking habits instead of each entities for each days, which means I replace feed view to thread view. Should I do that ? and what the difference between them in personal usecase, not collaborate ? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 24, 2023, 9:45am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/30 "2023-10-24T09:45:48Z")
Feed view displays the contents of rich text fields. Thread view displays the contents of comments. ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [October 25, 2023, 8:26am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/31 "2023-10-25T08:26:59Z")
Guys, is it possible to keep new comments in the same record window instead of opening a sidebar? Also, it will be useful to have a setting if we always want to show all comments. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 25, 2023, 8:28am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/32 "2023-10-25T08:28:13Z")
> [@Eugene\_Vabishchevich](#): > > Guys, is it possible to keep new comments in the same record window instead of opening a sidebar? It is coming in tomorrows release. > Also, it will be useful to have a setting if we always want to show all comments. Here we will not change anything so far. What do you mean here? Show only X latest comments setting? ---
**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\ **Post date:** [October 25, 2023, 5:37pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/33 "2023-10-25T17:37:29Z")
The ai filtering sounds amazing! Iā€™ve been sending lots of loom feedback on grid column ā€œchallengesā€ ā€“ great theyā€™re getting resolved. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 26, 2023, 1:46pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/34 "2023-10-26T13:46:10Z")
Weā€™ve fixed (I hope) nested comments in todayā€™s release > [@Oct 26, 2023 / speech\_balloon Replies in entity comments, Specify numeric values for select options](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334): > > speech_balloon Replies in entity comments Last week we experimented with comments in a separate panel, but feedback was negative (thank you!), so we iterated again. We removed panels for comments and just added replies to main entity view. To add the first reply, find Reply to Comment icon in a comment and click it. Weā€™ve added a comments icon in the top right entity menu. When you click on it, it scrolls you to the first comment. NOTES: Repliesā€¦ ---
**Author:** ![Nevil\_Hulspas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nevil_hulspas/32/4703_2.png) [@Nevil\_Hulspas](https://community.fibery.io/u/Nevil_Hulspas)\ **Post date:** [October 26, 2023, 4:13pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/35 "2023-10-26T16:13:59Z")
I was very excited to try this but also quite disappointed when I saw that you did not add collapsable replies. I REALLY want it to be like this: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/18c32c11545eef9993ac1243850a2bfa683ca203.jpeg) Please!! It will become a UI nightmare for us if this wonā€™t be implemented. Also it seems like we cannot disable it in experimental settings anymore? I donā€™t want to enable this as of now without collapsable replies. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 26, 2023, 4:17pm UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/36 "2023-10-26T16:17:19Z")
> [@Nevil\_Hulspas](#): > > Also it seems like we cannot disable it in experimental settings anymore? I donā€™t want to enable this as of now without collapsable replies. We are going to add collapsing as a part of Resolved Comments feature. Indeed it is not possible to disable it, but in old comments there was no collapsing as well. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [November 5, 2023, 4:55am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/37 "2023-11-05T04:55:20Z")
Just wanted to add on to my other post [here](https://community.fibery.io/t/oct-26-2023-replies-in-entity-comments-specify-numeric-values-for-select-options/5334) that Iā€™d love to have the ability to have the replies to comments not pre-collapsed. Being able to scroll down a page and see all the converstation, without grabbing the mouse and clicking to open up the nested replies, is a big time saver that Iā€™m already missingā€¦please consider adding this as a preference in settings! Thank you! ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [November 5, 2023, 5:04am UTC](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307/38 "2023-11-05T05:04:38Z")
Another option for how to handle many comments, could be: default to showing only new comments that you havenā€™t yet seen, with a button to reveal the entire thread. [Previous page](https://community.fibery.io/t/oct-19-2023-browser-notifications-modify-reference-selection-experimental-new-comments/5307.md?page=1)