On Wed, Oct 8, 2014, at 09:07 AM, Paul Gardner-Stephen wrote: Hello, On Wed, Oct 8, 2014 at 10:57 PM, Nathan of Guardian <[1][email protected]> wrote: On Wed, Oct 8, 2014, at 08:21 AM, Paul Gardner-Stephen wrote: > Hello Nathan, > > Root would not be required to use this transport. > > In other words: adding the bluetooth device name transport would allow > most > stock Android phones to mesh, albeit at low data rates (~1KB/minute), and > with limited range (~10metres). 1kb is approx 7 full length tweets or text messages, so sounds good to me. Actually, with SMAC, our open-source tweet-compressor, it is between 12 and 20 full length tweets, depending on their composition. That said, adding in our authentication and meta-data headers, it probably falls back to about 5 - 8 authenticated tweets per kilo-byte. Is there any repeater functionality that would extend messages beyond 10' as the people/phones move locations? This would be an automatic consequence of the Rhizome protocol, which stores and forwards. The prioritisation algorithm would likely need some tweaking, and I am sure there are other surprises that would have to be dealt with to make it all work efficiently over many hops, which are challenges that I hope we get the chance to face. Great to hear... btw, I just realized we can use the WifiDirect service discovery capability to send much longer data than the current SSID/name method allows: [2]http://developer.android.com/training/connect-devices-wirele ssly/nsd-wifi-direct.html Not sure what the limits are, but it doesn't require you to connect or join to be able to broadcast/listen for this info. References 1. mailto:[email protected] 2. http://developer.android.com/training/connect-devices-wirelessly/nsd-wifi-direct.html
_______________________________________________ Guardian-dev mailing list Post: [email protected] List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: [email protected] Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: [email protected]
