Client dev question:
I understand many if not all clients do "pre-upload" compression when a user uploads media files from within the client.
What about post-upload compression?
For example: If a user uploads a lossless file to nostr.build , do #amethyst, #gossip, #primal, #damus etc. perform any sort of post-upload compression before displaying the output?
Thx in advance :)
#cybersecgirl #nostr
Clients possibly unless not set?? 🤷♂️
Yes, I almost every image server compresses it further when the file reaches their server. Sometimes it depends on the media format, though.
Nostr.Build does not compress audio or video for pro accounts. If a user uploads the file there, it bypasses client "pre-upload" compression from what I was told by the devs.
Just to be sure I understand correctly, are you saying if an audio/visual creator (where quality is important) copy/pastes that lossless audio/video nostr.build link into Amethyst, that Amethyst perfoms a post-upload compression in order to display it?
And if so, what's the best way in your opinion to optimize the output quality to the end user?
Thx :)
Gossip processes downloaded images. It has a setting for which image resize algorithm to use (Nearst, Triangle, CatmullRom, Gaussian, Lanczos3). This is to avoid gigantic images, and to make the images fit better. It also rounds avatar images.
The point of downloading the image in gossip is to show it. If people want originals, the URLs are there and clickable and you can open images in your browser (not for avatars though).
Awsome! Thank you for answering :)
