62
Call to Action: Fediverse Media Server
(shlee.fedipress.au)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 May 2024
62 points (97.0% liked)
Programming
17314 readers
91 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Can someone explain what this is for? I'm basically unfamiliar with the non Lemmy parts of the fediverse. I had thought Mastodon was like Twitter so I don't understand what a federated media server is supposed to do. It just sounds destined to turn into free pr0n hosting and then get shut down. But who knows.
Mastodon is a Fediverse platform. Lemmy is too. Anyone can host their own Mastodon and Lemmy instances.
When a user uploads an image or video on Mastodon instance 1, and a user of Mastodon instance 2 is following them, that image or video is copied over to Mastodon instance 2 - because that's where that user resides.
This means content gets replicated and duplicated across every shared-network instance. Resulting in resilience, but also ~~exponential~~, excessive storage needs.
OP is suggesting that media files should be shared across platform instances so that they don't get duplicated many times. This would significantly reduce storage and bandwidth needs and use for the platform instances themselves, offloading and centralizing media file concerns.
The same thing happens with text posts, right? I don't see an exponential expansion, just linear in the number of nodes. It sounds like the decentralized way to do things. Hmm. Anyway, thanks for the explanation. It saves some storage but doesn't save bandwidth, it sounds like. Rather, the bandwidth requirement gets concentrated at the shared server.
Depends on the implementation. OP talked about potential of a CDN serving the shared resources. The instance servers wouldn't have to proxy the content. Which would allow caching and not duplicating content and transmission through multiple endpoints.
Yeah, I guess it's linear rather than exponential in growth. From an instance hoster point of view, it just never ends though, and not very predictable.