uBlock Origin GPL code being stolen by team behind Honey browser extension

Reports that the team behind PayPal’s former coupon extension Honey is reusing uBlock Origin’s GPL-licensed code and filter lists in its new Pie Adblock product have intensified scrutiny of their business practices. Commenters link this to earlier allegations that Honey and similar extensions hijack affiliate commissions and mislead users about “finding” coupons, framing the episode as part of a broader collapse in trust around adtech, influencer promotions, and the economics of “free” browser add‑ons. Many argue that only stronger regulation and more aggressive GPL enforcement will deter companies from treating open source projects and users as exploitable resources.

Alleged GPL and filter-list violations

  • Pie Adblock, created by people previously behind Honey, is accused of:
    • Bundling uBlock Origin’s “quick filters” list (GPL) and uBO JavaScript code without license compliance or attribution.
    • Distributing GPL-covered code in a closed-source Chrome/Firefox extension, which would require releasing their own source under GPL if it’s a derivative work.
  • Some note that whether filter lists/configs are copyrightable depends on jurisdiction (e.g., EU database rights); but copied JS code makes that debate largely moot.
  • There’s discussion of possible workarounds (e.g., downloading lists at runtime) and counters that this may still not avoid GPL obligations.

Honey / Pie business practices and affiliate model

  • Honey is widely described as:
    • Replacing existing affiliate links at checkout with its own, even when a creator referred the user.
    • Sometimes doing this even when no useful coupon is found, and using weaker, partner-provided coupons instead of the best available.
    • Crowdsourcing and redistributing “internal” or tester-only coupons, viewed by many as unethical.
  • Some commenters argue this behavior is standard for coupon/affiliate extensions and driven by affiliate networks’ last-click rules; others say this is still fraudulent and anti-competitive.
  • Several posts link to or reference lawsuits by creators alleging lost affiliate revenue, tortious interference, unjust enrichment, and possibly wire-fraud-style “cookie stuffing.”

Ethics, incentives, and regulation

  • Many see Honey/Pie as emblematic of:
    • Adtech and affiliate ecosystems that externalize costs onto users, creators, and merchants.
    • A broader trend where deceptive actors outcompete ethical ones, absent strong regulation.
  • Others emphasize user and platform responsibility: browsers/extension stores, regulators, influencers, and consumers all enabling this.

GPL, copyright, and “theft” debate

  • Large subthread contrasts:
    • “Copyright infringement isn’t theft” in media-piracy debates vs. outrage at GPL violations.
    • Views that GPL uses copyright to protect a software commons vs. critiques of copyright itself.
  • Multiple explanations of how GPL vs LGPL work, when code becomes a derivative work, and how enforcement/detection occurs.

User reactions and alternatives

  • Many state they never trusted Honey/Pie or anything heavily influencer-promoted.
  • Some admit Honey saved them money but now feel misled about how it worked.
  • Several urge use of uBlock Origin, SponsorBlock, and avoiding coupon/affiliate extensions entirely.