#coffeescript on 2011-11-08 – irclogger

00:08 hassox joined

00:16 _inc joined

00:30 negative joined

00:46 randallb joined

00:51 dguttman joined

00:53 jacobolus joined

01:04 kofel joined

01:14 phaedryx joined

01:18 jacobolus joined

01:39 pmuellr joined

01:57 ryanf joined

02:01 HT joined

02:05 sanoj joined

02:05 binarychef joined

02:09 poseid joined

02:13 piraya joined

02:18 pmuellr joined

02:23 keithpitt joined

02:23 hassox joined

02:29 toabi joined

02:31 pmuellr joined

02:32 sanoj joined

02:34 ryanf_ joined

02:55 jacobolus joined

02:57 daniel_karlsson joined

02:58 Marko__ joined

03:01 <Marko__> is it possible to deploy coffeescripts on nmpjs.org? and then require them normally on node.js apps configuring it on package.json?

03:22 jstrachan joined

03:27 kjeldahl joined

03:33 jstrachan joined

03:44 shesek joined

03:46 zmack joined

03:49 <jacobrask> Marko__: http://pkumar.github.com/10-23-2011/nodejs-module-in-coffee.html

03:53 <Marko__> jacobrask: thanks for reference, I guess thats what I'm going to do next

03:54 <jacobrask> I currently (after advice from here) have an index.js file in my package which require's coffeescript and then my coffeescript files

03:54 <jacobrask> I might switch to "preinstall" instead later

03:55 tvw joined

03:58 <Marko__> ok

03:59 <Marko__> i might need some more help later :) but need to test and try first

04:11 keithpitt joined

04:27 jstracha_ joined

04:36 jstrachan joined

04:37 TheJH_phone joined

04:47 mat_ joined

04:48 tomb| joined

04:49 lucian joined

04:51 tomb joined

04:52 _seriouslyrad joined

04:52 <_seriouslyrad> Hi guys, I know we have Cake but are there any plans to support a kind of @import statement within .coffee files to build large projects. That works great in SASS/Stylus etc...

05:12 <Industrial> _seriouslyrad: like require() ?

05:16 <_seriouslyrad> Industrial: No because require will just load another file, I want the file to actually get compiled in. So you end up with 1 JS file for your app. Seems Cake is the way to go to do that at the moment but it's not as nice as doing it from within the code

05:26 winterdj joined

05:30 zemanel joined

05:46 dubenstein joined

05:47 sanoj joined

05:48 dubenstein joined

05:52 Marko__ joined

05:53 pmuellr joined

06:03 masch joined

06:08 zdk left

06:12 angerman joined

06:23 mononofu joined

06:25 kbedell joined

06:36 tomh joined

06:36 Fofr joined

06:37 zorzar joined

06:38 cesario joined

06:40 deweysmith joined

06:44 Jarred joined

06:48 Hosh joined

06:50 zmack joined

06:51 yobi joined

06:52 jashkenas joined

06:53 upgrayeddd joined

06:54 matyr joined

06:55 etcetera joined

06:59 mattly joined

07:01 lmarburger joined

07:07 wycats joined

07:10 tanepiper joined

07:10 oal joined

07:11 RexM joined

07:16 micrypt joined

07:29 materialdesigner joined

07:41 shesek joined

07:48 KicStart42 joined

08:01 <shesek> _seriouslyrad, node-browserify uses require() calls to determines all the dependencies of a file, so it can be served as a single file to the client

08:01 <shesek> IIRC, RequireJS does that too

08:01 <KicStart42> sheesh: and a host of other file/package loading APIs do too

08:05 fracek joined

08:28 martin_sunset joined

08:44 pmuellr joined

08:52 itnomad joined

08:57 zemanel joined

08:59 winterdj joined

08:59 helloo joined

08:59 <helloo> hlo every 1

09:05 smurfke joined

09:09 tomlion joined

09:12 <CIA-39> coco: satyr master * r84e2081 / (lib/command.js src/command.co): command: global.eval - http://git.io/v4vBwA

09:13 devongovett joined

09:13 helloo left

09:18 gerard0 joined

09:23 dguttman joined

09:27 jimt joined

09:40 TheJH_phone joined

09:40 marcandre joined

09:41 kofel joined

09:49 imajes joined

09:51 cognominal_ joined

