Hopefully not with a centralized proxy. Clients can just block the download of larger files.

Client sided? Ask the webserver the size of the picture and ignore it if it is more than a specific size. Can even configure it that way?

deterministic scaling functions that use fixed point numbers and multi-party verification of the relation between the original and the scaled versions, mainly. i could easily write a sinc function using fixed point integers, like, as a pair of 64 bit limbs one being the integer part, and the other ...

in a decentralized network, client side.

Clients optimizing images upon uploading and not showing images based on a certain size.

Education

fixed point scaling algorithms. the end.

Clients implementing a limit when changing image in kind 0 metadata. You really can't solve it if someone puts a huge file there though. Besides just swapping with a robohash is size greater than x

there is just 2 ways. Have a proxy in front of your client, but that's for self hosting/advanced users. normalize blossom servers and have them stream chunk of contents rather than the full video. blossom servers should also be able to monetise any chunk served, with cashu channel, whatever they ...

Forced compression? If they don't want it, pay for a service. As for the loading by other viewers, could you put a data notification and manual load button for those with data concerns?

What's the issue? Why do you want to "censor" my 500 MB gifs? You should download them for free and relay them for free for me. /sarc

Forced compression. There literally no reason for multi MB profile images.

Why do we even use gifs in 2025?? Why don’t we use videos or something? Gifs have been fucking retarded for 40 years

1984 reports on kind 0 event id (not naddr) generated and consumed automatically by clients?

What a shocker, a prehistoric image format is inefficient for video 😭

Test the bandwidth and send the smaller jpeg or png version.

Limit file size and hurt some feelings. If your gif is bigger than your attention span, rejected.

its possible to specify in kind 0 spec that picture value cannot point to image larger than specific size. its also possible to change spec to specify two images: small and full size.

We don't this is not an issue