Is there a way to fix Kbin's formatting not working on Lemmy? this is in the mag bio. (see pic attached)

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 jsonencode 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

7 comments

This looks like a Lemmy issue, not a /kbin one. Perhaps find a Lemmy development community somewhere to ask.
- i asked there as well, in my other comment i showed their answer
Looks like basic markdown syntax to me. Does Lemmy maybe not use markdown formatting in that area of the site?
- i found out from lemmy that it appears they escape everything that comes from kbin like so:
  
  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 jsonencode 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