diff --git a/CHANGELOG.md b/CHANGELOG.md index 74596bf..a124838 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [2.20.2] - 2026-11-13 + +### Fixed + +- Replies to replies on crossposts were never captured. Backfeed read only the first level of replies (Threads `/replies`, GoToSocial's direct replies, Bluesky at depth 1). It now reads the whole conversation (Threads `/conversation`, every GoToSocial descendant, Bluesky ten levels deep) +- Your own replies in those conversations were skipped, so the other side of a back-and-forth was missing. They are now kept when they answer someone's reply (a reply to your own crosspost is the thread continuing, and is still left out). They don't send you notifications + +### Changed + +- Replies are shown nested under the reply they answer, as comments of comments (`u-comment` inside the parent `h-cite`). Migration 026 adds `webmentions.parent_remote_id`. Existing crossposts pick up their threads at their next backfeed check + +## [2.20.1] - 2026-11-13 + +### Fixed + +- A reply to a Mastodon post with a GIF showed a still image. Mastodon turns GIFs into short silent looping MP4s ("gifv"), and only their first frame was kept. The MP4 is now saved on this site and plays muted and looping, as on Mastodon, with the still image as its poster +- Animated GIFs (and animated WebP/PNG) from other sites stay animated in reply contexts instead of being cut to their first frame + +### Changed + +- Migration 025 adds `video` to `reply_contexts`, and has fediverse contexts with an image fetched again once, so existing replies pick up their gifv + ## [2.20.0] - 2026-11-13 ### Added diff --git a/docs/design/v2.20.1/2026-11-13-gifv-reply-context.md b/docs/design/v2.20.1/2026-11-13-gifv-reply-context.md new file mode 100644 index 0000000..d0a247f --- /dev/null +++ b/docs/design/v2.20.1/2026-11-13-gifv-reply-context.md @@ -0,0 +1,27 @@ +# v2.20.1: Moving pictures in reply contexts + +## Why + +The reply https://starpunk.thesatelliteoflove.com/note/20261114032356 answers +an infosec.exchange post with a GIF, but the card showed a still. Mastodon +converts uploaded GIFs to a silent looping MP4 (`media_attachments[].type == +"gifv"`, here 320×240, 5.3 s, ~140 KB). Its `preview_url` is a PNG of the +first frame, which is all v2.19.0 kept. + +## Changes + +| Area | Change | +|---|---| +| `reply_context._from_status` | A `gifv` attachment's `url` goes into the new `video` field (the preview stays in `photo`, used as the poster) | +| Migration 025 | `reply_contexts.video`; fediverse rows with a photo get `source = NULL`, so the worker's `refresh_stale` fetches them once more | +| `avatars.fetch_video` | Saves the MP4 as `DATA_PATH/previews/.mp4` (8 MB cap, must have an `ftyp` box); `fill_missing`/`remove_unused` cover it | +| `avatars._save` | Animated GIF/WebP/PNG previews are saved as animated WebP (frames narrowed to 640 px, at most 300 frames) instead of their first frame | +| `/previews/` | Also serves `.mp4` as `video/mp4` | +| Template | `