Based on the comment, it seems there's more opposition toward visible downvote than upvote, so maybe dev should just make upvote visible and not downvote?

There's more talk about how bad visible downvote is and no one seems to talk about the upvote lol.

I would like the option to make it public on my community. I have asked people not to downvote amateur bakers for just trying to improve their skills but some assholes don't listen.

That'd be nice.

I'm split, but I lean slightly towards no. On one hand, it could be good for discoverability, and it would help my efforts to make a client-side algorithm

On the other hand, it will make one of Lemmy's problems worse - engagement. Some people will vote less, and it's already feeling a little quieter around here as the numbers settled after the Reddit Exodus. I doubt it'll be a massive change, but a .5% decrease in voting, permanently, could make a difference

Ultimately, you can see it on federated platforms, so shrug

You could make a client or browser add-on or something that just uses a separate account for all your voting.

Sure, but I think we can go further.

Filter the votes I see based on which users or instances I've blocked. I've blocked them for a reason.

There are merits for it and against it. My biggest concerns would be privacy regarding data scrapers .

Regarding poor behavior, I really think that ultimately comes down to moderation on the platform. I've only had a few poor experiences but I am also someone who sometimes sees certain threads as dumpster fires and refrains from joining in or refrains from responding when I feel there isn't any form of discussion or chatter to be had. I can understand that it likely happens more often than not but I also believe that moderation is the only reasonable way of curbing it. Moderation teams have to make it clear that the behavior is not welcome and that it will be dealt with.