Nostr Web Client

I'm 170 KB animated... But my bots are about 4 MB each just because I like them to move smoothly. Maybe I should explore different ways how to animate them without using so much bandwidth. BTW shouldn't profile images be cached for at least a day?

daniele 4mo ago 💬 2

I don't think users of your bot are happy to download every day 4MB for a profile picture :) It's just wasting resources.

Btw, animated images can be quite disturbing for some people with specific conditions (epilepsy, ADHD, autism), therefore, as a general rule, they are not recommended for good accessibility.

Reply to this note

Please Login to reply.

Discussion

Aida 4mo ago

The bots are animated smoothly (for example, nostr:nprofile1qqsyeuhgtuhv77mc0j8gl7xgthpegs0vlqtnprf88glx5499wje9gtcpzamhxue69uhhwmm59eeksctkd9hxwtntd9mkjtcpzdmhxue69uhhyetvv9ujuumpdch8jap0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsp4zll2), so they're much less disturbing compared to my profile picture. I'm more concerned about the size. But you definitely have a good point about accessibility. I will see if I can find a different image for my profile without changing my Nostr identity too much.

Valentino Giudice 4mo ago

I think when it comes to accessibility it's better to disable animations on the client, rather than to avoid animated images altogether.

daniele 4mo ago 💬 1

As a general rule, I agree.

But animation in a PFP is an incidental feature, actually a bug. Rendering a still image for gif/webp is not simple, often requires extracting the first frame or leverage some rendering exceptions to halt the animation. Better manage it at the source.

Valentino Giudice 3mo ago

Getting the first frame, unless there is a way, in the format, to prescribe a different one (or even an alternative static image) seems pretty reasonable.

I don't like animated profile pictures, but I don't see accessibility as a reason to avoid them.