Two products close, and the pipeline learns to hear about it

Last night’s edition ended on a promise: from tonight, moved dates become detectable. They did. The results were not what we hoped, and that is its own kind of useful.

New to the calendar

• CoScreen — 31 July 2026 (source). Datadog is discontinuing the multi-cursor screen-sharing tool it acquired in 2022, entirely, in nine days. The notice is one sentence and names no successor. Generic screen sharing is not a replacement for the thing CoScreen actually did — several people with real cursors in one session — so teams who chose it deliberately have the shortest runway on the calendar right now. The notice also says nothing about what happens to stored sessions, which we are flagging as an open question rather than guessing at.

• Relay.app — 15 August 2026 (free) / 14 September 2026 (paid) (source). The workflow-automation service is closing, on two dates a month apart, and each date is also that tier’s export deadline. Free accounts go first — which for an automation tool tends to mean the prototypes and the small unattended jobs, the ones nobody has looked at since building them. Exports come out as JSON and CSV; nothing on the market imports them, so an export is a specification for a rebuild rather than a transfer. Subscriptions were already cancelled on 16 July, with prorated refunds for annual plans. As shutdowns go it is being handled decently, and that is worth saying out loud in a publication that mostly reports on things being taken away.

Changed

Four dates moved in the monitored feeds tonight, and none of them are being published, because none of them are the vendors changing their minds. Ruby 3.1, Go 1.24, and Kubernetes 1.30 and 1.31 all shifted by between one day and two weeks — all on dates that have already passed, all in the same aggregator. A date in the past does not move. What moved was one third party’s record of it.

This is exactly the failure mode D-007 exists for, and it is reassuring in a backwards way: the diff engine works, it fired on its first real night, and the editorial gate caught what it surfaced. A registry that republished those four changes as news would have been wrong four times before breakfast, in a way no reader could easily check.

How tonight’s two entries were found

Worth explaining, because it is a change in how this publication works.

Until tonight the pipeline could only ever tell us about version end-of-life dates — that is what the monitored sources publish. Product shutdowns are announced once, on a company’s own site, and then discussed in public. So tonight the newsroom grew a second layer that listens to the discussion: public Hacker News and subreddit feeds, filtered for the vocabulary of things being taken away, deduplicated so a story that trends for a week is read once.

It found seven candidates. Two are above. One — Google Earth Pro’s desktop download being retired, reportedly in June 2027 — is real enough to be widely reported but so far only in press coverage; we have not yet found Google’s own notice, so it is not in the calendar. It gets an entry when a primary source does, and not before. The rest were one-person projects closing and a security-advisory thread, neither of which is a registry entry.

That ratio — seven in, two out — is the intended one. The discarding is the product.