views: a replay inherits its livestream's views, and livestream view totals are kept per record. The running "views" count of a stream (playback sessions started, the number beside the concurrent viewers) lived in one row per streamer that was reset whenever their livestream record changed, so a title change that made a new record, or the next stream, threw the previous count away, and a stream's replay started from zero while the VOD's own view counting (CDN access logs, aggregated later) caught up. The totals are now one row per livestream record (livestream_view_totals; a node's existing per-streamer row is carried over once at startup, never overwriting a count that has moved on), and a video's view summary (getVideo, getVideoList) adds the totals of the place.stream.livestream records its connections point at, when they belong to the video's author: the records the Livestreams tab and the operator's finalize connect a recording to, so an event's replay shows the event's views from the moment it is published. Other authors' records are ignored, so connecting to someone else's popular stream inflates nothing (cherry picked from commit e0f685183665b350e067672049368054d01af218)