this post was submitted on 19 Oct 2023
13 points (100.0% liked)

Aotearoa / New Zealand

1657 readers
3 users here now

Kia ora and welcome to !newzealand, a place to share and discuss anything about Aotearoa in general

Rules:

FAQ ~ NZ Community List ~ Join Matrix chatroom

 

Banner image by Bernard Spragg

Got an idea for next month's banner?

founded 1 year ago
MODERATORS
Dave
RaoulDuke
13
Aotearoa Daily Kōrero 20/10/2023 (self.newzealand)
submitted 1 year ago by absGeekNZ to c/newzealand
45 comments fedilink hide all child comments
 

Welcome to today’s daily kōrero!

Anyone can make the thread, first in first served. If you are here on a day and there’s no daily thread, feel free to create it!

Anyway, it’s just a chance to talk about your day, what you have planned, what you have done, etc.

So, how’s it going?

you are viewing a single comment's thread
view the rest of the comments
[–] d3Xt3r 3 points 1 year ago (1 children)

Thanks for this, I normally browse by all/new and have noticed there's a big difference in what I see here v/s my account on lemmy.world.

I'm curious though how much of an increase in storage/bandwidth this would cause.

[–] Dave 3 points 1 year ago

I'm curious too!

I was having a chat with one of the devs yesterday (on lemmy, so I guess you could find it in my post history). They realised that thumbnails are not resized at all. Thumbnails are generated when content is federated, and stored in full resolution. So even if no one looks at it, it's stored. And the thumbnail cache never expires.

Currently the image cache in total is 137GB (based on last night's backup), and has images from June when the instance started.

The image storing component pictrs has no ability to resize images, so looks like resizing isn't coming any time soon (it would be good to have to help thumbnails load faster). However, the next major update, lemmy 0.19 and pictrs 0.5, will have the ability to set a time limit on the cache (or even disable it completely).

If we aren't even resizing the thumbnails then perhaps having the cache disabled would be appropriate, though I had planned to set it to a few days or a week. In either case, there should be a dramatic drop in the size of the cache once that update is out.

A smart person may have waited until that was available before triggering the seeder, but I just saw the tab that's been open for weeks and decided to just get it done while I had the chance.