IRC log for #maemo-ssu on 20120116

00:05.17*** join/#maemo-ssu MohammadAG (~MohammadA@ool-44c62415.dyn.optonline.net)
00:05.20*** join/#maemo-ssu MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG)
00:48.59*** join/#maemo-ssu Raimu-X (~rmaunula@130.231.241.29)
01:26.33*** join/#maemo-ssu Estel_ (~Estel@d35-11.icpnet.pl)
02:10.28*** join/#maemo-ssu Kaptenen (~Kaptenen@81.216.60.47)
03:05.20*** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn)
04:15.26*** join/#maemo-ssu psycho_oreos (~no@115.131.9.233)
05:18.44*** join/#maemo-ssu RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net)
05:34.21*** join/#maemo-ssu Timmo_ (~smuxi@46.115.18.229)
06:45.11*** join/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
07:16.47*** join/#maemo-ssu Timmo_ (~smuxi@46.115.25.89)
07:40.56*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
08:00.52*** join/#maemo-ssu dafox (~dafox@dyn-194228.nbw.tue.nl)
08:06.26*** join/#maemo-ssu scoobertron (~tom@93.186.148.226)
08:46.00*** join/#maemo-ssu DocScrutinizer (~halley@openmoko/engineers/joerg)
08:49.46DocScrutinizerno it's not
08:49.49*** mode/#maemo-ssu [+o DocScrutinizer] by ChanServ
08:49.56*** mode/#maemo-ssu [+b estel_!*@*] by DocScrutinizer
08:50.02*** mode/#maemo-ssu [-o DocScrutinizer] by ChanServ
08:50.11DocScrutinizernow it's "fixed"
08:50.51DocScrutinizerban for messing with infobot, exploiting it in a way that might cause infobot to get taken down from whole freenode
08:51.46DocScrutinizer**despite lovingly and in epic length explaining the problem to estel_ and asking him to stop that behaviour**
08:52.10psycho_oreoso.O I thought suddenly all of the maemo/meego related channels became active heh
08:52.47DocScrutinizer~onjoin -DocScrutinizer
08:52.47infobotDocScrutinizer: ok
08:53.17DocScrutinizer~chanset #maemo-ssu OnJoin=0
08:53.17infobotOnJoin=0 for #maemo-ssu is not set.
08:53.34DocScrutinizer~chanset #maemo-ssu OnJoin 0
08:53.34infobotSetting OnJoin for #maemo-ssu to '0'.
08:53.58DocScrutinizermumbles swearwords
08:54.53psycho_oreosmuses the thought of DocScrutinizer swearing in Deutsch ^^
08:56.13DocScrutinizermuses going thru all 121 chan infobot/apt is in, to set OnJoin 0, so moron estel_ won't abuse it there tomorrow
08:56.39*** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm)
08:57.11DocScrutinizerand even then he could abuse it in private query, making random nonsense onjoin msgs for any *new* channel infobot joins that I haven't immunized yet
08:57.50psycho_oreosideally you need to setup logins based on nickname
08:58.02DocScrutinizerSERIOUSLY pissed
08:58.58DocScrutinizernah, onjoin is a poorly designed cmd in infobot, and estel_ exploits the fact in all ways he could think of
09:00.01DocScrutinizerI'd disable it globally, if only I wouldn't already know it's been used for 'good' as well, by reasonable knowledgeable chanops
09:00.06psycho_oreosyeah but what I meant is that you might be able to set onjoin only available to certain uses.. or you can be really nasty and change the command completely to another name that estel wouldn't knot
09:00.18psycho_oreoss/uses/users/
09:00.22DocScrutinizerno, that's not how it's implemented
09:00.37psycho_oreosoh ffs, typo galore
09:00.44psycho_oreoshmm ok
09:00.56DocScrutinizerand I can't mess with infobot's source, I'm only admin of that bot
09:01.02psycho_oreosguesses changing the name of the command would be a nasty hack then :)
09:01.16psycho_oreosahh
09:02.08DocScrutinizerI *could* do chanset _default OnJoin 0
09:02.17psycho_oreospretty annoying that you can simply rename a command without changing the source and recompiling.. I mean even with all that effort it is a fair bit of hassle
09:02.42DocScrutinizerbut that'S like breaking a basic function for 10.000s of users
09:03.13DocScrutinizerTimRiker can do that in a minute
09:03.21DocScrutinizerbut not me
09:03.55psycho_oreosthinks its one heck of a brain****** that would be lol.. somehow its all correlated and yet complex
09:03.57DocScrutinizerI pinged him about that onjoin issue several times now, but he's not very available for this kinda stuff
09:04.57DocScrutinizer@chanops: you're free to unban estel, after a bit of shouting at him
09:05.52DocScrutinizerexiting rage mode, entering daywork mode (1h late now >:-( )
09:06.11psycho_oreosjust say you had family issues ;)
09:06.40DocScrutinizerthey know I'm a bot - bots have no family
09:06.55psycho_oreosthen you shouldn't be working there lol
09:07.20psycho_oreoseven bots do have a life to go through before they die heh
09:07.59psycho_oreosthinks he just contradicted himself with that bit of last statement there
09:08.07psycho_oreossurely there has to be a valid excuse somewhere
09:08.24psycho_oreosanyway have fun
09:19.17*** join/#maemo-ssu m0use (~m0use@office.wargaming.net)
10:04.38*** join/#maemo-ssu taziff (~taziff@82.139.137.210)
10:06.47*** join/#maemo-ssu Robot101_ (~robot101@iota.hadesian.co.uk)
10:09.47*** join/#maemo-ssu Milhouse (~irc_milho@Maemo/community/contributor/Milhouse)
10:10.09*** join/#maemo-ssu FireFly (firefly@firefly.xen.prgmr.com)
10:11.09*** join/#maemo-ssu Timmo_ (~smuxi@176.1.237.6)
10:20.57*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
10:22.23*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
10:24.02*** join/#maemo-ssu Timmo_ (~smuxi@46.115.12.246)
10:36.45*** join/#maemo-ssu taziff (~taziff@82.139.137.210)
11:01.34*** join/#maemo-ssu andre__ (~andre@85.207.98.106)
11:01.34*** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre)
11:05.54*** join/#maemo-ssu arcean (~Arcean@aafq165.neoplus.adsl.tpnet.pl)
11:28.53*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
11:39.51*** join/#maemo-ssu scoobertron (~tom@161.23.254.198)
11:51.19*** part/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
12:14.40*** join/#maemo-ssu Timmo_ (~smuxi@46.115.40.87)
12:44.40*** join/#maemo-ssu lizardo (~lizardo@189.2.128.130)
12:45.28*** join/#maemo-ssu scoobertron (~tom@161.23.254.198)
13:01.28*** join/#maemo-ssu arcean_ (~Arcean@aacz1.neoplus.adsl.tpnet.pl)
13:31.52BCMMthe new camera-ui is telling me that there is no space for new photos, when df says otherwise. is this a known problem?
13:32.31*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
13:33.28arceanBCMM: bug 12516
13:33.30povbotBug https://bugs.maemo.org/12516 Error Message camera-ui: "Not enough memory to save photo"
13:33.40BCMMarcean: thanks!
13:44.17*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
13:48.26*** join/#maemo-ssu taziff (~taziff@178.182.3.76.nat.umts.dynamic.t-mobile.pl)
14:00.41*** join/#maemo-ssu scoobertron (~tom@161.23.254.198)
14:08.02*** join/#maemo-ssu taziff_ (~taziff@178.182.230.221.nat.umts.dynamic.t-mobile.pl)
14:12.18*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
14:21.32*** join/#maemo-ssu taziff_ (~taziff@cyr108.internetdsl.tpnet.pl)
15:29.12Lava_Croftmubles about update
16:02.52*** part/#maemo-ssu taziff (~taziff@cyr108.internetdsl.tpnet.pl)
16:15.53gulymerlin1991: uploading new version/packages to repo via scp is okay?
16:59.37*** join/#maemo-ssu scoobertron (~tom@93.186.148.226)
16:59.59*** join/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
17:00.16merlin1991guly: not really unless you mean scpign to some incoming dir where a cronjob picks up packages and adds them to repo
17:10.27gulyexactly
17:11.15merlin1991which has been exactly what I did on maemo.org :)
17:11.31*** join/#maemo-ssu NIN101 (~NIN101@2001:530::216:3cff:fe71:5e1e)
17:13.26gulydupload or straight scp?
17:14.20merlin1991straight scp
17:14.35merlin1991though dupload worked too (mag used it)
17:16.56merlin1991DocScrutinizer: I guess that interests you: http://www.youtube.com/watch?v=mSJtUbnM46E (n9 dismantling)
17:19.24*** join/#maemo-ssu NIN102 (~NIN101@2001:530::216:3cff:fe71:5e1e)
17:32.48*** part/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
17:35.11*** join/#maemo-ssu AndrewX192 (~andrew@unaffiliated/andrewx192)
18:19.51*** join/#maemo-ssu MohammadAG (~MohammadA@ool-44c62415.dyn.optonline.net)
18:19.54*** mode/#maemo-ssu [+o DocScrutinizer51] by ChanServ
18:20.19*** mode/#maemo-ssu [-b estel_!*@*] by DocScrutinizer51
18:20.20*** join/#maemo-ssu xnt14 (~xnt14@ool-44c62415.dyn.optonline.net)
18:20.34*** mode/#maemo-ssu [-o DocScrutinizer51] by ChanServ
18:29.09*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
18:41.09*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
19:20.03*** join/#maemo-ssu NIN101 (~NIN101@2001:530::216:3cff:fe71:5e1e)
19:29.00*** join/#maemo-ssu trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623)
19:36.34*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
19:40.25merlin1991MohammadAG: how's the update building going?
19:57.14*** join/#maemo-ssu Kaptenen (~Kaptenen@81.216.60.47)
19:57.14*** join/#maemo-ssu gregoa (~gregoa@chello212186032184.406.14.vie.surfer.at)
19:57.16*** join/#maemo-ssu scoobertron (~tom@93.186.148.226)
19:57.22*** join/#maemo-ssu chainsawbike (~chainsawb@chainsawbike-1-pt.tunnel.tserv25.sin1.ipv6.he.net)
19:57.30*** join/#maemo-ssu DocScrutinizer (~halley@p5493B41F.dip.t-dialin.net)
19:57.33*** join/#maemo-ssu DocScrutinizer (~halley@openmoko/engineers/joerg)
19:57.36*** join/#maemo-ssu FireFly (firefly@firefly.xen.prgmr.com)
19:57.41*** join/#maemo-ssu NIN101 (~NIN101@2001:530::216:3cff:fe71:5e1e)
20:01.31*** join/#maemo-ssu m0use (~m0use@178.120.114.253)
20:04.35*** join/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
20:07.46*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
20:24.16*** join/#maemo-ssu Pali (~quassel@unaffiliated/pali)
20:37.53*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
21:15.42*** join/#maemo-ssu Estel_ (~Estel@d35-11.icpnet.pl)
21:16.08Estel_Thanks, DocScrutinizer ;)
21:16.28DocScrutinizerthaks for not yet banning you forever??
21:16.46Estel_merlin1991,  is there any place I can find specification for hildon-desktop memory leakage fix in ?
21:16.51DocScrutinizer[2012-01-16 20:57:30] *** Das Thema wurde am 2011-07-25 04:09 von DocScrutinizer!~halley@openmoko/engineers/joerg gesetzt.
21:16.53Estel_thanks for unbanning me here
21:16.53DocScrutinizer[2012-01-16 20:57:32] <apt> just checking if it's fixed on ssu channel
21:16.54DocScrutinizer[2012-01-16 20:57:34] <apt> just checking if it's fixed on ssu channel
21:16.56DocScrutinizer[2012-01-16 20:57:47] *** Kanalmodi: +Cn
21:16.57DocScrutinizer[
21:17.07DocScrutinizerwill be reverted in a second
21:17.21Estel_didn't touch anything
21:17.45Estel_I swear. ;)  I just returned after our last talk
21:17.52DocScrutinizerso why AGAIN this crap spammed 2 dozen channels?
21:17.57Estel_no idea.
21:18.08Estel_really, haven't touched it.
21:18.24Estel_it seem that this onjoin is really cool option, though :/
21:18.50DocScrutinizerit's a bit more complex than posix cmdline "echo"
21:19.17*** part/#maemo-ssu mirandir (~valentin@2a01:e35:2e63:5170:7a2b:cbff:fed1:407c)
21:19.30Estel_agreed. I think I'll stay with lart, thou.
21:19.36Estel_~lart Estel_
21:19.36infobotgives Estel_ an extra strength ACME sleeping pill, sending Estel_ to sleep for 150 years, and awakening to seven strange dwarfs and a large apple
21:19.45DocScrutinizerand it's not obvious like hitting somebody with a baseball bat that omitting [#cahn] causes onjoin to work on ALL channels
21:20.17Estel_hey, infobot is talking about permaban?
21:20.19Estel_erm
21:20.23Estel_now it is ;)
21:20.33DocScrutinizerand that you can have multiple onjoins for multiple channels
21:20.39Estel_You just sit on too many channels, face it. It spams only where You're
21:20.47Estel_ok.
21:21.12Estel_so, it is actually permitted for use by regular user *with* channel specified, or it's absolutely denied?
21:21.37Estel_I mean that is there a easy way to disable it by receiver after receiving?
21:22.47Estel_maybe I could fix it by writin [onjoin] -DocScrutinizer
21:22.48Estel_?
21:22.55Estel_should it delete it?
21:23.14Estel_last time seemed to work. just don't wanna try it without asking ;)
21:25.15Estel_should be fixed now, I hope
21:25.41infobottakes DocScrutinizer to the vet for a "special" visit, courtesy of estel_
21:26.18*** join/#maemo-ssu rd (~rd@p57B49754.dip0.t-ipconnect.de)
21:26.20DocScrutinizerEstel_: DO NOT TOUCH OnJoin
21:26.39Estel_Just asking.
21:26.53Estel_AFAIK -[nick] removes it
21:27.18DocScrutinizerwe are about to replace the command with something causing infobot to make user get klined nstead of bot
21:27.35DocScrutinizerEstel_: and I did exactly that
21:27.41DocScrutinizerand it re-appeared
21:27.56Estel_isn't it that user who set it must execute it?
21:28.02DocScrutinizerno
21:28.10Estel_last time it worked only after I - it, remember?
21:28.14Estel_h
21:28.16Estel_as You wish
21:28.28Estel_I havent touched it, though, and it's still alive
21:28.33DocScrutinizerthere's only ONE onjoin per destination nick per channel plus _default
21:28.35*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
21:28.43Estel_I see.
21:29.04*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
21:33.02DocScrutinizerwell, when you swear you haven't touched it, I will ask Tim for logs
21:33.12DocScrutinizerto see why it came back
21:33.21DocScrutinizerand whom to kickban
21:35.50DocScrutinizerlast week I didn't know what you have set, a global or a chan specific onjoin
21:35.59DocScrutinizeror both
21:36.32DocScrutinizeror maybe something even more tricky (also possible, but I would rather eat my tongue than telling you)
21:37.23DocScrutinizerand you *might* have noticed infobot lacks a ~list-onjoins command
21:39.24DocScrutinizerbut beware, infobot already has a general ~ignore <nick> function
21:39.49DocScrutinizerWe always hoped we don't need it
21:40.04DocScrutinizerbut it's easy to activate
21:44.36DocScrutinizeranyway until now onjoin got rarely used, so there was no problem with it - users acted responsible. Thanks to you demonstrating that reasonable users are not the norm anymore, onjoin might get deactivated globally now
21:45.51Estel_You oversimplifing, of course. Its not matter of 'responsible', rather, most users havent got idea about this function
21:46.21DocScrutinizeruntil you came spreading the news about how to abuse it
21:46.52Estel_Of course instead of actually thanking me from checki,ng it - even, when it resultedd in quite unexpected chain of events - You're threatening me with ban for a few hours.
21:47.01Estel_well, I havent told anyone
21:47.39Estel_You're running around and screaming, even if fix for it is as simple as [onjoin] -DocScrutinizer
21:47.42DocScrutinizerI'm generally not saying "Thank you" when somebody demonstartes me that my hammer can be used to hit my foot
21:47.56Estel_without Your temporal ban on -ssu there would not be even single public talk about it
21:48.18Estel_well, actually, You got steel foot ;) Honest excuses for inconveicence
21:48.20AndrewX192We should start a fork of maemo for arguments
21:48.21DocScrutinizerHAHAHAHA
21:48.31Estel_but You're clearly overreactive
21:48.34AndrewX192Maybe make a maemo SSU with lots of chat programs
21:48.40AndrewX192Defaulting to debate channels
21:48.41DocScrutinizerEstel_: again you don't realize you spammed DOZENS of channels
21:48.52Estel_I realize it. well.
21:48.59AndrewX192We should call it the DocScrutinizer SSU
21:49.04Estel_afaik "spammed" mean one single message, when doc joins
21:49.26AndrewX192Each installation will come with infobot source code for review of issues
21:49.32AndrewX192and a local ircd
21:49.55DocScrutinizerAndrewX192: there are already channels for that, for *real* developers, not trolls like you
21:50.08AndrewX192DocScrutinizer: excuse me?
21:50.15Estel_well, we're already talking about it 543456x longer than real issue was happening
21:50.21AndrewX192^
21:50.49Estel_if You ( DocScrutinizer ) want to red through logs for that, I'm fine with it - just be sure to check timestamps
21:51.03Estel_as I've not touched onjoin before issue -re-appeared
21:51.18DocScrutinizerEstel_: yeah, amazing isn't it? Especially that after all that talking you still haven't understood how onjoin works
21:51.54Estel_and invoked some help about function syntax, then, [onjoin] -DocScrutinizer it. All *much* after issue re-appeared
21:52.09Estel_now I understand, I hope. Not going to use it, if its so flawed though
21:52.31AndrewX192What is onjoin anyway?
21:52.33Estel_I can really imagine You going berserker again over finding that something is wrong again, be it my fault or not
21:52.44Estel_I won't tell You, ask DocScrutinizer  :P
21:53.39DocScrutinizerAndrewX192: it's what you are commenting about all the time, suggesting I should "forget about the problem" - is that honest to suggest to forget about a problem that you don't even knowWHAT it is?
21:54.07AndrewX192DocScrutinizer: Because your arguments weren't constructive in #maemo
21:54.26Estel_ok, have nice conversation gentlemans, I'm off ;)
21:54.36DocScrutinizerof course for somebody not even knowing onjoin my posts were not very helpful
21:55.08*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
21:58.10DocScrutinizerjust wonders why it never occurred to estel_ that for *trsting* he could set onjoin to *own* nick, rather than *mine*
22:02.16DocScrutinizerquize obviously the better testing method as the tester has a chance to see the test result, rather than not even being online when onjoin triggers. Plus it probably wouldn't have caused so much hot emotions by pestering/abusing others
22:03.31DocScrutinizergenerally unsolicited "tests" on public productive systems rarely are welcome
23:20.29*** join/#maemo-ssu Estel_ (~Estel@d35-11.icpnet.pl)
23:48.38Estel_guly,  hi there. How our "special" things are going? No unexpected problems?

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.