Clients should refuse to fetch profile pics that weight more than... 50Kb?

And of course if they allow to upload them, a sensible resize is needed.

Reply to this note

Please Login to reply.

Discussion

nostr:npub1gnwpctdec0aa00hfy4lvadftu08ccs9677mr73h9ddv2zvw8fu9smmerrq your one for example is ~1.8MB and it also doesn't have a sensible cache policy ;)

I really should go over my relays policys.

Like this constraint

I felt embarrassed, so now my avatar and banner are only 100 KB together 😁 But the quality is really bad now.

Non-optimised gifs are tragic ;)

I'll try using webp, although compatibility issues may arise.

I saw. It's not bad displayed at 'standard' size.

Btw animated pfp are quite annoying, they should be avoided, imho.

Macho Man only needs 15kb 😎👌

But how can you check the size of an arbitrary URL before downloading it?

Can you abort download after 50kb?

curl --max-filesize 51200 $URL

This is an interesting idea!

HEAD request

I guess most file hosts will probably support this, but not all will, and the ones that don’t are also probably the ones that care most about optimization 😅

Legit. Btw, as someone else suggested, truncating should work. Or just download it and trash it way, caching a void pic for a while. The purpose is discouraging the use of fat pics.