| 00:05.47 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 00:38.30 | *** join/#qi-hardware cladamw (~Adam@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 00:57.03 | *** join/#qi-hardware dvdk (~dvdkhlng@g225034252.adsl.alicedsl.de) |
| 00:59.29 | dvdk | is going to look into octave compilation failures, if nobody else has done so yet |
| 01:16.06 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 01:16.56 | wolfspraul | that'd be great, I think nobody got to that yet |
| 01:20.44 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 01:29.22 | dvdk | looks like C++ incompatabilities with latest compiler. hmm, if even octave people can'tmake c++ compilers happy :/ |
| 01:29.48 | dvdk | this will take time. another recompile, another 30 minutes. time to reactivate ccache. |
| 01:36.18 | wpwrak | (c++) Bjarne Stroustrup, the Marquis de Sade of the computer age ;-) |
| 01:37.22 | *** join/#qi-hardware zrafa (~rafa@190.14.174.29) |
| 01:50.26 | *** join/#qi-hardware dvdk (~dvdkhlng@g225033017.adsl.alicedsl.de) |
| 01:58.07 | *** join/#qi-hardware uwe_ (~uwe_@dslb-088-066-186-052.pools.arcor-ip.net) |
| 02:02.41 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 02:03.59 | *** join/#qi-hardware Jay7x (jay@2.92.212.41) |
| 02:07.09 | whitequark | wpwrak: did you know that while |
| 02:07.18 | whitequark | Class *klass = new Class; and |
| 02:07.27 | whitequark | Class *klass = new Class(); are the same, |
| 02:07.34 | whitequark | Class klass; and |
| 02:07.40 | whitequark | Class klass(); are completely different things? |
| 02:07.46 | whitequark | the latter, er |
| 02:07.50 | whitequark | I'm not completely sure |
| 02:07.57 | whitequark | but I think it calls static operator() or something like that |
| 02:08.26 | whitequark | don't ask me what the hell will it try to do with the return value; I don't know. |
| 02:09.12 | dvdk | whitequark: no. the latter is interpreted as a function prototype for function 'klass' with return value 'Class' (such as 'int main()'). |
| 02:09.30 | dvdk | see the C++ FQA (frequently questioned answers) for more reasons to hate C++ |
| 02:10.21 | wpwrak | ;-)) |
| 02:10.27 | whitequark | yeah, I've read that |
| 02:10.42 | whitequark | but that particular quirk I have encountered myself |
| 02:10.43 | dvdk | btw just having fun with C++ compiler issues of our openwrt octave package |
| 02:10.55 | whitequark | and it took me several fucking hours to understand what it doesn't like |
| 02:11.29 | whitequark | unfortunately, Qt is too good to not use it |
| 02:11.36 | whitequark | and it's the main reason to use C++ in 2012 |
| 02:13.30 | whitequark | wolfspraul: oh, about my package you're (I hope) just going to send me |
| 02:13.31 | wpwrak | gtk doesn't need any of that ... :) |
| 02:13.58 | whitequark | I just found out that I have lost all of my UBBs while not-so-smooth relocating, so I need some again |
| 02:14.21 | dvdk | wpwrak: but gtk+ (signals?) won't compile with (older) M$ compilers :) |
| 02:14.39 | wpwrak | i think they're still at tuxbrain HQ. but maybe wolfgang is acquiring them, too |
| 02:14.44 | dvdk | whitequark: still have a few left |
| 02:14.50 | whitequark | wpwrak: gtk2 is crap because it was coded without much thinking. gtk3 is crap because its UI was designed without thinking. |
| 02:15.04 | dvdk | (ubbs: #4) |
| 02:15.11 | *** join/#qi-hardware orsonzhai (~zhai@1.202.15.210) |
| 02:15.33 | wpwrak | dvdk: where are so many thing that won't work on windows, what's one more ? ;-) |
| 02:15.53 | whitequark | dvdk: well, I'll wait for wolfspraul to reply, I think. but thanks for the offer |
| 02:15.55 | dvdk | hey, octave finally compiled |
| 02:15.57 | wpwrak | whitequark: gtk2 works for me :) |
| 02:16.20 | whitequark | wpwrak: well, I somewhat like gtk2, in the sense that it has a lot of good apps. pidgin, for example. some more. |
| 02:16.26 | whitequark | but it really wasn't architected |
| 02:16.33 | whitequark | just written as it was going |
| 02:17.05 | wpwrak | natural, organic growth :) |
| 02:17.07 | whitequark | because of exactly same reason Linux had to be refactored so many times no one even remembers that |
| 02:17.27 | whitequark | and we, for example, still do not have true AIO like Windows has |
| 02:17.41 | whitequark | (yes, 2.6 has AIO without threads. it does not work with disk caches.) |
| 02:18.16 | wpwrak | how does AIO fail with disk caches ? |
| 02:18.23 | whitequark | it bypasses them. |
| 02:18.46 | whitequark | i.e. you can use AIO and it will be true AIO, but you will fetch the data from disk each time |
| 02:18.56 | dvdk | whitequark: select() is all the AIO i'll ever need :) |
| 02:19.03 | whitequark | dvdk: doesn't scale |
| 02:19.24 | dvdk | everybody tells that but I hardly ever see a case where select() hits a problem |
| 02:19.30 | whitequark | dvdk: C10k |
| 02:20.20 | whitequark | well, select() doesn't support more than maybe 4k of file descriptors (a compile time constant, grep it in your /usr/include), and with those 4k it isn't very performant |
| 02:20.30 | wpwrak | (disk caches) hmm, i have a few doubts about your statement, at least in such a general form. but i'm too lazy to look things up :) |
| 02:20.48 | whitequark | wpwrak: I will. there's an ages old thread on lkml and even a patch |
| 02:20.51 | whitequark | which was never merged |
| 02:21.28 | whitequark | I was once caught in a flamewar about Linux AIO and researched that stuff for a week |
| 02:21.33 | whitequark | now I know way more than I want to |
| 02:21.36 | wpwrak | ;-) |
| 02:21.47 | wpwrak | why was the patch not merged ? |
| 02:21.58 | whitequark | usual bureaucracy? |
| 02:22.05 | wpwrak | try harder :) |
| 02:22.18 | whitequark | not everyone wants/has time to |
| 02:22.43 | whitequark | and this is a vicious circle |
| 02:23.04 | whitequark | no one uses AIO on linux because it's broken, and no one works on support for it because it isn't used much |
| 02:23.24 | whitequark | I can remember only of a single app which uses aio, nginx, and I never really seen an env where it was enabled |
| 02:25.31 | qi-bot | [commit] David Kühling: octave: fix compilation with latest openwrt toolchain (master) http://qi-hw.com/p/openwrt-packages/51287e2 |
| 02:25.37 | wpwrak | so perhaps there's simply not enough of an itch :) |
| 02:26.17 | wolfspraul | I don't have the UBBs, unfortunately |
| 02:26.45 | wolfspraul | I forgot to ask David when he sent me the atben/atusb, and I have no better way to reach him than anybody else |
| 02:27.19 | wpwrak | btw, i rarely found getting stuff that ready for mainline into mainline a problem. the problem people hit most of the time is that stuff their boss things is ready for mainline isn't. and then they find out that, shockingly, the maintainers couldn't care less about their bosses opinion. |
| 02:31.38 | whitequark | wpwrak: http://lse.sourceforge.net/io/aio.html |
| 02:31.43 | whitequark | What Does Not Work? |
| 02:31.43 | whitequark | AIO read and write on files opened without O_DIRECT |
| 02:32.06 | wpwrak | now that makes a lot more sense |
| 02:33.11 | dvdk | night. |
| 02:33.15 | whitequark | and the "additional functionality" is last patched to 2.6.12 |
| 02:33.20 | wolfspraul | n8 |
| 02:33.21 | whitequark | which is ancient |
| 02:33.28 | wolfspraul | dvdk: and thanks! of course |
| 02:34.10 | dvdk | no problem. just scrating the itches :) |
| 02:34.49 | whitequark | wpwrak: also this: http://lwn.net/Articles/148755/ |
| 02:35.04 | whitequark | given that aio supposedly wasn't updated much since 2.6.12, that is still applicable |
| 02:36.41 | wpwrak | now you know how what you have to do to become a famous kernel hacker :) |
| 02:37.52 | whitequark | wpwrak: I'm _really_ tired of rewriting/fixing every things I don't like how they work |
| 02:38.22 | whitequark | from ACPI in my old netbook to the xf86-input-synaptics (these are obviously in the "fixing" domain) |
| 02:38.51 | whitequark | now that I updated to Android 4 I have several open-source apps I like in the queue |
| 02:39.04 | whitequark | and osPID firmware, because it's quite FUBAR |
| 02:39.10 | wpwrak | perhaps you should then try to adapt your energy level for dislikes to your constructive energy levels :) |
| 02:39.36 | whitequark | heh |
| 02:39.53 | whitequark | that was just an example about why "organic growth" for a big library like gtk is bad |
| 02:40.11 | *** join/#qi-hardware cfy (~cfy@unaffiliated/chenfengyuan) |
| 02:40.20 | cfy | xiangfu: hi,are you here? |
| 02:40.27 | xiangfu | cfy, yes |
| 02:40.38 | wpwrak | yeah. damn linus that he didn't have a master plan for linux back in 1991 ;-) |
| 02:40.58 | whitequark | Linux is less of an example, because people still don't know how to write good OS kernels; but gui libraries have't changed radically for 15 years or so |
| 02:41.19 | whitequark | it's still all about buttons and textboxes |
| 02:42.07 | wpwrak | depends a bit. sometimes you also get a nice canvas to play with |
| 02:42.14 | whitequark | sure |
| 02:43.11 | whitequark | (good OS kernels) I won't be running in circles screaming "Linux is crap", but seriously, it had a lot of major drawbacks, it has been rewritten several times (if you squash all the rewrites in one "changeset"), and it _still_ has major drawbacks |
| 02:43.19 | whitequark | an OS kernel shouldn't be ideal for people to use it |
| 02:43.23 | whitequark | it should only be good enough |
| 02:43.39 | whitequark | and, also, it has a very narrow external interface compared to the internal one |
| 02:44.09 | whitequark | on the other hand, gui library has an enormous external interface which closely resembles the parts on the screen |
| 02:46.18 | whitequark | or take android. |
| 02:46.35 | whitequark | they didn't really thought about design back in 1.0 and pre-1.0 times, and now it backfired |
| 02:46.55 | whitequark | they _did_ think about design and UX in ICS, and it is really good, but every freaking app is broken |
| 02:47.44 | whitequark | compare to iphone, where there weren't any major changes to UI from 1.0 |
| 02:48.00 | whitequark | this is not a reason to use iphone, but it _is_ a reason to think before you code. |
| 02:48.12 | wpwrak | the main problem of android is that they did what the hw makers wanted |
| 02:48.44 | whitequark | oh, the device diversity. I'd say this is not a "problem" in the sense that it wasn't unexpected or something like that |
| 02:48.47 | whitequark | it is like PCs |
| 02:48.47 | wpwrak | android fragmentation is a perfect example for what's wrong in the prevailing mindset of the embedded hw industry |
| 02:49.23 | whitequark | android is designed to run over a wide range of hardware. it kind of accomplished that task in the sense that it can run on an incredibly wide range, beginning from $99 chinese tablets |
| 02:49.47 | wpwrak | what i don't know is if google fully realized that from the beginning (and decided to play along for a while), or if they didn't understand what mess this would produce themselves |
| 02:49.58 | whitequark | wpwrak: on the other hand, your very reply is a perfect example of what's wrong with OSHW overall |
| 02:50.07 | wpwrak | there's no problem with a lot of hardware |
| 02:50.09 | whitequark | maybe not exactly in your case, but still valid |
| 02:50.24 | wpwrak | there's a big problem if you have a divergent branch for each piece of hardware |
| 02:51.08 | whitequark | wpwrak: (divergent branch) hm, what do you mean for that? kernel forks? custom UIs? the fact that manufacturers don't want to upgrade old HW? |
| 02:51.20 | wpwrak | well, sometimes you to speak an unpleasant truth :) |
| 02:51.46 | whitequark | wpwrak: (what's wrong) you're a HW maker. you think of a device in terms of hardware, and maybe software. pre-3.0 Android was designed by programmers |
| 02:51.49 | whitequark | this is VERY wrong |
| 02:51.50 | wpwrak | yes, forks all over the place. and nothing goes back upstream. and that means that you can't upgrade. |
| 02:51.56 | whitequark | because yes, it worked, and it was open-source |
| 02:52.08 | wpwrak | consider this: http://theunderstatement.com/post/11982112928/android-orphans-visualizing-a-sad-history-of-support |
| 02:52.35 | whitequark | but if I'd be given a crappy open-source app and a nice-looking and convenient to use proprietary app, even I would most certainly get the proprietary one |
| 02:52.44 | wpwrak | the problem aren't implementation details. it's the general development process. |
| 02:52.58 | *** join/#qi-hardware wej (~j@m2.mullvad.net) |
| 02:53.02 | whitequark | when you do something just to make it open-source, you're doing it horribly wrong, and you won't make anything good, unfortunately |
| 02:53.14 | whitequark | example: gcc |
| 02:53.27 | whitequark | counter-example: clang |
| 02:53.46 | wpwrak | it's not even a question of open or closed. e.g., microsoft seem to be getting that bit right - they require things to go into mainline. |
| 02:54.39 | whitequark | wpwrak: (fragmentation) they get better with that, and cyanogenmod solves much of that problem |
| 02:54.45 | whitequark | hm. microsoft and mainline? |
| 02:54.49 | whitequark | what do you mean by that? |
| 02:56.08 | wpwrak | (cyanogen) yeah. the proverbial silver lining :) of course, sabotaged by binary-only drivers ... |
| 02:56.35 | whitequark | wpwrak: (main problem) you've been talking about problems of Android as an ecosystem, and I was talking about problem of pre-v3 Android as an OS of itself. it is just not a good mobile OS. not by today's standards. |
| 02:56.36 | wpwrak | (ms) that they get the drivers/extensions back. so they can produce updated versions. |
| 02:56.51 | wpwrak | (ms) i don't remember the reference, though |
| 02:57.19 | whitequark | wpwrak: (cyanogen) binary drivers are bad in multiple ways, and they're a somewhat significant problem of CM, but CM works, and it works good |
| 02:58.48 | wpwrak | (ecosystem) correct. i don't know about android's merits as an application platform. |
| 02:59.28 | wolfspraul | it inherits Java to a degree, it will follow Java's path |
| 02:59.45 | wpwrak | the joy of oracle :) |
| 02:59.57 | wolfspraul | on the phone/tablet manufacturer side, >90% of participants are on unsustainable trajectories |
| 03:00.09 | whitequark | (binary drivers) it would also be strange for Google to require sources of all userspace drivers linked with Apache-licensed environment |
| 03:00.30 | whitequark | and vendors open the parts they're required to. kernel trees, for example. still not enough, obviously |
| 03:00.42 | wolfspraul | that may be the 'let's set them up to go against each other' strategy that was conceived in the ivory tower, but in the end it will still show its nasty side, if that doesn't happen already |
| 03:01.18 | wpwrak | whitequark: there are many ways for google to address this. also non-open approaches may work. but they haven't done this. |
| 03:01.33 | wolfspraul | I ask myself a simple question: if a good friend (non-techie like 99% of the world) asks what smartphone they should buy, I would recommend? iphone, clearly. |
| 03:01.33 | whitequark | wpwrak: (app platform) I use it daily for months, and pre-v3 android is definitely not a good OS. period. 4.0 brings it on par with WP and iOS, but apps lag behind. |
| 03:02.14 | wolfspraul | I think we should leap ahead of all this mess :-) |
| 03:02.36 | whitequark | wpwrak: what do you mean by "unsustainable trajectories"? |
| 03:02.53 | whitequark | moving too fast to produce good code, and too money-burning to live for a long time? |
| 03:03.10 | wpwrak | ssh whitequark s/wpwrak/wolfspraul/ |
| 03:03.13 | wolfspraul | the manufacturers have no chance to make a good product |
| 03:03.55 | wolfspraul | but I'm not running around, I don't need to convince anyone. android may go to 9x% whatever marketshare, and I wouldn't care |
| 03:04.12 | wpwrak | at the moment, they have the GHz race to win. again ;-) and then the multicore race. again :-) |
| 03:04.14 | wolfspraul | survived the Symbian times, will survive the Android times :-) |
| 03:04.36 | whitequark | wolfspraul: why they do not? |
| 03:04.59 | wolfspraul | takes too long to go through |
| 03:05.12 | wolfspraul | at least android is consistent in what they do |
| 03:05.41 | wolfspraul | at android's peak, will it have bigger smartphone 'market share' than Symbian? |
| 03:05.44 | wolfspraul | :-) |
| 03:05.46 | wolfspraul | let's guess |
| 03:07.03 | wolfspraul | ok I dare: YES! :-) |
| 03:07.32 | whitequark | wolfspraul: uhm. I definitely don't get what's bad with Android in your opinion, and why iPhone is better in that sense |
| 03:08.30 | whitequark | and what does Java has to do with this |
| 03:08.37 | wolfspraul | malware, updates |
| 03:08.58 | wolfspraul | how did Java develop? |
| 03:09.28 | wolfspraul | it got a huge hype at its beginning, expectations through the roof even though there are gross shortcomings of the language |
| 03:09.44 | wolfspraul | academia adopted it in droves, and pumped millions of poor students through Java classes |
| 03:10.04 | wolfspraul | startups jumped on it and found it a good way to lock enterprise customer into convoluted Java 'systems' |
| 03:10.07 | whitequark | ... and now JVM is _the_ best VM in the world with tens of languages running on it |
| 03:10.12 | wolfspraul | it grew and grew |
| 03:10.21 | wolfspraul | it's probably very profitable for the players in the system even |
| 03:11.38 | wolfspraul | maybe we should bring Java to the Ben to make it *really successful* :-) |
| 03:11.45 | wolfspraul | ah no, wait. ANDROID! |
| 03:12.31 | wolfspraul | whitequark: just look at malware/app store quality, and os updates. in those 2 instances you see the issues clearly imho. |
| 03:12.55 | wolfspraul | but again, no need to run around about Android. if you enjoy it - great! more power to you. |
| 03:13.25 | wolfspraul | the Amazon Fire is pretty cool, Amazon returned Google's opening |
| 03:14.48 | whitequark | I still don't see what's wrong with Java per se |
| 03:15.06 | whitequark | well, it probably really was abused |
| 03:15.10 | whitequark | which doesn't make it any worse |
| 03:15.40 | whitequark | if you use `dd' to kill a puppy, would it make `dd' itself a bad thing?.. |
| 03:17.07 | whitequark | wolfspraul: (os updates) yes, here I agree with you. this is very broken, but hopefully Google understands the issue and did something to manage that. they've already adjusted release cycles and so on |
| 03:17.26 | whitequark | if they won't fix that, well, it's windowsphone time again. |
| 03:17.52 | whitequark | (I have an allergy to apples.) |
| 03:19.23 | whitequark | wolfspraul: (ben) if only Ben had the hardware to run Android, or any task relevant to modern world whatsoever, it won't need Android to be successful. |
| 03:19.57 | whitequark | you don't buy a device and then do strange things to make any use of it. you buy a device and it impresses you with the number of things it can do. |
| 03:21.59 | whitequark | seriously, the very fact that the wiki has a _separate page for use cases_ is FUBAR. not to mention that most of these use cases are actually feature requests which will never be fulfilled. |
| 03:22.15 | wolfspraul | wiki? |
| 03:22.18 | wolfspraul | how did that work again? |
| 03:22.40 | whitequark | http://en.qi-hardware.com/wiki/Nanonote_use_cases |
| 03:23.12 | wolfspraul | I'm just doing a test on my fedora system. I have 1450 packages installed. grep -i java finds 5. I am currently uninstalling them one by one to see whether any one of them is a dependency of any of the dozens of apps I use all the time. |
| 03:23.16 | wolfspraul | results to come in shortly |
| 03:25.03 | whitequark | and how that would relate to android (which is not fully Java-compatible anyway) and the fact that JVM is the fastest VM we currently have? |
| 03:25.07 | whitequark | waves his hand |
| 03:25.15 | wolfspraul | yes, libreoffice needs one |
| 03:25.22 | whitequark | this is a pointless discussion. I don't even understand what do you want to tell me. |
| 03:25.26 | wolfspraul | well I am down to one, I'll leave it there in peace |
| 03:25.44 | wolfspraul | nothing, I just cleaned up my system a bit, was curious about Java dependencies |
| 03:25.56 | wolfspraul | now I know: libreoffice needs it |
| 03:27.03 | whitequark | sigh. nevermind. |
| 03:27.52 | wolfspraul | do you use the jvm on your notebook/desktop ? |
| 03:28.04 | whitequark | yes |
| 03:28.12 | wolfspraul | what use cases? |
| 03:28.28 | whitequark | I have several apps, most notably aerofs (think distributed dropbox without key escrow), and my IDE, RubyMine |
| 03:28.32 | whitequark | and I use jruby extensively |
| 03:29.05 | whitequark | it is an implementation of Ruby on JVM, and it is really really fast. much faster than any other thing around here, most of the time it even compares with native code. |
| 03:29.12 | wolfspraul | interesting. thanks for sharing! that gives me some things to read about. I had not known about aerofs for example. |
| 03:29.25 | whitequark | aerofs is very unfortunately closed source |
| 03:29.29 | wolfspraul | ah |
| 03:29.37 | wolfspraul | that speeds up the reading :-) |
| 03:29.39 | whitequark | but it is still better than dropbox in the sense that it is distributed |
| 03:29.57 | whitequark | that is, it won't generally send your data somewhere and allow anyone in that "there" to read it |
| 03:30.00 | whitequark | as dropbox does |
| 03:30.12 | whitequark | and I never managed to find a working opensource alternative |
| 03:30.15 | whitequark | no, rsync isn't. |
| 03:31.16 | whitequark | personally for me, Java isn't of much value of itself, but JVM definitely is |
| 03:38.12 | whitequark | http://owncloud.org is somewhat promising |
| 03:38.53 | whitequark | but it has no desktop app yet :/ |
| 03:43.57 | whitequark | wolfspraul: there's also open-source Syncany (not yet released, but seems to be in active development), and guess what |
| 03:44.00 | whitequark | it's in Java! |
| 03:49.49 | *** join/#qi-hardware cladamw (~Adam@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 03:56.43 | *** join/#qi-hardware cladamw_ (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 04:13.39 | zrafa | wolfspraul: have you been talking about iphone being better than other things? |
| 04:13.46 | wolfspraul | no |
| 04:13.53 | wolfspraul | I would never dare to do so knowing that you are in the channel! |
| 04:14.01 | wolfspraul | maybe my machine was hacked? |
| 04:14.12 | zrafa | ah... you will be at the heaven at the next life |
| 04:14.15 | zrafa | god is with you |
| 04:14.49 | zrafa | maybe wpwrak then |
| 04:14.57 | zrafa | I know him |
| 04:15.57 | zrafa | arhg!.. my machine is under attack! |
| 04:16.06 | zrafa | JAVAAAAAAAAA |
| 04:16.13 | zrafa | no free memory |
| 04:17.44 | zrafa | Yes, definitely libreoffice needs java |
| 04:20.54 | zrafa | I can not continue writting. Sorry. Some people ask me to leave |
| 04:21.13 | wolfspraul | :-) |
| 04:21.28 | wolfspraul | really? the gods of java come to redeem your sins? |
| 04:21.57 | zrafa | :) |
| 04:23.00 | zrafa | I think that it is Miriam ;) but she does not like jave. |
| 04:23.04 | zrafa | java* |
| 04:23.35 | zrafa | maybe she is corrupt. I will listen her. See you guys |
| 04:32.44 | wpwrak | Java -> JVM |
| 04:32.57 | wpwrak | Java <- {.} // the empty set |
| 04:33.00 | wpwrak | very simple :) |
| 05:16.59 | *** join/#qi-hardware cladamw (~Adam@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 06:29.29 | *** join/#qi-hardware jekhor (~jek@leased-line-46-53-195-5.telecom.by) |
| 07:24.17 | *** join/#qi-hardware cladamw (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 08:00.27 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-39-238.w109-223.abo.wanadoo.fr) |
| 08:10.36 | *** join/#qi-hardware Ayla (~paul@53.121.101.84.rev.sfr.net) |
| 08:20.13 | *** join/#qi-hardware Ayla (~paul@186.132.123.78.rev.sfr.net) |
| 08:52.34 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 08:57.28 | qi-bot | The build has FAILED: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/openwrt-xburst.minimal-20120322-0704 |
| 09:17.46 | *** join/#qi-hardware Ornotermes (~rikard@78-69-248-123-no180.tbcn.telia.com) |
| 09:34.03 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 09:36.12 | *** join/#qi-hardware jivs (~jivs@nat-sta-slph1.tvu.ac.uk) |
| 10:10.17 | *** join/#qi-hardware Ayla (~paul@44.95.13.93.rev.sfr.net) |
| 10:10.55 | *** join/#qi-hardware Ayla (~paul@44.95.13.93.rev.sfr.net) |
| 10:25.03 | *** join/#qi-hardware Ayla (~paul@53.121.101.84.rev.sfr.net) |
| 10:31.47 | whitequark | DocScrutinizer51: hi |
| 10:31.54 | whitequark | I ordered two SIM900D for you |
| 10:32.06 | whitequark | if everything would work as expected, I'll send them tomorrow |
| 10:37.11 | qi-bot | [commit] Adam Wang: updated Sourcing status (master) http://qi-hw.com/p/wernermisc/cb05c7f |
| 10:37.12 | qi-bot | [commit] Adam Wang: Merge branch 'master' of projects.qi-hardware.com:wernermisc (master) http://qi-hw.com/p/wernermisc/af07d13 |
| 10:44.38 | *** join/#qi-hardware DocScrutinizer (~halley@openmoko/engineers/joerg) |
| 11:04.31 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 11:58.09 | *** join/#qi-hardware cladamw (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 12:24.22 | *** join/#qi-hardware sunnysujan (~sunnysuja@cpc1-nmal9-0-0-cust259.croy.cable.virginmedia.com) |
| 12:28.52 | *** join/#qi-hardware GeorgeH (~George@c-69-141-105-145.hsd1.nj.comcast.net) |
| 12:51.44 | *** join/#qi-hardware Ayla (~paul@53.121.101.84.rev.sfr.net) |
| 12:56.11 | *** part/#qi-hardware sunnysujan (~sunnysuja@cpc1-nmal9-0-0-cust259.croy.cable.virginmedia.com) |
| 13:25.22 | *** join/#qi-hardware urandom__ (~user@p548A3EF3.dip.t-dialin.net) |
| 13:50.12 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-39-238.w109-223.abo.wanadoo.fr) |
| 14:34.34 | *** join/#qi-hardware jekhor (~jek@46.216.54.223) |
| 15:00.28 | *** join/#qi-hardware jekhor (~jek@46.216.54.223) |
| 15:17.57 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-39-238.w109-223.abo.wanadoo.fr) |
| 15:41.36 | *** join/#qi-hardware kuribas (~user@d54C43316.access.telenet.be) |
| 15:43.38 | *** join/#qi-hardware emeb (~ericb@ip72-223-81-94.ph.ph.cox.net) |
| 15:52.35 | viric | do you keep the microcode up to date for your computers? |
| 15:54.39 | *** join/#qi-hardware aisa (~a@173-10-243-253-Albuquerque.hfc.comcastbusiness.net) |
| 16:29.51 | kyak | :) |
| 16:30.30 | kyak | my computer is zillion years old, no more microcode updates for it -\ |
| 16:31.26 | viric | hehe |
| 16:31.31 | viric | I updated a Pentium IV today |
| 16:31.40 | viric | from rev 0x0 to 0x37 |
| 16:31.53 | viric | kyak: maybe your computer reached perfection |
| 16:32.52 | kyak | yes!! i like to think about it that way |
| 16:38.38 | *** join/#qi-hardware sujan (~sujan@cpc1-nmal9-0-0-cust259.croy.cable.virginmedia.com) |
| 17:31.15 | *** join/#qi-hardware Ayla (~paul@186.132.123.78.rev.sfr.net) |
| 17:46.22 | *** join/#qi-hardware panda|x201 (~hzhang@2001:5c0:1000:a::164b) |
| 17:57.27 | *** join/#qi-hardware sujan (~sujan@cpc1-nmal9-0-0-cust259.croy.cable.virginmedia.com) |
| 18:00.15 | *** join/#qi-hardware GNUtoo (~gnutoo@host155-102-dynamic.10-188-r.retail.telecomitalia.it) |
| 18:04.37 | *** join/#qi-hardware zenlunatic (~justin@c-68-48-40-231.hsd1.md.comcast.net) |
| 18:05.00 | zenlunatic | anyone now where to get the rubber footsie on the bottom of the BNN... lost one |
| 18:06.35 | wpwrak | maybe try a drop of silicone. available at your next DIY shop |
| 18:07.24 | wpwrak | if you wet your fingers with alcohol, you can shape the silicone without it sticking to your fingers |
| 18:10.14 | viric | the drop of sillicone works great |
| 18:17.31 | DocScrutinizer | whitequark: great! |
| 18:19.30 | zenlunatic | cool |
| 18:25.46 | DocScrutinizer | I'd ask wolfspraul |
| 18:26.24 | DocScrutinizer | standard mail letters from China with silly rubber blobs inside are dirt cheap |
| 18:27.11 | DocScrutinizer | wolfspraul: is a nice guy, he probably can help |
| 18:28.10 | DocScrutinizer | I ised to do similar things for OM FR, but for BNN I'm not really involved |
| 18:28.15 | DocScrutinizer | used* |
| 18:29.48 | wpwrak | DocScrutinizer: we would help, but i think he doesn't have spare feet himself |
| 18:30.01 | wpwrak | s/we/he/ |
| 18:30.02 | qi-bot | wpwrak meant: "DocScrutinizer: he would help, but i think he doesn't have spare feet himself" |
| 18:30.06 | wpwrak | grmbl |
| 18:30.55 | DocScrutinizer | who's admin of qibot? |
| 18:31.32 | wpwrak | kyak ? wolfgang ? |
| 18:32.31 | DocScrutinizer | so any of you would tell the bot to stop regex? pretty please |
| 18:33.33 | DocScrutinizer | qi-bot: master |
| 18:33.45 | DocScrutinizer | qi-bot: owner |
| 18:33.57 | DocScrutinizer | MEH |
| 18:34.26 | DocScrutinizer | qi-bot: info |
| 18:34.30 | DocScrutinizer | qi-bot: status |
| 18:34.34 | DocScrutinizer | qi-bot: help |
| 18:35.13 | DocScrutinizer | qi-bot: die! |
| 18:36.17 | wpwrak | since you seem to control infobot, with whose appearance the problem started, there seems to be an easy and immediately implementable solution :) |
| 18:37.59 | whitequark | hm |
| 18:38.01 | whitequark | infobot: hi |
| 18:38.01 | infobot | hello, whitequark |
| 18:38.05 | whitequark | qi-bot: hi |
| 18:38.14 | whitequark | henceforth, I prefer infobot to stay. |
| 18:38.20 | whitequark | it is more polite. |
| 18:41.14 | zenlunatic | so you mean i can't mail the BNN to a vendor and pay $60 for something I can fix myself |
| 18:43.27 | DocScrutinizer | I bet you can |
| 18:45.28 | DocScrutinizer | wpwrak: there's a number of (immediately) and not so \1 implementable solutions to my choice, but none of them will take care of the requirements set up in this very chan, by wolfspraul, you, whitequark |
| 18:47.05 | *** join/#qi-hardware Ayla (~paul@252.194.124.78.rev.sfr.net) |
| 18:47.26 | DocScrutinizer | wolfspraul said he wants to keep infobot, you said you prefer infobot 's regex implementation over the qi-bot nonsense, and now whitequark preferred infobot for other reasons |
| 18:48.55 | DocScrutinizer | so I'm not going to implement a partial botch solution just to deal with missing responsiveness of qi-bot 's admin |
| 18:49.54 | DocScrutinizer | esp since I'm not sure how to disable regex in infobot |
| 18:50.10 | DocScrutinizer | neither if I may do it at all |
| 18:51.01 | kyak | wpwrak: what is it? |
| 18:54.24 | kyak | i'm not sure if it is right to spend some time implementing a feature (regexp replacement) just to disable it some day because it turns out to annoy DocScrutinizer |
| 18:54.42 | kyak | it was a popular request, as far as i remember |
| 18:55.15 | DocScrutinizer | it seems it annoys other users more than exactly me |
| 18:55.22 | kyak | DocScrutinizer: this is probably the last time i say it: learn the "ignore" command of your irc client. It solve ALL problems. |
| 18:55.41 | DocScrutinizer | kyak: thanks for the lesson :-S |
| 18:56.20 | DocScrutinizer | I pay back with "learn to read full backscroll" |
| 19:00.30 | DocScrutinizer | btw I doubt /ignore will solve the problem of smart alec posts I cope with not that good when in a foul mood |
| 19:24.54 | *** join/#qi-hardware sujan (~sujan@94.197.127.108.threembb.co.uk) |
| 19:59.27 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 20:09.23 | *** join/#qi-hardware Ayla (~paul@186.132.123.78.rev.sfr.net) |
| 20:30.32 | wpwrak | DocScrutinizer: you're correct that i prefer infobot's regex handling to qi-bot's. i never said it was a requirement for me, though. |
| 20:32.27 | DocScrutinizer51 | wpwrak: if I'd not feel like 'MEH CBA' after that lesson of kyak, I'd immediately fix it |
| 20:32.30 | wpwrak | DocScrutinizer: and on general principles, i disagree with the way you just put infobot here, afaik without any prior discussion, and then demand the removal of qi-bot. that's rather impolite and bully-ish. |
| 20:33.00 | wpwrak | DocScrutinizer51: ah, you have access to qi-bot ? even better :) |
| 20:33.22 | DocScrutinizer51 | I neither put it here (or rather kept) without any discussion |
| 20:33.31 | DocScrutinizer51 | nope |
| 20:33.43 | DocScrutinizer51 | I hape some access to infobot |
| 20:34.25 | DocScrutinizer51 | which I temprarily /invide'd to "~wtf nfc" |
| 20:35.05 | DocScrutinizer51 | then I said I'm not planning to keep her, and any chanop is free to /kick |
| 20:35.27 | DocScrutinizer51 | wolfspraul said sth I understood like he appreciates infobot |
| 20:35.38 | DocScrutinizer51 | so I made it permanent |
| 20:36.03 | DocScrutinizer51 | and I never asked for shutdown of qibot, WTF?! |
| 20:37.09 | DocScrutinizer51 | honestly, can't you guys find out about your inability to read chanlogs on a day when I'm not in a extremely foul mood? |
| 20:37.17 | wpwrak | well, at least partial shutdown, just a few minutes ago: "so any of you would tell the bot to stop regex? pretty please" |
| 20:38.04 | DocScrutinizer51 | that's been all according to *zour* very decision |
| 20:38.59 | DocScrutinizer51 | read the friggin chanlog |
| 20:42.27 | DocScrutinizer51 | I just pointed to the problem, demonstrated the diffs in implementation of regex on both, and even dared to mention *I* would prefer infobot. The final decision been by wpwrak |
| 20:43.09 | wpwrak | "my decision" ? that sounds like some misunderstanding. anyway, perhaps this discussion is better continued on a day when your mood is less foul ? |
| 20:43.13 | DocScrutinizer51 | Now I take the flames for trying to implement what *you* picked |
| 20:43.56 | DocScrutinizer51 | sorry, too friggin stupid a debate for me today |
| 20:44.32 | DocScrutinizer51 | fix it or leave it like now, whatever you like. don't pester me again about it! |
| 21:15.32 | DocScrutinizer | [Do 15. März 2012] [13:37:00] <DocScrutinizer51> tell me what you decided on that |
| 21:15.33 | DocScrutinizer | [Do 15. März 2012] [13:37:41] <DocScrutinizer51> so I may find the proper chanset flag for infobot to turn it off, if it's infobot to shutup |
| 21:16.38 | DocScrutinizer | [Do 15. März 2012] [15:16:57] * kristianpaul loves infobots |
| 21:17.59 | DocScrutinizer | [Do 15. März 2012] [09:05:28] <DocScrutinizer> she won't stay anyway, I haven't added #qi-hw to infobot's autojoin list |
| 21:18.00 | DocScrutinizer | [Do 15. März 2012] [09:06:14] <DocScrutinizer> !status |
| 21:18.02 | DocScrutinizer | [Do 15. März 2012] [09:06:23] <wolfspra1l> DocScrutinizer: thanks a lot! in my opinion she should stay |
| 21:18.47 | DocScrutinizer | now you got one more chance to give me definitive instructions how to handle the issue |
| 21:19.24 | DocScrutinizer | I'm not your whipping boy |
| 21:20.43 | DocScrutinizer | [Do 15. März 2012] [13:18:19] <qi-bot> DocScrutinizer51 meant: "DUH! one problem though I'll deal with later on:" |
| 21:20.44 | DocScrutinizer | [Do 15. März 2012] [13:20:44] <DocScrutinizer51> wolfspra1l: shall infobot ignore regex, or do you prefer to disable it in qibot? |
| 21:20.46 | DocScrutinizer | [Do 15. März 2012] [13:21:24] <DocScrutinizer51> I personally think qibot's implementation is inferior |
| 21:20.47 | DocScrutinizer | [Do 15. März 2012] [13:23:25] <DocScrutinizer51> s/personally/for one/ |
| 21:21.16 | DocScrutinizer | you are free to read up your own contributions in chanlog |
| 21:21.49 | DocScrutinizer | I'm not going to take and accept any further blame regarding the issue |
| 21:22.14 | *** join/#qi-hardware panda|x201 (~hzhang@123.112.97.203) |
| 21:33.15 | wpwrak | DocScrutinizer: IMHO, the first step would be to determine what you're actually trying to accomplish. if it's a change to the regex handling (e.g., require ending /, remove implicit g), then i think there's a majority that agrees with such a change. then, the next step would be to discuss with kyak how to make that happen. most likely, it's a quick change to qi-bot. infobot wouldn't be needed or at least not for substitutions in that |
| 21:33.16 | wpwrak | case. if, however, he thinks this would be better handled by infobot, then he should disable the feature in qi-bot and let infobot do it. |
| 21:33.45 | DocScrutinizer | and I'll not take any further actions to sanitaze the situation, nor ever again rise the topic, unless someone of you starts giving clear instructions |
| 21:34.26 | DocScrutinizer | I'm thoroughly pissed of taking flames for trying to be helpful |
| 21:34.46 | wpwrak | see, the problem here is that nobody really "owns" the channel. normally, people follow their social instincts and resolve conflicts without needing a judge. |
| 21:35.31 | wpwrak | always remember: the road to hell is paved with good intentions :-) |
| 21:35.52 | DocScrutinizer | to me the chan is owned by a) those on access list and -- no not b) but major A) by owner of name qi-hardware |
| 21:36.41 | DocScrutinizer | I'm not interested on way to hell - I arrived there long time ago |
| 21:36.57 | wpwrak | hence the smoking ? :) |
| 21:37.29 | DocScrutinizer | cya |
| 21:37.43 | wpwrak | enjoy the pub ! :) |
| 21:37.55 | DocScrutinizer | already back home |
| 21:38.11 | wpwrak | back from the pub ? that's early |
| 21:38.22 | DocScrutinizer | I had my N900 with me |
| 21:38.31 | DocScrutinizer | so it was too dangerous to stay |
| 21:39.07 | wpwrak | ah, so you left before the fighting and thieving normally starts. i see :) |
| 21:40.07 | DocScrutinizer | before my mood - caused by #qi-hardware - made me do insane things to innocent guests |
| 21:41.00 | wpwrak | perhaps just catching up with a bit with sleep will help. it's been a long and busy week. |
| 21:41.21 | DocScrutinizer | it's been a night with 12h of sleep |
| 21:41.57 | DocScrutinizer | which actually might explain a few things to me which I forgot to take into account |
| 21:42.00 | wpwrak | okay, so that was either too much, or you need more of it. there's but one way to find out - controlled experiments :) |
| 21:42.26 | DocScrutinizer | madness started yesterday anyway |
| 21:42.35 | DocScrutinizer | and today it got worse |
| 21:42.48 | DocScrutinizer | and when I left friggin job, it got even worse |
| 21:43.26 | DocScrutinizer | and then came qi-hardware |
| 21:44.07 | DocScrutinizer | toldya I got a foul mood |
| 21:44.27 | DocScrutinizer | and that for I'm off now |
| 21:44.51 | DocScrutinizer | don't dare to ever pester me about infobot, unless you know what you want |
| 21:51.24 | kristianpaul | infobot: milkymist? |
| 21:52.02 | DocScrutinizer | one last note: it's a terrible sitaution that founder of this channel is a bot |
| 21:53.12 | DocScrutinizer | and that bot isn't exactly verbose and forthcoming when you try to find out who's her master |
| 21:53.37 | DocScrutinizer | ~listkeys milkymist |
| 21:53.53 | DocScrutinizer | ~listvalues milkymist |
| 21:54.26 | DocScrutinizer | ~milkymist is a mystery |
| 21:54.26 | infobot | DocScrutinizer: okay |
| 21:54.44 | DocScrutinizer | ~forget milkymist |
| 21:54.44 | infobot | DocScrutinizer: i forgot milkymist |
| 21:55.31 | DocScrutinizer | please keep in mind I have set up the bot in a way you can have your very own namespace, like: |
| 21:55.42 | DocScrutinizer | ~#qi-hardware milkymist is a mystery |
| 21:55.42 | infobot | DocScrutinizer: okay |
| 21:55.50 | DocScrutinizer | ~milkymist |
| 21:55.50 | infobot | rumour has it, milkymist is a mystery |
| 21:56.14 | DocScrutinizer | this factoid is not available as ~milkymist in any other chan |
| 21:56.34 | DocScrutinizer | likewise you can override factoids like ~flashing |
| 21:56.40 | DocScrutinizer | ~flashing |
| 21:56.40 | infobot | rumour has it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 21:56.47 | DocScrutinizer | ~literal flashing |
| 21:56.47 | infobot | "flashing" is "<reply>see maemo-flashing" |
| 21:57.15 | zrafa | I still do not know how to say "actions" like others do with "*pepe is cooking something" ;) |
| 21:57.27 | DocScrutinizer | ~qi-hardware flashing is the only way to get new firmware on milkymist |
| 21:57.27 | infobot | okay, DocScrutinizer |
| 21:57.50 | wpwrak | zrafa: /me is cooking something |
| 21:57.52 | DocScrutinizer | ~flashing |
| 21:57.52 | infobot | extra, extra, read all about it, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 21:58.00 | DocScrutinizer | dang |
| 21:58.06 | DocScrutinizer | ~#qi-hardware flashing is the only way to get new firmware on milkymist |
| 21:58.07 | infobot | DocScrutinizer: okay |
| 21:58.10 | DocScrutinizer | ~flashing |
| 21:58.11 | infobot | from memory, flashing is the only way to get new firmware on milkymist |
| 21:58.25 | zrafa | wpwrak: ha!°.. thanks! there is alwasy something new to learn :) |
| 21:58.28 | DocScrutinizer | ~forget qi-hardware flashing |
| 21:58.28 | infobot | i forgot qi-hardware flashing, DocScrutinizer |
| 21:58.45 | zrafa | is learning the actions thing |
| 21:58.57 | DocScrutinizer | you already did :-) |
| 21:59.13 | zrafa | DocScrutinizer: yeah it seems :) |
| 21:59.52 | zrafa | I am not a big fan of aaaaallll of tiny details about irc chat. I usually just write and press ENTER |
| 22:00.06 | zrafa | without to know all the functions irc chats have |
| 22:00.17 | DocScrutinizer | bots are a niche magic |
| 22:00.46 | zrafa | I have no idea what is bots, infobots, etc .. which are always remember things or fixing people words |
| 22:00.49 | zrafa | :P |
| 22:01.40 | zrafa | but they do not disturb me.. I just ignore the lines of infobot, bots.. when they say something |
| 22:01.52 | DocScrutinizer | some useful stuff to be found at http://freenode.net/using_the_network.shtml and neighbours |
| 22:03.28 | DocScrutinizer | zrafa: infobot has a database of ~150,000 factoids that you can query via ~factoid |
| 22:03.57 | viric | is 'factoid' a word? |
| 22:04.06 | DocScrutinizer | she has some other less intriguing functions as well |
| 22:04.21 | DocScrutinizer | viric: for infobot it is |
| 22:04.25 | DocScrutinizer | ~status |
| 22:04.25 | infobot | Since Thu Mar 22 21:21:46 2012, there have been 6 modifications, 46 questions, 0 dunnos, 0 morons and 32 commands. I have been awake for 1d 42m 39s this session, and currently reference 118475 factoids. I'm using about 22328 kB of memory. With 0 active forks. Process time user/system 337.55/7.15 child 0/0 |
| 22:04.40 | DocScrutinizer | ok only ~120,000 |
| 22:04.58 | DocScrutinizer | ~listkeys gates |
| 22:05.17 | DocScrutinizer | ~bill gates |
| 22:05.17 | infobot | [bill gates] lord of Darkness |
| 22:05.26 | viric | irc wisdom |
| 22:06.00 | DocScrutinizer | ~listkeys openmoko |
| 22:06.33 | DocScrutinizer | you see #openmoko-cdevel has a local namespace, just like this chan has |
| 22:06.35 | zrafa | DocScrutinizer: interesting |
| 22:06.53 | DocScrutinizer | ~#openmoko audio |
| 22:06.59 | DocScrutinizer | err |
| 22:07.06 | DocScrutinizer | ~#openmoko-cdevel audio |
| 22:07.07 | infobot | somebody said #openmoko-cdevel audio was http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem and http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem |
| 22:07.11 | wpwrak | viric: dict factoid :) |
| 22:07.23 | DocScrutinizer | ~dict factoid |
| 22:08.33 | wpwrak | hmm, /ignore should have a message pattern match as well |
| 22:09.02 | DocScrutinizer | re ~#openmoko-cdevel audio: in #openmoko-cdevel chan you invoke that factoid simply via ~audio |
| 22:09.27 | DocScrutinizer | while here you get sth different |
| 22:09.30 | DocScrutinizer | ~audio |
| 22:09.30 | infobot | from memory, audio is usually a codec issue. start with trying to set 'disallow=all' and 'allow=alaw' in sip.conf or the channel's config file if not using sip |
| 22:09.53 | DocScrutinizer | ~literal audio |
| 22:09.53 | infobot | "audio" is "usually a codec issue. start with trying to set 'disallow=all' and 'allow=alaw' in sip.conf or the channel's config file if not using sip" |
| 22:10.10 | DocScrutinizer | ~literal #openmoko-cdevel audio |
| 22:10.10 | infobot | "#openmoko-cdevel audio" is "http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem and http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem" |
| 22:11.09 | DocScrutinizer | there are another few more or less useful finctions of infobot |
| 22:11.23 | DocScrutinizer | ~2 + 3^15 |
| 22:11.23 | infobot | 10 |
| 22:11.29 | DocScrutinizer | err |
| 22:11.46 | DocScrutinizer | ~3^10 |
| 22:11.46 | infobot | 9 |
| 22:11.52 | DocScrutinizer | o.O |
| 22:11.56 | DocScrutinizer | LOL |
| 22:12.08 | viric | the exponent goes in binary |
| 22:12.10 | DocScrutinizer | ~12345 * 67890 |
| 22:12.10 | infobot | 838102050 |
| 22:12.20 | viric | or ^ means xor |
| 22:12.26 | DocScrutinizer | prolly |
| 22:12.32 | DocScrutinizer | ~3^^10 |
| 22:12.55 | DocScrutinizer | strange |
| 22:13.08 | DocScrutinizer | ~3^2 |
| 22:13.08 | infobot | 1 |
| 22:13.26 | DocScrutinizer | I forgot the math notation |
| 22:13.48 | DocScrutinizer | ~5! |
| 22:13.48 | infobot | [5!] 120 |
| 22:14.29 | viric | ~3**2 |
| 22:14.29 | infobot | 9 |
| 22:14.31 | viric | :) |
| 22:14.33 | viric | I win |
| 22:14.36 | DocScrutinizer | :P |
| 22:14.45 | DocScrutinizer | I am the loser today |
| 22:14.54 | DocScrutinizer | we already agreed on that |
| 22:14.57 | viric | haha |
| 22:14.57 | DocScrutinizer | ;-) |
| 22:15.10 | viric | ~0x321+10 |
| 22:15.13 | DocScrutinizer | ~3**55 |
| 22:15.13 | infobot | 174449211009120166087753728 |
| 22:15.48 | DocScrutinizer | I'm not sure about non-10 base |
| 22:15.59 | viric | ~07+01 |
| 22:15.59 | infobot | 8 |
| 22:16.08 | kristianpaul | ~wikipedia qi-hardware |
| 22:16.19 | kristianpaul | ~wikipedia milkymist |
| 22:16.31 | DocScrutinizer | anyway |
| 22:16.33 | DocScrutinizer | ~query |
| 22:16.33 | infobot | talk dirty to me! Preferably, do so after you have typed "/query infobot" which should open a new window/tab/whatever with most irc clients. You can talk to me all you like and don't annoy other people with endless queries. Be aware that the stuff you write is logged, so don't get too 1337 :) |
| 22:16.34 | kristianpaul | he |
| 22:16.38 | DocScrutinizer | and |
| 22:16.41 | DocScrutinizer | ~+help |
| 22:16.43 | kristianpaul | sure ;) |
| 22:17.09 | kristianpaul | DocScrutinizer: does this infobot reacts to questionns like |
| 22:17.18 | kristianpaul | How i do reflash my nanonote? |
| 22:17.28 | kristianpaul | automatically? |
| 22:17.34 | DocScrutinizer | only when introduced by ~ (key char) or infobot: |
| 22:17.43 | kristianpaul | ~How i do reflash my nanonote? |
| 22:17.49 | kristianpaul | got it |
| 22:17.55 | kristianpaul | ~ How i do reflash my nanonote? |
| 22:17.57 | kristianpaul | ergh |
| 22:18.05 | DocScrutinizer | it's too complex |
| 22:18.23 | kristianpaul | i heard infobots can understand that.. |
| 22:18.27 | kristianpaul | anyway back later |
| 22:18.34 | DocScrutinizer | basically best is to only post the keyword |
| 22:18.35 | kristianpaul | have fun with the bot |
| 22:18.53 | DocScrutinizer | ~what is milkymist |
| 22:18.53 | infobot | rumour has it, milkymist is a mystery |
| 22:19.21 | DocScrutinizer | ~tell me what you think about milkymist |
| 22:19.49 | DocScrutinizer | ~what do you think about milkymist |
| 22:20.42 | DocScrutinizer | sometimes she answers "gee, I don't know what you're talking about" |
| 22:21.11 | DocScrutinizer | she's no plain text parser ;-) |
| 22:21.30 | DocScrutinizer | ~omap |
| 22:21.30 | infobot | http://OMAP.com/ or Texas Instrument's OMAP Platform is comprised of high-performance, power efficient processors, a robust software infrastructure and comprehensive support network for the rapid development of differentiated internet appliances, 2.5G and 3G wireless handsets and PDAs, and other multimedia-enhanced devices. #ol |
| 22:22.47 | DocScrutinizer | and now I'm definitely off |
| 22:24.42 | DocScrutinizer | just keep in mind you might want to append to head of factoids a "#qi-hardware " when they are chan topic specific |
| 22:25.11 | DocScrutinizer | ~bill gates |
| 22:25.11 | infobot | somebody said bill gates was lord of Darkness |
| 22:25.33 | DocScrutinizer | ~#qi-hardware bill gates is not in this channel, and never will be |
| 22:25.33 | infobot | okay, DocScrutinizer |
| 22:25.37 | DocScrutinizer | ~bill gates |
| 22:25.37 | infobot | [bill gates] not in this channel, and never will be |
| 22:26.33 | DocScrutinizer | ~listkeys qi-hardware |
| 22:27.19 | DocScrutinizer | ~infobot |
| 22:27.19 | infobot | I'm your very local infobot, and this is a facoid only valid in this chan |
| 22:27.50 | DocScrutinizer | ~_default infobot |
| 22:27.50 | infobot | it has been said that infobot is happy, or a liar |
| 22:30.00 | DocScrutinizer | btw feel free to redefine ~milkymist |
| 22:30.40 | DocScrutinizer | just make bot ~forget milkymist before you define a new milkymist factoid |
| 22:30.56 | DocScrutinizer | otherwise: |
| 22:31.09 | DocScrutinizer | ~milkymist is "laready existing" |
| 22:31.09 | infobot | DocScrutinizer: okay |
| 22:31.15 | DocScrutinizer | dang |
| 22:31.24 | DocScrutinizer | sorry for confusing example |
| 22:31.27 | DocScrutinizer | :-) |
| 22:31.39 | DocScrutinizer | ~milkymist is "already existing" |
| 22:31.39 | infobot | ...but milkymist is already something else... |
| 22:31.54 | DocScrutinizer | ~forget milkymist |
| 22:31.54 | infobot | i forgot milkymist, DocScrutinizer |
| 22:32.21 | DocScrutinizer | ~milkymist |
| 22:32.21 | infobot | rumour has it, milkymist is a mystery |
| 22:32.27 | DocScrutinizer | ;-D |
| 22:32.38 | DocScrutinizer | ~literal milkymist |
| 22:32.38 | infobot | "#qi-hardware milkymist" is "a mystery" |
| 22:33.24 | DocScrutinizer | ~milkymist is /join #qi-hardware |
| 22:33.25 | infobot | okay, DocScrutinizer |
| 22:33.30 | DocScrutinizer | ~milkymist |
| 22:33.31 | infobot | from memory, milkymist is a mystery |
| 22:33.40 | DocScrutinizer | ~_default milkymist |
| 22:33.40 | infobot | extra, extra, read all about it, milkymist is /join #qi-hardware |
| 22:40.15 | DocScrutinizer | and since I'm fed up with the feeling left over from this evening... |
| 22:40.32 | DocScrutinizer | ~chanset #qi-hardware -sed |
| 22:40.32 | infobot | setting sed for #qi-hardware is not set. |
| 22:40.40 | *** join/#qi-hardware jekhor (~jek@176.60.45.222) |
| 22:40.43 | DocScrutinizer | ~chanset #qi-hardware sed 0 |
| 22:40.43 | infobot | Setting sed for #qi-hardware to '0'. |
| 22:40.50 | DocScrutinizer | ~chanset #qi-hardware |
| 22:40.50 | infobot | chan: #qi-hardware (see _default also) |
| 22:40.50 | infobot | <PROTECTED> |
| 22:41.00 | DocScrutinizer | foobar |
| 22:41.07 | DocScrutinizer | s/bar/XXX/ |
| 22:41.07 | qi-bot | DocScrutinizer meant: "fooXXX" |
| 22:42.48 | DocScrutinizer | ~lart wpwrak |
| 22:42.48 | infobot | eats wpwrak and falls over dead |
| 22:46.18 | DocScrutinizer | n8 folks |
| 22:57.13 | *** join/#qi-hardware wolfspraul (~wolfsprau@222.130.114.203) |
| 23:21.12 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 23:41.47 | *** join/#qi-hardware zear_ (~zear@2001:0:5ef5:79fb:8a2:20d5:2abe:b43b) |