Experimental IRC log sioc-2009-05-28

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

17:32:04<tuukkah>http://wave.google.com/ Why do we have to live with divides between different types of communication — email versus chat, or conversations versus documents?
17:37:49<blx>..just send all your data to us!
17:39:42<blx>hmm, seems like you can run your own servers as well. interesting
17:39:58<tuukkah>yup - built on top of xmpp
17:42:41<blx>i wonder what their business model is
17:45:56<tuukkah>be ahead and attract users from their competitors?
17:46:53<blx>but if they let people run their own servers they cannot data mine for ad targeting for example
17:47:17<blx>unless they tie it in somehow with their own servers, like app engine
17:52:40<tuukkah>i think they make the system open in the hopes that it will be accepted by users
17:53:49<blx>this does sound great, i'm just naturally suspicious of google, they know too much already :)
22:34:35<CaptSolo>interesting re Google Wave
22:34:53<CaptSolo>makes sense re. getting rid of divide b/w different kinds of communication
22:35:22<blx>CaptSolo: that was actually a plan of mine as well
22:35:35<CaptSolo>blx: it might be that the majority of ppl will prefer a hosted solution rather than deploying their own
22:35:50<CaptSolo>so google would still get to mine ~70-80% of communication
22:36:02<blx>yes probably
22:36:06<CaptSolo>blx: interesting re. plan
22:36:37<blx>it would be neat to just base things on FOAF, updates in different kinds listed by person
22:36:52<blx>like, person A sent you a message and commented on person B's blog
22:37:00<blx>facebook already does this in a great way
22:37:25<CaptSolo>it also matches observations reported by one of participants of http://webcamp.org/SocialNetworks/
22:37:43<CaptSolo>that different people have different preferred ways to receive conversations
22:38:01<blx>my systems rss reader is almost usable now :)
22:38:09<CaptSolo>even when conversations are on the same subject (which might ask you to pick one - a mailing list OR a blog OR ...)
22:38:19<CaptSolo>the solution is to bridge between them
22:38:46<CaptSolo>blx: the distributed p2p rss reader?
22:38:53<CaptSolo>or am i confusing 2 of your projects?
22:39:17<blx>it's the same project
22:39:30<blx>the rss data is not really fit for exporting though
22:39:40<blx>i'm planning on using it for local-only data as well
22:39:47<CaptSolo>how is that (not fit for exporting)?
22:39:48<blx>just so i can have one interface for everything
22:39:53<CaptSolo>as in - not interesting for exporting?
22:40:06<blx>well, i will use it for strictly private data as well
22:40:07<CaptSolo>sounds interesting
22:40:15<CaptSolo>'d love to take a look once it is ready
22:40:50<CaptSolo>but others could use it for their private data, too, right?
22:41:02<blx>yep
22:41:15<blx>CaptSolo: github.com/krl/rhzm
22:44:10<blx>not very well documented or anything though..
22:49:18<blx>(or usable)
23:28:32<Shepard>CaptSolo: my take on it is that all communication forms (e-mail, IM, phone etc.) have their unique areas of application where they are needed - otherwise they wouldn't have been specified
23:28:48<Shepard>but sometimes you need unifying views on them
23:29:33<Shepard>and that's exactly what SIOC does for online communication and collaboration - so we should keep a close eye on google wave to see if it can be exported to SIOC
23:30:27<Shepard>ah, missed something in the first line: unique areas of application (like in the CSCW matrix)
23:33:06<Shepard>(see http://en.wikipedia.org/wiki/Computer_supported_cooperative_work )

Back to channel and daily index: content-negotiated html turtle