I can heart myself

[tzarebczan]

@JYamihud commented on Mon Jun 20 2022

Here is a screenshot from FastLBRY GTK that uses the comment API a little bit more straightly than odysee. Meaning hearts are one of the reactions that could be made to comments. In theory even multiple people can heart the same comment, if they are using the API or any non-standard client to LBRY. FastLBRY GTK is just one way of using it like this.

It's clearly me who hearted this comment. But Odysee's UI shows it to come from the publisher channel. I think there are 3 ways to deal with it.

• Ban all hearting not done by the publisher channel. Perhaps could work, but also not the best option. It's nice to have the hearts as a metric that could have more than one hearts. Perhaps a comment moderator might add a heart, and a publisher might add another heart.
• Show hearts only when they are done by publisher channel. A bit better. And I know that you can do it. The API knows that I hearted the comment even long after I did it. Because each reaction is signed by the channel that makes it. Perhaps you can find out who actually signed it and if it's not the publisher, do not show it at all.
• Make the whole hearts system more flexible. I noticed ( while playing around with comments ) that there are more things than just Fire, Slime and Hearts. As you can see on the first screenshot. I exposed all of the option to the users. Now, think about this. Let's make hearts an interactive "show your appreciation game" that exposes whoever hearts. For each heart, a small user's logo will appear, just like it is now, with the original Publisher having the LARGEST LOGO that is the closest one to the heart. So people could know. So Fire will be an anonymous like. While heart will be a non-anonymous like. While if the heart is done by the publisher, it will be VERY PROMINENT to have the same effect as it is now.

---

@tzarebczan commented on Mon Jun 20 2022

Thanks for the bug report, will move this over the comment repo since that's where it would need to be solved. Don't have an ETA on this for now.