Listservants,
During this week's general meeting I started a conversation on using hand
signals during meetings as a way to rank speaker order and mark shifts
between the topic at hand (*sad trombone*) and the conversation's
meta-process. A number of you spoke up with a lot of great perspectives and
ideas. This email is intended to net in the lot of you interested in this
topic so we can create a concrete proposal for an upcoming general meeting.
Check out our beautiful wiki page <http://…
[View More]sudoroom.org/wiki/Hand_signals>,
and help refine the proposal!
VickykciV
[View Less]
Does any one have welding gloves? Eric?
Bring them in please so I can protect my paws. :)
Raymond Lai
Ice Cream Man
Atomic Ice Cream
Facebook.com/MotoAtomico
Proposal for discussion on list and at an upcoming meeting:
That Sudoroom endorse the Open Wireless Movement and join the Open Wireless
Movement coalition.
Noisebridge has already joined; you can find a list of endorsers at
https://openwireless.org/
Open Wireless Movement is a coalition organized by the Electronic Frontier
Foundation to build technologies that let users open their wireless
networks and educate people and businesses about open wireless.
After allowing for dicussion on the …
[View More]list, we can bring up this proposal as
an agenda item at a future meeting.
If you have any questions you can ask me or contact openwireless(a)eff.org
Thanks!
--mark B.
[View Less]
The below person emailed the info at sudoroom address, didn't receive a
response, and so contacted me via my phony Sudo Room "business" phone
number. This means three things:
1. Someone hasn't checked the info at sudoroom inbox in a while.
2. We will be having a very special visitor to the Brain Wave meetup
tonight.
3. MY GOOGLE PLACES HACK WORKED! WE NOW HAVE A LISTING! (Do a Google search
for Sudo Room. You will see a lovely listing on the right.) :D
---------- Forwarded message ----------
…
[View More]From: Rivkah Beth Medow <rivkahbeth(a)gmail.com>
Date: 2013/2/1
Subject: Fwd: Magnum photographer attending Brain Wave Meetup event Fri 2/1
To: vknoxsironi(a)gmail.com
Thanks!
Rivkah
Begin forwarded message:
*From: *Rivkah Beth Medow <rivkahbeth(a)gmail.com>
*Date: *January 31, 2013 9:43:07 AM PST
*To: *info(a)sudoroom.org
*Subject: **Magnum photographer attending Brain Wave Meetup event Fri 2/1*
Hi! What an amazing space it looks like you have!
I'm writing to let you know that Magnum
Photos<http://www.magnumphotos.com/C.aspx?VP3=CMS3&VF=MAGO31_2_VForm>
photographer Alessandra
Sanguinetti<http://www.magnumphotos.com/C.aspx?VP3=CMS3&VF=MAGO31_10_VForm&ERID=24KL53X…>
will attend the Brain Wave Meetup event this Friday, 2/1 (
http://www.braindjvj.net/) and make sure you are aware and comfortable with
her being there. She will work with her assistant, Sam Levine, and be
respectful to your other guests, shooting around anyone not wanting to be
photographed.
We are in direct contact with Masahiro Kahata, the event's organizer, and I
will cc you on my communications with him so we are all in open
communication.
Below I've also attached a brief description of the photo project. Please
don't hesitate to be in touch with any questions at all.
Many thanks!
Rivkah Beth Medow
++
Rivkah Beth Medow
rivkahbethmedow.com
[View Less]
> I'm wondering if any Sudoers have access to a dewar and/or liquid
nitrogen?
Probably can't make tonight happen, but let me know if you need it in the
future. I have access to a couple dewars and don't mind purchasing a bit of
ln2 from the gas supplier in Berkeley.
-rick
Dear Sudo folk.
At Friday Filosophy today at noon, we will have Borekas from Grand Bakery again - this time more potato ones for vegans and the vegan-curious.
All suggestions for topics will be considered. I propose we talk about the AutoAdmit online defamation case from several years back. See Citizen Media Law Project page for overview - http://www.citmedialaw.org/threats/autoadmit; the Justia page with the full legal docket - http://dockets.justia.com/docket/connecticut/ctdce/3:…
[View More]2007cv00909/78132/; and the original complaint at http://docs.justia.com/cases/federal/district-courts/connecticut/ctdce/3:20….
In brief summary, an anonymous bulletin board with informal law school related chatter had some anonymously posted horrible threads about fellow female law students, even for those of us not easily shocked. Three first-year Yale law students were particularly targeted, one of whom allegedly lost her summer job because her employers came across the posts on searches (the defamers had intentionally Google bombed the search results.) Two of these students brought a lawsuit against the website and anonymous individuals who had posted the stuff. The case was eventually settled out of court.
The third woman - Caitlin Hall, who happened to be a student of mine at the time - was deeply affected by the whole thing but chose not to join her classmates in the lawsuit. She wrote this provocative Op-Ed in the Univ. of Arizona newspaper where she was a journalist while in college called "Sex, Lies, and Broadband" (http://www.wildcat.arizona.edu/article/2008/05/sex_lies_and_broadband - May 21, 2008). Below is an excerpt from it. I don't presume to know what I would have done in her situation, but I do know that when people search for Caitlin and AutoAdmit now, this is what usually comes up first.
We can't stop malice on the Internet. Malice finds a way. We can try to shore up the banks of the ""real world"" with legal and digital sandbags, but online hate speech has the slow inevitability of a tsunami. When the avenues of publication and distribution are limitless, it becomes exceedingly difficult to control people's behavior (a concept our Constitution's framers not only accepted, but banked on).
Nor can we stop college students on the Internet.
Advisers invariably warn that the only way to keep unsavory information from bleeding into the professional world is to decline to put it on the Internet in the first place. To a college student, that solution has all the persuasive power of telling a high schooler the only surefire way to avoid pregnancy is to forego sex.
But even if we can't stop the lambs and we can't stop the wolves, we can still stop the slaughter. The best way to do that, counterintuitively, is to overwhelm the market with bad information by allowing online verbal abuse to run unchecked, so that all such speech becomes valueless, unreliable and irrelevant. That's the best solution in that it's the most efficient, because it enlists the boundless energy of the depraved in their own undoing. Moreover, it's the only way to bypass the question of how to keep employers from using social software to inform hiring decisions (the answer, by the way, is that we can't).
To state the obvious, for the first generation to be libeled on the Internet, this solution sucks. It's no treat overhearing a stranger say he read you ""fucked your way into Yale."" It's infinitely more unpleasant knowing your friends, parents and boss have all read the same thing. But that's the way it has to be, in the fatalistic sense that that's the way it's going to be. All we can control is how quickly it's over. And that, despite what some will say, is a real choice.
[View Less]
I'm wondering if any Sudoers have access to a dewar and/or liquid nitrogen?
Project is liquid nitrogen ice cream for First Friday (eek, today!)
Cheers,
Ray
When founder status has been abused to the point of revoking the decisions
of operators, behaving inappropriately with insulting symbols, and
intimidating one of our most awesomely proactive members (which Yardena
described most acutely and all of which I have been witness to), then it
would seem Founder status is indeed required to be held by someone the
community trusts.
Jenny
http://jennyryan.nethttp://thepyre.orghttp://thevirtualcampfire.orghttp://technomadic.tumblr.com
`~`~`~`~`~`~`~…
[View More]`~`~`~`~`~`~`~`~`~`~`~`
"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é
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
On Wed, Jan 30, 2013 at 3:47 PM, Mischa Spiegelmock
<thadwooster(a)gmail.com>wrote:
> Founder status is not required to "filter" the content of the channel
>
> On Jan 30, 2013, at 3:46 PM, Jae Kwon wrote:
>
> > Here's a proposal.
> >
> > Assume that #sudoroom on FreeNode should be officially operated by
> SudoRoom the collective. [assumption 1]
> > Assume that FreeNode will force the transfer of +F to whoever/whatever
> SudoRoom decides. [assumption 2]
> > Assume that SudoRoom agrees that the contents of #sudoroom should be
> filtered for the purpose of SafeSpace. [assumption 3]
> >
> > Then I suggest we:
> >
> > (0) test the assumptions first.
> > (a) vote on whether +F should be reassigned, and if so,
> > (b) vote to whom +F should go, where candidates are suggested -- real
> bot implementations included.
> >
> > On Jan 30, 2013, at 2:26 PM, hol(a)gaskill.com wrote:
> >
> >> bumping rachel's sentiment here. yardena's note here was the clearest
> explanation I've seen, as someone who doesn't really get on the IRC channel
> and who would like this information to get out prior to the meeting so as
> to reduce meeting time.
> >>
> >>
> >> Jan 30, 2013 01:15:46 PM, rachelyra(a)gmail.com wrote:
> >> i think this reply is dismissive and it makes me sadfaced.
> >>>
> >>> Yardena is talking about much deeper and more insidious, and
> potentially
> >>> divisive, issues than typos or spelling. If you think her concerns are
> >>> boring, then you could easily ignore them and stay silent without being
> >>> dismissive and rude.
> >>>
> >>> Yardena did an awesome job of facilitating meetings for 6 straight
> hours
> >>> last week... it seems to me like anyone who enjoyed that experience
> with
> >>> her might take a moment to give a damn about her concerns.
> >>>
> >>> Multiple folks have suggested it would be good to have a clear IRC
> >>> policy. That seems like a good next step. Maybe a wiki page, seeded
> >>> with Yardena 's suggestion here? I am not active on the channel so am
> >>> not sure if it makes sense for me to be too involved in that
> process...?
> >>>
> >>> R.
> >>>
> >>> On 1/30/2013 1:07 PM, Clarence Beeks wrote:
> >>>> Do you know why America is awesome? We have the time and privilege
> and
> >>>> resources to argue
> >>>> over replacing a "Y" with a "J".
> >>>>
> >>>> I can 't wait for the next comet.
> >>>>
> >>>> On Wed, Jan 30, 2013 at 12:54 PM, Yardena Cohen yardenack(a)gmail.com
> >>>> mailto:yardenack@gmail.com>> wrote:
> >>>>
> >>>>>> Apparently the Sudo folk with admin privileges to the #sudoroom
> >>>> IRC channel are jealously resistant to sharing control,
> >>>>
> >>>>> This is not the case. Jordana and Tunabananas have operator
> >>>> privileges and can perform any sort of moderation they desire. If
> >>>> you have an issue with the content of #sudoroom, creating a new
> >>>> channel will not solve that problem.
> >>>>
> >>>> I avoided replying to this right away, because I was too angry and
> >>>> creeped out over being called "Jordana." He did this once before in
> >>>> the IRC while at the same time talking about me with male pronouns
> >>>> (he/his) - he knows better, so I took this as targeted harassment,
> or
> >>>> at the very least disingenuous passive aggressive participation in
> the
> >>>> trolling games that have been going on lately. He 's apologized to
> me
> >>>> in private since then but I just want to register that joking about
> >>>> hackerspace wars can be fun, but actually gaslighting each other is
> >>>> NOT fun. It can be scary, intimidating, and seriously compromise the
> >>>> accessibility and diversity of our community.
> >>>>
> >>>> As to the substance, he 's absolutely right that we have op
> privileges,
> >>>> but this obscures a few things. For technical background, I
> encourage
> >>>> people to read about the difference between +F and +o. Your best
> guide
> >>>> will be logging onto freenode and typing: "/msg chanserv help flags"
> >>>> but more general guides are online:
> >>>>
> >>>> https://en.wikipedia.org/wiki/IRC#Modes
> >>>> https://freenode.net/using_the_network.shtml
> >>>>
> >>>> There 've been conflicts over how to run the channel. Namely:
> >>>>
> >>>> 1) The person with +F has used his privileges to override the
> >>>> decisions of those with only +o, at several times unquieting people
> >>>> we 've quieted. The contexts for these were admittedly
> controversial
> >>>> and fall on ideological fault lines over how to run an IRC channel
> in
> >>>> general, so I agree 100% with Andrew that a clear IRC policy is the
> >>>> way to go. For the record, this has been mostly about using
> oppressive
> >>>> slurs, and my position has been not to tolerate them very much. We
> >>>> happen to have in our community a person who makes it his life 's
> work
> >>>> to push peoples ' buttons with slurs, and happened to be doing
> that IN
> >>>> the IRC channel. He 'd also made a habit of typing anatomical
> words at
> >>>> random times. Form your own opinions. Again, the solution to this
> may
> >>>> be more about having a clear policy, than who enforces it.
> >>>>
> >>>> 2) The person with +F has acted in bad faith. He flooded the channel
> >>>> with ascii art of an ejaculating swastika and claimed it was an
> >>>> "accident", which would be a no-brainer kban in most any channel.
> When
> >>>> asked to share +F with other people, his response was to vandalize
> the
> >>>> Sudoroom wiki to say he is the "leader" (
> >>>> http://sudoroom.org/wiki/Community_Structure ). In the meantime, he
> >>>> shares +F with a friend of his who hadn 't been to Sudoroom since
> >>>> summer 2012 and didn 't even seem to know anybody 's name. They
> 'd also
> >>>> set the +S (successor) flag for a person who is emphatically NOT a
> >>>> Sudoroom member and has even publically criticized Sudoroom. This
> sent
> >>>> a clear message to the rest of us that we were dealing with people
> who
> >>>> saw us as a joke; didn 't respect our community; and that there was
> >>>> little we could do about it in the short term. That mistrust has
> >>>> colored all of the talk over IRC privileges since then, and has only
> >>>> escalated since these same people came to our 1/16 meeting and made
> it
> >>>> significantly longer (by complaining about the meeting being long!),
> >>>> and also filled our meeting agenda notes with things like "fuck",
> >>>> "poop" and "this is why you guys never hack anything".
> >>>>
> >>>> I 'm not bitter or anything, just trying to bring out some of the
> >>>> subtext here for those not following why things are happening the
> way
> >>>> they are.
> >>>>
> >>>> I think the best formulation for IRC rules that everyone can agree
> on
> >>>> would be something like: we want the IRC channel to accurately
> reflect
> >>>> the atmosphere at the physical sudoroom space. To me, that nicely
> >>>> encompasses all the many behavioral problems and general do 's and
> >>>> don 'ts. Honestly the room itself has rarely had the kind of
> problems
> >>>> the channel has, because people tend to be a lot more decent to each
> >>>> other face to face, and because it self-selects for people who care
> >>>> about the community.
> >>>> _______________________________________________
> >>>> sudo-discuss mailing list
> >>>> sudo-discuss(a)lists.sudoroom.org mailto:
> sudo-discuss(a)lists.sudoroom.org>
> >>>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> sudo-discuss mailing list
> >>>> sudo-discuss(a)lists.sudoroom.org
> >>>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>> _______________________________________________
> >>> sudo-discuss mailing list
> >>> sudo-discuss(a)lists.sudoroom.org
> >>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>>
> >> _______________________________________________
> >> sudo-discuss mailing list
> >> sudo-discuss(a)lists.sudoroom.org
> >> http://lists.sudoroom.org/listinfo/sudo-discuss
> >
> > _______________________________________________
> > sudo-discuss mailing list
> > sudo-discuss(a)lists.sudoroom.org
> > http://lists.sudoroom.org/listinfo/sudo-discuss
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>
[View Less]
Hi folks,
I still have a few gallons of some hefeweizen I brewed - not my finest but it gets the job done - and my buddy is repoing his kegs from me sunday morning. If anyone has a CO2 tank and a faucet, I will contribute the fuller of the 2 5-gal kegs to the art murmur event and help get it set up, but unfortunately will not be able to stay very late to drink it. Anyone have the equipment to activate this free beer opportunity?
Cheers,
Hol
Just wanted to advertise that I had it as an option.
I didn't write any direct control into the bot thus far. But the thing
about a bot is that the community could control it. It could, without
emotion, act on the IRC policies we program it to know.
-Wolfy
On Wed, Jan 30, 2013 at 1:44 PM, David Rorex <drorex(a)gmail.com> wrote:
> How is the bot any better than using the built in ChanServ features?
> And don't you end up with the same problem of deciding who gets to
> control …
[View More]the bot?
>
> On Wed, Jan 30, 2013 at 1:33 PM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> > I've also written an IRC bot in python. super basic that can ops people
> from
> > a list. It works with server messages directly too so i can write it to
> > perform any other actions that would be beneficial to our IRC channel and
> > policy.
> >
> > Just throwing that out there.
> >
> > -Wolfy
> >
> >
> > On Wed, Jan 30, 2013 at 1:20 PM, Matthew Senate <mattsenate(a)gmail.com>
> > wrote:
> >>
> >> OKAY, I've added some more to the conflict resolution item on our agenda
> >> tonight: https://pad.riseup.net/p/sudoroom
> >>
> >> // Matt
> >>
> >>
> >> On Wed, Jan 30, 2013 at 1:15 PM, rachel lyra hospodar
> >> <rachelyra(a)gmail.com> wrote:
> >>>
> >>> i think this reply is dismissive and it makes me sadfaced.
> >>>
> >>> Yardena is talking about much deeper and more insidious, and
> potentially
> >>> divisive, issues than typos or spelling. If you think her concerns are
> >>> boring, then you could easily ignore them and stay silent without being
> >>> dismissive and rude.
> >>>
> >>> Yardena did an awesome job of facilitating meetings for 6 straight
> hours
> >>> last week... it seems to me like anyone who enjoyed that experience
> with her
> >>> might take a moment to give a damn about her concerns.
> >>>
> >>> Multiple folks have suggested it would be good to have a clear IRC
> >>> policy. That seems like a good next step. Maybe a wiki page, seeded
> with
> >>> Yardena's suggestion here? I am not active on the channel so am not
> sure if
> >>> it makes sense for me to be too involved in that process...?
> >>>
> >>> R.
> >>>
> >>>
> >>> On 1/30/2013 1:07 PM, Clarence Beeks wrote:
> >>>>
> >>>> Do you know why America is awesome? We have the time and privilege
> and
> >>>> resources to argue
> >>>> over replacing a "Y" with a "J".
> >>>>
> >>>> I can't wait for the next comet.
> >>>>
> >>>> On Wed, Jan 30, 2013 at 12:54 PM, Yardena Cohen <yardenack(a)gmail.com
> >>>> <mailto:yardenack@gmail.com>> wrote:
> >>>>
> >>>> >> Apparently the Sudo folk with admin privileges to the
> #sudoroom
> >>>> IRC channel are jealously resistant to sharing control,
> >>>>
> >>>> > This is not the case. Jordana and Tunabananas have operator
> >>>> privileges and can perform any sort of moderation they desire. If
> >>>> you have an issue with the content of #sudoroom, creating a new
> >>>> channel will not solve that problem.
> >>>>
> >>>> I avoided replying to this right away, because I was too angry and
> >>>> creeped out over being called "Jordana." He did this once before
> in
> >>>> the IRC while at the same time talking about me with male pronouns
> >>>> (he/his) - he knows better, so I took this as targeted harassment,
> >>>> or
> >>>> at the very least disingenuous passive aggressive participation in
> >>>> the
> >>>> trolling games that have been going on lately. He's apologized to
> me
> >>>> in private since then but I just want to register that joking
> about
> >>>> hackerspace wars can be fun, but actually gaslighting each other
> is
> >>>> NOT fun. It can be scary, intimidating, and seriously compromise
> the
> >>>> accessibility and diversity of our community.
> >>>>
> >>>> As to the substance, he's absolutely right that we have op
> >>>> privileges,
> >>>> but this obscures a few things. For technical background, I
> >>>> encourage
> >>>> people to read about the difference between +F and +o. Your best
> >>>> guide
> >>>> will be logging onto freenode and typing: "/msg chanserv help
> flags"
> >>>> but more general guides are online:
> >>>>
> >>>> https://en.wikipedia.org/wiki/IRC#Modes
> >>>> https://freenode.net/using_the_network.shtml
> >>>>
> >>>> There've been conflicts over how to run the channel. Namely:
> >>>>
> >>>> 1) The person with +F has used his privileges to override the
> >>>> decisions of those with only +o, at several times unquieting
> people
> >>>> we've quieted. The contexts for these were admittedly
> controversial
> >>>> and fall on ideological fault lines over how to run an IRC channel
> >>>> in
> >>>> general, so I agree 100% with Andrew that a clear IRC policy is
> the
> >>>> way to go. For the record, this has been mostly about using
> >>>> oppressive
> >>>> slurs, and my position has been not to tolerate them very much. We
> >>>> happen to have in our community a person who makes it his life's
> >>>> work
> >>>> to push peoples' buttons with slurs, and happened to be doing that
> >>>> IN
> >>>> the IRC channel. He'd also made a habit of typing anatomical words
> >>>> at
> >>>> random times. Form your own opinions. Again, the solution to this
> >>>> may
> >>>> be more about having a clear policy, than who enforces it.
> >>>>
> >>>> 2) The person with +F has acted in bad faith. He flooded the
> channel
> >>>> with ascii art of an ejaculating swastika and claimed it was an
> >>>> "accident", which would be a no-brainer kban in most any channel.
> >>>> When
> >>>> asked to share +F with other people, his response was to vandalize
> >>>> the
> >>>> Sudoroom wiki to say he is the "leader" (
> >>>> http://sudoroom.org/wiki/Community_Structure ). In the meantime,
> he
> >>>> shares +F with a friend of his who hadn't been to Sudoroom since
> >>>> summer 2012 and didn't even seem to know anybody's name. They'd
> also
> >>>> set the +S (successor) flag for a person who is emphatically NOT a
> >>>> Sudoroom member and has even publically criticized Sudoroom. This
> >>>> sent
> >>>> a clear message to the rest of us that we were dealing with people
> >>>> who
> >>>> saw us as a joke; didn't respect our community; and that there was
> >>>> little we could do about it in the short term. That mistrust has
> >>>> colored all of the talk over IRC privileges since then, and has
> only
> >>>> escalated since these same people came to our 1/16 meeting and
> made
> >>>> it
> >>>> significantly longer (by complaining about the meeting being
> long!),
> >>>> and also filled our meeting agenda notes with things like "fuck",
> >>>> "poop" and "this is why you guys never hack anything".
> >>>>
> >>>> I'm not bitter or anything, just trying to bring out some of the
> >>>> subtext here for those not following why things are happening the
> >>>> way
> >>>> they are.
> >>>>
> >>>> I think the best formulation for IRC rules that everyone can agree
> >>>> on
> >>>> would be something like: we want the IRC channel to accurately
> >>>> reflect
> >>>> the atmosphere at the physical sudoroom space. To me, that nicely
> >>>> encompasses all the many behavioral problems and general do's and
> >>>> don'ts. Honestly the room itself has rarely had the kind of
> problems
> >>>> the channel has, because people tend to be a lot more decent to
> each
> >>>> other face to face, and because it self-selects for people who
> care
> >>>> about the community.
> >>>> _______________________________________________
> >>>> sudo-discuss mailing list
> >>>> sudo-discuss(a)lists.sudoroom.org
> >>>> <mailto:sudo-discuss@lists.sudoroom.org>
> >>>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> sudo-discuss mailing list
> >>>> sudo-discuss(a)lists.sudoroom.org
> >>>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>>
> >>> _______________________________________________
> >>> sudo-discuss mailing list
> >>> sudo-discuss(a)lists.sudoroom.org
> >>> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>
> >>
> >>
> >> _______________________________________________
> >> sudo-discuss mailing list
> >> sudo-discuss(a)lists.sudoroom.org
> >> http://lists.sudoroom.org/listinfo/sudo-discuss
> >>
> >
> >
> > _______________________________________________
> > sudo-discuss mailing list
> > sudo-discuss(a)lists.sudoroom.org
> > http://lists.sudoroom.org/listinfo/sudo-discuss
> >
>
[View Less]
>> Apparently the Sudo folk with admin privileges to the #sudoroom IRC channel are jealously resistant to sharing control,
> This is not the case. Jordana and Tunabananas have operator privileges and can perform any sort of moderation they desire. If you have an issue with the content of #sudoroom, creating a new channel will not solve that problem.
I avoided replying to this right away, because I was too angry and
creeped out over being called "Jordana." He did this once before in
…
[View More]the IRC while at the same time talking about me with male pronouns
(he/his) - he knows better, so I took this as targeted harassment, or
at the very least disingenuous passive aggressive participation in the
trolling games that have been going on lately. He's apologized to me
in private since then but I just want to register that joking about
hackerspace wars can be fun, but actually gaslighting each other is
NOT fun. It can be scary, intimidating, and seriously compromise the
accessibility and diversity of our community.
As to the substance, he's absolutely right that we have op privileges,
but this obscures a few things. For technical background, I encourage
people to read about the difference between +F and +o. Your best guide
will be logging onto freenode and typing: "/msg chanserv help flags"
but more general guides are online:
https://en.wikipedia.org/wiki/IRC#Modeshttps://freenode.net/using_the_network.shtml
There've been conflicts over how to run the channel. Namely:
1) The person with +F has used his privileges to override the
decisions of those with only +o, at several times unquieting people
we've quieted. The contexts for these were admittedly controversial
and fall on ideological fault lines over how to run an IRC channel in
general, so I agree 100% with Andrew that a clear IRC policy is the
way to go. For the record, this has been mostly about using oppressive
slurs, and my position has been not to tolerate them very much. We
happen to have in our community a person who makes it his life's work
to push peoples' buttons with slurs, and happened to be doing that IN
the IRC channel. He'd also made a habit of typing anatomical words at
random times. Form your own opinions. Again, the solution to this may
be more about having a clear policy, than who enforces it.
2) The person with +F has acted in bad faith. He flooded the channel
with ascii art of an ejaculating swastika and claimed it was an
"accident", which would be a no-brainer kban in most any channel. When
asked to share +F with other people, his response was to vandalize the
Sudoroom wiki to say he is the "leader" (
http://sudoroom.org/wiki/Community_Structure ). In the meantime, he
shares +F with a friend of his who hadn't been to Sudoroom since
summer 2012 and didn't even seem to know anybody's name. They'd also
set the +S (successor) flag for a person who is emphatically NOT a
Sudoroom member and has even publically criticized Sudoroom. This sent
a clear message to the rest of us that we were dealing with people who
saw us as a joke; didn't respect our community; and that there was
little we could do about it in the short term. That mistrust has
colored all of the talk over IRC privileges since then, and has only
escalated since these same people came to our 1/16 meeting and made it
significantly longer (by complaining about the meeting being long!),
and also filled our meeting agenda notes with things like "fuck",
"poop" and "this is why you guys never hack anything".
I'm not bitter or anything, just trying to bring out some of the
subtext here for those not following why things are happening the way
they are.
I think the best formulation for IRC rules that everyone can agree on
would be something like: we want the IRC channel to accurately reflect
the atmosphere at the physical sudoroom space. To me, that nicely
encompasses all the many behavioral problems and general do's and
don'ts. Honestly the room itself has rarely had the kind of problems
the channel has, because people tend to be a lot more decent to each
other face to face, and because it self-selects for people who care
about the community.
[View Less]
hey all,
as discussed at last week's meeting, we are hoping to have a sewing
hackathon on sunday, February 10th. we talked about 1-4pm, but I heard
LOLspace is having its anniversary party on that day around 3pm, so I am
wondering if people want to have our sewing party on a different day, or
earlier so we can head over to LOLspace too?
i am proposing 12-3pm instead! thoughts?
also, how does one become endowed with the powers to add events to the
calendar? or alternately, where does …
[View More]one submit events for the calendar?
all hail sudo!
R.
[View Less]
Oakland Art Murmur First Friday is this Friday, Feb. 1.
In order to facilitate planning and discussion for this and upcoming Art
Murmurs - a new Sudo Room listserv has been created. If you would like to
help out, are an artist that wants to display stuff, or are just interested
in keeping full track of what's going on, please subscribe at the link
below. Today.
http://lists.sudoroom.org/listinfo/artmurmur
We will keep the sudo-discuss listserv updated on major changes and
announcements, but …
[View More]will otherwise focus all displayed art related energy
and information on the Art Murmur listserv.
Sent from eddan.com
--
sent from Eddan.com
[View Less]
Hey folks,
I wanted to ask the list if there would be any issues with myself and a
couple of my friends using a wall in the common area to colab on visuals
stuffs tomorrow night?
I know there are some meetings happening tomorrow, but we would be
relatively quiet. We're just experimenting with how to best coordinate
visuals with a couple projectors and possibly test out some projection
mapping stuff which requires a bit more space than I have in my apartment.
I understand it could be visually …
[View More]distracting and I don't want to step on
any toes so please let me know if anyone feels this would be encroaching on
the meetings already in place.
Thoughts?
Thanks in advance,
Jack
[View Less]
SUDO announce to list -get excited,
sudo shroom is rapidly progressing. We're going to grow oyster and shiitake
mushrooms in sudoroom, to 1) get some delicious mushrooms, 2) master the
growing process, 3) in the future experiement with creating grow kits,
water treatment and more.
We're on the verge of bringing in the simple gear we need. We've got spores
and growing mediums ready. It's going to be an explosion awesome cultures!
Let us know if you want to join.
Our wiki home: http://sudoroom.…
[View More]org/wiki/Sudoshroom
Make a great day,
Morten
[View Less]
for those interested:
https://www.facebook.com/events/439926452746883/
Also we (the sound art meetup group) would love to do an event for art
murmur on april 5th, anyone into helping us? it would be performances from
the meetup.
hi friends, thought some of you may be interested. - marina
---------- Forwarded message ----------
From: Daniel Lombraña González <teleyinex(a)gmail.com>
Date: 2013/1/28
Subject: [open-science] Citizen Science Open Technical Workshop on Google+
Hangout
To: open-science <open-science(a)lists.okfn.org>, okfn-labs <
okfn-labs(a)lists.okfn.org>
Dear all,
It's our pleasure to invite you to join the* Citizen Science Open Technical
Workshop* to be held next *Wednesday 30th …
[View More]January 16:00 CET* virtually
using Google Hangout.
You can attend the meeting and send all your comments in this *Youtube
channel <http://www.youtube.com/channel/UCbkYEbbo8qMYbA3P5iLanGw> *or
this twitter
account <http://twitter.com/SOCIETIC_EU>.
During 2 hours we'll have expert's talks and open discussions
about technologies such as BOINC, Bossa, PyBossa, Furnivall, Ourgrid and
others, with the focus on developments, administration issues and use
cases.
Speakers are: David Anderson (Univ. Berkeley <http://www.ssl.berkeley.edu/>),
Daniel Lombraña (CCC <http://www.citizencyberscience.net/>), Francisco Sanz
(BIFI <http://bifi.es/>), Eduardo Lostal (Ibercivis<http://www.ibercivis.es/>),
Francisco Brasileiro (Univ. Fed. Campina Grande<http://www.lsd.ufcg.edu.br/>),
Candida Silva (Univ. Coimbra <http://www.uc.pt/fctuc/dquimica/rbritolab>),
Juanjo Molinero (software developer).
The workshop is co-organized by the Ibercivis Foundation and the Society as
Infrastructure for e-Science <http://www.societic-project.eu/>project
funded by the European Commission under FP7.
Looking forward to see you there!
--
··························································································································································
http://daniellombrana.eshttp://www.flickr.com/photos/teleyinex
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino PDF, HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
_______________________________________________
open-science mailing list
open-science(a)lists.okfn.org
http://lists.okfn.org/mailman/listinfo/open-science
Unsubscribe: http://lists.okfn.org/mailman/options/open-science
[View Less]
This is a notice that public archives have now been enabled for all
@lists.sudoroom.org mailing lists.
Previous messages have not been archived, but all messages will be
archived starting with this message.
--
Juul
Eddan: Here, let me help to make it easier. I've attached a City RFP
issued in 2006, the final report issued by the consultant and the final
staff report that resulted from four years of work on the city wide wi-fi
project. The stories I could tell you. Ultimately, the report found that
the City's fiber infrastructure was inadequate to implement such a project -
and the City Council didn't "get it" anyway.
The next story is about the public/private partnership (City, IP Network and
…
[View More]Cisco) that applied for a federal ARRA grant in 2010 to build a $35 million
fiber optic network throughout the City. Didn't get the grant. Then my
subsequent efforts to pick up the pieces (see attached Executive Summary and
powerpoint completed 2 weeks before I left in June 2011). No one has picked
up this project since I left.
See Mark - you just have to ask the right person!!! Call me if you have
questions.
Work wasn't wasted - San Leandro has hired me to become its first Chief
Innovation Officer to represent Lit San Leandro and create a tech business
development strategy in that City.
Debbie
Deborah V. Acosta
Principal, iDOTconnect
Co-Chair, 2.Oakland
Tel: (510) 508-7926
Email: <mailto:dacosta@iDOTconnect.net> dacosta(a)iDOTconnect.net
Web: <http://www.idotconnect.net/> www.iDOTconnect.net
Web: <http://www.twopointoakland.com> www.twopointoakland.com
Facebook: <https://www.facebook.com/TwoPointOak>
https://www.facebook.com/TwoPointOak
From: Eddan Katz [mailto:eddank@gmail.com] On Behalf Of Eddan Katz
Sent: Friday, January 25, 2013 11:57 AM
To: mark burdett
Cc: sudo-discuss(a)lists.sudoroom.org; Susan Mernit; Deborah Acosta
Subject: Re: [sudo-discuss] Freedom of Information requests
Mark -
I think it would be useful to bring in Susan Mernit & Deborah Acosta, both
of whom are on this list as far as I know, who were around for these
discussions at the time. Susan, of Oakland Local, has also had extensive and
successful experience with FOI requests with the City of Oakland.
sent from eddan.com
On Jan 24, 2013, at 6:51 PM, mark burdett <mark(a)510pen.org> wrote:
Hmm as would I :) We'll need to figure out which office(s) to send it to,
and what type of documents to request. Let me know if you have any ideas re:
how to phrase the request - I'll also talk to some lawyer folks.
--mark B.
On Thu, Jan 24, 2013 at 3:34 PM, Eddan Katz <eddan(a)eddan.com> wrote:
I would be interested in learning more about discussions within municipal
leadership about previous attempts to introduce Open WiFi to Oakland.
On Jan 21, 2013, at 12:06 PM, mark burdett <mark(a)510pen.org> wrote:
Hi, if anyone is interested in making a Freedom of Information request to a
local/state/federal government agency, I have some surplus credits on
https://www.muckrock.com/ - a website which makes it pretty easy to send and
track FOI requests online. Just email me off-list and I can submit a request
for you.
Maybe could be useful for Oakland Wiki or other projects folks are working
on?
Note, sometimes agencies refuse to send documents and you have to file a
lawsuit (but hey, you might win a million dollars 10 years later), or they
want to charge exorbitant fees for documents - e.g.
https://muckrock.s3.amazonaws.com/foia_files/Ltr_-_1-17-13.pdf - but
sometimes you can get what you're looking for free of charge..
--mark B.
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
[View Less]
I've lost track of what we're talking about, but I think we should all be equipped with Sudo Sporks (knife-spork) - the butcher, the baker, and the candle-stick maker especially.
If all three are in conflict with each other, by the way, it may curiously be less of a problem and rather the ideal scenario for cooperation. A team of rivals, with deliberate separation of powers, can sometimes be the best way to get through a delicate challenge, like with the 13th amendment for those who've seen …
[View More]Spielberg's Lincoln.
sent from eddan.com
On Jan 24, 2013, at 6:59 PM, Deno Vichas <deno(a)syncopated.net> wrote:
> spoons? but don't most of us fork?
>
>
>
> On 1/24/2013 6:23 PM, Anca Mosoiu wrote:
>>
>>
>> On Thu, Jan 24, 2013 at 6:21 PM, Deno Vichas <deno(a)syncopated.net> wrote:
>>>
>>> On 1/24/2013 6:13 PM, Anthony Di Franco wrote:
>>>> I think that, while the Constable should not actually do any mediation, just documentation and communication of what's documented, it makes sense to have someone else act as Constable in a case where the Constable is in the conflict. Defaulting perhaps to an uninvolved volunteer, then Scribe, then Facilitator.
>>> but what if the constable, the scribe, and the facilitator are in conflict with each other?
>>
>> They should duke it out using spoons, rubber chickens, and the world's dwindling supply of Hostess Twinkies.
>>
>> Anca.
>>
>>
>>
>> On Thu, Jan 24, 2013 at 6:21 PM, Deno Vichas <deno(a)syncopated.net> wrote:
>>>
>>> On 1/24/2013 6:13 PM, Anthony Di Franco wrote:
>>>> I think that, while the Constable should not actually do any mediation, just documentation and communication of what's documented, it makes sense to have someone else act as Constable in a case where the Constable is in the conflict. Defaulting perhaps to an uninvolved volunteer, then Scribe, then Facilitator.
>>> but what if the constable, the scribe, and the facilitator are in conflict with each other?
>>>
>>>
>>>
>>>
>>>> The Constable should be encouraged, but not required, to come from a race of shapeshifters, or one regarded as gods by another, or to possess either or both of those attributes by other means, and to be brusque of manner and exceptionally shrewd.
>>>>
>>>> On Jan 24, 2013 5:44 PM, "Yardena Cohen" <yardenack(a)gmail.com> wrote:
>>>>> I enthusiastically support a more formal and clearer and well
>>>>> constructed conflict resolution process, even though I'm not sure how
>>>>> I feel about the details yet, and thank you Andrew for the initial
>>>>> brain dump!
>>>>>
>>>>> I like the idea of a point-person for conflict resolution but worry
>>>>> about having just one, because what happens when someone has a
>>>>> conflict with them? For instance, I'd volunteer for mediation in some
>>>>> conflicts but I have had my own conflicts with people in the Sudoroom
>>>>> community so I don't know if I'd be eligible in all cases, nor would
>>>>> anybody.
>>>>>
>>>>> I do like the title "Constable" because it reminds me of Odo in Deep Space Nine.
>>>>> _______________________________________________
>>>>> sudo-discuss mailing list
>>>>> sudo-discuss(a)lists.sudoroom.org
>>>>> http://lists.sudoroom.org/listinfo/sudo-discuss
>>>>
>>>>
>>>> _______________________________________________
>>>> sudo-discuss mailing list
>>>> sudo-discuss(a)lists.sudoroom.org
>>>> http://lists.sudoroom.org/listinfo/sudo-discuss
>>>
>>>
>>> _______________________________________________
>>> sudo-discuss mailing list
>>> sudo-discuss(a)lists.sudoroom.org
>>> http://lists.sudoroom.org/listinfo/sudo-discuss
>>
>>
>>
>> --
>> -=-=-=-
>> Anca Mosoiu | Tech Liminal
>> anca(a)techliminal.com
>> M: (510) 220-6660
>> http://techliminal.com | T: @techliminal | F: facebook.com/techliminal
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
[View Less]
I agree in this particular case and in fact admit to unintentionally participating in stifling a straw poll because my comment was understood as an objection. I was merely trying to introduce a note of caution into asking who would be willing to pay for something and how much, given how some people could really be turned off by that kind of peer pressure, however well-meaning.
I do however hesitate to be absolute about it, or unconditional. Bad faith consensus blocking has been discussed at …
[View More]Sudo Room many times, and I would hope that the process we go with could not be exploited as such.
sent from eddan.com
On Jan 24, 2013, at 4:26 PM, Jehan Tremback <jehan.tremback(a)gmail.com> wrote:
> Yea, totally, straw polls should be friction free. This would have saved like 15-30 minutes of talking about nothing yesterday.
>
> -Jehan
>
>
> On Thu, Jan 24, 2013 at 4:19 PM, Andrew <andrew(a)roshambomedia.com> wrote:
> I totally agree.
>
> In addition, I think that there should be some rules around making official proposals, for example that there must reasonable time to bring up clarifying questions and to make comments before bringing it to an official vote. There by making a clear distinction between sraw poll and proposals.
>
>
> On Thu, Jan 24, 2013 at 3:58 PM, Jehan Tremback <jehan.tremback(a)gmail.com> wrote:
> I was frustrated last night by the repeated suppresion of straw polls, and meta-processing around whether members should even be able to call for a straw poll about specific things.
>
> I would like to propose that we add to the compact that any meeting participant, when they are on stack, is unconditionally allowed to call for a straw poll. The other participants can then either yea, nay, or abstain. I think this will make the process more smooth.
>
> -jehan
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>
>
>
>
> --
> -------
> Andrew Lowe
> Cell: 831-332-2507
> http://roshambomedia.com
>
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
[View Less]
How about Safe Space Steward?
Just to keep the process moving, not to judge - as i understand Anthony's suggestion.
Such a person would keep issues from escalating to the whole group, and would bring clarity to when it would be appropriate to move from mediation stage to group conflict resolution due to inability to resolve informally. It was my impression that a big chunk of the controversy last night was whether or not alternative solutions were exhausted. If that transition is made more …
[View More]transparent and effective with a 'buck-stops-here' Safe Space Steward functionary position, I imagine people would feel more confident in the process. This person could also make sure that something is done rather than lingering (intentionally or not) when the group does make a decision.
I also am in favor of figuring out ways to implement the safe space framework embedded in the kernel of our social norms. Maintaining level-headed discussion on the topic, as has been practiced on this list so far from my perspective, also seems worth preserving somehow structurally. Yardena's draft does seem like a great place to start, as was mentioned again at the meeting last night.
sent from eddan.com
On Jan 24, 2013, at 4:19 PM, Anthony Di Franco <di.franco(a)gmail.com> wrote:
> The reason for this is that I think the process is failing not in its substance but just by being extremely disorganized, which has led to the flaws you sought to correct, such as poor communication, confusion about the facts, speculatively assuming intentions and motivations and consent from indirect evidence, gossiping around key questions rather than seeking clear answers from the relevant parties.
> Thus there should be someone on point for organizing the process, just as there are for meetings and finances.
>
> On Jan 24, 2013 4:12 PM, "Anthony Di Franco" <di.franco(a)gmail.com> wrote:
> I am not suggesting that there be a specialized mediation group or designated mediator, rather that there be someone responsible for gathering all relevant information about the process together and communicating it to the mediator and conflicting parties, and group if needed, and keeping the process on track.
>
> On Jan 24, 2013 4:01 PM, "Andrew" <andrew(a)roshambomedia.com> wrote:
> Jehan: putting the situation with Timon aside, if there is good documentation about the steps that have been taken to reach out to both parties, and diligent information gathering has taken place and is documented, then the group should have enough information to the unfortunate step of making a decision on how to proceed without one of the parties present or participating.
>
> Talking about the situation with Timon in particular, this was not done. Hence the jab at me not being at the last two meetings. I should not have to have been at the last two meetings to meaningfully participate in a conflict resolution that has gotten to the point of needing group intervention. As a specific example I was a singular third party witness to one on the incidents in question, while it is partly my fault for not coming forward with my perspective early in the process, at no time was the conflict well defined enough and the process working enough for me to feel comfortable providing my point of view. I'm also concerned that at no time did either party reach out to me to provide more information.
>
> Anthony: I disagree. every conflict is unique and there is no way that a specialized mediation group can provide a balanced view on all conflicts. However I do think that it's import to establish regular education sessions around deescalation and conflict resolution.
>
> --Andrew
>
>
> On Thu, Jan 24, 2013 at 3:46 PM, Anthony Di Franco <di.franco(a)gmail.com> wrote:
> All of this is excellent and because for the most part these things were are conspicuously lacking, I would like to propose the creation of an additional office to be responsible for doing all these things, including as well stewarding the mediator and conflicting parties through the resolution process, documenting clearly and concisely that this is done and collecting together all relevant communications, and informing relevant parties at the appropriate steps in the process including the whole group when appropriate. Additionally this officeholder would co-facilitate with the facilitator during whole-group conflict resolution, prepare a written background brief for the whole group with all relevant documentation, and answer points of information that come up.
> I propose to call this the office of the Judge Advocate General, and were it to be created, I would volunteer for it.
>
> On Jan 24, 2013 2:54 PM, "Andrew" <andrew(a)roshambomedia.com> wrote:
> Hi,
>
> This is kind of a brain dump about our conflict resolution process. The proposal is that the following ideas be placed in to the Articles of Association under conflict resolution or in a addendum that deals specifically with conflicts. Mainly I'd just like to get the meta conversation started with the goal of making the sudo room the conflict resolution process go smoother.
>
> 1. All steps that have been taken in resolution to a specific conflict should be documented. Beginning with a full account of complaints (if any).
>
> 2. While we can't guarantee objectivity it is important that discussions during conflict resolution revolve around problems and facts and not people and assumptions.
>
> 3. State explicitly that the goal of conflict resolution is to build mutual respect and understanding. Every step in the process is taken with this goal in mind.
>
> I would also propose that while every conflict is unique, the following basic steps are strongly suggested as a framework to resolution whether with a mediator, between individuals, or if the group needs to intervene:
>
> Set The Scene: Establish the goals and values surrounding conflict resolution at Sudo Room.
>
> Gather Information: Gather facts about the situation from both sides and any third parties who have relevant information. Identify the issues. Listen.
>
> Brain Storm Solutions: Both parties are given a chance to come up with possible solutions to the defined problems.
>
> Negotiate Solutions: Come to a win-win solution that takes in to account the interests of both parties. If this is not possible the group must intervene and vote on a possible solution brought up in the brain storming process based on the voting schema already in the Articles of Association.
>
>
> Thanks for reading,
> Andrew
>
>
> --
> -------
> Andrew Lowe
> Cell: 831-332-2507
> http://roshambomedia.com
>
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>
>
>
>
> --
> -------
> Andrew Lowe
> Cell: 831-332-2507
> http://roshambomedia.com
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
[View Less]