<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Also moving this discussion to the dev list. We've been talking
about re-writing or replacing the clunky OLSR-Viz that we currently
use to visualize a Commotion mesh on the OpenWRT firmware. Below we
mention a couple options:<br>
<br>
1) Freifunks super jazzy uber-visualizer:
<a class="moz-txt-link-freetext" href="http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html">http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html</a><br>
2) AlterMundi's altermap: <a class="moz-txt-link-freetext" href="http://mapa.mesh.altermundi.net/">http://mapa.mesh.altermundi.net/</a><br>
<br>
I personally like the decentralized, replicated nature of Altermap,
which synchronizes data between hub nodes (using CouchDB), so that
each has a full picture of the entire network. To build off this
idea, we could have nodes pushing their link-state data to nearby
hubs, and then the nodes could periodically pull summarized
snapshots of the network map that they could present to clients. If
the clients want more detailed info, there could be a link to a
nearby hub node, which would present a visualization of the full
data set. The hub node could be running a much more in-depth
visualization, perhaps using something like Freifunk's map.<br>
<br>
Here's a quick sketch of how this could be architected:
<a class="moz-txt-link-freetext" href="http://www.asciiflow.com/#Draw6659252420885764096">http://www.asciiflow.com/#Draw6659252420885764096</a>. <br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>Re: [OTI-Tech] Freifunks new node map</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Wed, 17 Apr 2013 11:29:39 +0200</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Dan Staples <a class="moz-txt-link-rfc2396E" href="mailto:danstaples@opentechinstitute.org"><danstaples@opentechinstitute.org></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:oti-tech@lists.opentechinstitute.org">oti-tech@lists.opentechinstitute.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>On 04/17/2013 12:54 AM, Will Hawkins wrote:
> I've seen some pretty cool network layout "stuff" that is done with d3
> and I think that it would be very worthwhile to investigate how to use
> it for the layout engine for olsr-viz!
>
> Will
>
> On 04/16/2013 06:28 PM, Georgia Bullen wrote:
>> using d3 & leaflet!
>>
>> nice.
>>
>> that's what i've been suggesting to jrb and preston as a way of
>> combining geographic info and network info.
>>
>> -GA
>>
>> On Mon, Apr 15, 2013 at 9:02 AM, Seamus Tuohy <a class="moz-txt-link-rfc2396E" href="mailto:s2e@opentechinstitute.org"><s2e@opentechinstitute.org
></a>> <a class="moz-txt-link-rfc2396E" href="mailto:s2e@opentechinstitute.org"><mailto:s2e@opentechinstitute.org></a>> wrote:
>>
>> It is just so pretty... btw, #battlemesh is the official channel of
>> battlemesh and it is starting to become active.
>>
>> <a class="moz-txt-link-freetext" href="http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html">http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html</a>
>>
>> s2e
>> _______________________________________________
>> OTI-Tech mailing list
>> <a class="moz-txt-link-abbreviated" href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>
>> <a class="moz-txt-link-rfc2396E" href="mailto:OTI-Tech@lists.opentechinstitute.org"><mailto:OTI-Tech@lists.opentechinstitute.org></a>
>> <a class="moz-txt-link-freetext" href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a>
>>
>>
>>
>>
>> --
>> Georgia Bullen
>> Field Operations Technologist, Open Technology Institute
>> <a class="moz-txt-link-rfc2396E" href="http://oti.newamerica.net/"><http://oti.newamerica.net/></a>
>> New America Foundation
>>
>>
>> _______________________________________________
>> OTI-Tech mailing list
>> <a class="moz-txt-link-abbreviated" href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>
>> <a class="moz-txt-link-freetext" href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a>
>>
> _______________________________________________
> OTI-Tech mailing list
> <a class="moz-txt-link-abbreviated" href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>
> <a class="moz-txt-link-freetext" href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a>
I'd also like to point to AlterMundi's mapping software:
<a class="moz-txt-link-freetext" href="http://mapa.mesh.altermundi.net/">http://mapa.mesh.altermundi.net/</a>
The front-end view isn't super sophisticated, but I like their back-end
model for collecting the nodes' data. Basically groups of nodes report
their link-state info (via JSON) to nearby nodes/servers running
CouchDB. Each of these DBs are federated and synchronize their data to a
central internet-routable web server that provides the front-end
display. It's decentralized, and could fit well with our
BigBoard/LittleBoard idea.
AlterMundi's altermap code is here:
<a class="moz-txt-link-freetext" href="https://colectivo.altermundi.net/projects">https://colectivo.altermundi.net/projects</a>
_______________________________________________
OTI-Tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>
<a class="moz-txt-link-freetext" href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a>
</pre>
<br>
</div>
<br>
</body>
</html>