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!

  • stray@pawb.social
    4·
    6 小时前

    SPOILERS for the 2025 film Weapons.

    Let’s see if this spoilers tag works.

    e: I think this should work for most people??

    Spoilers

    I think my favorite was looking directly into the face of a man mindlessly murdering his husband, and remembering what nice people they both were.

      • stray@pawb.social
        0·
        17 小时前

        I did. The problem is that different apps seem to work differently, and it’s quite frustrating. If I’ve understood my search correctly, spoilers aren’t supported by Lemmy’s backend.

          • stray@pawb.social
            1·
            13 小时前

            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:

            !>! Does this work? !<!<

            Firefox Mobile:

            Sync:

            I don’t know what the rules are to make this shit work.

            • ComfortableRaspberry@feddit.org
              3·
              12 小时前

              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 :/

              • stray@pawb.social
                1·
                6 小时前

                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. ???