chuckya/app
Plastikmensch ea10f2e1e0
Don't set me to true for remote reactions
When an account and a remote account reacted with a custom emoji with the same shortcode, the `me` attribute was also true for the remote reaction, despite being a different emoji.

This query should probably be optimised, but it works.

Signed-off-by: Plastikmensch <plastikmensch@users.noreply.github.com>
2023-05-27 12:01:13 +02:00
..
chewy Change algorithm of tootctl search deploy to improve performance (#18463) 2022-05-22 22:16:43 +02:00
controllers ReactionsController: Don't check for status reaction existence in destroy 2023-05-27 12:01:13 +02:00
helpers Add hCaptcha support (#25019) 2023-05-16 23:27:35 +02:00
javascript eslint fix 2023-05-27 12:01:13 +02:00
lib Handle Undo from Misskey 2023-05-27 12:01:13 +02:00
mailers Add user handle to notification mail recipient address (#24240) 2023-04-17 11:06:06 +02:00
models Don't set me to true for remote reactions 2023-05-27 12:01:13 +02:00
policies Add missing authorization to ReactService 2023-05-27 12:01:13 +02:00
presenters Fix Performance/CollectionLiteralInLoop cop (#24819) 2023-05-04 05:33:55 +02:00
serializers support reacting with foreign custom emojis 2023-05-27 12:01:13 +02:00
services Run rubocop -a 2023-05-27 12:01:13 +02:00
validators Fix invalidating status reactions when they already exist 2023-05-27 12:01:13 +02:00
views Fix visible reactions setting not applying 2023-05-27 12:01:13 +02:00
workers Reactions: Return 404 when status should not be visible, asynchronous unreact 2023-05-27 12:01:13 +02:00