<html><head></head><body bgcolor="#FFFFFF"><div>I'd definitely like to come to one of these, unfortunately I've had schedule conflicts last week and this week. I'll be interested in coming next week though.</div>
<div><br></div><div>I have some code I'd like to talk with someone about... but it's for a Tahoe-inspired key management system written in Ruby ;)<br><br>--<div>Tony Arcieri</div></div><div><br>On Sep 17, 2012, at 11:52 AM, Josh Wilcox <<a href="mailto:wilcoxjg@gmail.com">wilcoxjg@gmail.com</a>> wrote:<br>
<br></div><div></div><blockquote type="cite"><div> Hello all!<div><br><div> This Thursday, 2012-09-20 at 19:00 (UTC-7) there will be a physical meetup at the Noisebridge Hacker Space AT THE FRONT TABLE, in the Mission District of San Francisco.</div>
<div><br></div><div>
<a href="https://www.noisebridge.net/wiki/Noisebridge">https://www.noisebridge.net/wiki/Noisebridge</a></div><div><br clear="all"><div> In addition to inviting all readers of this list, I'd also like to stimulate an agenda-setting conversation.</div>
<div> </div><div> My personal preference is for a setup that results in me staring at code.</div><div><br></div><div> Ideally I'd know ahead of time that there're a few (or ONE!) chunk(s)/module(s) of code that are/is going to be examined/discussed during the meetup, so I can "study up".</div>
<div><br></div><div> I'd like to attract new mindshare so it'd be nice if the focus were on something that (perhaps with a short preamble) is difficult for a "typical" (as if there were such a thing!) Noisebridger to resist. This also means that our meeting space, AT THE FRONT TABLE, is a feature, not a bug.</div>
<div><br></div><div> I'd like to pre-empt a call for realtime video, because I believe that the physical space is likely to be difficult to control (particularly with regard to sound) for that purpose. I think realtime code-sharing (i.e. where those physically present can stare at a projected web-page that remote parties can view more "traditionally") will be feasible. </div>
<div><br></div><div> I'll be visiting the space tomorrow (Tuesday night) to, announce this meetup at the weekly Noisebridge political meeting, and troubleshoot the setup.</div><div><br></div><div> I'd like to have a head-count, so I can know how many chairs to commandeer, so emails to my "<a href="mailto:wilcoxjg@gmail.com">wilcoxjg@gmail.com</a>" account with subject:</div>
<div><br></div><div>[ATTENDING 2012-09-20 TAHOE MEETUP]</div><div><br></div><div> are greatly appreciated ( provided they're from an appropriate party! :) And there's a 1-1 correlation between party and email... and etc... ) .</div>
<div><br></div><div> OK... I've probably missed something, hopefully someone will remind me.</div><div><br></div><div> About Last Week:</div><div><br></div><div> During the inaugural (very informal) meetup last Thursday 2012-09-13, the following topics were discussed:</div>
<div><br></div><div> * Add Only Capabilities as an abstraction built on top of mutable files</div><div> * Resource Allocation Accounting</div><div> * Migration to vanilla HTTPS for inter-node communication</div><div> </div>
<div> I may (upon demand) publish slightly more detailed notes.</div>-- <br>Za <--> ظ<br><br>"I want people to see the truth... regardless of who they are... because
without information, you cannot make informed decisions as a public" <em>-- Bradley Manning</em><br><br>'Lame' is stale, 'cruft' is cruft. <br>"Who ordered it? Who ordered the saxogram?"<br>
<a href="https://www.youtube.com/watch?v=GaoLU6zKaws" target="_blank">https://www.youtube.com/watch?v=GaoLU6zKaws</a><a href="http://allmydata.org" target="_blank"><br></a><br>
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>tahoe-dev mailing list</span><br><span><a href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a></span><br>
<span><a href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a></span><br></div></blockquote></body></html>