v2.6.0 Feeds that no longer take a single node's word for what exists, an editor that tells the author what will happen before it happens, and the refreshed Terms of Service and Privacy Policy (MRs !182 to !202). - A post now has to be corroborated by two verified nodes before it appears in a feed. The chain leaves no tombstone for a deleted post, so a feed built from whatever one node returns keeps showing posts that no longer exist; corroboration is what stands in for the tombstone. The author's own post is the exception and appears as soon as one node has it, because the author already knows it exists. A merged feed is ordered from a single node rather than by rank across nodes, which is what keeps the order stable. - A node that is down no longer holds up the reader's first feed. The pool waits for a quorum, not for everyone, so one unreachable node costs latency and not a blank page. - A deleted post stays deleted whatever a stale node serves, and deleting one now reports progress and confirms, instead of appearing to do nothing while the operation is in flight. - The editor rejects a beneficiary that is not an account. A name that is not an account makes the chain reject the whole transaction, so the post never published and the author was told nothing: the editor reported success and the post was gone. Names are now checked before the transaction is built, in the field where the mistake was made, and a lookup that fails leaves the name undecided so a node having a bad minute can never block a publish. - The confirmation dialog names the operation being confirmed instead of the chain operation behind it. - Voting says more and guesses less: a closed payout window blocks the vote and explains why rather than failing silently, and a vote cast after the window is presented as a signal rather than as a mistake, naming the account and what is missing. - New in the reading and writing surface: an open reply box under every post, a lightbox for the images in a body, a back-to-top button on long views placed clear of the assistant's corner, and the author landing on their posts tab after publishing instead of somewhere they have to navigate back from. - Leaving the editor no longer depends on the browser's history behaving, which is what trapped authors on iOS, and a collection stored as null is no longer read as an absent collection, which is what made parts of the interface render empty rather than render nothing. - A submit that throws can no longer leave the form stuck behind its spinner, and a failover is verified before anyone is warned about it, with the client failing back once the node answers again. - The Terms of Service and the Privacy Policy are rewritten: plainer language, neutral governing law, the scope extended to the wallet, Blurt Dollars and an inherited DMCA address removed, and a Cookie Disclosure stating that only session cookies are used, with no third-party or tracking cookies. Contact addresses across the application now use the official @blurt.blog mailboxes. - The fake Blurt airdrop links are blocked in the phishing list. Both forms of the link were added to the three copies of that list, which is what stops the copies from drifting apart again. - Interface work across the application, most of it on phones: the posts header keeps its controls on screen, the stacked mobile header row gets its spacing and its side, the view and reblog glyphs preview what a click will bring rather than what is already the case, comment and reply footers match the post editor's layout, the back button closes a modal instead of navigating away with one still open, and the follow pills on a cover keep readable text in dark mode. The translations are finished for every string the application actually uses. - A scheduled pipeline now runs only the environments watchdog, which compares what each environment serves against the history of the default branch and fails when an environment serves something that branch does not know.