Like the title says, if you want to upvote something on KBin, you should use the Boost link, not the upvote button (Why? Don’t know…)
The upvote button doesn’t seem to do much, but Boost accomplishes what Reddit’s upvote did. So if you’re looking to encourage a post, use the Boost link.
@HamSwagwich
This is a result of the original design. Kbin, up until just before the peak traffic hit, was using boosts as upvotes and favorites/likes were just below the post/thread (where boost sits now). Lemmy does it the way it is now (likes = upvotes) so Ernest changed it to match Lemmy behavior. But just as he changed it, he hadn’t changed the calculation for reputation to match when the server nearly melted down and he has to spend all his time just trying to keep the site alive by himself.
Respect
I see you’re on a different Kbin instance. Was this intended to be a threaded reply, out of curiosity? Because it shows up as a top-level comment on the post for me.
He using an optional feature that lets you auto populate your reply box with the OPs username.
Yes, but my bigger point is that it’s not threaded as a reply to one of that user’s comments.
Edit: Oops, nevermind. I saw their comments elsewhere down here but didn’t realize they were OP. Just one of the interface things on Kbin that needs improvement.
Edit 2: I need to figure out how to do strikethrough text on here
You can do strikethrough text
~~like this~~I’m viewing this from KBin and I don’t see strikethrough.
That’s because I put that in a code block with backticks (`), here’s what it looks like normally
testingAs a desktop kbin user, there’s no strikethrough. Unsure as to why, if kbin is markdown. Strikethrough is considered advanced markdown formatting so I’m guessing kbin didn’t include it. Now I’m curious to see how much common markdown is visible on kbin’s desktop platform.
Guide for those unfamiliar with markdown, so you can see what I’m doing. ✔ means I can see it on desktop kbin, ❌ means it remains unformatted (formatting characters remain).
Horizontal rule ✔
Testing MD (headings)
bullet points ✔
bold ✔
emphasis ✔
~~strikethrough~~ ❌
escaping *characters* ✔
code (inline)✔I’m using kbin.social on desktop and it shows up fine for me, not sure what’s going on on your instance
Oddly enough all of that looks perfectly fine on kbin mobile, even the strike through, I’ll have a look at desktop later and if it’s doesn’t work
i on kbin.social see the strikethrough fine
How weird. When I do that, it doesn’t seem to work.
testtest successfultesting your assertiontestEdit: doesn’t seem to render properly on jerboa lemmy client
like this?