My first time encountering it, just scrolled to it like three times to check, anyone else having this issue?

Edit: ope, looks like I can’t edit the title lol.

    • davel [he/him]@lemmy.mlEnglish
      1·
      8 months ago

      Do you know what it is about that post that causes the crash? The Sync devs might like to know.

      Is it the image: https://lemmy.ml/pictrs/image/b733f506-7837-415d-a761-e3bea08c0594.png

      Or is it some specific thing in the body of the post:

      Heffalump Hackerz - Woozle Wizards - NIST Quantum Cryptography  

Enjoy some humor regarding 'quantum hysteria' and 'quantum scaremongering'.  

Quick expert critique of quantum computers and quantum cryptography:  
On the Heffalump Threat (short single-page essay)  
[https://www.cs.auckland.ac.nz/\~pgut001/pubs/heffalump\_crypto.pdf](https://www.cs.auckland.ac.nz/~pgut001/pubs/heffalump_crypto.pdf)  

Short 3-minute video (aptly portrays quantum hysteria)  
[https://youtu.be/CLnADKgurvc](https://youtu.be/CLnADKgurvc)  

[\#NIST](https://neon.nightbulb.net?t=nist) [#cryptography](https://neon.nightbulb.net?t=cryptography) [#cryptology](https://neon.nightbulb.net?t=cryptology) [#encryption](https://neon.nightbulb.net?t=encryption) [#heffalump](https://neon.nightbulb.net?t=heffalump) [#woozle](https://neon.nightbulb.net?t=woozle) [#quantumcomputers](https://neon.nightbulb.net?t=quantumcomputers) [#quantumcryptography](https://neon.nightbulb.net?t=quantumcryptography) [#quantum](https://neon.nightbulb.net?t=quantum) [#bigtech](https://neon.nightbulb.net?t=bigtech)  

[@[email protected]](https://lemmy.ml/c/programmerhumor)
      • m-p{3}@lemmy.caEnglish
        1·
        8 months ago

        I don’t think it’s either, previewing a new post using the same values doesn’t crash S4L, I think it has more to do with OP’s instance being based on snac2 (first time I encountered this ActivityPub-compatible server) and returning something S4L doesn’t normally expect.

        • davel [he/him]@lemmy.mlEnglish
          2·
          8 months ago

          If so then the workaround for Sync users would perhaps be to block the neon.nightbulb.net instance, and for the long term, file a bug with the Sync folks.