Hey Paul, Good to see your comments here, since you're deep in the mesh. I wanted to get your thoughts on a question: since this bluetooth name hack is a broadcast-only transport, I fear it will also have the same limitations as all other mesh transports with rely on some kind of broadcast message. For example, lot of work has been done in OLSR to reduce the amount of broadcast traffic (like multi-point relays, etc), and broadcasts overwhelming the mesh is still an issue. Any kind of message relaying in a broadcast-only transport will exacerbate this problem.
.hc Paul Gardner-Stephen wrote: > Hello, > > On Wed, Oct 8, 2014 at 10:57 PM, Nathan of Guardian < > nat...@guardianproject.info> 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. > > Paul. > > >>> >>> Paul. >>> >>> On Wed, Oct 8, 2014 at 9:45 PM, Nathan of Guardian < >>> nat...@guardianproject.info> wrote: >>> >>>> >>>> >>>> On Wed, Oct 8, 2014, at 06:48 AM, Paul Gardner-Stephen wrote: >>>>> Hello All, >>>>> >>>>> I have been following the discussion about FireChat, Gilgamesh and >> the >>>>> really interesting ideas in it for using bluetooth device names to >>>>> transfer >>>>> data. >>>>> >>>>> As someone pointed out, this transport could be fairly easily used by >>>>> Serval's Rhizome store-and-forward protocol, and this is something >> that I >>>>> am actively trying to find the means to make happen. Once we can >> make >>>>> this >>>>> work, MeshMS (end-to-end encrypted and authenticated text messaging) >> and >>>>> other Rhizome-based services will come for free. If anyone is >> interested >>>>> in helping us add support for this into Serval Mesh, we would >> welcome it. >>>>> >>>>> Paul Gardner-Stephen. >>>>> _______________________________________________ >>>>> Guardian-dev mailing list >>>>> >>>> proje >>>> >>>> How would this affect the root requirement? >>>> >>>> Thanks for the interest and support! >>>> _______________________________________________ >>>> Guardian-dev mailing list >>>> >>>> Post: Guardian-dev@lists.mayfirst.org >>>> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev >>>> >>>> To Unsubscribe >>>> Send email to: guardian-dev-unsubscr...@lists.mayfirst.org >>>> Or visit: >>>> >> https://lists.mayfirst.org/mailman/options/guardian-dev/paul%40servalproject.org >>>> >>>> You are subscribed as: p...@servalproject.org >>>> >> >> >> -- >> Nathan of Guardian >> nat...@guardianproject.info >> > > > > _______________________________________________ > Guardian-dev mailing list > > Post: Guardian-dev@lists.mayfirst.org > List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev > > To Unsubscribe > Send email to: guardian-dev-unsubscr...@lists.mayfirst.org > Or visit: > https://lists.mayfirst.org/mailman/options/guardian-dev/hans%40guardianproject.info > > You are subscribed as: h...@guardianproject.info > -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 _______________________________________________ Guardian-dev mailing list Post: Guardian-dev@lists.mayfirst.org List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: guardian-dev-unsubscr...@lists.mayfirst.org Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: arch...@mail-archive.com
