Cross-Platform P2P Wi-Fi: How the EU Killed AWDL

Original Article ↗ Hacker News Discussion ↗

Authentication, Identification & Security

  • Current seamless pairing (AirDrop, Samsung features) relies on platform accounts and vendor PKI; reproducing this in an open, cross‑platform way is unclear.
  • Some reverse engineering exists for AWDL/AirDrop, but typically still depends on Apple accounts, Macs, or private APIs. People doubt Apple would tolerate third‑party clones long‑term.
  • Commenters want an open authentication layer on top of standardized P2P Wi‑Fi, but disagree on implementation language (C vs safer languages) and security posture.
  • Several warn that generic P2P Wi‑Fi will lead to many insecure apps because most developers are weak at security.

Cross‑Platform File Transfer vs “It Just Works”

  • Many see the “elephant in the room” as Android–iOS local file transfer being impossible without cloud relays, apps, or accounts.
  • Objections to cloud‑based transfers: slower than LAN, use mobile data, require internet, introduce privacy concerns, often lack end‑to‑end encryption, and compress/modify media.
  • AirDrop is praised for easy sharing with strangers, preserving full‑quality photos and metadata, and requiring no phone numbers or apps. Some Android users are openly jealous of this.
  • Others argue that most of their usage is intra‑Apple, so identity‑based auto‑auth is more valuable than cross‑platform compatibility.

Wi‑Fi Aware / NAN and Linux & Hardware Support

  • Wi‑Fi Aware is seen as promising but opaque: documentation largely lives behind Wi‑Fi Alliance walls and Android‑centric docs.
  • On Linux, support appears minimal and experimental (few kernel commits, some iw commands). Non‑STA modes are described as a “crapshoot” due to vendor firmware, regulatory quirks, and lack of DFS support.
  • The Wi‑Fi Alliance’s marketing name vs spec name (NAN) adds confusion; a spec PDF is shared.
  • Some note working academic/Linux implementations of AWDL‑like behavior using commodity chips but currently at the cost of dropping AP connections; they believe dual‑mode may be possible.

Ad‑Hoc Wi‑Fi & Local‑First Networking

  • Multiple comments nostalgically recall early‑2000s ad‑hoc Wi‑Fi for effortless, infrastructure‑free sharing, claiming it “just worked” and was common where access points were rare.
  • Today, OSs, drivers, and network middleboxes often hinder simple broadcast/multicast discovery, pushing apps and games toward central coordination servers, even for LAN.
  • Several hope Wi‑Fi Aware plus good libraries could revive local‑first experiences (LAN games, offline sharing) that no longer work cleanly.

EU Regulation, AWDL, and Interoperability

  • The thread clarifies the EU did not demand AWDL be opened; it mandated support for Wi‑Fi Aware 4.0 and non‑discrimination against it. That effectively sidelines AWDL.
  • Some see this as overreach and an attack on the “free market” or product freedom, arguing Apple should be allowed to sell proprietary features.
  • Others strongly support the mandate: RF is already tightly regulated; interoperability prevents fragmentation, reduces waste, and counters lock‑in.
  • Several note Apple is free to exit the EU but won’t, and that EU tech regulation (chargers, DMA, etc.) often becomes de‑facto global due to market size.

Lightning, USB‑C, and Parallels to AWDL

  • Debate mirrors the AWDL issue: some argue Apple “pioneers” better proprietary tech (Lightning, AWDL) and regulators unfairly force inferior standards.
  • Others respond that Lightning was worse by virtue of being proprietary and heavily licensed; USB‑C’s universality and interoperability outweigh any minor connector advantages.
  • Commenters credit EU charger rules with accelerating or locking in USB‑C’s ubiquity, greatly improving practical convenience.

Implementation & Performance Questions

  • There’s skepticism that standardized Wi‑Fi Aware will match AWDL’s design and reliability; some bet AWDL works better due to Apple’s tight vertical integration.
  • Others counter that Apple will drop AWDL once Wi‑Fi Aware is “good enough,” since maintaining two stacks is costly and Wi‑Fi Aware will evolve with Wi‑Fi 7.
  • Hardware constraints like microsecond‑precision channel hopping and firmware capabilities are brought up; some are willing to dedicate extra adapters or Thunderbolt docks just to get robust P2P on Linux.