Explain how the headline number relates to GLAM#14
Open
mxinden-bot wants to merge 2 commits into
Open
Conversation
Adds a 'How these numbers relate to GLAM' note by the GLAM links: the page shows a per-connection estimate (from GLAM's non-normalized histogram, averaged over recent Nightly builds), whereas GLAM's UI defaults to a per-client, per-release proportion, so the click-through won't show the same percentage. Also fixes the stale charts.js header comment that claimed the opposite.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
savearoundtrip | 428a5de | Commit Preview URL Branch Preview URL |
Jun 16 2026, 02:18 PM |
Drop the details block; add a one-line 'GLAM's page defaults to per-client, so its numbers differ' note to each GLAM source link (top metric, data section, records-in-the-wild). Keep the charts.js comment fix.
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
2 participants
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.
Addresses the recurring "how do the website numbers match GLAM?" confusion.
The page shows a per-connection estimate: reconstructed from GLAM's non-normalized histogram (each bucket value × the clients reporting it), taken as each bucket's share of the four discovery outcomes, and averaged over the most recent ~14 Nightly builds. GLAM's own page defaults to a per-client proportion aggregated per release — a different denominator and a different aggregation — so clicking the GLAM link won't show the same percentage at a glance. That mismatch is what people are tripping over.
This PR:
js/charts.jsthat claimed the opposite ("shares are GLAM's By-Client-ID proportion… matches the GLAM UI") — it's actually per-connection, so the comment was itself a source of confusion.Files:
index.html,js/charts.js,css/style.css. Preview builds on the PR.Open question for you: is the per-connection estimate still the framing we want as the headline, or would you rather switch the site to GLAM's per-client proportion so it matches the click-through exactly? This PR just explains the current choice; happy to flip the methodology instead if you'd prefer they line up.
Generated by Claude Code