[guardian-dev] FireChat moved off iOS proprietary mesh to their own xp mesh protocol?

[Michael Rogers]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/10/14 17:53, Nathan of Guardian wrote:
> Interesting results... here is what my hacking has wrought:
> 
> https://github.com/n8fr8/gilgamesh
> 
> It is based on the Android-17 BluetoothChat sample, but changed to
> use the getName() as the message bearer, and the 3600 timeout
> option. This means that app starts up in discovery mode and stays
> there, and you don't have to pair or anything.
> 
> For the user name, it uses the first 6 digits of the Bluetooth MAC 
> address ID.
> 
> There is a "Direct Message" mode that uses the insecure socket
> option if not paired, and the secure socket option if paired (or it
> will soon). Over this socket, we could easily add in OTR.

Amazing! I'll test it on the pile o'phones tomorrow.

> Finally, if you are paired with a user, there username will be
> appended with a * so you can know that they are someone you trust
> and have linked with in person.

With later versions of Bluetooth I believe devices can pair
automatically without user intervention. Does your code distinguish
between manual and automatic pairing?

Cheers,
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJULDrfAAoJEBEET9GfxSfMQDUIAJBwVFbDETp2Fm5S87zensTJ
sy2vWdRTOeDZoC/u6JFyLt2VSfvDlNYn8XydXSsjRffIvf6GOi2YRedMXqbeLbE7
egcFC5Tj+Q6rmmpMBbuxFjwObs49UF7FHQ9D3mQbDKKHHKgmZhTARqOtwagg03ce
xMoKjeQ8fknZ9BaNA2xGKt31q0b9/3TJfq+nGq8jiYy+e95q0HH8DQ9KvViZey+I
p7O1TZDmw13Qzs/C3/vr8P5Vt7sns0/8CEgW+04L3D2RpD4KCEzlqgs50K1TpowG
OSbC/j8fb6rKrIdjP0ztTCrEr5UoOzBoMb9u8QJbo4g7fpRyq7KoZEl8IThvtYA=
=N9cE
-----END PGP SIGNATURE-----