18:00:48 #startmeeting tor-browser 18:00:48 Meeting started Mon Jun 4 18:00:48 2018 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:54 hi all! 18:01:10 hi! 18:01:21 the meeting pad is at https://storm.torproject.org/shared/tHoN4Ii7rLSjPE0OP4gydX4cMGadsXmRQNc-6lwru0N (as usual) 18:01:54 hi! 18:01:58 hello 18:02:01 hi 18:03:50 hello! 18:04:03 mcs: brade: i think i finish the mar testing this week and then we can move forward #26050 18:04:07 boklm: ^ 18:04:12 Guest4166: hi! 18:04:18 hi everyone! typing is very slow for me on storm today... 18:04:30 ahem 18:04:34 just me 18:04:39 ah, it's been you :) 18:04:41 GeKo: OK; sounds good. 18:04:50 Pidgin likes to un authenticate me at random it seems 18:05:22 sukhe: does the answer boklm gave help? 18:06:25 sysrqb: do we have a write-up somewhere where we are wrt the orfox bug? 18:06:35 i guess this is not supposed to be sekrit? 18:06:37 GeKo: ah yes. that makes sense 18:06:46 unmarking bold. thanks boklm 18:06:53 sukhe: i'll give you an updated patch after the meeting 18:07:15 the windows rust patch did not land before i had my stuff ready for review 18:07:23 GeKo: that's fine. I had actually rebased it on 1.26.0 and there was no difference. it was 1.26.1 18:07:28 :) 18:07:35 GeKo: unfortunately, no. i don't know what conversations igt0 had with Mozilla 18:07:56 but I'll ping igt0 and we'll post an update so everyone's on the same page with this issue 18:08:10 do we have a ticket for this issue actually? 18:08:36 i believe igt0 only opened the buzilla ticket 18:08:46 nothing on trac 18:08:50 i wonder if that would be a good thing or not 18:08:57 probably yes 18:09:14 i can do that after the meeting 18:09:33 i am usually a fan of having especially such tricky issues documented in trac 18:09:45 under the assumption that a bunch of cypherpunk brains might help 18:09:52 heh, true, true 18:10:04 especially this bug seems tricky 18:10:10 or someone is getting bored at the weekend and tries to track stuff down 18:10:18 yeah 18:11:00 okay, so, if igor and you could do that as part of tracking this problem further down that would rock 18:11:28 sure thing, will do 18:11:42 thanks 18:12:22 pospeselr: okay, the loclization issue 18:13:03 yes 18:13:17 pospeselr: Would it be possible to place the onion text in a separate xul element so you don't have to mess with the https strings at all? 18:13:30 i think arthur back in #20244 solved it by using an overlay with a separate xul element 18:13:35 yes 18:13:44 (what he just said) 18:15:01 So I'm not exactly sure how XUL works in relation to the 'Page Info' pane 18:15:24 looking at your patches, it seems like your just modifying the firefox settings XML directly 18:16:13 whereas the 'Page Info' window seems to be generated programmatically and doesn't *seem* to have any associated XML anywhere 18:16:35 though I could be off base here, I'm not terribly familiar with all FF UI machinations 18:16:35 pospeselr: so is this text you want to display in the Page Info "Security" tab? 18:16:39 yes exactly 18:16:57 each of those strings are pulled from the localization strings file 18:17:09 Is it the "technical details" section? 18:17:18 pippki.properties 18:17:19 yeah 18:18:13 Seems to be this file: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/pageinfo/pageInfo.xul 18:18:14 so the patch currently swaps out the 1st line there with a different printf-style formatted string 18:19:47 yeah ok, and those fields are set /browser/base/content/pageinfo/security.js 18:20:16 So I guess one possibility would be to create an extra element via XUL overlay. 18:20:29 It would be a child of 18:21:54 so we'd need to hide the "security-technical-longform1" description and replace it with our own 18:21:54 We can discuss after the meeting more though if that would be useful 18:22:01 yeah ok taht would be great 18:22:16 sounds good 18:23:57 okay, anything else before moving to the disussion part? 18:25:06 it seems "no" 18:25:11 so, discussion time 18:25:27 do we want to use "status: " as well? 18:25:49 I have seen people use it but I am not sure what it is? 18:25:58 yeah. also, had nick talked about this in the vegas team meetings? 18:26:05 as in, has this been useful for them? 18:26:22 no, not in the vegas team meetings 18:26:26 it seems nice for tracking progress during the week 18:26:29 okay 18:26:46 i think it has been part of the plan to keep everyone better informed what team members are working on 18:27:02 yes, thats my understanding, too 18:27:12 i'm not sure if that is a good fit for this team, though 18:27:17 is it just saying "/me status: " or is there more? :) 18:27:25 that seems like it 18:27:28 and see it earlier if folks get distracted/don't cope with a problem 18:27:42 sukhe: that's it, yes 18:27:49 the rule is at least once a day 18:27:57 * antonela likes the idea :) 18:28:24 should it be on -internal or -dev? 18:28:46 the network team uses tor-dev 18:28:52 yep 18:29:02 i think there's a bot that catches all status udates 18:29:11 yes 18:29:12 (i don't know if/where it's logged, though) 18:29:39 so, i don't have a strong opinion on that 18:29:53 that could be useful 18:29:56 +1 for the "/me status: " if more people want to do it :) 18:30:01 but if we use that, too, we should ask the network team folks first to not mess with their bot 18:30:04 Does the network team use the data for other purposes, e.g., a monthly status report? Or just to keep each other informed daiily? 18:30:08 maybe we can start on a voluntary basis and see if it catches on? 18:30:30 mcs: i am not aware of other purposes 18:30:34 Yes, I would not want to mess up their data collector. 18:30:35 GeKo: yes, agreed - can you bring this up at the next vegas meeting? 18:30:35 OK 18:30:36 * GeKo summons an isabela 18:30:39 GeKo: I believe that the bot/highlight/filter/whatnot that the network team has, by default, only does so for those on the network team 18:30:47 ah, or isa :) 18:30:47 sysrqb: sure 18:31:30 okay, either way. we'll have this sorted out by next week and can then start from that 18:31:37 yeah 18:31:44 sounds good, thanks 18:31:54 so, the website 18:31:55 (fwiw, I've been doing the "/me status: " for a month and no one has told me not to) 18:32:07 yeah 18:32:43 sysrqb: it's been worked on but i don't know any eta 18:33:11 it seems this irssi script can use the status updates: https://github.com/ahf/onion_status 18:33:14 * GeKo tries again to summon isabela 18:33:19 okay, i'm curious about its progress, in general, but also i started thinking about having a special TBA "Learn More" landing page 18:33:29 but this isn't something we need for the first or second alpha 18:33:35 just a thought 18:33:52 yes, that's a good idea and we should have such a page 18:34:26 boklm: ah, neat, thanks 18:34:35 GeKo: yeah, i'll open a ticket so we don't forget 18:34:45 thx 18:36:21 i guess a fraction of the tor browser team will be at the all hands meeting next week 18:36:31 and not at this meeting 18:36:47 true 18:37:07 it would be nice if the status updates would be available, though 18:37:28 so all the other folks can see what was worked on and get on the same page 18:37:39 will do 18:37:51 noted 18:37:53 thanks. 18:38:03 so, that's all i guess we have for today? 18:38:10 or is there anything else? 18:39:15 okay, thanks then, everyone! *baf* 18:39:18 #endmeeting