09:51 dguttman_ joined

09:58 bizniz98 joined

09:59 pmuellr joined

09:59 dubenstein left

09:59 martin_sunset joined

10:15 jedahan joined

10:17 luizlopes joined

10:22 TheJH joined

10:26 ckrailo joined

10:27 dguttman joined

10:27 sanoj joined

10:28 nofxx joined

10:32 ceej joined

10:32 Swimming_Bird joined

10:34 marcandre joined

10:38 SirFunk joined

10:41 <lucian> is coffee not compatible with node 0.6? i ger errors

10:41 <lucian> https://gist.github.com/1348095

10:41 <TheJH> lucian, works for me

10:42 Janiczek joined

10:42 <TheJH> lucian, mmhm... are you using the latest version from npm?

10:42 <lucian> yep

10:42 <toabi> lucian: you need coffee 1.1.3

10:42 <lucian> it actually worked until a few minutes ago

10:42 macmartine joined

10:44 <lucian> toabi: hmm, it's not on npm

10:44 <lucian> any reason why it would suddenly stop working?

10:45 <toabi> jeah. git clone npm and do an 'npm install -g' inside.

10:45 <toabi> maybe your code is suddenly using a feature of cs which wasn't needed before?

10:45 <TheJH> toabi, you mean, git clone coffee-script?

10:45 <toabi> euh. jeah :D

10:45 <TheJH> toabi, yes, and that feature is "pretty-print an error"

10:46 <lucian> toabi: i'd still expect an error, which i did get before

10:46 marcandre joined

10:49 <lucian> yeah, it was just a terrible error message, which is better in 1.1.3

10:49 <lucian> thanks

10:52 martin_sunset joined

10:54 mqt joined

10:57 KicStart42 left

11:03 kofel joined

11:04 malkomalko joined

11:07 dnolen joined

11:12 phaedryx joined

11:18 kofel_ joined

11:39 tilgovi joined

11:42 smathy joined

11:44 vipaca joined

11:47 mononofu joined

11:50 Swimming_Bird joined

11:52 stephank joined

11:53 jedahan joined

11:53 devongovett joined

11:55 jaequery joined

11:55 <jaequery> aloha

11:59 gauzmps joined

12:06 dguttman_ joined

12:07 nofxx joined

12:16 gregmoreno joined

12:16 sirdancealot joined

12:17 devongovett joined

12:20 cloke joined

12:24 maletor joined

12:25 badabim joined

12:26 enjalot joined

12:30 KicStart42 joined

12:31 Marko___ joined

12:32 Swimming_Bird joined

12:37 ezkl joined

12:41 cloke_ joined

12:42 cloke_ joined

12:45 gmcabrita joined

12:49 Clooth joined

12:56 chrixian joined

12:59 jstrachan joined

12:59 smurfke joined

13:00 cloke joined

13:02 adam_w joined

13:25 martin_sunset joined

13:28 dnolen_ joined

13:35 wilfredh joined

13:37 nofxx joined

13:38 jedahan joined

13:42 tilgovi joined

13:43 tazle__ joined

13:44 dropdriv1 joined

13:44 chops joined

13:46 FireFly joined

13:46 jedahan joined

13:46 vipaca joined

13:46 smathy joined

13:46 TheJH joined

13:46 jhbot joined

13:46 sstephenson joined

13:46 Dreamer3 joined

13:46 Padt joined

13:46 tectonic joined

