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.

      • CrayonRosary@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        4 months ago

        He’s… alive?

        I wonder when this supposed “next release” is going to be and how many other major bugs it will fix. He hasn’t replied to any of the other crash reports over the past 4 months.

        And you still can’t edit titles for crying out loud.

        • Ljdawson (Sync dev)@lemmy.worldM
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          4 months ago

          It’s just awaiting Googles go ahead.

          The next release is going to be a pretty big one but in terms of major bug fixes did you have anything specific bugging you?

          Editing titles has been added too.

          • CrayonRosary@lemmy.world
            link
            fedilink
            English
            arrow-up
            5
            arrow-down
            1
            ·
            4 months ago

            Yes, not using Lemmy’s markdown for spoilers, superscript, and subscript. Sync is still using reddit’s version of these things and even going so far as to change the Lemmy spoiler syntax into reddit style after editing a comment. Even inside of code blocks, preventing me from showing other users how to do a proper Lemmy spoiler.

            I don’t know what else to mention because all of the issues in github remain open and unacknowledged. Like the crash when trying switch users with “hide usernames” turned on.

            You can’t go away for 4 months, fix a bunch of things in secret, and expect users to know what still needs fixing.

            • Ljdawson (Sync dev)@lemmy.worldM
              link
              fedilink
              English
              arrow-up
              2
              ·
              4 months ago

              I’m intending to replace the markdown processor completely. If you have any other examples of incorrect markdown please let me know.

              That specific crash was patched today and the issue was already closed.

              I’m just trying to get a feel of what needs doing first and then get back to closing issues on Github.

          • can@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 months ago

            Breaking of SwiftKey’s autocorrect and gesture typing in titles. Major for me. Also spoiler markdown fix please.

    • bingbong@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      7
      ·
      4 months ago

      Lmfao I think it’s because someone posted what causes the crash for them in the comments. Every time I open this post and scroll to it, sync crashes

  • Death_Equity@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    4 months ago

    Yeah, there is a post from a few hours ago that is doing it.

    Edit: Now something in these comments is crashing Sync.

  • 69420@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    4 months ago

    Same. It’s only in my"Subscribed" feed. So far it hasn’t popped up in the “Everything” feed.

  • Shadow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 months ago

    Yes, I don’t know which post it is but I’ve been crashing all morning.

      • davel [he/him]@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 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.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          4 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.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 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.

    • WeirdAlex03
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 months ago

      Comparing against the web, I think it’s this one: https://lemmy.zip/post/10906124 (original source https://neon.nightbulb.net/firefly/p/1709468335.002251)

      Sync can handle posts from Mastodon well enough, but apparently not so much other AP-based platforms. This one came in from a snac-based instance apparently breaks something


      Device information

      Sync version: v23.11.29-22:27    
      Sync flavor: googlePlay    
      
      Ultra user: false    
      View type: Slides    
      Push enabled: false    
      
      Device: beyond0q    
      Model: samsung SM-G970U1    
      Android: 12
      
    • WeirdAlex03
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 months ago

      It’s caused by a user on another non-Lemmy, non-Mastodon fediverse platform. The lemmy web UI doesnt have a problem with them, but I think Sync doesn’t know how to deal with displaying a username from an unfamiliar platform

  • The Pantser@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    Yes, I tried to figure out the post but it’s really far down the list. I was going to attempt turning off images and find it but I lack the motivation.

  • Kevin@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    I’m not crashing (yet). Is it possible to link the post?

    Device information

    Sync version: v23.11.29-22:27    
    Sync flavor: googlePlay    
    
    Ultra user: false    
    View type: Slides    
    Push enabled: false    
    
    Device: cheetah    
    Model: Google Pixel 7 Pro    
    Android: 14