Whoa! What a fucking head bender of a movie this was. It sucks you in right from the beginning and just gets more intense as it goes a long.
It does leave a lot of questions unanswered but it sure is worth the ride!
Whoa! What a fucking head bender of a movie this was. It sucks you in right from the beginning and just gets more intense as it goes a long.
It does leave a lot of questions unanswered but it sure is worth the ride!
The triple colons don’t work for me, so whenever people use those it just shows the contents directly. Whereas >!spoiler!< shows up as:
An idea to test:
Firefox Mobile:
Sync:
I don’t know what the rules are to make this shit work.
Interesting! So now I was curious and had to look it up. Here’s the GitHub issue. It seems they can’t agree on a default for inline spoilers (like from your ff screenshot) and now there are a ton of different options with limited support.
But it also reads like the drop-down spoiler with the ::: is the default for Lemmy in general and the issue with these come from your app/frontend. Here’s also a post on Lemmy about this issue from 2 years ago. Seems things haven’t changed since then :/
I made another edit to my original comment attempting to use that syntax, and it actually does work on Sync (although it looks a little weird), but it doesn’t work on Voyager or the mobile site. Curious how it looks on your end and what the problem is with it.
e: Now it’s working on all three even though I didn’t change anything. ???