Several people in the community have expressed frustration in regards to the fact that any post that fits the community it’s posted to but is slightly out of the normal post type like, for example, being more hardcore rather than softcore, get’s a lot of downvotes by people who simply don’t like that particular post.
We have also had complaints that particular types of posts as a whole get more downvotes even if they are in the appropriate community and are the normal type of post for a community. This especially appears to be happening to male content.
Additionally we are seeing posts with more downvotes than a community has subscribers, meaning people are downvoting content they don’t even want to see in the first place.
We understand some may not like some content of a particular post or community, but downvoting posts discourages these posters who are actually passionate/interested in the topic of the community from posting again. Additionally, when posts are downvoted like that it can bury them in our instance and especially in other instances, preventing them from being viewed by others almost at all.
After some discussion amongst the moderators and admins,because of the reasons above, we’ve decided to disable downvotes at least for the time being.
What do I do if I dislike a post?
-
We recommend those who would normally downvote a post they don’t like just, instead, block the user who created the post, or, if the community is a topic you dislike, block the community. That way, you no longer see those posts, but don’t effect those posts’ visibility to other members of the community and instance.
-
Additionally, you can view your “Subscribed” feed instead of “Local” so that you only see posts from the communities you are subscribed to.
What do I do if a post doesn’t fit the community it’s posted in or is spam?
- Please report the post, either the mods of the community or an instance admin will remove the post if necessary, as soon as possible. We have admins and mods online almost around the clock, so these types of posts should be removed quickly.
Potential future post filtering on lemmy:
- In the future it appears that lemmy may implement a tagging system similar to flairs on reddit. This request has piqued the interest of the lemmy devs, so keep an eye out sometime in the (maybe not so near) future for the implementation of that feature.
As @[email protected] has said in the comments:
Downvotes should be used for posts you don’t like in your area of interest, and not for niche communities you don’t like.
When the RFC mentioned in the post is developed, we will be able to have a more refined home page, this way we can enable downvotes.
But for now, please block users/communities as it supposed to be.
Please put any comments questions and concerns in the comments below, we are of course always open to community thoughts and feedback, and want to work with you to keep this instance an enjoyable and entertaining place to post and browse.
I appreciate your verbalization of the issue at hand. I like to think of the vote system more along the lines of appropriateness upvote=appropriate/good, no vote=appropriate/neutral or not good, and downvote=inappropriate/broken/rule breaking.
Not interacting with a post has about as much of an effect on the non-chronological sorting as a downvote does so essentially you’re just going out of your way to make someone feel bad if it’s an appropriate fit for the community and you use it as an “Ew” button. This behavior becomes especially problematic when it comes to non-promotional OC.
It’s not perfect, but I think removing the downvotes for a brief stint will have a pretty good impact on training user behavior to help facilitate growth until this place is at a point where there is enough core functionality to allow for better solutions.
This is a Lemmy implementation problem - you need to vote to remove a post from your feed if you’re hiding seen posts. I’d much rather ignore posts that fit but aren’t for me, but there’s no other way to mark them read.
I actually wasn’t aware that the mark as read implementation required voting to register as I’ve never had it enabled. That does change my perspective quite a bit of true. I can see that being okay for general news or tech content, but when you add sex, which is largely going to come down to personal preferences, to that it certainly creates problems. Honestly a lot of the problems people are talking about in this thread come down to implementation problems in the end, but we just need to do the best we can with what we have for the time being.
A workaround for you: upvote twice (ie upvote and remove the upvote) to get the post marked as read.
Ooh, thanks, I’ll try that!