To offload the storage requirements of the instance you’re posting in. If everyone starts uploading images directly in the comment, the server HDD/SDD will be overloaded. Consider using a third party service and posting the link from there instead!
Thats kinda the point of the feature though… To be used. If its a performance issue, then it should be turned off. In the end, someone has to host the content.
Agreed, that decision should not be left up to the users. It’s the server maintainers who know best whether they can afford the storage space. If not, they should limit the ability to store too much data, by whatever means they find relevant, e.g. by limiting maximum post size.
Hosting the images directly on the lemmy/kbin instance creates imo unnecessary traffic to the servers. I don’t know if admins can disable selfhosting images, but considering the low-powered machines almost every instance is currently hosted on, I would assume it would be in everyones self-interest to outsource image hosting (at least for now).
This is a privacy risk because Lemmy doesn’t proxy external media (or cache remote media like Mastodon). It’s also better for longevity, if an external image host the image is gone.
Postimages already has official plugins for several forum softwares. I am sure one of them could be tweaked for use in Kbin and Lemmy instances. And postimages themselves might help in this, if contacted.
Wait, I’m simply pasting them into my comment. Why should I use a dedicated image holster?
To offload the storage requirements of the instance you’re posting in. If everyone starts uploading images directly in the comment, the server HDD/SDD will be overloaded. Consider using a third party service and posting the link from there instead!
Thats kinda the point of the feature though… To be used. If its a performance issue, then it should be turned off. In the end, someone has to host the content.
Agreed, that decision should not be left up to the users. It’s the server maintainers who know best whether they can afford the storage space. If not, they should limit the ability to store too much data, by whatever means they find relevant, e.g. by limiting maximum post size.
Hosting the images directly on the lemmy/kbin instance creates imo unnecessary traffic to the servers. I don’t know if admins can disable selfhosting images, but considering the low-powered machines almost every instance is currently hosted on, I would assume it would be in everyones self-interest to outsource image hosting (at least for now).
This is a privacy risk because Lemmy doesn’t proxy external media (or cache remote media like Mastodon). It’s also better for longevity, if an external image host the image is gone.
Postimages already has official plugins for several forum softwares. I am sure one of them could be tweaked for use in Kbin and Lemmy instances. And postimages themselves might help in this, if contacted.
https://postimages.org/plugins