Hey all!
Just a reminder that we have a mesh hack night tonight, starting at 7:30 (a
bit earlier than usual). Some folks have been working hard on the firmware
this week, so we'll update on that, and generally be working and helping
each other out :) Come on by and dive in!
Cheers,
Jenny
http://jennyryan.nethttp://thepyre.orghttp://thevirtualcampfire.orghttp://technomadic.tumblr.com
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
Hey y'all!
Just a quick intro: I'm the Community Manager at Open Garden, a company
making a mesh networking app for Android based in SF. I'm also a
decentralization enthusiast and liberty activist.
I'm interested in discussing potential collaborations between the Open
Garden community and Oakland mesh outreach. The first idea that comes
to mind for me is holding local events based on education about mesh
networking both in Oakland and SF. Oakland is obviously the most
important community to focus on for the Oakland mesh (duh), however
there can be a lot of benefit from marketing the project to a wider
audience - especially since SF is right next door.
How awesome would it be to do a basic demo using Internet from somewhere
like the TechShop and sending it to Yerba Buena Gardens for example?
There could also be a chance at leveraging the marketing from the
Google/SF WiFi initiative... something that says "Hey... we're trying to
do something similar over here but even better!" Of course while trying
to avoid pissing off Goog or SF.
Anyways... I know some (probably most) of you may have some reservations
about collaboration with a company making proprietary software on a
moral ground but I'm interested in discussion on mutual benefit - both
for outreach and as complementary solutions for meshing the planet! ;)
Be well,
Paige Peterson
"GNU's Framework For Secure Peer-to-Peer
Networking<https://gnunet.org/internetistschuld>
"
This is the video from the talks given by Christian Grothoff, Carlo von
Lynx, Jacob Appelbaum and Richard Stallman in Berlin on August 1st.
Very interesting.
I added some concerns to the wiki about the risk of malicious node
operators using sslstrip. I am interested to hear feedback on this.
https://sudoroom.org/wiki/Mesh/Challenges
Scott J.
>From now on every last Thursday of the month will be a general meeting with
discussions, decisions and an agenda. The next general meeting will be on
Thursday the 29th of August at 7:30 pm.
On all other Thursdays there will be a hack night starting at 7:30 pm
(NOTE: this is an hour earlier than previously).
The hack nights will be for actually working on stuff, not for discussions
or introducing new people to the project. We should discourage new people
from showing up for hack nights unless they are willing to read up about
our project on the wiki and dive right into a task during the hack night.
We are doing this because we have been seeing a trend where new people show
up and we spend a lot of time introducing them to the project and answering
their questions, and then they don't show up again and we get little real
work done.
--
Marc Juul
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
My name is Pau from Barcelona. I have heard about your project in the
battlemesh mailing list. First of all, congratulations for starting
such kind of initiative, I hope you succeed.
In my place I'm working in the development of a Mesh firmware named
qMp [2] which is being used mainly in our community network Guifi.net
[3].
The purpose of sending this mail comes from what I read in your Wiki
[4] about create a new firmware. IMHO it is a mistake since there are
several projects already created, probably too much because we are
dividing our strength.
Recently (thanks to the battlemesh and other events like that) we have
started a new project to put all the development efforts together and
make a firmware generic and useful for everybody. The idea is to make
a meta-firmware which can be used as basis to create specific
community firmwares. The project is named libre-mesh [5].
Until now three existing mesh communities have joined: Guifi.net
(Catalonia), AlterMesh (Argentina), Eigennet (Italy). I would like to
invite you to participate. We have a huge experience in the
OpenWRT-based distributions for mesh networking, I hope you are able
to take advantage of it.
I don't pretend to start a large discussion about routing protocols,
but I would like to summary our conclusions because they can be useful
for us. Batman-adv is very nice, but you cannot have a single
collision domain cloud for all the nodes because it does not scale.
So, the network have to be splitted in several clouds. To federate
them a layer3 routing protocol is needed, so here is where we use BMX6
[7]. Why? because BMX6 (100% rewritten fork of Batmand with native
IPv6 support) is very powerful and produces a very low overhead (see
[6]). Here [8][9] find a couple of small diagrams to understand a
little better this model.
Cheers.
PS: do not use ARC Freestations, they use Ralink USB chips and driver
is bullshit in ad-hoc mode.
PS2: CCed Libre-Mesh mailing list
[1] mesh(a)lists.sudoroom.org
[2] http://qmp.cat
[3] http://guifi.net
[4] https://sudoroom.org/wiki/Mesh/Firmware
[5] http://libre-mesh.org
[6] https://libre-mesh.org/attachments/download/12/overhead_mobile.png
[7] http://bmx6.net
[8] https://libre-mesh.org/attachments/download/4/smartmesh2.png
[9] https://libre-mesh.org/attachments/download/17/lime-modes1.jpg
- --
./p4u
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAEBAgAGBQJR9FHbAAoJEAX7rWpc+YnN1wsH/ROdF+IsNU8X9Ub0BslkEVw4
d0ixSUH2WQKwxd58iIf+4TbsH4SXHUQlm726KnCJMRx2hzZ9E/dyItrVvbrk9Vbw
YUS59VeVwqBqo39Pu16pxDoA4hrQa3yNi+Cq3CBOQlBh/oKf1r1OFNOznhkrzdNj
7pp/L146NSyl+TJ1U3nPpikf7AAvPVfU/ege/cLGrmDeP6rGdtArLJzGRDM/8syw
pQ/A75u11IyFs00EgJJufhG4ZSbKoZIaePOZAfONPKi+WxRJZsJw4IDxp7Gd3+wF
Dk5GPj5afDjSZpM8zxK88bwDUz6jW5S8V+pQd0+TnwcaqIrlYOqDI5ublyC9Z4s=
=Nr0g
-----END PGP SIGNATURE-----
