this post was submitted on 09 Jul 2023
101 points (96.3% liked)

Asklemmy

43329 readers
2004 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
 

As I was browsing lemmy and the fediverse at large, this question kept popping into my head.

Since multimedia files have a much bigger footprint than raw text, it made me feel worried since as time goes, massive resources will be needed to keep up with the big data coming in.

I do wonder if the instances have taken the route of the cloud and just decided to put all of it in something like AWS S3? Or maybe they use self hosted storage with something like minio for object storage?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 47 points 1 year ago* (last edited 1 year ago) (21 children)

This will differ greatly from instance to instance. The people running lemmy.world have published some info on their infrastructure. My instance is running on a rather small VPS with 100GB storage, but I will have to rethink my solution rather soon as images and videos from my subbed communities [Edit: which are stored on outside sites] are eating around a gigabyte per day and I think this is likely to increase.

Edit: I want to clarify that I was partially wrong - Lemmy only locally caches content which is hosted on outside sites (e.g. imgur). It does not cache content that was directly uploaded to another Lemmy instance and just embeds the source media.

[โ€“] [email protected] 3 points 1 year ago (7 children)

Is it caching the entire image from the post or just the thumbnail?

[โ€“] [email protected] 4 points 1 year ago* (last edited 1 year ago) (6 children)

Everything. It does some re-encoding when it retrieves content from other instances and you can set limits for pictrs (the software Lemmy uses to host media) regarding file sizes etc.

Edit: I was partially wrong about what is cached, see my original comment

[โ€“] [email protected] 2 points 1 year ago (1 children)

When I was looking into hosting my own instance I thought I saw an option to disable media file replication entirely so that they would always have to be fetched from their home instance.

[โ€“] [email protected] 2 points 1 year ago (2 children)

That would be great to know, any chance you remember where you read that?

[โ€“] [email protected] 2 points 1 year ago

No, but I bet I could find it again if I hadn't just imagined it and made it up for this comment. Give me a few.

[โ€“] [email protected] 2 points 1 year ago* (last edited 1 year ago)

It's possible that I've misunderstood. And it's also important to note that I was looking into this for the purposes of creating my own, single user instance. I wasn't planning on posting to my own instance, just using it as a single logon where I could control what other instances I federated with.

Here it mentions not installing pict-rs and removing its configuration if you don't need image hosting. My interpretation at the time was that it would mean that no images would be hosted locally on my instance. But that was very early on before I understood more about federation, and now I realize that it may in fact also mean that any content coming from federated instances could have images broken, not that it would load the images from the remote instance. So now, I no longer think that this is a solution for not syncing images, but I'm not at all sure of that.

load more comments (4 replies)
load more comments (4 replies)
load more comments (17 replies)