this post was submitted on 15 Mar 2025
135 points (96.6% liked)
Asklemmy
46498 readers
1302 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Google Search -> Ecosia, Qwant Browser -> Vivaldi Mail, Calender -> Proton* Drive -> Proton* DNS -> Quad9 Notes -> Joplin VPN -> Proton LLM/AI -> Mistral Translate -> DeepL Maps -> Here We Go Dall-E etc -> Stability Matrix Kindle -> Pocketbook
*Planning to move everything to a NAS with Nextcloud and synch in with Jottacloud as a backup.
I see from the "View source" option that your comment has everything in a neat, line-by-line fashion, though the final markup is decidedly not.
So, a pro-tip I've noticed from my own commenting experience: even if you have a line break, Lemmy (for some stupid reason) won't apply one when rendering; so if you want it to show, you have to use two line breaks, though then there will be an extra half-line or so that you probably never wanted.
For example, don't do
but rather do
Yes, I agree it's rather stupid.
It's the way Markdown works, for reasons, which is what Lemmy uses for its comment syntax.
If you want a regular line
break, you can put two spaces
at the end of a line.
Holy shit I've been using markdown message boards for years and
you just blew my mind
Yeah I know, and I don't like that limitation. Lol. xD
Yeah, it doesn't make a whole lot of sense here. Codeberg uses a Markdown flavor which honors single line breaks and it kind of surprised me how well that is working. Like, if you're used to Markdown, you can put those two spaces and they're just ignored. If you're not used to Markdown, it works like you'd expect.
I guess, the downside is that either each client needs to configure their Markdown renderer to behave like that, or I guess, the server software has to pre-process the Markdown to add in the double-spaces.
That's more of a problem for Lemmy than it is for Codeberg, because there is a number of different clients available.
Jerboa vs. the website do different things since they render Markdown differently. Markdown itself is so spartan that it doesnβt have many things users want or need, so a bunch of incompatible forks get made & everyone just pretends it is all the same when in reality, it often lies on a single toolβs implementation.
Take AsciiDoc with its verse directive or reStructuredText with its line-block directive. Both get you poetry-style newlines on demand & are a part of the spec instead of left to the implementer.
Yeah, that's kind of the advantage and disadvantage of Markdown. It's so simple that alternative implementations can be easily created, which helps with adoption. But because those alternative implementations exist and because there is a need to add more features, those alternative implementations will see custom changes for the format, ultimately making the format less standardized.
I find this pretty bad since everything seems to be compatible until it is too late & it is already adopted. I would like to see more uptake of the alternatives.
Didn't know that Codeberg did that. I'll have to add that to my list of reasons why I love Codeberg. Lol.