14:00:34 #startmeeting ux monthly sync 14:00:34 Meeting started Tue Sep 7 14:00:34 2021 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:43 good morning everyone :) 14:00:57 who's all here for today's UX team meeting? 14:01:27 o/ 14:02:39 o/ 14:02:56 hi both!! 14:03:01 nice to see you antonela ^^ 14:04:18 hellohello 14:04:28 hi antonela o/ 14:04:57 looks like it might just be us today 14:05:15 which gives us plenty time to talk about the first VPN survey :D 14:05:26 great stuff! 14:05:48 would you like to give a general introduction to the script you've been working on nah? 14:05:58 and then we can review and add comments together? 14:06:08 yes! 14:06:13 ty! :) 14:07:09 we're working on a "discovery" study to understand our user needs regarding vpns 14:07:22 we'll use a survey for this study 14:08:07 with two screens, (1) demographics with focus on vpn uses - if the user use a vpn already, with they use vpn with tor, wwhy they use vpn, why they use tor 14:08:34 one of the things we aim with this is to have a listing of most mentioned vpns 14:09:22 for the second part of the study (2) we'll ask questions to understand users needs regard privacy, security and anonymity when using vpn 14:09:33 as well their understanding of fingerprinting 14:09:41 and risks involved when using tor with third-party apps 14:10:56 for recruitment we will use mailing lists and tor browser banners 14:12:27 for context antonela, our planned workflow for the research phase is: vpn discovery study -> competitor analysis -> vpn features study/workshop(s) -> brand study/workshop(s) 14:12:46 (I think I've got the order right) 14:12:50 lovely 14:12:51 (i added the pad to the meeting pad) 14:13:00 thanks nah! 14:13:04 yep! thanks, duncan! 14:13:44 every time we met a group someone asked "how i can route all my desktop traffic via tor" 14:14:07 that sounds a sensible roadmap! 14:14:21 ha yess, ty! 14:14:37 i think one of the challenges of this study is to ask the right questions to understand user needs regarding privacy/security/anonymity. 14:14:50 and if they understand the difference between these terms 14:15:01 nah: I did a more detailed review this morning nah and added more comments to the pad, I think it's looking great though 14:15:58 let me know if you have any Qs! 14:16:52 hmm should we explain what a tor-powered vpn would be? 14:17:26 I was kind of thinking if we rolled those Qs together and presented the question _with_ the list, it's more obvious what we mean 14:17:31 if that makes sense? 14:18:13 and then we don't need to worry about the exact wording of the Q so much 14:19:00 (just an idea, feel free to disagree) 14:19:37 oh sorry nevermind nah, I misread your question! 14:19:55 I thought you were referring to Q1 14:20:06 hehe 14:20:19 maybe in the summary of the second screen 14:20:20 love the idea of trying to shape/define mental models around privace, security and anonimity, the nice thing is trying to link it with the product we can offer 14:20:30 *privacy 14:20:39 *anonymity 14:21:04 * antonela new keyboard is w e i r d 14:21:46 like explaining what is tor and what a tor-powered vpn would be - but not sure if we should explain tor-powered vpn 14:21:49 hmmmm 14:22:27 nah: yeah, I hear you – let me have a think 14:22:45 I def think we can roll Q12 and 13 together if we get the wording right 14:23:06 Q4 - can we expand? when do you use a vpn? why? how [do you think] it protects you? 14:23:14 ohhh i see 14:23:23 (about q12 and q13) 14:23:47 ^ agree with antonela, we touch on the contexts in Q3 14:23:53 maybe they need split out and expanded on 14:24:05 (the when/why questions I mean) 14:24:18 i think we already have this questions, antonela, if the person says "yes" 14:25:42 oh sorry, so we do 14:26:07 agreed that why should go earlier 14:26:18 * nah looking at the pad 14:26:27 maybe make it the first question in the branch? 14:26:41 branch/thread 14:27:37 like we have "do you use tor -> how often -> why" 14:27:58 we can do the same for vpn 14:28:05 yep 14:28:12 and then, do you use both together? 14:28:22 yeah that makes sense! 14:28:50 and you can go deeper > how? "tor over vpn", "vpn over tor", "im not sure, it just work" 14:29:13 maybe it is getting to granular and long, not sure 14:30:02 *too 14:30:52 yep, if the user doesn't use vpn, they will skip all these questions, jump to the remain demographics (gender, country) and then the second screen 14:31:49 we will focus on android atm 14:32:15 (q13) 14:32:21 sounds good 14:32:34 i made some comments regarding the options for mobile browsers 14:32:40 yeah, I'm not sure 14:32:48 earlier questions make the survey seem more device-agnostic 14:32:57 like where we ask on what devices they use a VPN 14:33:15 so it would follow we need to give a list of browsers available on both mobile and desktop 14:33:30 I guess we need to make a final decision if this survey is mobile-specific or not 14:33:51 if so, we'll need to make the wording ultra clear so we don't get desktop VPN users responding 14:34:02 unless the intention behind the platform question is to filter these out? 14:34:17 yes, it is 14:34:22 gotcha 14:34:39 however, if we have vpn users for both mobile and other devices 14:34:46 filtering will be hard anyway 14:35:19 unless we split the browser questions (in your mobile, which browser / in your computer...) 14:37:08 do we need to cover OS too? 14:38:20 (as in ask participants what OS they're using?) 14:38:31 not sure 14:38:50 if we have users from lineageOS, calyxOS... 14:39:12 but we should ask the developers if that's important 14:40:19 what do you mean sorry (re: the devs question)? 14:40:56 if it is important to know which OS users use 14:41:26 (i'm adding this points to the top of the vpn pad) 14:41:34 point* 14:41:40 so i'll check later 14:41:42 oh sorry, you mean ask the tor devs! 14:41:48 I'm following now 14:41:52 yes! haha sorry 14:41:59 yes, good question 14:42:22 if this is a discovery kind of survey, i'd avoid making device/platform specific questions BUT i bet we want some data to learn which OS prioritize in terms of support for example 14:42:52 yep, that's fair – I was moreso thinking incase we want to filter out iOS users 14:43:00 at the same time, i know this project focus on android mobile at the moment 14:43:09 right, so, not sure, its a good conversation to have with devs for sure 14:43:28 yeah, okay let's have a think about this – it's the last big Q remaining 14:43:40 I have a sync with isa later and I can get her opinion on it too 14:43:46 (although I think I know what she'll say ^^) 14:44:25 haha 14:44:54 :) 14:45:05 thanks so much for your help antonela! and for putting this together nah! it's looking fantastic 14:45:32 thanks, antonela and duncan :) 14:46:02 yes, great work nah, happy to run the first test round 14:46:32 On to the next and last item in the agenda – the user feedback report! 14:46:40 https://lists.torproject.org/pipermail/tor-project/2021-September/003177.html 14:47:25 I wonder if kulsoom_z[m] is around to chat us through it? 14:48:31 I notice there are still some reports of confusion over the V2 deprecation, we've obviously removed the about:tor banner which suggests they're either from users who haven't updated their browser yet 14:48:52 or are about the V2 deprecation error itself 14:49:22 (for reference, just 9 tickets – so not a huge amount) 14:50:39 did anyone else notice anything unusual in this month's report? 14:51:28 are we tracking about:connect issues in a central place? i owe sharing some notes there but im sure it improved a lot from last time 14:52:10 nope. but i should do it 14:53:05 I have an offline list of applications tickets I'm using to track design/UX fixes – but a master list would be good 14:53:23 (for the purpose of linking back to the report when I'm proposing a change) 14:53:39 right 14:53:47 e.g. here: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/29590#note_2749371 14:55:12 I also need to write a centralized spec doc for the censorship circumvention feature, so having a full issue tracker for about:torconnect would be extra useful 14:55:19 okay I've put that on my/our list! 14:56:05 we could also add a new GL label and track them on a kanban 14:56:22 (right now they just get added to user-feedback) 14:56:49 ^that would be good 14:56:53 yep 14:57:22 "torconnect 2.0" maybe 14:57:38 or "torconnect feedback" 14:57:45 okay leave that with me! 14:57:58 we're two minutes until the hour, anything else or are we good? 14:58:23 good 14:58:29 :) 14:58:57 thanks for all your hard work nah! 14:59:01 and thanks for your help today antonela! 14:59:02 <3 14:59:18 pressing the button in 3, 2, 1... 14:59:25 #endmeeting