[00:02] <sidi> well
[00:02] <sidi> now would be good
[00:02] <sidi> gf has arrived though
[00:02] <knome> heh
[00:07] <knome> well, ping me once you've done that
[00:08] <sidi> knome, i templated encryption, i'll let you fill the blanks with the *buntu specifics
[00:08] <sidi> also added a Dropbox mention in the backup, advising encryption prior to uploading
[00:10] <knome> mhm
[00:10] <knome> this document is very welcome
[00:10] <knome> i will add your name to the doc contributors list
[00:10] <knome> hooray
[00:14] <sidi> knome, done.
[00:14] <sidi> knome, feel free to mention UCL Information Security ;p
[00:15] <knome> sidi, let's see
[00:15] <knome> what else do i owe you? :P
[00:15] <sidi> nothing mate :p
[00:16] <knome> you come here and i'll buy you a beer or two
[00:17] <sidi> haha sure
[07:08] <Unit193> < darkxst> apw, what is the status of bug 1410480? this completely breaks installing via ubiquity on Ubuntu GNOME and probably most other flavours  ||  < ~pitti> yes, it's not flavor specific, happens for ubuntu as well
[07:09] <Unit193> Heads up.
[07:22] <ochosi> mm, good to know
[08:11] <ochosi> brainwash: your patch should be moved along shortly, then we can prep the SRU paperwork. seb128 said it's SRU-worthy
[10:18] <slickymasterWork> sidi, knome, thanks for https://docs.google.com/document/d/18sEImteNJVZ7T6o0RR7erJbCpS8dXwHDC0pRpu1K3aI/edit#heading=h.zafoylvno00b 
[10:18] <slickymasterWork> it's a fabulous work
[10:18] <sidi> slickymaster, erm you're welcome :p
[10:19] <slickymasterWork> not sure also about the xkcd comic
[10:20] <slickymasterWork> I don't think it would land particularly well in the all -docs layout
[10:21] <slickymasterWork> but other than than it's really a fabulous piece of work
[10:21] <slickymasterWork> s/than than/than that
[10:25] <slickymasterWork> like knome, I also owe you a couple of beers, so if you ever come down south I'll be more than glad to do it ;)
[10:28] <brainwash> ochosi: that's good news
[10:29] <ochosi> yup
[10:29] <ochosi> not totally unexpected, but still good :)
[10:29] <ochosi> btw, we shouldn't select a reviewer directly when filing a MR
[10:30] <ochosi> cause then ubuntu-branches gets removed and nobody else sees it, i.e. it drops off the radar
[10:30] <brainwash> ah ok
[10:30] <ochosi> had to figure that out when passing along the MR today
[10:30] <ochosi> so just for the future, to keep that in mind, always add reviewers after filing the MR on top of the default
[10:47] <slickymasterWork> knome, are you working on a MP based on sidi's paper or do you want me to do it?
[10:57] <sidi> slickymaster, south of US? too far for beer :P
[10:58] <sidi> slickymaster, it's up to you two now to decide how to turn this into a Xub doc.
[11:05] <slickymasterWork> sidi, south like in Iberian peninsula ;)
[11:05] <slickymasterWork> specifically the western country in europe
[11:07] <sidi> slickymaster, spanish or portuguese or catalan? ;P
[11:07] <slickymasterWork> portuguese :)
[11:07] <slickymasterWork> we're western than them
[11:27] <brainwash> ochosi: https://www.debian.org/security/2015/dsa-3131
[11:32] <brainwash> so there will be another patch before the -screensaver one
[11:33] <brainwash> or both patches will be shipped at the same time
[12:30] <knome> slickymasterWork, yep, i guess so ;)
[12:30] <slickymasterWork> lol knome, and that means ....
[12:31] <knome> that i'll do it and ask for your help if needed :P
[12:31] <knome> the thing is, there are still things that aren't ready
[12:31] <slickymasterWork> ok, I'm here to help you know
[12:31] <knome> for example, do we have unattended upgrades enabled on a new install?
[12:31] <knome> if not, how to turn them on?
[12:32] <slickymasterWork> I'd say that in two out of three times people will face unattended upgrades, afeter a new install
[12:33] <slickymasterWork> * after
[12:33] <knome> why 2/3 ?
[12:33] <slickymasterWork> unless they're installing in the immediate hour after the releases
[12:33] <knome> heh
[12:33] <knome> well can somebody double-check that?
[12:34] <slickymasterWork> I can perform a few tests on that, but  either Unit193 or bluesabre could cast some technical light on that issue
[12:35] <knome> https://help.ubuntu.com/community/AutomaticSecurityUpdates
[12:35] <knome> i guess we only need to see if we have a file in apt.conf.d
[12:36] <slickymasterWork> I'll boot a VM after lunch to see if I can check that
[12:36] <knome> sure
[12:54] <brainwash> bluesabre: thanks for the xubu default settings upload
[12:55] <knome> has anybody used any of the password managers in the repository?
[12:59] <brainwash> bluesabre: do you feel like SRU'ing the updated keyboard shortcuts file to utopic and trusty? utopic only needs the 1 line fix, trusty needs http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/revision/482 on top of that
[13:00] <brainwash> it would be great if you could fix this for 14.04.2, so new users who download this release won't be affected by the bug
[13:01] <elfy> knome slickymasterWork - http://pastebin.ubuntu.com/9784842/ our /etc/apt/apt.conf.d/50unattended-upgrades
[13:01] <knome> mhm
[13:01] <knome> so we have that enabled
[13:02] <knome> thanks
[13:02] <brainwash> not having it enabled would be kinda strange
[13:13] <knome> elfy, are you still on a new installation?
[13:14] <elfy> newish knome 
[13:14] <knome> ok
[13:14] <knome> can you check what the "updates" tab in software & upgrades say
[13:14] <elfy> I can - but ... 
[13:14] <knome> mostly interested in the three first dropdowns
[13:14] <knome> but what? :D
[13:14] <elfy> I'll boot vm 
[13:15] <elfy> the updates tab might be all over the place here :D
[13:15] <knome> huhu
[13:15] <knome> probably not though;)
[13:15] <knome> and this is for the V docs anyway
[13:15] <knome> so should be the situation in V
[13:15] <elfy> but - nvm - a clean install in that tab has all EXCEPT proposed enabled
[13:15] <knome> so what about the dropdowns?
[13:15] <knome> what are the values?
[13:16] <elfy> oh - hang on 
[13:16] <elfy> half asleep
[13:17] <knome> hehe
[13:17] <knome> me too
[13:17] <knome> always a good mood to write security documentation in!
[13:18] <elfy> http://www.zimagez.com/zimage/screenshot-190115-131753.php
[13:18] <knome> ok, i think i've mostly converted sidi's stuff to digestable text
[13:18] <elfy> any others while the vm's running?
[13:18] <knome> hmm, display immediately
[13:18] <knome> not download and install automatically
[13:18] <knome> ochosi, bluesabre, Unit193: want to investigate that?
[13:19] <knome> elfy, not at this time, thanks :)
[13:19] <elfy> ok :)
[13:19] <knome> or is that like so only because it's beta stage
[13:19] <knome> i'll run a trusty install or sth later today
[13:19] <elfy> hang on - I'll boot the trusty one 
[13:19] <knome> oh, ok ;)
[13:20] <sidi> knome, let me know when it's online ;P
[13:21] <elfy> knome: display immediately in the one with pink highlights
[13:21] <elfy> which I think was the last one ...
[13:21] <knome> sidi, probably takes time, it'll need to go to the branch first, then zyl needs to push it online
[13:21] <knome> and we'll probably not do that until release
[13:21] <knome> sidi, do you need it for something?
[13:22] <knome> i mean i can push a copy of that somewhere if you want to show it around
[13:22] <sidi> i dont need it now nope
[13:22] <knome> ok
[13:23] <knome> then expect it around april
[13:23] <sidi> okay ;p
[13:23] <knome> i can also poke you when it's on the branch
[13:23] <knome> so you can get it yourself!
[13:24] <ochosi> elfy: xnox did a recent update to that part, but afaik he only dropped the extra repo
[13:24] <ochosi> no idea what's supposed to be ticked exactly and what not
[13:24] <ochosi> (i presume the first two)
[13:24] <knome> ochosi, i was thinking that whether the unattended security updates should be on...
[13:24] <knome> not which repositories are ticked
[13:25] <elfy> I saw talk on extras - but that's in Other Software - not Updates
[13:34] <ochosi> knome: right, misinterpreted that maybe in the backlog
[13:34] <ochosi> didnt read too closely i guess
[13:34] <ochosi> elfy: btw, what you could check in the next update to xubuntu-artwork that bluesabre pushed/s today is whether that bluetooth icon is monochrome again
[13:34] <ochosi> it's one of the things i fixed
[13:52] <elfy> ochosi: well it is monochrome here after update and restarting panel and turning bluetooth on
[13:52] <elfy> but if it changes color during use - no way of checking that 
[13:53] <ochosi> it was only !monochrome in the "normal" state
[13:53] <ochosi> inactive and paired state worked
[13:54] <elfy> http://en.zimagez.com/full/6e676846acce0827817defaa1cf6b75464fa83b2bc94d3596924c0fb25bf0a9db891b39655ffc10a8a913820beaf444de21558616cb0271a.php
[13:54] <elfy> good lord - that's a long url
[13:55] <knome> in the shortish ;)
[13:55] <knome> what's that banana bumerang
[13:55] <knome> or is it an orange slice
[13:55] <elfy> bananamoon
[13:55] <ochosi> clemetine
[13:55] <ochosi> clementine
[13:56] <elfy> oh that - yea clementine 
[13:56] <ochosi> elfy: yeah that's the inactive state
[13:56] <elfy> ochosi: so - no way for me to check the other states 
[13:57] <ochosi> you can't activate bluetooth?
[13:57] <ochosi> you just need to click the item and then > "turn bluetooth on"
[13:58] <ali1234> ochosi: what does it mean if there's a bug report with "Theme parsing error: gtk.css:81" but gtk.css doesn't even have 81 lines?
[13:59] <ochosi> it shouldn't, but maybe it's continuing with the line-count in one of the included files
[14:00] <ali1234> hmm
[14:01] <ali1234> i think this might just be user error
[14:01] <ochosi> possible, what app throws it with what theme in what version of gtk3?
[14:02] <ali1234> all of them with orion in utopic, apparently
[14:02] <ali1234> an lots of other errors that don't seem to match up with anything in the css
[14:02] <ali1234> i think user might have an old version installed in their home directory
[14:02] <ochosi> yeah, that's quite possible
[14:02] <ochosi> many of the bugreports i got for gtk3 had wrong theme versions installed
[14:02] <ochosi> i get that all the time
[14:03] <ali1234> going to install utopic in a vm to test
[14:03] <ali1234> thanks for the hints
[14:03] <elfy> ochosi: clicking it - it changes to 'white' but I don't have any access to any bluetooth other than that
[14:03] <ochosi> ali1234: either way, fixing this level of bug in utopic is likely not a priority
[14:04] <ochosi> elfy: that's perfect, and all i wanted to hear. in your previous screenshot from the VM (if you remember) it was on a blue bg, and that should now be gone
[14:04] <elfy> nope - not remembering that :)
[14:04] <elfy> but - glad your happy :)
[14:04] <ochosi> let me remind you then: http://www.zimagez.com/zimage/screenshot-190115-131753.php
[14:05] <ochosi> see how blue that is?
[14:05] <elfy> oh right - yea
[14:05] <elfy> didn't even look at that vm - was just seeing what knome wanted :D
[14:05] <elfy> and 'this' machine has bluetooth off 
[14:06] <knome> ;)
[14:10] <brainwash> ochosi: it seems like xfpm + light-locker triggers suspend out of nowhere (according to the latest comment in bug 1307545)
[14:11] <ochosi> i read that, but i'm pretty sure that signal isn't coming from light-locker
[14:12] <ochosi> it doesn't send suspend signals, it only listens to those
[14:12] <ochosi> and about the power manager i'm not sure either, might be something else
[14:15] <brainwash> ochosi: so, xfpm -> light-locker > vt switch > logind takes control in vt8 > suspend is triggered > screen is locked twice in vt7 > blank screen bug?
[14:16] <brainwash> not sure about the "screen is locked twice" part though
[14:19] <brainwash> ochosi: I hope you understand this reaction chain :)
[14:21] <brainwash> the solution seems to be to always late lock the screen
[14:22] <brainwash> even when screen lock is triggered via light-locker-command
[14:22] <ochosi> was that the thing that always worked?
[14:22] <ochosi> not sure that locking twice is really happening or really the source of the problem
[14:23] <brainwash> that thing?
[14:23] <ochosi> the setting (late locking)
[14:25] <brainwash> I don't know, the dbus activation uses 2 steps, first lock the screen in vt7 and on resume switch to vt8
[14:25] <brainwash> similar to late locking
[14:25] <brainwash> and it never caused trouble I think
[14:26] <brainwash> but xflock4 -> light-locker-command will instantly switch to vt8
[14:27] <ochosi> so yeah, we could try to patch xflock to send a dbus command :}
[14:27] <ochosi> err, dbus signal
[14:28] <brainwash> is there one? currently light-locker listens to the suspend and resume signal from logind
[14:29] <ochosi> i was actually kidding
[14:29] <ochosi> i guess xfpm would have to be more intelligent about light-locker
[14:30] <brainwash> yes, but light-locker is limited too, you cannot enable late locking on the fly
[14:31] <brainwash> late locking aka "lock screen in vt7" > "suspend" > "resume" > "switch to vt8"
[14:32] <brainwash> without loignd
[14:32] <brainwash> maybe ask cavalier about this
[14:33] <brainwash> also, the elementary os team might encounter something similar
[14:38] <knome> http://bazaar.launchpad.net/~ubuntu-core-doc/xubuntu-docs/vivid/revision/281
[14:38] <knome> sidi, slickymasterWork, ochosi, elfy ^
[14:39] <elfy> lol - scared him away then 
[14:39] <knome> yep
[14:39] <slickymasterWork> already pushed knome?
[14:39] <knome> yes
[14:39] <elfy> why firewall? 
[14:40] <knome> elfy, read teh section :D
[14:40] <elfy> Use common sense when working in the web - should that no be on rather than in
[14:40] <elfy> or are we spiders from mars ? 
[14:40] <knome> elfy, that's the removed chapter ;)
[14:40] <knome> green are additions
[14:40] <elfy> oh yea
[14:40] <elfy> I hate these things :|
[14:40] <knome> heh
[14:41] <knome> just get the latest branch version then and run make
[14:41] <knome> ;)
[14:41] <knome> or see https://docs.google.com/document/d/18sEImteNJVZ7T6o0RR7erJbCpS8dXwHDC0pRpu1K3aI/edit?usp=sharing
[14:41] <elfy> that's betterer
[14:41] <knome> elfy, you're a platypus
[14:42] <elfy> yep
[14:42] <elfy> poisonous 
[14:42] <knome> heh
[14:42] <knome> no, just anonymous, regarding google
[14:42] <elfy> oic 
[14:43] <elfy> mmm
[14:43] <elfy> so missing words? 
[14:46] <knome> where?
[14:46] <elfy> exactly !!!
[14:46] <knome> what
[14:46] <elfy> how did you guess :p
[14:46] <knome> .
[14:46] <knome> :P
[14:46] <elfy> Use common sense when working in the web
[14:46] <knome> wha?
[14:47] <elfy> oh bah
[14:47] <knome> silly
[14:47] <knome> :)
[14:47] <elfy> attackers can damage your reputation and websites nobody
[14:47] <elfy> where between websites and nobody :)
[14:48] <ali1234> that whole sentence
[14:48] <ali1234> i had to read it about five times to even understand it
[14:49] <slickymasterWork> ok knome, I'll have a read to your rev later on at home
[14:50] <ali1234> i think in that section it's worth mentioning that the website owner might be able to see your password, not just attackers. and the website may even have been set up to steal passwords
[14:54] <knome> you can refer to the security expert sidi
[14:55] <ali1234> i added a comment on the doc
[14:55] <knome> if you do changes in the doc, mark them with comments so i'll catch the changes
[15:08] <elfy> read it - makes sense to me
[15:17] <sidi> Is there a buggy bug in the doc?
[15:17] <sidi> blame it on knome.
[15:17] <sidi> ali1234, we could talk about phishing indeed
[15:17] <sidi> it's good to know though that the odds are against us
[15:17] <sidi> essentially phishing is uncommon/unexpensive enough at a global scale
[15:18] <sidi> that even having users spend 2 minutes a year on avoiding phishing attacks is economically counter-productive
[15:18] <ali1234> i'm not talking bout phishing
[15:29] <knome> also updated the translation template so people can get translating soonish
[15:30] <slickymasterWork> great knome, thanks
[15:31] <knome> np
[15:33] <knome> slickymasterWork, we should start thinking the installer slideshow content and looks some day
[15:34] <slickymasterWork> yes, you're right knome 
[15:34] <slickymasterWork> do you already have something in mind, regarding the artwork?
[15:35] <slickymasterWork> or you want to do that after we finish the text part
[15:35] <knome> nothing apart that i want it updated, maybe in the direction of the website
[15:36] <slickymasterWork> aesthetically?  
[15:36] <knome> yes
[15:36] <knome> one aspect we might want to rethnk is the paths that we show in the slideshow
[15:36] <knome> are they needed?
[15:36] <knome> and should we try to point more to the documentation?
[15:36] <knome> i mean, more than in one place?
[15:37] <knome> since we do have it up-to-date and relatively broad now
[15:37] <slickymasterWork> well, in terms of text/info on the slides we're not shipping any major new things, apart from a few changes in some apps
[15:37] <knome> sure, but maybe we want to flesh out the text anyway
[15:37] <slickymasterWork> yeah, the paths could be something to be review
[15:38] <knome> anyway, when we start working on that, i'd figure out what kind of content we want there first
[15:38] <slickymasterWork> won't to schedule a sprint for us?
[15:38] <slickymasterWork> lol
[15:38] <knome> hmpf
[15:38] <slickymasterWork> why hmpf?
[15:38] <knome> let's schedule the scheduling for later
[15:39] <knome> but something this month
[15:39] <knome> do you have any preferences/days that simply won't work?
[15:39] <slickymasterWork> preferably at night
[15:39] <knome> wfm
[15:40] <slickymasterWork> after 22:00 UTC everything works for during week days
[15:40] <knome> weekday or weekend?
[15:40] <slickymasterWork> on weekends it would be better the ones my kid isn't with me
[15:41] <knome> which are those?
[15:41] <slickymasterWork> so I think it would be preferable week days after 22:00  
[15:41] <knome> ok
[15:41] <knome> hmm
[15:41] <knome> i'll consult my wife today on her shifts
[15:41] <slickymasterWork> ok
[16:12] <knome> ochosi, ping me when you're back
[16:15] <ochosi> knome: pon
[16:15] <ochosi> g
[16:15] <knome> oh :)
[16:15] <knome> will PM you
[17:07] <brainwash> bluesabre: https://code.launchpad.net/~thad-fisch/xubuntu-default-settings/use-gsettings-for-ll ?
[17:09] <brainwash> bluesabre: ok or not ok?
[22:33] <slickymaster> knome, it doesn't have to be now, but tomorrow we could discuss your rev of the docs
[22:34] <knome> slickymaster, i can do that in some time
[22:34] <knome> so if you have comments, just pour them in
[22:34] <slickymaster> well, I not to sure about the opening of the chapter
[22:35] <knome> it's better than before
[22:35] <knome> though that doesn't say much
[22:35] <knome> it was basically listing the ToC before
[22:36] <slickymaster> we're talking about a about a major subject, one that ought to be read carefully by our users, but at the same time we're almost telling them to at least read just a few subsection of it
[22:37] <slickymaster> on one hand we tell them "This is a brief guide on keeping your computer and personal information safe from security threats. "
[22:37] <slickymaster> but on the other we go about " If you only have a short while, you should read at least the following subsections:
[22:37] <slickymaster> I don't no, it seems a bit of a paradox to me
[22:38] <slickymaster> not sure if I made myself clear to you k
[22:38] <slickymaster> knome: 
[22:39] <knome> sure
[22:39] <knome> how else would you highlight the most important parts of the chapter?
[22:39] <slickymaster> that's the thing, I wouldn't, we start it by saying that it's a breif guide
[22:41] <slickymaster> I don't think you should make it briefer by inviting people to short circuit its read
[22:41] <knome> well tbh
[22:41] <slickymaster> even because its a really important subject
[22:41] <knome> it's not very brief...
[22:42] <knome> i would have hard time reading that if i didn't know most of it already
[22:42] <slickymaster> no it isn't, but I'm ok with its extension
[22:42] <knome> so maybe we shouldn't tell it's brief ;)
[22:42] <slickymaster> that would be a solution
[22:42] <slickymaster> I can drop that setence
[22:43] <slickymaster> as I found a typo in the chapter I can do both things
[22:43] <knome> maybe we should just face it and say it's written by a security student and that "if you had seen the original version, *then* you'd consider this brief"
[22:43] <slickymaster> is there a original version?
[22:43] <knome> not any more
[22:43] <knome> it was a rant by sidi
[22:44] <knome> i made it digestible
[22:44] <slickymaster> why not just drop the adjective 'brief' from that initial sentence?
[22:44] <knome> that works for me
[22:46] <slickymaster> ok, I'll do it then and push it
[22:46] <knome> thanks
[22:46] <sidi> slickymaster, remember this: users are EXTREMELY unmotivated by security
[22:46] <sidi> so, never ever waste their time
[22:46] <slickymaster> lol, the other way around knome, it's me you have to thank you 
[22:46] <sidi> that's why silly advice like "firewalls" must die
[22:46] <sidi> it pollutes their "compliance budget"
[22:47] <sidi> it's better, if they cant be bothered to go through the whole thing, to point them out to the absolute critical points
[22:47] <knome> though that's true for every subjet
[22:47] <knome> +c
[22:48]  * knome punches the C key
[22:48] <slickymaster> I can see that point sidi, that's just one more argument for me to force them to read it, and to avoid in any possible their lack of attention on such a big issue
[22:48] <sidi> it's like building up habits, you dont become a gym master in 24 hours if you were a couch potato. And since you barely see the positive externalities of security even after so many months/years, it's hard to motivate yourself into learning more security
[22:48] <sidi> slickymaster, they'll tell you to **** *** if you *force* them :p that'd be a terrible UX move
[22:48] <knome> sidi, tut tut
[22:49] <sidi> knome, sorry i dont mean to say that myself
[22:49] <sidi> i mean that the reaction will be extreme
[22:49] <ochosi> the knome train is rolling in..?
[22:49] <knome> choo choo
[22:49] <knome> nope
[22:49] <sidi> and, you dont suspect how people behave about technology that gets in the way when you're not watching
[22:49] <knome> ochosi, reversed the max-width ;)
[22:49] <slickymaster> the intention here isn't to force sidi, it's just not to help them being so casual about it all
[22:50] <slickymaster> nor eight, nor eighty
[22:50] <ali1234> it's funny how people turn into computer geniuses when they want to read reddit at work
[22:50] <sidi> slickymaster, i'm not casual about security. it's just very important to accept that we can achieve very little by asking users to invest in security
[22:50] <ali1234> but can't figure out how to restart a print job
[22:50] <sidi> they shouldnt have to
[22:50] <sidi> ali1234, exactly 
[22:50] <knome> just as funny as when everybody is an advanced user when a tutorial says "advanced users only:"
[22:51] <knome> maybe we should word it in a way that the important parts are the ones they should START with
[22:51] <sidi> you can only except a few minutes a day from a person to do all sorts of security-related tasks. whenever they need to login on a service, decide whether to open an email/file/app, register on a service, share files with others... they make tons of security decisions and they lose motivation quickly
[22:52] <knome> slickymaster, ^ see, this is near the original version rant :)
[22:52] <sidi> even when you dont follow advice, you dont necessarily get into trouble, and when you do follow it you can still have issues, and you see none of the attacks being blocked
[22:52] <knome> slickymaster, ^ and that
[22:52] <ali1234> yet they can follow any arbitrary amount of instruction 100% perfectly when they think they are going to get a free iphone
[22:52] <knome> wait, free iphones, where?
[22:52] <sidi> yeah, high perceived benefit ali1234 
[22:52] <sidi> security = low perceived benefit, high perceived cost
[22:52] <ali1234> yeah
[22:53] <slickymaster> I'm not trying to imply that all sidi, I know you're not casual about it, what I'm saying is that we shouldn't let the users be lazy about it just because they're used to and we shouldn't chnage those habits
[22:53] <knome> slickymaster, what about my latest proposal for wording? ;)
[22:53] <sidi> slickymaster, let's make a parallel
[22:53] <slickymaster> you'ver pushed another rev knome ?
[22:54] <knome> slickymaster, no, i said that in the channel, but you probably missed it from the discussion
[22:54] <knome> slickymaster, --> maybe we should word it in a way that the important parts are the ones they should START with
[22:54] <slickymaster> I did :P
[22:54] <knome> that would fix our issue
[22:54] <sidi> say, your parents are obese and are starting to show signs of heart disease. you want to convince them to change their diet and exercise. they personally have a fatalist attitude and think nothing they can do will pay off. how do you go about it?
[22:54] <knome> sidi, wow, are we going deep :P
[22:55] <sidi> (economics of security for end users: http://discovery.ucl.ac.uk/1301853/1/compliance_budgetfinal.pdf // http://www.is.uni-muenster.de/security/publications/BG2011_Security_Cost_of_Cheap_User_Interaction_NSPW.pdf)
[22:55] <knome> sidi, we're trying to fix the wording on the documentation, not save anybody's life
[22:55] <ali1234> i guess nobody is immune to this, people just have different priorities
[22:55] <sidi> (everyday security practice http://users.ece.cmu.edu/~adrian/630-f05/readings/dourish-grinter-delgado-joseph.pdf)
[22:55] <slickymaster> I woulf fight that fatalism sidi 
[22:55] <sidi> slickymaster, how?
[22:55] <sidi> that's the £100000 question
[22:55] <sidi> if you know how, i'll tip my boss into hiring you
[22:56] <knome> but no £1000000 ? :(
[22:56] <sidi> nah, that one is "how to get people to encrypt their emails?"#
[22:56] <slickymaster> mind me, we, as in Portugal', are famous for suffering from fatalism since the 18th century
[22:56] <ali1234> ihpones only cost about $600 right?
[22:56] <slickymaster> how?
[22:57] <slickymaster> make them, one way or the other, face the serious implications that that fatalism will, for sure, bring to their health
[22:57] <sidi> fatalism is an outcome of people making efforts and not observing any difference. it's the whole expectations that people have that are broken
[22:57] <sidi> they think they "should/deserve to" be safe if they make efforts
[22:57] <sidi> but risk prevention never works that way. accidents still happen
[22:57] <sidi> you can only look at risk situations by looking at global statistics
[22:57] <slickymaster> but they have to make some sort of an effort sidi 
[22:58] <sidi> yet people will select whatever rare event occurs to them  and inflate it because bias of availability.
[22:58] <sidi> slickymaster, yes but if you ask them more than they are willing to, they will quickly ignore you entirely
[22:58] <sidi> that's why we must prioritise security advice towards the most critical issues
[22:58] <sidi> when they are habituated to not run random scripts from forums, it'll already be a massive victory
[22:59] <sidi> and the practice, which is rife in linux communities, must be globally fought back. only when it's gone you can move on to the next topic
[22:59] <slickymaster> I agree with you entirely on that sidi, please don't missunderstand what I'm saying
[22:59] <ochosi> night all
[22:59] <sidi> night ochosi 
[22:59] <slickymaster> night ochosi 
[22:59] <knome> nighty ochosiy
[23:00] <ochosi> thanks knomey (and all others)
[23:00] <knome> thanksy!
[23:01] <slickymaster> what I'm saying is that people, like you pointed out, tend to be lazy and to always take the easier and shortest route, even more if they're invited to do it at the very begining
[23:01] <sidi> slickymaster, actually [UX evaluation needed, but] I expect people will  read the first two/three paragraphs, then scroll through that doc and read the section titles only
[23:02] <ali1234> that's what i did
[23:02] <sidi> there should be some research into how people read newspaper texts, it's fairly consistent
[23:02] <slickymaster> yes, I knome 
[23:02] <sidi> so you can use pictures, excerpts written in massive fonts, etc. to catch users' attention throughout the doc and disturb that scrolling down habit
[23:02] <slickymaster> ali1234 :P
[23:02] <sidi> vivid colors attract the eye too
[23:03] <sidi> slickymaster, if they want the short route, make the short route more appealing so they want to stop on the side. dont say "Nope,  I disagree, go for the detour instead it's better for you"
[23:03] <sidi> unfortunately the customer is always right ;-)
[23:04] <slickymaster> ok, sidi, in your opinion dropping the adjective 'brief', from "This is a brief guide on keeping your computer and personal information safe from security threats." will in any way change the way they're goping to read the chapter?
[23:04] <slickymaster> ali1234, would that have changed the way you read it?
[23:05] <ali1234> probably
[23:05] <ali1234> it's hard to say, i mean i already know all this stuff
[23:05] <sidi> slickymaster, it might. i dont take a side without A/B testing on that one
[23:05] <slickymaster> what would be different ali1234?
[23:05] <ali1234> different?
[23:06] <slickymaster> in what different way you think you've read it?
[23:06] <sidi> slickymaster, it depends on whether people consider it brief or not in the first place, and on whether they trust you or not
[23:06] <slickymaster> that's exactly it sidi 
[23:06] <sidi> if they dont trust you, they might be inclined to disagree that it's brief
[23:06] <ali1234> well speaking of newspapers
[23:06] <ali1234> if i see a picture in an article i'll try to scan through the article to know more about the picure
[23:06] <sidi> if they trust you, they might think that even though it's long there's a lot more to it (which reinforces the feeling that security is only for experts, etc.)
[23:06] <sidi> i mean, this thing is damn too long
[23:07] <sidi> the content is here, but the structure is painful for users, methinks
[23:07] <ali1234> i read the business section in the telegraph
[23:08] <ali1234> if there's ever news about a clothing company, or a movie company or something, they'll *always* use a picture with a pretty lady in it
[23:08] <ali1234> and it works on me... every time
[23:08] <slickymaster> putting the trust aspect aside (lets assume they trust the docs) do you think that just by having the brief adjective in that setence will catch more interest in the reading itself?
[23:09] <slickymaster> if yes, don't you think that the follwoing setence puts that already gained interest to loss when they're invited to go through a sort of a digest?
[23:10] <slickymaster> * sentence
[23:10] <slickymaster> sidi: 
[23:13] <sidi> slickymaster, sorry had to afk
[23:14] <sidi> was looking for painkillers Q.Q
[23:14] <slickymaster> bummer
[23:14] <sidi> slickymaster, i dont think the phrasing of that sentence is ideal
[23:14] <sidi> but the intro should, in a way or another, deliver the take-home message
[23:14] <sidi> because in this kind of documents people wont read through the conclusion
[23:15] <slickymaster> I agree on that
[23:16]  * slickymaster scratches head
[23:16] <sidi> sorry guys got urgent work to do
[23:16] <sidi> and im so tired
[23:16] <sidi> i can help later, but not now
[23:16] <sidi> still gotta do the damn UX survey too :-(
[23:16] <slickymaster> thanks for all the work you've done so far sidi 
[23:18] <Unit193> knome: keepassx.
[23:18] <knome> tell slickymaster 
[23:18] <sidi> slickymaster, its funny putting down the content doesnt feel like work for me ;P
[23:18] <sidi> the shape, however, is :p
[23:18] <slickymaster> lol
[23:19] <slickymaster> I already use it Unit193 
[23:21] <Unit193> You asked. :P
[23:22] <Unit193> slickymaster: There's also the mono keepass2, or if you pull the package from Debian there's the keepassx that supports the newer database format, but the UI isn't as good as the current keepassx.
[23:23] <knome> Unit193, oh you replied for that question
[23:23] <knome> i thought you told me it's keepassx, not keepass
[23:24] <slickymaster> the docs mention keepass, not keepassx
[23:24] <knome> yes, but the package name at least for trusty is keepass
[23:24] <slickymaster> I'm actually vety satiefied with keepassx
[23:24] <slickymaster> * very
[23:24] <knome> i like manual encfs stuff.
[23:25] <slickymaster> satisfied
[23:25] <Unit193> !info keepass
[23:25] <knome> well, semi-automated
[23:25] <Unit193> !info keepassx
[23:25] <Unit193> !info keepass2
[23:25] <knome> aha
[23:25] <knome> slickymaster, mind changing that?
[23:25] <slickymaster> opes, I'll do it
[23:25] <knome> KeePassX being the right casing?
[23:26] <slickymaster> replace it by what? 
[23:26] <knome> we say KeePass
[23:26] <knome> replace with KeePassX
[23:26] <Unit193> knome: If you use that one, yes.
[23:26] <slickymaster> ok, that one it will be
[23:26] <knome> Unit193, probably
[23:26] <knome> i don't know about password managers, and if you say it's better....
[23:26] <slickymaster> I'm still facing that first sentence
[23:27] <slickymaster> I'm quite happy with keepassx
[23:27] <knome> :)
[23:27] <knome> didn't you just say that? :D
[23:27] <AgAu> does keepassx work with keefox and such to work with thunderbird and firefox?
[23:27] <Unit193> keepass2 may have plugins that work with it, but it is mono.
[23:28] <slickymaster> I'm tired knome 
[23:28] <knome> slickymaster, awwh
[23:28] <slickymaster> :P
[23:28] <knome> Unit193, i was asking earlier because i needed to make another pick for the tip-box
[23:29] <knome> pick pasaffe because i know the maintainer by name, and it had a relatively recent release (nov 2014)
[23:29] <Unit193> AgAu: Ah cool, so plugins do generally work with keepass2?  Bah..
[23:29] <knome> why are these citruses so hard to peel!!!!
[23:30] <AgAu> im using keepass 2.28 with mono and keefox
[23:30] <knome> btw, that should be my next random quote
[23:30] <AgAu> so all my passwords get auto filled in thunderbird and ff
[23:30] <pleia2> knome: want to take a look at the proposed text for our stickers+qa post? pad.ubuntu.com/QAIncentive
[23:30] <knome> no
[23:30] <knome> but i can
[23:30] <pleia2> lolz
[23:30] <pleia2> thanks :P
[23:31] <pleia2> top of the pad, elfy and I worked on it a bit the other day
[23:31] <slickymaster> pleia2, defence or defense?
[23:31] <slickymaster> Unit193 ^^
[23:31] <pleia2> slickymaster: defense
[23:31] <knome> Manual testing of the development version of the Xubuntu development cycle.
[23:31] <slickymaster> thought so, also
[23:31] <slickymaster> thanks pleia2 
[23:31] <knome> pleia2, is the start supposed to be like that?
[23:31] <pleia2> knome: you're welcome to fix what's icky :)
[23:32] <knome> ugh
[23:32] <knome> :)
[23:32] <pleia2> probably need to say *during the* development cycle
[23:32] <knome> you are mussing a verb
[23:32]  * pleia2 fixed
[23:32] <knome> missing too...
[23:32] <pleia2> hmm, I could have sworn that made sense at some point
[23:32] <knome> haha
[23:41] <bluesabre> good evening folks
[23:41] <bluesabre> brainwash: nice, good one
[23:41] <bluesabre> I'll merge that in :)
[23:43] <Unit193> Howdy.
[23:43] <knome> pleia2, is it any better now?
[23:44] <pleia2> knome: yes, thank you :) I'll prep this on the wordpress later and maybe we publish tomorrow
[23:45] <knome> i think we should also move the thanks section somewhere
[23:45] <knome> it's kind of lost there
[23:45] <knome> especially the mention of future competitions is kind of hidden
[23:45] <pleia2> concluding with thanks is a kind of natural thing
[23:45] <knome> *potential
[23:45] <pleia2> maybe move the future thing up 
[23:46] <knome> should the unixstickers mention go down to thanks?
[23:46] <pleia2> probably
[23:47] <knome> much better
[23:48] <pleia2> woo editing at the same time
[23:49] <knome> if you are fine with this, i can dump it to WP
[23:49] <pleia2> sure
[23:49] <knome> ok, doing that now
[23:50] <pleia2> probably wait to publish until tomorrow though (holiday in the US today, lost of people missing from the intertubes)
[23:50] <knome> sure
[23:51] <slickymaster> knome: what do you think of: "Keeping your computer and personal information safe from security threats is one of the most important aspects of today's computing. This guide aims to help you achieving it, paying a particular attention following subsections:"
[23:51] <pleia2> knome: thank you for your help :)
[23:52] <slickymaster> + to the before ".... following subsection:"
[23:52] <knome> pleia2, np
[23:52] <slickymaster> corrected: "Keeping your computer and personal information safe from security threats is one of the most important aspects of today's computing. This guide aims to help you achieving it, paying a particular attention to the following subsections:"
[23:52] <knome> slickymaster, put that in a pad or sth and i'll poke it next
[23:54] <slickymaster> knome -> 
[23:54] <slickymaster> http://pad.ubuntu.com/Lfsfxme4JA
[23:57] <knome> pleia2, http://xubuntu.org/?p=2921&preview=true
[23:58]  * knome releases post edit lock
[23:58] <pleia2> knome: ooh, we shold put a picture of the bundle in too
[23:59] <knome> yes
[23:59] <slickymaster> wfm knome 
[23:59] <pleia2> grabbing the one that is on the bundles page is fine I think
[23:59] <pleia2> I could take a picture of them myself, but probably not as pro :)
[23:59] <knome> pleia2, or you can take a photo of them and you!
[23:59] <knome> who cares about pro!
[23:59] <pleia2> haha