3 ms·
This is very cool, because in theory it makes the barrier to entry into a meshnet, effectively zero. Is it any different conceptually than extending the handsh
by AndrewKemendo 9y ago
This is very cool, because in theory it makes the barrier to entry into a meshnet, effectively zero.
Is it any different conceptually than extending the handshake from analog modems to include the data? From what I hear it sounds like <handshake>{data}.
I assume you can't have an "open" connection because the sound is the transmission medium, so it would have to be constantly talking to keep the line open.
A lot of cool possibilities here!
- ggerganov 9y ago> Is it any different conceptually than extending the handshake from analog modems to include the data? By "include the data" do you refer to the transmitted file itself being included in the sound? If yes - you can include the file in the sound, but the transmission will be too long, because transfer rate is very slow. About what is heard as sound: <marker>{SDP data}. All peers initially listen for the <marker> because it is computationally cheaper. When the <marker> is received, then they start listening to the SDP data, which consumes more resources.
- AndrewKemendo 9y agoGlad I was hearing it correctly (generally). So based on what you write here, it sounds like it can only be one way - which makes sense given the architecture. I'd be curious if it could be made as a continuous two way connection - my guess is yes, but it would take FTDT or FDM to coordinate right?
- ggerganov 9y agoYes, it's one-way communication. I guess, extending to two-way can involve any of the practices used in modem communication. The biggest issue though would be dealing with the noise and making it reliable.
- chatmasta 9y agoDefinitely would be cool to use it as a bootstrapping method to get "into" a mesh. For example as a method for sharing wifi access credentials. But it seems most problems you could apply this to, you may as well just use Bluetooth or BLE.