5 ms·
"I said, ‘There’s a simple answer.’ I had my phone on the table, and he had his phone on the table. I said, ‘Look, our phones are next to each other, can they t
by snowy 11y ago
"I said, ‘There’s a simple answer.’ I had my phone on the table, and he had his phone on the table. I said, ‘Look, our phones are next to each other, can they talk to each other?’ He said, ‘of course they can.’ I said, ‘directly?’ And he said, ‘no, they cannot.’ And this is not because physically they can not, physically [you can connect] phone-to phone using WiFi, Bluetooth. But the TCP/IP protocol is the roadblock for phones to directly talk to each other. The protocols need to change because it doesn't enable the communication that we want.”
Am I missing something here? If both phones are on the same network (IE the internet) and have public IP address's (which IPv6 makes it feasible for every device to have) Why can't they talk to each other? Why is the TCP/IP protocol a roadblock??
- matthewrhoden1 11y agoI think technically you could setup a light weight server on your phone and you could get an address for it and expose it to the internet. However, that would only be for that cafe they are sitting in. Since the server would need to stay in a fixed location or keep updating the DNS everytime it moves. This would then take time to propagate, it's not immediate as far as I can remember. I could be wrong, I'm a little weak on my networking, but I believe that's why.
- spdustin 11y agoIsn't that pretty much exactly what AirDrop does on IOS? Connect two phones via Bluetooth when they're in proximity, and they then carry on a conversation?
- deleted 11y ago[deleted]