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
    8 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
      5
      ·
      edit-2
      8 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
        ·
        8 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
          ·
          8 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.