Wander Console Removes via= Query Parameter After Breaking URLs

In version 0.4.0 of Wander Console, the author added a via= query parameter to URLs to let destination sites log the source of traffic. The feature was intended as an opt‑out mechanism but quickly caused broken URLs on sites that already use query strings, such as https://int10h.org/oldschool‑pc‑fonts/fontlist/?foo. The added parameter changed the URL, resulting in 404 errors for many resources. The author realized that appending tracking data bypasses standard referrer policies and violates user privacy. After acknowledging the mistake, the feature was removed entirely. The project now runs with a single HTML file and a JavaScript configuration that does not modify URLs. The change restores compatibility with existing sites and aligns with best practices for privacy and link integrity.

The incident highlights the importance of testing URL modifications in real‑world scenarios and respecting browser referrer controls. It also demonstrates how a seemingly harmless feature can break functionality and erode trust. The author’s decision to remove the feature rather than keep an opt‑in option reflects a commitment to clean, privacy‑respecting code.

Developers building similar tools should avoid altering URLs for tracking purposes and rely on HTTP referrer headers instead. The Wander Console’s updated version now provides a clear, opt‑in configuration for optional features, ensuring that users can choose whether to enable them.

Overall, the story serves as a cautionary tale about the pitfalls of adding query strings for tracking and the value of swift remediation.