And I should add, Mycelia does seem like the most useful way to aggregate info re: people, things, skills. <div><br></div><div>Ideally what we&#39;d want in my view for a directory Mycelia might query is one somewhat like a password manager, in which user contact info is encrypted at rest to that user even to admins (as with passwords), with fields invisiblizable to everyone else unless they are shared (not unlike filesharing). IE a privacy token could be set for specific fields, so users toggle what fields are visible to whom, or template which fields are shared by default (ie email) and which fields must be manually made accessible to specific users (ie celfone, home address, etc), or reshareable by others, etc. I realize this doesnt exist (or does it..?) but it could be useful architecture for safely sharing personal info. </div>
<div><br></div><div>Then a way to publish/sub this db via carddav so we can have this sync to our phones.. </div><div><br></div><div>I was looking into this the other day and i<span></span>n general the current state of the market with respect to directory services, contact mgmt &amp; CRM still seems pretty impoverished with respect to user-settable access controls and field-specific privacy, so far as I can tell: You either add your (private) cel to your vCard, or you dont. No way to modulate down to this level. Actually I think M$ has some basic way to do this in AD-enabled GALs.. but nothing OSS-based as far as I know of, at least.</div>
<div><br></div><div><br></div><div><br></div><div><br><br>On Tuesday, February 18, 2014, David Keenan &lt;<a href="mailto:dkeenan44@gmail.com">dkeenan44@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This project brings up the age-old issue of transparency vs privacy. Too much &#39;transparency&#39; can be bad in ways Jenny pointed out, too much privacy keeps work from being more collaborative which is endemic to the attraction of hackerspaces and collectives. In general i feel transparency is too privileged. We forget transparency often involves a loss or giving up of individual agency and control, not just a gain in centralizeable, actionable &#39;data&#39;. <div>

<br></div><div>I do think this tradeoff needs to be modulated and controlled at all times by individuals themselves. In my view there shouldnt be a repo where you are expected to list what you deem is your personal info, even matching names to &#39;nym&#39;s if ppl arent down for that. But i think matching nym&#39;s to projects would be useful, if folks are willing to document say what part of what project they are working on, as in dev environments. And perhaps people could set their own privacy settings, only share at their discretion certain info with certain people. I would participate in something like this if such privacy controls were part of it from the outset. Privacy, with respect to user-controllable visibility of personal info, needs to be thought of as a fundamental integral component, not an add-on, for every  software product.</div>

<div><br></div><div>my 2c. carry on<span></span><br><br>On Tuesday, February 18, 2014, Jenny Ryan &lt;<a>tunabananas@gmail.com</a>&gt; wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir="ltr">Oh! I should add that we could do really interesting things with our user pages, linking to projects through tags and categories, creating portals. I&#39;d love to spend a Today We Learned working on making our wiki more awesome, semantic, navigable (Vicky? Pete?).<br>



</div><div><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>
&quot;Technology is the campfire around which we tell our stories.&quot;<br>
-Laurie Anderson<br>
<br>
&quot;Storytelling reveals meaning without committing the error of defining it.&quot;<br>
 -Hannah Arendt<br>
<br>
&quot;To define is to kill. To suggest is to create.&quot;<br>
-Stéphane Mallarmé<br>
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`</div>
</div>
<br><br><div>On Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <span dir="ltr">&lt;<a>tunabananas@gmail.com</a>&gt;</span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir="ltr"><div><div><div>Hey Troy! Thanks for the poke!<br></div><div><br></div><div>tl;dr: Fill out your wiki userpage with current projects and contact info! Help with the membership registry (PHP) and/or mycelia (node)!<br>




</div><div><br><br>ABOUT THE DATA<br></div><div>a) I don&#39;t want everyone at sudo room to be able to call or text me. Fairly certain I&#39;m not alone in this. If you ask for my number and I give it to you, we&#39;ve just created trust through consent. Would like to promote a case-by-case approach to providing sensitive information, and not store it ourselves. This is why, when I asked for up-to-date membership information, I only asked for an email and a name/nym.<br>




<br></div><div>b) I think we should encourage people to fill out their user pages on the wiki, and include there things like projects, contact info, and public keys. We sent out a template for user pages long ago, can&#39;t remember who put it together (Marina, I think?). Here are some examples of nice user pages:<br>




<a href="https://sudoroom.org/wiki/User:Juul" target="_blank">https://sudoroom.org/wiki/User:Juul</a><br><a href="https://sudoroom.org/wiki/User:Tunabananas" target="_blank">https://sudoroom.org/wiki/User:Tunabananas</a> <br>



<a href="https://sudoroom.org/wiki/User:Mk30" target="_blank">https://sudoroom.org/wiki/User:Mk30</a><br>
<a href="https://sudoroom.org/wiki/User:Maximilianklein" target="_blank">https://sudoroom.org/wiki/User:Maximilianklein</a><br></div><div><br><br><div>ABOUT THE MEMBER REGISTRY / SELTZERCRM<br></div>I&#39;m running the nascent member registry at <a href="http://mycelia.cc/crm" target="_blank">http://mycelia.cc/crm</a>, the code for which is <a href="https://github.com/elplatt/seltzer" target="_blank">here</a>
 if anyone wants to look and see if they can build something on top of 
this. It&#39;s PHP. I did a decent bit of research and this was the most 
viable FOSS membership registry system I could find. Soon will port it over to <a href="http://sudoroom.org" target="_blank">sudoroom.org</a> and push to Github (hopefully tomorrow). I&#39;ve been asking for help at the meetings as it would be great to have more people who want to work on this, but it needs to happen so I&#39;m not waiting around for a team to form. <br>




<br><br>ABOUT MYCELIA<br>The goal of <a href="http://mycelia.cc" target="_blank">Mycelia</a> is to create a decentralized database for documenting projects, people (skills) and objects between hackerspaces and also matchmaking between them. Pub/sub [publish / subscribe] model encouraging folks to have concrete projects about which they publish updates, or otherwise be a subscriber consuming the updates of others :)<br>




</div><br>Unfortunately, I can&#39;t code it myself and Marc&#39;s busy with sudomesh and freestore. What&#39;s up on Github is essentially Labitrack (the QR-code sticker inventory system we&#39;re using at sudo) converted into NodeJS and LevelDB. It&#39;s definitely a priority project, but not #1 right now. CC&#39;ing substack in case he&#39;s interested in this project.<br>




</div><br><br></div>Cheers,<br></div><div><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"></a></div></div></blockquote></div></div></blockquote></div>
</blockquote></div>