@iorale - eviltoast
  • 0 Posts
  • 7 Comments
Joined 1 year ago
Cake day: July 21st, 2023
  • iorale@lemmynsfw.comtoLemmy NSFW@lemmynsfw.com•An update on our community regarding downvotesEnglish
    3·
    1 year ago

    If you create a community for X, Y and Z, users who like X, Y and Z will join, from there the ones who are majority will favor Y because that’s what they like, if they dislike Z then it will get buried under Y and X. That’s why it’s encouraged to creat a community for X, one for Y and one for Z. If someone from Y posts on Z because they think “it also fits in Z”, then it might get liked or disliked, either accept that or don’t post outside Y.

    Now if it’s a federated place, users that like A, B or C, but that absolutely dislike X, Y or Z will make it known one way or another when that content reaches them (not IF, only WHEN), there’s no way around that, either deal with it or consider moving that community that deserves so much protection to a closed space.

  • iorale@lemmynsfw.comtoLemmy NSFW@lemmynsfw.com•An update on our community regarding downvotesEnglish
    13·
    1 year ago

    Protect them from what? Themselves? Their own ego?

    This is a terrible change and should have been discussed with the people who has an account inside the instance because this impacts every user, not just the few posters.

    If their content is getting downvoted because people don’t like it, they either change it, move somewhere else or suck it up, that’s how the Internet works. Now we are just another fucking Beehaw.

    This won’t magically make everyone accept their content, this will just open the door to people leaving negative comments and won’t really stop other instances from downvoting them (this only impacts us).

    Also now we can’t downvote federated posts to protect a few posters whose ego got hurt, good job.