aboutsummaryrefslogtreecommitdiffstats
path: root/static/punks/17.webp
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-11-18 22:38:42 -0700
committerAdam Soltys <[email protected]>2026-11-18 22:38:42 -0700
commit01c03a199f8aafacfcdbaac30af074dd1d56fc53 (patch)
treeeef880f8046077edc6d902acb74f90448f8830ef /static/punks/17.webp
parentcb5826cec34bd6933f1d8d3f1d76629b15ba44a1 (diff)
downloadcoinosv3-01c03a199f8aafacfcdbaac30af074dd1d56fc53.tar.gz
coinosv3-01c03a199f8aafacfcdbaac30af074dd1d56fc53.zip
GIFs loop, even ones made to play once. "My gif reply isn't looping" (Adam, 2026-11-19). The GIF from the picker (gifs.nostr.build/5d6fa840….gif, 23 frames) has no loop instruction (the NETSCAPE2.0 extension), so every browser plays it once and stops on its last frame. When the feed makes its copy of a picture, a GIF without the extension now gets "loop forever" written in after its global colour table. That copy, up to 4 MB, is what the post paints, kept on disk like the other copies. A GIF stored before this change is fetched and looped again; one that already loops, and any other picture, is untouched. Patched, that GIF reads as loop 0 with all 23 frames. New gif-loop-test passes; feed-picture-pager-test now checks that a non-looping GIF is painted from a copy that loops. feed-media-cache, gif-picker, feed-media-views and features-smoke pass.HEADmaster
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01VMan6TV6sjEZSpqqBen9T5
Diffstat (limited to 'static/punks/17.webp')
0 files changed, 0 insertions, 0 deletions