Great, thanks! I see the upgrade. I will try to still use it wisely.

All good, you should be seeing more space now 💜

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!

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.

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.

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.

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

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

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

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?

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

So far it’s only the creator, but I’ve already been given some ideas for improvements and could also look at multi-user managed lists.

Also, who has the ability to edit any given blocklist? If I create and share a blocklist, is there a way to allow another certain user to make whatever changes they want to the blocklist, or am I the only user who is ever able to edit it? Meaning that if I were to delete my account, that blocklist could no longer be updated and someone would effectively need to fork the blocklist.

Yes, or at least as intended they should. Will need to really test them in action to ensure it works.

Think of it like the Feeds, you can join someone elses and they add or remove comms that you can have in your feed. Depending on how much use they get I might add the ability to duplicate so you can copy someone elses list and make your own changes if you disagree with where it's going, also to give greater control over stuff like overriding and approving certain comms,users.

Shareable Blocklists: Users can create, maintain, and share block lists of users, communities, instances, or domains. Users can be hidden completely or muffled.

Do future changes to the public blocklist affect previous users? Let's say I apply a public blocklist today that blocks User A, User B, and User C. Then say that tomorrow, someone adds User D to that blocklist. Does that change propagate out to me so that I am automatically blocking User D now as well?

Anything that supports PieFed works with PyLova. Nothing supports the unique features of either.

I have been tempted to work on an app, and had previously given it a go.

I use summit extensively. The limitations are still very similar to with a piefed server.

I LOVE seeing all these new features continually popping up in PyLova!! And I love specifically these Transparency options!!!

I am not pushing for the ability of PyLova to block a community, although Lemmy has it and in general PieFed was built to have more features than Lemmy, which PyLova would have inherited, so it stands to reason that it might? And if PyLova does have this feature, then yes it would be great to see it added to the Transparency section like the others.

Yes, agreed that fascists need not be platformed automatically on every instance across the entire Fediverse - blocking is not a bad thing.

You guys / gals / other are awesome, thank you for all your efforts to improve things 😎.

PyLova has that and you can find that information on the About page at the bottom.

https://quokk.au/about

Most of the blocked ones are the defaults that came from PieFed. I added a feature to give explanations as for why the block was placed, but have not blocked anything since and as such they all list no reason. Most of them are far-right/nazi places.

Edit: Oh that's communities you're after. I'm not sure if that's even a feature for PF/PyLova.

Edi2: There is an ability to delete a community, but I'm not sure that stops it being re-added? I'll look into it and if not I can add the ability to block individual comms and also add them to the about page censorship list.

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.

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.

Its an upstream issue from PieFed, all instances PF and PyLova have this issue.

Apparently the script that auto-joins subs posted in !newcommunities@lemmy.world caused it because there was nothing in the post body to join?

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.

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?

New Communities without post body were breaking daily cron jobs.

wife:

I pray you're kidding, and use different schedulers for both pylova, and systems administration.

Fixed.