reply with features and bug fixes you’d like to see in Philthy, the lemmy fork that runs on this instance. no guarantees I’ll get to any of them soon, but particularly low-hanging fruit and well-liked features can be prioritized.

  • @selfOPMA
    link
    28 months ago

    maybe a better markdown implementation? the current one has a lot of oddities I’ve never seen in a markdown editor before

    • @froztbyte
      link
      English
      38 months ago

      that’ll devalue my Lemmy Ate My Formatting property t-shirt! I protest!*

      (* I most definitely do not protest)

    • David GerardA
      link
      English
      28 months ago

      they rolled their own right? there must be a pile of rust markdown implementations

      • @selfOPMA
        link
        38 months ago

        I’m fairly certain they did based on how it works – if that’s the case, I consider it fairly low hanging fruit to swap to something more sensible. this’ll break our compatibility with other instances in a minor way if we do it since we won’t be rendering posts in the same broken way, but I feel like the risk is fairly minor. I’ll check on this and post an update once I get started on the rebrand for the frontend

        • @selfOPMA
          link
          38 months ago

          so the frontend uses markdown-it which is fairly popular; I think the problems with it are the settings they configured for markdown-it’s parser, and the almost 800 line MarkdownTextArea making interacting with the damn thing so clumsy. we can probably get a pretty good improvement out of changing to a saner markdown-it configuration and swapping the MarkdownTextArea component for something well-supported from NPM

        • @froztbyte
          link
          English
          3
          edit-2
          8 months ago

          I was percolating on this. And here’s a maybe-nasty workaround that may even be usable in federated manner (I have no idea if this is even viable, need to learn some AP)

          Internally store posts in raw and some kind of decorated-raw format, where the “decorator” is essentially some frontmatter that specifies rendering/renderer properties. Think <!-- renderbits: […..] -->\n\npostgoeshere

          Upside of this approach is that if it is federable (and again, dunno, will need to check still 😅), it can allow each instance to self-handle as needed, along with providing own fallbacks and stylemaps

          • @selfOPMA
            link
            38 months ago

            not a bad idea! there might be an existing format that’d handle this well. I need to confirm what format Lemmy uses for styled text interchange — I think it might just be markdown?

            • @froztbyte
              link
              English
              38 months ago

              looks like both markdown/source, and html? this and this is what I drilled down to