<div dir="ltr">Hello,<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 23, 2013 at 1:52 AM, Dan Staples <span dir="ltr"><<a href="mailto:danstaples@opentechinstitute.org" target="_blank">danstaples@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's a good idea, Paul. I've been thinking about a lot of things that<br>
we could use the Rhizome layer to replicate across a mesh. One thing<br>
that could make it more useful for things like this is having a RESTful<br>
API, especially for web-based applications. Are there any plans for<br>
expanding the Rhizome API?</blockquote><div><br></div><div style>Funny you should mention this. We were just yesterday talking about HTTP-based APIs to get to contents of Rhizome bundles. This would map very naturally to a RESTful-type interface.</div>
<div style><br></div><div style>So in short, yes, we do intend to expand the Rhizome API as and when we are able. A simplistic implementation of an API that will allow access to HTTP-transported documents from in a bundle is likely to show up in the coming weeks, but I will let Jeremy confirm or deny my understanding of this ;)</div>
<div style><br></div><div style>Paul. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Wed 17 Apr 2013 07:09:33 PM EDT, Paul Gardner-Stephen wrote:<br>
> Hello,<br>
><br>
> Another approach to replicating this visualisation data is to use<br>
> Rhizome to replicate the network structure information for<br>
> visualisation on nodes. This could feasibly be integrated with these<br>
> existing tools.<br>
><br>
> Paul.<br>
><br>
><br>
> On Wed, Apr 17, 2013 at 7:58 PM, Dan Staples<br>
> <<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>>> wrote:<br>
><br>
> Also moving this discussion to the dev list. We've been talking<br>
> about re-writing or replacing the clunky OLSR-Viz that we<br>
> currently use to visualize a Commotion mesh on the OpenWRT<br>
> firmware. Below we mention a couple options:<br>
><br>
> 1) Freifunks super jazzy uber-visualizer:<br>
> <a href="http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html" target="_blank">http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html</a><br>
> 2) AlterMundi's altermap: <a href="http://mapa.mesh.altermundi.net/" target="_blank">http://mapa.mesh.altermundi.net/</a><br>
><br>
> I personally like the decentralized, replicated nature of<br>
> Altermap, which synchronizes data between hub nodes (using<br>
> CouchDB), so that each has a full picture of the entire network.<br>
> To build off this idea, we could have nodes pushing their<br>
> link-state data to nearby hubs, and then the nodes could<br>
> periodically pull summarized snapshots of the network map that<br>
> they could present to clients. If the clients want more detailed<br>
> info, there could be a link to a nearby hub node, which would<br>
> present a visualization of the full data set. The hub node could<br>
> be running a much more in-depth visualization, perhaps using<br>
> something like Freifunk's map.<br>
><br>
> Here's a quick sketch of how this could be architected:<br>
> <a href="http://www.asciiflow.com/#Draw6659252420885764096" target="_blank">http://www.asciiflow.com/#Draw6659252420885764096</a>.<br>
><br>
><br>
> -------- Original Message --------<br>
> Subject: Re: [OTI-Tech] Freifunks new node map<br>
> Date: Wed, 17 Apr 2013 11:29:39 +0200<br>
> From: Dan Staples <<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>><br>
</div></div><div class="im">> <mailto:<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>><br>
> To: <a href="mailto:oti-tech@lists.opentechinstitute.org">oti-tech@lists.opentechinstitute.org</a><br>
> <mailto:<a href="mailto:oti-tech@lists.opentechinstitute.org">oti-tech@lists.opentechinstitute.org</a>><br>
><br>
><br>
><br>
> On 04/17/2013 12:54 AM, Will Hawkins wrote:<br>
> > I've seen some pretty cool network layout "stuff" that is done with d3<br>
> > and I think that it would be very worthwhile to investigate how to use<br>
> > it for the layout engine for olsr-viz!<br>
> ><br>
> > Will<br>
> ><br>
> > On 04/16/2013 06:28 PM, Georgia Bullen wrote:<br>
> >> using d3 & leaflet!<br>
> >><br>
> >> nice.<br>
> >><br>
> >> that's what i've been suggesting to jrb and preston as a way of<br>
> >> combining geographic info and network info.<br>
> >><br>
> >> -GA<br>
> >><br>
> >> On Mon, Apr 15, 2013 at 9:02 AM, Seamus Tuohy <<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a><br>
</div><div class="im">> > <mailto:<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a>>> <mailto:<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a>> <mailto:<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a>>> wrote:<br>
> >><br>
> >> It is just so pretty... btw, #battlemesh is the official channel of<br>
> >> battlemesh and it is starting to become active.<br>
> >><br>
> >> <a href="http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html" target="_blank">http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html</a><br>
> >><br>
> >> s2e<br>
> >> _______________________________________________<br>
> >> OTI-Tech mailing list<br>
> >> <a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>><br>
</div>> >> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>><br>
<div class="im">> >> <a href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech" target="_blank">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> --<br>
> >> Georgia Bullen<br>
> >> Field Operations Technologist, Open Technology Institute<br>
</div>> >> <<a href="http://oti.newamerica.net/" target="_blank">http://oti.newamerica.net/</a>> <<a href="http://oti.newamerica.net/" target="_blank">http://oti.newamerica.net/</a>><br>
<div class="im">> >> New America Foundation<br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> OTI-Tech mailing list<br>
</div>> >> <a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>><br>
<div class="im">> >> <a href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech" target="_blank">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a><br>
> >><br>
> > _______________________________________________<br>
> > OTI-Tech mailing list<br>
</div>> > <a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>><br>
<div class="im">> > <a href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech" target="_blank">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a><br>
> I'd also like to point to AlterMundi's mapping software:<br>
> <a href="http://mapa.mesh.altermundi.net/" target="_blank">http://mapa.mesh.altermundi.net/</a><br>
><br>
> The front-end view isn't super sophisticated, but I like their back-end<br>
> model for collecting the nodes' data. Basically groups of nodes report<br>
> their link-state info (via JSON) to nearby nodes/servers running<br>
> CouchDB. Each of these DBs are federated and synchronize their data to a<br>
> central internet-routable web server that provides the front-end<br>
> display. It's decentralized, and could fit well with our<br>
> BigBoard/LittleBoard idea.<br>
><br>
> AlterMundi's altermap code is here:<br>
> <a href="https://colectivo.altermundi.net/projects" target="_blank">https://colectivo.altermundi.net/projects</a><br>
><br>
><br>
> _______________________________________________<br>
> OTI-Tech mailing list<br>
</div>> <a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a> <mailto:<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a>><br>
<div class="im">> <a href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech" target="_blank">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Commotion-dev mailing list<br>
> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
</div>> <mailto:<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a>><br>
> <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
><br>
><br>
<br>
--<br>
Dan Staples<br>
<br>
Open Technology Institute<br>
<a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
</blockquote></div><br></div></div>