this post was submitted on 30 Jul 2023
137 points (90.5% liked)

Technology

61366 readers
4484 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

Dear sweet Oghma. We can't even get rid of it on TTRPGs.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 2 years ago* (last edited 2 years ago) (2 children)

&

HTML escape sequence for &. Does this always happen when embedding articles on Lemmy?

Edit: I wanted to write a single ampersand of course, so it’s definitely Lemmy’s fault. Testing some other characters in in-line code: &lt; > [ ] { } | ~ ^ # outside: < > [ ] { } | ~ ^ # &

Edit: so "<" and "&" in code are affected; also I see the comment like this when editing:

Testing some other characters in in-line code: `&lt;` `>` `[` `]` `{` `}` `|` `~` `^` `#` outside: &lt; > [ ] { } | ~ ^ # &amp;

Someone likely implemented crude input sanitation and did not account for everything. I would prefer a closer-to-WYSIWYG editor where the user never sees escape sequences.

[–] FlyingSquid 4 points 2 years ago (1 children)

I don't know. I tried to edit it but it wouldn't let me.

[–] [email protected] 3 points 2 years ago

As things stand now, it would likely not help until the issue is addressed.

[–] [email protected] 4 points 2 years ago* (last edited 2 years ago)

There's a github issue about this if you want to add anything to it, this separate issue also has some details about the sanitation. The issue seems to have been introduced in v0.18.3.