this post was submitted on 11 Jul 2023
128 points (100.0% liked)

Fediverse

19 readers
2 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago
128
Imgur links suck (kbin.social)
submitted 1 year ago* (last edited 1 year ago) by atomicpoet@kbin.social to c/fediverse@kbin.social
 

Most Fediverse software supports image uploads, so there's no reason to use Imgur for image hosting. Hell, even on my small single-user server (atomicpoet.org), image hosting is easy peasy. Not only is Imgur not needed, they're an annoyance for those of us who are used to seeing images natively on the Fediverse.

I know habits are hard to break, but just remember: this isn't Reddit ๐Ÿ™‚

you are viewing a single comment's thread
view the rest of the comments
[โ€“] wutanc@lemmy.world 5 points 1 year ago (3 children)

How does images work with federation? If 1m users on a big server look at my images that I posted on a small server, is that small server hit with that traffic? Or is all servers caching the image?

[โ€“] imaBEES@kbin.social 2 points 1 year ago (1 children)

IIRC all text and posts are cached on each server that is federated with one another, while images are just referenced and loaded from the server they were posted on, so if you had an image post on your server, anytime someone wants to load that image it would hit your server

Not strictly true. Mastodon, pixelfed, KBin all cache images.

load more comments (1 replies)