this post was submitted on 20 Feb 2024
70 points (97.3% liked)
Fediverse
28468 readers
657 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thank you for sharing, interesting topic!
On a side-note, I just had a look at Piefed, I like their topics list: https://piefed.social/topics
Flippin' eck. Seeing a familiar Lemmy post on there, clicking it and seeing the whole thing render instantly was a bit of a shock after getting used to Lemmy's more pedestrian loading of stuff.
Using a CDN does not come without downsides, though. Cloudflare itself is becoming another "too big to fail" entity of a system that is not supposed to depend on the resilience/capacity/budget of any single actor.
Personally, I'd rather see a tiered architecture for data, where servers are only responsible for guaranteeing the data from actors on their own servers, but everything else stored in a distributed, append-only stream of data. This would make a lot cheaper to run individual instances and would allow clients to obtain the data from multiple sources.
Some kind of shared object storage would help for images at least. But for that to work Lemmy would need a way to redirect clients directly to the storage bucket instead of proxying all the pict-rs traffic like it is currently implemented.
Like this?
No that is something else. Currently Lemmy does not cache all remote media (other than thumbnails and some non-Lemmy images AFAIK), but I think this is currently being implemented and once that is added, a separate media storage like mentioned in that Mastodon issue might be useful.
What I mean is that currently all image data has to flow though your Lemmy backend, even though object storage usually provides static image hosting and the Lemmy backend could just tell the clients to load the images directly from there, similar to how an CDN would do it.
Yeah, my response was a bit tongue-in-cheek because one of the things that I don't like about Lemmy is this coupling to a specific storage backend. Maybe it was just immaturity of actix that led the devs to take this approach, but most mature web frameworks already allow pluggable storage backends, so in the end it seems that Lemmy will reinvent a bunch of wheels.
That’s true but there are a bunch of CDNs you can choose from and you can switch from one to another fairly easily. Cloudflare just happens to be the most popular at the moment but they’re not the only big player, not to mention smaller players.
FWIW I totally agree with the sentiment that Cloudflare (and AWS for that matter) is creating a too-centralized web. I just don’t see an issue with using CDNs for fediverse servers in general.
Yes. This is why:
https://join.piefed.social/2024/02/09/comparing-network-utilization-of-lemmy-kbin-and-piefed/
https://join.piefed.social/2024/02/13/technical-performance-of-each-fediverse-platform/
Oh wow. That really illustrates it. Your approach to a social media site is very admirable (so much modern stuff assumes that just throwing more CPU cycles / RAM / bandwidth at the problem is a solution).
Thanks :)
It is indeed a nice change