[Perf] Serve the images using the local server instead of base64

alexjba commented 6 months ago

Use the local server to serve the following images. There's lots of base64 images being transferred from status-go and kept in memory in nim and qt:

[ ] Community banner
[ ] User profile images (E.g. my profile, demo user profile in Appearance settings)
[ ] Community logo
[ ] ~Profile QR codes~ The qr code is generated in nim. The QR code view is redesigned and will be viewed in a popup. The memory impact is really low.
[x] Community tokens - The community settings view is always loaded and all the community tokens as well. TODO: use lazy load. Done by
[x] wallet community tokens. The Collectibles view is already a memory bomb because we're missing the means to limit the external collectible image size (we could easily load hundreds of mb for 1 fancy collectible).

alexjba commented 6 months ago

@jrainville I've labeled this issue for messenger-team as most the base64 images are related to communities

Cuteivist commented 6 months ago

Use media server for community token images for wallet view - https://github.com/status-im/status-desktop/issues/13029 Use media server for community collectible images and community images- https://github.com/status-im/status-go/pull/4477

iurimatias commented 5 months ago

moving to 2.29 due to lack of space in the current milestone

jrainville commented 1 month ago

status-im / status-desktop