New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a Full
vote display mode? And what should be the default?
#1400
Comments
Yeah I agree with the default change. But some users do like seeing the upvotes near the arrows. Even tho, it is more visual clutter. And we can add this option easily since all the stuff is still there for it. So the question is then, do make that Full and remove the Score + downvotes (Do users even want this option)? Or do we add ScoreDownvotes option to the backend for this? |
I actually did remove the score as a function param to post and comment footer/action bars. Now it only injects your
I think the more options the better, and that one is already done, so there's no reason to remove it. I'll just change the name to And I'll add a |
- Also making ScoreAndUpvotePercentage the new default, until these get added in the back-end. - Context #1400
Pre-Flight checklist
Describe The Feature Request Below
I have a PR to add these vote display modes to the lemmy back-end.
But we have two unresolved questions:
Full
mode alongsideScore+Downvote
?For 1, I don't think its necessary, mainly because I'm trying to avoid this mess: .
I removed all this distracting extra unecessary info, and put everything in the node header bar. But should it also show the upvotes alongside score? IE
score, upvotes, downvotes, time
. IMO that's too much info, and it isn't necessary.For 2, I think we should switch the default to
Score+UpvotePct
. It looks the cleanest, and seems to be what most lemmy front-ends are using now.For reference, here's what these modes look like in jerboa (without full)
Score + Downvote (the current default):
Score and Upvote Pct (I'd like this to be the new default):
Upvote pct:
Upvote pct in list view:
Hide all:
cc @MV-GH
The text was updated successfully, but these errors were encountered: