The row(s) of buttons with icons at the bottom indicate the reacji that the post has received, with the numbers inside them showing the counts of how many of each reacji has been received.
- 1 Why
- 2 How to
- 3 IndieWeb Examples
- 4 Silo Examples
- 5 Implementations
- 6 Brainstoming
- 7 Criticism
- 8 History
- 9 See Also
Why should you support posting reacji?
One great reason is to own your reactions(👍👎😆🎉😕❤️) to GitHub issues and comments by posting them on your own site and POSSEing (e.g. using Bridgy).
Why should you support receiving reacji and displaying them?
So people can send you reacji and have it show up? E.g. a 🎂 for your birthday, or different kinds of reactions instead of just a "like".
How to display
Display a reacji post itself with reply-context. Because a reacji is so minimal, it may appear meaningless or misleading without additional context. But because reacji are small, a normal reply context would be presentationally overwhelming and look awkward.
The reply context for a reacji should be similar to the reply context for a like, which tends to re-order the reply-context as the object of the like, rather than a header above it. At a minimum show the in-reply-to URL linked to itself, then additional information as it is available (e.g. name or summary of post), all of which can be wrapped in a
u-in-reply-to h-cite hyperlink. Some sample hypertext designs:
How to markup
Markup a reacji response post as follows:
Note: if there is HTML in the content property, it may mess with emoji detection, so you should use
p-content, rather than
e-content for reacji reply posts.
<p class="h-entry"> <span class="p-name p-content">👍</span> to <a class="u-in-reply-to h-cite" href="http://tantek.com/2018/102/t9/css-2-2">CSS 2.2</a> ... <a class="u-url" href="...permalink of post..."> <time class="dt-published">2018-05-01 11:00-0700</time> </a> </p>
Can use div or li or even span instead of (or around) the p element depending on what works for your site and context, e.g. on a permalink or in-stream. Note the reply-context comes after the content which is atypical for reply-context hypertext design/markup in general.
In addition, if your reacji is at least a somewhat positive approval, you may want to add a
u-like-of class (in addition to
u-in-reply-to) to your link to the original post, so that even if the receiver only supports likes, they can count your response as a like, until they add support for receiving reacji.
(complete h-entry reacji as a positive response code example would be nice here, perhaps with a thumbs-up or heart or smileyface emoji)
How to receive and display reacjis
You can detect a reacji reply post by inspecting any incoming reply to see if it is a single emoji character. This is harder than it seems as there are many possible emoji sets and some emoji can consist of multiple characters combined. Just looking for the single character emoji will cover most emoji however.
- Be sure to remove whitespace as there may be some extra at the beginning or end unintentionally
- brid.gy backfeeds twitter replies with the @username at the front, you may want to strip this
- You may want to strip HTML tags to make sure they don't prevent you recognizing an emoji
Once you have detected the reacji and what emoji it is, display it as a reaction like you display likes, followed by the count next to it or stamped on it like in the Slack example above.
Examples of receiving and displaying reacji:
Reacji displayed as a facepile under a post on Seblog.nl. (Actual faces removed for the screenshot, grey rounds contain photo's from Facebook.)
Month view on Seblog containing a reacji post in the middle of likes, reposts, photos, checkins and an rsvp 'yes'.
Feed of reacji on Seblog, consisting of six separate reacji posts, in the format: "[emoji] on [post name] by [author name]."
IndieWeb Reacji Posts
IndieWeb examples of reply posts consisting of a single emoji character.
If you also receive and display reacjis from others on your posts in some special way different from comments e.g. a facepile, then add yourself above to the main IndieWeb Examples section!
- is also a like post (hence the /f in the URL) for fallback purposes, so that targets that understand likes but not reacji at least get the positive sense of the reacji being communicated. This method only makes sense for like-like reacji, but that's an acceptable limitation.
Since 2018-05-02, showing in-stream mini-reply-contexts of the form:
👍 to issue 2588 of GitHub project “csswg-drafts”
Peter Molnar used to display reacji with Wordpress, then had them removed; now they are back again, but since it's a static site, they are display with significant delays - 2017-06-01
(permalinks needed that show displaying reacji from others)
- Post is in-reply-to the original post
- Content is single emoji character
Besides Slack, individuals have started to post reacjis on other silos.
Twitter seems ready to roll out official support for 'reacji' in the near future:
Until then, people have been experimenting on their own...
There are examples of individuals posting reacji as tweets (reacjweets as it were)
A tweet author can simulate a limited curated set of reacji by posting a survey with only single-emoji responses. E.g.
Facebook has reacji (Path-style, as a small set of emoji-like graphics) as an extension of "Like" and calls them reactions. Supported since 2016-02-24 on posts, and since 2017-05-03 on comments. emoji and text (on hover) equivalents:
- 👍 like
- ❤️ love
- 🌸 (purple) flower - temporary Time 2016, The Verge 2017
- 🌈 rainbow (flag) - temporary Telegraph 2017, NBC 2017
- 😆 haha
- 😮 wow
- 😢 sad
- 😠 angry
- some concept/design background information
- https://www.facebook.com/tantek.celik/posts/10102142524051423 (requires login)
2017-05-03 New feature prompt to "React to a Comment":
- 👍 +1
- 👎 -1
- 😆 Laugh
- 🎉 Hooray
- 😕 Confused
- ❤️ Heart
- https://help.github.com/articles/about-conversations-on-github/#reacting-to-ideas-in-comments (screenshot in that page shows a crying emoji but doesn't appear to be currently supported)
Path has had limited reacji, as a small set of emoji-like graphics, since (??? their launch) years ago, and was likely the first silo to do so.
Basecamp replaces their previous “like” functionality with “boosts” which aim to merge reacji with short text reactions and avoids counts. They also only show the boosts to the author, not to others. [This article https://m.signalvnoise.com/introducing-boosts-an-all-new-way-to-show-your-support-in-basecamp-fae325634998] should probably be analyzed more and summarized best practices and indieweb relevant pieces entered in here.
"single emoji" detection:
- Ben Roberts made a PHP library for determining if a string is a "single emoji" (a harder problem than it seems) available at https://github.com/dissolve/single-emoji-recognizer (selfdogfooding on his own site)
- Tantek Çelik wrote a ~25 line PHP function with a heuristic for determining if a string is a "single emoji" - simpler yet more approximate, catches common cases, likely to handle future emoji expansions too:
function is_one_emoji($s)in https://github.com/tantek/cassis/blob/master/cassis-lab.php (selfdogfooding on his own site)
Facebook reactions to reacji:
- Bridgy backfeeds Facebook reactions as of 2016-04-28. Details.
- Bridgy Publish supports POSSEing reactions to Github
- We should call this reactions instead of reacji. The rest of the industry already does - Slack, Facebook, GitHub, etc. Common terminology is more valuable than minor semantic differences. (Lots more discussion in IRC.) - Ryan Barrett
Slack was first to ship a built-in reacji feature that allows anyone to respond to any Slack message with a single emoji, which are then tallied like votes.