Update on this: I got the feature work done this weekend, so now I'll be testing it a bunch for upgrades and storage migrations
asonix
I am aware of garage, but haven't tested it yet with pict-rs. It's a cool project for sure
Yes. It uses sha256 rather than perceptual hashing, but that's Good Enoughβ’οΈ
I'm not against including an ipfs layer in pict-rs, but the complexity would go way up. Federating an image between lemmy servers would require sending the ipfs uri between servers via activitypub, and then each receiving server sending that uri to pict-rs. pict-rs would then need to decide, on each server, if the ipfs-stored image matches that servers' image requirements (max filesize, max dimensions, etc), and if it does, then that pict-rs server would request to pin the image. I don't know exactly how ipfs pinning works, but ideally it would only be stored locally if it isn't already stored in at least N other locations. If the remote image doesn't match the local server's configuration, it could either be rejected or downloaded & processed (resized etc).
Serving ipfs-stored images that aren't replicated locally might also be slow, but I won't know for sure unless I actually try building this out.
I can only say "when it's ready." I think most of what I want to include in 0.4 is there, but I don't have a ton of time to work on it currently. I might see if I can get my last feature changes in this weekend, then it will be a matter of ensuring the 0.3 -> 0.4 upgrade is smooth, and that storage migration is solid
pict-rs doesn't keep track of how often it serves different images, so there's not a good metric for pruning old images. That said, 0.4 will introduce functionality for cleaning up processed images (e.g. resizes/thumbnails), removing their files & metadata. If they are viewed again, they will be re-generated.
0.4 will also include the ability to scale down images on upload, rather than storing the original resolution. This is not yet implemented, but it's on my roadmap.
All this said, it is already possible to use pict-rs with object storage (s3-compatible), rather than block storage. That's a good option if your hosting provider offers it
Problem:
I gave tokio-console a buffer way too big
Fix:
Update pict-rs to at least v0.3.0-rc.7
, which doesn't enable console by default
As an update, I'm back online on cable internet instead of fiber. I still need to get our fiber fixed but paying a different provider to get us online in the meantime made some amount of sense.
git.asonix.dog should work now
If you want all the code required to build pict-rs I can try getting it all working on yerbamate.dev this evening
Yup, my internet is down. A fiber line in our neighbor's attic was broken (assuming an animal chewed through it). We're trying to get back online but it's taking some time. So far we've been offline for around 87 hours :/
I chose it at the start of the project π€·