Asklemmy

43858 readers

1993 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!

Open-ended question
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.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

104

How does Lemmy/Mastodon/Fediverse store videos and images? (programming.dev)

submitted 1 year ago by Blurker@programming.dev to c/asklemmy@lemmy.ml

56 comments fedilink hide all child comments

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

[–] laenurd@lemmy.lemist.de 14 points 1 year ago (1 children)

No need to thank me, currently I am the only non-bot-user of my instance and do not allow registrations 😅

Many of the bigger instances have links to donate to their operators, but I am doubtful that relying solely on donations will be enough in the long run.

[–] natflow@apollo.town 2 points 1 year ago (1 children)

Since you’re the only one, you might consider setting an expiration on the media so your local storage serves as more of a cache. Like, I’m sure you’re far more likely to revisit a recent thread than a super old one, and as long as the original instance is still around you could redownload the media. This might require software patches though idk

[–] laenurd@lemmy.lemist.de 2 points 1 year ago

Firstly: I was partially wrong about what gets cached, see my original comment.

There is an open pull request which is meant to give some options regarding media serving. Right now it's only a rough sketch though and does not implement a lot functionality.