this post was submitted on 04 Jul 2024
17 points (94.7% liked)

dailygames

898 readers
61 users here now

Community for daily games like Wordle, Jumblie, Connections etc.

Post your daily games and scores. Discover new games and discuss with others.

Find games

Share your results

It’s useful to wrap your results in a markdown codeblock to preserve the layout. Put three backticks ``` before and after your result to create a codeblock.

πŸŸ¨πŸŸ¨β¬›β¬›β¬›
πŸŸ¨πŸŸ©β¬›β¬›β¬›
πŸŸ©πŸŸ©πŸŸ¨πŸŸ¨β¬›
🟩🟩🟩🟩🟩

Rules

founded 4 months ago
MODERATORS
 

Is there a way to add spoiler tags?

I think I got spoilers to work, let me know.
I did the following:

::: SPOILER SPOILER TEXT
HIDDEN MESSAGE
:::

you are viewing a single comment's thread
view the rest of the comments
[–] aukspot@piefed.social 1 points 4 months ago (1 children)

I'm not sure, I'm just using my browser (Firefox) at piefed.social, the other spoiler tags in these comments are working for me though

[–] Zagorath@aussie.zone 2 points 4 months ago (2 children)

Oh whoops, I just realised your previous comment was a reply to @Emotional_Series7814@kbin.cafe and not @skillissuer@discuss.tchncs.de.

Ok so it looks like Piefed is the name of the platform you're on, a different threadiverse platform from Lemmy or Kbin. Unfortunately some of the more advanced syntax like spoilers are the first things to become incompatible when you cross over between different platforms.

This should work on Lemmy:

TestTest spoiler text

This should work on Kbin, I believe:

::: spoiler Test spoiler text :::

!This is the syntax that worked on Reddit.!< (and tbh I quite like that syntax because it enables inline spoilers, instead of only paragraphs)

From what I can tell, Piefed has similar behaviour to Lemmy. Unfortunately emotional_series is on Kbin which means their spoiler syntax is breaking for you, and for me. Their above comment is particularly bad for me because they didn't even include a paragraph break before starting the ::: spoiler. And it breaks even worse for you because Piefed seems to default to treating the text that Kbin intends to be hidden as the revealed part of the spoiler if they do have the paragraph break. And it also ignored code blocks in order to spoil code.

This is what you should be seeing in the lower comment:

instead of this:

and what emotional_series sees is this:

[–] aukspot@piefed.social 3 points 4 months ago (1 children)

This is incredibly helpful, thank you for taking the time to help! I honestly thought Piefed was Lemmy, I'm still new to the fediverse. I think I should try using an app

[–] Zagorath@aussie.zone 2 points 4 months ago

Yeah the great thing about the fediverse is how interoperative it is. There are differing degrees of compatibility, but to some extent we can talk to each other even between Mastodon (ostensibly a Twitter-like platform) and Lemmy (Reddit-like). You could never imagine Tweeting to reply to a Reddit post.

[–] Emotional_Series7814@kbin.melroy.org 2 points 4 months ago* (last edited 4 months ago) (2 children)

The fact these platforms all play differently is so annoying. First with linking other magazines/communities, now spoilers apparently. Something that looks nice and works on one platform is unreadable/spoils/nonfunctional on another. For what it is worth, all attempted spoilers in your comment that I am replying to now work for me on Kbin. Except the Reddit-style spoilers, which I believe work nowhere on the Fediverse.

[–] Zagorath@aussie.zone 2 points 4 months ago

The reason I included the Reddit one is because I think some Lemmy mobile clients that used to be Reddit clients might still support them. Because really rendering is a matter for the client more than the platform.

[–] MBM@lemmings.world 2 points 4 months ago

As a bonus, a bunch of apps have their own way of doing spoilers. It's a bit of a mess.