Version 2.1.20 of Claude Code shipped a change that re­placed every file read and every search pat­tern with a sin­gle, use­less sum­mary line.

Where you used to see:

You now get:

“Searched for 1 pat­tern.” What pat­tern? Who cares.

You’re pay­ing $200 a month for a tool that now hides what it’s do­ing with your code­base by de­fault.

Across mul­ti­ple GitHub is­sues opened for this, all com­ments are pretty much say­ing the same thing: give us back the file paths, or at min­i­mum, give us a tog­gle.

For the ma­jor­ity of users, this change is a nice sim­pli­fi­ca­tion that re­duces noise.

What ma­jor­ity? The change just shipped and the only re­sponse it got is peo­ple com­plain­ing.

Then when pressed, the fix of­fered was­n’t to re­vert or add a tog­gle. It was: “just use ver­bose mode.”

A big ’ole dump of think­ing traces, hook out­put, full sub­agent tran­scripts, and en­tire file con­tents into your ter­mi­nal. People ex­plained, re­peat­edly, that they wanted one spe­cific thing: file paths and search pat­terns in­line. Not a fire­hose of de­bug out­put.

The de­vel­op­er’s re­sponse to that?

I want to hear folks’ feed­back on what’s miss­ing from ver­bose mode to make it the right ap­proach for your use case.

Read that again. Thirty peo­ple say “revert the change or give us a tog­gle.” The an­swer is “let me make ver­bose mode work for you in­stead.”

As one com­menter put it:

If you are go­ing to dis­play some­thing like ‘Searched for 13 pat­terns, read 2 files’ there is noth­ing I can do with that in­for­ma­tion. You might as well not dis­play it at all.

Several ver­sions later, the “fix” is to keep mak­ing ver­bose mode less and less ver­bose by re­mov­ing think­ing traces and hook out­put so it be­comes a tol­er­a­ble way to get your file paths back. But ver­bose mode still dumps full sub-agent out­put onto your screen, among other things.

Before, when Claude spawned mul­ti­ple sub-agents you’d see a com­pact line-by-line stream of what each one was do­ing, just enough to glance at. Now you get walls of text from mul­ti­ple agents at once. So what’s the plan? Keep strip­ping things out of ver­bose mode one by one un­til it’s no longer ver­bose? Where does it end? At some point you’ve just rein­vented a con­fig tog­gle with ex­tra steps.

And the peo­ple who were us­ing ver­bose mode for think­ing and hooks now need to press Ctrl+O to get what they had by de­fault. So in­stead of fix­ing one prob­lem, you cre­ated two.

People are pin­ning them­selves to ver­sion 2.1.19 and in the mean­time the fix every­one is ask­ing for, a sin­gle boolean con­fig flag, would take less ef­fort to im­ple­ment than all the ver­bose mode surgery that’s been done in­stead.

Anthropic dur­ing the Super Bowl: we’d never dis­re­spect our users.

Anthropic on GitHub: have you tried ver­bose mode?

age ver­i­fies your ac­count au­to­mat­i­cally as an adult on any web­site us­ing k-id

made by xyzeva and Dziurwa, greetz to am­pli­tudes (for pre­vi­ous work)

this script does­n’t work any­more and has been tem­porar­ily dis­abled while we’re look­ing into a fix.

k-id, the age ver­i­fi­ca­tion provider dis­cord uses does­n’t store or send your face to the server. instead, it sends a bunch of meta­data about your face and gen­eral process de­tails. while this is good for your pri­vacy (well, con­sid­er­ing some other providers send ac­tual videos of your face to their servers), its also bad for them, be­cause we can just send le­git­i­mate look­ing meta­data to their servers and they have no way to tell its not le­git­i­mate.

while this was easy in the past, k-id’s part­ner for face ver­i­fi­ca­tion (faceassure) has made this sig­nif­i­cantly harder to achieve af­ter am­pli­tudes k-id ver­i­fier was re­leased, (which does­n’t work any­more be­cause of it.)

