> Bandwidth plays a role. Updating driver positions constantly, at scale, chews bandwidth. As does broad-casting trips, acceptances, and so on. How could this

> Bandwidth plays a role. Updating driver positions constantly, at scale, chews bandwidth. As does broad-casting trips, acceptances, and so on. How could this chew bandwidth? It's just some bytes for the positioning, over some socket (probably a websocket), it really doesn't sound like it'd chew bandwidth to send an ID + coordinates every second or so if your connection is already established. Maybe a few more bytes for a signature to avoid tampering/spoofing when updating the position.