| 00:10.41 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 01:04.07 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 01:14.36 | *** join/#maemo Wizzup (~Wizzup@a82-161-36-93.adsl.xs4all.nl) |
| 01:17.50 | *** join/#maemo Smily (~SmilzOrg@93-103-95-89.dynamic.t-2.net) |
| 01:20.16 | *** join/#maemo jrg (~jrg@unaffiliated/jrg) |
| 01:20.21 | jrg | hello |
| 01:20.33 | jrg | is the N900 the only device that runs maemo still nowadays? |
| 01:21.37 | Maxdamantus | The N770/N800/N810 also run "maemo". |
| 01:22.21 | jrg | yeah but those are ancient. i was just curious if there was some sort of newer hardware device that has come out since the N900 that can run maemo5 |
| 01:22.46 | jrg | or is the N900 the latest hardware capable of running it? |
| 01:23.39 | Hurrian | jrg: nope, the N900 is so far, the only device properly running all of Fremantle |
| 01:24.40 | jrg | ah ok. that's a shame. really miss my N900. it was a great device but the hardware became so outdated |
| 01:24.51 | jrg | it because a pain to run microb |
| 01:25.12 | Maxdamantus | http://maxdamantus.eu.org/3n.jpg |
| 01:25.14 | jrg | i was hoping after all this time maybe someone released something that it could run on like maybe an x86 device like a zen fone |
| 01:26.12 | jrg | i loved the qwerty on the N900... too bad those are a thing of the past :( |
| 01:26.23 | Maxdamantus | uses Dvorak on his. |
| 01:26.24 | Hurrian | jrg: fwiw, browsing the internet nowadays is even more painful, thanks to all the Javascript. |
| 01:26.41 | Hurrian | *browsing on the N900 |
| 01:26.49 | jrg | Hurrian: oh i don't disagree with you there.. but using safari on ios vs using microb on an N900 |
| 01:27.03 | jrg | i mean if the N900 had more power behind it .. it wouldn't be bad at all |
| 01:27.20 | Maxdamantus | Like if it were a Neo900? |
| 01:27.23 | Hurrian | I miss using the arrow keys to scroll long pages. |
| 01:27.25 | jrg | but the small ram coupled with the "swap" just slowed it to a crawl towards the end where i finally gave up on it |
| 01:28.27 | Hurrian | Maxdamantus: the Neo900 is still somewhat slow, IMO - it's about par with a N9/50 |
| 01:28.46 | jrg | isn't that still better than an N900? :) |
| 01:29.15 | Hurrian | it'd be miles faster than the N900, and you can say good bye to swap (finally!)... but it'd still be kinda on the slow side nowadays. |
| 01:29.35 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 01:29.53 | jrg | neo900 has a resistive screen still? :) |
| 01:30.04 | Maxdamantus | I don't think getting rid of swap is a good idea. |
| 01:30.31 | Maxdamantus | unless everything is running in some sort of VM where memory usage can be tightly controlled, you really should still have swap. |
| 01:30.50 | jrg | the neo900 looks interesting |
| 01:30.51 | Maxdamantus | otherwise the OOM killer will eventually kill things. |
| 01:31.16 | jrg | when is that thing due for release? |
| 01:31.35 | Hurrian | I'm working on a teeny Freescale i.MX6 board, derived from the Novena - while still behind flagship phones, it's probably good enough. And purchasable in quantities less than $FEW_THOUSAND. |
| 01:53.48 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 02:02.07 | *** join/#maemo trumee (~trumee@c-50-175-121-86.hsd1.tx.comcast.net) |
| 02:27.06 | *** join/#maemo eMHa_ (~mh@p54B0F38F.dip0.t-ipconnect.de) |
| 02:43.56 | *** join/#maemo Defiant (erik@f054176252.adsl.alicedsl.de) |
| 03:03.49 | *** join/#maemo LauRoman (~LauRoman@5-14-33-187.residential.rdsnet.ro) |
| 03:18.15 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 03:59.21 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 04:01.03 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 04:14.57 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:30.11 | Oksanaa | For those who heard of or know about Nokia's battery charger DT-33: how to counter its sensitivity to ambient temperature? |
| 04:32.16 | Oksanaa | Its temperature sensor is intended to detect battery being too cold or too warm, and abort charging. However, it results in annoying no-charging when temperature is too high (like, 28°C in shadow inside house). High humidity (50%-75%) might also contribute |
| 04:37.18 | Oksanaa | While I appreciate craftsmanship of the plastic case, I would prefer the electronics to survive 50°C and 80% humidity extremes (while not charging), and reliably charge in 30°C temperatures |
| 04:38.06 | Oksanaa | It might require different position of temperature sensor(s) |
| 04:41.44 | Oksanaa | speaks as user, not as electronics or battery-charging expert |
| 04:46.13 | Maxdamantus | Meh, the carrier for the SIM in my N9 only supports HSDPA. |
| 04:46.23 | Maxdamantus | So .. need a third plan. |
| 04:46.54 | Oksanaa | Fuuun... Three SIM slots in mobile phone, anybody? |
| 04:47.16 | Maxdamantus | Capitalism sucks. |
| 04:47.27 | Oksanaa | nods |
| 04:48.01 | Maxdamantus | In rural areas, you have three towers in the same place, hosted by three different carries. In that place because it's relatively optimal in area covered. |
| 04:48.15 | Maxdamantus | Then when you're outside of that area, you're fucked. |
| 04:49.22 | Oksanaa | There are some devices which fork one SIM slot into two slots. Combine that with two-SIM-slots-phone, and you feel better. If software handles this, of course |
| 04:49.49 | Oksanaa | remembers something for making N900 two-SIMs-capable |
| 04:50.11 | Oksanaa | I can be mistaken, I wasn't testing it |
| 04:52.09 | *** part/#maemo erlehmann (~erlehmann@x5ce15d1f.dyn.telefonica.de) |
| 04:54.04 | Maxdamantus | I imagine it'd depend on the modem. |
| 04:54.21 | Maxdamantus | I think the SIM card is connected electronically to that. |
| 04:54.33 | Maxdamantus | s/electronically/electrically/ |
| 04:56.07 | Maxdamantus | wants to try using his laptop's phone functionality, but apparently has to run something in Windows to enable it. |
| 04:56.15 | Maxdamantus | has never booted Windows on his laptop. |
| 04:57.50 | Oksanaa | Why in Windows? Phone functionality sounds like something to be enabled in BIOS? |
| 04:59.34 | Maxdamantus | Assuming the BIOS knows about it. |
| 04:59.36 | Maxdamantus | It doesn't. |
| 05:00.06 | Maxdamantus | Well, it might, depending on the scope of "BIOS". |
| 05:00.31 | Maxdamantus | I suspect it involves agreeing to some license. |
| 05:00.39 | Oksanaa | Then it's closed-source driver-like-switch for something-cellular implemented only for Windows? |
| 05:01.42 | Oksanaa | If it wasn't niche, there would have been hope of RE-ing it, I guess... |
| 05:02.06 | Maxdamantus | There are open source drivers for talking to the modem. You just have to flick some switch using some particular software that runs on Windows .. for some reason. |
| 05:02.12 | Oksanaa | Is it common in phone-laptops, or specific to this manufacturer? |
| 05:02.35 | Maxdamantus | http://support.lenovo.com/nz/en/downloads/migr-68495 |
| 05:02.37 | Maxdamantus | Dunno. |
| 05:10.48 | Oksanaa | Maxdamantus: have to windows it. maybe, live cd windows? https://wiki.archlinux.org/index.php/ThinkPad_mobile_internet |
| 05:50.21 | *** join/#maemo robink_ (quasselcor@unaffilated/robink) |
| 07:02.30 | *** join/#maemo disco_stu_droid (~wrt54gl@190.211.82.70) |
| 07:07.07 | KotCzarny | hurrian: remember that in n9 most of mem is eaten by some java engine (if my memory is not mistaken), so on fremantle 1GB should be more suitable, still, 2G would be even better |
| 07:07.37 | KotCzarny | maxd: there are physical adapters that can switch sim cards (cut out) even in single slot phones |
| 07:11.35 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 07:16.11 | *** join/#maemo disco_stu (~wrt54gl@190.211.82.70) |
| 07:35.17 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 07:49.12 | *** join/#maemo vectis (~phil@79-65-221-138.host.pobb.as13285.net) |
| 08:06.39 | *** join/#maemo futpib (~futpib@176.214.20.9) |
| 08:12.01 | Maxdamantus | Java engine? O_o |
| 08:13.08 | Maxdamantus | Nothing in `ps aux` here matching "java" |
| 08:13.14 | *** join/#maemo parazyd_ (~parazyd@chat.dyne.org) |
| 08:13.16 | KotCzarny | well, its not java per se |
| 08:13.22 | KotCzarny | just some sandbox engine |
| 08:13.52 | Maxdamantus | I don't think it uses any sandbox other than Linux itself. |
| 08:13.56 | KotCzarny | hrm |
| 08:14.04 | KotCzarny | then my memory must be playing tricks |
| 08:17.24 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 08:43.59 | *** join/#maemo Vajb (~Vajb@85-76-135-250-nat.elisa-mobile.fi) |
| 09:01.03 | *** join/#maemo joga (~joga@unaffiliated/joga) |
| 09:28.32 | *** join/#maemo disco_stu (~wrt54gl@190.211.82.70) |
| 10:04.29 | *** join/#maemo eijk (~eijk@x55b2c467.dyn.telefonica.de) |
| 10:13.31 | ceene | nobody seems to have tested new yappari at -devel |
| 10:13.39 | KotCzarny | ..yet |
| 10:13.43 | ceene | they're my guinea pigs! |
| 10:13.53 | ceene | i don't want to push it to -testing until someone says something |
| 10:14.29 | ceene | it's working for me, but... |
| 10:14.57 | Sicelo | going to install shortly, when on wifi :) |
| 10:15.16 | ceene | i was thinking too of splitting gui and whatsapp |
| 10:15.22 | ceene | make libyap |
| 10:15.29 | Sicelo | but, i won't be able to test registration, which i guess was the main reason? anything else that changed? |
| 10:15.33 | ceene | in the end it's the thing that has the most changes |
| 10:15.39 | ceene | you will, that's the thing i've solved |
| 10:15.41 | Sicelo | sounds like good idea that .. :) |
| 10:16.40 | ceene | there's some much things i should do |
| 10:16.45 | ceene | i should just use libwa from coderus |
| 10:16.50 | ceene | but the apis are not compatible right now |
| 10:16.57 | ceene | and i'd have to backport libwa to qt4 |
| 10:17.07 | ceene | on the other side, it already supports textsecure |
| 10:19.01 | KotCzarny | talk to him about common maintainship of WA stack |
| 10:19.45 | ceene | if i backport it to qt4 i guess he'd be willing to merge it |
| 10:22.16 | KotCzarny | maybe he would help you with that? |
| 10:22.36 | KotCzarny | who knows |
| 10:32.41 | ceene | i just hate this thing |
| 10:33.32 | ceene | https://github.com/stenyak/breakbot |
| 10:33.35 | ceene | maybe this thing works |
| 10:33.51 | ceene | or some other |
| 10:34.36 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 10:35.04 | ceene | thing is, we don't even have a good telegram client for n900 |
| 10:35.15 | ceene | so i can't even try and persuade my friends to use it |
| 10:36.57 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 10:38.03 | *** join/#maemo ToJa92 (~ToJa92@90-231-48-223-no126.tbcn.telia.com) |
| 10:43.24 | *** join/#maemo ToJa92 (~ToJa92@90-231-126-123-no126.tbcn.telia.com) |
| 10:48.04 | *** join/#maemo disco_stu (~wrt54gl@190.211.82.70) |
| 10:57.59 | *** join/#maemo ToJa92 (~ToJa92@90-231-126-123-no126.tbcn.telia.com) |
| 10:58.44 | Sicelo | indeed. some geek friends i have have switched to telegram, but again ... not many users. :) |
| 11:04.17 | buZz | if they dont irc, they are just not really geeks |
| 11:10.29 | Sicelo | :) |
| 11:11.33 | buZz | make sure to tell them that :P |
| 11:11.54 | buZz | maybe with something like 'once you used that practise stuff enough, you can come join the real irc' |
| 11:20.48 | ceene | best im application for maemo right now is yappari... which is quite sad |
| 11:21.03 | merlin1991 | wat? |
| 11:21.06 | merlin1991 | jabber works |
| 11:30.31 | Sicelo | yes, jabber is great :) |
| 11:30.41 | Sicelo | but again .. who uses it? :) |
| 11:31.12 | Sicelo | personally i'd be happy to use only irc and jabber (as jabber has everything: calls, im, video) |
| 11:32.18 | merlin1991 | I do, so do a few of my friends :D |
| 11:35.18 | ceene | merlin1991: it's not the same "works" than "sends image and video, reports and gets receipt/read reports", etc |
| 11:36.17 | merlin1991 | iirc there is an extension to the jabber protocol for that |
| 11:36.28 | ceene | on n900 the only thing that does that is yappari |
| 11:36.40 | ceene | i'm not saying there aren't alternatives better than whatsapp |
| 11:36.45 | ceene | i'm saying there aren't any for n900 |
| 11:37.00 | buZz | just send them a handwritten letter |
| 11:39.13 | ceene | i'd be thrilled to receive one |
| 11:39.34 | buZz | now, pay those emotions forward ceene |
| 11:39.52 | ceene | i can send you a handwritten letter if you want |
| 11:40.05 | ceene | postcards were nice |
| 11:40.56 | ceene | i remember there was one piece of software whose author instead of asking for donations, asked for postcards from its users |
| 11:41.36 | buZz | yeah its a license type |
| 11:41.55 | ceene | postcard-ware |
| 11:59.40 | *** join/#maemo shentey (~shentey@x55b32530.dyn.telefonica.de) |
| 12:00.03 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 12:11.11 | jonwil | hi |
| 12:11.43 | ceene | hi, jonwil |
| 12:12.56 | *** join/#maemo parazyd (~parazyd@unaffiliated/parazyd) |
| 13:06.04 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 13:09.29 | *** join/#maemo vahe (~vahe.spac@130.193.124.175) |
| 13:11.38 | *** join/#maemo M4rtinK2 (~M4rtinK@mail.melf.eu) |
| 13:33.48 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 13:34.59 | *** join/#maemo futpib (~futpib@176.214.20.9) |
| 13:50.21 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 14:08.36 | *** join/#maemo sparetire (~sparetire@unaffiliated/sparetire) |
| 14:36.29 | *** join/#maemo pagurus (~user@pD950F3C4.dip0.t-ipconnect.de) |
| 15:10.39 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 15:27.34 | DocScrutinizer05 | errwhat? >>iPhone's preinstalled app 'health' constantly records all sports activities, without user asking for that<< (quote from TV news, sidenote in a report about health apps) |
| 15:27.45 | *** join/#maemo phlixi (~phlixi@host-188-174-221-236.customer.m-online.net) |
| 15:28.32 | DocScrutinizer05 | spyPhone, indeed |
| 15:46.04 | Wizzup | and don't tell it the date is 1 january, 1970 |
| 15:46.20 | KotCzarny | ;) |
| 15:46.33 | KotCzarny | good sploit |
| 15:46.53 | KotCzarny | 'can i see your phone for a moment?' |
| 15:58.20 | DocScrutinizer05 | why? what will happen? |
| 15:58.30 | KotCzarny | he he |
| 15:58.41 | DocScrutinizer05 | self destruct? |
| 15:58.46 | Wizzup | it will fail to boot |
| 15:58.50 | Wizzup | on all the 64 bit arm ones at least |
| 15:58.58 | DocScrutinizer05 | lol |
| 15:59.13 | Wizzup | and then 4chan made https://i.imgur.com/mnfsKzF.png |
| 15:59.51 | DocScrutinizer05 | well, in case you just have to wait one day and then you can edit the resulting date from 2nd Jan 1970 to something more sane ;-) |
| 16:00.23 | Wizzup | yes |
| 16:01.28 | DocScrutinizer05 | nice gimmick |
| 16:02.33 | DocScrutinizer05 | I just hope it doesn't bootloop and kill the battery before the "day" is over |
| 16:02.34 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 16:02.53 | Wizzup | if it does, then the clock is reset too |
| 16:02.57 | Wizzup | probably to manufacture date |
| 16:03.02 | DocScrutinizer05 | oooh |
| 16:03.07 | DocScrutinizer05 | ok |
| 16:03.27 | DocScrutinizer05 | I had expected it resets to 1st Jan 1970 :-P |
| 16:04.44 | DocScrutinizer05 | well, possibly the bootloader takes care to set a bogus but less 'rogue' date, only if the RTC got reset |
| 16:08.21 | DocScrutinizer05 | ponders trying a `>xxx; touch --date="1955-01-01" yyy` |
| 16:08.56 | DocScrutinizer05 | s/yyy/xxx/ |
| 16:10.20 | DocScrutinizer05 | wow |
| 16:10.25 | DocScrutinizer05 | jr@saturn:~/tmp> touch --date="1855-01-01" xxx; ll xxx |
| 16:10.26 | DocScrutinizer05 | -rw-r--r-- 1 jr users 0 1. Jan 1855 xxx |
| 16:12.16 | Wizzup | very few devices that I know reset to 1970 |
| 16:12.22 | Wizzup | except for the sheevaplug |
| 16:13.27 | DocScrutinizer05 | man 2 stat; man 2 time >>time() returns the time as the number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).<< |
| 16:14.49 | DocScrutinizer05 | I wonder how the heck the filesystem stores, and stat() resturns, dates like 1. Jan 1855 |
| 16:16.34 | DocScrutinizer05 | time_t clearly seems to be a uint (or ulong, whatever) with seconds since epoch |
| 16:17.27 | DocScrutinizer05 | or has that recently been changed to a 64bit int with seconds since bigbang? |
| 16:21.21 | *** join/#maemo Smily (~SmilzOrg@93-103-95-89.dynamic.t-2.net) |
| 16:24.14 | DocScrutinizer05 | ummm #define __TIME_T_TYPE __SYSCALL_SLONG_TYPE |
| 16:25.02 | DocScrutinizer05 | # define __SYSCALL_SLONG_TYPE __SLONGWORD_TYPE |
| 16:27.24 | DocScrutinizer05 | so it's a signed 64bit? |
| 16:28.22 | DocScrutinizer05 | ~ 2**63/3600/24/365 |
| 16:28.22 | infobot | 292471208677.536010742188 |
| 16:29.41 | DocScrutinizer05 | suffices til Y2Trillion-problem kicks in ;-) |
| 16:30.03 | DocScrutinizer05 | nevermind Y2K-problem ;-P |
| 16:32.24 | DocScrutinizer05 | s/(time() returns the time as the number of seconds )since( the Epoch, 1970-01-01 00:00:00 +0000 (UTC).)/\1since\/before\2/ |
| 16:39.29 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 16:42.17 | DocScrutinizer05 | ~ 1970 + 2**31/3600/24/365 |
| 16:42.17 | infobot | 2038.096259766616 |
| 16:47.16 | DocScrutinizer05 | Wizzup: anyway you're right. RTCs generally work completely different, having no idea about epoch |
| 16:48.17 | DocScrutinizer05 | depends on chip what date they reset to on POR |
| 17:02.25 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 17:02.58 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 17:03.05 | DocScrutinizer05 | most RTC have a 2digit BCD year value from 00 to 99 |
| 17:04.01 | DocScrutinizer05 | so odds are it would reset to year (20)00 |
| 17:05.22 | Wizzup | olimex boards reset to 2010 |
| 17:05.30 | Wizzup | at least the ones that I have |
| 17:05.52 | DocScrutinizer05 | wow, so they have a one digit year only |
| 17:06.26 | KotCzarny | :) |
| 17:06.35 | DocScrutinizer05 | or a N-bit binary integer for year value |
| 17:08.36 | DocScrutinizer05 | Y1Decade problem approaching in 4 years |
| 17:10.30 | DocScrutinizer05 | prolly the designers thought it's safe to assume their product won't get older than 16 years, so 4 bit for the year value are just fine ;-) |
| 17:12.19 | DocScrutinizer05 | actually you might get away with assuming your system gets booted at least once per 16 years, and you store a new offset somewhere in persistent storage and adjust the RTC accordingly |
| 17:13.42 | DocScrutinizer05 | when you assume your system gets booted at least once per year, this scheme can get away without any year values in RTC |
| 17:17.01 | DocScrutinizer05 | downside of such scheme: restoring backups will mess up your system time massively |
| 17:20.24 | DocScrutinizer05 | when Amiga had no RTC, they simply forward-adjusted the syystem time accordingly whenever they found an arbitrary file on storage with a modification/access time supposedly into the future ;-) |
| 17:21.55 | DocScrutinizer05 | so adding a true clock was the very first hack I applied to all my Amiga devices |
| 17:24.08 | *** join/#maemo xray256 (~xray256@90.199.147.63) |
| 17:26.30 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 17:29.12 | *** join/#maemo LauRoman (~LauRoman@5-14-33-187.residential.rdsnet.ro) |
| 17:31.43 | *** join/#maemo vectis (~phil@79-65-221-138.host.pobb.as13285.net) |
| 17:37.09 | DocScrutinizer05 | later it got augmented by a DCF77 receiver with decoding in software (had to write a decoder for that) |
| 17:38.19 | *** join/#maemo xray256_ (~xray256@90.197.173.146) |
| 17:51.05 | *** join/#maemo infobot (ibot@rikers.org) |
| 17:51.05 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 18:14.56 | DocScrutinizer05 | idly wonders if it wuld be a feasible worthwhile and funny experiment to directly connect a 77.5kHz ferrite antenna + capacitor rrsonant circuit with a FET amp to a computer's audio-in |
| 18:16.32 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 18:42.10 | kerio | DocScrutinizer05: why didn't you use a NTP client? :> |
| 18:47.12 | KotCzarny | ~ugt |
| 18:47.12 | infobot | hmm... ugt is Universal Greeting Time. Created in #mipslinux, it is a rule that states that whenever somebody enters an IRC channel it is always morning, and it is always late when the person leaves. The local time of any other people in the channel, including the greeter, is irrelevant. http://www.total-knowledge.com/~ilya/mips/ugt.html |
| 18:56.40 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 19:04.29 | *** join/#maemo disco_stu_droid (~wrt54gl@190.211.82.70) |
| 19:13.51 | *** join/#maemo futpib (~futpib@176.214.20.9) |
| 19:28.27 | *** join/#maemo msava (~mircea@nl112-156-14.student.uu.se) |
| 19:33.05 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 19:36.21 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:51.37 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 20:10.32 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 20:13.37 | *** join/#maemo Roth (~quassel@2601:18c:c700:c4d3:7c90:265a:f157:b4f9) |
| 20:23.08 | *** join/#maemo krnlyng (~liar@77.117.67.32.wireless.dyn.drei.com) |
| 20:52.38 | *** join/#maemo msava (~mircea@nl112-156-14.student.uu.se) |
| 21:10.21 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 21:13.39 | *** join/#maemo FIQ (~FIQ@fiq.se) |
| 21:28.54 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
| 21:30.43 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 21:37.10 | *** join/#maemo krnlyng (~liar@77.117.67.32.wireless.dyn.drei.com) |
| 21:53.30 | *** join/#maemo Kabouik (~quassel@53.3.201.77.rev.sfr.net) |
| 22:43.21 | *** join/#maemo pagurus (~user@pD950F3C4.dip0.t-ipconnect.de) |
| 22:56.14 | *** join/#maemo heroux (bel3atar@gateway.insomnia247.nl) |
| 23:04.36 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 23:18.48 | *** join/#maemo eijk_ (~eijk@x55b2c624.dyn.telefonica.de) |
| 23:45.03 | *** join/#maemo xray256 (~xray256@90.197.156.181) |
| 23:47.34 | *** join/#maemo krnlyng (~liar@77.117.75.230.wireless.dyn.drei.com) |
| 23:57.40 | *** join/#maemo heroux (sandroco@gateway.insomnia247.nl) |
