Improve community discovery and add a bilingual network overview - #91
Improve community discovery and add a bilingual network overview#91n30nex wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 36c89a7010
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| root.addEventListener("focusout", function (event) { if (event.relatedTarget && !root.contains(event.relatedTarget)) root.open = false; }); | ||
| root.addEventListener("keydown", function (event) { if (event.key === "Escape" && root.open) { root.open = false; summary.focus(); } }); | ||
| document.addEventListener("visibilitychange", refresh); | ||
| window.setInterval(refresh, MAX_AGE); |
There was a problem hiding this comment.
When the page remains visible after a fresh request, this interval starts before refresh() finishes, while the cache timestamp is recorded afterward. The first five-minute tick therefore sees an entry just under MAX_AGE and reuses it, and the next fetch does not occur until the ten-minute tick, leaving the header totals and update timestamp stale for nearly twice the intended cache lifetime. Schedule the next refresh relative to data.at or otherwise ensure the first post-expiry tick fetches new data.
Useful? React with 👍 / 👎.
|
The requested changes are deployed for testing at https://canadaverse.org/meshcore-canada/ in English and French. The public manifest matches Try these on the preview:
Verified all 129 public pages and 70 hosted browser checks, plus real Cambridge lookups and Beacon responses in both languages. Two mobile map timing failures in overlapping runs passed when rerun separately without extending timeouts. Asset hashes and the deployed revision match the local candidate. Validation and Lighthouse are green on the final commit. The complete browser matrix passed 584 checks on the preceding commit; GitHub is rerunning it for the final line-ending-only cleanup: current CI run. The prior preview is retained for rollback. No shared-container restart was needed, the main Canadaverse homepage is byte-identical, and meshcore.ca was not changed by this deployment. No broker accounts or submission services were modified. |
n30nex
added
bug
1 participant
Summary
Follow-up to #90, which was merged while this browser-feedback work was in progress. English and French are updated together.
Validation
feb4070. The final commit only normalizes the generated SVG's line endings and makes its generator portable. The final public rerun had two mobile map timing failures during overlapping test runs; both passed in a separate run with the original timeouts unchanged.Preview and boundaries
Deployed to the Canadaverse test site at
9705f6df77faa9cd8c6c3b745cc7df73795481e7. The public manifest matches the candidate. All 129 public pages return HTML under the preview path and are excluded from search indexing; local preview checks cover 13,228 references.The previous preview and route configuration are backed up. The shared host container was not restarted, and the main Canadaverse homepage stayed byte-identical. No merge or meshcore.ca deployment was performed. Broker accounts, radio settings, region boundaries, and submission services are unchanged.
The host's existing security policy continues to block Cloudflare-injected analytics, as it also does on the main Canadaverse homepage. No application scripts or requested APIs were blocked in live browser checks; the policy was not broadened for analytics.