This is what made YouTube rabbit holes fun a few years ago. Now we’re all in our own echo chambers.
The easiest to grasp at a glance is Upvotes/Downvotes
.
Though I understand how Score + Upvote%
would be useful, percentages are impactful when there’s more than 100 reactions (which is uncommon).
I love this being a reply instead of an edit, ha.
Thanks for laying out what calculations would be needed, and why it may be a little harder to parse for a layperson.
thought about it, too!
(and… not sure if it’s Jerboa, but the image appears emoji-sized to me. a bite-sized comic, hehe)
that toast must really be evil…
Agreed. It’s a deal breaker.
It takes out of the equation how many people actually interacted with it at first glance.
Edit: The 10% downvote is the most reasonable of the bunch. Please let it be configurable.
showing all votes was my main reason to use jerboa over the others. it’d be preferable if it were a toggle.
thanks! I didn’t know it was a bug; i liked it. could it become a feature? it’s nice to reach the end of the feed.
This downvote proposal is good, but some instances don’t have them enabled.
Just the option to hide post, without necessarily interacting with it, would be great.
e.g.: On the options that pop up from the three dots, to have ‘Hide’ ‘Block’ and ‘Report’
thanks, bot. i wouldn’t know otherwise that this post on c/selfhosted is about #selfhosted
Oh, i get it! Yeah, 30% is a considerable percentage.
Where I work (text-based customer support), a few weeks ago I stumbled upon a spreadsheet analysing that they could “save” 25% in wages by implementing GPT-4.
It may still be mostly humans on the line, but 1 out 4 of us may get the boot.
I don’t think it’s perceived as good? (curious, why would it be?) Just that it’s disingenuous to market it as AI. Everyone and their mother now has “”“AI”“” 🤷♂️
I’ve never not had this issue while writing a comment since I first downloaded it, back to v0.0.35 around 2 months ago. Hopefully it’ll be addressed soon.
It’s quite frustrating, but I ended up being used to work around it (mainly tapping multiple times to the end of the comment). Feels like whacking an old TV to make it work.
Not constructive in the least, but I get your frustration of it crashing constantly. You could try designing a better app for a change.
If not, submit an issue on GitHub; though I’m sure it’s being worked on. What version have you downloaded?
isn’t this a good change though?