with dis­cord’s de­ci­sion of mak­ing the age ver­i­fi­ca­tion re­quire­ment global, we de­cided to look into it again to see if we can by­pass the new checks.

the first thing we no­ticed that the old im­ple­men­ta­tion does­n’t send when com­par­ing a le­git­i­mate request pay­load with a gen­er­ated one, is its miss­ing en­crypt­ed_­pay­load, auth_­tag, time­stamp and iv in the body.

look­ing at the code, this ap­pears to be a sim­ple AES-GCM ci­pher with the key be­ing nonce + time­stamp + trans­ac­tion_id, de­rived us­ing HKDF (sha256). we can eas­ily repli­cate this and also cre­ate the miss­ing parameters in our gen­er­ated out­put.

heres where it kind of gets tricky, even af­ter per­fectly repli­cat­ing the en­cryp­tion, our verification at­tempt still does­n’t suc­ceed, so they must also be do­ing checks on the ac­tual payload.

af­ter some trial and er­ror, we nar­rowed the checked part to the pre­dic­tion ar­rays, which are out­puts, pri­ma­ry­Out­puts and raws.

turns out, both out­puts and pri­ma­ry­Out­puts are gen­er­ated from raws. ba­si­cally, the raw numbers are mapped to age out­puts, and then the out­liers get re­moved with z-score (once for pri­ma­ry­Out­puts and twice for out­puts).

there is also some other dif­fer­ences:

* xS­caled­Shif­tAmt and yScaled­Shif­tAmt in pre­dic­tions are not ran­dom but

rather can be one of two val­ues

* it is checked that the me­dia name (camera) matches one of your me­dia de­vices in the ar­ray of

de­vices

* it is checked if the states com­ple­tion times match the state time­line

with all of that done, we can of­fi­cially ver­ify our age as an adult. all of this code is open source and avail­able on github, so you can ac­tu­ally see how we do this ex­actly.

Your Peon pings you when Claude Code needs at­ten­tion.

Claude Code does­n’t no­tify you when it fin­ishes or needs per­mis­sion. You tab away, lose fo­cus, and waste 15 min­utes get­ting back into flow. peon-ping fixes this with Warcraft III Peon voice lines — so you never miss a beat, and your ter­mi­nal sounds like Orgrimmar.

See it in ac­tion → peon-ping.ver­cel.app

curl -fsSL https://​raw.githubuser­con­tent.com/​tonyy­ont/​peon-ping/​main/​in­stall.sh | bash

One com­mand. Takes 10 sec­onds. ma­cOS and WSL2 (Windows). Re-run to up­date (sounds and con­fig pre­served).

Plus Terminal tab ti­tles (● pro­ject: done) and desk­top no­ti­fi­ca­tions when your ter­mi­nal is­n’t fo­cused.

Need to mute sounds and no­ti­fi­ca­tions dur­ing a meet­ing or pair­ing ses­sion? Two op­tions:

peon –pause # Mute sounds

peon –resume # Unmute sounds

peon –status # Check if paused or ac­tive

peon –packs # List avail­able sound packs

peon –pack

Tab com­ple­tion is sup­ported — type peon –pack to see avail­able pack names.

Pausing mutes sounds and desk­top no­ti­fi­ca­tions in­stantly. Persists across ses­sions un­til you re­sume. Tab ti­tles re­main ac­tive when paused.

“volume”: 0.5,

