[razingeden]

Ah yeah. They solve that by referencing the lorawan ble MAC But you know that.

did you find this project in your travels yet? apparently some portions of it stay and remain uniquely identifiable which this team considers a bug and apples position on it for now is a wont-fix

https://github.com/furiousMAC/continuity

I like the fact that they rotate them (and WiFi addresses) out so I don’t get stalked with tailored ads in Walmart or whatever but they only went so far with it and it’s probably still feasible

[redgridtactical]

Hadn't seen that repo, really interesting find. Using undocumented Continuity fields for discovery is tempting but I wouldn't want to build on something Apple could break in any iOS update. I'm doing a GATT characteristic handshake with a session-derived service UUID for re-identification after address rotations. Takes a couple extra seconds on reconnect but at least it's stable. Those Continuity protocol docs are useful regardless though, good to understand what Apple is doing under the hood.

[razingeden]

fair, I wouldn’t want a business model that’s dependent on something they could take away overnight.

so that’s discovery, I don’t have any ideas about retention offhand (you already do) but you’ve had that question rattling around for awhile and it’s new to me.

[redgridtactical]

Yeah exactly. Apple has a history of quietly changing undocumented behavior between point releases. Building on top of that is asking for a fun debugging session six months from now. The GATT handshake adds a couple seconds of latency on reconnect but at least I know it won't break with iOS 19.