| jonwil | Damn, I can't find any instructions on how to rebuild scratchbox (which I want to do to update some stuff for SSH), I can find the Scratchbox source code and I can find plenty of binaries but no instructions on how to actually rebuild it the way I need to :( | 08:05 |
|---|---|---|
| KotCzarny | rebuild parts you need then | 08:12 |
| KotCzarny | might be easier for you | 08:12 |
| jonwil | I cant find how to rebuild just SSH either | 08:25 |
| jonwil | the ssh binary is part of scratchbox-core | 08:26 |
| jonwil | so I need to rebuild all of that package | 08:26 |
| Oksana | jonwil : Is this relevent? https://wiki.maemo.org/Icecream_Scratchbox_Howto#Compiling_icecc sbox > ./configure --prefix=/scratchbox/tools | 08:34 |
| Oksana | relevant * | 08:34 |
| jonwil | No, thats for compiling icecc (whatever that is) for use with Scratchbox | 08:35 |
| jonwil | I need instructions for rebuilding Scratchbox itself (which dont seem to exist, even in the docs on scratchbox.org) | 08:35 |
| jonwil | No information on what build environment/prerequisites I need or where to get them and no information on how to actually build the thing :( | 08:37 |
| Oksana | jonwil : is installation of a scratchbox toolchain in any way similar to installation of scratchbox-core? http://www.mono-project.com/archived/scratchbox/ | 08:54 |
| jonwil | That's how you install scratchbox, not how you actually compile scratchbox-core (and scratchbox-libs and such) from the "scratchbox" source package) and get some .deb files out the other end. | 08:55 |
| KotCzarny | jonwil, maybe you should read about generic scratchbox compilation? it's not only maemo's thing | 08:56 |
| jonwil | I cant find anything generic either | 08:56 |
| jonwil | I can't find anything anywhere on scratchbox.org or google that explains how you compile the "scratchbox" source package | 08:56 |
| Oksana | I would have felt easier if I saw source packages in debian format, and not in tarball format. | 08:57 |
| jonwil | The tarball has a debian folder inside it | 08:58 |
| jonwil | dpkg-buildpackage just says "cannot open `debian/changelog' for reading" | 08:58 |
| jonwil | so clearly there is some other step you need to do which isn't documented anywhere | 08:59 |
| Oksana | jonwil : check permissions? | 08:59 |
| jonwil | the file doesn't exist | 08:59 |
| jonwil | there is a debian/changelog.in file though | 08:59 |
| Oksana | Doesn't exist... How can a changelog not exist? | 08:59 |
| jonwil | so presumably something else translates that into debian/changelog from elsewhere | 08:59 |
| KotCzarny | autoconf -vif ? | 08:59 |
| jonwil | It looks like it takes the changelog from the version history of the repo (its a repo from something called darcs apparently) | 09:00 |
| jonwil | Or possibly from somewhere else | 09:02 |
| Oksana | tarball is confusing, I do not even see debian folder in it | 09:09 |
| jonwil | I dont know what you are looking at but http://www.scratchbox.org/download/files/sbox-releases/hathor/src/ clearly has a debian folder inside the scratchbox-1.0.25.tar.gz file | 09:10 |
| Oksana | Huh... I was looking at /tarball/, not /src/. One moment... | 09:11 |
| jonwil | well actually I pulled my tree from http://scratchbox.org/repos/1.0/scratchbox/ which supplies version 1.0.26 of Scratchbox rather than the 1.0.25 version | 09:14 |
| jonwil | I want 1.0.26 since that's what is installed on my system | 09:14 |
| Oksana | changelog.in sounds exactly like a changelog, except for <DATE> variable. | 09:15 |
| Oksana | Going by rules, make has to be invoked. And this make, when asked for binary-arch, invokes dh_builddeb. | 09:19 |
| Oksana | Putting the whole "turn changelog.in into changelog" routine inside "rules" file sounds ugly. Ugly like a wall of text in IRC. | 09:21 |
| Oksana | Nice line >>@echo "Use the ./build script to build Scratchbox!"<< | 09:23 |
| jonwil | Ok, that's useful | 09:23 |
| Oksana | Just reading the Makefile ;-) | 09:23 |
| Oksana | It's like walking backwards, and using reflective surfaces in front of you to see terrain behind you - and dramatic "!!" exclamation points. At least, build script is talkative. | 09:25 |
| jonwil | Running it gives me a bunch of "missing packages" none of which exist in the repos currently set up in my VM | 09:27 |
| Oksana | Which packages? Are they available somewhere else? | 09:28 |
| jonwil | Those repos being "ubuntu lucid", "scratchbox hathor" and something to do with garage | 09:28 |
| jonwil | https://pastebin.com/FWR7GC8K is the errors I get | 09:29 |
| KotCzarny | you need older distro | 09:30 |
| KotCzarny | ehehehe | 09:30 |
| KotCzarny | try something from 2009 era | 09:30 |
| ceene | gcc 3.3 | 09:30 |
| ceene | lol | 09:30 |
| KotCzarny | ;) | 09:30 |
| KotCzarny | well, at least its not 2.96 ;) | 09:31 |
| ceene | you should try running that on a debootstrap of debian squeeze maybe | 09:31 |
| Oksana | Daunting. I used to have Firefox 1 installed somewhere, that's ancient. But a whole ancient distribution... | 09:32 |
| ceene | i should still have the CDs i bought from some online site of Debian Potato :) | 09:32 |
| * KotCzarny has redhat 3.0.3 cds somewhere | 09:33 | |
| KotCzarny | and debian 2 | 09:33 |
| * Oksana would have hoped that with backwards compatibility and what not, it's possible to adapt scratchbox-core to compiling with the latest gcc and such | 09:33 | |
| Oksana | Unfortunately, while the latest gcc may make scratchbox faster (at least on modern processors), it would also probably make scratchbox more bloated? Just guessing, now idea how gcc and others changed since then. | 09:36 |
| Oksana | no * idea | 09:36 |
| KotCzarny | i would say more buggy | 09:38 |
| KotCzarny | :) | 09:38 |
| KotCzarny | it was abandoned in 2010 in favor of sb2 | 09:38 |
| * Oksana thinks that an auto-builder for scratchbox packages would be a nice idea... It would probably need a total isolation between ancient packages necessary for building scratchbox packages, and new packages needed for converting /src/ to /deb/ | 09:38 | |
| KotCzarny | imo, whole maemo build infra should just move to arm server/native compilation | 09:38 |
| Oksana | Hmm, what's the difference between scratchbox and sb2 ? | 09:38 |
| KotCzarny | there are fast enough arm boards available | 09:39 |
| Oksana | KotCzarny : probably. It would be easier to do by setting up auto-builder for leste on an ARM server first , and then expanding to older maemo distributions. | 09:40 |
| KotCzarny | in my understanding sb1 runs as a chroot/qemu vm, sb2 is more like cross-compiler (system wise) | 09:41 |
| jonwil | The basic problem I have right now is that the scratchbox ssh binary (and openssl lib it uses) is so outdated it can't talk to github anymore. | 09:43 |
| KotCzarny | jonwil: just replace binary? | 09:43 |
| jonwil | Hence the desire to rebuild scratchbox-core (and through that the scratchbox ssh binary) with a newer openssl | 09:43 |
| jonwil | Its not a plain vanilla binary, the scratchbox build system does something special | 09:44 |
| KotCzarny | that's why i asked for maemo specific patches for sbox/ssh | 09:44 |
| KotCzarny | and yes, sb will happily run arm binaries, just slower | 09:45 |
| KotCzarny | if you just need ssh for github access it might be easier path | 09:45 |
| ceene | why do you want for scratchbox to talk to github? | 09:46 |
| jonwil | I want to be able to pull git repos inside scratchbox | 09:46 |
| ceene | i would just do it from the outside | 09:46 |
| ceene | less of a hassle it seems | 09:46 |
| KotCzarny | jonwil, then just compile newer ssh statically and put somewhere in the inside path | 09:47 |
| jonwil | Looks like moving the host scratchbox ssh out of the way and then using the openssh-client package installed into Scratchbox allows gitlab to work | 09:47 |
| jonwil | the one compiled for ARM | 09:48 |
| jonwil | So for now I think I am good. | 09:49 |
| jonwil | The good thing about experimenting with this is that I was able to find the right magic to wire the dev VM itself (i.e. not the Scratchbox root) up to the correct Ubuntu archives so I can apt-get things for ubuntu now (as well as the SB chroot) | 09:51 |
| jonwil | So that's good. | 09:51 |
| jonwil | My ubuntu dev VM is now as up-to-date as its possible to get for a Lucid install :) | 09:52 |
| KotCzarny | maemo: i personally just hacked sb1 a bit into working minimal chroot i can run on arm board | 09:53 |
| KotCzarny | so i can compile natively | 09:53 |
| KotCzarny | (also on n900, but that's a side effect) | 09:53 |
| jonwil | I seriously doubt my poor little N900 could compile something as large as QT... | 09:55 |
| ceene | i remember i took a couple hours or something like that on a i7 with 16gb of ram | 09:55 |
| ceene | *it took | 09:55 |
| KotCzarny | jonwil: get 2gb orange pi +2e | 09:55 |
| KotCzarny | :) | 09:55 |
| KotCzarny | for fun and kicks | 09:56 |
| jonwil | Why would I do that when I have a perfectly good Ubuntu dev VM :) | 09:56 |
| KotCzarny | for arm freedom, ofc | 09:56 |
| KotCzarny | from great x86 oppression! | 09:56 |
| Oksana | KotCzarny : Good point, but I don't particularly like Raspberry Pi. It has HDMI port... | 09:58 |
| KotCzarny | no, rpi is bad hardware, the only good thing about it is big community, everything else is marketing | 09:59 |
| jonwil | I wish someone would make something that has all the functionality and features of the pi except without all the proprietary Broadcomm crap required | 10:00 |
| KotCzarny | jonwil, they do | 10:00 |
| KotCzarny | just google around | 10:00 |
| KotCzarny | arm boards market is growing fast | 10:01 |
| Oksana | KotCzarny : Any board in particular to have a look at? | 10:01 |
| KotCzarny | broadcom is as bad as qualcomm, they run machine in a machine | 10:01 |
| KotCzarny | oksana: it all depends what you need it for | 10:01 |
| KotCzarny | your question is kind 'what computer to have a look at' | 10:02 |
| KotCzarny | different one for cad, for gaming, for multimedia, for mobility, etc | 10:02 |
| Wizzup | isn't the pi 3d open source now? | 10:03 |
| KotCzarny | wizzup, you still get videocore managing you from above | 10:04 |
| Oksana | KotCzarny : Small ARM board that can run modern Linux, and work like a mobile/pocket battery-based phone/assistant (wireless connectivity can be USB-attachable, instead of hard-wired) | 10:04 |
| Wizzup | sounds like most arm boards | 10:05 |
| KotCzarny | oksana: look at c.h.i.p. with the case its nice form factor and pretty complete for mobility | 10:05 |
| KotCzarny | it's only single core, but if you dont demand fast web browsing it should do | 10:05 |
| Oksana | I got PocketChip, but too lazy to actually open and use it. And the company making CHIP has gone into insolvency since then. | 10:05 |
| KotCzarny | sure, but chip uses quite well reverseengineered software | 10:06 |
| KotCzarny | so you can do practically anything with it | 10:06 |
| Oksana | Will probably get around to actually configuring PocketChip somewhen. But currently, just shudder at thought of using Google Chrome to flash firmware onto PocketChip. | 10:06 |
| KotCzarny | lol | 10:07 |
| KotCzarny | then just learn what it does | 10:07 |
| KotCzarny | unless it has nand instead of emmc | 10:07 |
| KotCzarny | then you can just run it off sdcard and use dd to write firmware, or install os | 10:08 |
| jonwil | The TI OMAP found in the N900 is a pretty good chip. The GPU needs binary blobs but they aren't 100% essential, can be replaced with a FOSS driver if such a thing ever exists and are fully under the control of the user (the kernel-bits are 100% FOSS for example) | 10:08 |
| KotCzarny | hmm, it has nand, oh well, a bit trickier, but still doable | 10:09 |
| Oksana | Trickier, as in, use SD card for Chrome-free flashing? | 10:10 |
| KotCzarny | tickier as in legacy kernel nand driver and mainline kernel nand driver are different and incompatible | 10:11 |
| KotCzarny | *trickier | 10:11 |
| tom13 | hello/ what is the best use for a n900 with broken usb port? | 11:55 |
| KotCzarny | gift for a skilled developer | 11:58 |
| inz | N900 fly | 12:03 |
| tom13 | can the port be fixed? | 12:05 |
| KotCzarny | yes | 12:05 |
| KotCzarny | but not by novices | 12:05 |
| tom13 | i wish n900 had 512MB | 12:07 |
| tom13 | is someone in germany who fixes usb? | 12:07 |
| KotCzarny | yes, any gsm repair shop | 12:08 |
| KotCzarny | but better go to bigger/more renowned ones | 12:08 |
| tom13 | gsm? | 12:08 |
| KotCzarny | shabby work can make matters worse | 12:08 |
| KotCzarny | gsm as in cellphone | 12:08 |
| KotCzarny | or tablet | 12:08 |
| tom13 | ok | 12:08 |
| tom13 | i still have one with good usb | 12:09 |
| tom13 | should i epoxy it, or is that useless? | 12:09 |
| KotCzarny | ~usbfix | 12:10 |
| infobot | methinks usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or https://www.youtube.com/watch?v=fYz5nIHH0iY#t=1866, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt, or to avoid breakage, see ~usb-unplug | 12:10 |
| tom13 | ty | 12:12 |
| tom13 | is n900 basically only good for non-javascript browsing now? | 12:13 |
| KotCzarny | yup. you can use old fennec (firefox 17 for mobile) to get more sites working | 12:13 |
| KotCzarny | still, not much you can do with limited ram | 12:13 |
| tom13 | ty | 12:13 |
| KotCzarny | keep in mind fennec will be slow, but if you only need something clicked etc might be enough | 12:14 |
| KotCzarny | currently jonwil tries to update microb engine to support tls1.2 etc | 12:14 |
| tom13 | mhm | 12:14 |
| tom13 | wow | 12:15 |
| tom13 | i am chatting on droid 4 with sailfish now | 12:15 |
| tom13 | but maemo on droid 4 would be fun | 12:15 |
| KotCzarny | there is some work done in that direction | 12:16 |
| KotCzarny | see maemo-leste | 12:16 |
| KotCzarny | it's far from even beta yet, but .. | 12:16 |
| tom13 | would the n900 binaries run without recompiling on the omap4? | 12:17 |
| KotCzarny | depends on os | 12:18 |
| tom13 | with maemo-leste | 12:18 |
| KotCzarny | might | 12:19 |
| tom13 | so both are eh, armhf right | 12:20 |
| KotCzarny | no | 12:20 |
| KotCzarny | fremantle is using armel | 12:20 |
| tom13 | oh i haver armv7l | 12:21 |
| KotCzarny | armel vs armhf is about how libs and floating point are used | 12:21 |
| KotCzarny | both are for arm7l too | 12:21 |
| tom13 | how do i see if my sailfish is armel | 12:22 |
| KotCzarny | ldd maybe | 12:23 |
| KotCzarny | or dpkg -l |grep something | 12:24 |
| tom13 | k | 12:24 |
| tom13 | I ried n900 again. i cant go back to that keyboard. | 13:13 |
| tom13 | and xt894 has 4x cpu, 4x ram | 13:15 |
| dreamer | too bad maemo-leste doesn't run very well on it yet | 13:22 |
| dreamer | 61 | 13:23 |
| dreamer | woops | 13:23 |
| dreamer | 61 | 13:23 |
| dreamer | damnit. my ctrl-key is broken is smth. moment | 13:23 |
| Wizzup | tom13: the droid4 keyboard isn't as nice as the n900 keyboard, yeah | 13:34 |
| Wizzup | dreamer: on n900 or droid (or both?:P) | 13:34 |
| tom13 | whatOA | 13:35 |
| dreamer | Wizzup: I think he means other way around | 13:35 |
| tom13 | droid 4 is so much better | 13:35 |
| dreamer | and I meant droid4 | 13:35 |
| dreamer | :) | 13:35 |
| Wizzup | on the droid4 I miss keys all the time even though I do press them | 13:35 |
| tom13 | oh i have one droid4 with that problem | 13:35 |
| tom13 | swapped the mainboard | 13:36 |
| tom13 | s/have/had/ | 13:36 |
| tom13 | missed keypresses are unforgiveable | 13:36 |
| dreamer | never have that on my n900 | 13:36 |
| Wizzup | I think I might have it on both droids, but didn't test that proeprly | 13:37 |
| Wizzup | I mostlu use my n900 | 13:37 |
| tom13 | i still liked the maemo days best | 13:37 |
| Wizzup | :) | 13:37 |
| dreamer | I only use my n900 for calls/text/alarm/music/terminal | 13:38 |
| dreamer | the rest doesn't really work well. but I don't need much else from a 'phone' anyway | 13:38 |
| tom13 | a free n900 from nokia made it even funner | 13:38 |
| dreamer | dual core and more ram would maybe make browsing functional | 13:38 |
| tom13 | yeh n900 fm transmitter is very nice for me, car has no bluetooth | 13:38 |
| dreamer | :) | 13:38 |
| tom13 | i think kernel 4.14 fixed the large file copy hangup that n900 had | 13:39 |
| tom13 | you ever copy a 600MB iso to n900 microsd? | 13:40 |
| Wizzup | are you talking about linux cache? | 13:40 |
| tom13 | yes | 13:40 |
| Maxdamantus | kill -STOP cp .. kill -CONT cp .. | 13:44 |
| Maxdamantus | s/kill/killall/ | 13:44 |
| infobot | Maxdamantus meant: killall -STOP cp .. kill -CONT cp .. | 13:44 |
| Maxdamantus | s/$/g/ | 13:44 |
| Wizzup | 'sync' ? | 13:45 |
| Maxdamantus | sync doesn't help. | 13:45 |
| Maxdamantus | unless you mean as an option to `dd` | 13:45 |
| Maxdamantus | sync(2) basically just means "wait until the writes before now have been committed to disk" | 13:46 |
| Wizzup | doesn't help with what | 13:46 |
| Wizzup | slow IO can looks like hangups. | 13:46 |
| Maxdamantus | with throttling the copy. | 13:46 |
| Wizzup | did he ask on ow to do that? | 13:46 |
| Wizzup | I'm confused | 13:46 |
| Maxdamantus | I'm guessing he's referring to the behaviour where Linux will not block writes to slow devices until it runs out of memory for use by the disk cache. | 13:48 |
| Wizzup | right | 13:49 |
| Maxdamantus | so when copying a file from a fast device to a slow device, eventually you're going to end up with a system that won't be able to allocate/swap in pages until it has written some dirty pages to disk. | 13:50 |
| Maxdamantus | right, so the way you need to solve that is by somehow blocking/throttling the writes in `cp` before the system gets into that state. | 13:50 |
| Maxdamantus | which an external `sync(2)` doesn't do. | 13:51 |
| Maxdamantus | since all `sync(2)` does is wait for pages that were dirty before the call to no longer be dirty. | 13:51 |
| tom13 | yeh and this got addressed in 4.14 i think | 13:51 |
| Wizzup | surprising | 13:52 |
| Maxdamantus | (and possibly also encourage the underlying filesystem to commit faster) | 13:52 |
| tom13 | thank you for the killall tip | 13:52 |
| tom13 | or rather -STOP / -CONT | 13:53 |
| Maxdamantus | That's nice to know .. will try it soon. | 13:53 |
| bencoh | how did they address it then? | 14:22 |
| Maxdamantus | I'm guessing it's due to the changes in 547248..aac8d4 | 14:42 |
| Maxdamantus | though that was only merged into 4.15-rc1 | 14:46 |
| tom13 | my favorite quote of the day: "You don't even know what country i'm in. Much less which Kanton." :) | 18:38 |
| sparre | :-) | 19:03 |
| tom13 | so i think maybe 4 n900s is too much for me | 19:26 |
| tom13 | just need 1-2 for reference/nostalgia | 19:26 |
| tom13 | anyone need one | 19:26 |
| Wizzup | is it broken in any way? | 19:27 |
| tom13 | yea | 19:27 |
| tom13 | usb | 19:27 |
| tom13 | but with the right touch it charges | 19:27 |
| Wizzup | sounds like fixable usb :) | 19:30 |
| tom13 | nokia 770, n810 and n900 will always be some of my happiest memories | 19:38 |
| tom13 | but i already burned out with n900 | 19:38 |
| tom13 | but i'm still alive, unlike... gary | 19:38 |
| tom13 | maybe someday we do a youtube or webpage dedicated to him | 19:39 |
| tom13 | and liqbase? | 19:39 |
| tom13 | you know lcuk Wizzup ? | 19:39 |
| KotCzarny | yeah | 19:39 |
| KotCzarny | he was a great dev | 19:39 |
| tom13 | you see Wizzup we had the 770 and 800 - tablets which used a desktop click and scrollbar metaphor | 19:40 |
| tom13 | some of the game/emu devs started figuring out how to blit graphics to n800 screen faster | 19:41 |
| tom13 | and lcuk had the idea, of scrolling the screen with the finger pulling | 19:41 |
| tom13 | instead of a menubar | 19:41 |
| tom13 | i'm not sure if he was the first ever to do that | 19:42 |
| tom13 | but he was the first to do it on maemo | 19:42 |
| tom13 | me and lcuk and somebody else were at a conference in brussels | 19:43 |
| tom13 | we had taken a hotel room together | 19:44 |
| tom13 | were walking around the redlight district. had a bunch of beers | 19:44 |
| tom13 | we got tired and went back but lcuk decided he wanted to visit ... one of the people there | 19:44 |
| tom13 | a few hours later he came back... "guys - i got mugged :(" | 19:44 |
| tom13 | i lost the pictures | 19:45 |
| tom13 | KotCzarny: you should learn to make fun shader effects for linux mobile | 19:46 |
| KotCzarny | i had my own part of pixel processing engine | 19:46 |
| KotCzarny | see 'osc' | 19:47 |
| tom13 | you never got into shaders?\ | 19:50 |
| KotCzarny | not the usual 3d accelerated ones | 19:53 |
| KotCzarny | o.o | 19:58 |
| tom13 | i did some 2d shader work | 20:05 |
| tom13 | filtering for emulators | 20:05 |
| tom13 | have you seen shadertoy.com KotCzarny ? | 20:05 |
| KotCzarny | i think i was browsing it few years ago | 20:05 |
| KotCzarny | personally i prefer my pixel engine | 20:06 |
| tom13 | it is more flexible | 20:06 |
| KotCzarny | more flexible than dynamically compiled c code? | 20:06 |
| tom13 | but it's like pulling a cart with a hamster when you have a horse standing there | 20:06 |
| tom13 | osc is more flexible than shaders | 20:07 |
| KotCzarny | yes, i can use any c code / device i would want | 20:07 |
| tom13 | yeh but it gets boring at 8-12 fps | 20:07 |
| KotCzarny | without any user recompilation, core does it all itself | 20:07 |
| KotCzarny | depends on the code | 20:07 |
| KotCzarny | can be ran at higher fps with different algos | 20:08 |
| tom13 | yeah nothing against osc | 20:08 |
| tom13 | it's fun | 20:08 |
| KotCzarny | just different target | 20:08 |
| tom13 | did you see it running on the Archos 80 tablet? | 20:08 |
| KotCzarny | shaders are generally graphics only enhancers | 20:09 |
| KotCzarny | osc is for doing whatever hardware allows | 20:09 |
| tom13 | there are branching limitations | 20:09 |
| tom13 | in shaders | 20:09 |
| tom13 | but a lot of the copy operations and blend operations in osc | 20:09 |
| tom13 | could be done in shaders | 20:09 |
| tom13 | you remember original idea was to do something like goom | 20:10 |
| tom13 | the clouds effect | 20:10 |
| tom13 | copy, transpose, blend | 20:10 |
| KotCzarny | blend is for fluff | 20:11 |
| tom13 | ok you can apply a function to r,g,b, values too | 20:11 |
| KotCzarny | originally osc was about mixing algo with user input | 20:11 |
| tom13 | so can shader | 20:11 |
| KotCzarny | so each frame would be recreated | 20:11 |
| KotCzarny | and also to visualize various graphics algos | 20:12 |
| KotCzarny | and learn | 20:12 |
| tom13 | do you run osc on pc sometimes? | 20:12 |
| KotCzarny | sometimes, was a long time. mostly i just play on n900 | 20:13 |
| tom13 | how many people in maemo were in it to prevent tyranny? | 20:18 |
| Wizzup | tom13: nope, don't know him | 20:20 |
| tom13 | █▗ ▀▟▌▙ ▌▝ ▚▐ ▗▟▚▀▐▐▞▚▚▗▗▗▗▗ ▚▖█▝▗ ▘ ▖▗▗▚▐ ▚▝▚▌▚▀▗▚ | 22:06 |
| tom13 | ▘ ▙▌▌▙▗▟▐▚▜▙▗▗▘█▟▟▄▚▚▚▞▚▚▗▚▗ ▄▗▘▖▖ ▗▗ ▗▗ ▚ ▟▄▛▚▄▝▝█▝ ▐▞▐▗▞▖▖▘▗▗ ▌▖▘▌▞▖▘▘█▜▛ | 22:06 |
| tom13 | ▚▙▐▙▄▛▌▝█▛▗▝▘▖█▟▟▐▞▚▌▚▚▌▖▞█▝ ▖▗▗▗▐▐▝▌▖▚▚▝▝▀▀▀▝▀▝█▝▗▗█▗▗▗▗ ▚ ▘█▄▚▗▝█▟▞▞▞▀▀▙▐▞▌▙▗▖▖▞▐▝▞▝▝▖▖▖▐ | 22:06 |
| tom13 | ▐▟▞▌▌ ▌▘ ▙▗ ▟▟▐▚▌▌▐▐▐▚▘▗█▘█▗█▘ ▚ ▚ ▖▀▝▝ ▌▖▘ ▚▗ ▖▖▗█▝▝█▘▚▗▗█▄▚▙▙▚▌▚▞▄ ▄▐▀▚▚▚▚▘▘ ▚ | 22:06 |
| tom13 | ▛ ▜▞▞▚▜▚ ▐▗█▘█▟▙▜▌▙▚▐▐▞▞▗▘▖▌▘▘█▘▝ ▖▄█▘▘▖▚▝▖▜▐█▘▘▌▌▄▞▙▄▄▚▐▗█▗▗ ▗▗▗ ▄▄▞▚▗ ▐▐▐▐▐▗▐▗ | 22:06 |
| tom13 | █▖ ▚▟▖▙▙▗▚ ▚▗█▖ ▟▜▟▞▞▚▀▚▜ ▗█▘▘▘ ▗ ▌▝▖▙▞▀▄▀█▘▗▗▄▄▄▄▄▀▀▀▀ ▚▄▄▄▘▝▝█▘▖▚ ▐ ▙▄▄▀▛▞ | 22:06 |
| tom13 | █▝ ▌▗▌▛▖▟▘ ▚ ▗ ▘ ▌▘▌▌▌▐ ▘█▖▗ ▗█▘▘▀▄▀▄▟▄▚▀▚▀▐▄▄▄▄▄▄▞▄▄▄▄▄▄▚▝█▖▘▀▀▀▄▗█▘▝▗ ▌▛ | 22:06 |
| tom13 | ▛▙▜▚▞ ▚ ▌▘▖▗█▖█▙▜▜▟▐▐▙ ▝█▖▌▝▗█▀▀▗▄▀▀▄▄▀▀▌█▝█▖▖▝▖▖▝▗▗ ▚ ▘▀▀▀▄▄▄▙ ▐ ▀▝▖▘▐ ▚▌ | 22:06 |
| tom13 | ▞▟▚▜▛▌▘ ▐▝▐█▘▚▗ ▚▝▐▗▗ ▘█▘▘▗ ▞▀▄▀ ▟▀▀▜▝▝▖▗█▘▘▘▗█▘▗ ▚▗█▟▜▙▜▟▟▟▞▟▟▞▟▗▄▙ ▖▚ ▘▖ ▀▀▐▌ | 22:06 |
| tom13 | █▜▙▜▚▚▜▘ ▚▝▝▖▌▌▘▖▖▗▟▟▀▗ ▖▖▖█▟▝▞▀▀▄▀▀▖▝█▜▜▙▜▙▜▙▙▙▙▛▙▙▜▙▜▛▙▛▙▛▙▌▙▞▙▙▐▚▚▚▗▟▄ ▄▚ ▗█▖ ▛▐▐ | 22:06 |
| tom13 | ▛▐ ▚▜ ▚ ▀▙▙▚▄▞▞▐▚▖ ▚▗▗ ▘▝▖▝▀▘▜ ▀▀▀▗▗█▘▘▖▖▘▗▗ ▌▝▝▝▖▝▗█▘▗ ▐▜▟▟▙▜▟▞▟▐▜▞▙▚▚▖▖█▙▄▄▘▖▗ ▚▌▖█▟▟▄ | 22:06 |
| Wizzup | thanks Sigyn ... | 22:08 |
| Wizzup | glad you're here... | 22:08 |
| KotCzarny | :) | 22:08 |
| sicelo | :p | 22:09 |
| Wizzup | /s | 22:09 |
| DocScrutinizer05 | slow though | 22:16 |
| DocScrutinizer05 | should act more trigger happy against ascii art and color | 22:16 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!