I find that the compression used for images in lemmynsfw is quite aggressive, and leads to a significant loss of image quality. I understand this may be done to reduce storage costs, but is there any chance it could be dialed back a bit?
I find that the compression used for images in lemmynsfw is quite aggressive, and leads to a significant loss of image quality. I understand this may be done to reduce storage costs, but is there any chance it could be dialed back a bit?
I wonder if there’s an API gateway for something like IPFS that speaks S3 – that’d allow pict.rs to speak to the storage layer if it already supports S3, and people could literally donate disk space to be used for the service. It’d need some thinking to get it right and a bit of a revamp of the deployment though, and I don’t know if it’s realistic idea at all, but it’s an idea at least 😀
There’d be a double image download for content fetched from IPFS, increasing latency. Essentially the server wouldn’t have to store any old content that hasn’t been accessed for a while. Would probably make operational costs a lot lower in the long term, at the cost of user experience for old and unpopular content. Not bad?
Yeah, could use the distributed block FS as a sort of cold store, but at the same time the local node would always have the currently most popular blocks.
Relying on a distributed system that has a lot of churn in members for content availability is a bit of a gamble though, and content that doesn’t get requested very often could just disappear if there’s no systematic “clones” being done. Probably a shit idea, honestly 😅 I’ll stick to posting pictures of pretty girls