**** BEGIN LOGGING AT Wed Dec 21 03:00:00 2016
Dec 21 06:55:05 <sixwheeledbeast> Mr_Pingu: My QtCreator is in the SDK I believe. Someone else has forked my repo so I assume it works fine.
Dec 21 06:55:09 <sixwheeledbeast> ~sdk
Dec 21 06:55:10 <infobot> it has been said that sdk is http://privatepaste.com/e4a5b13fad or "wget http://repository.maemo.org/tabletsdev/explicit/maemo-dev-env-downloads/downloads/Readme_Ubuntu_Lucid_Desktop_SDK_Virtual_Image_Final.txt"
Dec 21 07:31:59 <Mr_Pingu> ah I am using the halftux SDK, because that VM is way faster.
Dec 21 07:32:16 <Mr_Pingu> Will try in original SDK
Dec 21 07:44:41 <sixwheeledbeast> What errors you getting when building?
Dec 21 10:36:27 <Mr_Pingu> sixwheeledbeast: It just failes on building debian rules.
Dec 21 10:37:01 <Mr_Pingu> doesn't say much why :(
Dec 21 11:26:13 <Wizzup> Can the n900 SoC show different output on the tv-out?
Dec 21 12:20:03 <sixwheeledbeast> Mr_Pingu: Maybe it's my build environment, if you look in Projects and check over the build settings you may spot something.
Dec 21 12:20:56 <Mr_Pingu> That the problem, I don't have enough knowledge to spot that
Dec 21 12:21:27 <Mr_Pingu> But it could be very much my installation, see answer of halftux on TMO
Dec 21 12:25:48 <DocScrutinizer05> PALI!!! <3  you promoted bootmenu 1.14 :-)
Dec 21 12:26:36 <Pali> finally maemo.org infra accepted it
Dec 21 12:29:17 <DocScrutinizer05> first legit update since years
Dec 21 12:32:43 <DocScrutinizer05> ...on my system. Other than CSSU
Dec 21 12:34:59 <DocScrutinizer05> thanks to you and fmg!
Dec 21 12:39:17 <Pali> bah! for one week somebody is trying to brute force my freenode password!
Dec 21 12:39:39 <Pali> and stuff on #freenode just say "change password & ignore it"
Dec 21 12:40:44 <Pali> I'm starting to fell upset as ignoring any security attack is the worst what can they do...
Dec 21 12:43:42 <KotCzarny> just change it to something long
Dec 21 12:43:52 <KotCzarny> and dont forget to take a note of it
Dec 21 12:46:42 <Pali> but it is stupid to ignore such problem
Dec 21 12:46:56 <KotCzarny> maybe its common problem they cant easily mitigate?
Dec 21 12:47:27 <Pali> no idea, staff just told me that it could be broken client
Dec 21 12:47:35 <KotCzarny> adding login timeout wouldnt help because it could lock YOU out
Dec 21 12:47:56 <Pali> but broken client connected to some botnet...
Dec 21 12:48:39 <Pali> if I change my nick from Pali (to e.g. Pali_) then that attacker connect to freenode
Dec 21 12:48:55 <Pali> until I have nick Pali, I just got SaslServ error
Dec 21 12:49:17 <Pali> after I release nick Pali then I got NickServ error that user "Pali" failed to auth
Dec 21 12:49:32 <Pali> which means that person must be available on freenode
Dec 21 12:50:20 <KotCzarny> but see my point on dynamic ip, how would you block such user without harming others?
Dec 21 12:51:42 <KotCzarny> they might mitigate notifications about password failures to 1/day or something
Dec 21 12:52:42 <Wizzup> Pali: you can ghost people when they use your name
Dec 21 12:53:07 <Pali> that ip seems to be always same
Dec 21 12:53:36 <Pali> what do you mean with ghost people?
Dec 21 12:56:58 <Wizzup> Nickserv allows you to boot people off the network if they use your nick but are not identified
Dec 21 12:57:17 <Wizzup> you can also set strict nickname protection, which means people have only 30s to identify to the nickname, otherwhise they are force renamed
Dec 21 12:59:40 <Pali> Wizzup: right I have this 30s limit already set
Dec 21 13:00:10 <Pali> if I unset it, then that problematic person should connect to freenode with my nick
Dec 21 13:00:15 <KotCzarny> hehe, booting till freenode klines the offender?
Dec 21 13:00:19 <Pali> and I should be able to write him?
Dec 21 14:04:09 <DocScrutinizer05> Pali: there's actually zilch that can get done when somebody "tries brute-forcing your password"
Dec 21 14:06:14 <DocScrutinizer05> Wizzup: freenode actually only renicks the offender
Dec 21 14:06:46 <DocScrutinizer05> ghost mainly meant for autheticated client zombies
Dec 21 14:07:04 <DocScrutinizer05> regain is a nice command
Dec 21 14:07:46 <DocScrutinizer05> I log in via SASL with a temporary nick, then authenticate and regain my original nick
Dec 21 14:08:51 <DocScrutinizer05> which helps for all sorts of trouble, mainly my own stalled login of a few minutes ago that got disrupted by the DSL reconnect, but also for any nickname squatters
Dec 21 14:09:22 <DocScrutinizer05> and it reliably ensures my cloak being applied before I /join any channels
Dec 21 14:10:04 <DocScrutinizer05> (the authenticate part is bogus, not neede with SASL anymore, it's obsolete legacy)
Dec 21 14:10:32 <DocScrutinizer05> regain automatically changes my nick to the regained one
Dec 21 14:11:02 <DocScrutinizer05> while same time "booting" any other user or client that uses that nick
Dec 21 14:11:56 <DocScrutinizer05> also helps for releasing timed blocks that nickserv places on enforced nicks when they're "abused"
Dec 21 14:12:04 <DocScrutinizer05> iirc
Dec 21 14:12:23 <DocScrutinizer05> /ns help regain
Dec 21 14:12:27 <DocScrutinizer05> /ns help release
Dec 21 14:14:43 <DocScrutinizer05> Wizzup: you regained yourself? ;-)
Dec 21 14:14:58 <Wizzup> irssi was stuck in poll
Dec 21 14:15:02 <DocScrutinizer05> hah
Dec 21 14:15:06 <Wizzup> tried to fix it with gdb but to no avail
Dec 21 14:15:18 <DocScrutinizer05> sucks
Dec 21 14:34:11 <DocScrutinizer05> Pali: make sure your password is complex enough so the amount/number of "failed auth attempts" reported to you on log in is way too low to ever brute force it by chance. Nickserv auth is slow, so brute force password hacking is considered impossible
Dec 21 14:45:12 <Mr_Pingu> sixwheeledbeast: I keep getting fails on dpkg-buildpackage from your repo. Tried pierogi and that build fine
**** ENDING LOGGING AT Thu Dec 22 02:59:59 2016