Successful #collaboration is at the heart of project management. That's why our Activity tab for work packages has been completely revised two weeks ago.

💬 Interaction is now more intuitive and direct than ever. And with the addition of 🎉 emoji reactions, collaborating has never been more engaging.

➡️ Discover how OpenProject can transform your team’s collaboration: https://www.openproject.org/blog/project-interaction-collaboration

#ProjectManagement #TeamCollaboration #OpenSource #EmojiReactions #Interaction #OpenProject

I used to think that #emoji #reactions are for the illiterate.

Then I got addicted to them in Signal and Matrix.

Now I can't wait for #Jabber clients to implement them. Why is this #XEP still experimental after 5 years, @larma ?
https://xmpp.org/extensions/xep-0444.html

#xmpp #xep444 #emojiReactions

#npptech

Discover the power of Micro Talk - concise interactions that foster deeper connections by emphasizing non-verbal cues and mutual respect. Make every interaction count in today's fast-paced society. #MicroTalk #SocialConnections

https://t.co/2gQTypv8cG

#microtalk
#concisecommunication
#emojireactions

…for Glitch draft PR #2221 (not yet merged but deployed by catcatnya.com and wetdry.world, among others) and other implementations that implement it (my ports to Firefish and Iceshrimp).

displaying reactions

status objects now have a reactions field. if present, this will be a list of Mastodon Reaction objects, the same kind used by the existing announcements API. display them the same way you'd display reactions to an instance announcement.

adding and removing reactions

there are two new endpoints: POST /api/v1/statuses/:id/react/:name and POST /api/v1/statuses/:id/unreact/:name. id is a status ID. name can be a Unicode emoji, a local custom emoji shortcode, or a remote custom emoji shortcode (these last look like [email protected]). these endpoints do not take a request body, and return an updated Status object including the reaction changes.

reaction cap

instances have a limit on how many unique reactions you can have to a status. you can find this value in GET /api/v1/instance under .configuration.reactions.max_reactions (and you can use the presence of .configuration.reactions to detect the the reactions API).

if the number of reactions to a status with the me field set to true is equal to max_reactions, you should hide whatever button you use to add a reaction. ignoring the cap will lead to an error (Glitch) or previous reactions being removed (Firefish/Iceshrimp).

reaction notifications

there is now a reaction notification type for when an account reacts to a status. under Firefish and Iceshrimp, this notification type has a reaction field as well as account and status, which is a Reaction object with a count of 1, so that clients can show the actual reaction. this field isn't present under Glitch (yet?).

#MastoDev #FediDev #EmojiReactions #Glitch #GlitchSoc #Firefish #Iceshrimp