Perl 6 - the future is here, just unevenly distributed

IRC log for #ilbot, 2015-08-20

| Channels | #ilbot index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
04:52 cfloare How ilbot is working is clear now. Thank you for such a detailed information.
05:44 cgfbot1 joined #ilbot
06:17 cgfbee joined #ilbot
06:35 cgfbee joined #ilbot
07:09 cfloare Good Morning.
07:10 cfloare A question: Is there a way to connect to the channel #Node.js ?
07:11 cfloare I think the "." is not well parsed.
07:28 cfloare Also, I would like to know what will happen if we connect on a channel with the same name on two diffrent networks as an example ? We will then have only one channel in ilbot containing both logs ? Can be imagined a way to have specified on ilbot also the network and then their corresponding channels ?
08:27 cfloare Even if not so often encountered this could be a useful improvement.
10:54 nakilon joined #ilbot
15:21 moritz cfloare: if you log the same channel in two different networks, they will show up together on a single page :(
15:22 moritz cfloare: logging them with extra meta information wouldn't be hard, but the URL schema would need to be updated to access them, and that's not something I'm willing to do right now
15:24 moritz cfloare: a single dot in the channel name should not be a problem; I log #perl.pl on magnet ( http://irclog.perlgeek.de/perl.pl/2015-08-01 )
15:25 moritz cfloare: but note that the list of channels is cached, so a new channel might take some time to show up
19:25 cfloare You are right, it took longer to show up that particular channel. And there is no real problem with the duplicates as there are practically inexistent. I only thought that this situation can possibly appear.
19:26 cfloare Thank you again. :)
20:58 * moritz should really document all that stuff, at some point

| Channels | #ilbot index | Today | | Search | Google Search | Plain-Text | summary