Home / Articles / Feisty Duck, briefed / Versions / v1.1.0
Feisty Duck, briefed: what changed in v1.1.0
From v1.0.0 (2026-10-25, 2784e37ec) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 47 unchanged. About 0 words added and 129 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot fd-pages.webp | images/ | Feisty Duck on 25 October 2026: Feistyits Duck News, the livenews front pagepage, of cryptography and security news; the Cryptography & Security Newsletter, with issues to #141, "Get Ready for Seven-Day Certificates"; thenewsletter, SSL/TLS and PKI History, starting with SSL v2 in 1994; and the free Bulletproof TLS Guide, last updated on 16 June 2026.Guide. | screenshot
11 unchanged paragraphs, under In short {#in-short}, Brief: what Feisty Duck is {#brief}, Feisty Duck News {#news}
!shot fd-numbers.webp | images/ | Feisty Duck,Duck in numbers: the 100 items in theits news feed betweenfrom 1 September andto 25 October 2026, by category, led by post-quantum cryptography (24), PKI (21), cryptography (18) and security (17); and the 174 events in the SSL/TLS and PKIits history, by decade, 109 of them in the 2010s, scored 115 positive and 56 negative.decade. | chart
20 unchanged paragraphs, under The rest of the site {#site}, Debrief: what we share {#debrief}, How we could integrate {#integrate}
!shot fd-flow.webp | images/ | How Feisty Duck and our newsrooms could fit together:together, Feistyfrom Duck curates and explains; we link our crypto, TLS and PKI claims tolinking its guide,guide booknow and newsletter as an anchor, now; we could runto a crypto and TLS wire that follows the same public sources and credits Feisty Duck News; we could add provenance to the LLM summaries of items we cite; and, with permission, keep the history as a graph and capture pages in a vault.wire. | process
14 unchanged paragraphs, under Is there a need for a vault? {#vault}, What this does not claim {#limits}, Where this comes from {#sources}