9
Is there a way to fix Kbin's formatting not working on Lemmy? this is in the mag bio. (see pic attached)
(media.kbin.social)
this post was submitted on 03 Aug 2023
9 points (100.0% liked)
/kbin meta
639 readers
1 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mardown has several valid different ways to define itself, both ways listed are valid ways to indicate italics.
You would expect Lemmy and KBin to fix on one way but display both. That is a bug in the lemmy renderer.
For example asterisk Is a special character, when used in JSON you have to escape special characters with a backslash. A single backslash is also a special character. What your seeing is double escaping, (e.g. something is repeating it on code)
A quick look through the KBin code showed it using json_encode which is the JSON conversion library built into PHP. A quick google shows double calling the library on a string won't do that and I can't see KBin doing anything obviously wrong.
Lemmy has had some really weird bugs, an expectation that Lemmy hadn't escaped a block of code at a set point so they escape it and KBin is escaped would seem the most likely candidate.
The easiest test would be seeing how it renders on an alternate KBin instance, you would expect the extra characters to show up there, if they don't its probably Lemmy
So, not op, but I just tested this. The issue OP is seeing doesn't occur on karab.in and fedia.io the same way it does on lemmy, but I'm noticing that there IS an issue with how the markdown is federated between kbin instances.
This is, verbatim, what I get on both karab.in and fedia.io:
Notice how there's no new lines / paragraphs and that some of the
>(but not all of them) got changed into>and the receiving instance didn't change them back.For reference, this is how it should be:
So clearly there is an issue with kbin itself here, whether or not lemmy has an issue too.
@euphoria
That kind of character conversation is exactly what you would see if escaping wasn't being done properly.
Definitely a bug in KBin there