<div dir="ltr">Not sure how we ended up not on commotion-discuss, but re-sending...<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">I imagine you could also just host all of the GIS and CRM files in couchDB as well, potentially in the form of a couchapp (</span><a href="http://couchapp.org/page/index" target="_blank" style="font-family:arial,sans-serif;font-size:13px">http://couchapp.org/page/index</a><span style="font-family:arial,sans-serif;font-size:13px">) and work with Leaflet as the front end for the map.</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">We were thinking about this idea for Tidepools (<a href="http://tidepools.co/" target="_blank">tidepools.co</a>), which is currently uses MongoDB, but could be restructured to work on top of couchDB.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Also re:GIS... Vector maps are much smaller and easier to store, so you might opt for Vector over raster map data if you are working on the RPi.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">-Georgia</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 10:19 AM, Will Hawkins <span dir="ltr"><<a href="mailto:hawkinsw@opentechinstitute.org" target="_blank">hawkinsw@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
<br>
On 10/30/2013 09:52 AM, Ryan Gerety wrote:<br>
> This was also something Will, Andy and I puzzled over recently--we didnt<br>
> have an easy way to communicate over the mesh without running something<br>
> on a laptop.<br>
><br>
> We tried LinPhone, which could probably work with the proper<br>
> configuration, but we couldnt get it configured properly in a short<br>
> amount of time.<br>
<br>
</div>We were able to make a call. I mean that: call. Not calls. As Ryan said,<br>
our success was probably limited by the amount of time we had to spend<br>
on this.<br>
<br>
For posterity, if anyone uses LinPhone, make sure to turn of random port<br>
assignments through the configuration UI. Without this turned off, the<br>
SIP stack on the device chooses a random port each time it starts and<br>
means that calling another user is unecessarily complex.<br>
<span class="HOEnZb"><font color="#888888"><br>
Will<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> We know that Serval hasnt really worked for quick chatting in the<br>
> past--as there is too much delay.<br>
><br>
> When Will, Andy and I were together we did look at Kouchat but didnt try<br>
> it out (or maybe we did, I dont recall for sure). Anyone had experience<br>
> with that?<br>
><br>
> Running MediaGrid was fantastic, but it would be great to think about a<br>
> phone only solution...<br>
><br>
> ...<br>
><br>
> -------- Original Message --------<br>
> Subject: Re: [Commotion-discuss] Has anyone implemented serverless<br>
> messaging over a mesh?<br>
> Date: Tue, 29 Oct 2013 22:57:37 -0400<br>
> From: Evan Hutchison <<a href="mailto:evan_hutchison@post.harvard.edu">evan_hutchison@post.harvard.edu</a>><br>
> To: Dan Staples <<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>><br>
> CC: commotion-discuss <<a href="mailto:commotion-discuss@lists.chambana.net">commotion-discuss@lists.chambana.net</a>><br>
><br>
> Thanks Dan!<br>
><br>
> That is exactly what I am looking for. The replicated database is<br>
> crucial. I'll get it up on our sandbox server asap. I figured you all<br>
> would be working on something like that to complement Commotion.<br>
><br>
> Another question- I want to implement GIS servers and an emergency CRM on<br>
> the Pis but still retain survivability if one or more of the devices gets<br>
> knocked out. Any thoughts on using an Anycast routing scheme and multiple<br>
> instances of the CRM and map server to achieve this? I'm I barking up the<br>
> wrong tree?<br>
><br>
> Best-<br>
> E<br>
><br>
><br>
> On Tue, Oct 29, 2013 at 10:22 PM, Dan Staples <<br>
> <a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>> wrote:<br>
><br>
>> Evan,<br>
>><br>
>> You might want to check out my project MediaGrid:<br>
>> <a href="http://mediagrid.disman.tl/" target="_blank">http://mediagrid.disman.tl/</a><br>
>><br>
>> It implements a decentralized, encrypted webchat service (as well as<br>
>> file sharing), and was designed to run on Raspberry Pis in a mesh network.<br>
>><br>
>> It's decentralized in that each Pi (or whatever device running it) has a<br>
>> database of messages that it continuously synchronizes with the other<br>
>> devices on the mesh, constantly updating with new messages. You can also<br>
>> do private messages to other users in the webchat, similar to IRC.<br>
>><br>
>> Dan<br>
>><br>
>> On 10/29/2013 09:34 PM, Evan Hutchison wrote:<br>
>>> Yes Ben, they do- but it is embedded with the Serval Mesh package which,<br>
>>> as you point out, runs on Android handsets. We are using BATMAN with<br>
>>> Pis as WAPs and routers, as well as with an existing mesh running over<br>
>>> TP-Link routers- so I want something that can run across different<br>
>>> platforms (Linux, Mac OS, Windows, Android) and is independent of their<br>
>>> system.<br>
>>><br>
>>> Right after I posted, of course I found kouchat<br>
>>> <<a href="https://code.google.com/p/kouchat/" target="_blank">https://code.google.com/p/kouchat/</a>> which runs on everything but<br>
>>> IPhones. It does the trick, but I would like to find something that<br>
>>> allows for MUCs.<br>
>>><br>
>>> Thanks Dean, will check it out.<br>
>>><br>
>>><br>
>>> On Tue, Oct 29, 2013 at 9:15 PM, Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a><br>
>>> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>>> wrote:<br>
>>><br>
>>> Doesn't Serval have a messaging implementation that they've used on<br>
>>> Android handsets?<br>
>>><br>
>>><br>
>>> On Tue, Oct 29, 2013 at 6:48 PM, Evan Hutchison<br>
>>> <<a href="mailto:evan_hutchison@post.harvard.edu">evan_hutchison@post.harvard.edu</a><br>
>>> <mailto:<a href="mailto:evan_hutchison@post.harvard.edu">evan_hutchison@post.harvard.edu</a>>> wrote:<br>
>>><br>
>>> Hi all-<br>
>>><br>
>>> I'm working with my media lab class on an off-the-grid emergency<br>
>>> response mesh network. We want to integrate messaging. I was<br>
>>> initially experimenting with a Jabber server but decided<br>
>>> serverless messaging would better solve the problem- we want to<br>
>>> avoid centralization as much as possible so that if one node<br>
>>> goes down, folks can still communicate across the LAN or WAN<br>
>>><br>
>>> I ran across a description of an XMPP-like serverless messaging<br>
>>> system: <a href="http://xmpp.org/extensions/xep-0174.html" target="_blank">http://xmpp.org/extensions/xep-0174.html</a><br>
>>><br>
>>> Anyone have any experience or insights?<br>
>>><br>
>>> Thanks-<br>
>>> Evan<br>
>>><br>
>>> _______________________________________________<br>
>>> Commotion-discuss mailing list<br>
>>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>>> <mailto:<a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a>><br>
>>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Ben West<br>
>>> <a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br>
>>> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>><br>
>>> <a href="tel:314-246-9434" value="+13142469434">314-246-9434</a> <tel:<a href="tel:314-246-9434" value="+13142469434">314-246-9434</a>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Commotion-discuss mailing list<br>
>>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>>><br>
>><br>
>> --<br>
>> Dan Staples<br>
>><br>
>> Open Technology Institute<br>
>> <a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
>> OpenPGP key: <a href="http://disman.tl/pgp.asc" target="_blank">http://disman.tl/pgp.asc</a><br>
>> Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9<br>
>> _______________________________________________<br>
>> Commotion-discuss mailing list<br>
>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>><br>
>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OTI-Tech mailing list<br>
> <a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a><br>
> <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>
OTI-Tech mailing list<br>
<a href="mailto:OTI-Tech@lists.opentechinstitute.org">OTI-Tech@lists.opentechinstitute.org</a><br>
<a href="https://lists.opentechinstitute.org/mailman/listinfo/oti-tech" target="_blank">https://lists.opentechinstitute.org/mailman/listinfo/oti-tech</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Georgia Bullen<div>Field Operations Technologist, <a href="http://oti.newamerica.net/" target="_blank">Open Technology Institute</a></div><div>New America Foundation</div>
</div>