Edit from 2022: Consider checking the Forum user manual if you're not sure if something you're looking for might already be possible.
Hello, Forum!
This is Aaron and JP of the EA Forum team.
We spend a lot of time working on the Forum, and we’d like to hear your ideas for making it better. These can be new features or other kinds of requests.
Even if you don’t have suggestions of your own, consider upvoting ideas you like from the comments. That will have nonzero influence on the features we prioritize (though we also take many other factors into account).
If you’d rather make a suggestion privately, get in touch with us through this page.
Edit April 2022: This thread is still very live as you can see by the continual influx of suggestions. We have now synced our asana project with our public Github issues list, so you can see our recorded tasks there.[1] I'd still recommend suggesting features here so that other users can see and discuss them. — JP
- ^
Note: there's a delay between when we write tasks down and when they get triaged into a state that gets synced with Github.
Having recently wrote a post that got a lot of silent downvotes, I've been thinking more about the general role of silent downvotes and how we could mitigate their downsides. (See some earlier discussion here.)
Silent downvotes are important for content ranking/visibility and providing a rough high-level signal of what the Forum community values/disvalues, but they have some pretty important disadvantages, especially when they represent a preponderance of a post's karma:
There's already a feature that allows authors to hide comment karma on selected posts. I'm not sure entirely how it works, but I think it means that if the author chooses, nobody can see karma scores on that post?
That might be what some authors want, and is maybe preferable to seeing lots of silent downvotes, but at least for me it seems way worse than seeing downvotes and knowing why. I want to be able to make that update, but it's often hard to do that based on silent downvotes alone.
It would be great to get more information from people about their downvotes, but any system for doing that needs to be super quick, simple, and easy – if a silent downvoter had time/energy/interest in providing an in-depth explanation of their downvote they'd just write a comment. But I think getting even a couple of bits more information from silent downvoters would be super valuable to authors.
The solution I have in mind for this right now is to provide a little optional pop-up next to the post karma total with a few common reasons for downvoting, plus an "Other" option (with or without the option to specify). You'd probably want to iterate a few times on the options, but my first pass would be:
Then show the results to the author somehow (e.g. on the analytics tab).
You could also do this for upvotes; this might be nice and would reduce asymmetry with downvotes, but I'm not too concerned about it. You could also extend it to comment downvotes, though this seems lower priority to me.
I'm guessing a new feature like this would be a fairly significant lift code-wise, but I tentatively think it would be worth it – right now I see this as a fairly big problem with quality of discourse and community on the Forum.
+1