Comment on Self host Blorp, your personal Lemmy/PieFed frontend
cecilkorik@lemmy.ca 7 hours agoVery interesting I wonder what happens if I post both trailing and non-trailing options, do they both get canonized into the same format?
piefed.ca – has a trailing slash piefed.ca – does not
Thank you for having me along on this journey. I don’t really know where it’s leading, but maybe it’s about the weird software behaviors we discover on the way.
cecilkorik@piefed.ca 7 hours ago
And posting from piefed, is the result the same?
https://piefed.ca/ -- has a trailing slash
https://piefed.ca -- does not
cecilkorik@lemmy.ca 7 hours ago
Yup, they all have trailing slashes when viewed on Lemmy, and 3/4 have trailing slashes when viewed on piefed. So only piefed actually respects what was originally typed. Lemmy adds a trailing slash when you’re adding the comment, and also adds a trailing slash when reading a comment posted that doesn’t originally have a trailing slash. Intriguing (and slightly annoying).
cecilkorik@piefed.ca 7 hours ago
On a similar but unrelated note, Lemmy also displays the two-hyphens as an em-dash, but unlike the trailing slashes, it does not encode that into the comment, so on piefed you still see the two-hyphens in both comments.
Fun!
DesolateMood@lemmy.zip 7 hours ago
I see two separate dashes in voyager
moseschrute@lemmy.world 7 hours ago
I think that might just be how Lemmy’s default frontend renders markdown. The trailing slash thing happens at the API level. But a quick test shows submitting a comment with two dashes sends back a comment with two dashes.
POST https://lemmy.ml/api/v3/commentImage Image