TakeFlight007

10 ms·

1. 1.▲
   by TakeFlight007 9mo ago

   You are right... and being rigorous is the only path to trust. We can shift the issue from "what is it" to "why isn't it documented and why does status report inactive. 84.5 MB through utun2/IDS during stated isolat
2. 2.▲
   by TakeFlight007 9mo ago

   I'm aware of "Find My Device" that's a documented feature. Find My beacons go OUT (your device tells others where it is). This is 84MB coming IN. Different thing.
3. 3.▲
   by TakeFlight007 9mo ago

   Not possible due to directionality and volume: Find My/AirTag: Characteristic low-payload outbound beacons (Egress). Observed Reality: 84.5 MB Ingress (Received) vs. 1.25 MB Egress.
4. 4.▲
   by TakeFlight007 9mo ago

   Mathematically invalidated by the temporal anchor in the artifacts. The spindump captures a precise 2.00-second window (2025-12-31 13:35:14) where mDNSResponder (PID 10252) is in an active execution state with Priority 31 scheduling. Real-t
5. 5.▲
   by TakeFlight007 9mo ago

   Good catch! checked sharingd (PID 75) in spindump: <0.001s CPU time while mDNSResponder processed the 84MB. Traffic attribution rules out AirDrop. The 67:1 RX/TX asymmetry and idle sharing daemon confirm this isn't file tran
6. 6.▲
   Show HN: Forensic evidence of iOS mesh networking bypassing Airplane Mode(github.com)

   8 points by TakeFlight007 9mo ago|13 comments