[Commotion-dev] Serval Mesh Helper Device / ISM long-range meshing work

[Paul Gardner-Stephen]

Hello,

On Sat, Feb 9, 2013 at 12:55 AM, The Doctor <drwho at virtadpt.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/07/2013 03:23 PM, Paul Gardner-Stephen wrote:
>
>> 2. A Twitter-like mesh-based micro-blogging service (possibly with
>> a gateway to Twitter itself)
>
> Project Byzantium is considering a CouchApp called Toast for this
> purpose.  It's built on top of CouchDB, so we think it should be
> possible to distribute across arbitrary numbers of CouchDB nodes with
> a little hackery under the hood:
>
> - - Avahi/mDNS to collect IP addresses of other nodes (or,
> alternatively, scrape the node's routing table for
> /^192\.168\.[0-9]*\.[1-9][0-9]?/
> - - A shell script that runs every minute or two that pings the
> CouchApp's replication URI with those IP addresses.

Rhizome can let you avoid the scripted replication entirely, as once a
bundle is submitted to Rhizome, then the distribution/synchronisation
is an an automatic part of mesh functions.

The other nice thing for a twitter-type service is that you can grow a
bundle in an append-only mode, and (once we finish the code),
synchronisation occurs for only the added part among nodes that have
older (ie shorter) versions of the bundle.  In fact, this is how our
MeshMS (SMS-like) delay-tolerant short message service is implemented.

>> 3. Distribution of either introduced or locally produced
>> news/content
>
> It seems as if there are several ways of accomplishing this, from
> replicatable databases like CouchDB to custom apps that use DHTs to
> store-and-forward accomplished with UDP and IP multicasting (which is
> what Litter does).
>
>> Essentially it is best to think of it as a courier service between
>> nodes, like an inter-campus mail service, rather than a bulk
>> real-time
>
> We're treating each node like a dialup BBS in that respect.  Store
> local material, maintain a list of neighboring nodes, synchronize with
> neighboring nodes periodically to maintain a
> close-enough-for-government-work state when compared to those
> neighboring nodes.

See above, as Rhizome simplifies and generalises this.

It would be nice if we can make our solutions interoperable, if not
with technological commonality.

Paul.

> - --
> The Doctor [412/724/301/703] [ZS|Media]
> Developer, Project Byzantium: http://project-byzantium.org/
>
> PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F  DD89 3BD8 FF2B 807B 17C1
> WWW: https://drwho.virtadpt.net/
>
> LOAD "*",8,1
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iEYEARECAAYFAlEVCuMACgkQO9j/K4B7F8GH8wCg6Arg4TNgXD44rKiRb8c+4eQ0
> CcUAni8p5XhWQdJo40vrNHiS3K8HZK2Y
> =HRX5
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>