| 00:04.50 | *** join/#maemo janemba (~101@unaffiliated/janemba) |
| 00:05.13 | *** join/#maemo HylianHero (hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 00:10.38 | *** join/#maemo nikosapi (~nikosapi@nikosapi.org) |
| 00:28.39 | *** join/#maemo janemba (~101@unaffiliated/janemba) |
| 00:54.17 | *** join/#maemo Macer (mace@scientiam.org) |
| 00:54.52 | Macer | well. nice to see that i have been fighting with my router just to discover it is ddwrt that was the culprit |
| 00:55.15 | Macer | awesome |
| 00:58.34 | *** join/#maemo triggerhappy (~quassel@112.209.17.173) |
| 00:59.58 | ecc3g | the problem is still your router? |
| 01:00.35 | *** join/#maemo janemba (~101@unaffiliated/janemba) |
| 01:08.10 | *** join/#maemo kolp_ (~quassel@212.255.253.143) |
| 01:08.28 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 01:09.02 | Macer | no |
| 01:09.20 | Macer | it was |
| 01:09.29 | Macer | i installed tomato. no more issues |
| 01:09.55 | mashina | what router? |
| 01:10.09 | Macer | it was ddwrt |
| 01:10.12 | mashina | i have to use isp stock router with stock firmware |
| 01:10.17 | mashina | Macer: no the router |
| 01:10.35 | mashina | it's like asking what model of phone and you say android |
| 01:10.53 | Macer | i was answering ecc3g heh |
| 01:10.58 | Macer | it's a wrt610n |
| 01:11.28 | mashina | i have an actiontec R1000H here |
| 01:12.32 | Macer | heh. it was awful |
| 01:12.40 | Macer | had me pulling out my hair |
| 01:15.14 | Macer | it is nice now |
| 01:15.21 | Macer | although i'm getting some latency that i need to figure out |
| 01:18.31 | mashina | does the ctrl and shift keys feel a little creaky/suishy to you. |
| 01:19.06 | Macer | no. heh |
| 01:19.12 | Macer | i'm talking about from a laptop |
| 01:19.16 | Macer | the n900 is acting a big laggy too |
| 01:19.24 | Macer | i have to check out the options and see where the problem is |
| 01:19.35 | Macer | could just be crappy signal although the surface is going 6MB/s |
| 01:19.40 | Macer | before i was happy if i hit 1MB/s |
| 01:20.54 | Hurrian | Macer: tomato <3 |
| 01:21.39 | Macer | the 2.4GHz radio seems laggy |
| 01:21.45 | Hurrian | the newest builds finally have muli-ssid, bringing feature parity with DD-WRT |
| 01:21.49 | Macer | i'm trying to figure out the problem. n900 is really bad |
| 01:22.40 | Hurrian | Macer: sequential transfer performance, or burst transfers? |
| 01:22.42 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 01:23.22 | mashina | you have a surface? |
| 01:23.43 | *** join/#maemo Defiant (erik@e179197045.adsl.alicedsl.de) |
| 01:26.04 | Macer | hm |
| 01:26.06 | Macer | yeah |
| 01:26.22 | Macer | wth is wrong with this 2.4GHz line? heh |
| 01:26.45 | Macer | it is lagged to hell |
| 01:26.57 | *** join/#maemo jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 01:27.19 | mashina | Macer: rt or pro |
| 01:27.26 | Macer | especially on n900 |
| 01:27.46 | Macer | rt |
| 01:28.11 | Macer | hm |
| 01:28.15 | Macer | the laptop doesn't do it nearly as bad |
| 01:28.28 | mashina | do you like it? |
| 01:28.35 | mashina | what do you do with it? |
| 01:28.35 | Macer | yeah. it's actually not bad at all |
| 01:28.43 | Macer | mostly just layman stuff |
| 01:28.52 | Macer | browse, office work, facebook, etc heh |
| 01:29.15 | mashina | i was considering a surface because its portable and itd run teamviewer (what i use for remote support) |
| 01:30.10 | mashina | i run windows 8 on 2006 HW perfectly so i think it'd be fast on rt/tegra, yes? |
| 01:30.18 | Macer | i got the rt because it is awesome with the battery life |
| 01:30.23 | Macer | and is always on |
| 01:30.25 | Macer | pro sleeps |
| 01:30.41 | Macer | but then again the pro is an x86 so you can install anything on it |
| 01:30.46 | mashina | is there lag? (not network, usage) |
| 01:30.48 | Macer | you can "jailbreak" the rt and install some apps |
| 01:30.53 | Macer | not that i've noticed |
| 01:30.57 | mashina | Macer: if only official |
| 01:31.00 | Macer | ti's actually rather quick |
| 01:31.07 | Macer | yeah. it isn't heh |
| 01:31.12 | Macer | the jailbreak isn't a supported method |
| 01:31.13 | mashina | i'd love for ms to approve and sign desktop apps |
| 01:31.19 | Macer | yeah but i doubt they will |
| 01:31.24 | mashina | maybe thered be a maemoesque community |
| 01:31.24 | Macer | because then everybody would just dev for the arm lol |
| 01:31.37 | Macer | i mean.. there isn't much you need the desktop for anyways |
| 01:31.42 | mashina | because the android community is a joke |
| 01:31.44 | Macer | even the apps i did install i hardly use . like putty |
| 01:31.54 | Macer | you mean the high school virgin club? :) |
| 01:31.55 | Macer | lol |
| 01:31.57 | mashina | ssh is my n900s main use |
| 01:32.09 | mashina | Macer: theres no organization at all |
| 01:32.12 | Macer | oh i use my n900 for almost everything |
| 01:32.13 | mashina | nothing |
| 01:32.21 | Macer | you find that in all open communities lol |
| 01:32.24 | Macer | not just android |
| 01:32.24 | mashina | upstream is opaque |
| 01:32.30 | Macer | if android lost google |
| 01:32.33 | mashina | android dev process is opaque |
| 01:32.36 | Macer | android would be a nothing in a year or two |
| 01:32.44 | Macer | just like any other "open" project that loses its company support |
| 01:32.54 | mashina | custom roms are a foolish endavour (zipaligned deodexed) |
| 01:33.11 | Macer | i still don't understand why they call them "ROMs" |
| 01:33.11 | Macer | heh |
| 01:33.12 | mashina | community doesn't focus on quality or contributing to open source |
| 01:33.36 | mashina | google is closing parts of android |
| 01:33.41 | mashina | sad world in mobile |
| 01:33.45 | Macer | yeah |
| 01:33.50 | Macer | they are closing parts of google tbh |
| 01:33.58 | Macer | starting with connectivity with win8 and xmpp heh |
| 01:34.04 | mashina | i was never in google ecosystem |
| 01:34.18 | Macer | i used it quite a bit.. but it was a decade long bait and switch |
| 01:34.22 | Macer | now they'll start closing everything off |
| 01:34.29 | mashina | i was a little concerned they were tracking people for years before prism |
| 01:34.40 | Macer | naw |
| 01:34.43 | Macer | not tracking them like that |
| 01:34.44 | mashina | i was slightly but never fully paranoid |
| 01:34.52 | Macer | just tracking them inasmuch they want to advertise to you better |
| 01:34.55 | Macer | but that was a known |
| 01:35.10 | mashina | i imagine theyd keep your data with them only |
| 01:35.22 | mashina | why share with stasi if you dont have to? |
| 01:35.27 | Macer | heh |
| 01:35.31 | Macer | because people buy it ;) |
| 01:35.55 | Macer | if something can be sold someone will sell it |
| 01:36.10 | Macer | you didn't think all that free stuff was actually free did you? hehe |
| 01:36.18 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 01:36.35 | mashina | huehuehuehue |
| 01:36.57 | Macer | but google realized that it now has a large enough user base where it can close off shop |
| 01:37.03 | Macer | and handle everything and run exactly like ms and apple |
| 01:37.09 | ecc3g | just hope people realize that their data is not theirs anymore when trading it for convenience... |
| 01:37.14 | Macer | and wean the community off them and then abandon them lol |
| 01:37.26 | Macer | ecc3g: yeah. pretty much. |
| 01:37.26 | Macer | heh |
| 01:37.34 | Macer | ah well. time for me to go. ttyl. |
| 01:37.47 | ecc3g | runs own server... only way to do it. |
| 01:38.42 | mashina | shares with friends |
| 01:39.01 | mashina | because its more fun when you split costs and avoid duping |
| 01:39.17 | mashina | that and it feels like a mainframe with timesharing |
| 01:39.56 | ecc3g | it's all your choice when you decide to give everything away... |
| 01:40.30 | *** join/#maemo robbiethe1st (~robbiethe@50-52-1-122.cral.id.frontiernet.net) |
| 01:41.22 | mashina | looking for good caldav server |
| 01:41.50 | mashina | friend likes owncloud but we dont need owncloud's other bloat (that and he runs private instance on his private serv) |
| 01:42.00 | mashina | plus owncloud is flaky |
| 01:42.51 | ecc3g | nah, need to avoid big packages of bloat... I'll trade inconvenience for security. |
| 01:43.33 | ecc3g | or rather, i don't mind the inconvenience as long as I get the security... |
| 01:43.58 | mashina | i bet youre an openbsd user |
| 01:44.10 | mashina | i love openbsd but im not paranoid |
| 01:44.16 | mashina | just practical |
| 01:44.37 | ecc3g | no 100% linux |
| 01:44.59 | ecc3g | I run maemo after all... :o |
| 01:45.20 | mashina | i myself would drop linux (except maemo) completely if it just had virtualization |
| 01:45.58 | ecc3g | go and port it and have someone steal it and sell it? |
| 01:46.54 | mashina | oh no gpl purists |
| 01:47.10 | ecc3g | go ahead and port it, I'm not stopping you. |
| 01:47.47 | mashina | port what |
| 01:47.55 | ecc3g | virtualization software. |
| 01:48.10 | mashina | it has qemu but its in software |
| 01:48.29 | mashina | youd need kernel level changes afaik for hardware or even ring virt |
| 01:48.38 | ecc3g | port kvm... oh wait you can't, go design your own from scratch. |
| 01:48.54 | mashina | zzzzzzz |
| 01:49.06 | ecc3g | and give it away in the openbsd kernel... and watch it show up in ios |
| 01:54.58 | *** join/#maemo mschlens (~mschlens@p549365F6.dip0.t-ipconnect.de) |
| 01:59.14 | *** join/#maemo beford (~a@unaffiliated/beford) |
| 02:11.05 | *** join/#maemo guerby (~guerby@ip165-ipv6.tetaneutral.net) |
| 02:47.18 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 03:01.45 | *** join/#maemo lxp (~lxp@188-22-218-107.adsl.highway.telekom.at) |
| 03:17.58 | Macer | wow |
| 03:33.27 | *** join/#maemo maybeArgh (~cl@p5B165F25.dip0.t-ipconnect.de) |
| 03:55.46 | DocScrutinizer05 | the convo about frontcam was very inspiring. I think we need to check indepth how it#s handled and what might apps like "video call2 do to the hw config in cam chip |
| 03:56.13 | DocScrutinizer05 | yes it's known to need lots of light to work semi-decent |
| 03:56.47 | DocScrutinizer05 | it's also known from early N900 days that Nokia shiped several camdriver improvements to main cam but iirc also to frontcam |
| 03:57.35 | DocScrutinizer05 | freemangordon: ^^^ you might be interested in those details as of convo above |
| 03:58.34 | freemangordon | DocScrutinizer05: hmm? |
| 03:59.17 | DocScrutinizer05 | abysmal quality of frontcam when using mirror, until you did a video call after which is seems to be much better. Interesting, isn't it? |
| 03:59.36 | DocScrutinizer05 | ("mirror" is an app) |
| 03:59.43 | freemangordon | no, it isn't, it just shows that mirror is of bad quality |
| 04:00.21 | freemangordon | there is V2L API to control front cam properties, obviously mirror isn't using it |
| 04:00.40 | DocScrutinizer05 | :nod: |
| 04:01.05 | DocScrutinizer05 | but how would frontcam the "get better" after doing a video call, for mirror app? |
| 04:01.23 | freemangordon | it is the same story about gtalk video has way better quality than skype |
| 04:01.28 | DocScrutinizer05 | wouldn't cam get powered down and reset each time it gets opened? |
| 04:01.59 | freemangordon | sure, but driver restores what's been last set |
| 04:02.02 | DocScrutinizer05 | s/the7then get better... |
| 04:02.07 | freemangordon | or v2l, not sure which layer |
| 04:02.16 | DocScrutinizer05 | ooh |
| 04:02.21 | DocScrutinizer05 | interesting |
| 04:02.54 | DocScrutinizer05 | so where's the "persistance storage"? |
| 04:02.58 | freemangordon | the same happens if you use man camera through gstreamer |
| 04:03.03 | freemangordon | *main |
| 04:03.22 | DocScrutinizer05 | weird |
| 04:03.35 | freemangordon | if you want good quality, you need to open the camera-ui, close it and then use gstreamer |
| 04:03.36 | DocScrutinizer05 | kernel module var area? |
| 04:03.44 | DocScrutinizer05 | gconf? |
| 04:03.53 | DocScrutinizer05 | cam chip registers themselves? |
| 04:04.07 | freemangordon | DocScrutinizer05: not sure, but I think it is kernel, as it saves the context on suspend and restores it on resume, iirc |
| 04:04.28 | freemangordon | the context == registers |
| 04:04.30 | DocScrutinizer05 | yep, so a modprobe -r should "fix" that, eh? |
| 04:04.45 | freemangordon | maybe, never tried |
| 04:04.59 | DocScrutinizer05 | IOW unloading the kernel driver module should kill qulaity again |
| 04:05.11 | freemangordon | :nod: |
| 04:05.25 | DocScrutinizer05 | we need sb to test this |
| 04:05.32 | freemangordon | sb? |
| 04:05.36 | DocScrutinizer05 | I never even noticed the effect to start with |
| 04:05.41 | DocScrutinizer05 | somebody |
| 04:05.51 | freemangordon | ever used the mirror app? |
| 04:05.55 | DocScrutinizer05 | yes |
| 04:06.11 | DocScrutinizer05 | and yes the quality is abysmal |
| 04:06.14 | freemangordon | for sure the quality is bad |
| 04:06.31 | DocScrutinizer05 | I never noticed it getting better, not to think of *how* to do that |
| 04:06.42 | DocScrutinizer05 | no video calls here |
| 04:06.51 | freemangordon | make a video call :) |
| 04:06.52 | freemangordon | aah |
| 04:06.59 | DocScrutinizer05 | never managed to do a single video call in my life |
| 04:07.21 | freemangordon | register 2 google accounts and call your PC from your n900 |
| 04:07.29 | freemangordon | or the opposite |
| 04:07.39 | freemangordon | video call that is |
| 04:07.49 | DocScrutinizer05 | I tried from one SIP client to another one on same account, but my SIP provider doesn't even support video calls at all |
| 04:07.59 | freemangordon | gtalk supports |
| 04:08.07 | DocScrutinizer05 | I for sure won't register a google account |
| 04:08.11 | freemangordon | as is skype :P |
| 04:08.22 | DocScrutinizer05 | no skype on my devices |
| 04:08.42 | DocScrutinizer05 | thus I said "we need somebody..." |
| 04:09.06 | DocScrutinizer05 | best somebody who actually noticed the improvement already |
| 04:09.09 | freemangordon | no options left then, but you can ply a bit with mplayer, afaik it should support camera properties |
| 04:09.14 | freemangordon | play |
| 04:09.29 | freemangordon | so you can tweak exposure etc from it |
| 04:09.36 | DocScrutinizer05 | sure, I know |
| 04:10.02 | freemangordon | btw what do you want to "test"? |
| 04:10.10 | DocScrutinizer05 | but I'd prefer to get the improvement anf reversal thereof by rmmod approved first |
| 04:10.15 | DocScrutinizer05 | ^^^ |
| 04:11.06 | freemangordon | use mplayer to put brightness/exposure to max, check the quality with mirror, rmmod, modprobe, check agaimn |
| 04:11.45 | DocScrutinizer05 | that would assume I see an improvement and I'd know to play with mplayer |
| 04:12.07 | DocScrutinizer05 | I want the effect as reported by dos getting checked via "rmmod" |
| 04:12.13 | DocScrutinizer05 | that's all |
| 04:12.36 | freemangordon | you'll see improvement, that is for sure, I already tried it an year or so ago :) |
| 04:12.55 | DocScrutinizer05 | once we know how that improvement works, we can think of proper initialization on modprobe |
| 04:13.09 | freemangordon | I even got mirror sources thinking to fix it, but I gave up as there were more interesting things to play with |
| 04:14.01 | DocScrutinizer05 | this shouldn't get done on a per-app basis. udev is the right place to invoke a post-modprobe configurator daemon |
| 04:14.45 | freemangordon | DocScrutinizer05: you can't, setting camera props should be done on as-needed basis |
| 04:14.58 | DocScrutinizer05 | this would fix _all_ usecases that forget to do proper init themselves |
| 04:15.27 | DocScrutinizer05 | sure, but it can't hurt to have optimized defaults |
| 04:15.41 | freemangordon | no, you can't know in advance what the light conditions will be when those broken apps are started |
| 04:15.59 | DocScrutinizer05 | obviously what modprobe resp kernel driver init gives you is suboptimal |
| 04:16.06 | freemangordon | the same for the resolution btw |
| 04:16.31 | freemangordon | the default that driver gives you, is everything set to min |
| 04:16.38 | freemangordon | inc resolution |
| 04:16.50 | freemangordon | which is sane IMO |
| 04:16.56 | DocScrutinizer05 | so what? since you can't know which light we will have, you configure the module to 1billion lux ambient in kernel init? |
| 04:17.06 | freemangordon | it is up to the application to decide how to use the camera |
| 04:17.19 | DocScrutinizer05 | that's insane approach |
| 04:17.41 | freemangordon | the option is to implement some "auto mode" in the driver |
| 04:17.48 | DocScrutinizer05 | every hardware should come up with semi-usable defaults, not any crap that leaves it semi-broken |
| 04:18.31 | DocScrutinizer05 | obviously frontcam startup defaults are unbearable for *every* usecase |
| 04:18.40 | freemangordon | yep |
| 04:18.47 | DocScrutinizer05 | they aren't optimized for *anything* |
| 04:19.19 | freemangordon | sure they aren't, but again, it is not the driver to guess what application wants to do |
| 04:19.26 | DocScrutinizer05 | so no matter for what you optinize them - nightview or flash use - OPTIMIZE THEM for something! |
| 04:19.33 | freemangordon | it is the application to tell the driver |
| 04:19.43 | DocScrutinizer05 | again, that's an insane rationale |
| 04:19.55 | freemangordon | could be, but this is what I think |
| 04:20.19 | DocScrutinizer05 | ok, what are the values you'd pick for defaults of frontcam? |
| 04:20.39 | DocScrutinizer05 | your birthday? |
| 04:20.50 | DocScrutinizer05 | NaN? |
| 04:20.51 | freemangordon | everything on min |
| 04:21.04 | DocScrutinizer05 | or something that at least *sometimes* works? |
| 04:21.13 | freemangordon | and this falls in your "sane defaults" category :) |
| 04:21.18 | DocScrutinizer05 | why not everything at max? |
| 04:21.24 | freemangordon | no reason |
| 04:21.29 | DocScrutinizer05 | no, it does NOT |
| 04:21.37 | freemangordon | that is why it is hard to define "sane default values" |
| 04:21.59 | DocScrutinizer05 | sane default values are what works best with the most common usecase |
| 04:22.17 | DocScrutinizer05 | it's not at all hard to define |
| 04:22.17 | freemangordon | the most common usecase for the front cam is video calling |
| 04:22.19 | freemangordon | ;) |
| 04:22.28 | DocScrutinizer05 | fine |
| 04:23.12 | chainsawbike | freemangordon, DocScrutinizer05, to add my 2c - the app _needs_ to be changing these as it is environment Dependant, but semi-usable default would be nice (if only for testing) |
| 04:23.16 | DocScrutinizer05 | hten make kernel module configue the chip to the values needed for video calling, on module init |
| 04:24.13 | DocScrutinizer05 | otherwise I insist in using MY birthday date for register init, not min, max, or freemangordon's birthday ;-P |
| 04:25.22 | freemangordon | chainsawbike: you can use V2L API to set the camera to whatever you like, V2L is still driver "layer" albeit not in the kernel |
| 04:25.45 | DocScrutinizer05 | that's all fine and would be sad if it wasn't like that |
| 04:25.59 | freemangordon | maybe V2L have a way to set some defaults, dunno |
| 04:26.12 | DocScrutinizer05 | but that doesn't change *anything* in the reasoning to get *sane* defaults on module init |
| 04:26.56 | kerio | i don't think you can have sane defaults |
| 04:27.10 | *** join/#maemo jeropun (~a@186.29.27.239) |
| 04:27.12 | kerio | camera settings depend on the outside world too much |
| 04:27.28 | DocScrutinizer05 | sure, we can easily do a helper that gets invoked by udev on modprobe and opens cam for 0.01s with correct parameters, exploiting gstreamer or whatever you see fit |
| 04:27.46 | DocScrutinizer05 | kerio: please read backscroll!!!! |
| 04:28.09 | freemangordon | DocScrutinizer05: and that would make absolutely no difference to now |
| 04:28.18 | DocScrutinizer05 | kerio: while you can't have sane defaults maybe, this is no exciuse to have MAD defaults |
| 04:28.49 | freemangordon | because I am saying that putting everything to min is best for me as I livo on the beach and use the cam only between 10 and 16 |
| 04:29.21 | DocScrutinizer05 | even then you can't use that default since it simply doesn't work |
| 04:30.10 | DocScrutinizer05 | it's a flaw of kernel module devels who simply didn't think of initializing their values to something semi-decent. Just like with current-max on LP5523 |
| 04:30.14 | freemangordon | DocScrutinizer05: and what about is someone changes those settings |
| 04:30.23 | freemangordon | is/if/ |
| 04:31.10 | DocScrutinizer05 | then they are changed? |
| 04:31.17 | DocScrutinizer05 | don't get you |
| 04:31.34 | freemangordon | but they are no more those "works for everyone" defaults |
| 04:31.46 | freemangordon | should we keep them or reset? |
| 04:31.51 | DocScrutinizer05 | DOENT work for everyone is what we got now |
| 04:32.07 | DocScrutinizer05 | aaah *now* I get it |
| 04:32.15 | DocScrutinizer05 | I'm talking about kernel init |
| 04:32.24 | freemangordon | DocScrutinizer05: see, it is not only the exposure etc, it is also the resolution |
| 04:32.34 | freemangordon | what is the best resolution? |
| 04:32.36 | DocScrutinizer05 | that's why I asked for checing if those persistent settings go away with rmmod |
| 04:33.12 | DocScrutinizer05 | when they vanish with rmmod you want have new sane ones with insmod |
| 04:33.19 | freemangordon | and not only the resolution, but framerate too |
| 04:33.29 | DocScrutinizer05 | yesyesyesyes |
| 04:33.42 | DocScrutinizer05 | all quite irrelevant |
| 04:33.55 | DocScrutinizer05 | every app is free to change that to whatever it needs |
| 04:34.05 | freemangordon | exactly |
| 04:34.13 | freemangordon | and not only free to, but have to |
| 04:34.15 | DocScrutinizer05 | I#m talking about the initial defaults |
| 04:34.19 | freemangordon | I know |
| 04:34.28 | *** join/#maemo Custodian (~Custodian@46.39.225.253) |
| 04:34.41 | DocScrutinizer05 | and those HAVE TO be saner than they are now, cause the ones we have now are defunct |
| 04:34.49 | chainsawbike | would set it to work under the ambient lighting of my workspace by default to make testing easy and call any application broken that did not adjust it for the current conditions |
| 04:35.02 | DocScrutinizer05 | chainsawbike: exactly |
| 04:35.17 | DocScrutinizer05 | since that's most likely the most common usecase anyway |
| 04:35.23 | freemangordon | But a camera application that simply starts a stream without giving the user a tool to control the camera is simply broken. IMO |
| 04:35.39 | DocScrutinizer05 | so what? |
| 04:35.48 | freemangordon | and I would call that WFM approach :P |
| 04:35.48 | DocScrutinizer05 | yes, it is |
| 04:36.17 | DocScrutinizer05 | I would call that a "let's punish them2 approach by the kernel driver devels |
| 04:36.23 | *** join/#maemo ZogG_laptop (~ZogG_lapt@212.199.182.172) |
| 04:36.26 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 04:37.16 | freemangordon | DocScrutinizer05: if we assume something is broken, I'd rather say it is V2L, not the module |
| 04:37.16 | DocScrutinizer05 | "ooh your PSU exploded? too bad, you shouldn't have activated it without proper config of mains power range before you do so" |
| 04:37.55 | freemangordon | DocScrutinizer05: on the opposite, keeping everything to min is the safest approach |
| 04:38.04 | DocScrutinizer05 | in my book every module should come up with sane safe working defaults |
| 04:38.22 | DocScrutinizer05 | safe for what, goddamn? |
| 04:38.27 | freemangordon | for your PSU |
| 04:38.36 | freemangordon | I took your example |
| 04:38.38 | DocScrutinizer05 | safe for making every crappy app fail epically |
| 04:39.00 | freemangordon | it is not the kernal that should babysit crappy apps |
| 04:39.09 | freemangordon | kernel even |
| 04:39.22 | DocScrutinizer05 | in my PSU example keeping mains voltage to min is a sure way to make the PSU explode ;-P |
| 04:40.35 | DocScrutinizer05 | freemangordon: you're arguing on a "let's punish them,CBA to init that to 100 instead of using the compiler default" approach |
| 04:41.24 | jonwil | hmmm, I recon I could clone libdevlock if it wasnt for the totally confusing function that actually stores the devicelock in CAL :P |
| 04:41.28 | DocScrutinizer05 | keeping everything at 0 on module init has ZILCH rationale nor benefit |
| 04:41.43 | freemangordon | DocScrutinizer51: if we apply "sane defaults" to the audio for example, what would be it? |
| 04:41.52 | DocScrutinizer05 | 0 |
| 04:42.11 | DocScrutinizer05 | except for one default volume path |
| 04:42.19 | freemangordon | exactly the same for the video |
| 04:42.24 | DocScrutinizer05 | no |
| 04:42.33 | DocScrutinizer05 | since video is a sensor, no actor |
| 04:42.50 | freemangordon | what about microphone? |
| 04:43.09 | freemangordon | should it be disabled or enabled? with what gain? |
| 04:43.38 | DocScrutinizer05 | obviously should be set to a sane boost level and gain to semidecently handel a 60dBm |
| 04:44.05 | DocScrutinizer05 | though that's ALSA stuff, not kernel module. And ALSA DOES that already |
| 04:44.23 | freemangordon | there is no "sane level" for sensors which vastly depend on the outside world conditions |
| 04:44.23 | DocScrutinizer05 | it restores last settings on boot time |
| 04:44.50 | DocScrutinizer05 | freemangordon: stop telling nonsense, of course there are settings that are more sane than others |
| 04:45.11 | freemangordon | WFM? |
| 04:45.12 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 04:45.48 | DocScrutinizer05 | when there is no "sane level2 in your book, then why arguing against my request to change those settings from 0 to maybe 100 or whatever I may come up with? |
| 04:46.05 | chainsawbike | freemangordon, yes it is very dependant on external factors but what is the harm in setting it up to work somewhere by default ( a dev workspace for example) |
| 04:46.17 | DocScrutinizer05 | exactly |
| 04:46.45 | DocScrutinizer05 | there *is* something like a "standard" environment |
| 04:47.13 | freemangordon | my point is - you can change the defaults to whatever you like (in the kernel), but broken apps are just that - broken apps, and it is not the kernel that sould fix them |
| 04:47.16 | DocScrutinizer05 | and a sensor should work OOTB for such standard environment |
| 04:47.35 | DocScrutinizer05 | SO WHAT?????? |
| 04:47.46 | DocScrutinizer05 | "punsih them!!"? |
| 04:47.55 | freemangordon | DocScrutinizer05: what is the standard environment for a handheld device? |
| 04:48.12 | DocScrutinizer05 | earth, 12 noon, aequator |
| 04:48.13 | freemangordon | DocScrutinizer05: exactly, punish them don't tolerate lazy developers |
| 04:48.15 | DocScrutinizer05 | FFS |
| 04:48.32 | DocScrutinizer05 | >.-( |
| 04:49.00 | freemangordon | comeon, setting camera properties is like 50 lines of code |
| 04:49.19 | DocScrutinizer05 | it's NOT "inside an atomic explosion" or "11km deep in marian trench" |
| 04:49.38 | DocScrutinizer05 | SO WHAT?????????????????????????? |
| 04:49.46 | chainsawbike | likes a dev workspace so you get something resembling a picture not garbage when you first init the camera, rather than wondering wtf the garbage you are getting is, and wasting time realizing it really is the camera output |
| 04:50.08 | DocScrutinizer05 | chainsawbike: ack |
| 04:50.15 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 04:51.22 | DocScrutinizer05 | freemangordon: and you wonder why lots of app devels and users think kernel devels are mad and assholes? |
| 04:51.30 | freemangordon | guys, mirror is not even setting the resolution, what "sane defaults" we talk about here |
| 04:51.54 | DocScrutinizer05 | I'm NOT talking about mirror app, at least |
| 04:51.58 | chainsawbike | freemangordon, i consider mirror _broken_ |
| 04:52.12 | DocScrutinizer05 | forget that friggin app |
| 04:52.28 | DocScrutinizer05 | I want a sensor to work OOTB, no matter how poorly |
| 04:52.43 | freemangordon | and that is what you have |
| 04:52.49 | DocScrutinizer05 | it makes no sense to initialize it to a state where it doesn't work at all |
| 04:52.55 | DocScrutinizer05 | NO |
| 04:53.10 | DocScrutinizer05 | definizely not true for frontcam |
| 04:53.25 | freemangordon | it works OOTB and if there is enough light around, you'll even see an image of youself |
| 04:53.35 | DocScrutinizer05 | bullshit |
| 04:54.00 | DocScrutinizer05 | meh, i'll patch that shite myself and upstream it. Don't need you for that |
| 04:54.12 | chainsawbike | DocScrutinizer05, enough light... |
| 04:56.06 | DocScrutinizer05 | setting everything to zero is definitely the most idiotic setting you could find for cam |
| 04:56.23 | freemangordon | DocScrutinizer05: try it (upstreaming) but I bet you'll get exactly the same responce as mine :) |
| 04:56.37 | DocScrutinizer05 | even setting everything to max sensitivity is better than that |
| 04:57.09 | freemangordon | though... who knows |
| 04:57.18 | jonwil | wonders if reverse engineering libdevlock and devlocktool is worth the effort... |
| 04:58.22 | DocScrutinizer05 | freemangordon: I bet against that, since I can support my point using the cam manuf's suggested range of opperation values from datasheet, and setting values for the module somewhwre to the arithmetic or geometric middle of those is for sure a more sound approach than setting everything to zero |
| 04:58.31 | jonwil | probably not :) |
| 04:58.49 | freemangordon | DocScrutinizer05: ok |
| 04:59.09 | freemangordon | what about resolution and framerate? |
| 04:59.31 | DocScrutinizer05 | you said yourself it's usually used for video |
| 04:59.53 | freemangordon | frontcam supports 180x120, 320x240 and 640x480 |
| 05:00.02 | freemangordon | not sure about the framerates |
| 05:00.05 | DocScrutinizer05 | that makes VGA 25fps in my book, nit 0 fps and 0 resolution |
| 05:00.49 | freemangordon | not sure n900 can handle VGA@25fps video streaming |
| 05:00.50 | DocScrutinizer05 | and of course you configure sensors to their full capability, not to sth downsized |
| 05:01.36 | *** join/#maemo LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 05:01.38 | freemangordon | skype uses 180x120, gtalk 320x240 iirc |
| 05:01.41 | DocScrutinizer05 | when N900 can't support 25fps then you obviously set it to the max it *can* support |
| 05:02.03 | freemangordon | and ofc it depends on what the other side can handle |
| 05:02.29 | freemangordon | and iirc ususlly video call is @ 12fps |
| 05:02.35 | DocScrutinizer05 | the sensor shall work by the most simple means, like "cat $input >$output" |
| 05:03.05 | DocScrutinizer05 | and it should provide the best it can, in that mode |
| 05:03.39 | DocScrutinizer05 | this is a general rule for all sensors |
| 05:04.12 | DocScrutinizer05 | so max resolution, max sampling rate, max sensitivity and so on |
| 05:04.13 | freemangordon | DocScrutinizer05: maybe you should check what ISP in OMAP is |
| 05:05.09 | DocScrutinizer05 | maybe I should stop arguinfg with somebody who thinks "punish them" is a good approach since it doesn't require the kernel devel to muse about sane defaults |
| 05:05.15 | freemangordon | it is not only the sensor (and its module), there is dedicated HW who does exactly what you need, it even gives yout the histogram |
| 05:06.04 | DocScrutinizer05 | and I couldn't care less about that last point of yours since it won't change my notion on this |
| 05:06.19 | freemangordon | ok, lets agree to disagree :) |
| 05:06.38 | DocScrutinizer05 | setting everything to zero just because compiler initializes vars to zero is a poor and silly approach |
| 05:06.55 | DocScrutinizer05 | pathetic approach even |
| 05:08.04 | DocScrutinizer05 | as soon as you start to think about that, you easily find ~65534 better values to initialize than just zero |
| 05:10.23 | DocScrutinizer05 | and probably any optiomum is anywhere between 500 and 30000 |
| 05:11.21 | DocScrutinizer05 | definitely zero is no optimum, not even a lame compromise, not even any rationale at all to support that approach. Except "let's punish them" |
| 05:13.17 | DocScrutinizer05 | what is the default baudrate of an UART? zero? |
| 05:14.07 | freemangordon | 9600 iirc, but it is not set by the kernel UART driver iirc |
| 05:14.36 | DocScrutinizer05 | sure you *should* use stty to configure the 8n1 and 9600 or 19200 or 64k or whatever you want. but ZERO for sure is the most idiotic value for UART baudrate to have as default. Same for camera |
| 05:15.26 | freemangordon | DocScrutinizer05: it is not UART driver that sets the default, get my point? |
| 05:15.55 | freemangordon | afaik it is tty driver |
| 05:16.10 | DocScrutinizer05 | uhuh, so who else is setting uart to a particular speed? is it random? |
| 05:16.41 | DocScrutinizer05 | there MUST be some speed the UART is set to when it gets loaded |
| 05:17.04 | DocScrutinizer05 | and I doubt you even *can* set that to zero |
| 05:17.06 | freemangordon | it is passed through cmdline |
| 05:17.36 | DocScrutinizer05 | nonsense, you *can* pass that via cmdline. That's not any default though |
| 05:17.50 | DocScrutinizer05 | meh, I'm tired of this discussion |
| 05:20.59 | *** join/#maemo _jester_ (~user@host-106-net-118-160-119.mobilinkinfinity.net.pk) |
| 05:22.39 | *** join/#maemo hardfalcon (~hardfalco@f049233129.adsl.alicedsl.de) |
| 05:23.07 | *** join/#maemo triggerhappy (~quassel@112.209.10.184) |
| 05:26.36 | DocScrutinizer05 | (just on a sidenote: for UARTs there seem to be ~4 "sane" defaults: 300, 1200. 9600, 19200. No kernel driver or whoever will initialize a UART to 120, 600, 38400 or whatever) |
| 05:27.43 | DocScrutinizer05 | these values have historical and practical reasons, and they have sound rationale why they are used |
| 05:29.36 | DocScrutinizer05 | for every sensor you can find similar reasoning why you should use a certain (range of) values for module init default |
| 05:30.08 | DocScrutinizer05 | I honestly doubt zero for all values of a camera has *any* such sound rationale |
| 05:31.47 | DocScrutinizer05 | e.g stabdard PAL or NTSC or VGA would be a sane fallback and default |
| 05:33.12 | DocScrutinizer05 | and a exposure that somehow meets a normal daylight outside situation |
| 05:34.20 | DocScrutinizer05 | a less crappy chip would automatically set those values on reset |
| 05:34.42 | DocScrutinizer05 | in taht case the kernel module usually wants to just keep whatever the chip came up with |
| 05:35.22 | DocScrutinizer05 | in other cases manufactuers clearly state defaults |
| 05:36.33 | DocScrutinizer05 | when they don't then they state recommended operating conditions which usually are ranges and you want to pick a value for defaults that is "middle" of the range by whatever algo you use to find that middle |
| 05:37.01 | DocScrutinizer05 | for other sensors you want them to come up with maximum sensitivity |
| 05:37.43 | DocScrutinizer05 | actors you usually make come up with actual operation set to inactive, and limits set to those the hw manufacturer specified |
| 05:38.20 | DocScrutinizer05 | but you ALWAYS can find a better and less embarrassing (for your reputation as developr) value for defaults, than simply "all zero" |
| 05:40.49 | DocScrutinizer05 | there are situations where you don't want to come up with any sane working default at all - e.g. firmware for WLAN chip. But that's another topic not applicable for simple settings like exposure and ISO and framerate/resolution of a camera |
| 05:49.23 | DocScrutinizer05 | btw I never looked in V4L2 or the camdriver kernel API, but I could figure there are mandatory parameters you _must_ pass to an open(). When e.g resolution was one of those mandatory parameters then any default for resolution is moot anyway. |
| 05:50.29 | DocScrutinizer05 | you don't have a default for filename on an open() either |
| 05:54.15 | *** join/#maemo XATRIX (~xatrix@77.88.209.171) |
| 06:02.49 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 06:04.49 | *** join/#maemo int_ua (~int_ua@ip-602f.proline.net.ua) |
| 06:06.15 | *** join/#maemo FlameReaper (~assassin@175.138.168.175) |
| 06:07.33 | *** join/#maemo dafox (~dafox@88.128.80.6) |
| 06:23.15 | *** join/#maemo XATRIX (~xatrix@77.88.209.171) |
| 06:27.24 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 06:28.58 | *** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 06:50.51 | jonwil | bah this is annoying |
| 06:53.03 | *** join/#maemo topro (~topro@host-62-245-142-50.customer.m-online.net) |
| 07:01.32 | *** join/#maemo zammy (~sammy@ppp-154-184.98-62.inwind.it) |
| 07:12.25 | *** join/#maemo shentey (~shentey@g231220218.adsl.alicedsl.de) |
| 07:20.08 | DocScrutinizer05 | hm? |
| 07:20.11 | *** join/#maemo shentey (~shentey@g231220218.adsl.alicedsl.de) |
| 07:23.15 | zammy | morning |
| 07:30.38 | *** join/#maemo Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 07:35.29 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 07:36.42 | *** join/#maemo maybeHere (~cl@p5B165F25.dip0.t-ipconnect.de) |
| 07:37.23 | *** join/#maemo edheldil (~edheldil@2001:1488:ac14:1400:222:19ff:fe31:415e) |
| 07:42.32 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 07:44.55 | jonwil | trying to figure out the libdevlock change_devlock_code function and its so far eluded my ability to reverse engineer it (even with an x86 binary to play with) |
| 07:45.14 | jonwil | its doing something really funky for generating the salt and I cant work it out |
| 07:47.43 | *** join/#maemo M4rtinK (~M4rtinK@ip-89-177-124-88.net.upcbroadband.cz) |
| 08:02.03 | DocScrutinizer05 | haha |
| 08:03.30 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 08:03.36 | DocScrutinizer05 | you don't need to understand how it generates salt. You just need to generate own salt and understand how salt is added to the hash, so you can verify existing hashes incl salt |
| 08:04.09 | DocScrutinizer05 | since jack-the-ripper can crack the hash, I guess salt is added in a pertty standard way |
| 08:04.23 | DocScrutinizer05 | err johm-the-ripper |
| 08:04.29 | DocScrutinizer05 | meh! |
| 08:08.38 | DocScrutinizer05 | have you already found the if (hash == "12345") then return 0; ? |
| 08:08.46 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 08:09.43 | DocScrutinizer05 | funny enough the original default hash for default lockcode 12345 is also 12345 ;-P |
| 08:10.34 | FatPhil | yeah, ignore salt generation. A counter is just as salty as a something random |
| 08:11.40 | DocScrutinizer05 | for device lockcode for sure |
| 08:11.57 | DocScrutinizer05 | it's a hoax in the end, anyway |
| 08:12.43 | FatPhil | And as the salt must be stored in the clear, it adds very little security to what's intrinsically a small brute force problem |
| 08:12.51 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 08:14.43 | *** join/#maemo LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 08:19.33 | DocScrutinizer05 | yep. Salt only got invented to make rainbow table attacks harder |
| 08:20.10 | DocScrutinizer05 | and maybe to hide password changes |
| 08:20.12 | *** join/#maemo AD-N770 (~jep@o.bcn.fluendo.net) |
| 08:20.56 | DocScrutinizer05 | in the sense that you could use same password but still a different hash each day |
| 08:25.16 | Apic | A splendid wonderful fine Morning (UGT) on this gorgeous Boomtime! |
| 08:27.41 | merlin1991 | boomtime? |
| 08:29.19 | Apic | Discordian Weekday |
| 08:29.29 | Apic | Read http://principiadiscordia.com |
| 08:42.12 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 08:43.19 | FatPhil | Salt predates rainbow tables by decades |
| 08:44.21 | sono | splendid. |
| 08:45.08 | sono | would rather go outside and play sink |
| 08:45.23 | sono | eyes the pond |
| 08:45.45 | sono | eyes the headachy embedded devices from hell next to his desk |
| 08:45.48 | sono | yea, sink sounds good |
| 08:48.46 | sono | hands Apic a PIC32 based industrial thing with an oldschool LCD. a JTAG cable dangles from it. |
| 08:48.52 | sono | nods at the pond |
| 08:49.11 | sono | grabs something else that looks like the unholy union of an acer netbook and an ipad |
| 08:49.41 | sono | yells something undiscernable and PULLs |
| 08:49.47 | Apic | Thank You very much! |
| 08:49.49 | sono | *splash* |
| 08:50.09 | Apic | Shift to the Left, shift to the Right, push up, pull down, Byte, Byte, Byte! |
| 08:50.18 | sono | =) |
| 08:50.25 | Apic | \o\ /o/ ^o^ ,o, o< o< o< |
| 08:57.20 | *** join/#maemo eMHa_ (~mh@nat.de.netviewer.com) |
| 08:59.12 | *** join/#maemo rcg (~rcg@2a02:908:e253:51e4:76de:2bff:fe08:7809) |
| 09:00.57 | *** join/#maemo marainein (~net@2001:388:608c:6cb5:34b8:6702:7ab7:3d8e) |
| 09:06.41 | FatPhil | Drink all the booze, hack all the stuff? |
| 09:09.47 | Apic | Do You know Operation Swordfish, the Movie? |
| 09:09.57 | Apic | Log on, hack in, go anywhere, steal everything! |
| 09:12.09 | psycho_oreos | What a horrid movie that was. |
| 09:12.23 | Apic | ;-) |
| 09:12.32 | Apic | I liked it. |
| 09:20.46 | psycho_oreos | ._." there was simply too much blockbuster crap compared to what infosec was all about. |
| 09:21.03 | sono | popular movies are generally quite horrid. if some random persons likes a movie, that actually increases the odds that it's quite meh. |
| 09:21.27 | sono | random persons on average are quite meh. |
| 09:21.34 | sono | or one could simply say, |
| 09:21.37 | sono | law of averages |
| 09:21.40 | sono | and be done |
| 09:21.48 | psycho_oreos | It's more apparent if one has underlying knowledge of what the theme of the movie is trying to portray. |
| 09:22.19 | sono | i haven't seen it, but i can imagine. |
| 09:22.28 | sono | did they create a gui in visual basic? |
| 09:23.26 | psycho_oreos | I read in reader's digest awhile ago of some guy whom collect's spy paraphernalia. When asked how would the James Bond do in real world, he quoted from a ex KGB spy stating the real James Bond would not last in the spy world for more than 4 minutes or something. |
| 09:23.56 | psycho_oreos | I actually don't want to think about swordfish, I could imagine swordfish would be interesting is if I was stoned. |
| 09:24.06 | sono | surely he meant "before being fired" |
| 09:24.42 | psycho_oreos | No, probably before James Bond dies because he would be outsmarted by real spies probably. |
| 09:24.51 | sono | well if you're stoned, gravity is a much better movie to begin with |
| 09:24.57 | sono | real spies don't go around killing each other |
| 09:25.04 | psycho_oreos | Exactly. |
| 09:25.18 | psycho_oreos | Well I haven't watched gravity yet anyway. |
| 09:25.23 | sono | not as a day to day practice anyway. |
| 09:25.29 | sono | i don't doubt it has happened in the past. |
| 09:25.53 | psycho_oreos | The ex-KGB guy quoted that when spies pulls out their gun, intelligence ends. |
| 09:25.53 | jonwil | Gravity wasn't bad actually |
| 09:26.02 | sono | but there are some good boooks about the history of the services if you're in for a long flight or something. |
| 09:26.09 | sono | no need to rely on holywood. |
| 09:26.45 | psycho_oreos | Actually it's a little appealing if movies were to be based on more factual stuff rather than sci-fi crap and overexaggeration. |
| 09:27.30 | psycho_oreos | Kids these days playing with real pentesting tools used by professionals thinking they are the bomb but have no actual clue let alone the common sense when it comes to proper pentesting. |
| 09:27.35 | sono | gravity is a lot of action, and of course it's highly unrealistic as far as the entire story goes. but it somehow manages to take you along with it, and manages to rarely be outrageously impossible. |
| 09:27.40 | sono | so as far as blockbusters go, it is excellent |
| 09:28.04 | sono | and it has all the magic |
| 09:28.17 | sono | and a good arrangement, too |
| 09:28.21 | sono | and acting! |
| 09:28.22 | psycho_oreos | Like Harry Potter? |
| 09:28.25 | sono | idk |
| 09:28.27 | psycho_oreos | ._. |
| 09:29.08 | sono | magic = mood establishment etc pp |
| 09:29.28 | sono | i'm sure there are filmologists who can explain all the magic. |
| 09:29.34 | sono | i am not one. |
| 09:29.51 | psycho_oreos | Kind of like creative thinking, but in hollywood sense it would be probably more closely related into over-exaggeration of stated facts. |
| 09:30.12 | psycho_oreos | Neither am I, I just get annoyed thinking the likes of swordfish. |
| 09:30.39 | psycho_oreos | If someone were to tie swordfish with movies about IT security I'd lart them for that. |
| 09:31.09 | sono | points at oreos "he knows how to lart" |
| 09:31.17 | sono | so oldschool |
| 09:31.42 | sono | is young enough to only know the term from reading the jargon file when he was 16. |
| 09:32.37 | sono | and i'm 37! |
| 09:33.04 | sono | well i am also contiental so maybe the slang is just different |
| 09:33.13 | sono | but i don't think i have heard someone use the term in 5 years or so |
| 09:37.10 | *** join/#maemo eMHa_ (~mh@nat.de.netviewer.com) |
| 09:40.21 | Veggen | sono: I'm 42, and I'm old enough to have made it into the jargon file ;) (check http://catb.org/jargon/html/meaning-of-hack.html, towards the bottom) |
| 09:41.57 | psycho_oreos | is 29 but doesn't care about using old terminologies. :p |
| 09:42.39 | *** join/#maemo Venusaur (~wdwrf@wikipedia/Antonio-Lopez) |
| 09:48.40 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 09:49.59 | *** join/#maemo unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
| 09:51.14 | *** join/#maemo edheldil (~edheldil@2001:1488:ac14:1400:222:19ff:fe31:415e) |
| 09:57.53 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 10:13.55 | *** join/#maemo RP_ (~richard@93-97-173-237.zone5.bethere.co.uk) |
| 10:24.46 | *** join/#maemo foo` (~user@lapserv.damtp.cam.ac.uk) |
| 10:27.28 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 10:33.26 | *** join/#maemo tzafrir (~tzafrir@local.xorcom.com) |
| 10:43.03 | *** join/#maemo norrsken (~quassel@f049126018.adsl.alicedsl.de) |
| 10:45.15 | merlin1991 | ~lart sono |
| 10:45.15 | infobot | lowers sono's priority |
| 10:46.54 | FatPhil | I've fallen into the habit of always doing an ls -lart when I don |
| 10:47.23 | FatPhil | t have any reason not to |
| 10:48.44 | *** join/#maemo Pali (~Pali@Maemo/community/contributor/Pali) |
| 11:07.07 | *** join/#maemo psychologe (~user@58.243.254.238) |
| 11:24.29 | *** join/#maemo kolp (~quassel@212.255.253.143) |
| 11:31.49 | *** join/#maemo lizardo (lizardo@nat/indt/x-gzqqxcapvuazcllj) |
| 11:41.43 | DrCode | hi all |
| 11:41.45 | DrCode | can I use backupmenu with microsd ext2? |
| 11:41.47 | DrCode | I want to backup my maemo |
| 11:44.34 | Apic | Dunno, just try ;-) |
| 11:44.41 | Apic | Not much can go wrong |
| 11:51.07 | *** join/#maemo joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 12:04.54 | *** join/#maemo uen| (~uen@p5DCB27C8.dip0.t-ipconnect.de) |
| 12:21.29 | *** join/#maemo YnG (~YnG@213.158.217.97.pat.umts.dynamic.t-mobile.pl) |
| 12:28.20 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 12:32.31 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 13:03.40 | *** join/#maemo konelix (~konelix@190.148.67.38) |
| 13:09.20 | *** join/#maemo wmarone__ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 13:13.35 | *** join/#maemo x29a (~x29a@unaffiliated/x29a) |
| 13:13.45 | *** join/#maemo Veggen (~vegard@vegard.engen.priv.no) |
| 13:17.39 | *** join/#maemo pcfe (~pcfe@host86-156-27-137.range86-156.btcentralplus.com) |
| 13:20.45 | *** join/#maemo drathir (~kamiljk8@s51.linuxpl.com) |
| 13:23.48 | *** join/#maemo KhertanAtwork (~KhertanAt@nax2.naxos-fr.net) |
| 13:36.04 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 13:50.44 | *** join/#maemo otep_ (~quassel@27.126.153.141) |
| 14:13.59 | *** join/#maemo trx (ns-team@212.200.199.75) |
| 14:14.00 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 14:21.25 | *** join/#maemo shentey (~shentey@wlan-141-23-77-55.tubit.tu-berlin.de) |
| 14:24.08 | DocScrutinizer05 | ~lart sono |
| 14:24.08 | infobot | acting on orders from an unspecified client drags sono into court suing for $200 million |
| 14:24.24 | *** join/#maemo shentey (~shentey@wlan-141-23-77-55.tubit.tu-berlin.de) |
| 14:24.31 | Pali | who is sono? |
| 14:24.52 | DocScrutinizer05 | [2013-10-14 11:31:42] * sono is young enough to only know the term from reading the jargon file when he was 16. |
| 14:25.54 | DocScrutinizer05 | ooh, merlin1991 beaten me to it ;-P |
| 14:26.22 | *** join/#maemo ZogG_laptop (~ZogG_lapt@109.64.178.212) |
| 14:26.22 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 14:37.04 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 14:39.02 | *** join/#maemo sq-one (~sq-one@p549A9D50.dip0.t-ipconnect.de) |
| 14:39.25 | *** join/#maemo shentey (~shentey@wlan-141-23-77-55.tubit.tu-berlin.de) |
| 14:41.59 | *** join/#maemo cybrNaut (cybrNaut@unaffiliated/cybrnaut) |
| 14:54.48 | *** join/#maemo FlameReaper (~assassin@175.138.168.175) |
| 14:55.53 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 14:59.01 | *** join/#maemo SmilyOrg (Smily@BSN-182-183-170.dial-up.dsl.siol.net) |
| 15:01.02 | *** join/#maemo kolp_ (~quassel@212.255.126.239) |
| 15:07.26 | sono | Veggen: vegard? =) hey that's new. i didn't even know about it. |
| 15:07.26 | *** join/#maemo NIN101 (~NIN@p5DD28406.dip0.t-ipconnect.de) |
| 15:07.30 | sono | neat |
| 15:07.40 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 15:08.13 | zammy | guys meybe I will install the archlinux system on my n900 |
| 15:08.26 | sono | Veggen: does this mean you lost 5 pidgeons? =D |
| 15:08.37 | jonwil | Zammy: I doubt you can do that and have a working device |
| 15:08.48 | jonwil | Not if you want to make phone calls, use data, send SMS etc |
| 15:08.48 | sono | jonwil: nice constraint there. |
| 15:09.00 | freemangordon | depends on the definition of "working" :) |
| 15:09.31 | zammy | the I mean I am going to install in my next future the ArchLinuxARM-N900-2013.02-rootfs.tar.gz |
| 15:09.53 | jonwil | I doubt ArchLinux has working battery charging either |
| 15:10.00 | freemangordon | jonwil: it has |
| 15:10.06 | freemangordon | pali's drivers |
| 15:10.08 | jonwil | ok |
| 15:10.21 | freemangordon | afaik :) |
| 15:10.29 | zammy | but I must buy first a microsd to it |
| 15:10.30 | zammy | for it |
| 15:11.10 | zammy | ofc testing before using it definately |
| 15:12.09 | zammy | is it faster right? |
| 15:12.58 | zammy | and I mind to use it mainly for command lines usage... that's pretty cool |
| 15:13.30 | jonwil | god reverse engineering hildon status bar gadgets is hard, especially when they use like half of GTK and have a class size of 0x1A0 and a private class size of 0x3C |
| 15:14.47 | zammy | anyway I did not find any video around googling about this archlinux on n900 |
| 15:15.49 | jonwil | oh wait the 0x1A0 is misleading since the class is entirely composed of a HDStatusMenuItem structure |
| 15:16.25 | zammy | just some in which you can see the archlinux os for computers emulated like debian img... nothing about this ArchLinuxARM-N900 |
| 15:16.58 | jonwil | still, 0x3C of private class data is going to be annoying |
| 15:20.45 | freemangordon | jonwil: (0xA10 size) - most probably the first member variable is some GObjectClass descendant type |
| 15:20.57 | freemangordon | *0x1A0 |
| 15:20.58 | jonwil | yes it is |
| 15:21.04 | jonwil | Its a HDStatusMenuItem |
| 15:21.14 | freemangordon | :nod: |
| 15:21.39 | freemangordon | which leaves you woth only a couple of members to find |
| 15:21.44 | freemangordon | *with |
| 15:22.28 | freemangordon | jonwil: is ther x86 binary? |
| 15:22.33 | freemangordon | or only ARM |
| 15:22.44 | jonwil | no x86 unfortunately |
| 15:22.55 | freemangordon | yeah, thats bad |
| 15:27.05 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 15:30.12 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 15:35.55 | jonwil | anyone know what /dev/ttyGS* might be? |
| 15:37.20 | kerio | gadget serial? |
| 15:37.48 | jonwil | quite possible |
| 15:40.30 | zammy | so... what about this ArchLinuxARM-N900? |
| 15:40.53 | zammy | I did not understand in tecnical language how is it ... is it bad or good? |
| 15:40.57 | jonwil | I am about convinced that it would be easier for someone with GTK skills to write a totally new hildon-status-bar-usb (figuring out all the non-UI things the stock one is doing should be fairly simple from what I can see) than it would be to try and reverse engineer all the GUI bits in the stock one |
| 15:41.05 | jonwil | mostly because there is no x86 binary for the stock one |
| 15:41.42 | jonwil | and that the UI is more complex than it would appear to be |
| 15:42.30 | *** join/#maemo pcfe (~pcfe@212.183.128.91) |
| 15:48.56 | jonwil | most of the other status-bar-widget clones arent 1:1 clones, they are also only functional clones |
| 15:49.16 | jonwil | wonders if there is a GTK book that is as good as his QT book |
| 15:50.02 | MohammadAG | Brought to you by the largest Israeli bank's website |
| 15:50.05 | MohammadAG | To view our Web site you may use , Internet Explorer version 6 or above or Netscape version 7 or above. |
| 15:51.39 | zammy | ... anyway I want to see a faster n900... this maemo is too slow now.... |
| 15:52.00 | zammy | to me it is maybe too tasks simultaneous... |
| 15:59.03 | mashina | if they ask for netscape lie |
| 15:59.30 | MohammadAG | wtf is CLS |
| 15:59.37 | jonwil | My bank is great, not only does it have a mobile site that works great on the N900 but their main desktop online banking site works on every browser I have tried (I cant find the cite right now but I remember seeing something in their online banking info that mentioned Linux by name) |
| 15:59.38 | MohammadAG | I hate banks |
| 15:59.53 | MohammadAG | I want the IBAN number |
| 16:00.39 | MohammadAG | I can't figure out which to use http://www.theswiftcodes.com/israel/ |
| 16:01.32 | jonwil | Of course this is a small bank owned by its members (it used to be a credit union until the rules changed and it became a bank) |
| 16:01.52 | jonwil | and as such, they have none of the usual suckiness of a bank |
| 16:02.36 | *** join/#maemo FlameReaper (~assassin@175.138.168.175) |
| 16:10.13 | *** join/#maemo triggerhappy (~quassel@112.209.10.184) |
| 16:13.03 | jonwil | pali: ping |
| 16:13.05 | *** join/#maemo MohammadAG_ (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 16:18.14 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 16:18.18 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 16:19.35 | *** join/#maemo arcean (~arcean@aclq195.neoplus.adsl.tpnet.pl) |
| 16:30.17 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 16:34.22 | *** join/#maemo psychologe (~user@58.243.254.147) |
| 16:46.03 | *** join/#maemo triggerhappy (~quassel@112.209.10.184) |
| 16:47.10 | *** join/#maemo nmmm (~quassel@85.130.92.216) |
| 16:48.51 | *** join/#maemo dafox (~dafox@88.128.80.6) |
| 16:51.57 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 16:52.27 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 16:53.10 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 16:55.15 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 16:55.47 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 17:00.59 | *** join/#maemo tanty (~agomez@cs78210056.pp.htv.fi) |
| 17:02.13 | *** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa) |
| 17:09.17 | *** join/#maemo sq-one (~sq-one@p549a9d50.dip0.t-ipconnect.de) |
| 17:10.58 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 17:20.54 | *** join/#maemo hardfalcon (~hardfalco@f049233129.adsl.alicedsl.de) |
| 17:31.34 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 17:32.36 | *** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-58c0fc-218.dhcp.inet.fi) |
| 17:42.37 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 17:46.39 | *** join/#maemo nmmm (~quassel@85.130.92.216) |
| 17:53.13 | *** join/#maemo node00 (~node00@host86-180-158-155.range86-180.btcentralplus.com) |
| 17:58.14 | *** join/#maemo discopig (~discopig@unaffiliated/discopig) |
| 18:00.08 | *** join/#maemo HylianSavior (~hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 18:01.53 | *** join/#maemo frafl (~Thunderbi@e178071089.adsl.alicedsl.de) |
| 18:03.34 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 18:11.01 | *** join/#maemo jrocha (~JRocha@AAnnecy-651-1-59-183.w86-209.abo.wanadoo.fr) |
| 18:13.14 | *** join/#maemo shentey (~shentey@e179039222.adsl.alicedsl.de) |
| 18:17.22 | *** join/#maemo Pali (~Pali@Maemo/community/contributor/Pali) |
| 18:22.10 | *** join/#maemo piggz (~piggz@host-92-18-173-77.as13285.net) |
| 18:26.33 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 18:44.03 | *** join/#maemo arcean (~arcean@aclq195.neoplus.adsl.tpnet.pl) |
| 18:58.57 | *** join/#maemo _rd_ (~rd@p57B494D2.dip0.t-ipconnect.de) |
| 19:05.44 | Macer | hm |
| 19:05.55 | Macer | i'm having a hell of a time getting the manual dns to work in maemo |
| 19:07.38 | Macer | setting the ip/dns doesn't seem to work well |
| 19:08.24 | Macer | facepalm |
| 19:08.33 | Macer | if i set the ip and dns manually it won't work :-/ |
| 19:08.40 | Macer | why must everything use dnsmasq? |
| 19:09.31 | Macer | i've no idea what is going on here but the n900 has gone astray |
| 19:09.37 | *** join/#maemo teotwaki (~teotwaki@Maemo/community/contributor/crashanddie) |
| 19:11.32 | Pali | Macer: you need to configure ip/dns in icd2 configuration/gconf |
| 19:11.45 | Pali | Macer: Maemo using dnsmasq for caching |
| 19:12.41 | Pali | it speed up dns resolving, because lot of mobile operators have slow recursive dns servers with slow dns responce |
| 19:14.27 | Macer | i guess. i'm having problems with my new install with tomato |
| 19:14.41 | Macer | and the n900 seems to be the only device with me about to rip my hair out |
| 19:14.53 | Macer | my problem is i have a dns on a local 192. subnet |
| 19:15.16 | Macer | hm |
| 19:15.19 | Macer | brb |
| 19:15.50 | Defiant | Macer: yeah..had to modify my maemo a bit for lan dns resolution |
| 19:16.55 | Macer | oh |
| 19:17.01 | Macer | yeah it doesn't seem to be working out too well :-/ |
| 19:17.11 | Macer | i figured it was just a matter of unchecked automatic resolution |
| 19:17.13 | Macer | in advanced |
| 19:17.16 | Macer | and setting the ip |
| 19:17.23 | Macer | but it doesn't seem to be working out at all for whatever reason |
| 19:17.24 | Defiant | in my case it didn't append the suffix |
| 19:17.27 | Macer | and the wifi network seems totally broken |
| 19:18.06 | Defiant | broken? |
| 19:18.21 | Macer | oh! |
| 19:18.25 | Macer | i think i know the problem... |
| 19:19.16 | *** join/#maemo YnG (~YnG@213.158.217.127.pat.umts.dynamic.t-mobile.pl) |
| 19:21.34 | Macer | well.. how about that |
| 19:26.27 | Macer | hm |
| 19:26.38 | Macer | i think the problem is that the dhcpd on the router is sending the gateway as itself |
| 19:28.53 | *** part/#maemo YnG (~YnG@213.158.217.127.pat.umts.dynamic.t-mobile.pl) |
| 19:34.55 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 19:38.13 | *** join/#maemo uen (~uen@p5DCB39ED.dip0.t-ipconnect.de) |
| 19:42.56 | *** join/#maemo Macer (mace@scientiam.org) |
| 19:42.59 | Macer | finally |
| 19:43.01 | Macer | figured it out |
| 19:46.08 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 19:51.22 | *** join/#maemo RiD (Ghost@2.83.4.195) |
| 19:56.47 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 19:56.47 | *** join/#maemo Kabouik (~quassel@51.154.136.88.rev.sfr.net) |
| 19:58.30 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 20:02.43 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 20:05.55 | *** join/#maemo YnG (~YnG@213.158.216.236.pat.umts.dynamic.t-mobile.pl) |
| 20:08.14 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 20:22.03 | DrCode | hi all |
| 20:22.07 | DrCode | I have setup apn and mms |
| 20:22.38 | DrCode | can I use both mms and apn in single connection? |
| 20:23.12 | DrCode | I mean 3g data and mms in single connection ? |
| 20:29.00 | *** join/#maemo valerius (~user@85.26.180.129) |
| 20:40.05 | *** join/#maemo M4rtinK (~M4rtinK@ip-89-177-124-88.net.upcbroadband.cz) |
| 20:42.09 | ShadowJK | Well, the grass isn't that much greener on the other side |
| 20:42.23 | ShadowJK | Looks like ZTE's firefox phone is "abandoned" after ~3 months :) |
| 20:42.49 | MohammadAG | heh |
| 20:43.18 | MohammadAG | an Ubuntu ZTE phone might work |
| 20:43.34 | MohammadAG | the Edge looked nice :/ |
| 20:43.45 | MohammadAG | DrCode, why would you do that? |
| 20:43.54 | ShadowJK | They called it "ZTE Open", and included something saying something like "If you know how to code web, you know how to code firefox, take back your freedom!" |
| 20:44.09 | ShadowJK | Then they locked it down, locked the bootloader, etc |
| 20:44.29 | MohammadAG | not unlockable? |
| 20:44.51 | ShadowJK | There's a kernel exploit allegedly |
| 20:44.59 | MohammadAG | still better than samsung I guess |
| 20:45.30 | ShadowJK | Ubuntu ZTE would have the same problem, if ZTE shipped it without a working sudo/su or root account, and with locked loader, etc :) |
| 20:47.35 | MohammadAG | seen the Samsung efuse stuff? |
| 20:47.35 | MohammadAG | back when the S2 was out they touted openness |
| 20:47.43 | MohammadAG | even sent Cyanogen a device |
| 20:48.18 | MohammadAG | now they include an efuse that blows when you root it (Note 3) |
| 20:48.50 | MohammadAG | that decides whether or not you get hardware warranty |
| 20:49.03 | raccoon_ | wtf |
| 20:49.04 | MohammadAG | which with Apple or Nokia you might not need |
| 20:49.08 | raccoon_ | MohammadAG: got any more info on that? |
| 20:49.22 | MohammadAG | sure, everyone knws about it |
| 20:49.33 | raccoon_ | i seem to have missed the news |
| 20:49.35 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 20:50.53 | raccoon_ | ok got some stuff of the web |
| 20:51.10 | RiD | MohammadAG what if the efuse blows randomly :v |
| 20:51.41 | *** join/#maemo Macer (mace@scientiam.org) |
| 20:52.10 | MohammadAG | raccoon_, https://plus.google.com/+Chainfire/posts/LCfF5A9fsTG |
| 20:52.10 | MohammadAG | RiD, you don't get warranty :D |
| 20:54.02 | DrCode | I want to use mms also |
| 20:54.19 | MohammadAG | use fMMS |
| 20:54.25 | DrCode | after I have install fmms , I got new wifi AP call mms |
| 20:54.37 | MohammadAG | umm there are three modes |
| 20:54.46 | DrCode | so I have my 3g data AP and MMS |
| 20:54.58 | MohammadAG | I think the one that allows simultaneous use is havoc |
| 20:55.15 | DrCode | I can't use both 3gdata and mms in on AP |
| 20:56.01 | DrCode | also how can I change to what AP it will connect automticly? |
| 20:56.02 | MohammadAG | set it to havoc |
| 20:56.20 | DrCode | now it connect to mms and not 3g |
| 20:56.21 | DrCode | what is havoc? |
| 20:56.46 | MohammadAG | http://1.bp.blogspot.com/_jWWDyUCEUeA/S-PCuGjbulI/AAAAAAAAAIA/jvvZBPz1Yig/s1600/fmms-5.png |
| 20:57.05 | *** join/#maemo robotanarchy (~robotanar@f050198021.adsl.alicedsl.de) |
| 20:57.30 | DrCode | in fmms? |
| 21:05.25 | *** join/#maemo tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 21:05.42 | Macer | ugh |
| 21:06.07 | *** join/#maemo trx (ns-team@212.200.199.191) |
| 21:06.07 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 21:06.23 | Macer | this wifi router has me about to throw it |
| 21:06.29 | Macer | especially since i'm not really using it for "routing" |
| 21:06.43 | Macer | well. i guess i am but still heh |
| 21:07.05 | Macer | the n900 isn't taking very well to it at all |
| 21:15.17 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 21:23.33 | *** join/#maemo cyborg-one (~cyborg-on@37.203.8.72) |
| 21:36.35 | *** join/#maemo at1as (~at1as@50-192-119-234-static.hfc.comcastbusiness.net) |
| 21:43.40 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 21:47.50 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 21:49.39 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 21:59.16 | *** join/#maemo Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:00.43 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:03.32 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:04.49 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:43.19 | *** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com) |
| 22:49.53 | *** join/#maemo dos11 (~dos@d38-152.icpnet.pl) |
| 22:49.58 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 22:58.57 | *** join/#maemo valerius (~user@85.26.180.159) |
| 23:14.49 | *** join/#maemo Ninja (~ninja@50.9.215.104) |
| 23:28.03 | *** join/#maemo robink (~quassel@unaffilated/robink) |
| 23:32.28 | *** join/#maemo RiD (~RiD@bl22-4-195.dsl.telepac.pt) |
| 23:42.07 | Macer | uhm |
| 23:43.58 | *** join/#maemo discopig (~discopig@unaffiliated/discopig) |
| 23:45.32 | RiD | yes? |
| 23:50.02 | Apic | ? |
| 23:50.51 | *** join/#maemo LaoLang_cool (~LaoLang_c@113.73.183.40) |
