Yes it's Thursday again, and that means updates and hacking!
Tentative agenda:
*Introductions
*Updates from team-members
*Delegate missing essential features for sudowrt 0.1
*Set deadline for sudowrt 0.1 release?
*Hack all night
See you in sudo room! Bring snacks if ya can!
--
Marc
Let's build something beautiful!
Ping if you want to participate in building peoplesopen.net or sudomesh.org
We need it all!
Attached is a potential logo for sudomesh, very similar to sudoroom's new
branding (yet to be implemented... ping if you want to help with that, too
;P).
I made a business card with this logo and used it during the conference
(off my phone ;) - also attached.
I won't make it to this week's meetup, returning Friday from Berlin! Will
be making a writeup tomorrow :)
<3
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
We're having our weekly hacknight tonight at sudo room at 7:30 pm.
Maybe we can spend minimal time talking and just sit down and get some work
done? Here's a suggested agenda:
1. Introductions
2. Order stickers
3. Updates
4. Hack on stuff!
Things to work on:
*sudomesh.org web content and design
*peoplesopen.net web content and design
*Firmware (many aspects)
*sudomesh logo design
*Splash page content and design
*Fake captive portal
*Internet is down page design
*Secure VPN setup for exit nodes
*Fundraising (y-combinator grant?)
*Organizing workshops?
*Electronics and software for DisasterRadio!
Bring some snacks and caffeine!
--
Marc
Also a highly relevant conversation. I'll give a more in-depth reportback
once I have finally escaped the wondrous black hole that is c-base.
---------- Forwarded message ----------
From: Jenny Ryan <jenny(a)thepyre.org>
Date: Thu, Oct 3, 2013 at 4:53 PM
Subject: Notes on Governing the Wireless Commons
To: Greg Bloom <greg.bloom(a)gmail.com>
1. Clearly defined *boundaries*, which delineate who has access to the
Common pool resource.
- *"I clearly understand for which resources I need to care and with
whom I share this responsibility*."
- "This network is open to everyone" is also a clear boundary.
- Many forms of contribution make it difficult to define boundaries.
- Hyperlocal services provisioned to a specified area.
- Take the risks and define boundaries when necessary.
- Once connected to the Internet (which is propietary), terms and
conditions may apply.
2. Appropriation and provision *rules* which are tailored to local
conditions.
- *"We use the means (time, space, technology, and the quantity of a
resource) that are available in a given context. As commoner I am satisfied
that there is a fair relationship between my contributions and the benefits
I receive."*
- Rule of Who's not In is Out.
- Cellular network in Oaxaca, once they had it, it was available to
other communities, and the network community decided that they did not want
the other communities to be able to access their network.
- "Rules" makes it seems like it's set in stone.
3. Collective-choice arrangements, that allow most resource appropriators
to participate in the *decision-making* process.
- *"We enter into or modify our own rules and commitments, and every
commoner can participate in this process. Our commitments serve to create,
maintain, and preserve the commons to satisfy our needs."*
- BTOP project in Philadelphia to build out computer centers sought out
community group buy-in, in order to more effectively implement the project.
- Do-ocracy: Ask for forgiveness not for permission
4. Effective *monitoring* - monitors accountable to appropriators, or are
appropriators.
- *"We monitor the respect of these commitments ourselves and sometimes
we mandate others whom we trust to help reach this goal. We continually
reassess whether our commitments still serve their purpose."*
- In a way, Community Wireless Networks are a resource that is very easy
to monitor (traffic analysis) compared to some other commons.
- Process of monitoring and management is usually limited a smaller
group of people who has technical expertise. Maybe we need better tools for
"lay-users" to be able to monitor and manage common resources.
- "You have too many goats in our field... maybe you can eat some of
them?"
- Problem of "commoners" vs. "consumer-commoners"
- Think of a church which gives food only to those who worship with
them, vs one that provides to everyone and invites them to worship.
- Disconnect / lack of empathy between consumers and producers is core
to the problem
5. Graduated *sanctions* for resource appropriators who violate
operational community rules.
- *"We work out appropriate rules for dealing with violations of our
commitments. We determine whether and what kinds of sanctions shall be
used, depending on the context and severity of a violation."*
- Technological sanctions like ACLs (Access control list can ban certain
devices), filtering, QOS.
- What are some user-friendly (positive) graduated sanctions we could
adopt?
- Freifunk: Script running a system of points for individual nodes that
are throttled when a certain limit is reached
6. *Conflict resolution* mechanisms that are cheap and rapidly accessed.
- *"Every commoner can make use of a space and means for conflict
resolution. We seek to resolve conflicts among us in an easily accessible
and straightforward way."*
- Guifi has a formalized conflict resolution process. Gufi has a
operator license that is an umbrella for the members of the foundation.
- If an organization fails to fulfill the license agreement, the
following steps are taken:
- 1. Contact directly the organizers
- 2. Have an open discussion between the parties
- 3. Have a sit down meeting.
- 4. Generally turns out that one party has not fulflilled the license
and that is the source of the conflict.
- 5. Final step is taking the conflict to court
- Creator/consumer user hierarchy among the commoners - on one end is
simply agreement to the TOS, the other creating the rules.
7. *Self-determination* of the community recognized by higher-level
authorities.
- *"We regulate our own affairs, and external authorities respect that."*
- There are new regulations (in Germany?) that make it so that network
operators are also held accountable for violations, which makes people
nervous.
- DC had a municipal fiber networks that other organizations could
connect to - community anchor institutions attempted to organize mesh
networks, which spooked the government into rejecting it (due to their
lack of formal institutional structure).
- Must adjust self-governing principles to cooperate with the
authorities. We mostly work in wireless because that's where we *can* be
self-determining (open spectrum).
- CONFINE project funded by the EU supports the formation of local
community wireless networks
8. *Nested enterprises. *Larger CPRs are organised in the form of
multiple layers of nested enterprises, with small local CPRs at the base
level.
- *"We realize that every commons is part of a larger whole. Therefore,
different institutions working at different scales are needed to coordinate
stewardship and to cooperate with each other."*
- Network (FNF) in Kansas city has a design pattern that reflects
different levels of functionality and access. Guifi.net has zones. Many
different projects have a concept of different levels of access. Freifunk
and c-base have a layered structure, where each part of the structure
manages its own resources but they have a common idea or interest.
- Burning Man is a large organization that could be characterized as
having a similar structure.
- A common identity helps everyone to feel associated, like Freifunk or
CCC. Guifi could be a similar model - The Guifi Foundation hosts
principles for new network organizations to form around.
Notes from tonight's meeting re: Network Commons Licensing :)
Please give feedback in the next 24 hours if you have any questions for
folks! We have also created a temporary list here, which was spawned during
our meeting with Pau, Roger and Isaac some weeks ago:
lists.sudoroom.org/listinfo/tmpcommonsnet
Follow #is4cwn, the talks are streaming live and there's some excellent
tweeting going on!
Cheers from Berlin!
Jenny
---------- Forwarded message ----------
From: Jenny Ryan <tunabananas(a)gmail.com>
Date: Thu, Oct 3, 2013 at 10:04 PM
Subject: Notes from Network Commons License mtg @ IS4CWN2013
To: tmpcommonsnet <tmpcommonsnet(a)lists.sudoroom.org>
Greetings comrades!
A pleasure to participate in a most excellent roundtable discussion moving
toward a network commons license this evening at c-base!
Here are the notes off the etherpad, for documentation and sharing with our
friends across the pond. I will also shortly start a thread for a round of
introductions :-)
-------
This pad is meant to just as an index. Discussions must be kept in
individual pads
(tmp) mailing list
http://lists.sudoroom.org/listinfo/tmpcommonsnet
name
http://etherpad.guifi.net/L2-org-name
vision and mission
http://etherpad.guifi.net/L2-mission
initial pad THAT MUST BE REWORKED
http://etherpad.guifi.net/C4EU-orgs
=======================================================
rought notes of meeting at IS4CWN 2013
*) we continue the discussion via the tmp mailing list
pls send any update, no matter from where
*) international organisations
ISOC
RIRs (e.g. RIPE-NCC, )
*) international actions
lobbyingg
policy making
*) license
*) network map
to have a big picture
*) define what a CN is
=> which/who can be accepted at the L2org
FNF proposal: https://commons.thefnf.org/index.php/Free_network_definition
0. Freedom to participate and to make others participate
L2 access vs L3 access => access the network vs peering with the
network => joining th commons vs extending the commons
1. Freedom to communicate using the network for any purpose without
interception or interference - and free of charge
2, The freedom to modify and improve the network, including the ability to
access, author and distribute information about how the network functions.
? non-(private?)-profit with the network itself
not really sure if this must be at this level (could/should be placed
in the licence)
Fair profit [guifi] - can be legally enforced
Transit inside the network should be free
Guifinet: Difference between Network and content. Access to the
Internet is content
internally must be free. to get outside might be charged
Precaution that we maintain actual freedom - problem with Creative
COmmons is that much that is licensed under CC is not actually free
(non-commercial)
Additional concerns (very likely not to go to the def/license but as
recommendations)
The freedom to know the ecologial impact of the hardware?
The right to ask for the information about the hardware?
fairness as a restriction?
running free software?
distribured property (multistakeholder)
is not a request, but it is recommended
Cannot charge a fee to interconnect the commons.
Access to knowledge as a fundamental principle:
http://en.wikipedia.org/wiki/Access_to_knowledge_movement
Three themes here:
Free Network
Community Network - owned by the community
Profit / Non-profit
overlay net. vs physical net
we are talking about phy
what about mixed overlay+phy networks (e.g. fon)?
difference between the picopeer agr and our efforts
*)*) licence
FNF proposal
http://commons.thefnf.org/index.php/Network_Commons_License
creative-commons-like incremental license proposed by Mitar at Oakland (?)
suggestion: confront with statistics of CC in terms for flavours used
examples of additional clauses:
- free software only
- ecological footprint
- not for profit
- owned by the users?
Membership
???
=Action Items=
* Isaac: Take 'owned by its users' out of the preamble
* Annemarie will pass around suggestions for legal frameworks
* Isaac: compare the picopeer agr and our def
* roger: rewrites these notes and sends them to the ml
* christian: contacts a RIPE college
* jenny: send notes to the list
-------
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
Hi! I found this on eBay and thought you might like it! Check it out now!
Ubiquiti Power Station 5 Ext No Reserve!!! (PS5EXT) (PSE1)
http://r.ebay.com/o71Ptw
-steve
For those of you who haven't heard the news from Jenny, yet: Open Garden
decided to publicly release the original white paper "Multi-hop Wi-Fi
Offload <https://opengarden.com/Multi-hop_Wi-Fi_Offload.pdf>" by CTO,
Stanislav Shalunov.
Hopefully this brings some inspiration and answers some questions (ex.
Mitar: Why Bluetooth?)
Also, please excuse my lack of participation this past month - I'll be
back in the action next month. I'm also going to a festival called
Libertopia <http://libertopia.org> this weekend in San Diego where I'll
attempt to spread the word. These people are really into alternative,
decentralized services.
I'm starting my drive down tonight so have a great meeting and enjoy the
weekend everyone!
Peace.
-Paige
Hi everybody,
I kept notes that maybe we can expand on and add to the wiki. My notes are
mostly bullet points, but it's a decent summary of the meeting. I was going
to expand on a few points, but I don't have the time right now. Also,
where's the diagram that Marc had during the meeting? I didn't see it on
the wiki. Do we have any other information that would help new people
understand how to get involved? Max mentioned layers, maybe we can focus
the project into different layers and have separate meetings for those
layers.
Take care,
Jeremy
Low Bandwidth (disaster)
----------------------------------------------------------
-Using legal frequencies (900-928Mhz, Flutter, citizen band, amateur band)
-ISM bands
-Website for frequencies: Unwanted emissions > spectrum wiki > allocations
by service
-No encryption is legal
-Hack RF, Blade RF
-Maxim Chip, Iridium Modem 9601 (
http://www.iridium.com/products/iridium9601.aspx)
-IQ, External D/A modulator (sampling rate 10x)
-San Leandro is selling wifi to public
-1W and EIRP
-LCOM has cheap attennas
-LEO birds
High Bandwidth (standard)
-----------------------------------------------------------
-No flashing individually
-SSH generated by decentralized server
-Protocols (no cjds, Batman advanced, tunnel digger for internet, VPN,
LEADBAT, openWRT)
-500mW LUA
-3 SSIDS
-Authentication, encryption
-Protection of nodes by Section 230 of CDA (EFF)
-Server returns fake captive portal
-Firmware pages: internet usage, connected, testing the node (RSSI), change
password
-No using MD5 or broken encryption, no auto-authentication of other
certificates
-Open Garden uses Bluetooth
Per our agreement at last Thursday's meeting, we decided to drop the idea
of flashing nodes with individualized firmware images (since flashing is a
hassle and easier to do in bulk).
Instead, all nodes will be flashed with the same firmware and will then be
booted on a LAN where they will talk to a node configuration server that
will give them their individualized files (such as securely generated SSH
keys). This will also serve as verification that the firmware images have
been successfully flashed.
The node configuration server is controlled via a web interface that Rhodey
is currently writing.
The code is not ready yet, but here's what we have so far:
https://github.com/sudomesh/node-configurator
Also, with the gen_certificates.sh script, we are beginning to lay the
ground-work for a sudomesh.fork() script that will allow easy forking of
the entire project, including rebranding and generation of new
certificates, such that groups in other areas (e.g. SF) can join
peoplesopen.net by starting their own organization.
--
juul
Hey mesh team!
Open Garden is starting a series of social events in the interest of
sparking great conversations, sharing ideas and projects, and co-learning.
I can't be there for the first one, sadly, as it will be a great
opportunity to meet more folks interested in peer-to-peer applications,
mesh networking, decentralized and distributed tech. Also beer.
The first one is next Wednesday at Biergarten:
http://www.meetup.com/Tech-Garden-SF/events/139596332/
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
I've set up a $6 a month VPS (vpscheap.net) and configured mail for our
domains peoplesopen.net and sudoroom.org (and all variations).
I've also set up apache with free SSL certificates (still waiting for the
sudoroom.org certificates) for the domains and installed wordpress for both
domains (we don't have to use wordpress, it's just easy).
Who wants to design / help design our websites and content?
We can do something super simple like a single-page site that links to the
wiki for now, or just find a nice wordpress theme and tweak it, but we
should have _something_ up before the community wireless summit :)
--
Marc
Hi everybody,
I'm new to town and I'm interested in helping with the project. I'll be at
the meeting on Thursday. I wanted to focus more on the hardware aspect side
of things. I have a background as an EE and I haven't had much field
experience with radios and networking, but it's one of the three projects I
will be focusing on in Oakland. One detail that I can't figure out if it's
built into the cjdn nodes bridge to the internet. I'm guessing yes, but I
can't find anything that specifies it.
Maybe somebody will be willing to catch me up with some of the local
project details.
See you tomorrow,
Jeremy
On Wed, Sep 25, 2013 at 12:00 PM, <mesh-request(a)lists.sudoroom.org> wrote:
> Send mesh mailing list submissions to
> mesh(a)lists.sudoroom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sudoroom.org/listinfo/mesh
> or, via email, send a message with subject or body 'help' to
> mesh-request(a)lists.sudoroom.org
>
> You can reach the person managing the list at
> mesh-owner(a)lists.sudoroom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mesh digest..."
>
>
> Today's Topics:
>
> 1. Re: mail and web operational (charles(a)thefnf.org)
> 2. Re: mail and web operational (charles(a)thefnf.org)
> 3. Re: Open Garden white paper! (The Doctor)
> 4. Re: mail and web operational (rhodey)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 25 Sep 2013 08:17:07 -0500
> From: charles(a)thefnf.org
> To: Mitar <mitar(a)tnode.com>,Jenny Ryan <tunabananas(a)gmail.com>
> Cc: Marc Juul <juul(a)labitat.dk>, mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] mail and web operational
> Message-ID: <75d8a78d-8425-4c0e-9959-d7b66de6be51(a)email.android.com>
> Content-Type: text/plain; charset=UTF-8
>
> Mitar <mitar(a)tnode.com> wrote:
> >Hi!
> >
> >So, maybe you should talk with people behind the freifunk.net site and
> >see what is their vision is? Probably they are just around the corner.
> >:-)
> >
> >As I said, there could be two domain names pointing to the same page,
> >meshthepla.net having different theme and different (English) locale.
> >
> >
> >Mitar
> >
> >> Mitar and all,
> >>
> >> The idea with meshthepla.net is to create a campaign site that is
> >agnostic
> >> toward any particular network. Freifunk.net by and large points to
> >and
> >> promotes itself, which is really all the argument needed.
> >>
> >> Also, I'm intending to use the site for documenting the workshop I'll
> >be
> >> leading at the wireless summit, one output of which is a global
> >community
> >> asset map of free networks and a communications framework for
> >continuing
> >> the conversation. :)
> >>
> >> I do like the Freifunk site a lot and am hoping I can grok more of it
> >after
> >> spending a few weeks immersed in German!
> >> On Sep 25, 2013 6:53 AM, "Mitar" <mitar(a)tnode.com> wrote:
> >>
> >>> Hi!
> >>>
> >>>> As far as global directories, I don't see any reason for freifunk
> >to be
> >>> the
> >>>> only front end for all this open data - in part because "freifunk"
> >is a
> >>>> much better name for german speakers than for everyone else. As
> >long as
> >>> we
> >>>> are dealing with open data and open source, it shouldn't be a
> >problem for
> >>>> motivated folks to throw up their own translated/localized version,
> >>>> experiment with visualizations, etc. if they want to
> >>>
> >>> Yes. So providing your own interface to the same API is probably
> >>> reasonable. But I got a feeling that Marc was arguing for doing some
> >>> other API and another directory?
> >>>
> >>> Of course another idea could be that we just translate freifunk.net
> >>> webpage, point meshtheplanet.net to that site and make so that when
> >it
> >>> is visited through meshtheplanet.net, an English version (with
> >whatever
> >>> logo) appears. And if we want some additional feature, we extend
> >current
> >>> website with it and both freifunk.net and meshtheplanet.net then
> >have
> >>> it. This is open source as well. Don't fork if not necessary. Have
> >you
> >>> tried to contribute to freifunk.net? Was it proven to be impossible?
> >>> That they didn't accept your contributions with your translations
> >and
> >>> visualizations? If not, why fork?
> >>>
> >>>
> >>> Mitar
> >>>
> >>>>
> >>>> --mark B.
> >>>> On Sep 24, 2013 6:47 PM, "Mitar" <mitar(a)tnode.com> wrote:
> >>>>
> >>>>> Hi!
> >>>>>
> >>>>>> That site is completely freifunk-specific.
> >>>>>
> >>>>> Because it is starting from there.
> >>>>>
> >>>>> I am probably biased though. :-) But in the past they had already
> >a nice
> >>>>> planet (blog aggregator) and I know few networks (including wlan
> >>>>> slovenija) who were part of that. So I don't have a feeling it is
> >just
> >>>>> freifunk specific.
> >>>>>
> >>>>>> Site appears to be in german only.
> >>>>>
> >>>>> Currently. This is called international diversity. :-)
> >>>>>
> >>>>>> No easy way to add your own community to the mesh (need to use an
> >>>>>> api).
> >>>>>
> >>>>> Pull request against:
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
> https://github.com/freifunk/api.freifunk.net/blob/master/directory/director…
> >>>>>
> >>>>> What is easier?
> >>>>>
> >>>>>> No info on the different meshes except for a link.
> >>>>>
> >>>>> Have you checked the schema?
> >>>>>
> >>>>>
> >https://github.com/freifunk/api.freifunk.net/blob/master/specs/0.1.json
> >>>>>
> >>>>> And of course, schema can be worked on by communities.
> >>>>>
> >>>>>> This does not even seem to be an attempt at a global community
> >site.
> >>>>>
> >>>>> Interesting, I got a feeling that they are trying to be. They were
> >eager
> >>>>> to translate into English the GitHub README, once I told them that
> >this
> >>>>> would help others. :-)
> >>>>>
> >>>>>> Yeah, but maybe forking hackerspaces.org would be better.
> >>>>>
> >>>>> As you want. I am just saying that some people are already working
> >on
> >>>>> that and that it is really hard to maintain such lists. I know
> >because I
> >>>>> tried one:
> >>>>>
> >>>>> http://interop.wlan-si.net/
> >>>>>
> >>>>> There is then simply:
> >>>>>
> >>>>>
> >>>
> >
> https://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region
> >>>>>
> >>>>> Which was viewed by many as good enough.
> >>>>>
> >>>>> And now freifunk is trying to improve on situation. So making a
> >site
> >>>>> which uses the same API and same directory is probably reasonable.
> >But
> >>>>> doing one new directory is probably not. Because the question is
> >who
> >>>>> will maintain that directory.
> >>>>>
> >>>>>
> >>>>> Mitar
> >>>>>
> >>>>> --
> >>>>> http://mitar.tnode.com/
> >>>>> https://twitter.com/mitar_m
> >>>>> _______________________________________________
> >>>>> mesh mailing list
> >>>>> mesh(a)lists.sudoroom.org
> >>>>> http://lists.sudoroom.org/listinfo/mesh
> >>>>>
> >>>>
> >>>
> >>> --
> >>> http://mitar.tnode.com/
> >>> https://twitter.com/mitar_m
> >>> _______________________________________________
> >>> mesh mailing list
> >>> mesh(a)lists.sudoroom.org
> >>> http://lists.sudoroom.org/listinfo/mesh
> >>>
> >>
>
> I think Mitar is really on to something here and i tend to agree with his
> position. I think we have a great list of his points/position.
>
> Guifi.us has a very specific goal: take the wndw.net site and turn it
> into a simple process: plan, fund, procure, build. It will scrape from
> existing map sources for its map. The less to scrape from the better!
>
> Jenny/all,
>
> Do you have a spec/goals/motivations etc page up somewhere for
> meshthepla.net?
> --
> Charles Wyble
> (818) 280-7059 charles(a)knownelement.com
> CTO Free Network Foundation (thefnf.org)
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 25 Sep 2013 08:20:36 -0500
> From: charles(a)thefnf.org
> To: Jenny Ryan <tunabananas(a)gmail.com>
> Cc: Marc Juul <juul(a)labitat.dk>, mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] mail and web operational
> Message-ID: <33cd0fed-c796-4f49-9ff9-eda78202d056(a)email.android.com>
> Content-Type: text/plain; charset=UTF-8
>
> Jenny Ryan <tunabananas(a)gmail.com> wrote:
> >Charles,
> >
> >Can you link to a guifi.net page that demonstrates this global map?
> >Something in English, preferably. I'd love to know more about this
> >project
> >and its roadmap.
> >On Sep 25, 2013 3:55 AM, <charles(a)thefnf.org> wrote:
> >
> >> Marc Juul <juul(a)labitat.dk> wrote:
> >> >On Tue, Sep 24, 2013 at 12:20 AM, Marc Juul <juul(a)labitat.dk> wrote:
> >> >
> >> >> I've set up a $6 a month VPS (vpscheap.net) and configured mail
> >for
> >> >our
> >> >> domains peoplesopen.net and sudoroom.org (and all variations).
> >> >>
> >> >
> >> >I must have been pretty tired when I wrote this. I of course meant
> >> >sudomesh.org
> >> >
> >> >I'm also not sure that this has been officially announced on the
> >> >mailing
> >> >list, but our final naming decisions are in.
> >> >
> >> >The network is:
> >> >
> >> > Peoples Open Network
> >> > peoplesopen.net
> >> >
> >> >The SSID of the wifi/mesh is:
> >> >
> >> > peoplesopen.net
> >> >
> >> >The organization is:
> >> >
> >> > sudomesh.org
> >> >
> >> >and then we are thinking about using meshtheplanet.net (and
> >> >meshthepla.net)
> >> >as a campaign to get more people involved or a map of all community
> >> >networks (like hackerspaces.org)
> >> >
> >> >We decided to change the decision from last week and not use the
> >name
> >> >peopleswifi.org as the SSID so as not to have two different names
> >for
> >> >the
> >> >network.
> >>
> >> Would you be willing to work with the Free Network Foundation and our
> >> guifi.us effort for the mapping?
> >>
> >> Also look at guifi.net (they are working closely with global mesh
> >> networks to map everything).
> >> --
> >> Charles Wyble
> >> (818) 280-7059 charles(a)knownelement.com
> >> CTO Free Network Foundation (thefnf.org)
> >>
> >> _______________________________________________
> >> mesh mailing list
> >> mesh(a)lists.sudoroom.org
> >> http://lists.sudoroom.org/listinfo/mesh
> >>
>
> I would browse the site and also talk to Roje/Pau at the summit. They know
> the site far better than I.
>
> Guifi.us is a 2.0 version of that site/concept and also more US centric.
> --
> Charles Wyble
> (818) 280-7059 charles(a)knownelement.com
> CTO Free Network Foundation (thefnf.org)
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 25 Sep 2013 11:42:40 -0400
> From: The Doctor <drwho(a)virtadpt.net>
> To: mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] Open Garden white paper!
> Message-ID: <52430470.6020105(a)virtadpt.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/24/2013 06:33 PM, Marc Juul wrote:
>
> > I would also guess that bluetooth still consumes significantly
> > less power than wifi even if wifi is set to lower power, but I
> > don't actually know.
>
> http://www.diffen.com/difference/Bluetooth_vs_Wifi
>
> tl;dr - Bluetooth uses less power, but has significantly less range.
>
> - --
> The Doctor [412/724/301/703] [ZS]
> Developer, Project Byzantium: http://project-byzantium.org/
>
> PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
> WWW: https://drwho.virtadpt.net/
>
> "Allez cuisine!" --Chairman Kaga
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.20 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlJDBHAACgkQO9j/K4B7F8GLhgCgoUXSyDkV8EceTjw+6vpjDJ0z
> wkkAoPP8k/zUCUmXlgXZFN4Bouedih/n
> =600q
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 25 Sep 2013 08:43:07 -0700
> From: rhodey <rhodey(a)anhonesteffort.org>
> To: mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] mail and web operational
> Message-ID: <5243048B.5020605(a)anhonesteffort.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Guifi.us looks great and is something I would support us at least trying.
>
> On a general note I'm highly skeptical of any database built on top of
> JSON. My hope is for an API to be built for this dataset such that
> individual mesh networks are not forced into using this one size fits
> all biz.
>
> -- rhodey
>
> On 09/25/2013 06:20 AM, charles(a)thefnf.org wrote:
> > Jenny Ryan <tunabananas(a)gmail.com> wrote:
> >> Charles,
> >>
> >> Can you link to a guifi.net page that demonstrates this global map?
> >> Something in English, preferably. I'd love to know more about this
> >> project
> >> and its roadmap.
> >> On Sep 25, 2013 3:55 AM, <charles(a)thefnf.org> wrote:
> >>
> >>> Marc Juul <juul(a)labitat.dk> wrote:
> >>>> On Tue, Sep 24, 2013 at 12:20 AM, Marc Juul <juul(a)labitat.dk> wrote:
> >>>>
> >>>>> I've set up a $6 a month VPS (vpscheap.net) and configured mail
> >> for
> >>>> our
> >>>>> domains peoplesopen.net and sudoroom.org (and all variations).
> >>>>>
> >>>>
> >>>> I must have been pretty tired when I wrote this. I of course meant
> >>>> sudomesh.org
> >>>>
> >>>> I'm also not sure that this has been officially announced on the
> >>>> mailing
> >>>> list, but our final naming decisions are in.
> >>>>
> >>>> The network is:
> >>>>
> >>>> Peoples Open Network
> >>>> peoplesopen.net
> >>>>
> >>>> The SSID of the wifi/mesh is:
> >>>>
> >>>> peoplesopen.net
> >>>>
> >>>> The organization is:
> >>>>
> >>>> sudomesh.org
> >>>>
> >>>> and then we are thinking about using meshtheplanet.net (and
> >>>> meshthepla.net)
> >>>> as a campaign to get more people involved or a map of all community
> >>>> networks (like hackerspaces.org)
> >>>>
> >>>> We decided to change the decision from last week and not use the
> >> name
> >>>> peopleswifi.org as the SSID so as not to have two different names
> >> for
> >>>> the
> >>>> network.
> >>>
> >>> Would you be willing to work with the Free Network Foundation and our
> >>> guifi.us effort for the mapping?
> >>>
> >>> Also look at guifi.net (they are working closely with global mesh
> >>> networks to map everything).
> >>> --
> >>> Charles Wyble
> >>> (818) 280-7059 charles(a)knownelement.com
> >>> CTO Free Network Foundation (thefnf.org)
> >>>
> >>> _______________________________________________
> >>> mesh mailing list
> >>> mesh(a)lists.sudoroom.org
> >>> http://lists.sudoroom.org/listinfo/mesh
> >>>
> >
> > I would browse the site and also talk to Roje/Pau at the summit. They
> know the site far better than I.
> >
> > Guifi.us is a 2.0 version of that site/concept and also more US centric.
> >
>
>
>
> ------------------------------
>
> _______________________________________________
> mesh mailing list
> mesh(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/mesh
>
>
> End of mesh Digest, Vol 8, Issue 21
> ***********************************
>
Hey all,
Last night I finished our current budget based on the income we received
through the crowdfunding campaign and our expenditures thus far. You can
view it here:
https://docs.google.com/spreadsheet/ccc?key=0Ao_Q7DQvNFT-dGE0a3hSRnVlck1xVH…
Currently, the funds exist in my and Marc's joint bank account. Once we
incorporate and begin the non-profit process, we'll open a bank account in
the name of the organization.
Websites should all be up by the end of the weekend; ping me if you'd like
an account to work on the sites with your preferred username (they're
Wordpress installs).
Mesh the planet!
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
Hi all!
We've had some great hack nights these past three weeks, and I apologize
for not posting notes regularly. I'll put these up on the wiki later
tonight.
------
*September 19 Hacknight*
Attendees: Juul, Steve (playing w/ SDR for radio astronomy), Luis (frontend
web interfaces), Chris (building an exit node), Deekoo (secure messaging
client), Max (admin page for nodes, tinkering with OpenWRT), Rhodey (script
to automate regeneration of SSH host keys), Jenny (501c3 & grantfunding
stuff, working on documentation presentation), Sam, Paige (working on
outreach & flyer/logo design)
=Network name / SSID=
PeoplesOpen.net
WiFi ssid - peopleswifi.org? peoplesopen.net?
---> peoplesopen.net
=Decide organization name=
*SudoMesh++++
*FreedomUptime+
*510pen
=Activities=
*Refine stickers
*Admin interface
*SSH key generation
*Firmware generation
*Websites
*Network diagram
*Documentation fair poster
=Notes=
*Paige and Chris suggested donating CPU to projects such as SETI, or number
crunching of DNA,
*September 12 Hacknight*
Attendees: Juul, Steve, Max, Chris, Jenny, Patrick
More thoughts on names:
- *PeoplesWifi.org --> SSID
- *People's Open Network
- *PONG? RooftopPONG?
Branding for People's Open Network
- *We now own peoplesopennetwork.com, peoplesopennetwork.org,
peoplesopennetwork.net and peoplesopen.net
- *Confirmed on SSID: peopleswifi.org
- *we need stickers
What we're working on now:
- *We have two working nodes at current, running through a Linode we can
share access to for anyone who wants to experiment.
- *Fake captive portals on the exit nodes to welcome users to the mesh.
- *If disconnected from the Internet, can connect to the unique address
of different nodes
>From GuiFi:
- *Layer 2 doesn't scale beyond some limited number of nodes
- *Running BMX6 to connect between the nodes
-
Low Bandwidth Mesh:
- *Using BeagleBones as receivers
- *Building transmitters
- *Meant to be used in emergency situations
- *Could transfer the app between Android phones using Bluetooth:
http://www.guidingtech.com/10346/transfer-android-apps-between-phones-bluet…
- *HackRF
*September 4th Hacknight*
Attendees: Michaela, Isaac, Jenny, roger, pau, mitar,
What we've been working on:
*Presentation on Saturday was rad! We now have video documentation.
*Marc has been working on:
- *Autogeneration of firmware / kit to be finished up in ~ a month
- *Fake captive portal by capturing inspection traffic
*Pau from Guifi.net - working on the qmp firmware - clouds of about 50
nodes working on this system. Beginning to collaborate with Argentina and
Italy on a new firmware project: LibreMesh - Using batman-adv, bu
http://www.guidingtech.com/10346/transfer-android-apps-between-phones-bluet…<http://www.guidingtech.com/10346/transfer-android-apps-between-phones-bluet…>
t<http://www.guidingtech.com/10346/transfer-android-apps-between-phones-bluet…>Layer
2 has problems with scalability, 30-40 nodes hit peak congestion
through conflicting ARP requests. So they're using BMX6 (Layer 3) protocol
to make connections between Layer 2. They discover Layer 2 clouds and join
them. Layer 2 (batman-adv) still helpful to create continuity between nodes.
*Shadhi working on an OpenBTS network in Papua, isolated community -
100,000 txt messages sent since February. Using hardware from range
networks. Base station cost ~$4-5k. Cost is the biggest problem.
*Isaac from Kansas City - their community network is used daily by a
few thousand people. Adapted qmp firmware to the Kansas City network. Has
been playing with GNU MediaGoblin. Thinking about how to do diverse
authentication. WOrking on a Network Commons license.
*Mikaela interested in sharng tokens for access to the mesh
*Nader working on building a network among the UC Berkeley co-ops
*Miguel working on firmware
*Mitar built slovenia network on top of an abundance of fiber
- *Nodewatcher
Funding:
*
http://www.internetsociety.org/what-we-do/grants-awards/community-grants
* OpenTechFund
* Need to procure outdoor UV-resistant cable, colocation for the VPN
exit node
Legal Issues / Network Commons License
- * Ownership of the actual nodes to be retained by the people themselves
- * Enforceable agreement that gives the community the right to
disconnect a problematic node
- * Industries want security on their investments (Guifi input)
- * Part 97 of FCC Rules - License by rule, any purpose that's
industrial scientific or medical - 2.4 & 5.8 GHz
- * Creative Commons, pros and cons:
*Pros: Umbrella definition of a spectrum of licrnses that share some basic
principles; easier to change
*Cons: Assumption that basic Creative Commons license is enough, when it
really implies a wide spectrum; keeping it simple allows room for growth
*How to interconnect a free network with a proprietary network?
- *Guifi.net: Internet access as a service - all services must be
allowed (net neutrality) - businesses make the network sustainable, so we
need to accomodate them, too.
- *Organization that maintains and educates around use of this license
- *Distinguishing between the Foundation and the Network(s)
- *Internal Versioning Number for the NCL (Network Commons License) is
at version 0.2
- *Goal is to share definitions
Breakout Groups
- *Present on federation
- * Do you know about this: https://github.com/freifunk/api.freifunk.net
- *Licensing: Marc, Isaac
- *Operational: Shadhi,
- *Firmware
- *Communications / Remote Participation for IS4CWN
- *Local DNS / Services:
-
Guifi.net Operational Structure
- *Open project - no membership fee or policies - you're a member if you
decide you are
- * Ownership of the network is distributed
- * License is also important
- * Tries to automize as much as possible, to avoid manual intervention
- * Use the tools available to solve problems, avoiding manual operation
- * Nodes have a physical location, and can become supernodes
- * Ad-hoc mode not really used. To propagate the network, you must have
at least two radios to receive and propagate - this model is sim[ply more
supported
- * No central point of authority - theoretically. Source code public
and open, anyone can also set up a network infrastructure
- * Technology-agnostic - strives to be as inclusive as possible
- * Tools to check on the statistics of the network
- * Use BGP (+ OSPF)
- * Have routing problems - every day, hour, minute! BGP not meant for
wifi
- * Funded by itself - those who want to join must pay the cost of
joining it, in charge of upgrading hardware, etc
- * Up to the people themselves to keep up with maintenance
- * Normally if a supernode goes down, it will be fixed within the next
48 hours
- * They have a fundraising option to request money from the network
- * Mostly run as a web of trust - mostly one degree of separation from
each other
- * Monopolistic mentality is internalized in Western culture -
- * When they first connected to the Internet, started receiving DDOS
attacks
- * Guifinet Foundation is the umbrella of many small ISPs in the
network, using GuifiNet Foundation to connect to the Internet
- * GuifiNet Foundation as an incubator for small businesses seeking to
become their own ISPs
- * Interested in cultivating a fair competition within the network
- * Separating organization (run by benevolent dictator) from network
(owned by community - can mutiny)
- * How to deal with legal issues : Refer to EU directives; Telecom
directives; referring to govs to get permission to deploy fiber - more
complicated because not a traditional ISP; need to keep IP logs - data
retention policy - what's the information content of that Ip address,
what's discoverable from there?
- * Who's the ISP, and how is that defined? Usually by size, or
commercial interest
Ideas thenceforth:
- *Give away nodes or sell them for $5 in exchange for attending workshop
- *The bigger you are, the more weird things you're going to face
- *CALEA: Comms Assistant for Law Enforcement Act -- local
requirements for logging and reporting via industry best practices
- **Could say we don't log NAT because the technical requirements are
too high
*wlan-slovenia vs guifi.net*
*People own the equipment
*Slovenia has a lot of fiber
*overabundance of connectivity led to desire to share the bandwidth
*What if someone takes my link? steals my data? makes a stupid thing on the
internet and i'm blamed?
*soution: vpn tunnels
*when a person donates a node, he hosts bandwidth - not IP
*Had to develop their own VPN, as the throughput was too slow
*300 vs 21,000 nodes - but slovenia is very small :)
*international link to austria and to croatia
*longest hop is 40km
How to get wider participation?
- *Reach out to networks we don't even know about yet
- *What are some networks we should definitely
- *Roger Proposal: Commons For Europe
- Code For Europe / Bottom-Up Broadband
- Org of Orgs - at the Euro level? nah - talked to some other
communities (eg Ninux, Freifunk [difficult as they are separated by city],
Funkfeur - toward creating an organization to federate amongst.
What sort of organiz
------
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
The earth image has been updated; Marc will be sending it along.
---------- Forwarded message ----------
From: nicolas weidinger <dr.weidinger(a)gmail.com>
Date: Fri, Aug 30, 2013 at 9:39 PM
Subject: Mesh The SVGs
To: Jenny Ryan <tunabananas(a)gmail.com>
for science!
Hey all!
A very late reminder that there will be a hack night for the mesh tonight
at Sudo Room starting at 7:30pm and going 'til we stop.
Come ready to work on something related to the project - we'll start with
brief updates on what we're working on, and check in toward the end to
ensure we've been good documentarians :)
I'll be working on the visual documentation for the upcoming Wireless
Summit, so designers / artsy sorts especially welcome!
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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
