Logs for jdev

Show join/part/nick changes:

[00:02:36] * Tobias left the chat.
[00:02:43] * Zash left the chat.
[00:20:50] * deryni joined the chat.
[00:25:35] * smoku left the chat.
[00:46:44] * hawke left the chat.
[01:19:51] * evilotto left the chat.
[01:45:09] * whatever left the chat.
[01:45:09] * whatever joined the chat.
[01:46:26] * whatever left the chat.
[01:46:26] * whatever joined the chat.
[01:47:27] * whatever left the chat.
[01:47:27] * whatever joined the chat.
[02:17:51] * whatever left the chat.
[02:17:51] * whatever joined the chat.
[02:29:53] * whatever left the chat.
[02:29:53] * whatever joined the chat.
[03:01:38] * Zash joined the chat.
[04:05:07] * Yagiza joined the chat.
[04:05:26] <Yagiza> Hello every1!
[04:06:07] <Zash> 'lo
[04:06:44] <Yagiza> Zash!
[04:07:00] <Zash> ?!
[04:07:15] <Yagiza> Just a greeting
[04:07:42] <Zash> Ok :)
[04:08:51] <Yagiza> 'bout XEP-0047 and XEP-0066...
[04:09:14] <darkrain> [xep 47]
[04:09:16] <darkrain> [xep 66]
[04:09:18] <darkrain> Bah
[04:09:30] <Zash> HAL!
[04:09:50] <darkrain> Yagiza: People don't really use OOB anymore (AFAIK)
[04:10:03] <Yagiza> Can any1 tell me if those XEPs shoud be used only together with XEP-0095 or standalone?
[04:10:23] * mupp joined the chat.
[04:10:27] <Zash> mupp: xep 47
[04:10:28] <mupp> Zash: XEP-0047: In-Band Bytestreams is Standards Track (Draft, 2009-03-17) See: http://xmpp.org/extensions/xep-0047.html
[04:10:31] <Zash> mupp: xep 66
[04:10:31] <mupp> Zash: XEP-0066: Out of Band Data is Standards Track (Draft, 2006-08-16) See: http://xmpp.org/extensions/xep-0066.html
[04:10:36] <Zash> mupp: xep 95
[04:10:36] <mupp> Zash: XEP-0095: Stream Initiation is Standards Track (Draft, 2004-04-13) See: http://xmpp.org/extensions/xep-0095.html
[04:11:10] <Yagiza> May I send
[04:11:14] <Yagiza> <iq from='romeo@montague.net/orchard' id='jn3h8g65' to='juliet@capulet.com/balcony' type='set'> <open xmlns='http://jabber.org/protocol/ibb' block-size='4096' sid='i781hf64' stanza='iq'/> </iq>
[04:11:34] <Yagiza> Without initiating session via XEP-0095?
[04:11:40] <darkrain> Generally no
[04:12:01] <Yagiza> Oh, IC
[04:12:06] <darkrain> The other side won't know what to do with this IBB without some sort of signalling (i.e. Stream Initiation) about what it's for
[04:12:28] <darkrain> mup: xep jingle file transfer
[04:12:35] <darkrain> Zash: ... :(
[04:12:52] <Zash> !xep jingle file trans
[04:12:52] <mupp> Zash: XEP-0234: Jingle File Transfer is Standards Track (Experimental, 2010-02-19) See: http://xmpp.org/extensions/xep-0234.html
[04:13:12] <Yagiza> And what about
[04:13:16] <Yagiza> <iq type='set' from='stpeter@jabber.org/work' to='MaineBoy@jabber.org/home' id='oob1'> <query xmlns='jabber:iq:oob'> <url>http://www.jabber.org/images/psa-license.jpg</url> <desc>A license to Jabber!</desc> </query> </iq>
[04:13:21] <Yagiza> ?
[04:13:35] <Zash> >darkrain: Yagiza: People don't really use OOB anymore (AFAIK)
[04:13:44] <Yagiza> Here we have a link and we know what to do with it.
[04:13:53] <darkrain> Zash: Oh, whoops. I can't type.
[04:14:04] <Yagiza> Why not?
[04:14:13] <Zash> !xep jingle
[04:14:13] <mupp> Zash: Multiple matches: XEP-0247: Jingle XML Streams, XEP-0234: Jingle File Transfer, XEP-0176: Jingle ICE-UDP Transport Method, XEP-0183: Jingle Telepathy Transport, XEP-0181: Jingle DTMF, XEP-0261: Jingle In-Band Bytestreams Transport Method, 14 more
[04:15:01] <Zash> Is there any client supporting OOB?
[04:15:01] <darkrain> Yagiza: Because it generally doesn't allow two clients to transfer a file between them, since it requires the file be hosted on some service
[04:15:11] <Yagiza> It's a draft standard, so it its implementation is encouraged
[04:15:45] <darkrain> Zash: libpurple has code for it. I believe, in theory, one can trigger said code. I've never seen anyone do so (it's been there since before I got involved).
[04:15:54] <Zash> Last Updated: 2006-08-16
[04:16:09] <Zash> on '66
[04:16:41] <Zash> But, if you do a client today, you should probably look at Jingle
[04:16:41] <Yagiza> Yes, but if I don't wanna to spend my traffic and just want to send a link and ensure the other side downloaded it.
[04:16:52] <darkrain> How can you "ensure the other side downloaded it"?
[04:17:52] <Yagiza> I'll wait for <iq type='reply' /> from it.
[04:18:03] <Zash> It could just send that anyways
[04:18:06] <Yagiza> result
[04:18:28] <Zash> or rather type=error unsupported-something
[04:18:37] <Yagiza> Yes
[04:19:01] <Yagiza> I just wanna know if he downloaded my link or not.
[04:19:31] <Yagiza> And let's forget about cheating clients.
[04:19:58] <darkrain> Shall we also forget that I don't think it's widely deployed?
[04:21:04] <Yagiza> That's not my problem. If we won't implement features, which are not widely deployed, no new features will be implemented at all!
[04:22:20] <Zash> !xep user browsing
[04:22:20] <mupp> Zash: XEP-0195: User Browsing is Standards Track (Deferred, 2008-09-25) See: http://xmpp.org/extensions/xep-0195.html
[04:23:45] <Zash> And it's way easier to just send the link in the body of a normal <message type=chat>
[04:24:53] <darkrain> Yagiza: Let's try this: what are you actually trying to do?
[04:26:40] <Yagiza> I'm just looking for a best way of implementing XEP-0066 in my client.
[04:26:58] <Yagiza> Now, it implemented as a standalone XEP
[04:27:05] <darkrain> At a higher level, what's the use case?
[04:27:21] <Yagiza> I'm thinking about its implementation as SI method.
[04:27:42] <darkrain> It's not really written with that in mind
[04:27:47] <darkrain> Have you looked at [XEP 65]?
[04:27:49] <darkrain> !xep 65
[04:27:50] <mupp> darkrain: XEP-0065: SOCKS5 Bytestreams is Standards Track (Draft, in progress, last updated 2010-03-15) See: http://xmpp.org/extensions/xep-0065.html
[04:28:07] <darkrain> Zash: Feature request: support for []? :)
[04:28:19] <Zash> [xep 9999]
[04:28:19] <mupp> Zash: Sorry, I don't think there is a XEP-9999
[04:28:30] <darkrain> Bah, is it case sensitive? [xep 65]
[04:28:30] <mupp> darkrain: XEP-0065: SOCKS5 Bytestreams is Standards Track (Draft, in progress, last updated 2010-03-15) See: http://xmpp.org/extensions/xep-0065.html
[04:28:31] <Yagiza> I can't type so fast: I'm using a laptop with broken keyboard!
[04:28:34] <darkrain> Zash: Nevermind :(
[04:29:14] <Yagiza> And now, 'bout your question...
[04:29:17] <darkrain> Yagiza: If you're looking at the way forward, I strongly suggest you look at the Jingle File Transfer spec.
[04:29:33] <Yagiza> This is also in my plans
[04:30:33] <Yagiza> I just wanna let user a way to exchange links and operate them using file thransfer mechanism.
[04:32:06] <Yagiza> If i'm sending a link in the message, most of clients will open a browser, e-mail client or let system process thelink some othe way.
[04:33:40] <Yagiza> When we send link via OOB, the file will be downloaded via internal download manager of the client and other side will be notyfied about success or error.
[04:33:58] <darkrain> It doesn't look to me like xep-0066 supports being wrapped up in Stream Initiation.
[04:34:25] <Yagiza> <iq type='set' id='offer1' to='receiver@jabber.org/resource'> <si xmlns='http://jabber.org/protocol/si' id='a0' mime-type='text/plain' profile='http://jabber.org/protocol/si/profile/file-transfer'> <file xmlns='http://jabber.org/protocol/si/profile/file-transfer' name='test.txt' size='1022'> <desc>This is info about the file.</desc> </file> <feature xmlns='http://jabber.org/protocol/feature-neg'> <x xmlns='jabber:x:data' type='form'> <field var='stream-method' type='list-single'> <option><value>http://jabber.org/protocol/bytestreams</value></option> <option><value>jabber:iq:oob</value></option> <option><value>http://jabber.org/protocol/ibb</value></option> </field> </x> </feature> </si> </iq>
[04:35:06] <Yagiza> It's an example 3 fromXEP-0095
[04:35:28] <Zash> Kev: Wishlist, mod_pastebin
[04:35:37] <Zash> !xep 95 ex 3
[04:35:38] <mupp> Zash: http://xmpp.org/extensions/xep-0095.html#example-3
[04:35:39] <darkrain> I stand corrected, but I still don't actually know of anyone who uses it
[04:36:00] <darkrain> (peer-to-peer is generally where client file transfer is targeted)
[04:36:55] <Zash> Spectrum does something when a normal file transfer fails, like putting it in a web-accesible dir and then sends a link.
[04:37:08] <darkrain> I think it sends it in a <message/>, though
[04:37:37] <Zash> (OT: And it won't let me chgrp or chmod the dir so the httpd can read it :/ )
[04:37:52] <darkrain> Hahaha, spectrum or spectrumctl?
[04:38:11] <Zash> later
[04:38:18] <darkrain> Bug mati
[04:38:25] <Yagiza> Well...
[04:40:01] <Yagiza> There are some benefits in using OOB, so I don't thinkitshould be ignored just because it is not implemented in most clients.
[04:42:46] <darkrain> So at a high level, what's your user case?
[04:43:47] <Yagiza> Ok
[04:44:04] <Yagiza> Here's the situation
[04:44:26] <Yagiza> I wanna send a file to a user.
[04:45:07] <Yagiza> Both, me and him are using Mobile J2ME clients.
[04:45:39] <darkrain> So the file is on your phone? Or it's out on some HTTP server?
[04:46:08] <Yagiza> Both. But my 3G traffic is too expesive, so I don't wanna send it to him directly.
[04:46:40] <Yagiza> But I knowan internet link where the file could be obtained.
[04:47:15] <darkrain> You care about your 3G traffic, but not his?
[04:48:14] <Yagiza> Yes. He's the one, who needs the file. So, why Ishould spend my money sending the file to him?
[04:48:30] <Yagiza> If I'll send him a link in the message, his client will try to open it in the system.
[04:49:44] <Yagiza> But he has an ordinary mobile phone (not a smartphone or communicator), so his device cannot run thwo applications at once.
[04:50:46] <darkrain> Then yes, OOB might make sense.
[04:51:23] <Yagiza> (^_^)
[04:59:59] <darkrain> :)
[05:01:16] <Zash> mupp: leave damn it!
[05:01:16] <mupp> Zash: You can't tell me what to do!
[05:01:36] <Zash> >:(
[05:01:39] * mupp left the chat.
[05:03:13] <darkrain> Haha
[05:03:51] <Yagiza> That was awesome! (^_~)b
[05:18:54] * petermount joined the chat.
[05:19:07] * petermount left the chat.
[05:41:23] * teo1 left the chat.
[05:41:24] * teo1 joined the chat.
[06:25:18] <Yagiza> http://xmpp.org/extensions/xep-0065.html#example-9
[06:28:11] <Yagiza> Looks like in examples 9 and 10 "to" and "from" addresses are mixed up.
[07:00:11] * smoku joined the chat.
[07:01:21] * jonas joined the chat.
[07:22:15] * mlundblad_laptop joined the chat.
[07:33:23] * mlundblad_laptop left the chat.
[07:38:03] * jonas left the chat.
[07:48:48] * nabatt joined the chat.
[08:03:55] * jonas joined the chat.
[08:38:46] * dwd joined the chat.
[08:41:25] * ermine joined the chat.
[08:42:02] * mlundblad_laptop joined the chat.
[08:47:22] * teo1 left the chat.
[08:47:23] * teo1 joined the chat.
[08:47:53] * Treebilou left the chat.
[09:13:19] * Zash left the chat.
[09:13:42] * Zash joined the chat.
[09:34:08] * luca tagliaferri joined the chat.
[09:35:46] * alfeberlin left the chat.
[09:55:12] * Treebilou joined the chat.
[09:57:43] * petermount joined the chat.
[09:58:19] * alfeberlin joined the chat.
[09:58:26] * alfeberlin left the chat.
[11:25:54] * Kev left the chat.
[11:44:25] * Treebilou left the chat.
[11:55:30] * Yagiza left the chat.
[11:56:47] * alfeberlin left the chat.
[12:00:45] * alfeberlin joined the chat.
[12:01:01] * alfeberlin left the chat.
[12:02:32] * luca tagliaferri left the chat.
[12:31:46] * whatever left the chat.
[12:31:46] * whatever joined the chat.
[12:32:44] * whatever left the chat.
[12:32:44] * whatever joined the chat.
[12:45:47] * whatever left the chat.
[12:45:47] * whatever joined the chat.
[12:55:52] * alfeberlin joined the chat.
[12:58:11] * Kev joined the chat.
[13:04:11] * Zash left the chat.
[13:05:15] * whatever left the chat.
[13:05:16] * whatever joined the chat.
[13:06:17] * whatever left the chat.
[13:06:18] * whatever joined the chat.
[13:32:59] * whatever left the chat.
[13:32:59] * whatever joined the chat.
[13:56:55] * whatever left the chat.
[13:56:55] * whatever joined the chat.
[13:57:03] * smoku left the chat.
[13:57:05] * smoku joined the chat.
[13:59:03] * alfeberlin left the chat.
[14:08:56] * whatever left the chat.
[14:08:56] * whatever joined the chat.
[14:18:12] * whatever left the chat.
[14:18:12] * whatever joined the chat.
[14:18:58] * louiz’ joined the chat.
[14:26:56] * mlundblad_laptop left the chat.
[14:27:18] * mlundblad_laptop joined the chat.
[14:30:55] * hawke joined the chat.
[14:37:33] * alfeberlin joined the chat.
[14:37:42] * alfeberlin left the chat.
[14:42:09] * whatever left the chat.
[14:42:09] * whatever joined the chat.
[14:42:11] * luca tagliaferri joined the chat.
[14:50:40] * scippio joined the chat.
[14:50:51] * luca tagliaferri left the chat.
[14:55:12] * whatever left the chat.
[14:55:13] * whatever joined the chat.
[15:03:43] * jonas left the chat.
[15:09:14] * luca tagliaferri joined the chat.
[15:09:32] * deryni left the chat.
[15:19:43] * Treebilou joined the chat.
[15:20:26] * Treebilou left the chat.
[15:20:47] * luca tagliaferri left the chat.
[15:21:07] * Treebilou joined the chat.
[15:42:41] * smoku left the chat.
[15:42:42] * smoku joined the chat.
[15:44:07] * luca tagliaferri joined the chat.
[15:55:48] * whatever left the chat.
[15:55:48] * whatever joined the chat.
[15:57:41] * alfeberlin joined the chat.
[15:57:48] * alfeberlin left the chat.
[15:58:26] * nabatt left the chat.
[15:58:45] * smoku left the chat.
[16:06:59] * deryni joined the chat.
[16:09:56] * mlundblad_laptop left the chat.
[16:18:53] * Neustradamus joined the chat.
[16:19:36] * Florob joined the chat.
[16:20:07] * luca tagliaferri joined the chat.
[16:22:30] * whatever left the chat.
[16:22:30] * whatever joined the chat.
[16:22:55] * tofu left the chat.
[16:23:00] * tofu joined the chat.
[16:28:18] * tofu left the chat.
[16:28:21] * tofu joined the chat.
[16:34:31] * whatever left the chat.
[16:34:31] * whatever joined the chat.
[16:38:35] * luca tagliaferri left the chat.
[16:50:57] * Tobias joined the chat.
[16:56:40] * whatever left the chat.
[16:56:40] * whatever joined the chat.
[17:00:42] * teo1 left the chat.
[17:04:32] * luca tagliaferri joined the chat.
[17:10:18] * jonas joined the chat.
[17:11:23] * whatever left the chat.
[17:11:23] * whatever joined the chat.
[17:12:16] * luca tagliaferri left the chat.
[17:18:04] * stpeter joined the chat.
[17:21:22] * evilotto joined the chat.
[17:22:29] * whatever left the chat.
[17:22:30] * whatever joined the chat.
[17:34:31] * whatever left the chat.
[17:34:31] * whatever joined the chat.
[17:40:43] * waqas joined the chat.
[17:43:53] * whatever left the chat.
[17:43:53] * whatever joined the chat.
[17:45:09] <waqas> stpeter: The "re-scope" text only talks about jabber:client and jabber:server. I'm taking it to mean it applies for any content namespace (e.g., jabber:component:accept).
[17:46:06] * naw joined the chat.
[17:53:26] * teo1 joined the chat.
[17:54:19] <stpeter> yes, I would take it that way -- we don't talk about component connections in the RFCs, but we should add a few sentences about this to the component XEPs
[17:54:54] <stpeter> I could add a mention of the component XEPs to that paragraph in 3920bis
[17:55:55] * whatever left the chat.
[17:55:55] * whatever joined the chat.
[17:59:20] <waqas> By the way, we (and others) happen to treat the BOSH namespace the same way, as some (most?) BOSH clients don't bother adding xmlns='jabber:client'.
[17:59:44] <stpeter> true
[18:01:11] <stpeter> /me adds a sentence to 3920bis
[18:03:30] * luca tagliaferri joined the chat.
[18:07:06] * whatever left the chat.
[18:07:31] <stpeter> text: Finally, server implementers are advised to apply stanza re-scoping to other stream connection methods and alternative XMPP connection methods, such as those specified in [XEP-0124], [XEP-0206], [XEP-0114], and [XEP-0225].
[18:07:48] * whatever joined the chat.
[18:08:57] * whatever left the chat.
[18:08:58] * whatever joined the chat.
[18:10:45] * luca tagliaferri left the chat.
[18:11:08] <waqas> Works for me
[18:11:29] <stpeter> thanks
[18:11:59] <waqas> Thanks :)
[18:12:38] <stpeter> /me can't wait to be done with these documents :)
[18:13:27] * petermount left the chat.
[18:20:59] * whatever left the chat.
[18:20:59] * whatever joined the chat.
[18:24:16] * whatever left the chat.
[18:50:57] * naw left the chat.
[19:01:33] * Zash joined the chat.
[19:01:35] * petermount joined the chat.
[19:02:12] * petermount left the chat.
[19:21:36] * jcea joined the chat.
[19:25:05] <waqas> stpeter: http://gitorious.org/xmpp
[19:25:51] * Asterix left the chat.
[19:26:12] * Asterix joined the chat.
[19:35:25] * waqas left the chat.
[19:39:54] <stpeter> yep, I need to update http://xmpp.org/xsf/sourcecontrol.shtml or even move that page to the new user interface and put a redirect in place
[19:46:56] * mlundblad joined the chat.
[19:53:56] <Zash> .
[19:54:20] <Zash> ~$ openssl s_client -CApath /etc/ssl/certs/ca-certificates.crt -connect hermes.jabber.org:5222 -starttls xmpp CONNECTED(00000003) ~$
[19:54:25] <Zash> um, whats up
[19:54:43] <darkrain_> s/hermes\.//
[19:55:08] <Zash> why does dns say it's hermes then ^^
[19:55:36] <darkrain_> They're the same host (which I happen to "just know")
[19:56:02] <darkrain_> The issue is that openssl uses the connect hostname there as the to attribute on the opening stream
[19:56:13] <darkrain_> and M-Link (and Prosody) throw back a "We don't serve that host, go away"
[19:56:33] <darkrain_> (and openssl s_client doesn't support SRV lookups AFAIK)
[19:56:50] <Zash> hm, can you supply a diffrent name for the stream?
[19:57:38] <Kev> darkrain_: It's not, in fact, the same machine - there's port forwarding at work from the web server.
[19:58:04] <darkrain_> Oops, I stand corrected :)
[19:58:21] * wiretap joined the chat.
[19:59:34] <darkrain_> Kev: Eww :)
[20:00:31] <Kev> No doubt.
[20:00:48] <Kev> There are still lots of broken clients out there, though - and there were far more back when hermes was commissioned.
[20:01:02] <darkrain_> Zash: I've never found a way to
[20:03:09] <stpeter> /me disappears while taking another deep dive into Unicode normalization and related topics
[20:03:55] <Zash> stpeter: sounds painful
[20:04:13] <stpeter> Zash: feel free to follow along at home :)
[20:05:20] <stpeter> http://tools.ietf.org/html/rfc5895 and http://www.unicode.org/reports/tr46/ and http://www.unicode.org/reports/tr15/ -- oh my!
[20:05:41] <Zash> s/[^a-zA-Z0-9._-]//g, done. \o/
[20:07:03] <stpeter> if only :)
[20:07:19] <stpeter> /me slides his computer off to the side and reads this stuff on paper (!)
[20:34:14] * hawke left the chat.
[20:34:16] * hawke joined the chat.
[20:34:21] * duck1123 joined the chat.
[20:43:57] * Tobias left the chat.
[20:44:23] <dwd> Zash, Just replacing one character, right?
[20:44:59] <Zash> dwd: g
[20:45:18] <Zash> as in global
[20:46:02] <dwd> Zash, Ah, right. I slouch corrected.
[20:46:13] <Zash> :)
[20:47:38] <dwd> I love getting patches to review that state "Unit tests pass. Except for the XYZ ones, which is probably unrelated."
[20:48:11] <dwd> "pass" in this case being, presumably, the American spelling of "fail".
[20:50:05] * Tobias joined the chat.
[20:50:10] <Kev> Which is the same as the English spelling of "fail", but without the 'u'
[20:50:46] <dwd> stpeter, [Or anyone else who knows] How would one do the XEP equivalent of an informative appendix? Just sling in an informational section, or should I consider some alternative (like a whole separate XEP)?
[20:51:11] <Kev> We have done a protocol and an informational XEP pair before.
[20:51:48] <dwd> The case I have is a standards-track protocol proposal, with an existing largely undocumented close relative.
[20:52:29] <dwd> What I'd like to do is say "Here's my standards-track proposal, and by the way, there's this existing implementation which you might encounter which works like this".
[20:53:33] <Kev> That's historical then, not informational.
[20:54:02] <dwd> True. So an historical appendix/section/something.
[20:54:22] <Kev> Historical other XEP, I think.
[20:54:52] <dwd> OK. So two XEPs. I suppose it'll keep my count up.
[20:57:11] <Zash> "Most XEPs written when we hit XEP-9999 wins" ?
[20:57:40] <dwd> Zash, Nah. stpeter has too big a head-start.
[20:58:00] <dwd> Zash, Although I've been catching up the past few.
[20:59:24] <Zash> :D
[20:59:25] <dwd> Zash, But number of RFC/XEPs does seem to have a direct relationship to seniority and independence at Isode. After all, the guy with the most is still the CEO.
[21:00:04] <dwd> [Actually I'm not sure that's true anymore - I suspect Alexey overtook some time back]
[21:00:43] <Zash> Aiming for a promotion perhaps? ;)
[21:04:48] * Tobias left the chat.
[21:09:41] * Tobias joined the chat.
[21:13:29] * naw joined the chat.
[21:29:03] * RiaGuy joined the chat.
[21:30:58] * Treebilou left the chat.
[21:32:25] <stpeter> /me stops reading IDNA documents to keep from falling asleep
[21:33:59] <johnny> hmm... stpeter.. maybe one day'll you'll write some poetry and songs about your xmpp journey
[21:35:57] * Neustradamus left the chat.
[21:38:09] <dwd> stpeter, You don't want to fall asleep reading IDNA documents. You'll have nightmares about indic numeral grapheme equivalences.
[21:38:49] <deryni> I think I'm going to have nightmares just from having read that phrase.
[21:39:47] * naw left the chat.
[21:40:20] <dwd> deryni, I don't actually know what it means. But it's the kinds of thing I heard when briefly looking in on the IDNA2008 work.
[21:41:02] <deryni> I think I'm mostly afraid that I may actually have understood what it means.
[21:41:18] <dwd> Well. I know what indic numerals are. Just not what a grapheme is, and whether it can have an equivalence.
[21:44:52] * RiaGuy left the chat.
[21:45:36] <Florob> hmm... full hard-drives are fun. I didn't even get to see that phrase. ('til looking at the http logs)
[21:46:28] <dwd> Not even `cat wafer-thin-mint >/dev/sda1` ?
[21:52:53] <dwd> Okay, so now I know what a grapheme is, and it can have equivalences. Moreover, thanks to allography, it can even have different forms. Yay.
[21:53:56] <Zash> dwd: Now you *will* have nightmares about it?
[21:57:19] <dwd> Zash, On the plus side, it'll stop those disturbing dreams about Bloom filters.
[21:59:02] <Zash> Oh, yeah, those are pretty scary
[22:06:41] <Zash> dwd: http://www.vgcats.com/comics/?strip_id=222
[22:17:42] <dwd> Zash, Ah. Wrong kind of bloom.
[22:18:17] <dwd> Zash, Bloom filters are to do with eliding lookups via mind-bending application of hashes.
[22:21:01] <Zash> "which just so happens to look like that if you run an image through it"
[22:21:03] * deryni left the chat.
[22:23:35] * hawke left the chat.
[22:42:00] * ermine left the chat.
[22:58:32] * jonas left the chat.
[22:59:48] * johnny left the chat.
[23:02:20] * Florob left the chat.
[23:02:37] * Florob joined the chat.
[23:11:29] * stpeter left the chat.
[23:17:59] * mlundblad left the chat.
[23:20:25] * johnny joined the chat.
[23:34:18] * Zash left the chat.
[23:51:56] * Tobias left the chat.
[23:54:18] * deryni joined the chat.