# Fibery Is Making Zoomers Suffer (Emoji Support Needed) **URL:** \ **Category:** Ideas & Features\ **Created:** [June 27, 2025, 7:03am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083 "2025-06-27T07:03:36Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![inn0minatus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/inn0minatus/32/11751_2.png) [@inn0minatus](https://community.fibery.io/u/inn0minatus)\ **Post date:** [June 27, 2025, 7:03am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/1 "2025-06-27T07:03:36Z")
1. Zoomers can’t function without emojis. 2. Currently, it’s only possible to leave reactions on comments. 3. Result: dopamine-starved Zoomers. Not ideal. 😢 Jokes aside - it would be great to support reactions on more than just comments. For example: - **Any entity field** (if enabled via a field option by the DB admin) - Or at the very least, **Rich Text fields** (also toggleable). This would be especially useful for things like Feeds, changelogs, meeting notes, or announcements. Let the dopamine flow. 💥✨ ---
**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:** [June 27, 2025, 7:05am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/2 "2025-06-27T07:05:52Z")
We do like emojis, but we will never add reactions to fields. It will make Fibery much more complex internally. If you miss some other things related to emojis, please share them! ---
**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:** [June 27, 2025, 7:07am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/3 "2025-06-27T07:07:34Z")
One idea we have is Emoji Reactions block inside rich text, check it out > **[Emoji reaction block](https://the.fibery.io/Product_Management/feature/Emoji-reaction-block-4670?sharing-key=5fbd4c40-3085-4c7d-929b-d64369c3847c)** ---
**Author:** ![inn0minatus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/inn0minatus/32/11751_2.png) [@inn0minatus](https://community.fibery.io/u/inn0minatus)\ **Post date:** [June 27, 2025, 7:08am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/4 "2025-06-27T07:08:21Z")
Ah, that’s a pity. Our main (and currently only) use case is this: we use the **Feed view** to publish blog-like posts related to projects. People rarely leave comments on these posts, but they _would_ happily drop an emoji reaction (for example, directly on the **Rich Text field** ). Reactions here would go a way in boosting lightweight engagement. 💬✨ ---
**Author:** ![inn0minatus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/inn0minatus/32/11751_2.png) [@inn0minatus](https://community.fibery.io/u/inn0minatus)\ **Post date:** [June 27, 2025, 7:09am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/5 "2025-06-27T07:09:43Z")
Oh, cool, this would also solve the issue for us. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [June 27, 2025, 8:54am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/6 "2025-06-27T08:54:44Z")
> [@mdubakov](#): > > but we will never add reactions to fields Internal Comments in a rich text field are essentially ‘reactions to fields’, right? (related to the long standing request that comments become first class citizen entities in order to be a well integrated feature where comments can be part of views) So user emoji’s would be just a variant of the same future implentation of comment entities. ---
**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:** [June 27, 2025, 10:15am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/7 "2025-06-27T10:15:53Z")
> [@inn0minatus](#): > > Our main (and currently only) use case is this: we use the **Feed view** to publish blog-like posts related to projects. Did you consider using [Threads](https://the.fibery.io/@public/User_Guide/Guide/Thread-View-(experimental,-emulates-Slack-channels)-221) for this? ---
**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:** [June 27, 2025, 11:11am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/8 "2025-06-27T11:11:50Z")
> [@Yuri\_BC](#): > > Internal Comments in a rich text field are essentially ‘reactions to fields’, right? Nope, comment is an entity, so it is reaction to entity ---
**Author:** ![inn0minatus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/inn0minatus/32/11751_2.png) [@inn0minatus](https://community.fibery.io/u/inn0minatus)\ **Post date:** [June 27, 2025, 12:37pm UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/9 "2025-06-27T12:37:32Z")
Yes, we were considering whether to use Threads or Feed for this. However, for micro-blogging use cases, Feed seems to be a better fit. It’s more suitable for sharing important project updates, new releases, polls, and similar content. Ensuring these posts remain visible and don’t get buried in a flood of random chat messages, which often happens with Threads. ---
**Author:** ![JackC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jackc/32/5420_2.png) [@JackC](https://community.fibery.io/u/JackC)\ **Post date:** [August 5, 2025, 12:27am UTC](https://community.fibery.io/t/fibery-is-making-zoomers-suffer-emoji-support-needed/9083/10 "2025-08-05T00:27:04Z")
I’d find it really handy to be able to convert the icon field from emoji to the same emoji but as text so I could use it in other formulas. Making visible shorthands for crowded multi-selects or just adding them to slack notifications would really help visibility for a few cases.