1 Commits (dev)

Author	SHA1	Message	Date
Ashley	78c0b65222	Record a genuinely empty feed under its own key ... A feed with nothing in it and a feed that was never built look the same from Redis: neither has a key. That is why the read path could not tell "nothing to show" from "needs building", and why the only bookkeeping it had was a 300-second marker written before the outcome was known and evicted by nothing. The trait now carries an empty-warm guard keyed on the resolved feed key, holding the timestamp at which it lapses with a matching cache TTL. It is written only by a warm that published nothing and resolved every candidate it found: a candidate that would not resolve means the warm did not finish, so the feed stays eligible and the failure is logged. A forced warm never consults it. Eviction is automatic for the instance-wide feeds through setAdd, and explicit for home feeds, which have no key for a write to reach: the author's own post, a followed local or remote account posting, a new follow, and a followed hashtag getting a post all clear it. None of them creates the feed key, so a follower who has never loaded a timeline still does not get one.	7 days ago