How about we host the first sudo mesh hackathon as the first sudo event at
The Omni?
July 5 - 6 (Sat - Sun)
Something like an idea of an agenda:
* Local Network App Development
* JavaScript Convergence
* Firmware Development
* System / Tools Development
* Other development
* Hardware projects
* Community Outreach
* Marketing materials
* Creativity / art / laughter / delight / fun
We could also host a follow-up after the summer on Sep 6 - 7 (Sat - Sun).
// Matt
Hey all,
Brief discussion of a potential spot to mount a node near 17th and
Franklin, mapped a bit of it sound, seems like there is line-of-sight to
Laney college tower:
Laney: 37*47'48.53" N 122*15'46.52" W
17th and Franklin: 37 48 20.86 N 122 16 06.12 W
I'm not against it. It could be appropriate to use a key or additional labels. However, I wasn't sure how to represent participants by skill, and their distribution, so this diagram is effectively agnostic to it at the moment. Maybe there's s simple way to add it in?
I used the purple circle shape in respect of the symbol for gender neutrality. I changed the colors of some faces to represent folks of various communities / geographies, and how they build up and intersect with the core group and may overlap with one another. I left the core purple because as far as I can tell it remains true that to get a network to critical mass, there needs to be at least one group building and promoting tools for the network, as well as engaging others to grow.
I'm not satisfied with the captions, so any improvements / changes welcome.
// Matt
----- Reply message -----
From: "Mitar" <mitar(a)tnode.com>
To: "Matthew Senate" <mattsenate(a)gmail.com>
Cc: <drwho(a)virtadpt.net>, "mesh" <mesh(a)lists.sudoroom.org>
Subject: [Mesh] Network Development Diagram
Date: Thu, Jun 26, 2014 08:10
Hi!
Do you think it would be interesting for community diagram to maybe
identify various types of community members needed ideally? Also to
suggest in a way that participants do not have to be necessary
technically skilled, but also everyone else can have a role and can help
as well?
I know that I spent a lot of time explaining to people from
non-technical backgrounds that we need them as well.
Mitar
> Hey all,
>
> Haven't caught up entirely on this thread, but looking forward to
> re-reading shortly.
>
> I felt compelled to finish the updates to see what ya'll think of my
> depiction of a simplified and abstract representation of the overall
> pattern of network development / growth, this time paralleled with the
> community development that propels the growth. (I may switch Right with
> Left also btw)
>
> See attached.
>
>
> // Matt
>
>
> On Wed, Jun 25, 2014 at 11:44 AM, Mitar <mitar(a)tnode.com> wrote:
>
>> Hi!
>>
>>> In the US, sharing one's bandwidth is considered risky at best,
>>> dangerous at worst. Getting DMCA'd because somebody ran a torrent
>>> over your connection, getting raided because a neighbor downloaded
>>> something illegal using your connection, getting your service cut off
>>> because they found out you were sharing it... Additionally, there is
>>> always some risk incurred in using a network that you don't know the
>>> provenance of.
>>
>> All these issues we addressed by using VPN tunnels from nodes to connect
>> all nodes first together into a common network, and then Internet access
>> is a network-wide service. Public IP of host's Internet connection is
>> not visible.
>>
>> As I said, we made things easy. People do not have to know how to
>> protect their sharing of Internet, we designed that once and then can
>> just use it (they can of course also hack further on it, but this is not
>> a requirement for you to participate), so that they can then easily
>> share Internet.
>>
>> I agree with you, if you leave things complicated, then people will want
>> to learn first technology to be able to protect themselves and
>> understand better the risks. But if you develop technology in a way that
>> the risks are low, then they do not feel anymore that is necessary and
>> they are still willing to participate.
>>
>>> Looking at it from a user's perspective, hopping onto someone's AP can
>>> be hazardous because you don't know if it's a boobytrap or not.
>>
>> That's clients issue. Not hosts issue (the person who would host an open
>> AP). We should educate clients as well, they should not trust any
>> network anyway.
>>
>> The question is how to make many hosts to participate. You are saying by
>> teaching them how technology works. I am saying by making technology so
>> easy and safe, that they do not have to learn that. (But are of course
>> very much encouraged to do it, if they want, but it should not be a
>> requirement.)
>>
>>> In our experience, people started using the black box when they
>>> understood that it was set up for them, and intended for them to use.
>>> When it's less unknown it's often seen as safer, and more likely to
>>> be used.
>>
>> That's why you put a sticker on the black box which says "use me" and
>> you put SSID into the air which says "use me".
>>
>>> Most of the contact we've gotten was from activists who were actively
>>> setting up meshes for that purpose. Emergencies, unrest, disaster
>>> preparation, things like that. Very few people for the second. About
>>> as many people for the third as the second.
>>
>> OK, emergencies, unrest, disaster preparation are definitely a very
>> different use cases than what we are trying to address primarily in
>> Slovenia. Probably you really want and need to understand technology
>> when you want to deploy it in such situations.
>>
>> But for home use, for casual browsing, I would argue that this might not
>> be necessary (but of course welcoming and empowering).
>>
>>
>> Mitar
>>
>> --
>> http://mitar.tnode.com/
>> https://twitter.com/mitar_m
>> _______________________________________________
>> mesh mailing list
>> mesh(a)lists.sudoroom.org
>> https://lists.sudoroom.org/listinfo/mesh
>>
>
--
http://mitar.tnode.com/https://twitter.com/mitar_m
Hey all,
Realized there was a missing third in the series of basic technical
diagrams that capture the essential elements of the network:
How does the network start and grow?
Attached is a first draft of this diagram, please send comments!
So we have the apace for that? *grin*
Matthew Senate <mattsenate(a)gmail.com> wrote:
>we could hold it in the sudo space (bocce ball court), so we'd be insulated from any other events ;)
>
>
>
>On Fri, Jun 20, 2014 at 12:17 AM, Somebody <somebody(a)riseup.net> wrote:
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>I believe there is another event already scheduled (or tentatively
>scheduled) for July 5th. -Poetry.
>
>
>
>
>
>On 6/20/14, 12:11 AM, Matthew Senate wrote:
>> How about we host the first sudo mesh hackathon as the first sudo
>> event at The Omni?
>>
>> July 5 - 6 (Sat - Sun)
>>
>> Something like an idea of an agenda:
>>
>> * Local Network App Development * JavaScript Convergence * Firmware
>> Development * System / Tools Development * Other development *
>> Hardware projects * Community Outreach * Marketing materials *
>> Creativity / art / laughter / delight / fun
>>
>> We could also host a follow-up after the summer on Sep 6 - 7 (Sat -
>> Sun).
>>
>> // Matt
>>
>>
>
>> _______________________________________________ mesh mailing list
>> mesh(a)lists.sudoroom.org https://lists.sudoroom.org/listinfo/mesh
>>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
>Comment: GPGTools - https://gpgtools.org
>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
>iQEcBAEBCgAGBQJTo+ADAAoJEK2jBhiHY3O6+18H/0fncPBrH/9hCXxuEvwGvVrh
>6yP1oDd4b8aqZibzjQHf4vRnyk6TmULBw5WedKaz5tUs1CEnxuIvuPPQxqd+mUQq
>TU6717L0OYn4yYszZWxgKprdCV8tr+rO8zgJs42mpO+/ln/hEtsW0gBwLrzmTCyB
>JiYZiF6riMmUlx+Kez9V5rHp1qNHJBHqkR8QOU6KQkqEuHQzYAhDXRg4iZDIDoaM
>V3tPeCuhXKDnUrNpp0GP+Ltp2+wKxyHhRqJ/adx3bSgy7UNfIlkVyNrY831q1pf7
>IqXZwf8DmgVLgh0rDu1Nph16m2ZTZ9vrZ/9jGL5A9vtd0LvG4ZBevr0rvT37M1I=
>=DMCH
>-----END PGP SIGNATURE-----
>_______________________________________________
>mesh mailing list
>mesh(a)lists.sudoroom.org
>https://lists.sudoroom.org/listinfo/mesh
>
>
Hey all,
Just wanted to ping that I'm excited for our meetup tomorrow, I plan to be
there, and hope to see ya'll there too.
Who's coming?!
I'd like to revive the discussion of having a Sudo Mesh hackathon in the
near future!
// Matt
