Starting to realize how many people have >25MB profile pictures in Nostr. No wonder why things have been crashing...
Gotta find an image proxy and scale them down to under 500kb to make things better.
Discussion
8.4 kb
>25MB 😂
🤣
My Amethyst app size has gone up to 1.5 Gb after latest update, any idea why the app is getting so big?
Or maybe any plans in future updates that can scale down the app size?
😆 5mb is a fair limit
Check out the accounts #[2] is following. I made it for testing image down sampling in Damus.
That explains a lot. Literally <5k probably down to 2000 bytes, even configurable, would be fine for these thumbnails, scrolling is currently very janky. Unless the user individually requested a full size profile preview like Twitter. C# has brilliantly fast image resizing but that might only be due to Windows GDI. I made a 'facebook user profile image library' for a very similar problem years back. If there's a utility lib for Java/Android, these reduced images could go into a cache pool, and all be done in the client without a proxy online. I'm going library hunting.
What do you think? Worth a try? I don't see the robust interpolation options c# has but maybe it's fast and great OOB
This example resized image is under 7k and is larger pixel wise than the app profile thumbnails.
. This is just some random image a guy did off this thread and if the source image were better, so would be the result.
If it got really crazy, a lazy loader could go get and resize at higher quality when the scrolling stops, and you can always dispose the originals https://stackoverflow.com/questions/46149206/how-to-resize-image-without-losing-quality
Here's a list of Java and two Android image sizers
https://github.com/topics/image-resizer?l=java
This one looks very nice but might be difficult to get into Android
To be honest all of nostr needs better image management. Data usage on the protocol is not so efficient right now. Mobile companies loving it tho
Yes, I have to empty my cache regularly. Mayby an in app button to empty cache could be an idea.
#[2] reported that many users have profile pics larger than 25MB. If clients pull those images then that would add up quick. See note #[3]
Maybe that’s not it, but most likely contributes if profile pics aren’t cached. Or is it simply lots of relay traffic between client and the relays. #[4] #[5] curious to know your thoughts.
Fun things to work out as this amazing system gets built!