Thanks for the input, Rachel. That sounds like a more appropriate action.
I've flipped Giovanni's mod bit. It's now up to list admins to allow
messages to pass through, or reverse my decision back to a ban or full list
Anyone who feels strongly about this is welcome to bring it up at a weekly
"Technology is the campfire around which we tell our stories."
"Storytelling reveals meaning without committing the error of defining it."
"To define is to kill. To suggest is to create."
On Sat, Nov 2, 2013 at 9:04 AM, Eddan Katz <eddan(a)clear.net> wrote:
Mailman people - Are we still banning Giovanni from the Sudo Room mailing
Can we instead activate the moderation feature now that the party is over?
How long are we planning to ban all Yandex addresses for?
On Oct 31, 2013, at 3:01 PM, Rachel McConnell <rachel(a)xtreme.com> wrote:
Doesn't mailman have a feature where a user
can be put into moderation?
Separate from the whole list being moderated.
Rachel1.0 (lurker with a bit of list management experience)
On 10/31/13 1:36 PM, Eddan Katz wrote:
> Perhaps we can institute a "TRO-l bloc" action, with priorly agreed upon
> Law folks call stopping someone from doing something before everyone's
> gotten a chance to get a good handle on what's going on, most
> importantly a judge - a temporary restraining order (TRO) or preliminary
> injunction. So TRO-listserv (or TRO-l) could have some settled upon
> period and parameters by which it can be instituted without
> consensus-taking. When talking about speech and code though, the rise of
> (usually entertainment) company calls for shutting down websites
> immediately amounts to "Prior Restraint" - which often seems draconian
> especially to free speech/open culture advocates. The standard for doing
> something that would amount to a prior restraint would then be stricter
> for an action to be taken and require more checks and balances as a
> Excuse the long-winded way about it - but I think this lens helps me at
> least tease out what may have been bothering some people on the list
> about how action was taken in solving the problem.
> Not sure how Holacracy! deals with it yet. And unfortunately not going
> to be able to make this next workshop they're hosting.
> On Oct 31, 2013, at 12:24 PM, Jenny Ryan <tunabananas(a)gmail.com
> <mailto:email@example.com>> wrote:
>> For the record, the action was taken by three people - myself, Matt,
>> and Marc when we were at sudo late last night working on things (such
>> as this weekend's event). All three of us have access to the listserv
>> and regularly moderate the bounces, mailman errors, etc. Matt sent
>> Giovanni a private email informing him that he'd been removed from the
>> I entirely support the suspension of someone who's not only been
>> spamming the list, but has been defacing Noisebridge's wiki and
>> posting messages such as the following:
>> Banning someone from a mailing list is *not* the same as banning them
>> from the physical community; it's a preservation mode so we don't
>> receive a bevy of heartbreaking unsubscribe requests. And we are also
>> hoping people can come together this weekend and support Sudo Room in
>> person - though many of you may have missed those posts in the barrage.
>> "Technology is the campfire around which we tell our stories."
>> -Laurie Anderson
>> "Storytelling reveals meaning without committing the error of defining
>> -Hannah Arendt
>> "To define is to kill. To suggest is to create."
>> -Stéphane Mallarmé
>> On Thu, Oct 31, 2013 at 11:01 AM, Lovelle Mixon <sudoroom(a)ilovebeer.ca
>> <mailto:firstname.lastname@example.org>> wrote:
>> Running a listserv is a completely thankless job.
>> You're just witnessing how giovanni_re/john fastmail/john/john
>> regan works. I don't think
>> he's a bad person. He's not assaulting anyone. He is genuinely
>> excited about computers
>> and Linux and communities and free software. His usual mode is he
>> joins a free culture/
>> community/open source software community mailing list, and then
>> every few months or so
>> starts cross posting interesting links or forwarding emails from
>> one list to the other,
>> no editing, just WHAM here read email from this other place, not
>> realizing that if someone
>> wants to read email from the other mailing list, they would just
>> JOIN that mailing list,
>> no need to forward it. He's been doing this for over 10 years.
>> He'll be doing it
>> long after sudoroom is gone.
>> You usually don't notice what's happening because he's on a LOT
>> mailing lists, and annoying
>> each of the mailing lists is a lot of work, so he doesn't get
>> around to forwarding stuff
>> to your mailing list until about a month in the cycle.
>> Sometimes he gets super excited about something ( RADIO! ) and
>> starts concentrating on
>> your particular community, and boom you get the 10 emails in 1
>> hour problem you just saw.
>> Unknown how to properly deal with him. People don't join his list
>> BerkeleyTIP so he feels
>> the need to branch out. Personally, I think it would help if he
>> fixed the links on his site
>> that are broken and updated and are over 4 years old now. That
>> would be a great start.
>> John, you have a perfectly good wiki over on BerkeleyTIP. You
>> could update it with spectrum FCC
>> radio announcements. You've been trying to get inspire
>> Noisebridge and Sudoroom to grab
>> some spectrum of their own. Getting your website in order would
>> be a good start.
>> Get your own ILoveBeer.ca <http://ILoveBeer.ca> email,
>> <yourname>(a)ilovebeer.ca <http://ilovebeer.ca/>!
>> sudo-discuss mailing list
>> sudo-discuss mailing list
>> sudo-discuss(a)lists.sudoroom.org <mailto:
sudo-discuss mailing list
sudo-discuss mailing list