Thread: Tech we can’t use or teach?

Original Article ↗ Hacker News Discussion ↗

Overall sentiment about Thread and “enshittification”

  • Many see Thread’s licensing as part of a broader trend of “enshittification” and closed ecosystems, especially in home automation.
  • Some hope regulation (especially from Europe) and consumer pressure will eventually push the market toward more open, interoperable standards.
  • Others are pessimistic, viewing this as big tech protecting moats and constraining genuinely disruptive/open tech.

Licensing model and restrictions

  • Access to the Thread spec is free but gated by an EULA stating membership is “necessary to implement, practice, and ship” Thread technology and specifications.
  • Implementor membership with IP rights reportedly costs around $7,500/year; lower/free tiers exist but do not grant IP rights.
  • OpenThread (from Google) is under a permissive license, but Thread Group’s separate IP/patent claims still apply; using OpenThread does not shield users from those.

Impact on hobbyists, teaching, and small businesses

  • Strong concern that hobbyists, educators, and small startups cannot legally:
    • Implement Thread,
    • Share designs or dev boards,
    • Write detailed tutorials/spec analyses,
    • Or sell even small-scale devices (e.g., a few boards on a crowdfunding site).
  • Others argue the wording targets shipping commercial devices, not private tinkering or blogging, and that the FAQ explicitly ties legal action to “shipping.”
  • Several note that even if one is technically in the right, the mere risk and cost of defending a lawsuit is chilling.

Patents, copyright, and “practice”

  • Disagreement over how far patents reach:
    • Some assert there is no private-use patent exemption (at least in some jurisdictions); others cite limited research exemptions or explicit private-use carveouts (e.g., in parts of Europe).
    • There is mention of EU-style interoperability exceptions for software.
  • Debate over whether “practice” could cover any operational use, including non-commercial or internal experimentation.
  • Concern that copyright on the spec plus contract terms could be used to suppress derivative documentation, though some think normal citation/critique rights still apply.

Comparisons and alternatives

  • Bluetooth is cited as another paid-membership standard, but widely implemented “illegally” in cheap devices with euphemistic branding.
  • LoRaWAN, Zigbee, and plain IPv6/6LoWPAN are mentioned as more legally straightforward, though often technically more complex or slower.
  • Matter is criticized for device attestation and PKI requirements; Thread is seen as part of this increasingly closed smart-home stack.

Community responses and proposed workarounds

  • Suggestions:
    • Boycott Thread, don’t teach or build on it, and actively warn others.
    • Prefer open standards even if technically less convenient.
  • A proposal for a shared “umbrella” entity to buy a license for many users is deemed unworkable due to affiliate definitions and sublicensing restrictions.
  • Some predict that if Thread gains traction, unlicensed “clone” implementations (similar to Bluetooth knockoffs) might appear, but others argue that this only strengthens Thread’s dominance while leaving compliant actors bound by fees and restrictions.

Broader reflections

  • Several comments zoom out to criticize:
    • Charging for access to knowledge and interoperability as unethical.
    • The dependence of big tech on unpaid open-source “hobbyists.”
    • The tension between closed, monetized standards and a more open, user-respecting future internet.