Repository navigation
Add a compatibility page for the v2 server (hidden until v2 ships) - #41
Merged
Merged
Conversation
What the Private API can do depends on the macOS version on the server Mac, and the only place that was written down was a pair of hand-maintained HTML tables inside a single FAQ answer -- behind an accordion, inside a category, three clicks from anywhere. It is the most decision-relevant content on the site and was the least visible. /compatibility lists all 23 capabilities, grouped by category, each with its macOS floor and a one-line summary, and reuses the macOS picker: choose a release and the page highlights what it supports. 16 of 23 on Sonoma, 20 on Sequoia, 23 on Tahoe. Data is copied from the server's CapabilityCatalog.swift -- ids, titles, summaries, macOS floors and categories -- so the page and the server describe the same thing rather than drifting. Deliberately no subscription tier on this page. It answers "does my Mac support this", which is a different question from what a plan includes, and Pro is not announced. Adding a tier badge later is additive, and nothing here links to or mentions /pricing, so that page stays undiscoverable -- asserted in the build. The picker itself is now a shared component. The pricing page was the only user and had the markup and ~40 lines of script inline; both pages now use one copy, so the cumulative rule cannot diverge between them. Verified the pricing page is unchanged by the refactor: 10 cards, 5/7/10 across the releases, still noindex, prices intact. Linked from the header and footer, since being findable is the point. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The page describes the v2 Swift server, which supports macOS 14 and newer. The server shipping today is v1.x on Node.js, which runs on Mojave through Ventura and has a different capability set. Publishing this now would tell a Ventura user they are unsupported when v1 supports them perfectly well. So it is hidden exactly as /pricing is: out of the header and footer, out of the sitemap, noindex. The route still resolves and is still asserted in the build, so it cannot rot while it waits. The page also now states its own scope -- "BlueBubbles Server 2.0 and newer... earlier macOS releases are supported by the 1.x server, which has a different feature set" -- so it is not silently wrong about which server it describes, whenever it does go live. Launch steps are in a comment at the top of the page. The FAQ's existing tables are untouched and stay the public answer for now, which is correct: they describe the v1 server that people are actually running. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
zlshames
changed the title
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.
Builds
/compatibilityfrom the server's capability catalogue — but hidden, because it describes the v2 Swift server and v1 is what ships today.Why it is hidden
The page reflects the v2 Swift server: macOS 14 and newer, 23 capabilities from
CapabilityCatalog.swift.The server shipping today is v1.x on Node.js, which runs on Mojave through Ventura with a different feature set. Publishing this now would tell a Ventura user they are unsupported when v1 supports them fine.
So it is hidden exactly as
/pricingis — no nav or footer link,noindex, out of the sitemap — while the route still resolves and is still asserted in the build, so it cannot rot while it waits.The page also states its own scope on the page itself, so it is never silently wrong about which server it describes.
What it does, for when it launches
All 23 capabilities grouped by category, each with its macOS floor, and the macOS picker:
To launch, once v2 is out
/compatibility/back toNAV_LINKSandFOOTER_LINKSinsrc/data/site.tsnoindexfrom the pageastro.config.mjsSteps 1–3 are listed in a comment at the top of the page.
Also in here
noindex, prices intact.🤖 Generated with Claude Code