this post was submitted on 25 Jun 2023
0 points (NaN% liked)

/kbin meta

200 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
 

I viewed my own comment on both my profile and in the original context of the post I commented on. The text enclosed by two tildes previously appeared as striked through, as you would usually get in Markdown when enclosing text with two tildes. But now it doesn’t appear to be striked through, it just shows two tildes enclosing the text. I’m not sure why this is happening. It appears like this both on kbin.cafe and kbin.social.

It’s also relevant that this very post has an issue. When you click on it to view it, the link appears correctly. When you just see its preview in m/kbinMeta, the link does not appear as a link but as the raw text you use to set up links with the square brackets and parentheses.

you are viewing a single comment's thread
view the rest of the comments
[–] Elevator7009@kbin.cafe 0 points 1 year ago (1 children)

Hey thank you! I was thinking of creating an issue myself but frankly did not want to make an account for it… maybe I should just suck it up, not be lazy, and make the account

[–] cjerrington@kbin.social 1 points 1 year ago

you could for sure. If you're not using a git service for other projects I can see the hesitation of creating an account just for a single issue. But then again, Codeberg is a great alternative to GitHub. Either way I do think some minor improvements could be made.