Give Plaza its own page, and its name everywhere it was anonymous - #6
Conversation
The site described "the flagship client" in three places and never once said what it was called, which makes the one app I am building hardest to find the one nobody can look up. A page of its own now: reading before identity, where the key actually lives (a separate keyholder process, or your own signer, never the app), what is in it today, why replaceable events get read back before they are written, and the frame budget the feed holds while scrolling. The home page, the ecosystem list and the roadmap all name it and link to it. It says plainly that there is nothing to download yet and gives the source build instead. A one-line installer belongs on this page the day the first tag exists and not an hour before, because a curl that resolves to "no release published yet" is worse than no curl at all.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Review checked every sentence against the code and found six that do not hold. Key custody was the bad one. "Plaza does not hold your secret key" was stated absolutely, and a bare source build falsifies it: there is no ceremony window in zig-out, so pasting an existing key lands in Plaza itself and is written to ~/.plaza. The app already knows this and changes its own wording for it. The page now says where the key goes on each path, and names the exception rather than leaving a reader to discover it. Follower counts. The page claimed profile pages show follows and followers. Plaza deliberately shows only a following count, with the reasoning written into profileCounts and a test holding it there: following is a number someone states about themselves, followers is one nothing on your disk can know. I turned the claim into the restraint, which is the more interesting thing to say anyway. Windows CI. "Linux and Windows build and test in CI" is false; the matrix is ubuntu-latest alone, because the relay transport needs libc getaddrinfo and Zig's standard library does not declare it for Windows. The same sentence is wrong in the app's README, fixed separately. Also: relay lists are rebuilt from the app's own slots, so "keeps the parts it does not understand" is true of follow lists and profiles and not of those. Plaza does not use the core's outbox model yet. And a remembered follow waits for a follow list to arrive rather than always completing, so the sentence promising otherwise is softened. The home page's app card still said "Flagship client" and pointed at the roadmap, which is exactly what the last commit claimed to have fixed everywhere. It says Plaza and links to the page. The roadmap's year ahead listed threads, reactions, quotes and media as future work while the new page lists them as shipped. Two public pages disagreeing about what exists is worse than either being wrong alone.
|
Reviewed the page against the app it describes rather than merging it on the build passing. 17 findings survived refutation, deduplicating to eight real problems. All fixed in the second commit. The one that mattered"Plaza does not hold your secret key" was false, stated absolutely, in a configuration this page's own build instructions produce.
The app is more honest than my page was: the join card changes its own subtitle to "Pasted here, and kept on this device." for exactly this case. The page now says where the key goes on each path and names the exception. The create half survives: Straight factual errors
The followers one is the one I mind. The app refuses to print a follower count because nothing on your disk can honestly know it, and that restraint is a better thing to say than the feature I invented. The page says it now. The thing the last commit claimed to have doneThe home page's app card still read "Flagship client" and pointed at Neighbouring pages that now disagreedThe roadmap's "year ahead" scheduled threads, reactions, quotes and media as future work while the new page lists all four under "What is in it today". Two public pages disagreeing about what exists is worse than either being wrong on its own, so the year-ahead item is now what actually remains. Out of scopeThe same false Windows sentence is in the app's README, where I copied it from. Fixed separately in zig-nostr/plaza#83.
Rebuilt, served, and walked the pages again: every internal link resolves and the corrected sentences are the ones being served. |
1 participant
The site talked about "the flagship client" in three separate places and never said what it is called. The app I have put the most work into was the one thing on zignostr.com you could not look up.
/plazaA page of its own, covering what the app actually is rather than a feature list:
scripts/frame-budget.shreproduces.Named everywhere it was anonymous
The home page's "Native apps" card, the ecosystem list, and the roadmap's "In progress" entry all say Plaza and link to the page. Two headings in the ecosystem list moved from a dash to a colon so the section reads consistently.
No download line yet
The page says plainly that Plaza is not tagged for download and gives the source build instead.
A
curl | bashline belongs here the day the first tag exists and not an hour before. Until then it resolves to "there is no published release yet", which is a worse first impression than no install line at all. Cutting that tag is a separate, deliberate act and this PR does not do it. When it happens, one paragraph on this page changes.Checked
npm run buildclean, 14 static pages. Served the build and walked it:/plazareturns 200, every internal link on the page resolves, the perf table renders, and the four pages that now link to it all resolve too.