Right now Lemmy is unusable for writing code that contains less than/greater than signs because Lemmy’s sanitizer treats that as potentially malicious HTML code.
Here’s an example:
if(x < y)
{
/* ... */
}
The listing becomes littered with < gibberish.
You must log in or register to comment.
What&rsquo;re you talking about?
It actually looks perfectly fine on Sync for Lemmy so I assume this is only a front-end problem. There are alternative front-ends that you could try.
This is what it looks in the web UI:
This is how it looks on Sync, seems like he’s a front end issue.
There are alternative front-ends that you could try.
The 3 frontends for browser / PC that I know (default, mlmym and alexandrite) have this problem. Do you know of any other one that works?
Thanks!
Yeah I think this was hastily done to prevent the XSS injection attacks that were happening IIRC. They implemented encoding for content, but looks like they never got around to fully decoding it.
Issue could’ve been avoided by just restricting the encoding to when the user types content in (and before database insertion), and decoding when showing the content in the UI.
