Note:

I have some bigger changes to push to blorpblorp.xyz this week. Bigger changes means sightly higher risk of breaking things. Sorry for any inconvenience. Let me know ASAP if you see anything broken.

v1.9.24 in production

  • feat: add support for markdown superscript and subscript #196
  • feat: allow images to be pasted into markdown editor #197
  • feat: piefed post flairs #184
  • fix: storage garbage collection #199
  • refactor: improve blocking #205
  • refactor: shrink react query cache #210
  • feat: ultra compact posts #204
  • feat: add remove post as mod #208

v1.9.25 in beta

  • refactor: handle failed comments better #211
  • refactor: use fallback imgs in lightbox feed #218
  • feat: make main sidebar collapsible #216
  • fix: fallback post embed and how post urls are parsed #220
  • refactor: label banned post/comment authors #217
  • refactor: virtualize blocked users and communities screen #223
    • Mose13@lemmy.worldOPMEnglish
      4·
      4 months ago

      For PieFed, it uses the selected instance’s /api/alpha/upload/image endpoint. Lemmy uses the equivalent endpoint.

      https://github.com/Blorp-Labs/blorp/blob/main/src/lib/api/adapters/piefed.ts#L1824

      There’s also some image compression we apply. That happens inside of a web worker. I have to double check the npm library I’m using, but I can add more info if you’re curious. It all happens locally on your device.

      • Zedstrian@lemmy.dbzer0.comEnglish
        2·
        4 months ago

        Is the compression lossy? I noticed that one of the posts I did with Blorp seemed to have a lower image quality for images than normal, but wasn’t sure why.

        • Mose13@lemmy.worldOPMEnglish
          2·
          4 months ago

          Yes unfortunately. This is something I would like to investigate further. I’m not entirely sure if Lemmy/PieFed will auto compress images that are too big, or if they will fail. The goal is to avoid failed uploads at all costs. But it’s possible I over did the compression.

          • I would like to further investigate what Lemmy/PieFed do if an image is too big
          • Decide if we should back off on compression or leave it on by default with a setting to turn it off
          • Probably a bad idea, but we could auto detect photography communities and turn it off for those

          I’m open to other ideas

          • Zedstrian@lemmy.dbzer0.comEnglish
            2·
            4 months ago

            While in most cases images seem to stay under the Lemmy file size limit (at least for the instance I’m on), as it’s a pain to upload videos to Lemmy, I think auto-compressing them to an accepted format would be useful. Auto-converting images to accepted formats would also be useful.

            If the file size limits of different instances could be queried, whether or not a given file should be compressed could be determined on that basis. Should a user prefer to do their own compression and/or image adjustment, compression could be toggled off altogether.

            • Mose13@lemmy.worldOPMEnglish
              1·
              4 months ago

              I have to double check this, but I think the currently Lemmy version doesn’t surface the image upload size limits. But I wanna say a figure version might. I know for sure gif upload is a lot more strict and will fail if it’s too big. From my testing, it seems non animated images might get auto compressed.

              I personally enjoy looking at sharp images in the photography communities. I would hate for Blorp’s compression to be holding people back from posting their photography. That feels like the biggest issues imo.

  • Mose13@lemmy.worldOPMEnglish
    5·
    4 months ago

    Welcome you to all the new people here! Happy this community has been more active lately. I’ve seen all your posts. I’ll get around to fixing everything as I have time.