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 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.
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 ----------
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
> 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: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.
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
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"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
>
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 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
> >
>
>> 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#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.
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 one submit events for the calendar?
all hail sudo!
R.