13:46 ianl` joined

13:46 msekimura joined

13:46 mrkurt joined

13:46 jimt joined

13:46 mrkurt joined

13:47 TheJH joined

13:47 sstephenson joined

13:50 Marko___ joined

13:51 jstrachan joined

13:58 shakakai joined

14:00 travisglines joined

14:01 disnet joined

14:02 <travisglines> hey guys, the coffee-script package in the npm registry is 44 days out of date and as of node v .6 is no longer working due to the use of a depreciated api ... anyone know how we can bump the version on github into the npm registry?

14:02 badabim_ joined

14:10 <toabi> it'll probably happen when 1.1.3-pre will be stable�

14:10 kbedell joined

14:12 <travisglines> well as of right now any node developers that have upgraded to v .6 and are running their code on coffeescript ... and using npm to update packages/deploy are kind of sunk

14:13 <travisglines> hmm guess ill just clone the git repo

14:16 jacobolus joined

14:18 adam_w joined

14:21 jscheel joined

14:21 ryanf joined

14:22 ryanf left

14:24 <toabi> travisglines: jeah you can clone coffee-script and do an npm install -g in it.

14:25 chops joined

14:27 adam_w joined

14:29 marco4net joined

14:32 marcandre joined

14:36 <marco4net> hello

14:36 KicStart42 left

14:37 <marco4net> I'd like to use the debugging with node-inspector in combination with a script that restarts the server on changes

14:37 <TheJH> marco4net, is this a coffee specific question?

14:37 <TheJH> marco4net, if not, ask in #node.js, moar active people there

14:38 <marco4net> would you have a recommendation how to restart coffee on changes?

14:38 nyrb joined

14:38 <TheJH> marco4net, not sure, I think forever does that, too

14:38 <marco4net> thanks, the issue is, that I tried to use nodemon for example to restart coffee, but kill SIGUSR2 does not seem to be effective

14:39 <jaequery> whats the usage adoption rate for coffeescript?

14:39 <marco4net> that's why I thought it's more specific to coffee

14:39 <TheJH> marco4net, use SIGTERM for graceful halt and SIGKILL for killing

14:39 kjeldahl joined

14:39 kofel joined

14:40 <marco4net> ok, I'll try to update nodemon to see if that works to distinguish the 2 cases

14:40 <marco4net> thanks

14:42 blueadept` joined

14:44 dropdrive joined

14:47 indexzero joined

14:54 Stuffness joined

14:54 zemanel_ joined

15:03 malkomalko joined

15:08 toshok joined

15:17 enjalot_ joined

15:23 ylluminate joined

15:30 Swimming_Bird joined

15:40 robbrit joined

15:50 TheJH joined

15:53 TheJH_ joined

15:57 smathy joined

15:58 TheJH joined

15:58 <CIA-39> coffee-script: Jeremy Ashkenas master * r426f51d / (lib/coffee-script/coffee-script.js src/coffee-script.coffee): removing another process.binding() private snafu - http://git.io/8emHvg

15:59 robbrit left

16:00 tvw joined

16:02 ivey left

16:02 Swimming_Bird joined

16:02 TheJH joined

16:04 <CIA-39> coffee-script: Jeremy Ashkenas master * r78491b3 / (lib/coffee-script/command.js src/command.coffee): fixing relative path to jsl.conf - http://git.io/gzgDmw

16:05 negative joined

16:09 martin_sunset joined

16:13 <CIA-39> coffee-script: Jeremy Ashkenas master * rd592d2c / (lib/coffee-script/command.js src/command.coffee): Fixes #1803 -- use fs.watch instead of fs.watchFile ... more of a PITA, but hey. - http://git.io/tZ-YRQ

16:14 chops joined

16:15 itnomad joined

16:21 chops joined

16:23 matyr joined

16:37 chops joined

16:44 tauren joined

16:51 Sorella joined

16:52 jstrachan joined

16:57 TheJH joined

16:58 csnew joined

16:59 <csnew> join #jquery

17:06 naturalethic joined

17:07 TrevorBurnham joined

17:07 nofxx joined

17:10 hassox joined

17:11 <TrevorBurnham> @jashkenas Re: 1837, I'd rather do a 1.1.3 release without Windows support (no changes to command.coffee) than one that's unreliable on the Mac.

17:13 <jashkenas> trevor: if you try master, does it seem to work for you?

17:13 <jashkenas> that fs.stat bit should be a reliable way to avoid duplicates.

17:13 <jashkenas> matyr: or perhaps you can illuminate what you tested exactly?

17:17 <matyr> was using macvim to make file change

17:17 kbedell joined

17:17 <matyr> node -e 'require("fs").watch("t.js", console.log)'

17:18 keithpitt joined

17:18 <jashkenas> matyr: sure -- but did you test the new coffeescript support?

17:18 <matyr> then editing t.js gives "rename null" twice

17:18 <jashkenas> I know it's not working right.

17:18 fracek joined

17:18 <jashkenas> But we're ignoring "rename" ... and stat-ing the file.

17:18 <jashkenas> matyr: try pulling master, and then doing: bin/coffee -cw test.coffee

17:19 <matyr> yup. `coffee -pw t.coffee` spits the compilation, then do nothing after

