Thanks for asking! :) In general, I’d prefer that users act as if there are no resource limitations. It’s our job on the backend side to manage the implications of this. In the short term this isn’t using up enough to be a huge worry. In the long term, lemmy should improve and make it easy for us to manage this.
I heard from dcx that the images are the ones that eat the most storage(which is understandable) and yes it can eat resources quite fast. The main problem would be storage, while multiple large size, high res images being rendered could make a site load slower(but Lemmy’s performance is pretty good so it should mostly only be a storage issue, at least for now)
I was also thinking about whether to bring this up to dcx regarding image compression, but perhaps we’ll have to do that ourselves… Aside from storing a compressed version of the image, it’s also possible to decompress it for viewing(if we further compress it), but depending on the compression/decompression algorithm it can be computationally costly(it depends on how much quality you want to preserve)
Ye I was thinking of that too, but we’ll probably have to modify the source code or something unless other developers come up with that. I haven’t tried doing that before myself, but it’s certainly possible
I considered that, but viewing old posts/comments is going to be a problem… In reality I don’t think people actually delete old data but rather they stash them somewhere separately(and retrieve when necessary). But we’ll still need to allocate storage for that I think?
@[email protected] I noticed that images are full sized. Will this eventually eat up the server’s resources and bandwidth?
I find that for sharing and viewing (not pixel-peeping like what digital photographers do) 720p or 1080p sized images are good enough
Thanks for asking! :) In general, I’d prefer that users act as if there are no resource limitations. It’s our job on the backend side to manage the implications of this. In the short term this isn’t using up enough to be a huge worry. In the long term, lemmy should improve and make it easy for us to manage this.
I heard from dcx that the images are the ones that eat the most storage(which is understandable) and yes it can eat resources quite fast. The main problem would be storage, while multiple large size, high res images being rendered could make a site load slower(but Lemmy’s performance is pretty good so it should mostly only be a storage issue, at least for now)
I was also thinking about whether to bring this up to dcx regarding image compression, but perhaps we’ll have to do that ourselves… Aside from storing a compressed version of the image, it’s also possible to decompress it for viewing(if we further compress it), but depending on the compression/decompression algorithm it can be computationally costly(it depends on how much quality you want to preserve)
Maybe it’s possible to disable direct uploads and point to image hosts like https://postimages.org/ instead?
Ye I was thinking of that too, but we’ll probably have to modify the source code or something unless other developers come up with that. I haven’t tried doing that before myself, but it’s certainly possible
Possible to auto-delete images once it’s up for, say, 2 weeks or 1 month?
I considered that, but viewing old posts/comments is going to be a problem… In reality I don’t think people actually delete old data but rather they stash them somewhere separately(and retrieve when necessary). But we’ll still need to allocate storage for that I think?
I messaged him asking the same question as i setup two image-heavy sub, he said should be okay(for now, i think)
Sape dcx? Owner of this site?
Admin, yes.