Tuba icon indicating copy to clipboard operation
Tuba copied to clipboard

Post reactions

Open GeopJr opened this issue 3 years ago • 5 comments

GeopJr avatar Jan 03 '23 14:01 GeopJr

You can view reactions as of https://github.com/GeopJr/Tooth/commit/2df67299a07ea4896a1f8b115c34d771f9f55d13

GeopJr avatar Jan 09 '23 01:01 GeopJr

You can view reactions as of 2df6729

Any plans of making them actionable under Chuckya/Glitch-Soc?

cyrneko avatar Aug 21 '24 18:08 cyrneko

I'm kinda waiting for glitch-soc to merge it because apart from it there are two competing implementations:

  • Akkoma(/Pleroma(?)) allows you to do multiple reactions and favorite a post
  • Misskey on forks that have somewhat masto api compat allow you to either favorite or react

I think the current runner up for glitch-soc follows the Akkoma one(?) so that will be the one we implement I guess. But until it gets merged I'm a bit hesitant to implement it

GeopJr avatar Aug 22 '24 03:08 GeopJr

I'm kinda waiting for glitch-soc to merge it because apart from it there are two competing implementations:

* Akkoma(/Pleroma(?)) allows you to do multiple reactions and favorite a post

* Misskey on forks that have somewhat masto api compat allow you to either favorite or react

I think the current runner up for glitch-soc follows the Akkoma one(?) so that will be the one we implement I guess. But until it gets merged I'm a bit hesitant to implement it

I mean, it is downstream in Chuckya which is already used on instances, primarily wetdry.world, in production

It does follow the Akkoma model, you can favourite and react. With wdw's config you can react with one reaction at most + a fav

Though judging from my notifications from *key users, they can also do both (react+fav) if they so wish

cyrneko avatar Aug 22 '24 10:08 cyrneko

I mean, it is downstream in Chuckya which is already used on instances, primarily wetdry.world, in production

I'd still rather wait. Chuckya and downstreams depend on glitch-soc's design decisions still, say glitch-soc decides to do something as simple as change the API endpoint for it, then downstreams will follow.

Of course that is not set in stone, but I'd really prefer if we didn't have to go back to it again and again because it's not merged yet and stuff might change :/

GeopJr avatar Aug 22 '24 10:08 GeopJr

Ended up adding support for the Chuckya API, but istg if they change it last minute :anger:

GeopJr avatar Oct 20 '24 23:10 GeopJr