14:59:16 #startmeeting Tor Browser Weekly Meeting 2022-09-26 14:59:16 Meeting started Mon Sep 26 14:59:16 2022 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:21 hello hello 14:59:25 hello 14:59:27 pad per usual: https://pad.riseup.net/p/tor-tbb-keep 14:59:50 Hi! 14:59:56 o/ 14:59:58 hello 15:00:04 hi 15:05:16 ok it looks like pad activity has settled down 15:05:58 no major announcements or discussion points from me this week 15:06:13 I have a bolded item 15:06:43 build tags for alpha should be happening today; did a test alpha build and all went fine so should be smooth sailing there 15:06:53 richard: no plz 15:06:59 and stable tags hopefully by the end of the week pending YEC stuffs 15:07:06 I think that the font issue is very important 15:07:20 I think that it should be a blocker for the alpha 15:07:27 oh really? 15:07:28 We have a few workarounds 15:08:02 Yes. As I said last week, all non-Latin script users are screwed in Ubuntu/Fedora at the moment with 12.0a2 15:08:44 So, even though the Bugzilla ticket is still at the moment, we should use one of the workarounds 15:09:44 alright, we'll have alpha tags after the fonts are fixed :D 15:09:59 woops, HELLO 15:10:07 Currently the issue is assigned to dan_b, but we can reassign if needed 15:10:35 PieroV: can you point me to w/e relevant info/patch/pref changes needed to fix? 15:10:53 tor-browser#41163 15:11:01 i have an MR up for it at tor-browser!365 with one of the work arounds 15:11:22 ok then I'll test/review/merge it after this 15:11:40 Thanks! 15:11:52 with notes from PieroV on why the current state of the MR may not be optimal 15:12:08 but then I switchtedto YEC22 work friday 15:12:53 yes, the TL; DR is that the fix is an okay workaround, but it needs to be in ifdef XP_LINUX in a preference file, rather than StaticPrefs.yaml 15:13:16 ok I can move that pretty quickly and update it today 15:13:25 dan_b: wfm 15:14:00 henry-x: iirc we had to solve this same font issue in last year's YEC, I'll take a peak at it after the meeting and get back to you 15:14:42 (beyond the font embedded in the SVG last year) 15:15:24 ok PieroV: what's the good news on the tor-launcher migration? 15:15:43 I think that either today or tomorrow I'm moving to the last file 15:15:56 Yeah, you embedded it as `src: url('data:application/octet-stream;base64,` last year, but the chat on the bug between you and PieroV implies it could be done some other way to avoid the very long stream 15:16:19 So, I think we should move the localization soon. As a workaround we could move it to torbutton 15:17:14 I'm still catching up, but are there two fonts in the artwork? 15:17:27 donuts: yeah 15:17:32 donuts: yes, or 3 if you count the bold 15:17:36 PieroV do you know why loading a font from `resource:` is not allowed in "about:tor", but loading images from `resource:` is ok? 15:17:52 henry-x: nope. But you can check it on about:manual 15:18:04 pierov: can we do variable in TB (if that's smaller than two weights)? 15:18:29 donuts: I've thought about that, but it depends on the OS, I think 15:18:33 Rather than on Firefox 15:18:39 space mono is obvs very important to the look and feel of the campaign 15:19:02 the sans-serif is less so, if it's resulting in many kbs 15:19:29 anyway I'll catch up with the ticket and repeat the same there :) 15:19:44 henry-x: I think that a reason is that I've set chrome:// URLs in about:manual, but maybe I should have used resource:// 15:20:15 donuts: they aren't that big, ~100kB or ~130kB when zip compressed, iirc 15:20:32 pierov: cool, ty 15:20:33 I think it could be done, for a few releases 15:20:44 i suspect either way it's smaler than last year so we should probably not agonize abou tit 15:20:52 ha ok fair 15:21:01 LESSONS WERE LEARNED 15:21:09 lol 15:21:54 re localization migration 15:22:17 richard how did you create the base64 octet stream last year? 15:22:19 * emmapeel raises ear 15:22:38 henry-x: most likely a one-off script 15:23:08 oh, now that I think of it 15:23:12 I've tested the sizes of ttf 15:23:16 We could use woff2 15:23:24 And the size would diminish 15:25:05 I'm somewhat hesitant doing that w/o understanding the differneces between woff2 and ttf encoding (eg can the conversion occur losslessly?) 15:25:26 richard: woff2 are optimized for the web 15:25:33 And I think that it can be lossless 15:25:49 I have both sfnt2woff and woff2sfnt 15:26:00 (but maybe this is for woff 1?) 15:26:19 you ocan always pop them into fontforge :p 15:26:51 The sans is more than half! 15:26:58 Err, less than half 15:27:05 if it works it works, just make sure the glyphs still look right :p 15:27:11 but anywya 15:27:28 regarding localization migration: 15:28:01 (yes, it's lossless, just tried) 15:28:06 it seems like a reasonable stop-gap 15:29:00 maybe it will be easiser to migrate ultimately to fluent if we only have 1 system to migrate from 15:29:24 what's your reasoning in moving the strings from tor-launcher -> torbutton rather then doing the fluent migration all at once? 15:29:37 let's us purge tor-launcher sooner? 15:30:00 Yes 15:30:14 So that we can purge one for starters 15:30:27 And if things with torbutton go long, we can do that for 12.5 15:31:09 yeah ok that makes sense 15:31:16 And to parallelize works more 15:31:35 My plan for the fluent migration was to start with New Identity and Security Level, which are small enough 15:31:39 (or even with one of them) 15:31:49 Since we have to test the whole new pipeline 15:31:51 can we make that migration a secondary MR from the tor-launcher functionality migration MR? 15:32:27 Yes. I've deleted a few strings in the current MR 15:32:36 I can cherry pick on another branch, in case 15:32:44 and remove them from the current MR 15:32:51 ok perfect 15:33:21 But we will need to change also the script to import translations in torbutton 15:33:51 yes 15:35:26 dan_b: can you prioritize the alpha work (go upgrade patch, font fix) over the YEC changes this week? 15:35:53 i'll get the font fix out today 15:36:07 the go thing I have no idea what that's going to entail but I can start looking 15:36:30 my fenix YEC22 isn't too far along, i only have hte YEC21 patch applied and showing and partially date gated 15:36:53 well small steps 15:37:02 but if that's cool then yeah I can start digging into whats up with go 15:37:19 richard: we won't be able to update obfs4proxy anyway 15:37:23 well unless the go thing is a quick fix then it can wait until next week 15:37:54 ah ok then go can wait until after YEC, ignore that bit 15:37:55 but updating go will be a good thing anyway :) 15:37:59 cool 15:38:18 font MR > YEC22 > go :) 15:38:26 yep exactly 15:38:39 anything from anyone else? 15:38:55 only organizational 15:38:59 I will be afk on Oct 5 15:39:03 then nothing else from me 15:39:37 I'm getting serious about native UI for per-tab notifications, adding a WebExtensions API 15:40:19 donuts just asked for a rebranding of the notification bar (indeed it looks ugly with that foxy orange gradient) and I've just verified it's doeable as well 15:40:34 🙌 15:40:36 fantastic! 15:40:42 donuts: you should invite people to figma 15:40:49 So that they can see the inspector 15:40:59 (BTW we already show that ugly bar for other stuff, so it would be a win anyway) 15:41:22 a bit of cool stuff on my end. 15:41:26 pierov: oh actually I think that file's open, so anyone can inspect it with an account – but will invite everyone to the whole UX account anyway 15:41:28 donuts, the current gradient is linear-gradient(0, #9059ff 0%, #ff4aa2 52.08%, #ffbd4f 100%); Just tell me the colors you prefer 15:41:36 ma1: my thoughts exactly :D 15:41:36 will do! 15:41:42 thanks for the reference 15:41:42 I'll be afk this afternoon, and then i'm also someewhat afk next Monday and all of next Wednesday (3rd and 5th) 15:42:38 PieroV I created a figma account by myself without an invite and I could see the inspector for YEC2022 15:42:52 Electrum-NMC is now about 2-2.5x lower latency for resolving names (cut down to 1 round trip, very helpful over Tor), and it also verifies scriptSigs on the name transactions it fetches (sort of like a full node, but as scalable as a usual SPV node) 15:43:05 henry-x: yeah it's unlocked, but if I invite you to THE TEAM i think it'll make it easier to find these files in future 15:43:19 Jeremy_Rand_36C3[m]: cool, congrats! 15:43:19 or it'll make no difference at all 15:43:19 Electrum-NMC now also supports Tor environment variables (good for system Tor / Whonix / Tails / etc) as well as SOCKS over Unix sockets 15:43:24 _shurgs_ 15:43:58 Jeremy: neat 15:44:12 ironically richard never accepted their ux team invite :< 15:44:30 ah well 15:44:41 i was probably distracted by something else shiny 15:45:05 Jeremy_Rand_36C3[m]: when I'll finish with tor-launcher I'll probably go after torbutton 15:45:19 And we'll need to revisit your patches 15:45:52 PieroV: ah cool. Yeah we should discuss that sometime -- I think part of the patch it redundant since it duplicates a UI element that the SecureDrop stuff has 15:46:03 (I wonder if torbutton is also needed to merge the GeckoView-TBB desktop branches) 15:46:11 So yes we should consider properly refactoring that stuff 15:46:24 invites away! 15:46:52 donuts: got it! thanks 15:46:56 I also noticed henry isn't on the Applications team meeting invite 15:46:59 will see if I can fix 15:47:01 PieroV: please CC Arthur and me in any tickets about that 15:47:32 Jeremy_Rand_36C3[m]: I hope to remember to, please remind me if I start talking about torbutton stuff without doing so 15:47:43 PieroV: ok, no worries 15:47:48 (I don't know if we have an issue for it, yet) 15:49:39 tor-browser#41286 15:51:12 ok, anything else before I endmeeting? 15:51:21 * Jeremy_Rand_36C3[m] has nothing more 15:51:26 * PieroV neither 15:51:31 nope 15:51:34 * boklm neither 15:51:41 nope 15:51:45 ok then have a good week everyone 15:51:52 thanks! 15:51:55 Thanks! 15:51:59 #endmeeting