Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


NodeBB Setting Change: Make upvotes and downvotes public


  • I support this idea, though I'd argue that it doesn't matter so much "who" is for or against something, just the tally matters IMO, so if it's a positive number than we know at least more people liked it than disliked it, right? That's what matters IMO. Frankly if there's a way to turn off names for likes and dislikes that may be helpful in another way too - it's the "reddit" style, though then that takes away the pride I get for a moment when I see @girish upvoting my comments. 😛 hahaha


  • @d19dotca We almost never downvote here, so I think it's useful because then you get to see if other user, developers, or admins agree with something you're thinking / saying. Specific people all have different expertise so knowing who liked what does have merit, to me at least.


  • I like the current system. It’s a good balance between a little insight into who upvoted while at the same time pivots towards being the ”community voice” by avoiding personal grudges by hiding occasional downvotes. Qualitative responses is best expressed in replies anyway, imo.


  • I'm not in favor of the downvote to start with.

    There's a reason downvote doesn't exist on most social media, because it create antagonism and dissent ( which can quickly become personal) without being actionnable feedback, enriching debate and discussion.

    Upvote/Downvote make sense when you try to make content resurface (like Reddit or Stack Overflow). Which is not the case here.

    Finally, as it was pointed out, downvote is rarely used, so I don't think we'll miss it.

    For these reasons, I'd rather prefer there was only a 'heart', a la Twitter.

    That being said, feel free to downvote me. 🙂


  • Thinking about it, I'm now wondering if some people have actually downvoted apps in App Requests section.


  • @ruihildt yes, that definitely happens.


  • @jdaviescoates Wow, that's really disappointing and unnecessary.

    (BTW, I updated my previous message)


  • @ruihildt I don't think it's that bad really.

    As you said:

    @ruihildt said in NodeBB Setting Change: Make upvotes and downvotes public:

    Upvote/Downvote make sense when you try to make content resurface (like Reddit or Stack Overflow). Which is not the case here.

    But that kinda is the case in the App wishlist category.


  • @jdaviescoates Maybe I'm too naive, but I don't see what would be an argument not to have an app on the store?

    If I'm not interested, then I don't upvote it. I see that section more as a gauge of the number of people interested in it.


  • @ruihildt I don't think I've ever downvoted an app either. But I guess it's more about prioritising.


  • Note that in comparison with typical social media reputation score is a thing on NodeBB. I feel like the voting system is used in a very positive and encouraging way in this community as well, I’m actually inspired to replicate it in other communities.

    On occasion downvotes happen. In my experience it’s usually not when members disagree on taste or favorite apps but when the content is outright spammy, abusive or utterly negative. Then the community reacts and rightfully so.

    I see no issue with the current system at all and I see no point in changing what has been around and worked well for so long.


  • Oh, it did change. Nevermind ¯_(ツ)_/¯


  • Tbh, for me, it's just to make sure if a suggestion I make is more or less likely to make it into master based on who liked / disliked it (the actual developers, app devs, and then users).

  • App Dev

    @Lonk said in NodeBB Setting Change: Make upvotes and downvotes public:

    it's just to make sure if a suggestion I make is more or less likely to make it into master based on who liked / disliked it

    Don't forget that it's not the forum users that decide this, but actually @girish and @nebulon. And that should purely be on what they see value in and can see themselves maintain and support in the future.

  • Staff

    I like the idea of removing downvotes in general. For example, this post also has gone to "-1". I am not sure what I am supposed to make out of that 🙂 It's better people leave a note. It's not like we have 10k different users here, it's still a small manageable community.

    I have disabled downvotes for now and made the upvote public, let's see how it works for some time. We can always revert this change, in case we missed out on what it offers.


  • @girish said in NodeBB Setting Change: Make upvotes and downvotes public:

    I have disabled downvotes for now and made the upvote public, let's see how it works for some time. We can always revert this change, in case we missed out on what it offers.

    I think this is perfect because we're such a small community, I don't see the need for downvotes. 0 means no ones interested. 3 upvotes is when I start to take notice. It also makes it insanely easier to hit the target on mobile for now (which I put a ticket into NodeBB to increase, mobile target ranges and it is fixed in the newest version).


  • @fbartels said in NodeBB Setting Change: Make upvotes and downvotes public:

    Don't forget that it's not the forum users that decide this, but actually @girish and @nebulon. And that should purely be on what they see value in and can see themselves maintain and support in the future.

    That's exactly my point, by being able to see what they like, I have a much better idea of what could make it into master. If a bunch of app devs or consumers like it, I know @girish and @nebulon are at least going to look into it. But if a Feature Suggestion even only has 2 likes, if I can see it's girish and nebulon, then I know it's much more likely going to happen in the future over 5 regular users upvoting. Does that make sense?