So now that Lemmy and the community overall are getting a lot of attention, with /c/memes being one of the biggest communities across instances, I think we should be a bit more strict about certain things.
I’d like your opinion, though. What do you think about a rule about only allowing images, and that such images need to be uploaded to Lemmy instead of linking to something like Imgur. I think that text and videos are a better fit for some other community (at least until we get something where we are able to play videos within Lemmy).
Not a good idea, sites like Imgur allows lemmy to not store the data, which takes up a huge amount of space, accross all instances. It’s better to have image on the instance, yes, but after a bit of work, the lemmy’s devs can show external images inline, just like on reddit.
Agree with this, there’s also instances like mine that have a very low file size limit for uploaded images (100kb) in order to keep hosting costs down.
That’s fair, but this community is hosted on lemmy.ml so you can still have that rule, images are cached and shared among servers without the need of each server actually having to own it on their server.
Not exactly true, unlike Mastodon I believe only the original instance stores the photo. Even when browsing a remote instance, you’re loading from their server.
Oh, might be right, yeah.
But still, devs should implement showing videos/images from other services to show up here inline, instead of having to click the link!
I think that’s implemented but it’s something specific to Imgur which blocks from viewing and which may require you to code something specifically for Imgur rather than it being a universal thing. On Reddit it works because it was created to be used there.
oh yeah, only if it link directly to an image, not the imgur link itself (which makes sense)
I think it’s cached on federating servers - that’s why copies of beehaw communities still exist on lemmy.world and sh.itjust.works despite defederating
The posts are cached, like the text and comments. The images aren’t AFAIK. The links to the images are also cached, and BeeHaw can’t tell what instance is accessing them, it just sees a request from each user’s computer for the image.