This was a comment I made on a “sink” post the mods deleted, and I think it’s an issue that needs addressing, so I’m pasting it here. The comment I replied to said something like “Superscript and spoilers have always worked fine in Sync”.


Ironically, that isn’t valid Lemmy markdown. Sync should be supporting Lemmy markdown, not Reddit markdown. Here’s what your comment looks like on the website:

This issuperscript and you can also dosubscript.

Source:

This is^superscript^ and you can also do~subscript~.

Here’s what it should look like:

Instead, you get this:

Personally I don’t like Lemmy’s syntax for spoilers, but Sync should still support it!

hidden or nsfw stuff

a bunch of spoilers here

Source:

::: spoiler hidden or nsfw stuff
a bunch of spoilers here
:::

I’m surprised that actually even works in Sync. It didn’t used to. However, Sync doesn’t show my code block accurately, which is funny as fuck! No app should be editing my code block. Sync is replacing my text with reddit markdown in order for it to display properly. And even when I put that markdown in a code block, it still converts it to reddit style! It also strips out the warning text!

Here is what I actually typed:

And here’s what Sync shows:

What a lazy ass way of doing it. It removes an important feature: the warning text, and won’t even let me show Sync users how to do a proper spoiler!

Oh, WTF. Sync butchered my comment when editing it! I had to fix it back on desktop.

Sync is not fine. It’s full of bugs that the dev is ignoring.

  • @aeharding
    link
    English
    1210 months ago

    Hi, Voyager dev here. Other than spoilers/horizontal rules, please let me know what shortcomings you encounter. I can only fix what issues I know about. Voyager is open source and bugs are tracked here: https://github.com/aeharding/voyager cheers!

    • @[email protected]
      link
      fedilink
      English
      110 months ago

      I’m getting a hostname mismatch in hermit when I browse the https://vger.app/ domain for the webapp. Firefox also fails to load the website due to the HSTS site policy. Did something expire or break?