17:19 nicksergeant joined

17:19 <jashkenas> with macvim edits ...

17:19 <jashkenas> how about a different text editor?

17:19 <matyr> let me see

17:20 <jashkenas> it prints out every time for me with TextMate, as long as a wait for a brief pause between saving.

17:20 <jashkenas> I think our mtime has a resolution to the nearest second.

17:20 <jashkenas> works for me with nano as well.

17:21 <jashkenas> Are you actually making a change, or just re-saving?

17:23 <matyr> making change

17:23 <matyr> doen't work with normal vi, emac, and TextEdit

17:24 <jashkenas> bizarre -- we're on the same version of mac os x.

17:24 poseid joined

17:24 <matyr> I used homebrew to install node 0.6.0. maybe that's making the difference?

17:25 <jashkenas> perhaps...

17:25 <jashkenas> I built from the github tag.

17:25 <jashkenas> want to try that?

17:26 <TrevorBurnham> Seems unlikely. Homebrew just runs the standard install.

17:27 <TrevorBurnham> Good news, though: I've been unable to replicate any problems with the current master. So LGTM.

17:27 <jashkenas> any ideas of what it could possibly be? is it working for you, trevor?

17:27 <jashkenas> matyr's problems make me nervous about it.

17:27 <jashkenas> we could always put out a quick patch, but...

17:27 chops joined

17:34 _inc_ joined

17:35 <TrevorBurnham> Actually, on further testing, it looks like duplicates aren't being weeded out.

17:35 <jashkenas> you can hit save once, and get two saves?

17:36 <jashkenas> any command I can reproduce?

17:36 <jashkenas> really -- I'm ready to tag and push this otherwise.

17:36 _inc joined

17:36 <TrevorBurnham> Hold up! It's definitely a problem. I'm still trying to understand what I'm seeing.

17:36 devongovett joined

17:37 <jashkenas> Sure. We've got 15 minutes to work this out, otherwise I'll hold off for another day ;)

17:37 nyrb joined

17:38 poseid joined

17:38 <TrevorBurnham> It's bizarre. If I do a save from TextMate, coffee only detects the change once; but if I do fs.writeFile (sync or async), it detects it twice. Try it.

17:38 <TrevorBurnham> I guess fs.writeFile is erasing the existing file, then writing the new contents?

17:39 <jashkenas> perhaps ..

17:39 <jashkenas> oh, and you have a build tool that uses fs.writeFile?

17:40 <jashkenas> you can change it to print out the contents of what it's writing to the console to find out.

17:40 <TrevorBurnham> Yeah, trying that now...

17:42 <TrevorBurnham> Nope, fs.writeFile isn't erasing. The contents are the same both times.

17:43 <jashkenas> and the stat.size is the same? and the stat.mtime is the same?

17:43 <jashkenas> that line should filter it out if so.

17:47 <TrevorBurnham> Ah, y'know what? I take it back. fs.writeFile is erasing. So stats.size is 0 on the first one.

17:48 <jashkenas> so then we're good?

17:48 <TrevorBurnham> But by the time fs.readFile processes, it always reads the non-empty version of the file. So the file gets read twice.

17:48 <jashkenas> makes sense.

17:48 taruti joined

17:49 <TrevorBurnham> I guess... I dunno. I don't fs.writeFile .coffee files myself. But someone must. I mean, what about that Node-based text editor, Kod?

17:51 <TrevorBurnham> Hmm, just tried in Kod, doesn't seem to cause any problem. So I'd say we're good.

17:52 <jashkenas> ok. sweet.

17:52 <jashkenas> pushing momentarily.

17:52 <TrevorBurnham> Great.

17:53 <TrevorBurnham> So you're going to note in the changelog that coffee --watch no longer works under Node 0.4.x?

17:54 <TrevorBurnham> (But that, on the plus side, it should now work with Windows?)

17:54 <jashkenas> Sure, I can do that.

17:59 brandel joined

18:00 zemanel joined

18:01 <CIA-39> coffee-script: Jeremy Ashkenas master * r3e41659 / (19 files in 9 dirs): CoffeeScript 1.1.3 - http://git.io/2txAFg

18:01 <jashkenas> boom.

18:03 <jashkenas> shit.

18:03 <jashkenas> Error: npm doesn't work with node v0.6.0

18:04 <jashkenas> how is that possible?

