Bring every page up to date with what actually ships - #11
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Both apps are downloadable now and the site still described one of them as unfinished. The Plaza page said "Plaza is not tagged for download yet", which stopped being true at v0.2.0. Corrected across the site: - Plaza is shipped, with the install one-liner, on the home page, the ecosystem page and its own page. - The library snippet installs v0.3.8, not v0.3.5. - "pre-alpha" becomes "early". Two apps you can download is past pre-alpha. - The messenger stops being a separate planned app. Private messages are a milestone inside Plaza, which is what the roadmap says. - Nothing promises mobile or more platforms any more. The roadmap says those are deliberately not being built, and three pages were still advertising them. The performance table was wrong, not just stale. Its third column was labelled "Profile query" and held the timeline numbers, understating the profile query by about thirty times. It now carries all four columns from the library's own benchmark, and says plainly that a profile read costs eight microseconds regardless of how much history sits behind it. The NIP page listed reply threading as planned under a milestone name that no longer exists, while Plaza has been threading replies for months. Library NIPs and app NIPs are now separate tables, because they are different claims. Every row in the app table was checked against the source: NIP-45 and NIP-51 are not there despite being mentioned in comments, so they are not listed.
sepehr-safari
force-pushed
the
site-refresh
branch
from
August 6, 2026 20:28
27c7bb3 to
1cd4e96
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both apps are downloadable now and the site still described one of them as
unfinished.
Wrong, not just stale
/plazasaid "Plaza is not tagged for download yet." That stopped being trueat v0.2.0. It now carries the install one-liner.
The performance table's third column was mislabelled. It said "Profile query"
and held the timeline numbers, understating the profile query by about thirty
times. All four columns from the library's own benchmark are now there, and the
page says plainly that a profile read costs eight microseconds no matter how much
history sits behind it.
The NIP page listed reply threading as planned, under a milestone name that no
longer exists, while Plaza has been threading replies for months.
Out of date
/ecosystemand/plazamilestone inside Plaza, which is what the roadmap says
deliberately not being built, and three pages were still advertising them
On the NIP page
Library NIPs and app NIPs are now separate tables, because they are different
claims: one is what you get when you import the library, the other is what Plaza
does above it.
Every row in the app table was checked against the source rather than against
comments. Two candidates did not survive that check: NIP-45 appears in a comment
saying relay support is too spotty to use, and NIP-51 appears in one saying lists
come later. Neither is listed.