“categories”: {

“greeting”: true,

“acknowledge”: true,

“complete”: true,

“error”: true,

“permission”: true,

“annoyed”: true

* vol­ume: 0.0–1.0 (quiet enough for the of­fice)

* an­noyed_thresh­old / an­noyed_win­dow_sec­onds: How many prompts in N sec­onds trig­gers the easter egg

* pack­_ro­ta­tion: Array of pack names (e.g. [“peon”, “sc_kerrigan”, “peasant”]). Each Claude Code ses­sion ran­domly gets one pack from the list and keeps it for the whole ses­sion. Leave empty [] to use ac­tive_­pack in­stead.

peon –pack ra2_so­vi­et_en­gi­neer # switch to a spe­cific pack

peon –pack # cy­cle to the next pack

peon –packs # list all packs

{ “active_pack”: “ra2_soviet_engineer” }

Want to add your own pack? See CONTRIBUTING.md.

bash ~/.claude/hooks/peon-ping/uninstall.sh

* ma­cOS (uses af­play and AppleScript) or WSL2 (uses PowerShell MediaPlayer and WinForms)

peon.sh is a Claude Code hook reg­is­tered for SessionStart, UserPromptSubmit, Stop, and Notification events. On each event it maps to a sound cat­e­gory, picks a ran­dom voice line (avoiding re­peats), plays it via af­play (macOS) or PowerShell MediaPlayer (WSL2), and up­dates your Terminal tab ti­tle.

Sound files are prop­erty of their re­spec­tive pub­lish­ers (Blizzard Entertainment, EA) and are in­cluded in the repo for con­ve­nience.

is a se­nior re­viewer with over twenty years of ex­pe­ri­ence. She cov­ers smart home, IoT, and con­nected tech, and has writ­ten pre­vi­ously for Wirecutter, Wired, Dwell, BBC, and US News.

is a se­nior re­viewer with over twenty years of ex­pe­ri­ence. She cov­ers smart home, IoT, and con­nected tech, and has writ­ten pre­vi­ously for Wirecutter, Wired, Dwell, BBC, and US News.

Posts from this au­thor will be added to your daily email di­gest and your home­page feed.

People voiced con­cerns across so­cial me­dia that the AI-powered tech­nol­ogy Ring uses to iden­tify dogs could soon be used to search for hu­mans. Combined with Ring’s re­cent roll­out of its new fa­cial recog­ni­tion ca­pa­bil­ity, it feels like a short leap for a pet-find­ing fea­ture to be turned into a tool for state sur­veil­lance.

Ring spokesper­son Emma Daniels told The Verge that Search Party is de­signed to match im­ages of dogs and is “not ca­pa­ble of pro­cess­ing hu­man bio­met­rics.” Additionally, she main­tains that the Familiar Faces fa­cial recog­ni­tion fea­ture is sep­a­rate from Search Party. It op­er­ates on the in­di­vid­ual ac­count level, she said, and there’s no com­mu­nal shar­ing as there is with Search Party.

While Familiar Faces is opt-in for each user, Search Party is en­abled by de­fault on any out­door cam­era en­rolled in Ring’s sub­scrip­tion plan. It works by us­ing AI to scan footage in the cloud for the miss­ing dog once the owner up­loads a pic­ture to Ring’s Neighbors app. If a match is found, Ring alerts the cam­er­a’s owner, who can then choose to share the video or no­tify the owner through the app.

While that may be the case to­day, I asked whether Ring cam­eras could one day be used to specif­i­cally search for peo­ple. “The way these fea­tures are built, they are not ca­pa­ble of that to­day,” she said. “We don’t com­ment on fea­ture road maps, but I have no knowl­edge or in­di­ca­tion that we’re build­ing fea­tures like that at this point.”

Ring users can cur­rently share footage from their cam­eras with lo­cal law en­force­ment dur­ing an ac­tive in­ves­ti­ga­tion through a fea­ture called Community Requests. Unlike pre­vi­ous Ring po­lice part­ner­ships, Community Request goes through third-party com­pa­nies — the Taser com­pany Axon and, soon, Flock. “The rea­son we did that is these third-party ev­i­dence man­age­ment sys­tems of­fer a much more se­cure chain of cus­tody,” says Daniels. If a user de­clines a re­quest, no one will be no­ti­fied.

The com­pany main­tains that nei­ther the gov­ern­ment nor law en­force­ment can ac­cess its net­work, and that footage is shared only by users or in re­sponse to a le­gal re­quest. Daniels re­it­er­ated what the com­pany had pre­vi­ously told The Verge, that it has no part­ner­ships with ICE or any other fed­eral agency, and said you can see every re­quest agen­cies have made on its Neighbors app pro­file.

Additionally, the Flock in­te­gra­tion is not cur­rently live, al­though Daniels had no up­date on the com­pa­ny’s plans for the part­ner­ship fol­low­ing the back­lash. She re­ferred me to an ear­lier re­sponse. “As we ex­plore the in­te­gra­tion, we will en­sure the fea­ture is built for the use of lo­cal pub­lic safety agen­cies only — which is what the pro­gram is de­signed for.”

The prob­lem is that there’s noth­ing pre­vent­ing lo­cal agen­cies from shar­ing footage with fed­eral ones. And while the Super Bowl ad played up heart­warm­ing im­ages of a girl re­united with her puppy, the leap to this tech­nol­ogy that can track peo­ple in your neigh­bor­hood is still very small. Combined with gov­ern­ment over­reach, it’s not hard to imag­ine how a pow­er­ful net­work of AI-enabled cam­eras goes from find­ing lost dogs to hunt­ing peo­ple.

Siminoff said he came back be­cause of the pos­si­bil­i­ties AI brings. With this tech­nol­ogy, he be­lieves neigh­bor­hood cam­eras could be used to vir­tu­ally “zero out crime” within a year. Given these stated goals and the new ca­pa­bil­i­ties AI can bring, why would­n’t Ring be plan­ning to add some form of Search Party for People to its cam­eras?

Eliminating crime is an ad­mirable goal, but his­tory has shown that tools ca­pa­ble of large-scale sur­veil­lance are rarely lim­ited to their orig­i­nal pur­pose. Ring has a re­spon­si­bil­ity here to pro­tect its users, which it says it is do­ing. But ul­ti­mately, it comes down to how much you can trust a com­pany — and the com­pany it keeps — to never over­step. If Ring is cloak­ing its am­bi­tions be­hind our in­stinct to pro­tect our furry friends, that trust will be hard to find.

Fluorite is the first con­sole-grade game en­gine fully in­te­grated with Flutter.

Its re­duced com­plex­ity by al­low­ing you to write your game code di­rectly in Dart, and us­ing all of its great de­vel­oper tools. By us­ing a FluoriteView wid­get you can add mul­ti­ple si­mul­ta­ne­ous views of your 3D scene, as well as share state be­tween game Entities and UI wid­gets - the Flutter way!

At the heart of Fluorite lies a data-ori­ented ECS (Entity-Component-System) ar­chi­tec­ture. It’s writ­ten in C++ to al­low for max­i­mum per­for­mance and tar­geted op­ti­miza­tions, yield­ing great per­for­mance on lower-end/​em­bed­ded hard­ware. At the same time, it al­lows you to write game code us­ing fa­mil­iar high-level game APIs in Dart, mak­ing most of your game de­vel­op­ment knowl­edge trans­ferrable from other en­gines.

Your browser does not sup­port the video tag.

This fea­ture en­ables 3D Artists to de­fine “clickable” zones di­rectly in Blender, and to con­fig­ure them to trig­ger spe­cific events! Developers can then lis­ten to onClick events with the spec­i­fied tags to trig­ger all sorts of in­ter­ac­tions! This sim­pli­fies the process of cre­at­ing spa­tial 3D UI, en­abling users to en­gage with ob­jects and con­trols in a more in­tu­itive way.

Your browser does not sup­port the video tag.

Powered by Google’s Filament ren­derer, Fluorite lever­ages mod­ern graph­ics APIs such as Vulkan to de­liver stun­ning, hard­ware-ac­cel­er­ated vi­su­als com­pa­ra­ble to those found on gam­ing con­soles. With sup­port for phys­i­cally-ac­cu­rate light­ing and as­sets, post-pro­cess­ing ef­fects, and cus­tom shaders, the de­vel­op­ers can cre­ate vi­su­ally rich and cap­ti­vat­ing en­vi­ron­ments.

Your browser does not sup­port the video tag.

Thanks to its Flutter/Dart in­te­gra­tion, Fluorite’s scenes are en­abled for Hot Reload! This al­lows de­vel­op­ers to up­date their scenes and see the changes within just a cou­ple frames. This sig­nif­i­cantly speeds up the de­vel­op­ment process, en­abling rapid it­er­a­tion and test­ing of game me­chan­ics, as­sets, and code.

Have a ques­tion about this pro­ject? Sign up for a free GitHub ac­count to open an is­sue and con­tact its main­tain­ers and the com­mu­nity.

By click­ing “Sign up for GitHub”, you agree to our terms of ser­vice and pri­vacy state­ment. We’ll oc­ca­sion­ally send you ac­count re­lated emails.

Already on GitHub? Sign in

to your ac­count

I re­cently wrote about what the longevity ex­perts don’t tell you. Since then, I’ve been think­ing about why so many of the peo­ple in this space are ob­sessed with blood trans­fu­sions specif­i­cally. It seemed like a strange fix­a­tion — un­til I looked at the ev­i­dence prop­erly.

I think they’re vam­pires. Not metaphor­i­cally. I think the mod­ern longevity move­ment is a vam­pire dis­clo­sure pro­gram.

In 1864, a French phys­i­ol­o­gist named Paul Bert sur­gi­cally con­nected two mice so they shared a cir­cu­la­tory sys­tem.1 When he con­nected an old mouse to a young one, the old mouse got younger. The tech­nique is called para­bio­sis, from the Greek para (next to) and bios (life), which is also how vam­pires have his­tor­i­cally de­scribed feed­ing.

By the 1950s, re­searchers at Cornell had ex­tended this work and found that old rats con­nected to young rats lived four to five months longer than con­trols.2 The sci­en­tific com­mu­nity filed this un­der “interesting but im­prac­ti­cal” and moved on.

Then in 2005, Stanford re­searchers re­vived the tech­nique and showed that within five weeks, old mice con­nected to young mice had mus­cle and liver tis­sue that re­sem­bled young tis­sue.3 This made in­ter­na­tional head­lines. The fram­ing was: “Scientists dis­cover young blood re­verses ag­ing.”

The vam­pires, pre­sum­ably, were not sur­prised.

Pale. Gaunt. Appears to not age but also to never have been young.4

Told Inc. mag­a­zine that he finds para­bio­sis “really in­ter­est­ing” and that his in­ter­est is per­sonal rather than com­mer­cial.5 His com­pa­ny’s chief med­ical of­fi­cer sub­se­quently con­tacted Ambrosia, a startup that charged $8,000 to in­ject you with young peo­ple’s blood plasma.6 The com­pany was called Ambrosia — the food of the gods. Subtle.

Has taken hu­man growth hor­mones and in­ves­ti­gated ex­treme calo­rie re­stric­tion.7 Gawker re­ported he was spend­ing $40,000 per quar­ter on blood in­fu­sions from an 18-year-old, though this was never con­firmed.8

Co-founded Palantir, a com­pany whose name comes from the all-see­ing stones in Lord of the Rings.9 Palantír lit­er­ally means “far-seeing.” You know what else is far-see­ing? A crea­ture that has been alive for cen­turies.

Destroyed Gawker, the me­dia out­let that re­ported on his blood habits. He se­cretly funded a $10 mil­lion law­suit that re­sulted in a $140 mil­lion judge­ment, bank­rupt­ing the com­pany.10 When a jour­nal­ist gets too close to re­veal­ing a vam­pire, the vam­pire de­stroys the jour­nal­ist’s en­tire or­ga­ni­za­tion. This is stan­dard vam­pire op­er­a­tional se­cu­rity. It has been stan­dard since at least the 1600s.

Bought a 477-acre es­tate on the shores of Lake Wanaka in New Zealand’s South Island.11 Remote. Southern hemi­sphere. Minimal sun­light scrutiny. He has called New Zealand his “utopia.”12

Thiel told Business Insider in 2012 that death is “a prob­lem that can be solved.”13 This is not the lan­guage of a man who fears death. This is the lan­guage of a man who solved it in the 1400s and is tired of pre­tend­ing.

Johnson is more com­pli­cated, be­cause he ap­pears to be con­duct­ing his vam­pirism in pub­lic. This is ei­ther a strate­gic er­ror or an un­prece­dented act of courage.

He trans­fused his 17-year-old son’s blood plasma into his own body. His son, Talmage, also re­ceived Johnson’s plasma in re­turn. Johnson framed this as “multi-generational plasma ex­change.”14 Vampires have his­tor­i­cally called this “turning.”

He dis­con­tin­ued the blood ex­change af­ter data showed “no ben­e­fits.”15 A sus­pi­cious per­son might note that a vam­pire would say ex­actly this af­ter the me­dia got too in­ter­ested.

His skin has the grey, translu­cent qual­ity of some­one who has op­ti­mised past the point of ap­pear­ing hu­man. He is 48 but looks like a very well-pre­served 300.

He pub­licly tracks his erec­tions, sleep, body fat, and or­gan age with the zeal of some­one doc­u­ment­ing a body he has not yet fully fig­ured out how to op­er­ate.16

His com­pany is called Blueprint. As in: he is shar­ing the blue­print.

The longevity com­mu­nity pre­sents para­bio­sis re­search as a mod­ern sci­en­tific break­through. This is wrong. Blood-based life ex­ten­sion has been doc­u­mented for mil­len­nia:

Roman spec­ta­tors rushed into are­nas to drink the blood of fallen glad­i­a­tors, be­liev­ing it trans­ferred vi­tal­ity.17 The sci­en­tific com­mu­nity calls this “anecdotal.” Vampires call it “dining out.”

In 1489, the Italian philoso­pher and Catholic priest Marsilio Ficino pub­lished De Vita Libri Tres, in which he ex­plic­itly rec­om­mended that the el­derly suck the blood of a youth from a vein in the left arm. His ex­act words: “Why should­n’t our old peo­ple, namely those who have no other re­course, like­wise suck the blood of a youth?”18 He pub­lished this. Openly. In a book. As a priest.

Elizabeth Báthory, a 16th-century Hungarian no­ble­woman, al­legedly tor­tured and mur­dered hun­dreds of young women. Legends that she bathed in their blood to re­tain her youth first ap­peared in print over a cen­tury af­ter her death and are likely em­bell­ished, but she was nonethe­less con­fined — pos­si­bly walled up — in a room in her own cas­tle un­til she died.19 Which is ex­actly what you’d ex­pect hu­mans to do to a vam­pire they could­n’t kill.

Bram Stoker pub­lished Dracula in 1897. The novel fea­tures a cen­turies-old aris­to­crat who sus­tains him­self on young blood, sleeps in un­usual con­di­tions, has ex­tra­or­di­nary phys­i­cal abil­i­ties for his ap­par­ent age, and is even­tu­ally de­stroyed by a group of peo­ple who fig­ure out what he is. Stoker, a the­atre man­ager with no med­ical back­ground, some­how de­scribed the ba­sic mech­a­nism of het­e­rochronic para­bio­sis al­most per­fectly — ninety years be­fore Stanford “discovered” it.

The stan­dard ex­pla­na­tion is that Stoker drew on Eastern European folk­lore. The al­ter­na­tive ex­pla­na­tion is that Stoker drew on Eastern European vam­pires.

Here’s what’s gen­uinely in­ter­est­ing. Recent re­search from UC Berkeley sug­gests that the ben­e­fit of young blood might not come from some­thing in the young blood. It might come from di­lut­ing the old blood.20 The young blood does­n’t add youth. It re­moves age.

If true, this re­frames the en­tire vam­pire mythol­ogy. Vampires don’t drink blood be­cause young blood con­tains an elixir. They drink blood be­cause their own blood ac­cu­mu­lates fac­tors that ac­cel­er­ate ag­ing, and they need to pe­ri­od­i­cally di­lute it. Feeding is­n’t nu­tri­tion. It’s dial­y­sis.

This also ex­plains why vam­pires need to feed reg­u­larly. The ef­fect is tem­po­rary. The old blood fac­tors re­build. This is con­sis­tent with the Stanford mouse data, where the re­ju­ve­nat­ing ef­fects di­min­ished af­ter the mice were sep­a­rated.21

I be­lieve we are watch­ing a care­fully man­aged dis­clo­sure:

Phase 2 (2005–2015): “Breakthrough” pa­pers from Stanford, Harvard, Berkeley. Seed the idea that blood-based re­ju­ve­na­tion is sci­en­tif­i­cally plau­si­ble rather than su­per­nat­ural.23

Phase 3 (2016–2023): Early adopters go pub­lic. Thiel funds blood star­tups. Johnson trans­fuses his son on cam­era. The pub­lic be­gins to as­so­ci­ate blood trans­fu­sion with ec­cen­tric bil­lion­aires rather than with un­dead preda­tors. This is a crit­i­cal nar­ra­tive shift.

Phase 4 (2024–present): Normalisation. Podcasts. Netflix doc­u­men­taries.24 The word “parabiosis” en­ters main­stream vo­cab­u­lary. By the time full dis­clo­sure hap­pens, the pub­lic will have been primed to see vam­pirism as a “wellness pro­to­col” rather than a curse.

The one thing the longevity-vam­pire com­mu­nity has not yet learned from Dracula is op­er­a­tional se­cu­rity.

Dracula op­er­ated in si­lence for cen­turies. He did­n’t have a pod­cast. He did­n’t track his erec­tion qual­ity on a pub­lic dash­board. He did­n’t ap­pear on Netflix. He un­der­stood that the fun­da­men­tal rule of be­ing a vam­pire is: don’t talk about be­ing a vam­pire.

Johnson, Thiel, and their co­hort have bro­ken this rule com­pre­hen­sively. Whether this rep­re­sents a new era of trans­parency or a cat­a­strophic strate­gic mis­cal­cu­la­tion re­mains to be seen.

In the mean­time, I will be mon­i­tor­ing their blood work with in­ter­est.

Here’s where things are on this par­tic­u­lar February 11: we just shipped 7.0 for Mac and iOS, and now we’re work­ing on NetNewsWire 7.0.1.

After a big re­lease, no mat­ter how care­ful we are, there are of­ten some re­gres­sions to fix and tweaks to make right away, so we’re work­ing on those. Here’s the mile­stone with the cur­rent to-do list.

Big pic­ture: we still have a lot of bugs to fix, lots of tech debt to deal with, and lots of pol­ish-needed ar­eas of the app. With Brent’s re­tire­ment last year we’ve been able to go way faster on deal­ing with all this. We plan to keep up the pace.

Here are our cur­rent plans:

For NetNewsWire 7.1 we’re fo­cus­ing on sync­ing fixes and im­prove­ments.

NetNewsWire 7.2 does­n’t have a fo­cus yet. Could end up be­ing UX fixes and pol­ish, could be some­thing else. Could be a pot­pourri, though we do pre­fer hav­ing a fo­cus when pos­si­ble.

We don’t have a NetNewsWire 7.3 plan yet — that’s too far out. Depends on what ac­tu­ally hap­pens with 7.1 and 7.2, and it de­pends on what Apple adds to our to-do list at WWDC this year. (Touchscreen Macs? Folding iPhones? Big new Swift fea­tures? Who knows!)

Note that we do add and re­move tick­ets from mile­stones at any time — none of this is set in stone, of course.

It’s NetNewsWire’s birth­day, but that’s a day to look for­ward, not to look back. The very best ver­sions of NetNewsWire are still to come!