September 17, 2026 — GA4 measurement and Cloudflare Pages deployment
- Added the Google Analytics 4 measurement tag through the shared site layout, with the Measurement ID supplied through a public Astro environment variable.
- Updated the Privacy Policy to describe standard page-view measurement and to keep camera, microphone and diagnostic values outside analytics payloads.
- Added a one-command production deployment path for Cloudflare Pages.
September 7, 2026 — Site information and navigation
- Added dedicated About, Changelog, Contact, Privacy and Terms pages with permanent internal routes.
- Added a responsive site footer that links to those first-party pages on every route.
- Documented the Google Analytics 4 data-handling boundary and the site's privacy-first analytics rules.
- Corrected the native Astro 404 page so it is clearly presented as a missing page and carries a
noindex, followdirective without a misleading canonical URL.
Current release — Expanded WebRTC developer tools
The current tool set extends the original camera, microphone, speaker, ICE, STUN, TURN and WebRTC leak checks with more focused browser diagnostics. Newer pages include a screen share test, camera resolution probes, a measured webcam FPS test, an ICE candidate parser, an SDP parser, browser-advertised codec inspection, a local RTCDataChannel test and a live getStats() viewer.
The parser tools process input in the browser and do not need a server-side parsing API. Local loopback tools describe their throughput and round-trip results as browser and device measurements, not as Internet-speed or remote-network benchmarks. Camera, microphone and screen-capture tools also release media tracks when a test is stopped or completed.
Initial release — Core readiness checks
The first release established WebRTCTest as a static Astro site with interactive React diagnostics. It introduced the combined WebRTC readiness test, individual webcam, microphone and speaker tests, plus ICE connectivity tools for inspecting host, server-reflexive and relay candidates.
From the beginning, public pages were rendered as complete HTML with page-specific titles, descriptions, headings, canonical URLs, Open Graph data and structured data. The project also established a privacy boundary: media streams remain local, parser input is not intentionally transmitted, and sensitive diagnostic values are excluded from analytics.
How this changelog is maintained
Entries focus on user-visible features, privacy changes, reliability fixes and changes that affect how a result should be interpreted. Small copy edits and internal refactors may be grouped instead of listed individually. Deployment timing can differ from repository timing, so a newly documented change may take a short time to reach every cached copy of the site.
See About WebRTCTest for the project principles, or use the Contact page to report a regression that should appear in a future entry.