#[2] your pfp is not loading! Too big! You’ll need to optimize it. If you need help, let me know! 🐶🐾🫡
Discussion
#[3] , how are you shrinking gifs?
What do you use?
On a Mac I use image optimizer ! For the service, there are few things you can use. If you want to know more, let me know and I’ll dig something up! I assume you are asking for nostr.build and php! 🐶🐾🫡
Yeah, something I can use on the backend, 70% of my storage is probably oversize gifs 😄
Ok, let me DM you with info and tech details! 🐶🐾🫡
So you can probably start here: https://imageoptim.com/versions.html and https://trimage.org
Longer term, assuming you use AWS, you should look into Lambda to do that for you. You basically upload file to S3 and then trigger a lambda to optimize the file. If you want me to help you with that, do not hesitate to DM me. Otherwise this should be a good start for your current setup! 🐶🐾🫡
Can AWS lamda do Gifs, I thought just videos? Interesting, thank you, let me look into it. I’m likely moving to S3 soon, so that could work..
Lambda is just a docker on steroids! Again, if you need help or want to converse about it, let me know in DM! 🐶🐾🫡
Recommend against AWS S3. You'll have better performance and lower costs (no egress fees) using Cloudflare R2 bucket instead , which is also S3 API compliant.
Yeah, I already suggested it but in his current situation S3 makes sense. He has a startup grant from AWS! 🐶🐾🫡
Ah nice, yes that make sense then. At least it'll be easy to migrate to Cloudflare R2 when the time comes 😎
Yep, that is the right way! CF also has some startup programs but I think it can be easier to get going in AWS! 🐶🐾🫡
It's also easy to add a non-AWS-CloudFront domain for CDN to the S3 bucket. So, with a CNAME record at Cloudflare could be used (ex: files.nostr.build) and with the $20/m Pro plan to enable the Lossy image optimisation from the edge, rather than server-side. That would also deliver WebP to help speed up delivery for web-based nostr clients.
Thinking this AWS grant will last 6-8 months, will likely move platforms after..
I’ve been using ezgif.com and I can usually chop my gif sizes by 50-75% and they still look pretty good.
They have a GitHub api hack that could work, but once I put content on the S3, it will basically do it for my automagically at the edge
This is the way.
There is a next level of scale after that, but for now get the server out of the read path. Not just for cost but for sanity of operating with such a small team.
The write path you can switch to APIGW and a bit of lambda and eliminate the “running computers” thing there. Use cost savings plans.
