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
David,
Garbage cans in front of electrical panels are an OSHA violation, the
front of that panel has to have about 4 feet of clear space. And about
1 foot on the side, someone correct me if I a wrong. Not to mention
water splashing.
All we need is a snitch within us to call on us, and we are in
trouble. So we have to be careful there.
The idea I presented is to bring it to Sudo and SudoMesh, so it can be
killed there and not waste OOC's meeting times.
Why not in Sudo?
I personally would love to have the Server Room in the Sudoroom. But,
it may incur into additional expenses (make windows, or install a AC
unit) to make the area less hot than what it currently is.
As you may know, in the Corporate world and Public places like the one
I work for, we keep the equipment between 65-72 degrees. Have you
checked how high is the temperature at the Sudoroom area?
Did you know that our storage server, when in our old sudoroom
location, crashed and a drive went down very likely because the high
temperature of that closet?
If we want to have a decent server room that will server Sudo+OOC, we
need to think accordingly and decide.
And not, we cannot just be moving the server room from one place to
another, we need to run cables from that location to the whole
building no? Long term location would be ideal, wherever we chose it
to be.
Anyhow, if a shitty physical network is okay with everyone, then I am
wasting my time. That kind of server room can go anywhere.
Matt, Luis, and I did two walks. We discussed some of those areas that
you mentioned and also checked a place that Yar suggested.
But some didn't qualify because the are right under the restrooms, so
potential water leakage right on top of the equipment is a high risk
to take. Also, at least the one that Yar suggested, the rack in mind
doesn't fit, the ceiling is too low.
And by the way, I almost gave up yesterday; ideas are not written in
stone; besides being ideas consensus is used, at least in the
Sudo/Sudo-Mesh world.
And remember, OOC is the one that would decide at the very end, not
Sudo/SudoMesh.
Daniel
On 7/7/14, 4:01 PM, Matthew Senate wrote:
> Don't micro-manage creativity. Be pleased that folks want to solve
> communal (omni-wide) problems right now; this will not always be
> true. Assume good faith.
>
> This being said, arguments exist on all sides. To me the questions
> are:
>
> What are the problems? Need a place to put network utilities very
> soon. What are the constraints? Only certain kinds of places work
> for network devices, without intractable costs. What are the
> opportunities? Two branches (a) places that are convenient and
> already appropriate for setting up network devices (fast, easy)
> and (b) places that allow for integrating network devices into the
> heating/cooling systems (potential energy/cost-savings, require
> coordination, approval, and implementation with potential extra
> costs). What are the priorities? To me: speed, simplicity.
>
> In my opinion, we should put devices in the simplest place as soon
> as possible and move on to the many other, more complex problems.
>
> // Matt
>
>
> On Mon, Jul 7, 2014 at 3:08 PM, David Keenan <dkeenan44(a)gmail.com
> <mailto:dkeenan44@gmail.com>> wrote:
>
> (Also I am thinking, low-power solar fans for mellow airflow into
> the basement venting, like the kind had on boats, would be cool.)
>
>
> On Mon, Jul 7, 2014 at 3:06 PM, David Keenan <dkeenan44(a)gmail.com
> <mailto:dkeenan44@gmail.com>> wrote:
>
> Also, re: ventilation in the basement - we have to recconnect the
> blower from the room (the 1'x3' venting) on the east side asap. On
> the west side, there is active cooling on the west side already (2x
> fans, plus windows above the sidewalk. There is also a large
> lightwell above the barr-room bathroom that could probably be
> easily gotten to. So, re: cool air (without a/c) to the servers if
> they are in the basement, we could pull cool air from the street or
> roof to the cold side of the rack, and vent heat from the hot
> side/top to the existing exhaust venting the furnaces use, or vent
> heat directlty to the basement in the winter, or vent perhaps to
> that lightwell... we can use thermostats in the room to trigger A/C
> from the compressor to the rack only if needed, and use ambient the
> rest of the time.
>
> In general, the ventilation setup in the basement - what needs to
> exhaust separately, what venting is shared and whence does it
> come/go - needs to be coordinated with the FNB, La Commune, Black
> Hole, and OOC. It's a logistical issue that Sudoers I think would
> be really good at help sorting out, and I would really love it if
> we could.
>
> As others have stated, we need a working group just for the
> basement and space there to hash out this stuff - plumbing is
> another equally pressing aspect. It's enough work and discussion I
> think it may be a good idea to set up its own email list perhaps on
> riseup or google, but I am open to suggestions about how best to
> comprise this.
>
> Love David
>
>
> On Mon, Jul 7, 2014 at 2:30 PM, David Keenan <dkeenan44(a)gmail.com
> <mailto:dkeenan44@gmail.com>> wrote:
>
> Hi all,
>
> Again I am /super/ psyched that we are tackling where to rack
> servers and very grateful to all who are putting energy and effort
> into this.
>
> Whether it be for servers or any other ideas about how to use
> others' space and shared space, I feel the only real missing piece
> in the discussion here, and actually to various degrees within
> pretty much /every/ member collective actually, is not keeping in
> mind any other group's plans or ideas for a given space in the
> building - especially for their very own space which they have
> already been promised are technically in possession of.
>
> /For sure/, by all means, lets brainstorm about every possible
> place things like servers could go. If we are imagining the rack
> should /not/ go into sudo/ccl's room (why not?), but rather
> elsewhere in the building, I think that's a conversation that
> should include others in the building too, not just sudoers,
> because it affects others' planning and use of space.
>
> The same I feel is true for anyone else's plans to do any
> build-out, and all buildout really should be discussed within the
> OOC as a whole. This doesn't have to be a nightmare of endless
> meetings - its simply a way to try to act in a coordinated and
> thoughtful manner in concert with other groups in the space.
>
> For example, in the hypothetical of Sudo putting a server rack into
> what is presently another group's dedicated space (Backspace), that
> particular conversation should be had with that _group_ from the
> get-go. For sure, hash out pros & cons on sudo-discuss, walk the
> building with other sudoers - yes! - but that discussion should not
> take place /only/ on sudo-discuss (or sudo-mesh), or /only/ with
> other sudoers (me and Andrew). Also, the Backspace area presently
> needs a lot of work - apparently, many people can only envision as
> a place for garbage, or to get to utility panels.
>
> Just because the Backspace area has not been fixed up yet, does not
> mean it won't soon be. Backspace area is at a real disadvantage
> here compared to nearly every other group, and I feel we all must
> be understanding of this, as Backspace clearly needs more work (and
> /time/ to do that) than pretty much anywhere else in the building.
> I mean, Backspace has far more intense permitting and structural
> issues to address - we're getting architectural drawings (I had the
> architect over yesterday partly for this reason), and planning it
> out thoughtfully - this is not going to happen in one week or even
> one month. Also, Backspacers are a much smaller, newer group than
> Sudo, in which almost everyone has day jobs and simply can't be
> there alla the time - they are not on sudo-discuss, nor necessarily
> should they be, at least any more than all of sudo should be on
> backspace's list.
>
> For those that don't know - Backspace Wellness Collective is a
> regularly-meeting group presently comprised of four healers /
> bodyworkers, in addition to Andrew and myself: Samantha,
> Margaretha, Athena, and Sarah. So, the notion of building Sudo
> stuff into Backspace needs to be discussed extensively with
> Backspace as a group. I see this model as applying to any group
> wanting to build out in another group's space.
>
> As you can imagine Backspace is having their own internal
> discussions about how articulate their model, including how best to
> build out, refinish, and make use of that physical area. Consider
> that if you blow away part of Backspace's area or an entire room
> for a different use, you are also potentially actually talking
> about removing an individual from Backspace, who would have used
> that room for their practice. I think it might be best to think
> about the pro's of putting servers into backspace in that way: Do
> you really feel that strongly about having servers there that you
> are willing to do ask that of another group? So you see what I mean
> here.
>
> Anyhow, to a less intensive extent that conversation should also be
> had with the Omni Oakland Commons as a whole (in the omnilogistics
> list), especially if you see the servers as serving the entire
> building, not just sudo (which would need to be explained to
> everyone else too - easily enough done, but the common use of these
> servers should be clarified.)
>
> Regarding server racks specifically and knowing sudo frankly I am
> somewhat doubtful that racks would be simply be left alone in a
> set-and-forget mode as much as has been inferred. Rather, I imagine
> sudo will actually need not-infrequent physical access.. to hack on
> things, install and upgrade new donated equipment, etc. Therefore
> they should be in a space where physical access is not an issue,
> and probably for permitting issues alone not infringe on the area
> for electrical panels. The electrical panel area should be closeted
> off no matter what and really never entered unless a breaker is
> flipped which, with 200A (or is it 240A?) of power and solid
> distribution throughout the building, and thoughtful planning re:
> circuit load, I see as being rare. Yes, a number of the circuits
> are powered off presently throughout the space - we will address
> that, and then the electrical closet should be rarely entered, if
> only for safety's sake if nothing else. My 2c.
>
> Best, David
>
>
>
> On Sun, Jul 6, 2014 at 6:51 PM, Luis Murillo
> <luis.murillo.plos(a)gmail.com <mailto:luis.murillo.plos@gmail.com>>
> wrote:
>
> Hey guys sorry I've been MIA today, been running some errands/TCB
> will swing by sudo later tonight and monday night :-)
>
>
> On Sun, Jul 6, 2014 at 6:08 PM, Somebody <somebody(a)riseup.net
> <mailto:somebody@riseup.net>> wrote:
>
>
> Excuse me for resending this email treat, but the Sudo-mesh list
> was not linked from the first email that I sent out.
>
> Thx!
>
>
>
> -------- Original Message -------- Subject: Re:
> [sudo-discuss] Server Room Status Date: Sun, 06 Jul 2014 17:12:03
> -0700 From: hol(a)gaskill.com <mailto:hol@gaskill.com> To:
> David Keenan <dkeenan44(a)gmail.com <mailto:dkeenan44@gmail.com>> CC:
> sudo-discuss(a)lists.sudoroom.org
> <mailto:sudo-discuss@lists.sudoroom.org>
>
>
>
>> the compressor for that could also provide cooling
> for the servers. i think doing experiments on heat recovery and
> regenerative hx are good for longterm - using a compressor and
> refrigerant to cool hot things may be less green than using fans
> and just circulating fresh cool air and letting convection do the
> work. if there's no objection, we could set up temp racks where
> daniel and others propose until we can run coax to a more optimal
> area. i finally have some time this week so i'll be around to
> assist with low-level tasks in support of setting up basic
> infrastructure
>
> cheers
>
>
>
>
>
>
>
> On 2014-07-06 10:00, David Keenan wrote:
>
>> hey guys,
>>
>>
>> I applaud the effort to find a good, secure server
> space! I definitely
>> wanna help.
>>
>> The main issue with using this particular room is,
> as you can see by
>> looking at the floorplan, the Backspace wellness
> collective is
>> already paying rent on that particular area (NW
> groundfloor
>> corner) and will be making their own changes to
> that space. Backspace
>> is myself, Andrew of course, Margaretha, Athena,
> and Sarah.
>>
>> The wellness collective needs quiet - thats partly
> an attraction for
>> that corner of the building - and, a cabinet full
> of fans plus almost
>> certainly AC for the cabinet, is loud. Also, it
> takes up Backspace,
>> and to be honest, i have hard time inamagining
> Sudo wont need to get
>> into it alla the time, so it seems nonideal to me.
>>
>> In general I would think, before using other
> essentially non-shared
>> areas of the building for Sudo's servers, we would
> have to
>> actually rule out why building the room in other
> locations, like Sudo
>> room, wouldnt work, and why we think actually that
> particular location
>> in someone else's area is really the only place it
> could work.
>>
>> Regardless of Bsckspace, having racked & stacked
> for going on 20 years
>> that would not be my first location in the entire
> building for a lot
>> of reasons.
>>
>> Also, a server cabinet / closet does not need to
> be near the main
>> electrical panel. Nor does it does not need to be
> near the street.
>>
>> We could find a room in the basement. There is
> excellent ventilation
>> to the basement, that just needs a small fix. Also
> the furnaces are in
>> the basement, and heat from the servers could tap
> into that venting to
>> actually help heat the building, which could save
> on energy. Also,
>> there is a plan to build a walk-in in the basement
> - the compressor
>> for that could also provide cooling for the servers.
>>
>> In other words, in my view, we should attempt a
> green solution that
>> ties the serbers into the infrastructure for the
> building.
>>
>> :) d
>>
>> On Saturday, July 5, 2014, Somebody
> <somebody(a)riseup.net <mailto:somebody@riseup.net>> wrote:
>>
>> === SERVER ROOM UPDATES === 2014/07/05: Today Luis, Matt, and I
>> did the walk in the
> building, and so far the
>> only place that seems the most appropriate to have the server
>> room is the
> room by the bar.
>>
>> This area is the most ideal in the whole building
> because the air
>> flow, temperature, electricity proximity, and also
> because it is where the
>> Internet access enters the building.
>>
>> Since this area is not is not part of the SudoRoom
> space, we will have
>> to talk about it with the rest of the Sudo-Mesh
> group and the group
>> approves it, then we would have to present the
> idea at our
>> Omni Collective meeting for approval.
>>
>> If approved by the Omni Collective, we would need
> to build:
>>
>> * A 2" or so high floor (two by fours and plywood
> would do, I believe.
>> * A 55" x 65" cage with chicken wire walls and a door.
>>
>> If this place is NOT approved by the OOC then
> perhaps we should
>> consider building the Server Room in the SudoRoom Space.
> High temperature and
>> noise levels are the main issues.
>>
>> If others have ideas/comments/or want to be part
> of this process
>> please jump in. You may contact Matt, Luis, or myself
> (Daniel).
>>
>> This update and all other Network/Reboot project
> is found at:
>>
> https://sudoroom.org/mediawiki/index.php?title=Network/Reboot
>>
>>
>> This update and all other Network/Reboot project
> is found at:
>> https://sudoroom.org/wiki/Network/Reboot
>>
>> Thx!
>>
>> _______________________________________________ sudo-discuss
>> mailing list sudo-discuss(a)lists.sudoroom.org
> <mailto:sudo-discuss@lists.sudoroom.org>
>> https://lists.sudoroom.org/listinfo/sudo-discuss
>>
>>
>> _______________________________________________ sudo-discuss
>> mailing list sudo-discuss(a)lists.sudoroom.org
> <mailto:sudo-discuss@lists.sudoroom.org>
> <mailto:sudo-discuss@lists.sudoroom.org
> <mailto:sudo-discuss@lists.sudoroom.org>>
>> https://lists.sudoroom.org/listinfo/sudo-discuss
>
>
> _______________________________________________ mesh mailing list
> mesh(a)lists.sudoroom.org <mailto:mesh@lists.sudoroom.org>
> https://lists.sudoroom.org/listinfo/mesh
>
>
>
> _______________________________________________ mesh mailing list
> mesh(a)lists.sudoroom.org <mailto:mesh@lists.sudoroom.org>
> https://lists.sudoroom.org/listinfo/mesh
>
>
>
>
>
> _______________________________________________ sudo-discuss
> mailing list sudo-discuss(a)lists.sudoroom.org
> <mailto:sudo-discuss@lists.sudoroom.org>
> https://lists.sudoroom.org/listinfo/sudo-discuss
>
>
>
>
> _______________________________________________ sudo-discuss
> mailing list sudo-discuss(a)lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/sudo-discuss
>
Excuse me for resending this email treat, but the Sudo-mesh list was not
linked from the first email that I sent out.
Thx!
-------- Original Message --------
Subject: Re: [sudo-discuss] Server Room Status
Date: Sun, 06 Jul 2014 17:12:03 -0700
From: hol(a)gaskill.com
To: David Keenan <dkeenan44(a)gmail.com>
CC: sudo-discuss(a)lists.sudoroom.org
>the compressor for that could also provide cooling for the servers.
i think doing experiments on heat recovery and regenerative hx are good
for longterm - using a compressor and refrigerant to cool hot things may
be less green than using fans and just circulating fresh cool air and
letting convection do the work. if there's no objection, we could set
up temp racks where daniel and others propose until we can run coax to a
more optimal area. i finally have some time this week so i'll be around
to assist with low-level tasks in support of setting up basic infrastructure
cheers
On 2014-07-06 10:00, David Keenan wrote:
> hey guys,
>
>
> I applaud the effort to find a good, secure server space! I definitely
> wanna help.
>
> The main issue with using this particular room is, as you can see by
> looking at the floorplan, the Backspace wellness collective is
> already paying rent on that particular area (NW groundfloor
> corner) and will be making their own changes to that space. Backspace
> is myself, Andrew of course, Margaretha, Athena, and Sarah.
>
> The wellness collective needs quiet - thats partly an attraction for
> that corner of the building - and, a cabinet full of fans plus almost
> certainly AC for the cabinet, is loud. Also, it takes up Backspace,
> and to be honest, i have hard time inamagining Sudo wont need to get
> into it alla the time, so it seems nonideal to me.
>
> In general I would think, before using other essentially non-shared
> areas of the building for Sudo's servers, we would have to
> actually rule out why building the room in other locations, like Sudo
> room, wouldnt work, and why we think actually that particular location
> in someone else's area is really the only place it could work.
>
> Regardless of Bsckspace, having racked & stacked for going on 20 years
> that would not be my first location in the entire building for a lot
> of reasons.
>
> Also, a server cabinet / closet does not need to be near the main
> electrical panel. Nor does it does not need to be near the street.
>
> We could find a room in the basement. There is excellent ventilation
> to the basement, that just needs a small fix. Also the furnaces are in
> the basement, and heat from the servers could tap into that venting to
> actually help heat the building, which could save on energy. Also,
> there is a plan to build a walk-in in the basement - the compressor
> for that could also provide cooling for the servers.
>
> In other words, in my view, we should attempt a green solution that
> ties the serbers into the infrastructure for the building.
>
> :)
> d
>
> On Saturday, July 5, 2014, Somebody <somebody(a)riseup.net> wrote:
>
> === SERVER ROOM UPDATES ===
> 2014/07/05:
> Today Luis, Matt, and I did the walk in the building, and so far the
> only place that seems the
> most appropriate to have the server room is the room by the bar.
>
> This area is the most ideal in the whole building because the air
> flow,
> temperature, electricity proximity, and also because it is where the
> Internet access enters the building.
>
> Since this area is not is not part of the SudoRoom space, we will have
> to talk about it with the rest of the Sudo-Mesh group and the group
> approves it, then we would have to present the idea at our
> Omni Collective meeting for approval.
>
> If approved by the Omni Collective, we would need to build:
>
> * A 2" or so high floor (two by fours and plywood would do, I believe.
> * A 55" x 65" cage with chicken wire walls and a door.
>
> If this place is NOT approved by the OOC then perhaps we should
> consider
> building the Server Room in the SudoRoom Space. High temperature and
> noise levels are the main issues.
>
> If others have ideas/comments/or want to be part of this process
> please
> jump in. You may contact Matt, Luis, or myself (Daniel).
>
> This update and all other Network/Reboot project is found at:
> https://sudoroom.org/mediawiki/index.php?title=Network/Reboot
>
>
> This update and all other Network/Reboot project is found at:
> https://sudoroom.org/wiki/Network/Reboot
>
> Thx!
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/sudo-discuss
>
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org <mailto:sudo-discuss@lists.sudoroom.org>
> https://lists.sudoroom.org/listinfo/sudo-discuss
exit1.sudomesh.org is not working!
It crashed and after rebooting it is listing all of the connected
tunneldigger clients, but batctl o says "No batman nodes in range ..."
Anyone change any config on this server?
I haven't been able to find anything wrong. Someone else want to take a
stab at it? Or maybe we should blast it and re-install.
Thanks to Pete Forsyth for alerting us!
--
marc/juul
:)
Max B <maxb.personal(a)gmail.com> wrote:
>_______________________________________________
>mesh mailing list
>mesh(a)lists.sudoroom.org
>https://lists.sudoroom.org/listinfo/mesh
We will be having our hacknight at the NEW sudo room location 4799 Shattuck
Ave, Oakland, tonight at 7:30 pm!
We brought back a bunch of gear from Portland that Russel from Personal
Telco donated to sudo mesh! (weird and awesome stuff) We should play around
with it!
hack hack hack
I will bring beers, caffeinated herbal tea and high spirits!
--
marc/juul
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
Hi all,
I just wanted to say hello. I've been lurking on the Mesh list for a while
now, and I've always been excited by the work you all are doing, so it was
funny to read the recent chain about me. :)
I'm 100% not doing a "Oakland just Launched a New Mesh Project" article,
but rather featuring what you've done thus far, why it's important (to me
but most importantly to you all), maybe obstacles you are overcoming, and
what you hope it accomplishes.
I really believe mesh networks present a great opportunity to change the
web but few people understand them. I hope an article about the work you
all are doing might get mesh networks in general and your project
specifically more attention or involvement. Tech President I think is a
really good space for this.
Please don't hesitate to voicing concerns about the article here or to me
directly, I will try to be as responsive as possible :) I definitely would
love to speak with many of you and please feel free to email me personally.
I also would really like to photograph some hubs if possible.
If you all are meeting Thursday the 26th, I hope to make it there
thanks
//bv
--
Ben Valentine
benjaminvalentine.com
@bennnyv
765-277-1573
Hi all,
I got an inquiry from a reporter for thecivicbeat.com who wants to
interview me about my node. I told him I'd give him a ring tomorrow.
Any requests or suggestions about how I should approach it?
Pete
503-383-9454
[[User:Peteforsyth]]
node:phorzaith
either aligned in such a way as to have created a rip in the fabric of time
and spece...
or there's no significance to planets and you all are trying to avoid me...
I worked late, and came over to sudoroom but there doesn't seem to be any
meshing happening here... tonight.
Oh well.
--
Chris Jefferies
(510) 409-0003 - mobile
We met, about five of us, but we left somewhere between Mars and Venus. I mean... 10 to 11.
steve <sc_shepard(a)hotmail.com> wrote:
>_______________________________________________
>mesh mailing list
>mesh(a)lists.sudoroom.org
>https://lists.sudoroom.org/listinfo/mesh
