What Is a Dickover?

Original Article ↗ Hacker News Discussion ↗

Nature of “dickovers” and user experience

  • Defined as popups/popovers/curtains that block content and force an unnecessary interaction (cookie consent, newsletter signups, app install prompts, SMS alerts, etc.).
  • Many commenters say they immediately leave sites showing them, especially if they appear during checkout or on first page load.
  • Some see persistent cookie/newsletter modals plus captchas/etc. as creating a hostile, cluttered “gauntlet” before reaching content.

Privacy, tracking, and regulation

  • Strong anti‑tracking sentiment: many self‑host blogs without analytics, viewing visits as irrelevant to their purpose.
  • Others argue basic analytics and reCAPTCHA are practically necessary, even if they trigger consent banners.
  • Debate over GDPR/European rules:
    • One side: GDPR doesn’t require banners; it prohibits unnecessary PII collection, and banners are malicious compliance by trackers.
    • Another side: EU/CCPA are credited with exposing tracking and mandating equal “accept/deny” designs; “reject and pay” models criticized as mafia‑like.
  • Disagreement whether cookies themselves are “no big deal” vs. cross‑site tracking being a major issue.

Business models and entitlement

  • Some argue users aren’t entitled to free content without “dickover price” (ads, tracking, prompts); if people keep using such sites, the market has spoken.
  • Others counter that abusive models should simply be illegal and that running the site isn’t “necessary.”
  • Paying subscribers being hit with modals (e.g., SMS promos) is widely viewed as indefensible.

Developer/company perspectives

  • Several suggest most devs/managers don’t see the live experience (they cleared it once), or they’re overruled by marketing/legal and prioritize paychecks.
  • Consent SaaS, lawyers, and corporate risk aversion are blamed for widespread banners.

User workarounds and technical ideas

  • Common tactics: adblockers (uBlock + annoyance lists), reader mode, Stylus/user CSS, JS toggling, custom bookmarklets to remove fixed/sticky elements, or simply closing the tab.
  • Calls for browsers to:
    • Support global privacy preferences (e.g., Global Privacy Control) and enforce them.
    • Treat web JS as hostile and technically prevent true modals, history hijacking, and other dark patterns.

Naming and tone

  • Many like “dickover” as a deliberately rude, memorable term that stigmatizes the pattern, similar to “enshitification.”
  • Others find it childish, profane, hard to use in professional contexts, and prefer “popup,” “popover,” or “unwanted popup.”