- cross-posted to:
- videos@kbin.social
- cross-posted to:
- videos@kbin.social
yeah I know you, you’re a bunch of queer fucks just like me
this video has some big twists that I really want to talk about but I don’t want to spoil it for you guys
yeah I know you, you’re a bunch of queer fucks just like me
this video has some big twists that I really want to talk about but I don’t want to spoil it for you guys
You did the spoilers wrong lol its uhhh >!!< so >! Spoiler !< >!spoiler!<
I just used the spoiler button in the lemmy interface. I don’t think there is a standard way of formatting spoilers in markdown?
That is how it works on Reddit. Lemmy has its own entirely incompatible spoiler tag system which works like this:
::: spoiler Text next to the arrow Text inside the spoiler which can be multiple lines and can contain *formatting* :::
Which produces this:
Text next to the arrow
Text inside the spoiler
which can be multiple lines and can contain formatting
Reddit style spoilers that look like >!this!< don’t work on desktop or, as far as I know, any mobile app besides Sync.
Oh my gosh this is insanely helpful, thank you. Yes Im on Sync and your message looks completely not spoilered except for the last bit. So thats cool. My spoilers are incompatible with the spoilers everyone else is using?
Correct.
What’s more, Sync somehow manages to mess up the formatting of Lemmy style spoilers despite not rendering them. The correct sequence for a spoiler is a triple colon at the beginning and end, akin to the triple backtick for a code block. If you view a comment formatted like that in Sync, it will for some inexplicable reason convert the triple colon into >! … !<, even inside a code block.
Here’s how my comment looks on Jerboa:
Here’s how it looks on web (lemmy.blahaj.zone):
And here’s how the exact same comment looks on Sync:
I do not know what the Sync devs are thinking.
Bruh. Thanks for letting me know, I otherwise would have had no idea.