| 00:12.05 | Maxdamantus | Seems like an unnecessary amount of effort for an interface people would rarely use. |
| 00:12.36 | Maxdamantus | You should already be able to bind things to keys using something like `xbindkeys`, which is probably easy enough for most N900/maemo users. |
| 00:16.15 | CatButts | less user, more programmer making his application |
| 00:17.27 | CatButts | a way to conveniently deal with discrepancies in key layout |
| 00:17.31 | CatButts | s |
| 00:17.44 | CatButts | by having user press ALL the keys |
| 00:17.45 | CatButts | :P |
| 00:17.55 | CatButts | in order |
| 00:24.50 | Maxdamantus | You mean the user is forced to press all keys before being able to use the device? |
| 00:31.12 | CatButts | being forced to press all the keys before using application |
| 00:31.13 | CatButts | once |
| 00:31.54 | CatButts | or rather, one application, with the rest benefiting from stored config |
| 00:32.06 | Maxdamantus | I don't really understand what the purpose is. |
| 00:32.24 | Maxdamantus | Is it to ensure that users are using a keyboard layout they specifically want? |
| 00:32.30 | CatButts | yes |
| 00:32.44 | CatButts | rather |
| 00:32.49 | Maxdamantus | I imagine most people would probably just use whatever is provided. The decision for where most keys go is pretty much completely arbitrary. |
| 00:33.22 | Maxdamantus | The fact that it's fairly arbitrary is basically solved by just having a standard layout that everyone just uses. |
| 00:33.32 | CatButts | it's to give application view of where all keys are |
| 00:34.01 | Maxdamantus | You can change that if you really want (I did, since I'm used to Dvorak, not QWERTY, and I also mapped all remaining printable ASCII characters to keys) |
| 00:34.18 | Maxdamantus | Why would an application care where the keys are? |
| 00:34.46 | Maxdamantus | If it cares about where keys are, it must be specific to N900, in which case it should be using key codes instead of key symbols. |
| 00:35.32 | Maxdamantus | It shouldn't need to care what the mapping is between codes and symbols. |
| 00:35.58 | Maxdamantus | unless it is an application designed for something like the configuration between the two. |
| 00:37.19 | CatButts | well, the first stage maps out where everything is |
| 00:38.05 | CatButts | the second stage is setting default keys according to first stage and optionally letting user rebin |
| 00:38.06 | CatButts | d |
| 00:40.17 | Maxdamantus | Are you talking about so that maemo is device-agnostic? |
| 00:41.52 | CatButts | nope |
| 00:41.59 | CatButts | wait |
| 00:42.15 | CatButts | device agnostic means OS running on other devices as well? |
| 00:42.32 | Maxdamantus | Yes, on devices other than N900 |
| 00:42.36 | CatButts | in that case, N900 specific |
| 00:43.00 | CatButts | it's not at OS level |
| 00:43.16 | CatButts | it's a helper application for other apllications to use |
| 00:44.43 | CatButts | with two things to do |
| 00:45.23 | CatButts | 1. do that silly 'press all keys in order' thing if it hasn't been done before(re-requestable if shit don't line up) |
| 00:45.39 | *** join/#maemo sunshavi (~user@181.64.192.149) |
| 00:46.00 | CatButts | 2. provide helping interface for key setup and way to return mapped keys to requesting app |
| 00:46.07 | CatButts | with visual aid |
| 00:46.57 | Maxdamantus | What's the point in `1`? You're basically asking the user to produce input that is completely predictable (assuming all users are using an N900) |
| 00:47.16 | Maxdamantus | it sounds like calibration where there is nothing to actually calibrate. |
| 00:48.28 | CatButts | aren't returned keycodes different depending on whatever mapping you have? |
| 00:48.36 | CatButts | yes, it's a calibration step |
| 00:48.48 | Maxdamantus | If a screen calibration asks you to press in a particular position, it's because the screen calibration tool isn't sure extactly what numbers will be produced if the user presses where he/she thinks that place is. |
| 00:49.18 | Maxdamantus | but in this case, the program should know exactly what input will be produced when someone presses a particular key. |
| 00:50.11 | Maxdamantus | If I press the top left key on my device, it will produce the same key code as if you pressed the top left key on your device. |
| 00:50.42 | Maxdamantus | and a program could easily be hardcoded with that information. |
| 00:50.45 | CatButts | what about anything inbetween? |
| 00:51.01 | CatButts | what about up-down-left-right |
| 00:51.05 | Maxdamantus | You don't bother gathering data for things you already know. |
| 00:51.20 | Maxdamantus | Yes, those should also produce the same input on all N900 devices. |
| 00:52.03 | Maxdamantus | at a hardware level, the keyboard is just a 2D grid of buttons. |
| 00:52.44 | CatButts | different keycode will be produced when same key is pressed with different mappings |
| 00:52.47 | CatButts | that's the point |
| 00:52.49 | Maxdamantus | If you press the button with the same coordinates on two different N900 devices, it will produce the same electronic signals to the CPU. |
| 00:53.31 | Maxdamantus | No. Keycode is independent of mapping (at least at an Xorg level) |
| 00:53.59 | Maxdamantus | The keycode is determined by the keypad driver in Linux, which should behave the same way across devices. |
| 00:54.45 | Maxdamantus | The thing that's configured differently because of different keyboard layouts is the mapping between keycodes and keysyms, which happens in Xorg. |
| 00:55.25 | Maxdamantus | when you receive a keyboard event in X11, you get the keycode, then you can look up the keysym. |
| 00:55.32 | CatButts | so an application can listen to either keycode or keysym? |
| 00:55.49 | Maxdamantus | Yes. |
| 00:56.00 | CatButts | in this case the first stage becomes useless |
| 00:56.02 | Maxdamantus | Try running `xev` |
| 00:56.36 | Maxdamantus | it will show you both the "key code", which is just some number reported by the kernel, independent of you keyboard layout. |
| 00:57.27 | Maxdamantus | It'll also show the "key sym", which is how applications should generally interpret that key code (eg, as the letter 'a' or the escape key) |
| 01:00.02 | CatButts | so this theoretical application is now reduced to pretty, unified interface for games to receive keymappings from |
| 01:22.50 | Oksanaa | I am quite annoyed at how physically frail Nokia N900's back cover is. Battery cover. |
| 01:23.46 | Oksanaa | Plastic hook can be broken off, camera lens cover may stop spring-ing properly into open-closed positions, and back-stand may be broken out of the plastic, too. |
| 01:24.18 | Oksanaa | Besides the magnet wishing to come unglued, which is relatively easy to fix. |
| 01:27.30 | Oksanaa | I have just received a Nokia N900 with broken case. MicroUSB port works (for charging, at least; will try flashing later), screen is fine if slightly scratched (I applied a screen protector immediately upon receiving the device). Major damage? Back cover misses a triangle of plastic (no clue how it |
| 01:28.19 | Oksanaa | And it's difficult to find N900's back cover being sold. Whole case? Easy. Battery cover only? Difficult. I could check again... |
| 01:28.19 | Oksanaa | happened, innards seem to be fine), back-stand shows its sharp metal pointy ends, and plastic hooks are broken off. |
| 01:28.38 | Oksanaa | I wish Mugen or somebody else continued to make N900 battery covers. |
| 01:28.50 | Oksanaa | Because I would buy more than one. |
| 01:29.12 | Oksanaa | Stylus is much easier to source. |
| 02:51.47 | *** join/#maemo auenfx8 (~David@120.154.64.171) |
| 03:00.49 | *** join/#maemo trumee (~trumee@c-73-183-219-14.hsd1.tx.comcast.net) |
| 03:10.04 | *** join/#maemo auenf (~David@120.154.64.171) |
| 03:43.58 | *** join/#maemo auenf (~David@120.154.64.171) |
| 04:01.28 | *** join/#maemo trumee (~trumee@c-73-183-219-14.hsd1.tx.comcast.net) |
| 04:18.57 | *** join/#maemo sunshavi (~user@181.64.192.149) |
| 08:03.44 | *** join/#maemo Maxdamantus (~Maxdamant@unaffiliated/maxdamantus) |
| 08:39.10 | *** join/#maemo jkepler (~Thunderbi@gateway/vpn/privateinternetaccess/jkepler) |
| 08:39.49 | *** join/#maemo shentey (~shentey@x55b4f8a3.dyn.telefonica.de) |
| 09:40.45 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 09:53.00 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 09:53.46 | Wikiwide | I didn't re-install modrana. 44MB of dependencies? No thank you... |
| 09:54.20 | Wikiwide | Mappero looks nice, though. But not quite hildon-ised. Just look at its "Full screen" button... |
| 09:55.05 | Wikiwide | GeePS doesn't cache tiles for offline storage, right? Will uninstall it. |
| 09:57.03 | Wikiwide | Also, is it possible that a problem with light sensor causes excessive brightness of display and drains battery way too quickly? |
| 10:06.45 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 10:15.02 | *** join/#maemo Kabouik (~kabouik@236.34.200.37.customer.cdi.no) |
| 10:17.05 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 10:24.57 | *** join/#maemo spiiroin (~spiiroin@37-219-2-171.nat.bb.dnainternet.fi) |
| 10:40.09 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 10:43.48 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 10:46.40 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 11:27.42 | *** join/#maemo Maxdamantus (~Maxdamant@unaffiliated/maxdamantus) |
| 11:29.01 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 11:31.55 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 11:32.34 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 11:34.17 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:38.08 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:38.43 | Wikiwide | Tired. Tired. Tired. |
| 11:39.42 | *** join/#maemo spiiroin (~spiiroin@37-219-13-196.nat.bb.dnainternet.fi) |
| 11:48.37 | DocScrutinizer05 | CatButts: (keymaps) learn the basics! the hw keycodes are (surprise!) *hardware* defined and immuatable on a certain hw platform. It's only higher layers that assign different chars to t hw keycode, usually according to what you print on your keycaps |
| 11:50.33 | DocScrutinizer05 | oooh, seems somebody on my ignore list helped sorting stuff and contributed a useful pointer to "keysym". Pretty unusual |
| 11:51.18 | CatButts | Max? |
| 11:51.45 | CatButts | watcha piss him off with? :P |
| 11:52.05 | Maxdamantus | He'd be surprised .. the reason I'm actually on his ignore list was because I was trying to figure out what program was responsible for producing vibration in response to touchscreen presses and he kept insisting it was Xorg and I kept insisting it was an external program. |
| 11:53.48 | CatButts | so, from application programmer perspective, you get access to both hw keycodes and mapped keys |
| 11:53.50 | CatButts | yes? |
| 11:53.52 | Maxdamantus | (and it was an external program; maemo-xinput-sounds or something along those lines) |
| 11:53.52 | Maxdamantus | Eh, internet DCed again. |
| 11:54.05 | DocScrutinizer05 | yes |
| 11:54.37 | CatButts | then the calibration step I yapped about can become automagic |
| 11:54.54 | DocScrutinizer05 | check xev, very useful app |
| 11:54.57 | Maxdamantus | http://mg.pov.lt/maemo-irclog/%23maemo.2016-01-13.log.html |
| 11:55.44 | DocScrutinizer05 | http://paste.opensuse.org/35424980 |
| 11:57.34 | CatButts | >sh: xev not found |
| 11:57.36 | CatButts | whooops |
| 11:58.12 | DocScrutinizer05 | http://paste.opensuse.org/7504181 |
| 11:58.51 | DocScrutinizer05 | IroN900:~# apt-cache search xev |
| 11:58.52 | DocScrutinizer05 | x11-utils - X11 utilities |
| 11:59.56 | DocScrutinizer05 | ~pkg x11-utils |
| 12:00.11 | DocScrutinizer05 | ~pkg |
| 12:00.11 | infobot | pkg is probably http://maemo.org/packages/ |
| 12:02.02 | DocScrutinizer05 | http://maemo.org/packages/view/x11-utils/ |
| 12:03.31 | DocScrutinizer05 | also see http://maemo.org/packages/view/xmodmap/ |
| 12:05.12 | CatButts | oh sweet, it has xkill |
| 12:15.51 | CatButts | tries it on flash 10 player |
| 12:19.12 | CatButts | nope |
| 12:19.22 | CatButts | I guess it's only good when bound to a key |
| 12:31.24 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 12:48.15 | DocScrutinizer05 | it'sit particularly pointless on hildon desktop which doesn't support the usual focus setting by clicking with mouse into the window, since there's always just one fullscreen window with focus in front |
| 12:48.49 | DocScrutinizer05 | then, maemo has "kill recent task" OWTTE in powerbuttonmenu, and the task switcher offers killing tasks as well |
| 12:50.09 | DocScrutinizer05 | so xkill is useless at best, probably rather not compatible at all |
| 12:50.10 | CatButts | I make do with htop, so far |
| 12:51.00 | CatButts | xkill worked fine on the console that summoned it :P |
| 12:51.20 | DocScrutinizer05 | lol, yeah. since that consile has the focus |
| 12:51.44 | CatButts | I imagine you are suppose to assign it to a key combination for it to be of any use |
| 12:55.05 | DocScrutinizer05 | not really, it should check the X-event cueue for mouse LMB clicks (as seen by e.g. xev, I leave it to you for an exercise to figure how to make your won xkill using xev in a script, with awk and kill) and find the process owning the window to kill it. Obviously this concept is prone to fail completely on hildon |
| 13:08.06 | CatButts | sounds like a work of masochism if all I am going to get failure :p |
| 13:11.06 | CatButts | where is proximity sensor located on the n900? |
| 13:11.17 | DocScrutinizer05 | sys fs |
| 13:11.28 | CatButts | physically, I mean |
| 13:11.52 | CatButts | I want to use that instead of keyboard combos |
| 13:12.07 | DocScrutinizer05 | ooh damn you! my nice paste ;-P |
| 13:12.10 | DocScrutinizer05 | IroN900:~# find /sys -name proximity |
| 13:12.11 | DocScrutinizer05 | /sys/devices/platform/gpio-switch/proximity |
| 13:12.13 | DocScrutinizer05 | /sys/bus/platform/devices/proximity |
| 13:12.14 | DocScrutinizer05 | /sys/bus/platform/drivers/gpio-switch/proximity |
| 13:12.57 | DocScrutinizer05 | portrait mode upper left corner, next to camera and ALS |
| 13:13.20 | DocScrutinizer05 | err landscape mode, sorry |
| 13:15.26 | DocScrutinizer05 | watch cat /sys/bus/platform/devices/proximity/state |
| 13:16.57 | CatButts | ah, bueno |
| 13:17.01 | CatButts | it works |
| 13:17.10 | CatButts | unlike ShortcutD |
| 13:17.13 | DocScrutinizer05 | watch -d -n "0,5" cat /sys/bus/platform/devices/proximity/state |
| 13:19.11 | CatButts | invalid number 0,5 |
| 13:19.21 | DocScrutinizer05 | YMMV, regarding decimal |
| 13:19.32 | DocScrutinizer05 | try 0.5 |
| 13:19.44 | CatButts | same |
| 13:19.52 | DocScrutinizer05 | if that fails too, get beter `watch` bibary |
| 13:20.06 | DocScrutinizer05 | if that fails too, get better `watch` binary |
| 13:22.51 | DocScrutinizer05 | or live with messybox limitations and use interval <INTEGER> |
| 13:23.28 | DocScrutinizer05 | sorry, no idea where from I installed my `watch` binary |
| 13:25.10 | CatButts | http://cat.butt.care:3434/priv/Screenshot-20171126-152321.png hmmmmm |
| 13:25.55 | DocScrutinizer05 | hmm makes sense |
| 13:26.10 | CatButts | I have the oportunity to type N and avoid a pottential fudge-up |
| 13:26.27 | DocScrutinizer05 | http://paste.opensuse.org/88420944 |
| 13:27.41 | DocScrutinizer05 | I *thought* procps been fixed to NOT remove MP-fremantle-community-pr |
| 13:27.49 | CatButts | installed: (none) |
| 13:29.19 | DocScrutinizer05 | http://paste.opensuse.org/19538933 |
| 13:31.35 | CatButts | installed: 21.2011.38-17maemo11+thumb0 |
| 13:31.55 | CatButts | mp-fremantle-community-pr |
| 13:32.39 | DocScrutinizer05 | hmm thumb |
| 13:32.49 | DocScrutinizer05 | sorry no idea |
| 13:32.59 | CatButts | oh well, sod it |
| 13:33.57 | *** join/#maemo Maxdamantus (~Maxdamant@unaffiliated/maxdamantus) |
| 13:34.20 | DocScrutinizer05 | I think thumb isn't for me since i'm not competent enough to consider all the implications it introduces |
| 13:34.48 | DocScrutinizer05 | and honestly I wouldn't want to deal with those even if I were competent enough |
| 13:35.16 | CatButts | eh, I am more reckles |
| 13:35.38 | CatButts | I should at least keep a list of applications installed |
| 13:35.56 | CatButts | for when Maemo goes tits-up |
| 13:37.34 | CatButts | when I have little attachment to the way things are currently set up, I behave recklessly |
| 13:40.03 | CatButts | when it has grown on me(like my crusty windows PC), I become reluctant to change anything drastic |
| 13:42.57 | *** join/#maemo pkill9 (~pkill9@unaffiliated/pkill9) |
| 13:45.57 | DocScrutinizer05 | makes sense :-) |
| 13:55.53 | *** join/#maemo NotKit (~nekit@85-95-189-112.saransk.ru) |
| 13:58.28 | DocScrutinizer05 | could you please pastebin result of `apt-get -s procps`? |
| 14:01.02 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 14:06.46 | CatButts | ok |
| 14:08.54 | CatButts | invalid operation procps |
| 14:08.55 | CatButts | :p |
| 14:26.47 | CatButts | I'm missing an option |
| 14:38.51 | *** join/#maemo xes__ (~xes@unaffiliated/xes) |
| 14:43.49 | DocScrutinizer05 | install, sorry |
| 14:44.06 | DocScrutinizer05 | `apt-get -s install procps` |
| 14:44.52 | CatButts | apt-get -s install procps | installog.txt |
| 14:44.57 | CatButts | how's this |
| 14:45.14 | DocScrutinizer05 | but it seems this won't yield useful info on why exactly procps wants to uninstall mp-fremantle-community-pr |
| 14:47.47 | CatButts | oh derp |
| 14:47.51 | CatButts | it's > |
| 14:54.38 | *** join/#maemo MaemoButts (~MaemoButt@188.173.53.45) |
| 14:54.43 | MaemoButts | https://pastebin.com/DasWmM7v |
| 14:56.50 | CatButts | nothing good here |
| 14:57.12 | CatButts | except for the fact that I have naughty repos left open :P |
| 14:59.16 | *** join/#maemo Maxdaman1us (~Maxdamant@unaffiliated/maxdamantus) |
| 14:59.53 | DocScrutinizer05 | apt and dpkg tools are such a crap. No useful diagnostic output for in-depth analysis. NFC if procps conflicts mp-fremantle-community-pr or a property of mp-fremantle-community-pr and in which one |
| 14:59.54 | *** join/#maemo eijk_ (~eijk@p200300454A12D90041F8665AB6CFAC0A.dip0.t-ipconnect.de) |
| 15:11.55 | DocScrutinizer05 | honestly, reading https://ubuntuforums.org/showthread.php?t=1942440 makes me weep |
| 15:14.22 | DocScrutinizer05 | IroN900:~# apt-cache depends mp-fremantle-community-pr|grep procps |
| 15:14.24 | DocScrutinizer05 | <PROTECTED> |
| 15:15.54 | DocScrutinizer05 | don't ask me how to fix that |
| 15:19.16 | *** join/#maemo spiiroin (~spiiroin@178-55-119-17.bb.dnainternet.fi) |
| 15:20.01 | *** join/#maemo spiiroin (~spiiroin@178-55-119-17.bb.dnainternet.fi) |
| 15:22.28 | *** join/#maemo shentey (~shentey@x55b4f8a3.dyn.telefonica.de) |
| 15:23.44 | DocScrutinizer05 | feels massive headache http://paste.opensuse.org/86359988 - prolly getting too old for such shit |
| 15:26.17 | DocScrutinizer05 | I guess Pali or freemangordon or a few others in here could shed more light on this issue |
| 15:26.40 | DocScrutinizer05 | ~jrtools |
| 15:26.41 | infobot | jrtools is probably http://wiki.maemo.org/User:Joerg_rw/tools |
| 15:26.53 | DocScrutinizer05 | ^F ps |
| 15:28.01 | DocScrutinizer05 | ### breaks cssu-t5.1 MP, so it's commented out. Use on own peril: |
| 15:28.02 | DocScrutinizer05 | ### allegedly fixed in mp-fremantle-community-pr 21.2011.38-1Tmaemo11 |
| 15:28.04 | DocScrutinizer05 | apt-get install procps |
| 15:29.06 | DocScrutinizer05 | there's a reasin I try to record stuff on this wikipage: I tend to forget details myself |
| 15:29.17 | DocScrutinizer05 | raisin* |
| 15:31.44 | DocScrutinizer05 | CatButts: you're free to install and accept removal of your MP, and just re-install the MP prior to running next MP update (implicitly removing procps again), then after MP update you can install procps again and hope it won't remove MP again vsince it got fixed in thumb-MP too by then |
| 15:32.52 | DocScrutinizer05 | freemangordon: could you have a look ^^^ thumb MP conflicts with procps |
| 15:34.41 | DocScrutinizer05 | I'm a total debian washout but I *think* for that reason they invented "alternatives" |
| 15:36.26 | DocScrutinizer05 | MESSYvox |
| 15:36.31 | DocScrutinizer05 | box even |
| 16:00.05 | *** join/#maemo shentey (~shentey@x55b4f8a3.dyn.telefonica.de) |
| 16:14.56 | *** join/#maemo Kabouik (~kabouik@236.34.200.37.customer.cdi.no) |
| 16:15.59 | *** join/#maemo Kabouik_ (~kabouik@ks3100825.kimsufi.com) |
| 17:00.52 | *** join/#maemo Kabouik (~kabouik@38.ip-37-187-46.eu) |
| 17:15.54 | *** join/#maemo pagurus (~user@i59F774CA.versanet.de) |
| 17:54.32 | *** join/#maemo shentey (~shentey@x55b4f8a3.dyn.telefonica.de) |
| 18:19.23 | *** join/#maemo Cor-Ai (~cor-ai@c-56de71d5.06-922-7570702.cust.bredbandsbolaget.se) |
| 19:14.50 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 19:27.38 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 19:53.31 | *** join/#maemo sunshavi (~user@181.64.192.149) |
| 20:07.19 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 20:39.11 | *** join/#maemo Kabouik_ (~kabouik@236.34.200.37.customer.cdi.no) |
| 20:51.08 | *** join/#maemo CatButts (~c@188.173.53.45) |
| 20:52.21 | *** join/#maemo pkill9 (~pkill9@unaffiliated/pkill9) |
| 21:07.37 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 21:10.42 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 21:31.47 | *** join/#maemo yosafbridge (~yosafbrid@68.ip-149-56-14.net) |
| 21:38.13 | *** join/#maemo yosafbridge (~yosafbrid@68.ip-149-56-14.net) |
| 21:56.18 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
