IdeaWell

Project ideas from Hacker News discussions.

I’ve banned query strings

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1️⃣ Opposition to Unauthorised Query‑String Additions (Anti‑Tracking)

“I’m broadly anti‑tracking: it’s generally against the interests of the individual.” – chrismorgan

The discussion repeatedly frames extra query parameters as unwanted tracking cargo that site owners should reject.

2️⃣ Technical Response & the Robustness Principle Debate

“Robustness principle is itself bad manners, in plenty of contexts.” – wizzwizz4 Participants discuss whether to answer unknown query strings with 404, 400, 414, 418, etc., and critique the old “be liberal in what you accept” mindset.

3️⃣ Legitimate Value of Query Strings

“I build a lot of internal applications, and one of my golden UI rules is that a user should be able to share their URL and others should see exactly what the sender did.” – legitster

The thread points out genuine uses—search filters, state sharing, PDF downloads—where query strings are essential and not merely for tracking.

4️⃣ Revival of Curated Link Communities (Webrings / Wander Console)

“'wander console' sounds like they're just web rings re‑invented.” – gtowey

“This is cool and creative!” – moritzwarhier

The conversation celebrates the nostalgic “wander console” idea—a community‑curated, graph‑based link explorer—as a modern twist on classic webrings.

🚀 Project Ideas

CleanLink Clipper

Summary

  • Strips unauthorized query parameters (e.g., utm_*, fbclid, ?ref=) from URLs before copy or sharing, preventing broken target pages.
  • Provides a one‑click “Copy Clean Link” button and clipboard fallback for browsers.

Details

Key Value
Target Audience Web users who share links and want to avoid broken or tracked URLs.
Core Feature Automatic query‑string sanitisation with configurable blocklist/allowlist.
Tech Stack Chrome/Firefox extension (Manifest V3), JavaScript, URL API.
Difficulty Low
Monetization Hobby

Notes

  • Directly addresses HN complaints about sites rejecting URLs with unknown query strings.
  • Quote from discussion: “I hate when my shared links are twice as long because of tracking parameters.”

QueryGuard API#Summary

  • Centralised API that validates incoming URLs and returns standardized HTTP error codes (400/404/418) for unsupported query strings.
  • Offers sandbox and docs for developers to test their own endpoints.

Details

Key Value
Target Audience Backend developers and API providers needing predictable responses to malformed URLs.
Core Feature Query‑string whitelist enforcement with configurable error responses.
Tech Stack Node.js (Express), TypeScript, OpenAPI spec.
Difficulty Medium
Monetization Revenue-ready: Pay‑as‑you‑go (e.g., $0.01 per request after 10k free).

Notes

  • Solves the problem highlighted by users wanting a clear, spec‑compliant way to reject unwanted query strings.
  • Enables consistent error handling across diverse services, reducing “it works on my side” friction. ## NoQuery Wander Console Network

Summary- Decentralised network of personal “Wander Consoles” that explore curated web graphs without using query strings.

  • Each console publishes its neighbour list; a central index aggregates them while enforcing a strict “no query‑string” policy.

Details

Key Value
Target Audience Indie web creators, privacy‑focused explorers, community curators.
Core Feature Graph‑wide randomised exploration with URL hygiene (no tracking params).
Tech Stack React front‑end, IPFS for discovery, Node.js for peer coordination.
Difficulty High
Monetization Hobby

Notes

  • Revives the “Wander Console” / web‑ring discussion from HN, giving users a privacy‑first way to traverse curated links.
  • Aligns with comments praising “randomised graph exploration” and “ever visited node is a fast travel station.”

Fragment‑Only Router

Summary

  • Lightweight library that encourages routing via URL fragments (#) instead of query strings, automatically handling fallback for deep linking.
  • Provides CLI tool to convert existing query‑string‑heavy URLs to fragment‑based equivalents.

Details

Key Value
Target Audience Front‑end developers building SPAs who want to avoid tracking‑related URL pollution.
Core Feature Automatic migration of ?param=value to #/param/value and sync with browser history.
Tech Stack TypeScript, Vite plugin, Web History API.
Difficulty Medium
Monetization Revenue-ready: SaaS with hosted migration service (subscription $5/mo).

Notes

  • Directly addresses HN concern about “tracking parameters” and the desire for clean, shareable URLs. - Offers practical utility for developers who want to keep URLs clean without breaking existing functionality.

Read Later