This is @DingoInThere@lemmy.today

The user created an account 19 days ago and has made 1,179 downvotes compared to 0 upvotes.

The user hasn’t made a single post or comment either.

Yet another example of someone targeting a very small handful of users. Looks like the posts being downvoted are random comments and nothing controversial, but they are all downvoted by this user.

It seems very targeted, almost like he’s fixated on a small group of users and is trying to bully them into no longer enjoying Lemmy.

Of course, this would never stop me, since I'm not afraid of bullies. But it may turn other people off and less inclined to being a part of the fediverse.

Not very nice behavior. Hmm, I wonder what they are so angry about?

https://lemvotes.org/user/DingoInThere@lemmy.today

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 6 points 3 weeks ago

As far as I can tell, that only really affects Hexbear users though.

Someone on another federated instance can still see the post from their own instance, downvote it, and potentially see those downvotes there. Hexbear users just don’t have the downvote feature on their own instance.

So, for example, you post something about four-leaf clovers. From Hexbear, you see the upvotes and think, “Cool, I brightened some people’s day.” But someone viewing that same federated post from another instance might see 125 downvotes. They may decide not to read it because of that score, or even add another downvote.

Basically, disabling downvotes on an instance doesn’t necessarily eliminate downvotes across the whole Threadiverse. It mainly changes how voting works and appears for users on that particular instance.

That’s been my experience, anyway. I have an alt account on an instance with downvotes disabled. When I’m logged in there, I can’t see or use downvotes. But when I view the same federated content from my account on another instance, I can see downvotes and even cast them.

  • source
  • parent