/kbin meta

5 readers

2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

Issue with sort by hot (kbin.social)

submitted 9 months ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

This has been an issue since the beginning of Kbin tmk, but when you make a post, it won't appear under sort by hot unless it has an upvote. This means that if someone forgets to upvote their own post, it just won't appear on the default sort. There are plenty of posts I've missed because of this.

Any idea when something like this might be changed?

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 9 months ago

You might try "new"..."hot is specifically for upvoted content.

[–] [email protected] 3 points 9 months ago (1 children)

how can it be hot if it has zero upvotes? seems pretty not-hot to me

[–] [email protected] 5 points 9 months ago (2 children)

Given that we're so small at the moment, why should a post need an upvote to be at all visible on the default sort? It can the only post of the past two weeks, but if there's no upvote, it doesn't get seen. It's very impractical.

And even if we go with this logic, why should the criterion for a post being seen be whether OP remembers to upvote their own post? It doesn't make sense. If you think that posts should only be seen if someone opts to go through new and give it an upvote (because otherwise it's not a "hot" post), OP shouldn't be able to do that.

Right now, we have a system where a major factor in post visibility is, "Did OP remember to click the upvote button?" It's just not beneficial.

[–] [email protected] 3 points 9 months ago

The "sort by hot" algorithm was probably designed with a larger user base in mind, but I agree with you. For small communities in particular (and the vast majority of Fediverse communities are still tiny) I think even posts with no upvotes (ie no self-upvotes) should be included in the "sort by hot" view. For larger communities, where the threshold for "new" and "hot" may be set higher, so it doesn't matter so much. (I don't know what the algorithm is, but it might be something like 'hot is defined as getting a minimum of X votes, where X scales with the size or activity intensity of the community'.)

[–] [email protected] 2 points 9 months ago (1 children)

i agree, i think your argument is 'why arent my own posts automatically liked by me'

call me a pedant but it hurts me to hear a category labeled hot, that has not had literally any user related activity. those 2 things are incompatible. just swap hot for new and call it day

hot to me is an 'activity over time' metric, and zero doesnt play nice

[–] [email protected] 1 points 9 months ago

Yeah, having posts automatically upvoted by OP would be great. I think that Lemmy automatically starts with an upvote count of 1 regardless of OP's vote, so I think Kbin should do the same. I get that Hot is meant to factor in activity and time, but it just feels super off for the only post in the past month to not appear. Surely a post that was made an hour ago is hotter than a post was made weeks back.

[–] [email protected] 3 points 9 months ago

I think it would be great if we could change the default sort. Would love to sort by new by default.

If there's not already a functionality like that hidden somewhere (checked in both settings menus), I'll put it on my list of stuff I want to implement via userscripts.