Detecting vote manipulation or brigading (example)
After reading this post here I took a deep dive into the database and ran a few queries to see if I could use it to detect some basic manipulation such as brigading or other types of persistent hostile behavior.
I'd describe this as people who could have blocked a certain community but instead seemingly dedicate themselves to continuously downvote posts, maybe because they don't like furry stuff in general.
Each line in the image corresponds to one person and how many times they have downvoted posts in a given community.
I won't take any actions right now, this is all very experimental. I just wanted to share this with y'all to let you know that we admins have tools to give us clues about whether some sort of brigading is going on.
Interesting stuff. Personally, I'd urge people who don't like furry stuff to just block a community and carry on. There's nothing to be gained by obsessing yourself with stuff you don't like.
What action can you take? Your problem is that 99% of the population is repulsed by furry stuff, you'll always get tons of downvotes if your posts end up in the "all" feed. Because it is quick for users. Instead of checking who downvotes furry stuff because they dislike it, threatening ineffective "actions", you should ask lemmy devs for a way to avoid that your community to end up on "all" feed, similar to reddit where sub can opt out of r/all
Edit. I saw this post on the "all" feed that's why I am commenting
That's not exactly my concern. The top users in that list seem to systematically engage in downvoting everything instead of simply blocking the community.
This does not seem to be mere stumbling upon something in All.
I... Really don't understand why people would browse the "all" feed with NSFW filters disabled, it just doesn't seem to be a pleasent experience. There's much worse than a dog man with his dick out that'll be on that feed. Violence, gore, scat, extreme porn, politics and the full range of offensive comments. Or even, depending on who your instance federates with, stuff like loli and bestiality.
People browsing "all" should be willing and ready to blacklist communities that post things that they find objectionable, rather than deciding that the "all" feed should be automatically curated for their preferences.
Would be nice if there was a seperate "NSFW" toggle for the "all" feed, full instance blocks or even specific, blockable NSFW tags.
Tbf, in the current state of lemmy, everything is pretty vanilla with the exception of furry stuff. Once gore will become a thing on lemmy, I am pretty sure it is going to get downvoted as well, likely much more
um no. its not just furry stuff. I have not blocked any furry stuff as its not that bad so far but I have blocked fuckevil, fuckbully, fuckfacist or something akin to that where the evil, bully, facist is what its all about despite the titles that would make you think otherwise. but with really disturbing porn.
It's clear that lemmy still has some major work to do yet on this front. The fact that you have to visit the community first in order to block it seems like quite a flaw. And there is no way, to my knowledge, to deemphasize some content on the front-end without basically purging it completely. Not exactly ideal solutions for those that don't want to be blasted by scat or gore, but also don't want to live exclusively in their subscribed tab.
I think one thing that would help is an off by default. So all federations and all magazines except for some default feed off and you go to enable them as you want with the area always having an allow all and allow button. My hope is that the federation gets to that point at some point. I think the moment is there for this to become one of the massive gamechanges like gpl, linux, wikipedia, etc.
Wow, a perfect example of how people make up statistics from nothing. Maybe the better option is to find a way to reverse block the childish babies who decide to go and downvote everything on furry instances.
That's already a thing, it's called banning them from the instance. Though I can understand why they wouldn't want to start banning people for downvoting alone, it might be seen as extreme, but it also could be seen as necessary since these people are brigading the instance.
I clearly made that up, who has ever done such a real stats? In real world furry is such a niche that 99% is likely an underestimation. What I am trying to say is that you guys will always get downvoted, because most people genuinely don't like furry stuff. The best way for you to avoid it is to stay out of majority of people's sight. Out of "all" feed. You win, average lemmy user wins, all are happy. All subscribers of your community won't anyway join from all. You don't lose anything. Visibility is more of a problem than a benefit for this sub. Ask the developers for an option to opt out of "all", and your problem will be gone
"In real world furry is such a niche that 99% is likely an underestimation"
In the real world, animated furry characters, anthro or not, are among the most popular and beloved and have been for decades. Puss in Boots: The Last Wish is the most recent breakout success amongst the general public. Furry characters are loved by the general population.
Furry stuff is cute. Why would 99% of people dislike it? I'm not gonna join furry communities because I'm not a furry, but I'd probably upvote furry content if it appeared on all and I'd think it would be sad to keep it off there.
To be fair in the context of the main topic here, it looks like all the communities being down voted are porn. Not quite the same as seeing a beloved furry character from a hit movie if they are engaged in lewd behaviour.
But they can always block them and forget about it than go looking specifically for it and down voting it.
Such is censored generally, so they have to go out of their way to see such.
Also don't get why people would have a problem with seeing such unless it was like gore, but I acknowledge that often people do have a problem with such.
Yours is not a common opinion, but that's beside the point.
The issue here is a combination of end users not using the block functionality, and a major flaw in how it's implemented (you have to visit that which you want to block.)
You're never going to change end users' behavior, so the beatings will continue until blocking functionality improves.