18:04 <TheJH> jashkenas, you have to update it

18:04 <jashkenas> whew.

18:04 <TheJH> jashkenas, you have to reinstall

18:04 <TheJH> !@jashkenas mem npm-install

18:04 <jhbot> jashkenas, you can install npm by doing "curl http://npmjs.org/install.sh | sudo sh". If you don't feel comfortable piping data from http in a sudo'ed shell (which really isn't a good idea), you can also download it, look at it and then pipe it in the shell.

18:05 <jashkenas> wow, jhbot -- what a tip.

18:05 dreinull joined

18:05 <jashkenas> boom. http://search.npmjs.org/#/coffee-script

18:05 <jashkenas> folks, give it a try from npm and let me know if it works for you.

18:05 <jhbot> jashkenas, thank you - I actually am quite intelligent :)

18:08 <brandel> yep, npm updated sucessfully. swanky

18:08 <CIA-39> coffee-script: Jeremy Ashkenas gh-pages * r2e037dc / (114 files in 14 dirs): updating gh-pages (+9 more commits...) - http://git.io/pli1TA

18:08 <jashkenas> coffeescript.org updated.

18:10 randallb joined

18:11 <CIA-39> coffee-script: Jeremy Ashkenas master * rcebfe39 / (documentation/index.html.erb index.html): change_log -> changelog - http://git.io/1ryrmw

18:11 apucacao joined

18:13 <CIA-39> coffee-script: Jeremy Ashkenas master * r74501f6 / index.html : whoops. - http://git.io/54iAJw

18:13 zmack joined

18:13 <CIA-39> coffee-script: Jeremy Ashkenas gh-pages * rcebfe39 / (documentation/index.html.erb index.html): change_log -> changelog - https://github.com/jashkenas/coffee-script/commit/cebfe394ad2e3fbd761440d4e21059b1d2a616f3

18:13 <CIA-39> coffee-script: Jeremy Ashkenas gh-pages * r74501f6 / index.html : whoops. - https://github.com/jashkenas/coffee-script/commit/74501f643cd54d7ca2d773ebe88ccd191ec79e14

18:13 <CIA-39> coffee-script: Jeremy Ashkenas gh-pages * r590bd3d / (documentation/index.html.erb index.html): Merge branch 'master' into gh-pages - http://git.io/Nsx38A

18:17 naturalethic left

18:18 w09x joined

18:19 Sorella joined

18:21 SamWhited joined

18:22 <matyr> well, I don't really use `coffee --watch` anyway. let me know if anyone's using `coco --watch` on windows

18:23 <TrevorBurnham> @jashkenas Ah, and it just occurred to me that the fs.writeFile issue I mentioned could be averted by switching the order of the `stats.size is prevStats.size` and `stats.mtime.getTime() is prevStats.mtime.getTime()` checks. *facepalm*

18:23 <jashkenas> how so?

18:23 jamescarr_ joined

18:23 <jamescarr_> why does new Date().toLocalTimeString() blow up in coffeescript!?

18:23 <TrevorBurnham> The problem was when we got two events�one with size 0, one with non-zero size�but the same mtime. The short-circuiting is undesirable there.

18:24 <TrevorBurnham> Oh, nm. *facepalm again*

18:24 <TrevorBurnham> I'm tired.

18:24 <jamescarr_> anyone?

18:25 <jamescarr_> it makes NO sense

18:25 <jamescarr_> new Date().toLocalTimeString() <-- boom

18:25 <jamescarr_> d = new Date()

18:25 <jamescarr_> d.toLocalTimeString() <-- boom

18:26 indexzero joined

18:26 <TrevorBurnham> We could cut out the size check, but then we'd *just* get the 0-size change event. Ugh.

18:26 <jamescarr_> I really wish I could understand this issue

18:27 <TrevorBurnham> @jamescarr_ That's not a CoffeeScript issue. There's no such method on Date, at least not under Node 0.6.

18:27 <jamescarr_> really? WTF

18:27 <deltab> alert new Date().toLocaleTimeString()

18:28 <jamescarr_> I'm pretty sure there is

18:28 <jamescarr_> in the node console it works

18:28 <TrevorBurnham> $ node -e "(new Date()).toLocalTimeString();"

18:28 <deltab> check the spelling

18:28 <jamescarr_> fuck

