[guardian-dev] GilgaMesh (was Re: FireChat moved off iOS proprietary mesh to their own xp mesh protocol?)

[Nathan of Guardian]

On Sat, Oct 4, 2014, at 07:02 AM, Michael Rogers wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 03/10/14 16:03, Nathan of Guardian wrote:
> > Second, within the limits of Bluetooth, we can employ some useful
> > app behaviors to extend the range of any message. In the latest
> > code, if you have paired with a trusted person’s device (using the
> > built-in Bluetooth settings panel of your device), and the
> > Gilgamesh app receives a broadcast message from that user, it will
> > be automatically re-shared, aka re-tweeted, aka RT. (Yes, we are
> > building old school Twitter here, just over Bluetooth). What this
> > creates then is a chain reaction – “the wave” phenomenon that I
> > blogged about earlier – that allows a message to propagate up to
> > 30ft in any direction, over and over again, as long as there are
> > trusted/paired devices out in the crowd.
> 
> Are you assuming that trust is transitive? If Alice and Bob have
> paired their devices and Bob receives a retweet from Alice, who claims
> it was originally tweeted by Carol, then Bob will trust Alice and
> retweet it, right? Likewise for anyone who trusts Bob. So Alice only
> needs to fool a single person into trusting her in order to spread
> forged messages.
> 
> > In addition to the auto-retweet feature, anyone can press and hold
> > on a message, and it will allow for a manually RT, whether you are
> > paired with the sender or not.
> 
> I think this is a better way to handle retweets. Make it as easy as
> possible, but make it manual.
> 
> This is essentially what we're planning to do with forums in Briar.
> 
> > Finally, let’s not forget that anyone with any bluetooth device, be
> > it a simple feature phone, an iPad or a laptop, can participate in
> > this process, by changing their Bluetooth device name manually
> > themselves, and setting it to a retweet message.
> 
> Perhaps it would make sense to use a special character (such as >) at
> the start of the device name to indicate that it's meant to be
> interpreted as a message? Otherwise people will keep saying "Alice's
> iPad" in the chatroom. ;-)
> 
> Cheers,
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQEcBAEBCAAGBQJUL9PVAAoJEBEET9GfxSfMBAEH/Ao+br+9Pfp0oIhOfD8UkJgW
> //PbsQKIVDFL+3ZXtjyqkUSeRJxyS6j1L93FtKJtJC/afzXQ8J68+sYDzZBshDSM
> 7pZNDXrT6Qun999MRMb1WQjBpkD+fCB4ppe6QuRqNwoh/ZUTUMakirF9auR5YOwW
> sfqjJi/og7LX9BgBYcHUjpoK/4lgYeE+gNif5YUVKB6bWiFkObC8/1m4MZyZVigJ
> B2luBW+JACsMjayNCWA4xcg4c3nWoP0RNpHkz6APtCs0Cue78DTmIEThfQKf0mxo
> N6rF9jnuvmli+82wbvscOT5aK0QHsXtciFboCf7/FsU8L63/KbYXvqR8up7HHbQ=
> =xlG0
> -----END PGP SIGNATURE-----

Thanks for the feedback on the poisoning possibility. I have removed
autoreshare for now, but made manual reshare even easier.

Also all Gilga statusnames must start with a space to differentiate from
standard Bluetooth names.

Here is the latest update;

http://openideals.com/2014/10/06/gilgamesh-twitter-over-bluetooth/

-- 
  Nathan of Guardian
  nathan at guardianproject.info