Stephen 🐈 🇨🇦 on Nostr: npub16e228…sks3l So assuming you're talking about the functionality of the ...
npub16e22826p4rpdla2ugvn76w6s730gmll3fw6upqudmhp9f3cq2ursssks3l (npub16e2…ks3l) So assuming you're talking about the functionality of the transceiver firmware and not a protocol-level change this is actually a pretty difficult problem to solve.
How do you introduce the error? If you do it randomly, then with enough samples you'll be easy to triangulate. If you statically offset it then that's relatively easy to figure out too ("Oh, they're following the path of this road, just 500 meters north. They're clearly just offsetting their position.")
If you're just doing it fixed then it's pretty easy as you can just fudge the coordinates yourself. The firmware would have to be updated to add the ability to specify deliberate error though.
How do you introduce the error? If you do it randomly, then with enough samples you'll be easy to triangulate. If you statically offset it then that's relatively easy to figure out too ("Oh, they're following the path of this road, just 500 meters north. They're clearly just offsetting their position.")
If you're just doing it fixed then it's pretty easy as you can just fudge the coordinates yourself. The firmware would have to be updated to add the ability to specify deliberate error though.