17:59:08 #startmeeting tor browser 17:59:08 Meeting started Tue Jun 26 17:59:08 2018 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:14 hi everyone! 17:59:15 hi everyone 17:59:18 ha 17:59:19 hi! 17:59:36 o/ 17:59:38 so, a somehat unusual meeting time 17:59:41 hi everyone 17:59:46 Hi /types furiously 17:59:46 let's see who is here today 17:59:48 !! 17:59:59 https://storm.torproject.org/shared/tHoN4Ii7rLSjPE0OP4gydX4cMGadsXmRQNc-6lwru0N is the pad as usual 18:00:10 please add your items if you have not done so yet 18:00:50 hi! 18:02:03 hello 18:03:49 pospeselr: do you plan to have a look at possible fixups for #26309 as well this week? 18:03:54 err 18:03:57 yeah i have a patch for that 18:03:57 #26039 18:04:05 okay, cool 18:04:21 just getting rid of extensions-overrides altogether and dumping to a temp file to get squashed into 000-tor-browser.js 18:04:32 kk 18:04:46 webextension version of noscript and httpseverywhere are completely different from the old ones so those options don't apply at all (even if webextensiosn could read prefs) 18:05:03 yeah, that's what i thought 18:05:40 boklm: i am fine if you want to look at #26323 but we need to have the test environments set up first 18:05:51 i don't want to fly blind again as we did last time 18:06:11 ok 18:06:14 and i plan to look into #26475, so no need to pick that up 18:06:20 ok 18:06:27 oh, yes, please the binutils bugs 18:06:48 i have some hope that we get that sorted out quickly with the help of the original patch author 18:07:26 it might help with mozilla's bug 1470772 as well in case this is fixed in newer binutils 18:09:23 tjr: i put sukhe on the moizlla bug as he asked to for something to work on 18:09:49 if you really want to look at it by yourself let me know and i'll find something else for him to do 18:10:01 that said, you are up with your item 18:10:25 I'm happy to have him look at it. My plan was to look at the crash in windbg and see if it was fixable/sensible 18:10:46 I bet he's going to go at it a different way, so maybe we can both work on it and see who comes up with more information :) 18:10:59 fine with me, please coordinate? 18:11:13 kk 18:11:48 My windows x86 question is for you - it looked like the 8.0a9 builds had win32 builds? Are we keeping Windows x86 around? 18:12:09 for now i think so 18:12:25 does mozilla have data about the percentage for 32bit only windows? 18:12:44 in general we support what mozilla supports 18:13:04 at least that's the policy we have for now 18:14:03 apparently 18% of people are on 32 bit but that isn't windows only. https://hardware.metrics.mozilla.com/ 18:14:11 * mcs was not seeing any IRC traffic for a little while 18:14:40 oh wait "this metric likely undercounts non-Windows OSs, seeing as it relies on the environment.system.isWow64" 18:15:01 so yea i guess x86 windows is important 18:15:21 didn't think anything newer than windoes 8 supported x86 though.... 18:15:38 Okay; anyway, I'll keep that in mind when we're adding jobs 18:15:43 * tjr is done 18:16:11 thanks 18:16:46 hrm, no arthur 18:17:53 mcs: if you could make a first estimation on the severity of the issues you found during review that would help as well 18:18:17 (it seems arthur was lost in the netslit) 18:18:23 GeKo: Makes sense. We will try. 18:18:23 we should get the patching going soon i guess (apart from fixing all the breakage we get reported) 18:18:24 yes 18:19:24 sysrqb: https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#AddingNewDefaultBridges 18:19:50 i asked dcf to write this up and he did so during the montreal meeting 18:19:58 that's all we have right now 18:20:42 GeKo: Oh, great, thanks 18:20:43 sysrqb: re the rustconf thing, sounds good to me 18:21:16 i wonder if pospeselr will be interested, too 18:21:24 i am not sure yet what we need from the browser side apart from the build related issues 18:21:26 but he was lost, too 18:21:30 * arthuredelstein is back from a weird irc zombie state -- may have missed messages 18:21:39 wb! 18:22:01 sysrqb: but there might defnitely be opportunities in going to it 18:22:14 :) 18:22:29 arthuredelstein: i was only about to ask you about the state of your notes on the pad :) 18:22:37 i know the network team has learned a lot from their interactions with rust people 18:22:52 yeah 18:22:55 and having more rust knowldge on this team may be helpful 18:23:12 for build and patching 18:23:20 as more things are rewritten in rust 18:23:29 that's for sure although this is somewhat orthogonal to going to the conference i guess 18:23:39 yes 18:23:45 anyways, yes, please go if you want to 18:23:54 okay, thanks 18:24:22 GeKo: My notes are more or less stable I think :) Any questions about them? 18:24:39 Hoping my notes have synced properly 18:28:13 arthuredelstein: I added a response r.e. your question about “headless” Tor Launcher. 18:28:32 got it. thank you! 18:29:40 mcs: I suspect the two issues are related, but not sure 18:29:59 You may be correct. There are definitely some weird things happening. 18:32:09 netsplit == no fun 18:34:09 arthuredelstein: regarding #26506, what version of NoScript are you testing with? shipping version? 18:36:02 brade: initially the shipping version, but then I also testing with earlier versions and found that the problem went away for 10.1.5.8rc1 and earlier 18:36:31 so the diff posted in comment:5 might offer a clue 18:36:42 arthuredelstein: I noticed several things in that diff that looked like typos to me 18:37:31 yikes. I wonder if they are still present in the current version 18:37:52 I haven’t had a chance to check 18:38:16 plus, I’m not really familiar with the code so maybe they aren’t “typos” 18:38:49 at some point we should do some kind of audit for the new NoScript. Do we have a ticket for this already? 18:38:59 not to my knowledge 18:39:27 unfortunately there is a dearth of comments and no up-to-date git mirror 18:42:39 did we lose GeKo? 18:42:52 yes 18:43:09 I opened #26513 as a reminder 18:43:34 thanks! 18:45:16 Looks like we don't have boklm either so it's hard to talk about the alpha release 18:47:54 funky oftc 18:47:57 The Windows alpha release seems particularly weak; not sure why it’s just Windows 18:48:23 pospeselr: I mentioned a bunch of UI bugs in the tor-qa thread; but I think they are all dupes of issues you have on your radar already 18:48:48 related to the onion icon? 18:48:53 brade: By “weak” you mean it is not very good? Many issues? 18:49:27 pospeselr: And cert errors 18:49:31 yes, there are many issues and many seem to be windows-only 18:49:43 interesting 18:50:36 tjr: The extra "New Prviate Window" item in the hamburger menu you mentioned is hidden by my proposed patch in #26321. 18:50:57 neat! 18:53:49 I have made contact with GeKo over on mozilla's irc network 18:53:59 he can't reconnected to oftc 18:54:00 he said he emailed tbb-dev 18:54:44 he did 18:54:46 as did boklm 18:54:58 no europeans allowed on oftc for the time being it would seem :p 18:55:41 " so, feel free to meet without me or just close the meeting and wait for me to shut down the tor-meeting logging :)" 18:56:12 do we have anything more we should discuss at the moment? 18:56:22 when will we meet next? 18:56:23 yeah, i think the person who starts meet-bot must stop it, too 18:56:42 Regarding the alpha release, I think it makes sense for everyone to work on tickets and boklm and GeKo can decide whether to respin to pick up fixes or ship as-is. 18:56:55 i'm guessing we'll need to discuss the next meeting over mail 18:57:03 or another quick team irc meeting 18:57:55 actually it is “meetings” on storm… I assume next week is a US holiday so GeKo is asking about it and the following week GeKo is out 18:58:10 Quick poll: anyone here who can't meet on July 2 (next Monday)? 18:58:23 nope 18:58:25 Since the US holiday is on Wednesday, Monday should work (maybe) 18:58:44 I mean i can meet 18:59:01 i can 18:59:04 Yeah, I shouldn't have asked the question in the negative :) 18:59:07 My plans for next week are not firm but I will try to be available for Monay’s meeting 18:59:27 Monday’s 18:59:58 so let’s plan to meet and then lock down subsequent dates at that meeting 19:00:09 OK! At least July 2 sounds plausible and we can see what GeKo and boklm can do 19:00:25 or discuss via email if GeKo wants to make sure plans are in place soon for when he is out 19:00:54 yeah, sounds good 19:01:58 OK, anything else before we wrap? 19:01:59 arthuredelstein: baf? 19:02:15 yes baf 19:02:22 let's see how this thing works: *baf* 19:02:40 :) 19:02:45 *baf* *baf* *baf* 19:02:49 highly satisfying 19:03:09 Just be careful what you say; the bot is still listening! 19:03:18 or is it? 19:03:20 #endmeeting 19:03:23 .... 19:03:29 welp 19:03:30 you don't have the power 19:03:43 *cough* 19:04:14 * sysrqb slowing walks away... 20:28:44 * sysrqb reminds GeKo to *baf* the meeting 20:55:55 #endmeeting