--- Log opened Wed Feb 15 00:00:46 2012
06:04 -!- davycw_ is now known as davycw
09:42 < sdboyer> hieroph4nt: iiiinteresting...you guys decided to avoid the browser and go for a desktop app, eh?
09:42 < sdboyer> only way to really not be client/server
09:42 < hieroph4nt> sdboyer: web is dead xD
09:42 < sdboyer> hieroph4nt: lol
09:43 < hieroph4nt> for those who want to be update on globalsquare, last release http://theglobalsquare.org/call4coders
09:43 < hieroph4nt> sdboyer: what do you think about that?
09:43 < hieroph4nt> need help to get python coders on board
09:44 < sdboyer> hieroph4nt: i can understand why you made the decision...i gotta get on the train though, i'll ponder it a bit while i'm there then ping you once i'm at the office
09:44 < hieroph4nt> great
09:45  * scottrigby hellos hieroph4nt 
09:46  * hieroph4nt hails scottrigby
09:46 < hieroph4nt> how are u mate?
09:46 < hieroph4nt> did we talk before?
09:47 < scottrigby> hey :) oh yeah, it's scott from basekamp
09:47 < hieroph4nt> oooh
09:47 < hieroph4nt> right, right!
09:48 < hieroph4nt> what is up?
09:49 < scottrigby> right now trying to find a place for the Squatting Europe Kollective to get internet to talk with us while they're in NYC
09:50 < hieroph4nt> nice
09:50 < scottrigby> actually…
09:50 < hieroph4nt> i dont know this kollective
09:50 < hieroph4nt> will find out
09:50 < scottrigby> oh… i'll get a link
09:51 < hieroph4nt> k
09:51 < scottrigby> http://occuprop.blogspot.com/
09:51  * hieroph4nt looking
09:51 < scottrigby> has info on the SQEK "convention"
09:52 < hieroph4nt> yes i see
09:52 < hieroph4nt> sounds interesting
09:52 < hieroph4nt> hope somehave the chance to also visit nyc
09:53 < hieroph4nt> hope someday i will have the chance to also visit nyc
09:53 < scottrigby> and Philly!
09:56 < hieroph4nt> haha sure!
09:58 < scottrigby> sdboyer: btw, someone (Jake?) sent an email about the Yippie Museum… do you (or know who might) have a sympathetic contact there?
09:58 < scottrigby> or do you know of any other places where an occupy-related Skype conference call might happen in NYC? ^ for the SQEK thing i mentioned just above
09:59 < hieroph4nt> i really dont know :D
09:59 < scottrigby> this would be sometime during February 23-27
09:59 < scottrigby> actually, i should probably mail the list
11:15 < sdboyer> scottrigby: i don't know yippie, sorry
11:18 < sdboyer> hieroph4nt1: so, my thoughts - i think a p2p network is ideal for content distribution, ensuring availability, and avoiding tampering and censorship
11:18 < scottrigby> ok np… this just promises to be a really cool ows-related un-conference and they've been trying to connect to us on Skype, but have nowhere to do that atm
11:18 < sdboyer> and i also think that doing p2p pretty much inevitably does mean not doing it via a browser (which is entirely fine)
11:21 < sdboyer> that you're still planning on emitting rdf is excellent, it keeps us describing things semantically and provides an interoperability format
11:21 < hieroph4nt1> yes
11:21 < hieroph4nt1> hope we can make our coordination stronger tho
11:21 < sdboyer> that's on the plus side. on the downside, without knowing tribler, i think there are some key coordinative problems that p2p makes very difficult
11:21 < hieroph4nt1> are u still in contact with ed?
11:22 < sdboyer> haven't talked with him in a little while, he and i should catch up
11:22 < hieroph4nt1> for example?
11:22 < sdboyer> any item of content that can be edited by multiple people
11:23 < sdboyer> what happens with a simultaneous write in multiple locations? it's your basic master-master replication problem
11:24 < sdboyer> this isn't really an issue with most filesharing right now, where it's all fundamentally additive...ehh, there's a word for the journaling technique
11:24 < sdboyer> you never overwrite anything, just create new instances
11:24 < sdboyer> which is fine for something like a piece of media, but is much less fine when you need to have a canonical thing, like say an event
11:25 < sdboyer> i think that's just a Hard Problem to do in a fully decentralized fashion
11:26 < sdboyer> not impossible, but
11:27 < sdboyer> that's one more technical issue, anyway. i also tend to believe that the key problem to be solved for a network like this to be good is the discoverability and porousness of the overall system to new/different people
11:27 < sdboyer> that's really what makes it transparent and participatory
11:27 < sdboyer> which isn't necessarily something that's more difficult to do in a desktop app, but it is something we're generally a bit more accustomed to in the web world
11:28 < sdboyer> which also dovetails with the note that i think there are, generally speaking, a lot fewer folks with the skills to work on something desktop app-based than web-based
11:29 < sdboyer> all that having been said, it's been in the back of my mind for a while that something like a non-http-based connection to this system would be necessary, as well as the p2p distribution of the content
11:29 < sdboyer> so from what i read of your plans so far, i'm still pretty happy in that it seems like we could design something interoperable with both an http-based and a desktop-based component, with some different capabilities for each
11:29 < sdboyer> e.g., nothing private over the http (which is our current plan for FGA, already)
12:32 < sdboyer> scor: ping
12:32 < sdboyer> elf-pavl1k: ping to you too :)
12:41 < scor> sdboyer: in meeting but will try to reply shortly
12:41 < sdboyer> scor: no rush
12:41 < scor> what's up?
12:41 < sdboyer> it's a big-picture question
12:41 < sdboyer> i'm working on the shell of the overall FGA spec doc right now
12:42 < sdboyer> and thinking about the role of RDF in describing various components of the system
12:42 < sdboyer> actually i need to step back and remember my original question, it's kinda muddy now, one sec :)
12:44 < elf-pavl1k> melvster1: hi =)
12:44 < melvster1> hi :)
12:45 < elf-pavl1k> sdboyer has some questions related to RDF here, since you have posted about project he works on to socialswarm and others lists thought to invite you here =)
12:45 < melvster1> i know a bit about rdf ... happy to help, if I can :)
12:45 < sdboyer> elf-pavl1k: ahso - had a diff question for you
12:46 < sdboyer> no worries, i'm sure scor can cover it if not
12:46 < sdboyer> still formulating the RDF question, let me switch to my one for elf-pavl1k
12:46 < melvster1> haha scor knows much more than me :)
12:47 < melvster1> but ive been following distributed social networks for a few years ... so any questions you have i can probably help there
12:47 < sdboyer> cool
12:47 < sdboyer> so, how is the problem of registering any sort of node typically handled in a federated system? seems like explicit registration is usually just skipped
12:47 < elf-pavl1k> sdboyer: melvester helped with creating webid spec and does bunch of other cool projects!
12:47 < sdboyer> aaaaaaaaaawesome!
12:47 < sdboyer> melvster1++
12:47 < melvster1> lol :)
12:47 < sdboyer> and nodes only 'appear' when some manner of interaction actually occurs
12:48 < sdboyer> scor convinced me that webid probably *is* an option for our particular distributed auth situation, which is exciting
12:48 < melvster1> sure it is
12:48 < melvster1> it's good you talk about nodes
12:49 < melvster1> this is the most important thing to get right (or wrong)
12:49 < sdboyer> :)
12:49 < sdboyer> lemme turn this doc on public, hang on
12:49 < sdboyer> the basic problem we need to solve is that without any kind of canonical listing of all the sources, it's impossible to design network-wide search capabilities
12:49 < sdboyer> which is really pretty important
12:49 < elf-pavl1k> sdboyer: but i haven't understood this 'reqistering' part, do you mean in some example?
12:49 < melvster1> first things first
12:50 < melvster1> and this is the most important think i can tell you
12:50 < sdboyer> https://docs.google.com/document/d/1jURttum7YjVTxwLU8Ocv5ZhWMZ0RM4sByEuzQMabzIg/edit
12:50 < sdboyer> let's not share it around too much just yet
12:50 < melvster1> nodes must have an identifier
12:50 < sdboyer> yep
12:50 < scor> sdboyer: I think there should be a central repository that gets pinged when someone creates a node and wants to be included
12:50 < sdboyer> scor: yeah i've been dancing around that a bit but it seems kinda unavoidable
12:50 < sdboyer> i was thinking a p2p approach to that could work well
12:50 < melvster1> if the identifier is a local variable your system will scale locally, if your identifier is a global identifier (ie a URI) it will scale globally
12:50 < melvster1> hi scor :)
12:51 < sdboyer> melvster1: for sure
12:51 < scor> hi melvster1
12:51 < melvster1> this is what almost every network gets WRONG
12:51 < sdboyer> melvster1: seriously? that's kinda...distributed system 101
12:51 < sdboyer> :)
12:51 < scor> melvster1: no worries, sdboyer knows it already
12:51 < melvster1> yes well the simple things are the most powerful
12:51 < melvster1> great!
12:51 < sdboyer> :)
12:52 < scor> we've got site URIs etc
12:52 < sdboyer> yep
12:52 < scor> UUID is necessary
12:52 < sdboyer> though those are potentially subject to change, so yeah...uuid
12:52 < melvster1> which URI scheme?  http?
12:52 < sdboyer> i would prefer a uuid at the core, which could have (potentially mutable) schemes depending on how its being accessed
12:52 < melvster1> a UUID is not a URI
12:52 < melvster1> you can have a URN
12:52 < sdboyer> yep, i know
12:52 < melvster1> with a UUID
12:52 < melvster1> sorry
12:53 < sdboyer> no worries
12:53 < melvster1> i dont mean to be patronizing!
12:53 < sdboyer> you're not at all, don't sweat it :)
12:53 < sdboyer> you have no idea how much i know, and want to make sure basics are covered, it's totally understandable
12:53 < sdboyer> our primary initial use case is a website and HTTP-based services
12:54 < melvster1> brilliant
12:54 < melvster1> well we know that scales
12:54 < melvster1> :)
12:54 < sdboyer> iiiiindeed. there'll lkely be some others as time goes on, but that's the first use case to tackle
12:55 < sdboyer> elf-pavl1k: so the primary case here - we've got a ton of network nodes which are all producing content. most of the time it's fine if "network interaction" only occurs if some user from one site crosses the boundary to another site and joins a group, posts content, wants to get updates, etc.
12:55 < sdboyer> that part's easy. what's *hard* is giving that user the ability to do a "global" search throughout the network, including of nodes they're not already subscribed to in some fashion, for some relevant content
12:55 < sdboyer> we've already established that network wide RDF datastores is a good way to solve this problem in general
12:56 < melvster1> sure and even better is read / write RDF data stores
12:56 < sdboyer> but we still have to be able to provide a canonical, or at least approaching-canonical, list of the data sources to the RDF dbs so that they can index everything in the first place
12:56 < scor> sdboyer: isn't that what we brielfy discussed on skype? (the search on nodes thing)
12:56 < sdboyer> scor: exactly
12:57 < sdboyer> melvster1: rw RDF? interesting...can't quite picture that, i've always thought of it as really read-oriented
12:57 < scor> yes
12:57 < scor> sdboyer: that's the RDF push I was telling you about
12:57 < sdboyer> scor: ohhh, i totally forgot about it
12:57 < melvster1> sdboyer: the first browser written in 1990 was read / write ... you could save edits to pages ;)
12:57 < scor> RDF data available in each node, each node can push its data to the central index
12:57 < sdboyer> melvster1: and we still have all the relics in the http protocol, hehe
12:58 < elf-pavl1k> sdboyer: maybe shooting blind - how about putting up some nodes of http://yacy.net/en/ ?
12:58  * sdboyer looks
12:58 < scor> or the central repo can pull from all the subscribed nodes
12:58 < melvster1> POST PUT PATCH DELETE MKCOL
12:59 < sdboyer> indeedly
12:59 < melvster1> sparql POST is very clever too
12:59 < melvster1> there's something called the sparql 'protocol' ... i havent looked at it much lately
12:59 < melvster1> but people i know say good things about it
12:59 < sdboyer> elf-pavl1k: that's interesting, first i'd heard of that
12:59 < melvster1> http://www.w3.org/TR/rdf-sparql-protocol/
13:00 < melvster1> oh yes there's rdf push too
13:00 < melvster1> i forgot about that one :)
13:00 < sdboyer> elf-pavl1k: RDF gets us other benefits, so i think it's maybe best to stick with that...but let me try to read a bit more about yacy later and how you create a network within it that indexes only a specific set of "sites"/data
13:01  * sdboyer sees if he can mentally reconcile these things
13:01 < elf-pavl1k> sdboyer: i don't see them coliding... yacy just gives some 'out of the box' searching
13:02 < sdboyer> elf-pavl1k: gotcha
13:02 < scor> melvster1: SPARQL protocol is what is used to retrieve sparql results, I'm sure you've used it without knowing it ;)
13:02 < melvster1> cool!
13:03 < melvster1> so you're going to base this on drupal?
13:03 < sdboyer> the web platform anyway, yup
13:03 < elf-pavl1k> sdboyer: can you write down some example interaction scenarios expressing the chellenge you talk about? (whenever you get a chance)
13:03 < sdboyer> elf-pavl1k: yeah, i'm tryin to write them in this doc...
13:04 < melvster1> the lorea.cc folks have done quite a bit of work on this stuff, including webid / ostatus integration, but it's based on elgg ... unfortunately elgg has very few resources these days
13:04 < sdboyer> yep
13:04 < sdboyer> we've been conversing with lorea folks for a while
13:04 < elf-pavl1k> sdboyer: i guess you've met hellekin? he did bunch of stuff for lorea-elgg
13:05 < scor> melvster1: and with dispora too
13:05 < sdboyer> much of the reason to do it with drupal is simply that we can make it *rain* developers
13:05 < melvster1> lol
13:05 < melvster1> good choice
13:05 < melvster1> maybe we can put this in freedombox too then
13:06 -!- scottrigby_ is now known as scottrigby
13:06 < sdboyer> i heard about those but haven't had time to investigate - that's that debian...thing, right?
13:06 < melvster1> yep
13:06 < sdboyer> and yeah, hellekin used to camp out in here
13:06 < melvster1> dont worry, i follow it
13:06 < sdboyer> remind me of the goal again?
13:06 < melvster1> it's a little box you plug in
13:06 < melvster1> plug computer
13:06 < melvster1> and it does your social networking for you
13:06 < melvster1> among other things
13:07 < sdboyer> elf-pavl1k: so basically, the situation is this: someone sets up a new node (drupal site + correponding services). how do we provide a way for a) its new, fresh-faced users to discover other occupation sites (since they're not explicitly connected to any yet)
13:08 < sdboyer> and b) how do we know where to reach out to to find out what's trending/happening in the meta-network spaces? (this is MUCH more complicated and longer-term, but still relevant
13:08 < sdboyer> basically it's a problem of providing connection to existing activity without users having reached out and made an explicit connection
13:09 < sdboyer> melvster1: see it's interesting, the more i think about FGA the more i think it's *not* about individuals. they're important, but it's really more about the group situations we create
13:09 < melvster1> sdboyer:  one possible solution give your project a DOAP file (description of a project)
13:09 < melvster1> from the DOAP you can link to a registry
13:10 < sdboyer> which makes it orthogonal to many of the highly individual-centric efforts
13:10 < melvster1> you can do both :)
13:11 < elf-pavl1k> sdboyer: i would see need of some nodes acting as such 'registries', not one central but various one - some more popular some less, but
13:11 < melvster1> scor might have a good idea how to do this kind of distributed search
13:12 < scor> melvster1: I think the main question here is about infrastructure, data flow…. DOAP is just a vocab, mostly about providing a decription for each node
13:12 < elf-pavl1k> and it should work rather smooth to make 'listings' in any number of them
13:12 < sdboyer> elf-pavl1k: yeah ok you're thinkin in the same direction as i am
13:12 < scor> which is good, but does not solve the data flow, where data lives
13:12 < sdboyer> which brings me back to p2p or a gossipy protocol of some kind for the registry data
13:13 < melvster1> but you can have a central DOAP for the parent project that links to it's preferred registry ... when all else fails you can check that
13:13 < elf-pavl1k> not sure if on the same page but i would see it in plurale 'registries'
13:13 < scor> yeah p2p it is - we could bake that in the RDF data module in Drupal
13:13  * sdboyer is happy to file this away under questions to be solved specifically later
13:13 < melvster1> discovery in the "open world assumption" is an interesting problem ...
13:13 < sdboyer> elf-pavl1k: yeah it's essential that it be multiple - whether those are all the same canonical copy or multiple incomplete copies from which a whole can be stitched together...i could go either way
13:14 < elf-pavl1k> sdboyer: to collect some 'interaction cases' in executable plain english you can look at stuff like here: http://bdd.alexo.it/
13:14 < sdboyer> melvster1: that it is :)
13:14 < elf-pavl1k> i just have xp with cucumber while doing rails stuff...
13:14 < sdboyer> mmm, cucumber
13:14 < melvster1> i can ask kingsley .. he's good at that kind of thing
13:14 < sdboyer> i do like bdd, but i haven't had a chance to actually employ it for anything yet
13:14 < sdboyer> it's one of the many dev best practices areas that drupal lags behind in
13:15 < sdboyer> interesting that this guy is doing it with drupal though, that's handy
13:15 < sdboyer> elf-pavl1k: maybe this ends up in an interaction use case, but i think this is mostly something i'd prefer be solved faaaar away from user interaction
13:15 < sdboyer> at least that's my gut
13:16 < melvster1> if you're going to use drupal matt slater runs the LETS module for time banking etc.  elf-pavl1k knows him too ... ive also made a linked data economic system :)
13:17 < elf-pavl1k> sdboyer: i just sometimes find people (including me) fooking for a 'holy grail' and very general solution, while many stuff we can solve piece by piece and generalize later...
13:17 < melvster1> in fact i based my system mostly on the drupal table :)
13:17 < sdboyer> elf-pavl1k: yeah quite agreed
13:17 < sdboyer> elf-pavl1k: consider this discussion me trying to just get the lay of the land, identify where the holy grail is, then go solidly in the direction of "good enough" :)
13:18 < elf-pavl1k> sdboyer: hey, i do love to brainstorm =D
13:18 < sdboyer> :)
13:18 < scor> melvster1: kingsley is also very pushy
13:18 < sdboyer> hehe
13:18 < melvster1> sure he can be, but he knows his stuff
13:18  * elf-pavl1k 'pushy' LOL :-)
13:18 < sdboyer> melvster1: i wonder if i may have heard about that...there's been a bunch of alternative economic discussions going on in ows spaces, needless to say
13:19 < melvster1> id say only timbl himself and perhaps a few others have kingsley's knowledge
13:19 < sdboyer> i can handle pushy personally, though i'm loathe to introduce pushy folks into the FGA group spaces
13:20 < elf-pavl1k> sdboyer: you can still ask questions on various channels, melvster1 knows tons of them from what i see ;)
13:21 < sdboyer> absolutely
13:21 < sdboyer> melvster1: if you're the irc camping type, i'd love it if you'd hang out in here
13:21 < melvster1> ill add it to my macros :)
13:21 < sdboyer> great
13:21 < melvster1> xdotool key slash
13:21 < melvster1> xdotool type "join #ows-fga"
13:21 < melvster1> xdotool key KP_Enter
13:22 < melvster1> :)
13:22 < sdboyer> the past 6 weeks have been slow for us - honestly since the wired article came out i've basically just been swamped with conversations about the project, rather than actually driving it forward
13:22 < melvster1> yeah that normally happens in the beginning
13:22 < melvster1> after 6 months often a different story
13:22 < sdboyer> we've been shoring up our overall plans for the network, and just had our inaugural meeting of our "sounding board" (composed of actual real-world organizers) last week
13:22 < sdboyer> hehe
13:23 < melvster1> one person in lorea that is very good is caedes
13:23 < sdboyer> but we finally got the skeleton for this spec doc out, so i'm going through and...giving birth to all the crap that's gotten built up in my head since our original docs & specs were written
13:23 < sdboyer> don't know him/her
13:23 < sdboyer> we've got our build system somewhat together, which i'm pretty excited about
13:24 < sdboyer> actually very excited about - imo, it's a lynchpin in making this something which can actually have lots of people working on it, commenting on its development, etc.
13:24 < melvster1> joining forces with drupal could be an awesome idea
13:25 < sdboyer> that part is decided, a donedeal
13:26 < sdboyer> consider it a pre-assumption for the project. it doesn't necessarily have to be built in drupal, of course, but much of the interest we've drummed up thus far has been through the drupal community
13:26 < sdboyer> got a lot of people waiting to be able to sink their teeth in and hel
13:26 < scor> well, a lot of people in the group are from the Drupal community already - that's the first thing I noticed when I joined!
13:26 < sdboyer> help
13:26 < sdboyer> indeed
13:26 < melvster1> sdboyer: have you heard of social swarm?
13:26 < sdboyer> the whole idea was first written down at drupalcamp san francisco last october
13:26 < sdboyer> melvster1: i have
13:26 < sdboyer> it feels rather different from what we're looking to do
13:27 < sdboyer> i'm a bit of an apostate when it comes to swarms :)
13:27 < scor> sdboyer: #swig is where a lot of the semweb / RDF discussion happens…
13:27 < elf-pavl1k> sdboyer: ok, i need to lay down and rest a bit, please ping me once you have written down some example interaction scenarios showing various challenges =)
13:27 < sdboyer> scor: cool, joined
13:28 < sdboyer> elf-pavl1k: i'll try to, but i'll likely have to backburner it - can't get into that level of detail at this stage in the spec-writing
13:28 < sdboyer> need to cover the full spectrum first
13:28 < elf-pavl1k> sdboyer: no rush ;)
13:28 < sdboyer> thanks!
13:29  * elf-pavl1k waves to all \o/
13:29 < sdboyer> ...holy shit i'm on the frontpage of the village voice website
13:30 < sdboyer> melvster1: http://projects.occupy.net/boards/6/topics/27 - we're really oriented towards groups, like i said, so i'm slightly hesitant towards more algorithmic/swarm-based interaction models
13:31 < sdboyer> but i have read a bit about socialswarm and do want to know more - i've not prejudged it or anything :)
13:31 < melvster1> sdboyer: seen that page already ... posted it to a few lists this morning :)  yes it looks good
13:32 < sdboyer> yeah the reporter didn't tell me it'd been published, heh
13:32 < melvster1> oh wait ... maybe not that exact page
13:32 < melvster1> one other from the site
13:32 < melvster1> ok reading ...
13:33 -!- hieroph4nt1 is now known as hieroph4nt
13:34 < melvster1> sdboyer: im amazed how many conversations you can hold simultaneously :D
13:35 < sdboyer> melvster1: ahh, that's the wonderful illusion of technology - that i'm actually "holding" the conversations, not just flitting around like an ADD fuzzball
13:35 < melvster1> :)
13:35 -!- amgine is now known as Amgine
13:39 < sdboyer> oh...yikes. nick really got the wrong impression from me about a launch date
13:39 < sdboyer> well, that's not good
13:40 < lifeSUX> http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2012/02/15/BA8N1N7HNQ.DTL
13:40 < lifeSUX> no change in 130 years of snowfall in the sierras
13:44 < lifeSUX> hehehe
13:45 < lifeSUX> http://www.wnd.com/2012/02/20-reasons-obamas-a-socialist/
13:46 < sdboyer> lifeSUX: not really on-topic for this channel
13:46 < lifeSUX> yes, it IDS. OWS is run by socialists
13:46 < lifeSUX> IS
13:47 < scottrigby> :|
13:47 < sdboyer> lifeSUX: still not on topic for this channel.
13:47 < sdboyer> this is a channel for a software project, not political discussion about occupy in general
13:47 < lifeSUX>   ...and the OWS is full of eco-nazis
13:48 < lifeSUX>  This channel is for the Federated General Assembly working group (infrastructural support for a federation of occupations in solidarity with Occupy Wall Street)         hmmm, OWS.
13:48 < sdboyer> yes. it's an software project in support of occupy. the purpose of the discussion is not politics about the movement - it's about the software project.
13:49 < sdboyer> you're welcome to criticize or call the movement into question in other spaces, but it's not on topic here
13:50 < lifeSUX>      ok, wronf channel .. sorry.  I';ll let you marsists sceme in peace
13:51 < sdboyer> thank you
13:51 < lifeSUX> still, if you support them , you must agree with their thinking and/or philosophy .. GHow stupid is THAT???
13:52 < sdboyer> heh
13:52  * sdboyer is glad he didn't have to kick him
13:58 < scottrigby> nice one sdboyer
13:58 < sdboyer> scottrigby: ty
13:58 < scottrigby> kicking is sometimes fuel on the fire
13:58 < sdboyer> exactly
13:59 < sdboyer> to say nothing of it also being totally inconsistent with that whole "respectful group spaces" thing i'm always touting :)
13:59 < sdboyer> OH CRAP
13:59 < scottrigby> ?
13:59 < sdboyer> i have the email waiting from the directcongress.org people
13:59 < sdboyer> you saying something just reminded me
13:59 < scottrigby> cool
13:59 < sdboyer> it slipped through the cracks, i'll respond right now
14:00 < scottrigby> i mean… idk how cool that project really is, but does seem an interesting thing to at least be in conversation with
14:15 < sdboyer> right
16:44 -!- tbishop is now known as thebishop
22:09 -!- davycw_ is now known as davycw
--- Log closed Thu Feb 16 00:00:02 2012