Consistency
As you may know, a message written in one Reddit client doesn’t display the same in another. Here’s an example:
Example
```
First line
Second line
```
reddit.com and the official app both render this correctly:
First line
Second line
old.reddit.com, however, renders everything on one line:
First line Second line
They also differ in how they render subscripts with parentheses (a^(\(b\))
), nested subscripts (a^b^c
), and code blocks and lists that immediately follow text.
Lemmy doesn’t have these issues, since its Markdown specification is clearly defined.
Images
On Reddit, if you want to add images to a text post, you have to use the Fancy Pants editor on reddit.com. If you attempt to edit such a post on the official app, a third-party app, old.reddit.com or the mobile site, these images simply turn into links. Additionally, you can’t attach images in comments.
Lemmy lets you attach images from anywhere, including comments.
Source | Rendered |
---|---|
![Lemmy logo](https://join-lemmy.org/static/assets/images/lemmy.svg) |
Multi-line spoilers
Lemmy lets you clean up your post using spoilers:
Source
::: spoiler Heading
Content
:::
Rendered
Heading
Content
Subscript text
Source | Rendered |
---|---|
H~2~O |
H2O |
Well, this is a good bug report for jerboa! Lots of rendering not working
Yep, spoilers are a big one - but it’s a known issue
What is still missing for me is the support for some html tags, such as
<sup>
and<sub>
that are very useful for making a whole sentence appear very small. with the current options you have to~write~ ~each~ ~word~ ~like~ ~this~
or it won’t work:~hello everybody~
: ~hello everybody~~hello~ ~everybody~
hello everybodyalso, in jerboa this is not recognized. But we’ll arrive everywhere, it’s just a matter of time :D
Support for syntax highlighting would also be nice, though Reddit doesn’t have that either:
Source
```c++ int main() { // comment } ```
Rendered
int main() { // comment }
I think that’s it. Its Markdown support is pretty fleshed out otherwise
Jerboa doesn’t seem to render spoiler tags or subscripts. Anyway, here’s an image in a comment:
It’s actually an SVG, which is pretty awesome.
This is a reported bug on github, so a fix will happen for sure. While Markdown is awesome and perfect for browsers, incompatible implementations (esp. when using extensions as Lemmy does, e.g. subscript) are often a problem on non-web based platforms, like Android. If Jerboa was an electron app, it would probably be an easier fix than it is; Jerboa is written in Java and there are less and probably less extensive Markdown parsers in that ecosystem.