Buttondown vs Gumloop

Buttondown publishes a dated entry almost every day, and the overwhelming majority are single bug fixes, several credited by name to the subscriber who reported them. The current window is nine-tenths repair work — stretched newsletter icons in the archive, a portal 403 for subscribers with many accounts, rejected WebP uploads, cursor placement between stacked tables. Two genuine features sit at the window's edges: filtered blocks on July 31 and flexible monthly RSS scheduling on August 1. Every entry is titled with its date alone, so the titles carry no signal until rewritten.

The shape here is a maintained product rather than one under redirection: the fix stream is dense, specific and largely user-reported, which reads as a small team with an engaged base rather than as instability. The features that do land are narrow gap-fillers — letting a monthly send fall on the 29th, making one section of an email visible to a single audience type — each closing a limitation someone actually hit. Filtered blocks are the only recent change that adds a primitive instead of a setting, since audience-scoped sections are where segmentation inside a single send begins.

The likeliest next step is more surface built on filtered blocks, as audience-scoped content is the one recent addition with somewhere further to go. Otherwise the daily fix cadence should simply continue; nothing in this window points to a larger change.