# XIP-20: Reactions content type

**URL:** <https://improve.xmtp.org/t/xip-20-reactions-content-type/524>\
**Category:** Final XIPs\
**Tags:** content-type, proposal\
**Created:** [January 10, 2024, 10:26pm UTC](https://improve.xmtp.org/t/xip-20-reactions-content-type/524 "2024-01-10T22:26:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mg](https://improve.xmtp.org/user_avatar/improve.xmtp.org/mg/32/533_2.png) [@mg](https://improve.xmtp.org/u/mg)\
**Post date:** [January 10, 2024, 10:26pm UTC](https://improve.xmtp.org/t/xip-20-reactions-content-type/524/1 "2024-01-10T22:26:41Z")

</div>

> <https://github.com/xmtp/XIPs/blob/main/XIPs/xrc-20-reaction-content-type.md>

---

<div class="post-metadata">

**Author:** ![nplasterer](https://improve.xmtp.org/user_avatar/improve.xmtp.org/nplasterer/32/582_2.png) [@nplasterer](https://improve.xmtp.org/u/nplasterer)\
**Post date:** [January 10, 2024, 11:12pm UTC](https://improve.xmtp.org/t/xip-20-reactions-content-type/524/2 "2024-01-10T23:12:28Z")

</div>

I’ve seen this successfully implemented in several apps now including xmtp.chat. This proposal looks good to me 👍

My only comment would be on reaction removals being the same content type just sent again with the same content but flagged as a removal. It might be nice if reaction removals were a different content type or if there was a way to make certain aspects of contentTypes mutable.

---

<div class="post-metadata">

**Author:** ![nick](https://improve.xmtp.org/user_avatar/improve.xmtp.org/nick/32/466_2.png) [@nick](https://improve.xmtp.org/u/nick)\
**Post date:** [January 24, 2024, 1:49am UTC](https://improve.xmtp.org/t/xip-20-reactions-content-type/524/3 "2024-01-24T01:49:44Z")

</div>

Before we finalize this content type I want to make sure: do we really need to support non-unicode schemas in the initial version?

Unicode seems to be the only schema currently used by applications. If someone were to send a `shortcode-discord` emoji it is unlikely that any client application other than their own would be able to read it and display it properly. This hurts interoperability, and raises the bar _substantially_ for an integrator to fully support this content type.

---

<div class="post-metadata">

**Author:** ![rygine](https://improve.xmtp.org/letter_avatar_proxy/v4/letter/r/e274bd/32.png) [@rygine](https://improve.xmtp.org/u/rygine)\
**Post date:** [January 25, 2024, 7:10pm UTC](https://improve.xmtp.org/t/xip-20-reactions-content-type/524/4 "2024-01-25T19:10:11Z")

</div>

i’m OK with this suggestion. it definitely simplifies the implementation.