If you come across something that doesn’t work pop it here
Markdown in the media bias bot doesn’t work as visibly intended.
Yep, I have this issue too.
Came here to report the new fact-check bot
Any progress being made here? I was really hoping that not being able to view certain communities such as !newbrunswick@lemmy.ca would be considering bad enough of a bug to bring a little development back.
Yup. I’m in the process of ripping out the old markdown processor.
Hey! Good to hear from you. Hope you took some good time for yourself. I appreciate the progress update on the merkdown.
I’ve been flat out on new features. Just finishing up a built in ad blocker ༼ つ ◕_◕ ༽つ
What’s it gonna do? 👀 Hopefully block ads for web pages you’re viewing?
Yup. Even managed to get websites caching and working offline too.
Any way you can block the “sign up for the newsletter” type dialogs that websites like to have? Lol
Already added (☞゚ヮ゚)☞
Code blocks in quotes appear a little funky.
Some line of code
> Extended quote > ``` More code
Further extended quote
I’m not sure if you’re still monitoring this or if I should make new thread.
I just encountered a comment where they included a link with brackets in the url and it didn’t parse for me in Sync. I assumed it needed escape characters , which did make it a working link for me in app, but I got curious and checked the website and the original link worked fine there. Maybe the Lemmy web ui will escape characters in links by default?
Testing embedded gifs
Footnotes are weird? Maybe this post is weird?
https://lemmy.world/comment/8880898
Sync view:
Mobile web view:
Device information
Sync version: v24.03.26-14:56 Sync flavor: googlePlay Ultra user: true View type: Slides Push enabled: false Device: d2q Model: samsung SM-N975U Android: 12
Spoiler formatting was a big one, Lemmy wants to do it like this, I think:
Some paragraph text.
Spoiler Title
Some spoiler elements
Other paragraph text.
EDIT: the main issue being Sync not displaying the spoiler title properly
See also this exchange: https://lemmy.dbzer0.com/comment/9667987
I’d also like to mention that the way it’s done in the community about page for S4L doesn’t seem to work:
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Edit: this is so confusing. It doesn’t work in the about section, but looks fine in my web interface. I don’t even know what to believe!
Furigana (a feature of Japanese text) is supported by Lemmy on the web but doesn’t work in Sync. It’s not a part of core markdown but Lemmy uses a plugin.
Here’s an example post showing how to use it. https://programming.dev/post/530608
Here’s what it should look like:
And here’s Sync:
This in-line animation doesn’t work but when you tap on it there preview is fine
!spoiler spoiler Test Comment
with line breaks!<
with line breaks!<``` Saw this comment in the wild which does not appear correct in Sync. https://discuss.tchncs.de/comment/8334366 In Sync it looks like this: ![](https://lemmy.world/pictrs/image/a660f68f-f78b-41a8-ae15-17a8cd896c3e.jpeg) On Lemmy via browser, it looks like this: ![](https://lemmy.world/pictrs/image/ed917b91-cdf6-401a-92e0-01462790b8ce.jpeg)
+1 for this, would be nice to have proper lemmy style spoilers.
Posts are not being marked as read, unless the comments are opened.
Several of the Wikipedia links in the post below contain parentheses in the URL. They work in the web front-end but not in Sync.
Funny stuff is happening with the spoilers in this comment, they aren’t rendering as spoilers on the first two but tapping the actual spoilers removes the broken spoiler characters around the first two lines? Really strange: https://lemmy.world/comment/10822445
The bullet points in my comment here render correctly in the official Lemmy frontend, but not in Sync: https://lemmy.world/comment/6271596
I think a way to make them work is to add two spaces after each line. Here’s a test…
- Line one
- Line two
- Line three
Hopefully that works.
It did :-)
That’s a placebo and it’s not doing anything. Bulleted lists never need two spaces at the end of each line. You only use two spaces at the end of line that are not in bulleted or numbered lists.
The bug is that Sync requires a blank line before you start the bulleted list. The Lemmy website doesn’t require that.
Here is your comment with no spaces at the end of each line:
spaces after each line. Here’s a test…
- Line one
- Line two
- Line three
See? It still works fine.
Now here’s an example of what two spaces do.
The first sentence below has a new line after each word but no spaces. The second sentence has two spaces and a new line after each word. The spaces force a line break to be rendered.
This Is Not A List
This
Is
Not
A
ListSource of the above:
This Is Not A List This Is Not A List
This feature of markdown was implemented to prevent text from emails and such from wrapping in funny ways when pasted into a comment (or whatever). Old emails often force line breaks after 80 columns of text and it looks goofy when viewed in a modern web browser if those line breaks are kept, so they are ignored. To preserve the line breaks, you add two spaces at the end of each line. That or you might prefer to write paragraphs with a hard wrap at some column, but other people shouldn’t have to suffer that.
Adding the two spaces to lines in a bulleted list does nothing useful, but it also doesn’t break it, so of course it works.
Superscript was reported as ^not working^
I installed Sync just to test this. To me, that’s displaying with “not” superscript but not “working”. On web, it just doesn’t work at all (this is due to the markdown library lemmy-ui uses not allowing spaces).
Suspect ~subscript will~ also not work. Curious about
struck-out text.Okay subscript didn’t work on lemmy-ui or Sync. Struck out is fine.
How about single-word subscript? edit: yup, works in lemmy-ui, not in Sync.
Lemmy-ui uses markdown-it-sup, so I think superscript should work on a single word like this: superscript . It won’t work if there is a space in the superscript text: ^this wont work^ . Each word must be enclosed with superscript tags: this should work
deleted by creator