<div dir="ltr">Apologies, Mia, I was composing my email and sent it off before I saw you'd replied. I'm sorry to hear you've had such a scary experience, and totally empathize. <div><br></div><div>The issue of protecting one's personal identity is a different issue than concealing all of our community's communications from public visibility. Openness and transparency is critical to any radical endeavor, and rather than resorting to the easy solution of locking things down, I think it's important we endeavor to find creative solutions to tangible problems.</div><div><br></div><div>The former problem of protecting one's personal identity can be solved by creating a pseudonymous identity from which to communicate with the group. Several members of this list (and many members of sudo) use pseudonyms when communicating with the community - some of them use those pseudonyms for all online communications and also in-person! I'd be happy to help anyone interested in creating a pseudonymous identity.</div><div><br></div><div>With love,</div></div><div class="gmail_extra"><br clear="all"><div>Jenny<br>
<a href="http://jennyryan.net/" target="_blank">http://jennyryan.net</a><br>
<a href="http://thepyre.org/" target="_blank">http://thepyre.org</a><br>
<a href="http://thevirtualcampfire.org/" target="_blank">http://thevirtualcampfire.org</a><br>
<a href="http://technomadic.tumblr.com/" target="_blank">http://technomadic.tumblr.com</a><br>
<br>
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`<br>
<div>
"Technology is the campfire around which we tell our stories."<br>
-Laurie Anderson<br>
<br>
"Storytelling reveals meaning without committing the error of defining it."<br>
-Hannah Arendt<br>
<br>
"To define is to kill. To suggest is to create."<br>
-Stéphane Mallarmé<br>
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`</div>
</div>
<br><div class="gmail_quote">On Sat, Oct 4, 2014 at 3:25 PM, Jenny Ryan <span dir="ltr"><<a href="mailto:tunabananas@gmail.com" target="_blank">tunabananas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Concur'd on all points, Matt. If people are concerned about their contributions being publicly viewable, they can post to 'confidential' or another private list - or simply have an in-person conversation. I'd like to know the particular use cases for which we would need closed, private mailing lists - because I strongly believe that open and transparent communication and documentation is essential to this project having an impact not just within our community, but for the wider world. If we intend to create something greater than ourselves, our methods of organizing, the problems we face and overcome, the things that bind or break us, our experiences of creating the space and communicating about it, all of this is vital and important knowledge we have a responsibility to share so that others may learn from, iterate off, adapt, fork, and possibly change their own corners of the world for the better, inspired by what we're doing here. <div><br></div><div>Let's not keep our history to ourselves. Knowing that our communications are public and archivable also keeps us accountable to ourselves, each other, and the world. We should always _expect_ what we communicate online to become potentially public, and may as well just own it, be responsible for our words, and communicate with kindness and wisdom - because words are often the most powerful artifacts we leave behind for future generations to inherit.</div><div><br></div><div>My favorite quote on communication, in particular the debate of dialogue vs. dissemination and the way in which communication flows from internal dialogue to outward dissemination:</div><div><span style="color:rgb(14,13,13);font-family:'Helvetica Neue',Helvetica;font-size:13px;font-style:italic;line-height:19.5px">Justice that is not loving is not just; love that is not just is not loving. Just so, dissemination without dialogue can become stray scatter, and dialogue without dissemination can be interminable tyranny. The motto of communication theory ought to be: Dialogue with the self, dissemination with the other</span><span style="color:rgb(14,13,13);font-family:'Helvetica Neue',Helvetica;font-size:13px;font-style:italic;line-height:19.5px">. This is another way of stating the ethical maxim: Treat yourself like an other and the other like a self.</span><br></div><div><br></div><div>(John Durham Peters, Speaking Into the Air: A History of the Idea of Communication, p. 57)</div></div><div class="gmail_extra"><br clear="all"><div>Jenny<br>
<a href="http://jennyryan.net/" target="_blank">http://jennyryan.net</a><br>
<a href="http://thepyre.org/" target="_blank">http://thepyre.org</a><br>
<a href="http://thevirtualcampfire.org/" target="_blank">http://thevirtualcampfire.org</a><br>
<a href="http://technomadic.tumblr.com/" target="_blank">http://technomadic.tumblr.com</a><br>
<br>
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`<br>
<div>
"Technology is the campfire around which we tell our stories."<br>
-Laurie Anderson<br>
<br>
"Storytelling reveals meaning without committing the error of defining it."<br>
-Hannah Arendt<br>
<br>
"To define is to kill. To suggest is to create."<br>
-Stéphane Mallarmé<br>
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`</div>
</div><div><div class="h5">
<br><div class="gmail_quote">On Sat, Oct 4, 2014 at 12:21 PM, Matthew Senate <span dir="ltr"><<a href="mailto:mattsenate@gmail.com" target="_blank">mattsenate@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>David, </div><div><br></div><div>I understand what you're sharing about the experiences you have had with people seeking voice and space in this project.</div><div><br></div><div>However, I do not believe that flipping bits from public to private on our email list archives will change that. I think Jordan's implementation of a <b>helpdesk@</b> list (private archives to protect senders), and leveraging clear public-facing, private (or semi-private), and alternative communication channels (e.g. physical "anonymous comment box" by the front door) are all <b>excellent</b> ways to approach these situations. We should set up a <b><a href="mailto:whistleblower@lists.omnicommons.org" target="_blank">whistleblower@lists.omnicommons.org</a> </b>or <b><a href="mailto:leaks@lists.omnicommons.org" target="_blank">leaks@lists.omnicommons.org</a></b> for instance!</div><div><br></div>Historically, I have had more than a handful of conversations with folks (some active members, other allies elsewhere in the world) who have used and read the public archives of the sudo room email lists for their information and for all of our benefit. We depend on this form of participation to continue to exist. Further, we link to these discussions in our email threads, on the wiki, and elsewhere.<div><br></div><div>We must be <b>clear</b> about what is <i>public</i> versus <i>private,</i> but we should challenge ourselves to make more communications available (indexed by google also means we can link to it on the public web... the structure of the web that was valuable <i>even before </i>search engines and the information search engines use to crawl content and formulate rankings, etc). We can also encourage search engines not to index this content to keep it unsearchable, but probably the folks who typically want to search it will be us and our community.</div><div><br></div><div>To me, a good number of our problems right now correspond to <b>access</b>, <b>transparency</b>, and <b>engaging new participants</b>. In light of these issues, there is a clear direction for us to travel in which we should value <b>"open, public discourses over closed, proprietary processes"</b> as well as <b>"access and transparency over exclusivity"</b> in order to <b>"solve real problems over hypotheticals, while respecting visions of the future"</b> - <a href="https://sudoroom.org/wiki/Articles_of_Association#Values" target="_blank">https://sudoroom.org/wiki/Articles_of_Association#Values</a></div><div><br></div><div>All three of us on this thread so far are sudo room members, what do you all think about these values I've shared?</div><div><br></div><div>// Matt</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 3, 2014 at 2:11 PM, yar <span dir="ltr"><<a href="mailto:yardenack@gmail.com" target="_blank">yardenack@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><span>On Fri, Oct 3, 2014 at 12:51 PM, David Keenan <<a href="mailto:dkeenan44@gmail.com" target="_blank">dkeenan44@gmail.com</a>> wrote:<br>
> I would like to help you welcome new members - if I can get those notices, I<br>
> will reply and copy you and Jenny.<br>
<br>
</span></span>We already have a list called "helpdesk" which is for receiving<br>
private emails about the omni, so if we all CC helpdesk then others<br>
know what's being done and how it's being done. Perhaps if we notice<br>
subscriptions from somebody new, we can forward the request to<br>
helpdesk!<br>
<br>
Anybody interested in being part of the general email liaison /<br>
outreach team, please subscribe. :)<br>
<br>
<a href="https://omnicommons.org/lists/listinfo/helpdesk" target="_blank">https://omnicommons.org/lists/listinfo/helpdesk</a><span><br>
<div><div>_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.omnicommons.org" target="_blank">discuss@lists.omnicommons.org</a><br>
<a href="https://omnicommons.org/lists/listinfo/discuss" target="_blank">https://omnicommons.org/lists/listinfo/discuss</a><br>
</div></div></span></blockquote></div><br></div>
<br>_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.omnicommons.org" target="_blank">discuss@lists.omnicommons.org</a><br>
<a href="https://omnicommons.org/lists/listinfo/discuss" target="_blank">https://omnicommons.org/lists/listinfo/discuss</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div>