18:28 <jamescarr_> Locale

18:28 <jamescarr_> I wasted 15 minutes on this :)

18:28 <TrevorBurnham> That'll do it.

18:28 nicksergeant joined

18:31 Sorella_ joined

18:31 <TrevorBurnham> @jamescarr_ For future reference: coffee> Object.getOwnPropertyNames(Date::)

18:45 <jamescarr_> whats a good way to loop over a collection to do something and stop when a certain condition is true?

18:45 <jamescarr_> x for x in y when x == 'foo'

18:45 <jamescarr_> afaik

18:46 <jamescarr_> iterates over the whole thing

18:46 <jamescarr_> not what I want

18:46 <jamescarr_> I'm looking for the first element that meets condition y, pass it to a callback and stop iterating

18:46 <jamescarr_> because the array can possibly be extremely large

18:48 <jamescarr_> nvm

18:51 devongovett joined

18:54 WillMarshall joined

18:54 dancingturtle joined

19:09 CornflakesForTea joined

19:21 enjalot joined

19:22 adam_w joined

19:24 Zamarok joined

19:26 nicksergeant joined

19:31 tomlion joined

19:43 jedahan joined

19:43 indexzero joined

19:47 esparkman joined

19:52 juandg joined

20:09 shesek joined

20:14 dnolen joined

20:15 phaedryx joined

20:15 gavin_huang joined

20:17 materialdesigner joined

20:19 indexzero joined

20:24 esundahl joined

20:28 nicksergeant joined

20:30 yllox joined

20:36 sirdancealot joined

20:39 esundahl joined

20:40 hadees joined

20:41 der| joined

20:41 <der|> Hello! I'm new to coffeescript and I've got to say that I'm loving it so far! Thank you so much for creating this :D

20:41 vipaca joined

20:57 _inc_ joined

20:59 _inc joined

20:59 tvw joined

21:02 nicksergeant joined

21:05 toshok joined

21:06 tomlion joined

21:10 tomlion_ joined

21:14 ylluminate joined

21:18 tomlion joined

21:21 zdk joined

21:21 ceej joined

21:24 tomlion_ joined

21:25 cloke_ joined

21:30 ckrailo joined

21:38 ryanf joined

21:58 angerman_ joined

21:59 adam_w left

22:01 devongovett joined

22:04 phaedryx joined

22:06 imajes joined

22:23 cognominal joined

22:24 cognominal joined

22:26 <CIA-39> coffee-script: Michael Ficarra master * r11544f2 / (extras/coffee-script.js src/browser.coffee): fixes #1832: speed up `CoffeeScript.eval` in browser script - http://git.io/LU_8ew

22:26 <CIA-39> coffee-script: Jeremy Ashkenas master * r97d1eed / (extras/coffee-script.js src/browser.coffee):

22:26 <CIA-39> coffee-script: Merge pull request #1839 from michaelficarra/issue1832

22:26 <CIA-39> coffee-script: fixes #1832: speed up `CoffeeScript.eval` in browser script - http://git.io/5nmzsw

22:27 frankz_ joined

22:29 inimino joined

22:32 sanoj joined

22:37 airhorns joined

22:38 <airhorns> jashkenas, i just finished bisecting, i'll report my results

22:40 <airhorns> jashkenas this is the little guy that did it: https://github.com/Shopify/batman/commit/2256a36e32e0d0763b33edeff2e0165923175935#L1L2957

22:41 <airhorns> would you like me to file an issue?

22:42 mat_ joined

22:49 <jashkenas> yes, please.

22:56 sanoj joined

22:56 dnolen joined

23:03 jacobolus joined

23:03 gavin_huang joined

23:04 <airhorns> done, awesome work on 1.1.3 jashkenas, thanks for all your hard work!

23:05 <jashkenas> thanks to the people who actually patched -- I hardly touched it ;)

23:08 <devongovett> jashkenas: any reason CoffeeScript doesn't preserve non block comments?

23:08 <jashkenas> yes, it's very difficult to parse

23:08 smathy joined

23:08 <devongovett> hmmm

23:19 disnet joined

23:20 jdpacker joined

23:24 badabim joined

23:36 Somix joined

23:41 jazzy_ joined

23:41 dguttman joined

23:55 macmartine joined

23:57 dguttman joined

23:57 esundahl joined