<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Dear Admin,<BR>
<BR>
I would like to add on to Laurence's request below, besides a non-technical user guide, is it possible to also include a technical user guide?<BR>
<BR>
Points to include in the user guide could be<BR>
1) what to download and where<BR>
2) how to reverse engineering your router or mobile with commotion<BR>
3) what configuration is required<BR>
4) how to create a mesh network after having a couple of commotion-enabled UE devices<BR>
and on to other more advanced topics, but that could just be a start<BR>
<BR>
I also like to point out that there are problems with the user login feature on the website, or is that not required afterall?<BR>
<BR>
Hope that this does not come across as a demand but rather a suggestion, I love the idea and will work towards creating a mesh network for seniors to save on mobility costs.<BR>
<BR>
Thank you,<BR>
Vincent<BR>
> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. Re: New here & International Development applications<BR>> (Brian Duggan)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Sun, 02 Oct 2011 18:23:05 -0400<BR>> From: Brian Duggan <bcdugga@gmail.com><BR>> To: laurence bascle <lbascle@gmail.com><BR>> Cc: commotion-discuss@lists.chambana.net<BR>> Subject: Re: [Commotion-discuss] New here & International Development<BR>> applications<BR>> Message-ID: <4E88E449.1020104@gmail.com><BR>> Content-Type: text/plain; charset=UTF-8<BR>> <BR>> Hi Laurence,<BR>> <BR>> Great to hear you're interested in the project, and thanks for your<BR>> thoughtful questions. I'll answer them as best I can for now. Responses<BR>> inline.<BR>> <BR>> On Thu Sep 29 12:38:25 2011, laurence bascle wrote:<BR>> > Hi there,<BR>> ><BR>> > better late than never!<BR>> > I also discovered Commotion via Le Monde's article (so this is almost<BR>> > a french speaker thread! ;), and currently working in the<BR>> > non-profit/human rights sector, I was obviously thrilled.<BR>> > I am Technical Project Manager though not a dev myself, and as such<BR>> > tend to think more of the gap between developers and users/potential<BR>> > stakeholders. I believe it would be great to get more plain language<BR>> > documentation (as accessible say, as the<BR>> > so-successful-LeMonde-article) to promote the concept and the progress<BR>> > of the project to potential community/institutional users. Because the<BR>> > people who will use it are ultimately not devs, but say emergency<BR>> > field workers and Human Rights Defenders (HRDs)! This in turn might<BR>> > totally influence your roadmap (and if you have some vague idea to<BR>> > service the 'third sector', then better develop something fits their<BR>>
> need).<BR>> ><BR>> > I have seen this wiki entry which is a great start I think<BR>> > https://tech.chambana.net/projects/commotion/wiki/Newbie_How_it_Works<BR>> > but as a non-dev there are still a few things I am struggling to<BR>> > understand:<BR>> ><BR>> > 1) what are the USPs (Unique Selling Points) of this project compared<BR>> > to other open source wireless mesh networks initiatives already used<BR>> > (like OLPC<BR>> > http://en.wikipedia.org/wiki/OLPC_XO-1#Wireless_mesh_networking. Oh<BR>> > actually just reading that "Although one goal of the laptop is that<BR>> > all of its software be open source<BR>> > <http://en.wikipedia.org/wiki/Open_source>, the source code for this<BR>> > routing protocol is currently closed source" booh!). I understand one<BR>> > is the integration with TOR, but any others?<BR>> <BR>> The concept behind Commotion is to make the barrier to entry into a<BR>> local mesh network as low as possible while leveraging the inherent<BR>> benefits of mesh networks.<BR>> <BR>> Most existing mesh network platforms require a significant amount of<BR>> networking knowledge of users and deployers. A mesh device running<BR>> Commotion will require the minimum amount of configuration from the<BR>> user. The pre-release of Commotion basically reduces this configuration<BR>> to selecting the name of a mesh network to start or join.<BR>> <BR>> No mesh platforms include a set of commonly-used services or services<BR>> that are suited to take advantage of the unique characteristics of mesh<BR>> networks. Commotion will include anonymization, encryption, and<BR>> communication services by default. Commotion distributions for end user<BR>> devices will also include a services browser. This tool will display<BR>> local services that have been deployed on the mesh network like video,<BR>> chat, streaming radio, and any other services that communities
choose to<BR>> deploy on their networks.<BR>> <BR>> Existing mesh platforms target a very narrow set of hardware, severely<BR>> limiting deployment. Commotion already targets the most common wifi<BR>> hardware, but will also be available for as many consumer wifi devices<BR>> as possible. Commotion will target consumer- and professional-grade<BR>> wireless routers, Windows, Mac OS X, Linux, and mobile phones. The goal<BR>> is to increase the quality of the infrastructure by encouraging users to<BR>> deploy Commotion on as many devices as possible.<BR>> <BR>> ><BR>> > 2) how is the access to the internet addressed, and bandwidth in<BR>> > particular (access to a wider network for HRDs for example is<BR>> > strategically crucial). It would be good to have a non-tech version of<BR>> > why/how 100s can access the internet through the one point/computer<BR>> > and what kind of speed they can expect.<BR>> ><BR>> <BR>> A mesh network does not include Internet access by default. At least one<BR>> mesh node must be connected to the Internet to provide Internet access<BR>> to other nodes within the mesh. The quality of that Internet access<BR>> would then, of course, be dependent on the quality of the link of that<BR>> single node, or "backhaul". But since wireless links between nodes are<BR>> inherently lossy, the quality of the Internet connection for any node<BR>> within the network would also depend on the number of links, or "hops",<BR>> between it and the backhaul node. It would also depend on the quality of<BR>> those hops.<BR>> <BR>> But a mesh network can also utilize multiple backhauls. The more<BR>> backhauls that users can incorporate into the mesh, the more robust<BR>> Internet access will be. More backhauls - even low-quality backhauls -<BR>> will at the very least decrease the number of hops for some nodes in a mesh.<BR>> <BR>> That said, developing a very basic non-techy table of numbe
r of<BR>> backhauls vs backhaul quality vs number of hops would certainly be<BR>> helpful, and we will attempt to incorporate this into our non-technical<BR>> documents as we go forward.<BR>> <BR>> > 3) Commotion routers and their role, and access from say deep Rural<BR>> > Northern Uganda.<BR>> ><BR>> <BR>> One of the primary benefits of a mesh network is its unique capacity to<BR>> distribute local services to mesh participants without Internet<BR>> backhauls. For example, in my hometown we have a low-power FM radio<BR>> station whose range has been severely limited by the geography of the<BR>> area. Once my community deploys mesh nodes, we can start a very simple<BR>> network service at the station that will stream the audio from the<BR>> soundboard out to any user on the mesh, effectively extending the range<BR>> of the radio station without any Internet access.<BR>> <BR>> Rural areas are egregiously underserved by commercial Internet service<BR>> providers, but a mesh network reduces the need for Internet service in<BR>> the first place. By encouraging hyper-local services and communication,<BR>> communities can reduce their dependence on commercial Internet service<BR>> providers.<BR>> <BR>> Further, mesh networks can be connected to other mesh networks very<BR>> easily. Mesh node radios within a village may be low-power or only use<BR>> low-gain antennas. But a high-power, directional radio could connect a<BR>> village mesh with any other village mesh within range. This would<BR>> connect multiple rural villages to each other the same way that<BR>> villagers are connected to each other by their local mesh. Local<BR>> services in one village could be extended to other villages.<BR>> <BR>> Then, if one village acquired a sufficiently high-data-rate Internet<BR>> backhaul, that backhaul could be shared with other villages.<BR>> <BR>> > Ok, that's a lot to address, but hopefully there will be a
few people<BR>> > out there who are able to answer! I'd suggest best done via the wiki,<BR>> > and then send us a link,<BR>> > thanks!<BR>> ><BR>> <BR>> Great idea. I think these answers should go on our upcoming<BR>> non-technical site. Meanwhile, feel free to respond with your thoughts.<BR>> <BR>> > PS: wasn't chambana down yesterday?<BR>> ><BR>> <BR>> Yes, it was. Our apologies. We're working to upgrade access to the<BR>> Commotion source code. It's up now, and all public-facing functionality<BR>> has been restored.<BR>> <BR>> Thanks!<BR>> Brian<BR>> <BR>> > Laurence<BR>> ><BR>> ><BR>> > On Fri, Sep 2, 2011 at 6:00 PM,<BR>> > <commotion-discuss-request@lists.chambana.net<BR>> > <mailto:commotion-discuss-request@lists.chambana.net>> wrote:<BR>> ><BR>> > Send Commotion-discuss mailing list submissions to<BR>> > commotion-discuss@lists.chambana.net<BR>> > <mailto:commotion-discuss@lists.chambana.net><BR>> ><BR>> > To subscribe or unsubscribe via the World Wide Web, visit<BR>> > http://lists.chambana.net/mailman/listinfo/commotion-discuss<BR>> > or, via email, send a message with subject or body 'help' to<BR>> > commotion-discuss-request@lists.chambana.net<BR>> > <mailto:commotion-discuss-request@lists.chambana.net><BR>> ><BR>> > You can reach the person managing the list at<BR>> > commotion-discuss-owner@lists.chambana.net<BR>> > <mailto:commotion-discuss-owner@lists.chambana.net><BR>> ><BR>> > When replying, please edit your Subject line so it is more specific<BR>> > than "Re: Contents of Commotion-discuss digest..."<BR>> ><BR>> ><BR>> > Today's Topics:<BR>> ><BR>> > 1. Re: New here (Yann Forget)<BR>> > 2. Re: New here (L. Aaron Kaplan)<BR>> > 3. Introducing myself. (Merouan Mekouar)<BR>> ><BR>> ><BR>> > -------------
---------------------------------------------------------<BR>> ><BR>> > Message: 1<BR>> > Date: Fri, 2 Sep 2011 00:19:58 +0530<BR>> > From: Yann Forget <yannfo@gmail.com <mailto:yannfo@gmail.com>><BR>> > To: F L <legendre@tik.ee.ethz.ch <mailto:legendre@tik.ee.ethz.ch>>,<BR>> > commotion-discuss@lists.chambana.net<BR>> > <mailto:commotion-discuss@lists.chambana.net><BR>> > Subject: Re: [Commotion-discuss] New here<BR>> > Message-ID:<BR>> > <BR>> > <CAKcJoPk0eSJwuBCU2N-_cX0fUPBFCMajnrB7YqBP-pC=jxtY5Q@mail.gmail.com<BR>> > <mailto:jxtY5Q@mail.gmail.com>><BR>> > Content-Type: text/plain; charset=ISO-8859-1<BR>> ><BR>> > 2011/9/1 F L <legendre@tik.ee.ethz.ch<BR>> > <mailto:legendre@tik.ee.ethz.ch>>:<BR>> > > Hi Yann,<BR>> > > Since you're in India, are you aware of?http://drupal.airjaldi.com/<BR>> ><BR>> > Yes, I wrote to them.<BR>> ><BR>> > > Cheers,<BR>> > > --<BR>> > > Franck<BR>> ><BR>> > Regards,<BR>> ><BR>> > Yann<BR>> ><BR>> ><BR>> > ------------------------------<BR>> ><BR>> > Message: 2<BR>> > Date: Thu, 1 Sep 2011 20:59:31 +0200<BR>> > From: "L. Aaron Kaplan" <aaron@lo-res.org <mailto:aaron@lo-res.org>><BR>> > To: Yann Forget <yannfo@gmail.com <mailto:yannfo@gmail.com>><BR>> > Cc: commotion-discuss@lists.chambana.net<BR>> > <mailto:commotion-discuss@lists.chambana.net>, F L<BR>> > <legendre@tik.ee.ethz.ch <mailto:legendre@tik.ee.ethz.ch>><BR>> > Subject: Re: [Commotion-discuss] New here<BR>> > Message-ID: <DF7F2CE4-1C42-4B9D-B062-6AFF77EA2B8D@lo-res.org<BR>> > <mailto:DF7F2CE4-1C42-4B9D-B062-6AFF77EA2B8D@lo-res.org>><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> ><BR>> ><BR>> > On Sep 1, 2011, at 8:49 PM,
Yann Forget wrote:<BR>> ><BR>> > > 2011/9/1 F L <legendre@tik.ee.ethz.ch<BR>> > <mailto:legendre@tik.ee.ethz.ch>>:<BR>> > >> Hi Yann,<BR>> > >> Since you're in India, are you aware of http://drupal.airjaldi.com/<BR>> > ><BR>> > > Yes, I wrote to them.<BR>> ><BR>> > Hehe, I proposed the same :)<BR>> ><BR>> ><BR>> > a.<BR>> ><BR>> ><BR>> > -------------- next part --------------<BR>> > A non-text attachment was scrubbed...<BR>> > Name: smime.p7s<BR>> > Type: application/pkcs7-signature<BR>> > Size: 2213 bytes<BR>> > Desc: not available<BR>> > URL:<BR>> > <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20110901/2c948fdb/attachment-0002.bin><BR>> > -------------- next part --------------<BR>> > A non-text attachment was scrubbed...<BR>> > Name: PGP.sig<BR>> > Type: application/pgp-signature<BR>> > Size: 243 bytes<BR>> > Desc: This is a digitally signed message part<BR>> > URL:<BR>> > <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20110901/2c948fdb/attachment-0003.bin><BR>> ><BR>> > ------------------------------<BR>> ><BR>> > Message: 3<BR>> > Date: Fri, 2 Sep 2011 12:10:42 -0400<BR>> > From: Merouan Mekouar <merouanm@gmail.com <mailto:merouanm@gmail.com>><BR>> > To: commotion-discuss@lists.chambana.net<BR>> > <mailto:commotion-discuss@lists.chambana.net><BR>> > Subject: [Commotion-discuss] Introducing myself.<BR>> > Message-ID:<BR>> > <BR>> > <CAK1MRQf8wwGUwKo1Vm0zvwxfiGPbfG4WVU5FJD7zs6Aon_PUvQ@mail.gmail.com<BR>> > <mailto:CAK1MRQf8wwGUwKo1Vm0zvwxfiGPbfG4WVU5FJD7zs6Aon_PUvQ@mail.gmail.com>><BR>> > Content-Type: text/plain; charset="iso-8859-1"<BR>> ><BR>> > Hi everyone,<BR>> ><BR>> > My name is Merouan, I am a PhD stude
nt in Political Science at McGill<BR>> > University - Montr?al. I also heard about commotion through the french<BR>> > website lemonde.fr <http://lemonde.fr> and I immediately fell in<BR>> > love with the project!!<BR>> ><BR>> > I am currently doing my research on the concept of "informational<BR>> > cascades"<BR>> > or why random instances of street protest spiral in some cases and not<BR>> > others (for instance, I am trying to understand why would the<BR>> > self-immolation of a street vendor trigger massive protests in<BR>> > Tunisia and<BR>> > not elsewhere in the Arab world). Nothing tech related as you can<BR>> > see but I<BR>> > do speak/write Arabic and French fluently and would be very very<BR>> > happy to<BR>> > help with translations or anything else if need be.<BR>> ><BR>> > Again, I would like to congratulate all those working on the<BR>> > project. Coming<BR>> > from the Arab world, I can only testify on the importance of a<BR>> > free (and<BR>> > secure) access to the internet for the defence of individual freedoms.<BR>> ><BR>> > Cheers!<BR>> ><BR>> > Merouan<BR>> > -------------- next part --------------<BR>> > An HTML attachment was scrubbed...<BR>> > URL:<BR>> > <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20110902/f3214d8b/attachment-0001.html><BR>> ><BR>> > ------------------------------<BR>> ><BR>> > _______________________________________________<BR>> > Commotion-discuss mailing list<BR>> > Commotion-discuss@lists.chambana.net<BR>> > <mailto:Commotion-discuss@lists.chambana.net><BR>> > http://lists.chambana.net/mailman/listinfo/commotion-discuss<BR>> ><BR>> ><BR>> > End of Commotion-discuss Digest, Vol 2, Issue 2<BR>> > ***********************************************<BR>> ><BR>> ><BR>> ><BR>&
gt; ><BR>> > -- <BR>> > Laurence Bascle<BR>> > Technical Project Manager<BR>> > mob: +44 7739 189 035<BR>> > skype: lbascle<BR>> ><BR>> ><BR>> ><BR>> > _______________________________________________<BR>> > Commotion-discuss mailing list<BR>> > Commotion-discuss@lists.chambana.net<BR>> > http://lists.chambana.net/mailman/listinfo/commotion-discuss<BR>> <BR>> -- <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> Commotion-discuss mailing list<BR>> Commotion-discuss@lists.chambana.net<BR>> http://lists.chambana.net/mailman/listinfo/commotion-discuss<BR>> <BR>> <BR>> End of Commotion-discuss Digest, Vol 3, Issue 2<BR>> ***********************************************<BR><BR> </div></body>
</html>