17
PyLova v0.4.1 Customisation, Performance, QoL & Bugs New Release (self.pylova)
submitted 3 weeks ago by [A] to c/pylova
16 comments fedilink hide all child comments
 

image

PyLova (Python+Pavlova) is a soft fork of PieFed, aimed at improving the user experience through UI overhauls, empowering users and admins with agency, improved administration and moderation functions, and general bug fixing.

New in V0.4.1

New & Improved

  • Customisable Sidebar Widgets: You can now choose what widgets appear (if any) and in what order. Selection is small for now, this feature will be expanded upon further in future updates. Please suggest any ideas for widgets you would like to use.

Bug-Fixes & Misc

  • Can Sort Communities by Sub Count
  • Comms can now be assigned into multiple communities.
  • Fixed security vulnerability with markdown injection.
  • New Communities without post body were breaking daily cron jobs.
  • Updated requirements. For older instances this should enable AVIF in post thumbnails.
  • Images upload into WebP to reduce storage needs.
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 weeks ago (13 children)

Images upload into WebP to reduce storage needs.

Does that mean literally every image file that I upload will be converted to WebP? Is that something configured by the instance admin so they can disable that behaviour if they want?

  • permalink
  • fedilink
  • source
  • hideshow 13 child comments
    •
  • [–] [S, A] 3 points 3 weeks ago (12 children)

    Yes it can be set in the .env, the default behaviour was JPG. If you think it’s going to cause any issues for you, let me know and I can disable it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 2 points 1 week ago (10 children)

    You might want to set it to not convert AVIF images to WebP. I just tried uploading a static AVIF image, and it was automatically converted into a WebP file that actually had a larger file size than the original AVIF, which seems to be the opposite of the intended purpose of the "automatically convert to WebP" feature. For most old file types, automatically-converting makes sense because converting to WebP will save on storage, but AVIF files are already incredibly small.

    • My original AVIF: 28.9 kB
    • The WebP after converting: 51.2 kB
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] [S, A] 1 point 1 week ago (9 children)

    Okay, I've added a check and if the converted image is larger it'll use the original. It'll be in 0.5.1 I should release tomorrow with some other small stuff, mind checking it again when it's live?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 2 points 1 week ago (8 children)

    Smart! I can surely test that when I see 0.5.1 is live.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] [S, A] 1 point 6 days ago (7 children)

    We’re on 0.5.1 if you don’t mind checking now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 2 points 6 days ago (6 children)

    Seems to be working as intended. I tested several files:

    I deleted the original AVIF that I had tried uploading yesterday, but I recreated basically the same image and uploaded it again:

    • Original AVIF: 28.86 kB
    • Converted AVIF: 28.18 kB

    Some AVIF that I rendered to intentionally be a huge file:

    • Original AVIF: 513.16 kB
    • Converted WebP: 133.25 kB

    Just to make sure legacy file formats are still converting as expected:

    • Original PNG: 86.28 KB
    • Converted WebP: 10.90 KB

    Making sure animations DO NOT convert even if the resulting WebP would have undoubtedly been smaller:

    • Original GIF: 631.17 kB
    • Converted GIF: 631.17 kB
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S, A] 1 point 6 days ago* (5 children)

    Awesome, glad to see it working. Thanks for all your help with image support, your testing over all this has made the process much easier.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 6 days ago (4 children)

    Sort of off-topic, but do you know if there is a good way to manage my old uploads? For example, if I want to delete an old image that I had uploaded months ago.

    In the textbox to create a post/comment, the "Upload or insert media" button brings up a modal with my 50 most recent images and I can delete any of them, but I can only see those 50. Looking everywhere around the website, I can't find any way to delete a really old image from before my 50 most recent.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S, A] 1 point 6 days ago* (3 children)

    image

    On your settings page on the right card you'll have a button for the file manager. You can mass delete as well.

    If you need more storage space let me know, happy to allocate you extra.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 6 days ago (2 children)

    Thanks! I just knew there was a page like that somewhere that I have visited before, but I just could not find it recently. It seems to work better than the Lemmy equivalent page, which is great.

    I am sitting at "You are using 42.6 MB out of a quota of 50.0 MB", so if you are really willing to allocate extra, I will certainly take it!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 weeks ago* (last edited 3 weeks ago)

    Personally, no, I do not have an issue. For still images, it seems that WebP works just fine for everyone everywhere, so I upload just about every still image as WebP anyway. But a lot of apps still don't handle WebP animations optimally, so I like to use GIF for most animations. But through a little testing, it seems like animated files don't actually convert to WebP, so that doesn't seem to be an issue.

    some testing
    GIF I just uploaded, which ended up as GIF:

    bvXGmB23zH4zjsi.gif

    AVIF I just uploaded, which ended up as AVIF:

    9tZhXAQNRcWGTjM.avif

    JPEG I just uploaded, which ended up as WebP:

    ShUggHyKLKhp6VY.webp

    I am glad to see that it is customizable by the admin. I am not actually an admin myself at all, but I know that different admins tend to have different opinions on the issue. Notably, lemmy.sdf.org actually works in the opposite direction: any WebP image uploaded gets automatically converted to PNG, which I assume is a philosophical choice due to WebP being controlled by Google.

  • permalink
  • fedilink
  • source
  • parent