From e470f7aba320a9bc014c79f4a66923d0733cae3e Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Thu, 19 Nov 2026 15:44:08 +0600 Subject: [PATCH] [2026-11-19] eagle: work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.json work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.md --- .../transcript.json | 1245 +++++++++++++++++ .../transcript.md | 249 ++++ work/zoom-transcripts/index.json | 12 +- work/zoom-transcripts/sync-status.json | 2 +- .../transcript.json | 560 ++++++++ .../transcript.md | 112 ++ .../transcript.json | 520 +++++++ .../transcript.md | 104 ++ 8 files changed, 2797 insertions(+), 7 deletions(-) diff --git a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json index 34670af0..5cb1a4fe 100644 --- a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json +++ b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.json @@ -23,6 +23,1251 @@ "time": "16:09:31", "speaker": "Alex Martemyanov", "text": "Okay. So for the past week, uh, what was there?" + }, + { + "time": "16:09:38", + "speaker": "Dominik Kapusta", + "text": "To priority." + }, + { + "time": "16:09:40", + "speaker": "Alex Martemyanov", + "text": "Yes, uh, there is, uh, current priorities, uh…" + }, + { + "time": "16:09:41", + "speaker": "Dominik Kapusta", + "text": "Jest." + }, + { + "time": "16:09:45", + "speaker": "Alex Martemyanov", + "text": "to be postmortemed on Thursday, since today's slot is taken. Which is a good thing, I guess, not to go to the late night. There is still some. some discussion going on the extra extension lifecycle matrix to be added as a follow-up to analyze some NGS code. Whether we receive this in it or not. Is it almost before? Probably it's not before, but we need to understand. Exactly where. Anyways, I'm gonna… comment to the project later today. Postmortem is planned for, uh, Thursday slots. And, uh, there was, uh, the metric… I was discussing with Bartek a couple of weeks ago, and I just pushed it forward today, and uh… I've got a scalpel of four. Couple of feature flags removed. Couple of tasks still in this step. One crush, and let… Hopefully to be reviewed today and. And the neutral priority, yes. So I started kinda looking into it. Again, it doesn't seem like something… Precise. To be done, some measurements. Okay, hopefully it won't take too long, just some time-boxed experiments, I guess, and some defined experiments like splitting the CSAs into… Zero parts. Mm-hmm. Yeah, and really hoping the next top priority won't be of… these claims. If you can just… Speak up to… somebody in the objectives that, yeah, I'm seeking for something closer to the browser. Probably… If it can work, because, uh, yeah, the last top priority, I can't say that it was. Great, and I feel great about it. Hmmm." + }, + { + "time": "16:12:25", + "speaker": "Dominik Kapusta", + "text": "Feel great about what exactly? Sorry." + }, + { + "time": "16:12:27", + "speaker": "Alex Martemyanov", + "text": "Yeah, I'm not feeling great about the last top priority I got, the CPM." + }, + { + "time": "16:12:31", + "speaker": "Dominik Kapusta", + "text": "You are not feeling good. Yeah." + }, + { + "time": "16:12:33", + "speaker": "Alex Martemyanov", + "text": "Yeah, I'm really tired of it, and uh… Of life." + }, + { + "time": "16:12:40", + "speaker": "Dominik Kapusta", + "text": "Yeah, I can tell. I can tell, of course. It's not an obvious win, right? This project, which sucks." + }, + { + "time": "16:12:50", + "speaker": "Alex Martemyanov", + "text": "Yeah. Yeah." + }, + { + "time": "16:12:53", + "speaker": "Dominik Kapusta", + "text": "But the… The most important question is, or maybe you have the answer already, or maybe someone gave that answer to you, whether that work you spent on it was… Uh, useful or not useful." + }, + { + "time": "16:13:13", + "speaker": "Alex Martemyanov", + "text": "So, so, I'm sure there's a lot." + }, + { + "time": "16:13:15", + "speaker": "Dominik Kapusta", + "text": "Yeah." + }, + { + "time": "16:13:15", + "speaker": "Alex Martemyanov", + "text": "So there were some bugs fixed, but the main metric." + }, + { + "time": "16:13:17", + "speaker": "Dominik Kapusta", + "text": "Um, okay." + }, + { + "time": "16:13:19", + "speaker": "Alex Martemyanov", + "text": "was not, it didn't reach the target basically defined to lower the numbers below one percent. At least on macOS, it's still above one percent." + }, + { + "time": "16:13:26", + "speaker": "Dominik Kapusta", + "text": "Oh, yeah. Mm-mm. So I guess one other question could be… Could this work be stopped earlier? Just for the post-mortem, because, of course, it happened already, so just for the future… Could you? Could someone, because it's not only you, it's plenty, like, many people in OE, right? being fine with this project running for… As long as it run. So, it looked like… There was hope all the time, or… yeah, we had…" + }, + { + "time": "16:14:07", + "speaker": "Alex Martemyanov", + "text": "Okay. I… for sure it could, uh, probably finish earlier, maybe couple of weeks." + }, + { + "time": "16:14:09", + "speaker": "Dominik Kapusta", + "text": "Some more ideas." + }, + { + "time": "16:14:16", + "speaker": "Alex Martemyanov", + "text": "But I don't know. Not in the fall. Since we got several iterations, like first naive approach, several bugs found, measured, two weeks to the next release, measured again. And, uh… Measurement showing the debugs did not affect, and another iteration of adding metrics. To find something else. So, uh… Of course we could just drop it at some point defining like. Like a trailer or partial. But, uh… Probably the research was kind of genuine, I guess. heading… several hypotheses tested, tried, measured, and. There is still some progress done over the bug fixes. Only maybe just not enough. to to call it successful." + }, + { + "time": "16:15:24", + "speaker": "Dominik Kapusta", + "text": "Right. Um… Is the postmortem happening today?" + }, + { + "time": "16:15:38", + "speaker": "Alex Martemyanov", + "text": "Meeting Thursday." + }, + { + "time": "16:15:39", + "speaker": "Dominik Kapusta", + "text": "Thursday." + }, + { + "time": "16:15:42", + "speaker": "Alex Martemyanov", + "text": "Yeah. Yes. Today, today is Thursday." + }, + { + "time": "16:15:48", + "speaker": "Dominik Kapusta", + "text": "Oh, yeah, yeah, yeah." + }, + { + "time": "16:15:48", + "speaker": "Alex Martemyanov", + "text": "During the slot system." + }, + { + "time": "16:15:51", + "speaker": "Dominik Kapusta", + "text": "Okay, sure, sure, sure. Cool. Yeah, but anyway, and you're moving to OB right now. Which… is great. I think, what do you think about this project?" + }, + { + "time": "16:16:10", + "speaker": "Alex Martemyanov", + "text": "Hmm. Okay. I hope. I'll be still alive when it ends. There will be New Year holidays close. So that should add on it. But, uh, yeah, I can't say that I'm happy about it." + }, + { + "time": "16:16:32", + "speaker": "Dominik Kapusta", + "text": "You're not happy about it." + }, + { + "time": "16:16:33", + "speaker": "Alex Martemyanov", + "text": "Not really." + }, + { + "time": "16:16:36", + "speaker": "Dominik Kapusta", + "text": "Yeah, from my perspective, it's just that it's… It's an important project." + }, + { + "time": "16:16:46", + "speaker": "Alex Martemyanov", + "text": "For sure, for sure, yeah." + }, + { + "time": "16:16:46", + "speaker": "Dominik Kapusta", + "text": "It's something that has many eyes on it right now. So. I'm glad you're working on it. It's not…" + }, + { + "time": "16:16:58", + "speaker": "Alex Martemyanov", + "text": "like… Unfortunately, my, uh…" + }, + { + "time": "16:16:59", + "speaker": "Dominik Kapusta", + "text": "It's…" + }, + { + "time": "16:17:02", + "speaker": "Alex Martemyanov", + "text": "Mm, feeling on it, and, uh, my motivation… is not driven by the importance of the project. Oh, okay." + }, + { + "time": "16:17:11", + "speaker": "Dominik Kapusta", + "text": "Yeah, and that's…" + }, + { + "time": "16:17:14", + "speaker": "Alex Martemyanov", + "text": "It's a pity, but… yeah." + }, + { + "time": "16:17:15", + "speaker": "Dominik Kapusta", + "text": "That's, I mean, that's fair, that's fair, of course. I'm just saying it for context. Because… I know it's hard. Because you have to… You have to endure that. But my hope is that in the long run you could. Even, perhaps… Stay in OB." + }, + { + "time": "16:17:45", + "speaker": "Alex Martemyanov", + "text": "And let's see… let's see how it goes. So, I…" + }, + { + "time": "16:17:47", + "speaker": "Dominik Kapusta", + "text": "I'm… I'm… No." + }, + { + "time": "16:17:51", + "speaker": "Alex Martemyanov", + "text": "Yeah, looking to the project, looking at the project, it's split to some parts, tasks for one or two days. Uh, so hopefully it won't take, uh, too much of… of my energy. to complete it." + }, + { + "time": "16:18:08", + "speaker": "Dominik Kapusta", + "text": "Oh. No." + }, + { + "time": "16:18:09", + "speaker": "Alex Martemyanov", + "text": "At least in the scope to define it right now. So, the kickoff goes to the next week, I guess?" + }, + { + "time": "16:18:23", + "speaker": "Dominik Kapusta", + "text": "Bring the apple slices back." + }, + { + "time": "16:18:28", + "speaker": "Alex Martemyanov", + "text": "Or… When the will be quickly happening." + }, + { + "time": "16:18:32", + "speaker": "Dominik Kapusta", + "text": "I don't know. I don't know." + }, + { + "time": "16:18:35", + "speaker": "Alex Martemyanov", + "text": "November 16 yesterday, on Monday, yeah, so…" + }, + { + "time": "16:18:38", + "speaker": "Dominik Kapusta", + "text": "Okay, Mondays. Mm-hmm." + }, + { + "time": "16:18:43", + "speaker": "Alex Martemyanov", + "text": "Okay, fine. I guess it naturally goes to the next Monday." + }, + { + "time": "16:18:56", + "speaker": "Dominik Kapusta", + "text": "at least… At least this is… kind of… work, where you can… Clearly see the result, at least in the numbers of… The size of, of, of… JavaScript bundle that's loaded into the binary, into the, well, WebView." + }, + { + "time": "16:19:20", + "speaker": "Alex Martemyanov", + "text": "Yeah, I can't say that I'm really good at JavaScript bundles. And all this stuff and how it should work, but yeah, having… probably having LLMs and some good judgment. We can just make a testing strategy and experiment on the memory footprint, and whether the testing website." + }, + { + "time": "16:19:36", + "speaker": "Dominik Kapusta", + "text": "Um… Bye." + }, + { + "time": "16:19:45", + "speaker": "Alex Martemyanov", + "text": "websites work, although I didn't find the exact websites when it fails. But we have the privacy test pages done by Bartosz, so… Hopefully it just works and should be pretty straightforward looking from." + }, + { + "time": "16:19:59", + "speaker": "Dominik Kapusta", + "text": "Yeah." + }, + { + "time": "16:20:04", + "speaker": "Alex Martemyanov", + "text": "from today. But we'll see how it goes." + }, + { + "time": "16:20:07", + "speaker": "Dominik Kapusta", + "text": "So they had some previous work on that, apparently. from… Uh, config, pruning, and uh… Passing config as a JSON string. What is that? Probably not using JSON serialization." + }, + { + "time": "16:20:29", + "speaker": "Alex Martemyanov", + "text": "I guess…" + }, + { + "time": "16:20:33", + "speaker": "Dominik Kapusta", + "text": "Anyway, they were doing some optimizations, and they had some…" + }, + { + "time": "16:20:33", + "speaker": "Alex Martemyanov", + "text": "And then…" + }, + { + "time": "16:20:40", + "speaker": "Dominik Kapusta", + "text": "Some test websites. Some websites to test it on, so that part should be…" + }, + { + "time": "16:20:43", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:20:48", + "speaker": "Dominik Kapusta", + "text": "resolved, but now I'm wondering… I'm essentially wondering why do they need a native engineer for that, because it sounds like JavaScript work. If they want to have separate bundles for iOS and macOS, they could do it in CSE, just like that, and then just… Rename the files in the native code." + }, + { + "time": "16:21:12", + "speaker": "Alex Martemyanov", + "text": "Well, who cares nowadays?" + }, + { + "time": "16:21:16", + "speaker": "Dominik Kapusta", + "text": "Yeah, of course, I mean, whatever. You could get a project advisor, speak to Dave, I guess, and get a project advisor from the front-end team, maybe? Maybe?" + }, + { + "time": "16:21:17", + "speaker": "Alex Martemyanov", + "text": "Okay. Mmhm." + }, + { + "time": "16:21:27", + "speaker": "Dominik Kapusta", + "text": "Someone who is experienced with CS." + }, + { + "time": "16:21:29", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "16:21:32", + "speaker": "Dominik Kapusta", + "text": "But also, an alternative is to have someone from the Apple team, and then LLM help, and just reach out, being able to reach out to a front-end person. If needed." + }, + { + "time": "16:21:45", + "speaker": "Alex Martemyanov", + "text": "Okay, I'll just ping Dave, probably, who could…" + }, + { + "time": "16:21:47", + "speaker": "Dominik Kapusta", + "text": "Yeah, I mean…" + }, + { + "time": "16:21:48", + "speaker": "Alex Martemyanov", + "text": "You suggest for… Advising the project." + }, + { + "time": "16:21:57", + "speaker": "Dominik Kapusta", + "text": "Yeah, that's a good idea. Dave would probably be able to." + }, + { + "time": "16:21:59", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm, I'll be back in. Luke." + }, + { + "time": "16:22:02", + "speaker": "Dominik Kapusta", + "text": "So just someone." + }, + { + "time": "16:22:03", + "speaker": "Alex Martemyanov", + "text": "Or is it Thanksgiving?" + }, + { + "time": "16:22:07", + "speaker": "Dominik Kapusta", + "text": "Not yet. Not yet." + }, + { + "time": "16:22:10", + "speaker": "Alex Martemyanov", + "text": "Where is it?" + }, + { + "time": "16:22:12", + "speaker": "Dominik Kapusta", + "text": "I think it's…" + }, + { + "time": "16:22:13", + "speaker": "Alex Martemyanov", + "text": "I'm leaving 2026." + }, + { + "time": "16:22:14", + "speaker": "Dominik Kapusta", + "text": "Beginning… or, yeah, last week of November or first week of December. 26." + }, + { + "time": "16:22:20", + "speaker": "Alex Martemyanov", + "text": "Uh, 26." + }, + { + "time": "16:22:22", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:22:23", + "speaker": "Alex Martemyanov", + "text": "Yeah, okay, it's Thursday. Mmhm." + }, + { + "time": "16:22:34", + "speaker": "Dominik Kapusta", + "text": "Split the iOS bundle from macOS. Make the isolated world mainframe only on Apple." + }, + { + "time": "16:22:50", + "speaker": "Alex Martemyanov", + "text": "Okay, I think Dave in the advisor's task." + }, + { + "time": "16:23:00", + "speaker": "Dominik Kapusta", + "text": "Okay. And drop the unused tracker." + }, + { + "time": "16:23:05", + "speaker": "Alex Martemyanov", + "text": "Yes." + }, + { + "time": "16:23:07", + "speaker": "Dominik Kapusta", + "text": "Try from Apple bundles. Okay. Nice. Sounds… Easy? I don't want to… I don't want to say easy, but… Uh…" + }, + { + "time": "16:23:24", + "speaker": "Alex Martemyanov", + "text": "Yeah, I hope so." + }, + { + "time": "16:23:25", + "speaker": "Dominik Kapusta", + "text": "You'll have a hack phase, and you'll figure out most of the things in the hack phase, hopefully." + }, + { + "time": "16:23:26", + "speaker": "Alex Martemyanov", + "text": "Because…" + }, + { + "time": "16:23:32", + "speaker": "Dominik Kapusta", + "text": "And also, if you're… if everything goes smoothly. You probably will have the entire project implemented during the hack phase. Who knows?" + }, + { + "time": "16:23:42", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:23:42", + "speaker": "Dominik Kapusta", + "text": "But if there are obstacles, then of course you'll have to… go through them during the project." + }, + { + "time": "16:23:48", + "speaker": "Alex Martemyanov", + "text": "Anyways, there's probably some triages. Reviews, front end team, back and forth and so on." + }, + { + "time": "16:23:53", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah, yeah. Totally. Maybe tech designs." + }, + { + "time": "16:23:57", + "speaker": "Alex Martemyanov", + "text": "Yeah. For sure." + }, + { + "time": "16:24:01", + "speaker": "Dominik Kapusta", + "text": "Sounds good. It's a bit unclear to me whether we should, um… Whether we should, uh… Have it as… or run… Involve more Apple people or front-end people here. But let's see. Let's see what Dave suggests, first of all." + }, + { + "time": "16:24:24", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:24:25", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. And, uh… When do you think you would start working on it? Thursday?" + }, + { + "time": "16:24:34", + "speaker": "Alex Martemyanov", + "text": "Uh, yes, uh, I think tomorrow." + }, + { + "time": "16:24:37", + "speaker": "Dominik Kapusta", + "text": "Tomorrow. Oh, that's cool. Nice." + }, + { + "time": "16:24:38", + "speaker": "Alex Martemyanov", + "text": "Wednesday. Should work, I guess, if nothing strikes." + }, + { + "time": "16:24:52", + "speaker": "Dominik Kapusta", + "text": "Nice, nice. Awesome." + }, + { + "time": "16:24:52", + "speaker": "Alex Martemyanov", + "text": "So there is still one follow up for the current project to analyze metrics. So, I just need… Max and Mihal to you. Uh, to check. Basically, it seems, uh… Hmm… It is in the middle, I guess. And should not be… Too big. So, the pull requests are basically ready, and we should just agree on what we measure, and… Added Grafana board, probably. So it's not… It's not too much." + }, + { + "time": "16:25:29", + "speaker": "Dominik Kapusta", + "text": "Yeah, uh, I see that this task is not added to technical designs?" + }, + { + "time": "16:25:29", + "speaker": "Alex Martemyanov", + "text": "Okay." + }, + { + "time": "16:25:35", + "speaker": "Dominik Kapusta", + "text": "I'm not sure if it's an omission or you meant it that way." + }, + { + "time": "16:25:35", + "speaker": "Alex Martemyanov", + "text": "Hmm… Oh, shit. You're right. per year. Review your remarks. Yeah." + }, + { + "time": "16:25:54", + "speaker": "Dominik Kapusta", + "text": "Awesome." + }, + { + "time": "16:25:56", + "speaker": "Alex Martemyanov", + "text": "Indeed, the extensions. Mm-hmm." + }, + { + "time": "16:26:21", + "speaker": "Dominik Kapusta", + "text": "So setting this project aside and setting your new top priority aside. What are the kinds of things you would like to work on right now?" + }, + { + "time": "16:26:32", + "speaker": "Alex Martemyanov", + "text": "I guess it's mostly, uh… Around my profile, and… I told, uh… Basically, the browser and… There is still some, uh… Things not finished, never finished, like bookmarks, history, and so on. Mm-hmm." + }, + { + "time": "16:26:57", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:26:59", + "speaker": "Alex Martemyanov", + "text": "So…" + }, + { + "time": "16:27:00", + "speaker": "Dominik Kapusta", + "text": "So, essentially, OL…" + }, + { + "time": "16:27:02", + "speaker": "Alex Martemyanov", + "text": "Extension to oil, yeah." + }, + { + "time": "16:27:03", + "speaker": "Dominik Kapusta", + "text": "Type of work. Uh… Got it. That would be great. But the problem with OL right now is that it's tier two, whatever that means. I mean, it means that it's not the greatest impact on the company top priority, but okay. And, uh…" + }, + { + "time": "16:27:25", + "speaker": "Alex Martemyanov", + "text": "I mean, there's alternative options if to consider if we have, for example, if we have, if we ever plan to deliver, like, a browser, Chromium-based browser to Linux, and I could switch to it, for example." + }, + { + "time": "16:27:32", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Mm-hmm. Yeah. Yeah." + }, + { + "time": "16:27:40", + "speaker": "Alex Martemyanov", + "text": "Yeah. Just just not to Windows." + }, + { + "time": "16:27:41", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah, yeah. Of course, yes, yes, yes. It's still a couple months ahead. So let's see, but… it seems to me that there will be push to having… to having a Chromium. Based browser on macOS. and that will be a big project. Of course, Mac OS, yes, and then we will have to migrate everything essentially the entire app to chromium, which is what windows is working on right now." + }, + { + "time": "16:28:06", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm. Marcus? Mmhm. Right, sir." + }, + { + "time": "16:28:17", + "speaker": "Dominik Kapusta", + "text": "And, uh… Yeah, and for that we will need many people. But let's see if it happens in the first place. On Windows, it's happening because Windows browser is shitty. As hell, it's just…" + }, + { + "time": "16:28:33", + "speaker": "Alex Martemyanov", + "text": "Mmhm." + }, + { + "time": "16:28:35", + "speaker": "Dominik Kapusta", + "text": "Crap. So, they are fixing it by… Forking Chromium. Then once they have Chromium, they could… a Chromium fork… We could work on… a Linux client, and macOS client as well. The added value of a Chromium fork… is that suddenly you get all the core browser features for free. Things like tab groups." + }, + { + "time": "16:29:04", + "speaker": "Alex Martemyanov", + "text": "Yeah, basically this was, that's what I was suggesting during my, when I was just hiring, I mean employed." + }, + { + "time": "16:29:05", + "speaker": "Dominik Kapusta", + "text": "Profiles." + }, + { + "time": "16:29:16", + "speaker": "Alex Martemyanov", + "text": "Oh. And, uh, yeah. I do understand since I did some research back then and I was basically proving that the browser needs to be Chromium based. But back then. It was… About policy mostly. But I guess it's a good news. And it's a bit pity that there is some work done that's being trashed." + }, + { + "time": "16:29:54", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah." + }, + { + "time": "16:29:55", + "speaker": "Alex Martemyanov", + "text": "But anyways." + }, + { + "time": "16:29:56", + "speaker": "Dominik Kapusta", + "text": "I mean, let's see, because I… That's something that we'll need to probably calculate, try to estimate, uh, but… in the long run, I think this sounds good, because otherwise, we have to… we would have to implement. Everything ourselves. And then there's a question of whether to go that way. or not, whether to invest time and people in. Implementing… Tab multi-select, things like that, right? Or…" + }, + { + "time": "16:30:31", + "speaker": "Alex Martemyanov", + "text": "Yeah, I'm…" + }, + { + "time": "16:30:35", + "speaker": "Dominik Kapusta", + "text": "For Chromium, spend… Half a year or more. And have it… just for free, in a sense. So… We'll get there, probably not earlier than spring next year. And, uh, in the mean… because what I'm… Observing right now is… It's looking harder and harder to get buy-in for implementing features. I wanted to add reader mode. and I run a Hackface for the reader mode, and, uh, well, it works. It just needs some more… Integration with whatever we have in the browser right now, like adding these two settings." + }, + { + "time": "16:31:26", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:31:30", + "speaker": "Dominik Kapusta", + "text": "And I wanted to push it through in the assessment, and I was like, okay, we can have a hack phase. Just 3 days! To use an agent and, like. embed. Reader mode settings in permissions mechanism, because it's… Similar. Uh, and they were like, okay, hug face maybe, and then someone said. that's fine, I understand it's a hack phase, it's just 3 days, but blah blah blah, there's something more important, and let's only do it if we run out of tasks for that. For the assessment, I mean, for the roadmap. So it's still waiting. And it was like it was a couple of days. it's not even… Any kind of a long project. Uh, so if it's going to look like this going forward for everything else, then… Are we even needed here for anything, or what? So, yeah. Let's see." + }, + { + "time": "16:32:36", + "speaker": "Alex Martemyanov", + "text": "Okay, anyways, I think it's a wide move to Chromium. There is, like, WebRTC, there is all the browser site issues solved, basically, for free, because I got my tax payments have to be done in Chrome, because they don't work in LambdaGo." + }, + { + "time": "16:32:37", + "speaker": "Dominik Kapusta", + "text": "Yeah, we… You know. Yeah, yeah, yeah. Yeah, yeah." + }, + { + "time": "16:32:54", + "speaker": "Alex Martemyanov", + "text": "And, yeah, a lot of things, basically." + }, + { + "time": "16:32:59", + "speaker": "Dominik Kapusta", + "text": "Um… Nothing will happen in that area this year, for sure. Probably not in January, but I'll keep monitoring it. The next assessment in OL is in January. shouldn't be… this shouldn't be a topic in January either. Because Windows is not shipped yet. But yeah, let's… I'll keep an eye on that, for sure." + }, + { + "time": "16:33:27", + "speaker": "Alex Martemyanov", + "text": "Yeah." + }, + { + "time": "16:33:28", + "speaker": "Dominik Kapusta", + "text": "And if we get to rewriting the app in Chromium, we will definitely get a bigger team. And we'll have plenty of work, of course." + }, + { + "time": "16:33:37", + "speaker": "Alex Martemyanov", + "text": "Yeah, and that is basically the chance to get to Linux platform, or…" + }, + { + "time": "16:33:38", + "speaker": "Dominik Kapusta", + "text": "So…" + }, + { + "time": "16:33:43", + "speaker": "Alex Martemyanov", + "text": "Almost free, I guess." + }, + { + "time": "16:33:44", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah." + }, + { + "time": "16:33:45", + "speaker": "Alex Martemyanov", + "text": "And I've seen there was some planning around it being done in Asana somewhere." + }, + { + "time": "16:33:52", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:33:54", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm. Who knows, maybe I could upgrade my MacBook to the Framework MacBook. Next slide." + }, + { + "time": "16:34:01", + "speaker": "Dominik Kapusta", + "text": "Yeah. Uh… Ah, ah, ah. All right, that's it. On… In other… topics. There was… Oh, but this is not really a macOS thing, but anyway, there was this Bitrise incident over the weekend. They haven't… they…" + }, + { + "time": "16:34:25", + "speaker": "Alex Martemyanov", + "text": "Yeah, I know." + }, + { + "time": "16:34:27", + "speaker": "Dominik Kapusta", + "text": "It's ongoing, it's actually ongoing, Jackie." + }, + { + "time": "16:34:28", + "speaker": "Alex Martemyanov", + "text": "I tried to merge on Saturday to get to the release, because there was late approval on Friday, and yeah." + }, + { + "time": "16:34:32", + "speaker": "Dominik Kapusta", + "text": "Right… And, uh…" + }, + { + "time": "16:34:38", + "speaker": "Alex Martemyanov", + "text": "Been there. There is bankings. Incident, as promised, on 17th of November." + }, + { + "time": "16:34:44", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Oh, yeah. Oh." + }, + { + "time": "16:34:48", + "speaker": "Alex Martemyanov", + "text": "So, yeah, should get some cash from base." + }, + { + "time": "16:34:52", + "speaker": "Dominik Kapusta", + "text": "Ha ha ha." + }, + { + "time": "16:34:53", + "speaker": "Alex Martemyanov", + "text": "While I could." + }, + { + "time": "16:34:56", + "speaker": "Dominik Kapusta", + "text": "Interesting." + }, + { + "time": "16:34:57", + "speaker": "Alex Martemyanov", + "text": "And…" + }, + { + "time": "16:34:59", + "speaker": "Dominik Kapusta", + "text": "Yeah. But they had, uh… One, two, three. 3… almost 3 days… 60 something hours of downtime. Or some sort of uses." + }, + { + "time": "16:35:13", + "speaker": "Alex Martemyanov", + "text": "Oh, right, about the priorities and interests. So, basically, I've got some… not some, maybe a lot of plans being done around testing infrastructure, all this stuff that should. That looks mostly like a top priority project, I guess, to set up some older OS runners and prepare this. I guess it would be something I would be interested in, too. If there is some possibility, but since it's kind of objective work." + }, + { + "time": "16:35:46", + "speaker": "Dominik Kapusta", + "text": "Yeah. Okay. Mmhm." + }, + { + "time": "16:35:51", + "speaker": "Alex Martemyanov", + "text": "And… I'm not sure if it could be chosen chosen as a top priority." + }, + { + "time": "16:35:52", + "speaker": "Dominik Kapusta", + "text": "This will have to… Yeah, well, uh… well, yes, if it's scored appropriately." + }, + { + "time": "16:35:57", + "speaker": "Alex Martemyanov", + "text": "Okay." + }, + { + "time": "16:36:01", + "speaker": "Dominik Kapusta", + "text": "and scores highly in the Apple Projects rubric. So, if you have a… If you have some… project-sized work to… to do… The best thing would be to… Scope a project for it. Added to Apple Projects, and… And, uh… And Scott is there. And let's see. If it can be picked up. And then keep linking it in your next TP tasks." + }, + { + "time": "16:36:37", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm. Okay." + }, + { + "time": "16:36:37", + "speaker": "Dominik Kapusta", + "text": "Apart from these, we were talking about a separate Xcode project for UI tests." + }, + { + "time": "16:36:45", + "speaker": "Alex Martemyanov", + "text": "Yes, but, uh… But it didn't move on since then. So basically, um… No worries. What was there? It was not needed. Yeah, I should have commented it. And, uh, so I had some experiments what was needed and what I, uh… What I tried and had some success is basically building all the…" + }, + { + "time": "16:37:16", + "speaker": "Dominik Kapusta", + "text": "Oh, okay." + }, + { + "time": "16:37:20", + "speaker": "Alex Martemyanov", + "text": "all the corners in one run from the project, including the app and the runners, and then just distributing to the tester, to the runners." + }, + { + "time": "16:37:23", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:37:33", + "speaker": "Alex Martemyanov", + "text": "So there will be only some extra work needed to build the macOS 12 compatibility layer. It's also defined and sitting somewhere in my work trees. So basically, the project can stay as it is, and we don't need since… but we can build all together and just distribute it to every other macOS, and it works." + }, + { + "time": "16:37:55", + "speaker": "Dominik Kapusta", + "text": "But… Is it? Okay. Interesting. But you're build… so what are you building? What would the…" + }, + { + "time": "16:38:06", + "speaker": "Alex Martemyanov", + "text": "the app and the runner, the UI test runner." + }, + { + "time": "16:38:06", + "speaker": "Dominik Kapusta", + "text": "What do we build there? The app and the test run… okay, but the test runner would be a debug build. Like, ad hoc, signed, or unsigned?" + }, + { + "time": "16:38:16", + "speaker": "Alex Martemyanov", + "text": "Maybe. But I think…" + }, + { + "time": "16:38:19", + "speaker": "Dominik Kapusta", + "text": "I'm wondering about code signing and the ability to run this on a different machine." + }, + { + "time": "16:38:23", + "speaker": "Alex Martemyanov", + "text": "I… I remember it did… it used to work, it just worked, but I didn't push it forward since then, so…" + }, + { + "time": "16:38:29", + "speaker": "Dominik Kapusta", + "text": "Okay, I mean, yeah, if it works for you, then that's great. I tried doing something like that some time ago. It was probably different. It was probably different. But it was, ah, it was a different thing. It was a different thing. It was copying derived data to runners." + }, + { + "time": "16:38:58", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:38:58", + "speaker": "Dominik Kapusta", + "text": "so that it could be reused. But that didn't work." + }, + { + "time": "16:39:02", + "speaker": "Alex Martemyanov", + "text": "Okay." + }, + { + "time": "16:39:08", + "speaker": "Dominik Kapusta", + "text": "Cool. Uh…" + }, + { + "time": "16:39:08", + "speaker": "Alex Martemyanov", + "text": "Sure. Do you have it by your hand, the task?" + }, + { + "time": "16:39:15", + "speaker": "Dominik Kapusta", + "text": "Oh, no, no, no, that was a long time ago, and I didn't have a task for that. That's when I was breaking down UI tests." + }, + { + "time": "16:39:21", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm. No, I mean… The, uh, the one about splitting the project." + }, + { + "time": "16:39:25", + "speaker": "Dominik Kapusta", + "text": "What do you mean?" + }, + { + "time": "16:39:32", + "speaker": "Alex Martemyanov", + "text": "I'm just trying to find it." + }, + { + "time": "16:39:32", + "speaker": "Dominik Kapusta", + "text": "No, I don't think… Well, let's see." + }, + { + "time": "16:39:40", + "speaker": "Alex Martemyanov", + "text": "Thank you. Move, yeah, on it. I'll just probably post an update on it, that it's currently on pause, and uh…" + }, + { + "time": "16:39:50", + "speaker": "Dominik Kapusta", + "text": "Okay. Okay, okay, good." + }, + { + "time": "16:39:53", + "speaker": "Alex Martemyanov", + "text": "And. I don't see her. If it's reasonable to move on with it." + }, + { + "time": "16:40:11", + "speaker": "Dominik Kapusta", + "text": "The next thing we should talk about is the Apple Meetup. We don't have any…" + }, + { + "time": "16:40:15", + "speaker": "Alex Martemyanov", + "text": "Which is not gonna happen in Japan, as I understand." + }, + { + "time": "16:40:19", + "speaker": "Dominik Kapusta", + "text": "Yeah, very unlikely. Well, I don't know anything. I haven't spoken to Jonathan." + }, + { + "time": "16:40:22", + "speaker": "Alex Martemyanov", + "text": "Here." + }, + { + "time": "16:40:27", + "speaker": "Dominik Kapusta", + "text": "And I expect Jonathan to say something about it in today's Apple Weekly. But… Yeah, it's unlikely to be Japan, or… Well, let's see, let's actually see, because… There's this discussion here, if you missed it." + }, + { + "time": "16:40:49", + "speaker": "Alex Martemyanov", + "text": "Yeah, it's, you know, it's…" + }, + { + "time": "16:40:52", + "speaker": "Dominik Kapusta", + "text": "Meetup location guide. Hmm. Places that would work for you. I like Chile, Costa Rica again, Mexico." + }, + { + "time": "16:41:16", + "speaker": "Alex Martemyanov", + "text": "It's Chris Harbour, I guess." + }, + { + "time": "16:41:19", + "speaker": "Dominik Kapusta", + "text": "Mexico is what? Sorry, higher. Mm." + }, + { + "time": "16:41:19", + "speaker": "Alex Martemyanov", + "text": "I've got this. Mexico is maybe problematic." + }, + { + "time": "16:41:24", + "speaker": "Dominik Kapusta", + "text": "Ah, okay." + }, + { + "time": "16:41:26", + "speaker": "Alex Martemyanov", + "text": "Um, not sure. They kinda have, uh… easier visa rules, seemingly easy visa rules, but I've heard there's a lot of rejections just in the airport that they just said, you're not going because of no explanations. So they are." + }, + { + "time": "16:41:41", + "speaker": "Dominik Kapusta", + "text": "Oh, shit. Oh, that sucks." + }, + { + "time": "16:41:46", + "speaker": "Alex Martemyanov", + "text": "experienced some problems with crimes, probably, or some Russia-related stuff, I don't know, but…" + }, + { + "time": "16:41:51", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:41:56", + "speaker": "Alex Martemyanov", + "text": "There were some issues I've heard of." + }, + { + "time": "16:41:56", + "speaker": "Dominik Kapusta", + "text": "No. Yeah, I am." + }, + { + "time": "16:42:10", + "speaker": "Alex Martemyanov", + "text": "Yeah, it's done, yeah. Still not considered, although it's a really great place from my perspective. Mmm. Broadcasting… Uruguay, probably… And. And, uh… Ireland, Australia, UK, generally. So that's kind of there. But Canada, I don't know, maybe it may work. Speeds. Also may work, but they require extra… Extra movements to…" + }, + { + "time": "16:43:01", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:43:02", + "speaker": "Alex Martemyanov", + "text": "Probably bizarre. And for… yeah, Egypt. Why not?" + }, + { + "time": "16:43:09", + "speaker": "Dominik Kapusta", + "text": "Egypt would be interesting." + }, + { + "time": "16:43:12", + "speaker": "Alex Martemyanov", + "text": "Ah, it's not, it's not, it's not the place. It's the places where…" + }, + { + "time": "16:43:12", + "speaker": "Dominik Kapusta", + "text": "I haven't been there. Not on the list. Ah, okay. Yeah." + }, + { + "time": "16:43:17", + "speaker": "Alex Martemyanov", + "text": "Yeah, our team leaves. Wrong location. Rome, Paris, London, Barcelona, Vienna… Europe, basically." + }, + { + "time": "16:43:30", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm, yeah, yeah." + }, + { + "time": "16:43:32", + "speaker": "Alex Martemyanov", + "text": "I can give it another try, maybe. Who knows? Maybe because… Maybe France. So I've heard people are getting visas to France." + }, + { + "time": "16:43:48", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah." + }, + { + "time": "16:43:49", + "speaker": "Alex Martemyanov", + "text": "And anyways, you can get a visa for France, and then go to some other… country, or just have a flight to France first, and then move further." + }, + { + "time": "16:43:55", + "speaker": "Dominik Kapusta", + "text": "That's right. That's right." + }, + { + "time": "16:44:03", + "speaker": "Alex Martemyanov", + "text": "Correct, yeah, Spain, Sweden, Belgium, Portugal… It's basically all the… European cities." + }, + { + "time": "16:44:14", + "speaker": "Dominik Kapusta", + "text": "Yeah, I think the first… The first that's not European is, well, New York City and then Playa del Carmen in Mexico." + }, + { + "time": "16:44:26", + "speaker": "Alex Martemyanov", + "text": "Yeah, I guess, uh… New York could work better. But it's harder for me to… to fulfill all the paper paperwork for it." + }, + { + "time": "16:44:37", + "speaker": "Dominik Kapusta", + "text": "Okay, I see. Well." + }, + { + "time": "16:44:39", + "speaker": "Alex Martemyanov", + "text": "So, for Europe, it's just an easy application. I just have to go and apply for… get some bank statements and apply, but it's…" + }, + { + "time": "16:44:45", + "speaker": "Dominik Kapusta", + "text": "Yeah…" + }, + { + "time": "16:44:47", + "speaker": "Alex Martemyanov", + "text": "Would be a third reject in a row, maybe or maybe not." + }, + { + "time": "16:44:50", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Oh." + }, + { + "time": "16:44:53", + "speaker": "Alex Martemyanov", + "text": "That's, you know, for New York, it's kind of more complicated. Including the flight." + }, + { + "time": "16:45:01", + "speaker": "Dominik Kapusta", + "text": "You know. I'm really curious what will… come out of it because, yeah, it's interesting. It's just… Sounds… sounds bad that we have to sort of rule you out of every meetup every year, unless we go… To Costa Rica, like, 3 years ago, 2 years ago, uh…" + }, + { + "time": "16:45:35", + "speaker": "Alex Martemyanov", + "text": "Yeah, why not?" + }, + { + "time": "16:45:36", + "speaker": "Dominik Kapusta", + "text": "Why not? Yeah, I mean, we should do it. Let's see. Yeah, let's see, maybe we'll talk about it in the Apple Weekly, hopefully. All right, other than that, so to recap the call, perhaps… Unless… do you have anything else to talk about?" + }, + { + "time": "16:46:06", + "speaker": "Alex Martemyanov", + "text": "And… Well, I guess not." + }, + { + "time": "16:46:09", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:46:10", + "speaker": "Alex Martemyanov", + "text": "Should be…" + }, + { + "time": "16:46:12", + "speaker": "Dominik Kapusta", + "text": "Yeah, sure, sure, sure. Alright, uh… So… Yeah, so you're moving to OB, but you'll have to… Go through. Uh… And it looks like you have another project scheduled after this one." + }, + { + "time": "16:46:33", + "speaker": "Alex Martemyanov", + "text": "Yeah, the, uh… It seems it's…" + }, + { + "time": "16:46:37", + "speaker": "Dominik Kapusta", + "text": "Stop. Stop." + }, + { + "time": "16:46:37", + "speaker": "Alex Martemyanov", + "text": "consequent projects." + }, + { + "time": "16:46:39", + "speaker": "Dominik Kapusta", + "text": "Stop iOS reload loops after tab memory kills. Which may be interesting… I mean, interesting, as in, uh, maybe straightforward, because we have the… Uh, we have that in macOS. To some extent, in some shape. It's, of course, different, but… At least there's a precedent. But it looks like you'll stick with OB until the end of the year, at least. And, uh… That's that, essentially. Umm. Fine. So if you could update the UI tests thingy, that would be great as well. And that's it, you're wrapping up your project, so…" + }, + { + "time": "16:47:37", + "speaker": "Alex Martemyanov", + "text": "Mmhm." + }, + { + "time": "16:47:38", + "speaker": "Dominik Kapusta", + "text": "Probably not much time to work on AORs. But also, there's nothing burning over there. I mean, there is a burning thing in the CIA UR, and I'll have to rotate all GitHub Action secrets. Should be funny! Okay. Uh, yeah, so we can just… Wrap it up here, let's catch up again next week. And see how OB work is going." + }, + { + "time": "16:48:06", + "speaker": "Alex Martemyanov", + "text": "Okay. Noted. Cool." + }, + { + "time": "16:48:09", + "speaker": "Dominik Kapusta", + "text": "Cool. Yeah, I'll see you at the Apple Weekly. Thanks a lot, Alex. Have a great rest of the day." } ] } diff --git a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md index 68f2285b..855079d7 100644 --- a/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md +++ b/work/zoom-transcripts/2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A/transcript.md @@ -15,3 +15,252 @@ source: "https://us01mynotes.zoom.us/KcmYOq5_SQGPxdkdbhRx9A" - **16:09:03 · Alex Martemyanov:** Pretty good. How's it going? That's… that's great. Yeah, probably I'm gonna take one day off next week too, or Monday, or extended weekend. Uh, yeah, just to have some rest from the… Project I'm doing. - **16:09:28 · Dominik Kapusta:** Nie. - **16:09:31 · Alex Martemyanov:** Okay. So for the past week, uh, what was there? +- **16:09:38 · Dominik Kapusta:** To priority. +- **16:09:40 · Alex Martemyanov:** Yes, uh, there is, uh, current priorities, uh… +- **16:09:41 · Dominik Kapusta:** Jest. +- **16:09:45 · Alex Martemyanov:** to be postmortemed on Thursday, since today's slot is taken. Which is a good thing, I guess, not to go to the late night. There is still some. some discussion going on the extra extension lifecycle matrix to be added as a follow-up to analyze some NGS code. Whether we receive this in it or not. Is it almost before? Probably it's not before, but we need to understand. Exactly where. Anyways, I'm gonna… comment to the project later today. Postmortem is planned for, uh, Thursday slots. And, uh, there was, uh, the metric… I was discussing with Bartek a couple of weeks ago, and I just pushed it forward today, and uh… I've got a scalpel of four. Couple of feature flags removed. Couple of tasks still in this step. One crush, and let… Hopefully to be reviewed today and. And the neutral priority, yes. So I started kinda looking into it. Again, it doesn't seem like something… Precise. To be done, some measurements. Okay, hopefully it won't take too long, just some time-boxed experiments, I guess, and some defined experiments like splitting the CSAs into… Zero parts. Mm-hmm. Yeah, and really hoping the next top priority won't be of… these claims. If you can just… Speak up to… somebody in the objectives that, yeah, I'm seeking for something closer to the browser. Probably… If it can work, because, uh, yeah, the last top priority, I can't say that it was. Great, and I feel great about it. Hmmm. +- **16:12:25 · Dominik Kapusta:** Feel great about what exactly? Sorry. +- **16:12:27 · Alex Martemyanov:** Yeah, I'm not feeling great about the last top priority I got, the CPM. +- **16:12:31 · Dominik Kapusta:** You are not feeling good. Yeah. +- **16:12:33 · Alex Martemyanov:** Yeah, I'm really tired of it, and uh… Of life. +- **16:12:40 · Dominik Kapusta:** Yeah, I can tell. I can tell, of course. It's not an obvious win, right? This project, which sucks. +- **16:12:50 · Alex Martemyanov:** Yeah. Yeah. +- **16:12:53 · Dominik Kapusta:** But the… The most important question is, or maybe you have the answer already, or maybe someone gave that answer to you, whether that work you spent on it was… Uh, useful or not useful. +- **16:13:13 · Alex Martemyanov:** So, so, I'm sure there's a lot. +- **16:13:15 · Dominik Kapusta:** Yeah. +- **16:13:15 · Alex Martemyanov:** So there were some bugs fixed, but the main metric. +- **16:13:17 · Dominik Kapusta:** Um, okay. +- **16:13:19 · Alex Martemyanov:** was not, it didn't reach the target basically defined to lower the numbers below one percent. At least on macOS, it's still above one percent. +- **16:13:26 · Dominik Kapusta:** Oh, yeah. Mm-mm. So I guess one other question could be… Could this work be stopped earlier? Just for the post-mortem, because, of course, it happened already, so just for the future… Could you? Could someone, because it's not only you, it's plenty, like, many people in OE, right? being fine with this project running for… As long as it run. So, it looked like… There was hope all the time, or… yeah, we had… +- **16:14:07 · Alex Martemyanov:** Okay. I… for sure it could, uh, probably finish earlier, maybe couple of weeks. +- **16:14:09 · Dominik Kapusta:** Some more ideas. +- **16:14:16 · Alex Martemyanov:** But I don't know. Not in the fall. Since we got several iterations, like first naive approach, several bugs found, measured, two weeks to the next release, measured again. And, uh… Measurement showing the debugs did not affect, and another iteration of adding metrics. To find something else. So, uh… Of course we could just drop it at some point defining like. Like a trailer or partial. But, uh… Probably the research was kind of genuine, I guess. heading… several hypotheses tested, tried, measured, and. There is still some progress done over the bug fixes. Only maybe just not enough. to to call it successful. +- **16:15:24 · Dominik Kapusta:** Right. Um… Is the postmortem happening today? +- **16:15:38 · Alex Martemyanov:** Meeting Thursday. +- **16:15:39 · Dominik Kapusta:** Thursday. +- **16:15:42 · Alex Martemyanov:** Yeah. Yes. Today, today is Thursday. +- **16:15:48 · Dominik Kapusta:** Oh, yeah, yeah, yeah. +- **16:15:48 · Alex Martemyanov:** During the slot system. +- **16:15:51 · Dominik Kapusta:** Okay, sure, sure, sure. Cool. Yeah, but anyway, and you're moving to OB right now. Which… is great. I think, what do you think about this project? +- **16:16:10 · Alex Martemyanov:** Hmm. Okay. I hope. I'll be still alive when it ends. There will be New Year holidays close. So that should add on it. But, uh, yeah, I can't say that I'm happy about it. +- **16:16:32 · Dominik Kapusta:** You're not happy about it. +- **16:16:33 · Alex Martemyanov:** Not really. +- **16:16:36 · Dominik Kapusta:** Yeah, from my perspective, it's just that it's… It's an important project. +- **16:16:46 · Alex Martemyanov:** For sure, for sure, yeah. +- **16:16:46 · Dominik Kapusta:** It's something that has many eyes on it right now. So. I'm glad you're working on it. It's not… +- **16:16:58 · Alex Martemyanov:** like… Unfortunately, my, uh… +- **16:16:59 · Dominik Kapusta:** It's… +- **16:17:02 · Alex Martemyanov:** Mm, feeling on it, and, uh, my motivation… is not driven by the importance of the project. Oh, okay. +- **16:17:11 · Dominik Kapusta:** Yeah, and that's… +- **16:17:14 · Alex Martemyanov:** It's a pity, but… yeah. +- **16:17:15 · Dominik Kapusta:** That's, I mean, that's fair, that's fair, of course. I'm just saying it for context. Because… I know it's hard. Because you have to… You have to endure that. But my hope is that in the long run you could. Even, perhaps… Stay in OB. +- **16:17:45 · Alex Martemyanov:** And let's see… let's see how it goes. So, I… +- **16:17:47 · Dominik Kapusta:** I'm… I'm… No. +- **16:17:51 · Alex Martemyanov:** Yeah, looking to the project, looking at the project, it's split to some parts, tasks for one or two days. Uh, so hopefully it won't take, uh, too much of… of my energy. to complete it. +- **16:18:08 · Dominik Kapusta:** Oh. No. +- **16:18:09 · Alex Martemyanov:** At least in the scope to define it right now. So, the kickoff goes to the next week, I guess? +- **16:18:23 · Dominik Kapusta:** Bring the apple slices back. +- **16:18:28 · Alex Martemyanov:** Or… When the will be quickly happening. +- **16:18:32 · Dominik Kapusta:** I don't know. I don't know. +- **16:18:35 · Alex Martemyanov:** November 16 yesterday, on Monday, yeah, so… +- **16:18:38 · Dominik Kapusta:** Okay, Mondays. Mm-hmm. +- **16:18:43 · Alex Martemyanov:** Okay, fine. I guess it naturally goes to the next Monday. +- **16:18:56 · Dominik Kapusta:** at least… At least this is… kind of… work, where you can… Clearly see the result, at least in the numbers of… The size of, of, of… JavaScript bundle that's loaded into the binary, into the, well, WebView. +- **16:19:20 · Alex Martemyanov:** Yeah, I can't say that I'm really good at JavaScript bundles. And all this stuff and how it should work, but yeah, having… probably having LLMs and some good judgment. We can just make a testing strategy and experiment on the memory footprint, and whether the testing website. +- **16:19:36 · Dominik Kapusta:** Um… Bye. +- **16:19:45 · Alex Martemyanov:** websites work, although I didn't find the exact websites when it fails. But we have the privacy test pages done by Bartosz, so… Hopefully it just works and should be pretty straightforward looking from. +- **16:19:59 · Dominik Kapusta:** Yeah. +- **16:20:04 · Alex Martemyanov:** from today. But we'll see how it goes. +- **16:20:07 · Dominik Kapusta:** So they had some previous work on that, apparently. from… Uh, config, pruning, and uh… Passing config as a JSON string. What is that? Probably not using JSON serialization. +- **16:20:29 · Alex Martemyanov:** I guess… +- **16:20:33 · Dominik Kapusta:** Anyway, they were doing some optimizations, and they had some… +- **16:20:33 · Alex Martemyanov:** And then… +- **16:20:40 · Dominik Kapusta:** Some test websites. Some websites to test it on, so that part should be… +- **16:20:43 · Alex Martemyanov:** Mm-hmm. +- **16:20:48 · Dominik Kapusta:** resolved, but now I'm wondering… I'm essentially wondering why do they need a native engineer for that, because it sounds like JavaScript work. If they want to have separate bundles for iOS and macOS, they could do it in CSE, just like that, and then just… Rename the files in the native code. +- **16:21:12 · Alex Martemyanov:** Well, who cares nowadays? +- **16:21:16 · Dominik Kapusta:** Yeah, of course, I mean, whatever. You could get a project advisor, speak to Dave, I guess, and get a project advisor from the front-end team, maybe? Maybe? +- **16:21:17 · Alex Martemyanov:** Okay. Mmhm. +- **16:21:27 · Dominik Kapusta:** Someone who is experienced with CS. +- **16:21:29 · Alex Martemyanov:** Yep. +- **16:21:32 · Dominik Kapusta:** But also, an alternative is to have someone from the Apple team, and then LLM help, and just reach out, being able to reach out to a front-end person. If needed. +- **16:21:45 · Alex Martemyanov:** Okay, I'll just ping Dave, probably, who could… +- **16:21:47 · Dominik Kapusta:** Yeah, I mean… +- **16:21:48 · Alex Martemyanov:** You suggest for… Advising the project. +- **16:21:57 · Dominik Kapusta:** Yeah, that's a good idea. Dave would probably be able to. +- **16:21:59 · Alex Martemyanov:** Mm-hmm, I'll be back in. Luke. +- **16:22:02 · Dominik Kapusta:** So just someone. +- **16:22:03 · Alex Martemyanov:** Or is it Thanksgiving? +- **16:22:07 · Dominik Kapusta:** Not yet. Not yet. +- **16:22:10 · Alex Martemyanov:** Where is it? +- **16:22:12 · Dominik Kapusta:** I think it's… +- **16:22:13 · Alex Martemyanov:** I'm leaving 2026. +- **16:22:14 · Dominik Kapusta:** Beginning… or, yeah, last week of November or first week of December. 26. +- **16:22:20 · Alex Martemyanov:** Uh, 26. +- **16:22:22 · Dominik Kapusta:** Okay. +- **16:22:23 · Alex Martemyanov:** Yeah, okay, it's Thursday. Mmhm. +- **16:22:34 · Dominik Kapusta:** Split the iOS bundle from macOS. Make the isolated world mainframe only on Apple. +- **16:22:50 · Alex Martemyanov:** Okay, I think Dave in the advisor's task. +- **16:23:00 · Dominik Kapusta:** Okay. And drop the unused tracker. +- **16:23:05 · Alex Martemyanov:** Yes. +- **16:23:07 · Dominik Kapusta:** Try from Apple bundles. Okay. Nice. Sounds… Easy? I don't want to… I don't want to say easy, but… Uh… +- **16:23:24 · Alex Martemyanov:** Yeah, I hope so. +- **16:23:25 · Dominik Kapusta:** You'll have a hack phase, and you'll figure out most of the things in the hack phase, hopefully. +- **16:23:26 · Alex Martemyanov:** Because… +- **16:23:32 · Dominik Kapusta:** And also, if you're… if everything goes smoothly. You probably will have the entire project implemented during the hack phase. Who knows? +- **16:23:42 · Alex Martemyanov:** Mm-hmm. +- **16:23:42 · Dominik Kapusta:** But if there are obstacles, then of course you'll have to… go through them during the project. +- **16:23:48 · Alex Martemyanov:** Anyways, there's probably some triages. Reviews, front end team, back and forth and so on. +- **16:23:53 · Dominik Kapusta:** Yeah, yeah, yeah. Totally. Maybe tech designs. +- **16:23:57 · Alex Martemyanov:** Yeah. For sure. +- **16:24:01 · Dominik Kapusta:** Sounds good. It's a bit unclear to me whether we should, um… Whether we should, uh… Have it as… or run… Involve more Apple people or front-end people here. But let's see. Let's see what Dave suggests, first of all. +- **16:24:24 · Alex Martemyanov:** Mm-hmm. +- **16:24:25 · Dominik Kapusta:** Mm-hmm. And, uh… When do you think you would start working on it? Thursday? +- **16:24:34 · Alex Martemyanov:** Uh, yes, uh, I think tomorrow. +- **16:24:37 · Dominik Kapusta:** Tomorrow. Oh, that's cool. Nice. +- **16:24:38 · Alex Martemyanov:** Wednesday. Should work, I guess, if nothing strikes. +- **16:24:52 · Dominik Kapusta:** Nice, nice. Awesome. +- **16:24:52 · Alex Martemyanov:** So there is still one follow up for the current project to analyze metrics. So, I just need… Max and Mihal to you. Uh, to check. Basically, it seems, uh… Hmm… It is in the middle, I guess. And should not be… Too big. So, the pull requests are basically ready, and we should just agree on what we measure, and… Added Grafana board, probably. So it's not… It's not too much. +- **16:25:29 · Dominik Kapusta:** Yeah, uh, I see that this task is not added to technical designs? +- **16:25:29 · Alex Martemyanov:** Okay. +- **16:25:35 · Dominik Kapusta:** I'm not sure if it's an omission or you meant it that way. +- **16:25:35 · Alex Martemyanov:** Hmm… Oh, shit. You're right. per year. Review your remarks. Yeah. +- **16:25:54 · Dominik Kapusta:** Awesome. +- **16:25:56 · Alex Martemyanov:** Indeed, the extensions. Mm-hmm. +- **16:26:21 · Dominik Kapusta:** So setting this project aside and setting your new top priority aside. What are the kinds of things you would like to work on right now? +- **16:26:32 · Alex Martemyanov:** I guess it's mostly, uh… Around my profile, and… I told, uh… Basically, the browser and… There is still some, uh… Things not finished, never finished, like bookmarks, history, and so on. Mm-hmm. +- **16:26:57 · Dominik Kapusta:** Okay. +- **16:26:59 · Alex Martemyanov:** So… +- **16:27:00 · Dominik Kapusta:** So, essentially, OL… +- **16:27:02 · Alex Martemyanov:** Extension to oil, yeah. +- **16:27:03 · Dominik Kapusta:** Type of work. Uh… Got it. That would be great. But the problem with OL right now is that it's tier two, whatever that means. I mean, it means that it's not the greatest impact on the company top priority, but okay. And, uh… +- **16:27:25 · Alex Martemyanov:** I mean, there's alternative options if to consider if we have, for example, if we have, if we ever plan to deliver, like, a browser, Chromium-based browser to Linux, and I could switch to it, for example. +- **16:27:32 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Yeah. Yeah. +- **16:27:40 · Alex Martemyanov:** Yeah. Just just not to Windows. +- **16:27:41 · Dominik Kapusta:** Yeah, yeah, yeah. Of course, yes, yes, yes. It's still a couple months ahead. So let's see, but… it seems to me that there will be push to having… to having a Chromium. Based browser on macOS. and that will be a big project. Of course, Mac OS, yes, and then we will have to migrate everything essentially the entire app to chromium, which is what windows is working on right now. +- **16:28:06 · Alex Martemyanov:** Mm-hmm. Marcus? Mmhm. Right, sir. +- **16:28:17 · Dominik Kapusta:** And, uh… Yeah, and for that we will need many people. But let's see if it happens in the first place. On Windows, it's happening because Windows browser is shitty. As hell, it's just… +- **16:28:33 · Alex Martemyanov:** Mmhm. +- **16:28:35 · Dominik Kapusta:** Crap. So, they are fixing it by… Forking Chromium. Then once they have Chromium, they could… a Chromium fork… We could work on… a Linux client, and macOS client as well. The added value of a Chromium fork… is that suddenly you get all the core browser features for free. Things like tab groups. +- **16:29:04 · Alex Martemyanov:** Yeah, basically this was, that's what I was suggesting during my, when I was just hiring, I mean employed. +- **16:29:05 · Dominik Kapusta:** Profiles. +- **16:29:16 · Alex Martemyanov:** Oh. And, uh, yeah. I do understand since I did some research back then and I was basically proving that the browser needs to be Chromium based. But back then. It was… About policy mostly. But I guess it's a good news. And it's a bit pity that there is some work done that's being trashed. +- **16:29:54 · Dominik Kapusta:** Yeah, yeah. +- **16:29:55 · Alex Martemyanov:** But anyways. +- **16:29:56 · Dominik Kapusta:** I mean, let's see, because I… That's something that we'll need to probably calculate, try to estimate, uh, but… in the long run, I think this sounds good, because otherwise, we have to… we would have to implement. Everything ourselves. And then there's a question of whether to go that way. or not, whether to invest time and people in. Implementing… Tab multi-select, things like that, right? Or… +- **16:30:31 · Alex Martemyanov:** Yeah, I'm… +- **16:30:35 · Dominik Kapusta:** For Chromium, spend… Half a year or more. And have it… just for free, in a sense. So… We'll get there, probably not earlier than spring next year. And, uh, in the mean… because what I'm… Observing right now is… It's looking harder and harder to get buy-in for implementing features. I wanted to add reader mode. and I run a Hackface for the reader mode, and, uh, well, it works. It just needs some more… Integration with whatever we have in the browser right now, like adding these two settings. +- **16:31:26 · Alex Martemyanov:** Mm-hmm. +- **16:31:30 · Dominik Kapusta:** And I wanted to push it through in the assessment, and I was like, okay, we can have a hack phase. Just 3 days! To use an agent and, like. embed. Reader mode settings in permissions mechanism, because it's… Similar. Uh, and they were like, okay, hug face maybe, and then someone said. that's fine, I understand it's a hack phase, it's just 3 days, but blah blah blah, there's something more important, and let's only do it if we run out of tasks for that. For the assessment, I mean, for the roadmap. So it's still waiting. And it was like it was a couple of days. it's not even… Any kind of a long project. Uh, so if it's going to look like this going forward for everything else, then… Are we even needed here for anything, or what? So, yeah. Let's see. +- **16:32:36 · Alex Martemyanov:** Okay, anyways, I think it's a wide move to Chromium. There is, like, WebRTC, there is all the browser site issues solved, basically, for free, because I got my tax payments have to be done in Chrome, because they don't work in LambdaGo. +- **16:32:37 · Dominik Kapusta:** Yeah, we… You know. Yeah, yeah, yeah. Yeah, yeah. +- **16:32:54 · Alex Martemyanov:** And, yeah, a lot of things, basically. +- **16:32:59 · Dominik Kapusta:** Um… Nothing will happen in that area this year, for sure. Probably not in January, but I'll keep monitoring it. The next assessment in OL is in January. shouldn't be… this shouldn't be a topic in January either. Because Windows is not shipped yet. But yeah, let's… I'll keep an eye on that, for sure. +- **16:33:27 · Alex Martemyanov:** Yeah. +- **16:33:28 · Dominik Kapusta:** And if we get to rewriting the app in Chromium, we will definitely get a bigger team. And we'll have plenty of work, of course. +- **16:33:37 · Alex Martemyanov:** Yeah, and that is basically the chance to get to Linux platform, or… +- **16:33:38 · Dominik Kapusta:** So… +- **16:33:43 · Alex Martemyanov:** Almost free, I guess. +- **16:33:44 · Dominik Kapusta:** Yeah, yeah. +- **16:33:45 · Alex Martemyanov:** And I've seen there was some planning around it being done in Asana somewhere. +- **16:33:52 · Dominik Kapusta:** Mm-hmm. +- **16:33:54 · Alex Martemyanov:** Mm-hmm. Who knows, maybe I could upgrade my MacBook to the Framework MacBook. Next slide. +- **16:34:01 · Dominik Kapusta:** Yeah. Uh… Ah, ah, ah. All right, that's it. On… In other… topics. There was… Oh, but this is not really a macOS thing, but anyway, there was this Bitrise incident over the weekend. They haven't… they… +- **16:34:25 · Alex Martemyanov:** Yeah, I know. +- **16:34:27 · Dominik Kapusta:** It's ongoing, it's actually ongoing, Jackie. +- **16:34:28 · Alex Martemyanov:** I tried to merge on Saturday to get to the release, because there was late approval on Friday, and yeah. +- **16:34:32 · Dominik Kapusta:** Right… And, uh… +- **16:34:38 · Alex Martemyanov:** Been there. There is bankings. Incident, as promised, on 17th of November. +- **16:34:44 · Dominik Kapusta:** Mm-hmm. Oh, yeah. Oh. +- **16:34:48 · Alex Martemyanov:** So, yeah, should get some cash from base. +- **16:34:52 · Dominik Kapusta:** Ha ha ha. +- **16:34:53 · Alex Martemyanov:** While I could. +- **16:34:56 · Dominik Kapusta:** Interesting. +- **16:34:57 · Alex Martemyanov:** And… +- **16:34:59 · Dominik Kapusta:** Yeah. But they had, uh… One, two, three. 3… almost 3 days… 60 something hours of downtime. Or some sort of uses. +- **16:35:13 · Alex Martemyanov:** Oh, right, about the priorities and interests. So, basically, I've got some… not some, maybe a lot of plans being done around testing infrastructure, all this stuff that should. That looks mostly like a top priority project, I guess, to set up some older OS runners and prepare this. I guess it would be something I would be interested in, too. If there is some possibility, but since it's kind of objective work. +- **16:35:46 · Dominik Kapusta:** Yeah. Okay. Mmhm. +- **16:35:51 · Alex Martemyanov:** And… I'm not sure if it could be chosen chosen as a top priority. +- **16:35:52 · Dominik Kapusta:** This will have to… Yeah, well, uh… well, yes, if it's scored appropriately. +- **16:35:57 · Alex Martemyanov:** Okay. +- **16:36:01 · Dominik Kapusta:** and scores highly in the Apple Projects rubric. So, if you have a… If you have some… project-sized work to… to do… The best thing would be to… Scope a project for it. Added to Apple Projects, and… And, uh… And Scott is there. And let's see. If it can be picked up. And then keep linking it in your next TP tasks. +- **16:36:37 · Alex Martemyanov:** Mm-hmm. Okay. +- **16:36:37 · Dominik Kapusta:** Apart from these, we were talking about a separate Xcode project for UI tests. +- **16:36:45 · Alex Martemyanov:** Yes, but, uh… But it didn't move on since then. So basically, um… No worries. What was there? It was not needed. Yeah, I should have commented it. And, uh, so I had some experiments what was needed and what I, uh… What I tried and had some success is basically building all the… +- **16:37:16 · Dominik Kapusta:** Oh, okay. +- **16:37:20 · Alex Martemyanov:** all the corners in one run from the project, including the app and the runners, and then just distributing to the tester, to the runners. +- **16:37:23 · Dominik Kapusta:** Mm-hmm. +- **16:37:33 · Alex Martemyanov:** So there will be only some extra work needed to build the macOS 12 compatibility layer. It's also defined and sitting somewhere in my work trees. So basically, the project can stay as it is, and we don't need since… but we can build all together and just distribute it to every other macOS, and it works. +- **16:37:55 · Dominik Kapusta:** But… Is it? Okay. Interesting. But you're build… so what are you building? What would the… +- **16:38:06 · Alex Martemyanov:** the app and the runner, the UI test runner. +- **16:38:06 · Dominik Kapusta:** What do we build there? The app and the test run… okay, but the test runner would be a debug build. Like, ad hoc, signed, or unsigned? +- **16:38:16 · Alex Martemyanov:** Maybe. But I think… +- **16:38:19 · Dominik Kapusta:** I'm wondering about code signing and the ability to run this on a different machine. +- **16:38:23 · Alex Martemyanov:** I… I remember it did… it used to work, it just worked, but I didn't push it forward since then, so… +- **16:38:29 · Dominik Kapusta:** Okay, I mean, yeah, if it works for you, then that's great. I tried doing something like that some time ago. It was probably different. It was probably different. But it was, ah, it was a different thing. It was a different thing. It was copying derived data to runners. +- **16:38:58 · Alex Martemyanov:** Mm-hmm. +- **16:38:58 · Dominik Kapusta:** so that it could be reused. But that didn't work. +- **16:39:02 · Alex Martemyanov:** Okay. +- **16:39:08 · Dominik Kapusta:** Cool. Uh… +- **16:39:08 · Alex Martemyanov:** Sure. Do you have it by your hand, the task? +- **16:39:15 · Dominik Kapusta:** Oh, no, no, no, that was a long time ago, and I didn't have a task for that. That's when I was breaking down UI tests. +- **16:39:21 · Alex Martemyanov:** Mm-hmm. No, I mean… The, uh, the one about splitting the project. +- **16:39:25 · Dominik Kapusta:** What do you mean? +- **16:39:32 · Alex Martemyanov:** I'm just trying to find it. +- **16:39:32 · Dominik Kapusta:** No, I don't think… Well, let's see. +- **16:39:40 · Alex Martemyanov:** Thank you. Move, yeah, on it. I'll just probably post an update on it, that it's currently on pause, and uh… +- **16:39:50 · Dominik Kapusta:** Okay. Okay, okay, good. +- **16:39:53 · Alex Martemyanov:** And. I don't see her. If it's reasonable to move on with it. +- **16:40:11 · Dominik Kapusta:** The next thing we should talk about is the Apple Meetup. We don't have any… +- **16:40:15 · Alex Martemyanov:** Which is not gonna happen in Japan, as I understand. +- **16:40:19 · Dominik Kapusta:** Yeah, very unlikely. Well, I don't know anything. I haven't spoken to Jonathan. +- **16:40:22 · Alex Martemyanov:** Here. +- **16:40:27 · Dominik Kapusta:** And I expect Jonathan to say something about it in today's Apple Weekly. But… Yeah, it's unlikely to be Japan, or… Well, let's see, let's actually see, because… There's this discussion here, if you missed it. +- **16:40:49 · Alex Martemyanov:** Yeah, it's, you know, it's… +- **16:40:52 · Dominik Kapusta:** Meetup location guide. Hmm. Places that would work for you. I like Chile, Costa Rica again, Mexico. +- **16:41:16 · Alex Martemyanov:** It's Chris Harbour, I guess. +- **16:41:19 · Dominik Kapusta:** Mexico is what? Sorry, higher. Mm. +- **16:41:19 · Alex Martemyanov:** I've got this. Mexico is maybe problematic. +- **16:41:24 · Dominik Kapusta:** Ah, okay. +- **16:41:26 · Alex Martemyanov:** Um, not sure. They kinda have, uh… easier visa rules, seemingly easy visa rules, but I've heard there's a lot of rejections just in the airport that they just said, you're not going because of no explanations. So they are. +- **16:41:41 · Dominik Kapusta:** Oh, shit. Oh, that sucks. +- **16:41:46 · Alex Martemyanov:** experienced some problems with crimes, probably, or some Russia-related stuff, I don't know, but… +- **16:41:51 · Dominik Kapusta:** Mm-hmm. +- **16:41:56 · Alex Martemyanov:** There were some issues I've heard of. +- **16:41:56 · Dominik Kapusta:** No. Yeah, I am. +- **16:42:10 · Alex Martemyanov:** Yeah, it's done, yeah. Still not considered, although it's a really great place from my perspective. Mmm. Broadcasting… Uruguay, probably… And. And, uh… Ireland, Australia, UK, generally. So that's kind of there. But Canada, I don't know, maybe it may work. Speeds. Also may work, but they require extra… Extra movements to… +- **16:43:01 · Dominik Kapusta:** Okay. +- **16:43:02 · Alex Martemyanov:** Probably bizarre. And for… yeah, Egypt. Why not? +- **16:43:09 · Dominik Kapusta:** Egypt would be interesting. +- **16:43:12 · Alex Martemyanov:** Ah, it's not, it's not, it's not the place. It's the places where… +- **16:43:12 · Dominik Kapusta:** I haven't been there. Not on the list. Ah, okay. Yeah. +- **16:43:17 · Alex Martemyanov:** Yeah, our team leaves. Wrong location. Rome, Paris, London, Barcelona, Vienna… Europe, basically. +- **16:43:30 · Dominik Kapusta:** Mm-hmm, yeah, yeah. +- **16:43:32 · Alex Martemyanov:** I can give it another try, maybe. Who knows? Maybe because… Maybe France. So I've heard people are getting visas to France. +- **16:43:48 · Dominik Kapusta:** Yeah, yeah. +- **16:43:49 · Alex Martemyanov:** And anyways, you can get a visa for France, and then go to some other… country, or just have a flight to France first, and then move further. +- **16:43:55 · Dominik Kapusta:** That's right. That's right. +- **16:44:03 · Alex Martemyanov:** Correct, yeah, Spain, Sweden, Belgium, Portugal… It's basically all the… European cities. +- **16:44:14 · Dominik Kapusta:** Yeah, I think the first… The first that's not European is, well, New York City and then Playa del Carmen in Mexico. +- **16:44:26 · Alex Martemyanov:** Yeah, I guess, uh… New York could work better. But it's harder for me to… to fulfill all the paper paperwork for it. +- **16:44:37 · Dominik Kapusta:** Okay, I see. Well. +- **16:44:39 · Alex Martemyanov:** So, for Europe, it's just an easy application. I just have to go and apply for… get some bank statements and apply, but it's… +- **16:44:45 · Dominik Kapusta:** Yeah… +- **16:44:47 · Alex Martemyanov:** Would be a third reject in a row, maybe or maybe not. +- **16:44:50 · Dominik Kapusta:** Mm-hmm. Oh. +- **16:44:53 · Alex Martemyanov:** That's, you know, for New York, it's kind of more complicated. Including the flight. +- **16:45:01 · Dominik Kapusta:** You know. I'm really curious what will… come out of it because, yeah, it's interesting. It's just… Sounds… sounds bad that we have to sort of rule you out of every meetup every year, unless we go… To Costa Rica, like, 3 years ago, 2 years ago, uh… +- **16:45:35 · Alex Martemyanov:** Yeah, why not? +- **16:45:36 · Dominik Kapusta:** Why not? Yeah, I mean, we should do it. Let's see. Yeah, let's see, maybe we'll talk about it in the Apple Weekly, hopefully. All right, other than that, so to recap the call, perhaps… Unless… do you have anything else to talk about? +- **16:46:06 · Alex Martemyanov:** And… Well, I guess not. +- **16:46:09 · Dominik Kapusta:** Mm-hmm. +- **16:46:10 · Alex Martemyanov:** Should be… +- **16:46:12 · Dominik Kapusta:** Yeah, sure, sure, sure. Alright, uh… So… Yeah, so you're moving to OB, but you'll have to… Go through. Uh… And it looks like you have another project scheduled after this one. +- **16:46:33 · Alex Martemyanov:** Yeah, the, uh… It seems it's… +- **16:46:37 · Dominik Kapusta:** Stop. Stop. +- **16:46:37 · Alex Martemyanov:** consequent projects. +- **16:46:39 · Dominik Kapusta:** Stop iOS reload loops after tab memory kills. Which may be interesting… I mean, interesting, as in, uh, maybe straightforward, because we have the… Uh, we have that in macOS. To some extent, in some shape. It's, of course, different, but… At least there's a precedent. But it looks like you'll stick with OB until the end of the year, at least. And, uh… That's that, essentially. Umm. Fine. So if you could update the UI tests thingy, that would be great as well. And that's it, you're wrapping up your project, so… +- **16:47:37 · Alex Martemyanov:** Mmhm. +- **16:47:38 · Dominik Kapusta:** Probably not much time to work on AORs. But also, there's nothing burning over there. I mean, there is a burning thing in the CIA UR, and I'll have to rotate all GitHub Action secrets. Should be funny! Okay. Uh, yeah, so we can just… Wrap it up here, let's catch up again next week. And see how OB work is going. +- **16:48:06 · Alex Martemyanov:** Okay. Noted. Cool. +- **16:48:09 · Dominik Kapusta:** Cool. Yeah, I'll see you at the Apple Weekly. Thanks a lot, Alex. Have a great rest of the day. diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index ee0bf83b..2683c8ec 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -134,8 +134,8 @@ "note_modified_at": "2026-11-12T09:53:25.042Z", "source_url": "https://us01mynotes.zoom.us/DLwAbUQ_RZ6X_D63xiX_Ww", "folder": "undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww", - "sha256": "db809c761f4db97fd8b6f58235b80d896f8b4ac7886f3c495a4f396f3f875879", - "cues": 3 + "sha256": "a3436342699e9bdbbbf1071cd8c4e9189e3be8feb502df39b34ae20812cd2142", + "cues": 115 }, "VSuzeqZCR5O2z5KtmaQt3g": { "title": "Apple Weekly Team Meeting - Zoom ID", @@ -170,8 +170,8 @@ "note_modified_at": "2026-11-03T16:03:13.297Z", "source_url": "https://us01mynotes.zoom.us/e5TYWRytRz2WwWSe68BSWQ", "folder": "undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ", - "sha256": "0eef46a82d99e398a6e65a0f8d9b541a2def2faaa736e8eb187bbcf57c8f8552", - "cues": 3 + "sha256": "d84adb2acc1a8a258a69aa56146293ffd8b2f03613f6669679727a1d07165894", + "cues": 107 }, "3sv2crbiShun--0lAywwvg": { "title": "Alex Martemyanov's Zoom Meeting", @@ -374,8 +374,8 @@ "note_modified_at": "2026-11-17T10:09:04.028Z", "source_url": "https://us01mynotes.zoom.us/KcmYOq5_SQGPxdkdbhRx9A", "folder": "2026-11-17 Dominik Kapusta's Personal Meeting Room KcmYOq5_SQGPxdkdbhRx9A", - "sha256": "cdce4f852b434945d53f44b1f66ab533243bcda2c06687c7b3935661ab786a56", - "cues": 3 + "sha256": "5c109ab406cc31416901fa0074d845e38f8600045da5ba76945e879eea975b92", + "cues": 252 }, "GJhjFoDDRY6PkqEUdM-YFg": { "title": "Apple Weekly Team Meeting - Zoom ID", diff --git a/work/zoom-transcripts/sync-status.json b/work/zoom-transcripts/sync-status.json index 118ddd36..dee25a4c 100644 --- a/work/zoom-transcripts/sync-status.json +++ b/work/zoom-transcripts/sync-status.json @@ -1 +1 @@ -{"observed_at":"2026-11-19T09:09:36.979Z","scanned":31,"imported":3,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file +{"observed_at":"2026-11-19T09:40:55.331Z","scanned":31,"imported":3,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file diff --git a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json index 38585322..80874e3b 100644 --- a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json +++ b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.json @@ -23,6 +23,566 @@ "time": "15:55:00", "speaker": "Max Tsoy", "text": "Yes, but still, like, I would expect… it's… it's not… it's all breakage reports, right? So… Yes, it is filtered by people who report something, but it's still a signal and it's not related to what kind of breakage report it is." + }, + { + "time": "15:55:21", + "speaker": "Michal Smaga", + "text": "And you filter by the macOS version as well, right?" + }, + { + "time": "15:55:24", + "speaker": "Max Tsoy", + "text": "Um… I think so. Yes, it's a stacked thing. It's in the same… in the same… Dashboards. Uh, this one. Right, so, uh, it's hidden under CPM diagnostics. Role." + }, + { + "time": "15:55:51", + "speaker": "Alex Martemyanov", + "text": "Yeah, and just answered in your removed breakage diagnostic thread. And yeah, I basically asked Claude to check the breakages and related reports." + }, + { + "time": "15:55:51", + "speaker": "Max Tsoy", + "text": "That's what I… Mm-hmm. Oh. Okay. Good." + }, + { + "time": "15:56:06", + "speaker": "Alex Martemyanov", + "text": "So, it highlighted that, uh… The baseline is basically the same with the waiting signal, but there is a new report categories. Uh, that may be affecting, uh. that weighting metric and." + }, + { + "time": "15:56:24", + "speaker": "Max Tsoy", + "text": "Okay, so…" + }, + { + "time": "15:56:27", + "speaker": "Alex Martemyanov", + "text": "So…" + }, + { + "time": "15:56:27", + "speaker": "Max Tsoy", + "text": "So we… we got more reports?" + }, + { + "time": "15:56:29", + "speaker": "Alex Martemyanov", + "text": "if there is a report flow on the error page, uh, which basically has no, uh, CPM running on it, and we've been affected, uh, with it with the, uh, CPM breakage pixels as well, uh, because, uh, they're not run on determination and there are pages on macOS." + }, + { + "time": "15:56:37", + "speaker": "Max Tsoy", + "text": "Okay." + }, + { + "time": "15:56:47", + "speaker": "Alex Martemyanov", + "text": "And if we exclude the report flow for the error page, it stays steady basically. And answering your treatment effect question, yeah, basically it was not…" + }, + { + "time": "15:56:53", + "speaker": "Max Tsoy", + "text": "Okay, okay." + }, + { + "time": "15:57:02", + "speaker": "Alex Martemyanov", + "text": "lowering much, not affecting much the overall breakage signal magic." + }, + { + "time": "15:57:08", + "speaker": "Max Tsoy", + "text": "Mm-hmm. Okay, so…" + }, + { + "time": "15:57:10", + "speaker": "Alex Martemyanov", + "text": "Because the main signal still stays in the seemingly normal flow as the metrics shown." + }, + { + "time": "15:57:17", + "speaker": "Max Tsoy", + "text": "Right. Okay, so basically, the increase is probably driven by something else, but there was no decrease either. Um…" + }, + { + "time": "15:57:30", + "speaker": "Alex Martemyanov", + "text": "There was a… Probably less than a percent decrease and there's still fluctuation depending on a week measured, so we can tell for sure." + }, + { + "time": "15:57:34", + "speaker": "Max Tsoy", + "text": "Yeah, yeah. Okay. Got it. Okay, so, uh, uh, alright, now, uh, I'm looking at your tech design, and my main question there is, do we… Do we not already have this? Because… so the tech design is basically proposing to send more, like, status reports from the extension." + }, + { + "time": "15:58:04", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "15:58:05", + "speaker": "Max Tsoy", + "text": "But we already have one signal, which is exactly the same thing, actually. So, if you look at this old… that design. that introduced that… other signal. So, the CPM dashboard state… Uh, specifically. Um… So basically, immediately after navigation, we set the CPM dashboard state to waiting in native code. And then… The first thing that… The extension does. After it gets… after it injects the content script. it's… initializes, and then… Almost immediately sends back the refresh CPM dashboard state. So… The problem is that. In the error state, this message is not received. So… Like, what you're proposing there… I think you will just not receive. Most of these messages. And that's the whole point of problem, right? So, like. Um… I don't think it's a problem of the granularity. It's basically that in this error state, we don't get. Any response?" + }, + { + "time": "15:59:37", + "speaker": "Alex Martemyanov", + "text": "Mmhm." + }, + { + "time": "15:59:37", + "speaker": "Max Tsoy", + "text": "So, it kind of looks like the messaging is broken. And that's the whole reason, right? Like, we don't know what's happening. Is the extension stuck? Is it just the messaging that doesn't get through, or is it the… You know, the whole… Thing doesn't work." + }, + { + "time": "15:59:55", + "speaker": "Alex Martemyanov", + "text": "I think it was mainly based on the, um… In the state that may be pending before we send the… The repair is unmarked state. Like, uh, for example, the config, uh, the config update state." + }, + { + "time": "16:00:09", + "speaker": "Max Tsoy", + "text": "Right." + }, + { + "time": "16:00:14", + "speaker": "Alex Martemyanov", + "text": "or. And. What else was there? Let me just open it." + }, + { + "time": "16:00:21", + "speaker": "Max Tsoy", + "text": "Right, so basically you're suggesting that within that initialization, maybe it gets stuck. In between these first… so, what we could do…" + }, + { + "time": "16:00:28", + "speaker": "Alex Martemyanov", + "text": "Yes, yes." + }, + { + "time": "16:00:32", + "speaker": "Max Tsoy", + "text": "We could just send one message. Immediately, like, on… On wake up. And I think we actually already do. Uh, don't we, like, there is some… I don't know, um, I don't remember exactly, but the… I think there was… so… What I'm saying is that I don't know if the, uh, all these other stages are… Um… useful, because I think it… the problem is that we… I suspect we won't get the first message, even." + }, + { + "time": "16:01:07", + "speaker": "Alex Martemyanov", + "text": "Maybe, but… Probably we don't know." + }, + { + "time": "16:01:15", + "speaker": "Max Tsoy", + "text": "So we have this… the first…" + }, + { + "time": "16:01:15", + "speaker": "Alex Martemyanov", + "text": "So here we kind of add no wait, so there is no await, it's kind of asynchronously as soon as we…" + }, + { + "time": "16:01:24", + "speaker": "Max Tsoy", + "text": "Mm-hmm." + }, + { + "time": "16:01:26", + "speaker": "Alex Martemyanov", + "text": "Wake of the script wakes. Unless so first. Yeah, so there is the stage for, like, no, nothing was received, then, uh… H script in it. There may be possible hang on the config read, and if it hangs for whatever reason, it won't get through and won't get to the dashboard update state. Uh, so the suggestion is, like, sending, uh… And… log messages to… To set the list. Received state. that we could report in the main CPM breakage pixel." + }, + { + "time": "16:02:15", + "speaker": "Max Tsoy", + "text": "Yeah, um…" + }, + { + "time": "16:02:16", + "speaker": "Alex Martemyanov", + "text": "I see." + }, + { + "time": "16:02:18", + "speaker": "Max Tsoy", + "text": "Well, then I would… I would suggest just to trim it down to, like, the very first. signal, because… Um, I think for the rest, we actually… we have some… We have the CPM stage thing, right? Which is kind of… the same. Um… So, the last tech design that they shared? Um, there is this, yeah." + }, + { + "time": "16:02:48", + "speaker": "Michal Smaga", + "text": "Yeah, Max, just to clarify, I'm not up to date because, like, I'm still catching up after yesterday, so I haven't read the new tech design." + }, + { + "time": "16:02:53", + "speaker": "Max Tsoy", + "text": "Yeah." + }, + { + "time": "16:02:55", + "speaker": "Michal Smaga", + "text": "But, the goal is to, like, remove the old metrics like that, that were, like, very detailed and, like, very precise. Get rid of that just because of privacy reasons and, like, to implement the new ones." + }, + { + "time": "16:03:01", + "speaker": "Max Tsoy", + "text": "Mm-hmm, mm-hmm." + }, + { + "time": "16:03:04", + "speaker": "Alex Martemyanov", + "text": "Sweet. We may be not at the same page because I've just opened another tech design I wanted to discuss. And, uh, yes, so basically, uh, I suggest to remove, uh, all the old metrics and, uh, this recorder thing, and, uh, delegate, uh, proxy." + }, + { + "time": "16:03:24", + "speaker": "Max Tsoy", + "text": "Okay." + }, + { + "time": "16:03:28", + "speaker": "Alex Martemyanov", + "text": "And basically the only basic metric that would relate page committed state to the dashboard update." + }, + { + "time": "16:03:37", + "speaker": "Max Tsoy", + "text": "Mm-hmm, mm-h." + }, + { + "time": "16:03:38", + "speaker": "Alex Martemyanov", + "text": "Uh, message. So if we don't receive it within, uh, 30 seconds, uh, we…" + }, + { + "time": "16:03:45", + "speaker": "Michal Smaga", + "text": "Record the stacks that you want." + }, + { + "time": "16:03:45", + "speaker": "Alex Martemyanov", + "text": "So we expect to receive it. Yeah, but… before we navigate to another page, or before we close this tab. And if the page was alive for longer than 30 seconds, so basically it was measured, there were some cases when the dashboard update received after 30 seconds." + }, + { + "time": "16:04:01", + "speaker": "Max Tsoy", + "text": "Mm-hmm." + }, + { + "time": "16:04:06", + "speaker": "Alex Martemyanov", + "text": "It's for loading, because of, um… getting load, or whatever. And, uh, so if we navigate from the page, and, uh, it never received, uh, anything, and the page was active more than 30 seconds, we send a metric of the page of CPM hand. And if it was, uh, caught on another job." + }, + { + "time": "16:04:22", + "speaker": "Max Tsoy", + "text": "Mm-hmm." + }, + { + "time": "16:04:27", + "speaker": "Alex Martemyanov", + "text": "After it, we send the permanent breakage." + }, + { + "time": "16:04:28", + "speaker": "Max Tsoy", + "text": "Right." + }, + { + "time": "16:04:31", + "speaker": "Alex Martemyanov", + "text": "There was another issue of matching tab against actual… web extension tab against actual tab that we are measuring, because if we open the same page in two tabs, it basically can match both. Ahm. there is the tab index, and there is window ID that we cannot access from the app itself, but there is, like, a heuristics that allow us match it if we send all the window IDs. Um, so WebKit gives the window an ID in, uh… Consequently, it's not zero-based. It may be like 44, 72, and so on, but they are always ordered consequently as they are received from the app itself. And if we send these IDs from the script, we can match exact window and exact tab that the message is meant for." + }, + { + "time": "16:05:32", + "speaker": "Max Tsoy", + "text": "Wait, wait, sorry, are you saying, uh… Are you saying we can match… we can map the extension tab ID to the native tab ID?" + }, + { + "time": "16:05:39", + "speaker": "Alex Martemyanov", + "text": "Yes. Yes. Yes." + }, + { + "time": "16:05:43", + "speaker": "Max Tsoy", + "text": "Oh, that's a, that's a great thing. I, uh, I." + }, + { + "time": "16:05:45", + "speaker": "Alex Martemyanov", + "text": "So I was breaking my head the last three days on how could we actually match it to…" + }, + { + "time": "16:05:45", + "speaker": "Michal Smaga", + "text": "Yeah, we…" + }, + { + "time": "16:05:52", + "speaker": "Alex Martemyanov", + "text": "To avoid, uh, false positives." + }, + { + "time": "16:05:52", + "speaker": "Max Tsoy", + "text": "We have a separate, like. Separate tests somewhere we have that, uh… But how would it work in a nutshell again?" + }, + { + "time": "16:06:00", + "speaker": "Alex Martemyanov", + "text": "Yeah, basically we have a tab index that we set for the tab in the window." + }, + { + "time": "16:06:07", + "speaker": "Max Tsoy", + "text": "Yes." + }, + { + "time": "16:06:08", + "speaker": "Alex Martemyanov", + "text": "Oh, it's, uh…" + }, + { + "time": "16:06:09", + "speaker": "Max Tsoy", + "text": "Huh?" + }, + { + "time": "16:06:11", + "speaker": "Michal Smaga", + "text": "A native one." + }, + { + "time": "16:06:13", + "speaker": "Alex Martemyanov", + "text": "the tab collection index. So it's not tab ID, but tab index. And we can send… we also have this tab index in the extension." + }, + { + "time": "16:06:19", + "speaker": "Max Tsoy", + "text": "Okay." + }, + { + "time": "16:06:25", + "speaker": "Alex Martemyanov", + "text": "And we don't need tab ID in that case. And it would just work on iOS, because we only have one window on iOS. But on macOS, there is another complication. If we open exact two windows with exact the same tab URLs in the same order." + }, + { + "time": "16:06:33", + "speaker": "Max Tsoy", + "text": "Right, right." + }, + { + "time": "16:06:41", + "speaker": "Alex Martemyanov", + "text": "There is a corner case that we cannot match it. But the window enumeration goes with the groan counter in the webkit. So it's not zero based, so it's not consequent. But it is growing." + }, + { + "time": "16:07:01", + "speaker": "Max Tsoy", + "text": "Okay, uh, can you…" + }, + { + "time": "16:07:02", + "speaker": "Alex Martemyanov", + "text": "So, a web extension window ID could be…" + }, + { + "time": "16:07:04", + "speaker": "Max Tsoy", + "text": "Can you drop some message in this stack design, then? Because this is the…" + }, + { + "time": "16:07:09", + "speaker": "Alex Martemyanov", + "text": "Both." + }, + { + "time": "16:07:09", + "speaker": "Max Tsoy", + "text": "I think we considered this to… There, um…" + }, + { + "time": "16:07:14", + "speaker": "Alex Martemyanov", + "text": "So basically the idea is to have another growing counter from the native side. And whenever we return a window, an extension window from the app, we grow the counter. So we will have window IDs starting like this. 1, 2, 3, and so on. And from WebKit, we would have IDs like 44, 72, 99, and so on. But there will be always two arrays of the matching size, and the sequence would match. So here we can match exactly window ID. from web extension and window ID that we gave it." + }, + { + "time": "16:07:47", + "speaker": "Max Tsoy", + "text": "Okay. Um… Yes, I mean, I'm not, like, following 100%, but I think it… I mean, if there is a way, I would like, uh, if you can read that, uh, that tech design." + }, + { + "time": "16:08:06", + "speaker": "Alex Martemyanov", + "text": "Okay, I will post an update there." + }, + { + "time": "16:08:06", + "speaker": "Max Tsoy", + "text": "just see if… because I know we… I see we actually did consider, like, the indexes and stuff, but. Um, uh, yeah, just like consider if as long as all of these are also, um, considered, I think whatever. We can do to map it, it will really help, because it's also… it's a problem for other reasons as well, right? Because now we're just matched by this, like, domains, and it's just messy. Um…" + }, + { + "time": "16:08:32", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "16:08:38", + "speaker": "Max Tsoy", + "text": "Anyways, okay, so, but to the, um… Uh, do this, uh, metrics thing, right? So, I… I will look at it later. Right now. It sounds like the, uh, tech design from, uh, your tech design sounds, like, very similar to what we already have, the CPM stage parameter. Which is already there, and we didn't plan to remove it. Uh, so I will need to check that. Um, and the second… Uh, one is… so this other… tasks, the… remove temporary CPM breakage diagnostics. So it's assigned to me now. I don't know if it makes sense for you to cover that too. Or, uh, I should do, because some of it is an extension. Um… Because if your goal is to clean up the old metrics and make permanent ones. Maybe that's also… but it's okay, I mean, if… I can also do that. That's no problem." + }, + { + "time": "16:09:49", + "speaker": "Alex Martemyanov", + "text": "I mean, I only wanted to validate the direction. There is one tech design for you for the need stage. I will check what you suggested. Another one is mostly for Michal, I guess." + }, + { + "time": "16:09:55", + "speaker": "Max Tsoy", + "text": "Yeah." + }, + { + "time": "16:10:05", + "speaker": "Alex Martemyanov", + "text": "But I just wanted to sync up with you both, so we have… Okay. the shared understanding of, uh, the remaining stages. So what I'll suggest is basically removing, uh, the fixes that didn't work out." + }, + { + "time": "16:10:21", + "speaker": "Max Tsoy", + "text": "Mm-hmm." + }, + { + "time": "16:10:21", + "speaker": "Alex Martemyanov", + "text": "We will keep updates on launch, base, stable base URLs restart after error six. But the ones that didn't appear in the metrics are just removed. I think it's kind of an obvious decision." + }, + { + "time": "16:10:37", + "speaker": "Max Tsoy", + "text": "Mm-hmm. Mm-hmm." + }, + { + "time": "16:10:40", + "speaker": "Alex Martemyanov", + "text": "And, uh, the next pull request, it just cleans up. all the metrics, so mostly on all the metrics that, uh, were added. And, uh, the next one would be re-adding based on some stabilized, uh, algorithms. So basically, we… rely on the sub or web page lifecycle, and if it didn't receive a CPM signal, we will report the breakage. So it should be that easy and nothing else gets connected." + }, + { + "time": "16:11:10", + "speaker": "Max Tsoy", + "text": "Yes." + }, + { + "time": "16:11:16", + "speaker": "Alex Martemyanov", + "text": "And it would be just a permanent metric that could give us understanding of where the trend going, but no reason." + }, + { + "time": "16:11:16", + "speaker": "Max Tsoy", + "text": "Okay. Yep. Okay, so, so, so far, basically, what I'm hearing is that. Um… you want to implement the same thing as we have this CPM stage, but it will be a metric for all page loads, not just for, um, uh, breakage reports. Which is… good." + }, + { + "time": "16:11:41", + "speaker": "Alex Martemyanov", + "text": "Uh, yes, uh, for all page loads, like a permanent metric, and uh…" + }, + { + "time": "16:11:44", + "speaker": "Max Tsoy", + "text": "Yep." + }, + { + "time": "16:11:46", + "speaker": "Alex Martemyanov", + "text": "So the init stage, it's kind of an extra mile for this effort just to. get an understanding of where it breaks. So it's not related, it's like another…" + }, + { + "time": "16:11:56", + "speaker": "Max Tsoy", + "text": "Okay." + }, + { + "time": "16:12:00", + "speaker": "Alex Martemyanov", + "text": "Extra magic." + }, + { + "time": "16:12:01", + "speaker": "Max Tsoy", + "text": "Okay, so basically it's optional, this step design for the web extension lifecycle metrics." + }, + { + "time": "16:12:02", + "speaker": "Alex Martemyanov", + "text": "Temporary. Yes." + }, + { + "time": "16:12:08", + "speaker": "Max Tsoy", + "text": "Okay. Um… my first… my first reaction is that, like, why do we reinvent and, like, why don't we just reuse the same? thing, because the extension already sends the CPM stage, and we could just wire it up. So it doesn't just… so it's reported. also outside breakage reports. Um, but I haven't seen… haven't looked into the actual values, like… on the first glance, it looks the same. To me. Um, and then…" + }, + { + "time": "16:12:42", + "speaker": "Alex Martemyanov", + "text": "Okay, I'll check and let you know." + }, + { + "time": "16:12:44", + "speaker": "Max Tsoy", + "text": "Yeah, you can check that. Uh, and… Yeah, I will try to get back to you today. I'm a little tied up because we have the, uh, assessment today, and I need to… Sorry for that, but, um… I hope it's not blocking you too much." + }, + { + "time": "16:13:04", + "speaker": "Alex Martemyanov", + "text": "Okay, no problem. I hope we can… get through it before Tuesday or Thursday." + }, + { + "time": "16:13:14", + "speaker": "Max Tsoy", + "text": "Uh, no, but definitely before, before Tuesday, uh, I, uh, it's, like, today or tomorrow, we can resolve it, I'm sure." + }, + { + "time": "16:13:22", + "speaker": "Alex Martemyanov", + "text": "Yep. That works." + }, + { + "time": "16:13:25", + "speaker": "Max Tsoy", + "text": "Mm-hmm." + }, + { + "time": "16:13:26", + "speaker": "Alex Martemyanov", + "text": "Okay, thanks. Then I'll give you an update async." + }, + { + "time": "16:13:28", + "speaker": "Max Tsoy", + "text": "Right. Good route." + }, + { + "time": "16:13:30", + "speaker": "Michal Smaga", + "text": "Alex, can you stay for a moment?" + }, + { + "time": "16:13:32", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "16:13:34", + "speaker": "Max Tsoy", + "text": "Uh, let's see if I can leave without…" + }, + { + "time": "16:13:37", + "speaker": "Michal Smaga", + "text": "Okay, so we can…" + }, + { + "time": "16:13:39", + "speaker": "Max Tsoy", + "text": "No, I can, I can, I can…" } ] } diff --git a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md index 87629411..a1d8b507 100644 --- a/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md +++ b/work/zoom-transcripts/undated Max Tsoy's Personal Meeting Room DLwAbUQ_RZ6X_D63xiX_Ww/transcript.md @@ -15,3 +15,115 @@ source: "https://us01mynotes.zoom.us/DLwAbUQ_RZ6X_D63xiX_Ww" - **15:53:25 · Max Tsoy:** Yeah, so I only have a few minutes, but, like, I have this question I asked about this dashboard yesterday. So, I don't understand… So, basically… We, uh, before this project, right, I made this, uh, this, uh, dashboard. With the… which was tracking this, uh, side effect. That kind of correlated with the error rate. And, uh, so we have this signal that shows. That at least one message was received from the extension, basically. Right. And it turned out that, like, I think it was, like, 10% of macOS breakage reports. Did not receive any message from the extension. So, which kind of meant that the… something was stuck. And I think that… that was the… Before this project, that was the best indicator of the problem. Right now, I'm looking at that dashboard, and I see that this… that signal only went up. on macOS. Uh, so… I don't understand, is it still relevant, or… do we, uh… I know we didn't look at it, but, like… Um… I'm not sure what it tells us. Does it actually mean that we didn't move anything, or… - **15:54:54 · Michal Smaga:** Yeah. But the question is, like, the the signal is only for the braggage reports. Right? - **15:55:00 · Max Tsoy:** Yes, but still, like, I would expect… it's… it's not… it's all breakage reports, right? So… Yes, it is filtered by people who report something, but it's still a signal and it's not related to what kind of breakage report it is. +- **15:55:21 · Michal Smaga:** And you filter by the macOS version as well, right? +- **15:55:24 · Max Tsoy:** Um… I think so. Yes, it's a stacked thing. It's in the same… in the same… Dashboards. Uh, this one. Right, so, uh, it's hidden under CPM diagnostics. Role. +- **15:55:51 · Alex Martemyanov:** Yeah, and just answered in your removed breakage diagnostic thread. And yeah, I basically asked Claude to check the breakages and related reports. +- **15:55:51 · Max Tsoy:** That's what I… Mm-hmm. Oh. Okay. Good. +- **15:56:06 · Alex Martemyanov:** So, it highlighted that, uh… The baseline is basically the same with the waiting signal, but there is a new report categories. Uh, that may be affecting, uh. that weighting metric and. +- **15:56:24 · Max Tsoy:** Okay, so… +- **15:56:27 · Alex Martemyanov:** So… +- **15:56:27 · Max Tsoy:** So we… we got more reports? +- **15:56:29 · Alex Martemyanov:** if there is a report flow on the error page, uh, which basically has no, uh, CPM running on it, and we've been affected, uh, with it with the, uh, CPM breakage pixels as well, uh, because, uh, they're not run on determination and there are pages on macOS. +- **15:56:37 · Max Tsoy:** Okay. +- **15:56:47 · Alex Martemyanov:** And if we exclude the report flow for the error page, it stays steady basically. And answering your treatment effect question, yeah, basically it was not… +- **15:56:53 · Max Tsoy:** Okay, okay. +- **15:57:02 · Alex Martemyanov:** lowering much, not affecting much the overall breakage signal magic. +- **15:57:08 · Max Tsoy:** Mm-hmm. Okay, so… +- **15:57:10 · Alex Martemyanov:** Because the main signal still stays in the seemingly normal flow as the metrics shown. +- **15:57:17 · Max Tsoy:** Right. Okay, so basically, the increase is probably driven by something else, but there was no decrease either. Um… +- **15:57:30 · Alex Martemyanov:** There was a… Probably less than a percent decrease and there's still fluctuation depending on a week measured, so we can tell for sure. +- **15:57:34 · Max Tsoy:** Yeah, yeah. Okay. Got it. Okay, so, uh, uh, alright, now, uh, I'm looking at your tech design, and my main question there is, do we… Do we not already have this? Because… so the tech design is basically proposing to send more, like, status reports from the extension. +- **15:58:04 · Alex Martemyanov:** Yep. +- **15:58:05 · Max Tsoy:** But we already have one signal, which is exactly the same thing, actually. So, if you look at this old… that design. that introduced that… other signal. So, the CPM dashboard state… Uh, specifically. Um… So basically, immediately after navigation, we set the CPM dashboard state to waiting in native code. And then… The first thing that… The extension does. After it gets… after it injects the content script. it's… initializes, and then… Almost immediately sends back the refresh CPM dashboard state. So… The problem is that. In the error state, this message is not received. So… Like, what you're proposing there… I think you will just not receive. Most of these messages. And that's the whole point of problem, right? So, like. Um… I don't think it's a problem of the granularity. It's basically that in this error state, we don't get. Any response? +- **15:59:37 · Alex Martemyanov:** Mmhm. +- **15:59:37 · Max Tsoy:** So, it kind of looks like the messaging is broken. And that's the whole reason, right? Like, we don't know what's happening. Is the extension stuck? Is it just the messaging that doesn't get through, or is it the… You know, the whole… Thing doesn't work. +- **15:59:55 · Alex Martemyanov:** I think it was mainly based on the, um… In the state that may be pending before we send the… The repair is unmarked state. Like, uh, for example, the config, uh, the config update state. +- **16:00:09 · Max Tsoy:** Right. +- **16:00:14 · Alex Martemyanov:** or. And. What else was there? Let me just open it. +- **16:00:21 · Max Tsoy:** Right, so basically you're suggesting that within that initialization, maybe it gets stuck. In between these first… so, what we could do… +- **16:00:28 · Alex Martemyanov:** Yes, yes. +- **16:00:32 · Max Tsoy:** We could just send one message. Immediately, like, on… On wake up. And I think we actually already do. Uh, don't we, like, there is some… I don't know, um, I don't remember exactly, but the… I think there was… so… What I'm saying is that I don't know if the, uh, all these other stages are… Um… useful, because I think it… the problem is that we… I suspect we won't get the first message, even. +- **16:01:07 · Alex Martemyanov:** Maybe, but… Probably we don't know. +- **16:01:15 · Max Tsoy:** So we have this… the first… +- **16:01:15 · Alex Martemyanov:** So here we kind of add no wait, so there is no await, it's kind of asynchronously as soon as we… +- **16:01:24 · Max Tsoy:** Mm-hmm. +- **16:01:26 · Alex Martemyanov:** Wake of the script wakes. Unless so first. Yeah, so there is the stage for, like, no, nothing was received, then, uh… H script in it. There may be possible hang on the config read, and if it hangs for whatever reason, it won't get through and won't get to the dashboard update state. Uh, so the suggestion is, like, sending, uh… And… log messages to… To set the list. Received state. that we could report in the main CPM breakage pixel. +- **16:02:15 · Max Tsoy:** Yeah, um… +- **16:02:16 · Alex Martemyanov:** I see. +- **16:02:18 · Max Tsoy:** Well, then I would… I would suggest just to trim it down to, like, the very first. signal, because… Um, I think for the rest, we actually… we have some… We have the CPM stage thing, right? Which is kind of… the same. Um… So, the last tech design that they shared? Um, there is this, yeah. +- **16:02:48 · Michal Smaga:** Yeah, Max, just to clarify, I'm not up to date because, like, I'm still catching up after yesterday, so I haven't read the new tech design. +- **16:02:53 · Max Tsoy:** Yeah. +- **16:02:55 · Michal Smaga:** But, the goal is to, like, remove the old metrics like that, that were, like, very detailed and, like, very precise. Get rid of that just because of privacy reasons and, like, to implement the new ones. +- **16:03:01 · Max Tsoy:** Mm-hmm, mm-hmm. +- **16:03:04 · Alex Martemyanov:** Sweet. We may be not at the same page because I've just opened another tech design I wanted to discuss. And, uh, yes, so basically, uh, I suggest to remove, uh, all the old metrics and, uh, this recorder thing, and, uh, delegate, uh, proxy. +- **16:03:24 · Max Tsoy:** Okay. +- **16:03:28 · Alex Martemyanov:** And basically the only basic metric that would relate page committed state to the dashboard update. +- **16:03:37 · Max Tsoy:** Mm-hmm, mm-h. +- **16:03:38 · Alex Martemyanov:** Uh, message. So if we don't receive it within, uh, 30 seconds, uh, we… +- **16:03:45 · Michal Smaga:** Record the stacks that you want. +- **16:03:45 · Alex Martemyanov:** So we expect to receive it. Yeah, but… before we navigate to another page, or before we close this tab. And if the page was alive for longer than 30 seconds, so basically it was measured, there were some cases when the dashboard update received after 30 seconds. +- **16:04:01 · Max Tsoy:** Mm-hmm. +- **16:04:06 · Alex Martemyanov:** It's for loading, because of, um… getting load, or whatever. And, uh, so if we navigate from the page, and, uh, it never received, uh, anything, and the page was active more than 30 seconds, we send a metric of the page of CPM hand. And if it was, uh, caught on another job. +- **16:04:22 · Max Tsoy:** Mm-hmm. +- **16:04:27 · Alex Martemyanov:** After it, we send the permanent breakage. +- **16:04:28 · Max Tsoy:** Right. +- **16:04:31 · Alex Martemyanov:** There was another issue of matching tab against actual… web extension tab against actual tab that we are measuring, because if we open the same page in two tabs, it basically can match both. Ahm. there is the tab index, and there is window ID that we cannot access from the app itself, but there is, like, a heuristics that allow us match it if we send all the window IDs. Um, so WebKit gives the window an ID in, uh… Consequently, it's not zero-based. It may be like 44, 72, and so on, but they are always ordered consequently as they are received from the app itself. And if we send these IDs from the script, we can match exact window and exact tab that the message is meant for. +- **16:05:32 · Max Tsoy:** Wait, wait, sorry, are you saying, uh… Are you saying we can match… we can map the extension tab ID to the native tab ID? +- **16:05:39 · Alex Martemyanov:** Yes. Yes. Yes. +- **16:05:43 · Max Tsoy:** Oh, that's a, that's a great thing. I, uh, I. +- **16:05:45 · Alex Martemyanov:** So I was breaking my head the last three days on how could we actually match it to… +- **16:05:45 · Michal Smaga:** Yeah, we… +- **16:05:52 · Alex Martemyanov:** To avoid, uh, false positives. +- **16:05:52 · Max Tsoy:** We have a separate, like. Separate tests somewhere we have that, uh… But how would it work in a nutshell again? +- **16:06:00 · Alex Martemyanov:** Yeah, basically we have a tab index that we set for the tab in the window. +- **16:06:07 · Max Tsoy:** Yes. +- **16:06:08 · Alex Martemyanov:** Oh, it's, uh… +- **16:06:09 · Max Tsoy:** Huh? +- **16:06:11 · Michal Smaga:** A native one. +- **16:06:13 · Alex Martemyanov:** the tab collection index. So it's not tab ID, but tab index. And we can send… we also have this tab index in the extension. +- **16:06:19 · Max Tsoy:** Okay. +- **16:06:25 · Alex Martemyanov:** And we don't need tab ID in that case. And it would just work on iOS, because we only have one window on iOS. But on macOS, there is another complication. If we open exact two windows with exact the same tab URLs in the same order. +- **16:06:33 · Max Tsoy:** Right, right. +- **16:06:41 · Alex Martemyanov:** There is a corner case that we cannot match it. But the window enumeration goes with the groan counter in the webkit. So it's not zero based, so it's not consequent. But it is growing. +- **16:07:01 · Max Tsoy:** Okay, uh, can you… +- **16:07:02 · Alex Martemyanov:** So, a web extension window ID could be… +- **16:07:04 · Max Tsoy:** Can you drop some message in this stack design, then? Because this is the… +- **16:07:09 · Alex Martemyanov:** Both. +- **16:07:09 · Max Tsoy:** I think we considered this to… There, um… +- **16:07:14 · Alex Martemyanov:** So basically the idea is to have another growing counter from the native side. And whenever we return a window, an extension window from the app, we grow the counter. So we will have window IDs starting like this. 1, 2, 3, and so on. And from WebKit, we would have IDs like 44, 72, 99, and so on. But there will be always two arrays of the matching size, and the sequence would match. So here we can match exactly window ID. from web extension and window ID that we gave it. +- **16:07:47 · Max Tsoy:** Okay. Um… Yes, I mean, I'm not, like, following 100%, but I think it… I mean, if there is a way, I would like, uh, if you can read that, uh, that tech design. +- **16:08:06 · Alex Martemyanov:** Okay, I will post an update there. +- **16:08:06 · Max Tsoy:** just see if… because I know we… I see we actually did consider, like, the indexes and stuff, but. Um, uh, yeah, just like consider if as long as all of these are also, um, considered, I think whatever. We can do to map it, it will really help, because it's also… it's a problem for other reasons as well, right? Because now we're just matched by this, like, domains, and it's just messy. Um… +- **16:08:32 · Alex Martemyanov:** Yep. +- **16:08:38 · Max Tsoy:** Anyways, okay, so, but to the, um… Uh, do this, uh, metrics thing, right? So, I… I will look at it later. Right now. It sounds like the, uh, tech design from, uh, your tech design sounds, like, very similar to what we already have, the CPM stage parameter. Which is already there, and we didn't plan to remove it. Uh, so I will need to check that. Um, and the second… Uh, one is… so this other… tasks, the… remove temporary CPM breakage diagnostics. So it's assigned to me now. I don't know if it makes sense for you to cover that too. Or, uh, I should do, because some of it is an extension. Um… Because if your goal is to clean up the old metrics and make permanent ones. Maybe that's also… but it's okay, I mean, if… I can also do that. That's no problem. +- **16:09:49 · Alex Martemyanov:** I mean, I only wanted to validate the direction. There is one tech design for you for the need stage. I will check what you suggested. Another one is mostly for Michal, I guess. +- **16:09:55 · Max Tsoy:** Yeah. +- **16:10:05 · Alex Martemyanov:** But I just wanted to sync up with you both, so we have… Okay. the shared understanding of, uh, the remaining stages. So what I'll suggest is basically removing, uh, the fixes that didn't work out. +- **16:10:21 · Max Tsoy:** Mm-hmm. +- **16:10:21 · Alex Martemyanov:** We will keep updates on launch, base, stable base URLs restart after error six. But the ones that didn't appear in the metrics are just removed. I think it's kind of an obvious decision. +- **16:10:37 · Max Tsoy:** Mm-hmm. Mm-hmm. +- **16:10:40 · Alex Martemyanov:** And, uh, the next pull request, it just cleans up. all the metrics, so mostly on all the metrics that, uh, were added. And, uh, the next one would be re-adding based on some stabilized, uh, algorithms. So basically, we… rely on the sub or web page lifecycle, and if it didn't receive a CPM signal, we will report the breakage. So it should be that easy and nothing else gets connected. +- **16:11:10 · Max Tsoy:** Yes. +- **16:11:16 · Alex Martemyanov:** And it would be just a permanent metric that could give us understanding of where the trend going, but no reason. +- **16:11:16 · Max Tsoy:** Okay. Yep. Okay, so, so, so far, basically, what I'm hearing is that. Um… you want to implement the same thing as we have this CPM stage, but it will be a metric for all page loads, not just for, um, uh, breakage reports. Which is… good. +- **16:11:41 · Alex Martemyanov:** Uh, yes, uh, for all page loads, like a permanent metric, and uh… +- **16:11:44 · Max Tsoy:** Yep. +- **16:11:46 · Alex Martemyanov:** So the init stage, it's kind of an extra mile for this effort just to. get an understanding of where it breaks. So it's not related, it's like another… +- **16:11:56 · Max Tsoy:** Okay. +- **16:12:00 · Alex Martemyanov:** Extra magic. +- **16:12:01 · Max Tsoy:** Okay, so basically it's optional, this step design for the web extension lifecycle metrics. +- **16:12:02 · Alex Martemyanov:** Temporary. Yes. +- **16:12:08 · Max Tsoy:** Okay. Um… my first… my first reaction is that, like, why do we reinvent and, like, why don't we just reuse the same? thing, because the extension already sends the CPM stage, and we could just wire it up. So it doesn't just… so it's reported. also outside breakage reports. Um, but I haven't seen… haven't looked into the actual values, like… on the first glance, it looks the same. To me. Um, and then… +- **16:12:42 · Alex Martemyanov:** Okay, I'll check and let you know. +- **16:12:44 · Max Tsoy:** Yeah, you can check that. Uh, and… Yeah, I will try to get back to you today. I'm a little tied up because we have the, uh, assessment today, and I need to… Sorry for that, but, um… I hope it's not blocking you too much. +- **16:13:04 · Alex Martemyanov:** Okay, no problem. I hope we can… get through it before Tuesday or Thursday. +- **16:13:14 · Max Tsoy:** Uh, no, but definitely before, before Tuesday, uh, I, uh, it's, like, today or tomorrow, we can resolve it, I'm sure. +- **16:13:22 · Alex Martemyanov:** Yep. That works. +- **16:13:25 · Max Tsoy:** Mm-hmm. +- **16:13:26 · Alex Martemyanov:** Okay, thanks. Then I'll give you an update async. +- **16:13:28 · Max Tsoy:** Right. Good route. +- **16:13:30 · Michal Smaga:** Alex, can you stay for a moment? +- **16:13:32 · Alex Martemyanov:** Yep. +- **16:13:34 · Max Tsoy:** Uh, let's see if I can leave without… +- **16:13:37 · Michal Smaga:** Okay, so we can… +- **16:13:39 · Max Tsoy:** No, I can, I can, I can… diff --git a/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.json b/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.json index 9a6da476..4253d925 100644 --- a/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.json +++ b/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.json @@ -23,6 +23,526 @@ "time": "22:05:00", "speaker": "russell holt", "text": "Can you explain NPS, Francis? It's Net Promoter something or other." + }, + { + "time": "22:05:02", + "speaker": "FD", + "text": "And he had to. Yeah, net promoter score. So it's basically a a signal of loyalty. So it's basically saying how likely would you recommend this product to a friend? And… And so it's like a… It's like a substitute for retention, basically. Um, yeah, so… it's a proxy. So it's, um, since we don't actually measure retention, it's the, you know, it's like a measure that we can take. Which will proxy for retention, so… Yeah, given that… satisfaction with ad blocking and CPM and MPS all raised at the same time. I mean, we can't say for sure, but we can be fairly confident that those improvements helped improve overall satisfaction. And attention." + }, + { + "time": "22:05:52", + "speaker": "russell holt", + "text": "Yeah, it's gone up 9 percentage points over the past year. I think that's pretty impressive. Yeah, and ad blocking in particular has gone up more than 10. Looks like we had just over 10 points since second quarter, so… That's, um… people… 63% of people in the survey rate. ad blocking on DuckDuckGo better than other browsers they use. That's up 10 points. That's pretty… You know, presumably the work we've done has actually moved that number. Who knows for sure, but… That's what we've been working on, so…" + }, + { + "time": "22:06:44", + "speaker": "FD", + "text": "Yeah, great stuff." + }, + { + "time": "22:06:44", + "speaker": "russell holt", + "text": "She feel good. She feel good about that. Um, okay, uh, Alex, why don't you… you put yourself on the agenda. Tell us what's happened… happening with the, um… with your project and help us decide what to do about it." + }, + { + "time": "22:07:00", + "speaker": "Alex Martemyanov", + "text": "Uh, yep, so the, uh, CPM breakage, so I've, uh, summarized… You can find the link in the description. summarize the current project states and refresh the data as of today's state. It's the first day of the last public release measurements. Um, so, um… On the… on the last week progress, uh, I found out there was, uh, some, uh… Post positive sense for error pages for Mac OS and that. lowered our metrics, uh, the 30% on failures, and it is now comparable with iOS, so it's still, uh, higher than 1%, but it's not 33%, it's 1 point. 9 of permanent breakage to our daily." + }, + { + "time": "22:07:58", + "speaker": "russell holt", + "text": "What, what's… What's an example of an error page here?" + }, + { + "time": "22:08:04", + "speaker": "Alex Martemyanov", + "text": "Any any error page basically any navigation like Wi Fi is not available or. Or some other problems like domain does not exist. So on that, on that page is naturally." + }, + { + "time": "22:08:16", + "speaker": "russell holt", + "text": "Really? Like, the new tab page?" + }, + { + "time": "22:08:20", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "22:08:21", + "speaker": "russell holt", + "text": "Like the new tab page?" + }, + { + "time": "22:08:23", + "speaker": "Alex Martemyanov", + "text": "Yeah. No. Not not the new tab page. New tab page was not measured, but error pages, like, domain name is." + }, + { + "time": "22:08:24", + "speaker": "russell holt", + "text": "Really?" + }, + { + "time": "22:08:31", + "speaker": "Alex Martemyanov", + "text": "Incorrect." + }, + { + "time": "22:08:32", + "speaker": "russell holt", + "text": "Oh, okay." + }, + { + "time": "22:08:33", + "speaker": "Alex Martemyanov", + "text": "So on that pages, natural ACPM won't load. And those, I used to follow the metrics. And, yeah, the the effect was around thirty thirty percent, and, that dropped, around one percent of daily users." + }, + { + "time": "22:08:42", + "speaker": "russell holt", + "text": "Okay." + }, + { + "time": "22:08:52", + "speaker": "Alex Martemyanov", + "text": "as expected. Uh, another two fixes, uh, that were a work in progress were merged, so to speak, as well, but they go, uh, to public release only. The next Monday. So, those are… kind of reproduced fixes as well. Still not the main breakage point here. And I expect some observable… expect from those, but probably it won't cross the 1% line, uh, still. And, uh, so we got this, uh, largest group, Neat and Wake, as discussed. And, uh, so basically it shows, uh, normal regular flow, and, uh, it shares around 30 to 40% of, uh, all the failures. And yeah, around 30% of permanent hands. So we need to look into the extension life cycle itself, I guess. And that is the point of today's discussion. Still there is a cleanup planned for the project because there were a lot of fixes implemented and some of them didn't work out because they were kind of fixing things synthetically reproduced but not happening in production. Uh, so, uh, I'm planning to roll… roll back the fixes that are… ineffective. And, uh, we need to clean up the data metrics, because they are… they are sending large chunks of data that we probably won't need anymore. We already collected. Everything that we needed from the current state. But I think we still are going to need some permanent metrics for the feature breakage. The one that's going to be presented in the earlier. page, so we can… Observe the spikes or other stuff. And, uh, the suggestion is to modify. the extension itself to track each lifecycle step, basically. Where do we lose those communications? Whether it's the extension not loading, or it needs not. getting to the browser or other parts of the sequence? Because there are a couple of hypotheses, although they seem not… they should not cause permanent breakage, like, for example. If the config is the… config fetch from the web extension is hanging, it will cause hanging of the whole queue, but it should be reloaded by the worker after, like, half a minute. So it's not validated, and we have no idea where exactly it breaks because other other metrics are all good. And not representative here." + }, + { + "time": "22:11:57", + "speaker": "russell holt", + "text": "Okay, so it sounds like…" + }, + { + "time": "22:11:57", + "speaker": "Alex Martemyanov", + "text": "Uh, so my suggestion for…" + }, + { + "time": "22:12:00", + "speaker": "russell holt", + "text": "Go ahead." + }, + { + "time": "22:12:02", + "speaker": "Alex Martemyanov", + "text": "So my suggestion for this week is to clean up the fixes that didn't work and clean up the metrics and feature flags where needed or put some feature flags to permanent state and add some extra metrics. Then we put the project on hold because we have run out of all the hypothesis and current issues we know." + }, + { + "time": "22:12:12", + "speaker": "russell holt", + "text": "Okay." + }, + { + "time": "22:12:25", + "speaker": "Alex Martemyanov", + "text": "And after we start receiving the data." + }, + { + "time": "22:12:26", + "speaker": "russell holt", + "text": "Well, I think you should postmortem. I think you should close it. Yeah, so this is the… um… This is a good point. Uh, to, uh…" + }, + { + "time": "22:12:35", + "speaker": "Alex Martemyanov", + "text": "Yeah." + }, + { + "time": "22:12:36", + "speaker": "russell holt", + "text": "I think post-mortem it. Rather than putting it on hold, because I don't know what the trigger would be for pulling it back off hold, other than, like. you know, maybe you look at the data. So, I agree with your plan here. I think it's… let me try to make sure I understand. So, there's a bunch of cleanup to do, which seems… You know, to kind of… Things that you have tried here. are still hanging out and need to be wrapped up or deleted or whatever." + }, + { + "time": "22:13:05", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "22:13:09", + "speaker": "russell holt", + "text": "Okay, so there's the cleanup. Then you want to make some of the temporary metrics permanent?" + }, + { + "time": "22:13:17", + "speaker": "Alex Martemyanov", + "text": "I guess, so make… so we got… so we would have some metric that could indicate, like, in the… some future failures, if they happen. For example, something changes in macOS." + }, + { + "time": "22:13:19", + "speaker": "russell holt", + "text": "Okay. Yeah, okay. Okay. And then there was something about the life cycle. I wasn't sure I totally followed that." + }, + { + "time": "22:13:38", + "speaker": "Alex Martemyanov", + "text": "then there is two fixes that are merged, but getting released on Monday, and, uh, we'll need an extra day, uh, for data analysis before we can post-mortem, probably next Tuesday, I guess. And, uh, there is an extent." + }, + { + "time": "22:13:47", + "speaker": "russell holt", + "text": "Okay. Next Tuesday, perfect." + }, + { + "time": "22:13:52", + "speaker": "Alex Martemyanov", + "text": "Yep. And, uh, there is, uh, this extended lifecycle metrics, so basically wipe out the metrics that we were measuring, like the surroundings, uh, the events of the browser itself, uh, but dive into the extension itself and its, uh, events that it's, uh." + }, + { + "time": "22:13:53", + "speaker": "russell holt", + "text": "Okay." + }, + { + "time": "22:14:11", + "speaker": "Alex Martemyanov", + "text": "goes through just to to get an idea where it fails, at which exactly and at which step. Because otherwise, the big the largest group is, looks normal from from the data that we have." + }, + { + "time": "22:14:20", + "speaker": "russell holt", + "text": "Okay. Okay, I think I follow that. Okay, that sounds good." + }, + { + "time": "22:14:35", + "speaker": "Alex Martemyanov", + "text": "Okay. So I will communicate this, I'll communicate it, with Max and, probably have a tech design on how to." + }, + { + "time": "22:14:36", + "speaker": "russell holt", + "text": "Next next Tuesday." + }, + { + "time": "22:14:43", + "speaker": "Alex Martemyanov", + "text": "How to do it, and uh… Yeah, we'll try to complete it this week." + }, + { + "time": "22:14:50", + "speaker": "russell holt", + "text": "Okay. Michal, you're still the advisor. You're on board." + }, + { + "time": "22:14:56", + "speaker": "Michal Smaga", + "text": "Yeah, so, yeah, we synced earlier today, and this is, like, what we discussed, so I fully approve of the plan, and I think this is, like, the most reasonable." + }, + { + "time": "22:15:00", + "speaker": "russell holt", + "text": "I'm good." + }, + { + "time": "22:15:05", + "speaker": "Michal Smaga", + "text": "Way to go to use that we can drop up everything." + }, + { + "time": "22:15:10", + "speaker": "russell holt", + "text": "Okay." + }, + { + "time": "22:15:10", + "speaker": "Michal Smaga", + "text": "Yeah, great job, Alex." + }, + { + "time": "22:15:14", + "speaker": "russell holt", + "text": "Awesome. Thank you, Alex." + }, + { + "time": "22:15:14", + "speaker": "Alex Martemyanov", + "text": "Thanks." + }, + { + "time": "22:15:17", + "speaker": "russell holt", + "text": "Okay. Hey, Marcus, what's happening with the top sides?" + }, + { + "time": "22:15:21", + "speaker": "Marcos Gurgel", + "text": "Hey, yes. So let me post this link here. Uh, top sites went public to 5% starting yesterday, so… Let me share my screen. The numbers that I mean, bottom line is we need more time to make any definitive conclusions. But the numbers I want to focus for now, given that we don't even have 24 hours of credible data. are these here. Uh, so, unhandled rate between top 10K and other. So, how many top 10K were detected versus how many were unhandled? How many others were detected versus how many were unhandled? And… Right now, it differs wildly between US and EU. So, top 10K in US. for less than 24 hours gave us 16% unhandled. 40% unhandled in the EU, so I think these numbers are still gonna stabilize. I don't think we should take them as meaning anything yet. Just to give you another idea." + }, + { + "time": "22:16:23", + "speaker": "russell holt", + "text": "What does it mean unhandled here?" + }, + { + "time": "22:16:28", + "speaker": "Marcos Gurgel", + "text": "Unhandled means…" + }, + { + "time": "22:16:28", + "speaker": "russell holt", + "text": "Individual pop-ups?" + }, + { + "time": "22:16:31", + "speaker": "Marcos Gurgel", + "text": "Yes, it means, uh… It means that… We detected a pop up in using regex, but we didn't detect it with rules or heuristics." + }, + { + "time": "22:16:43", + "speaker": "russell holt", + "text": "Okay." + }, + { + "time": "22:16:45", + "speaker": "Marcos Gurgel", + "text": "So, yeah, fell through the cracks, basically. We see them in regex, but…" + }, + { + "time": "22:16:48", + "speaker": "russell holt", + "text": "That's not 16." + }, + { + "time": "22:16:51", + "speaker": "Marcos Gurgel", + "text": "Sorry, go ahead." + }, + { + "time": "22:16:51", + "speaker": "russell holt", + "text": "That's not 16.5% of sites, that's 16.5% of…" + }, + { + "time": "22:16:57", + "speaker": "Marcos Gurgel", + "text": "Detected. So any page that we think was there was a pop up. For 16% of them, we didn't find a pop up effectively and we didn't remove any pop ups. And… Same for other sites. So this would be the long tail. But I'm not… Very interested in this right now. I'm more interested in the top sites. Just to give you another idea of why we shouldn't… we should ignore all the numbers that came before, uh, because everything was in internal before. These were the numbers of pop ups being detected up until yesterday. So around. 20 to 30 per day. And now we're up to, you know, 30,000. So today was only the first meaningful day of data, and the releases happened. So macOS happened in the morning in the EU. But it happened in the evening in. Uh, in the EU for iOS. So, I would… I would guess that… if we look at the US numbers for yesterday, they're going to be closer to reality, because I think a lot of people were already asleep in the EU by the time the app came out. So, what else can I… can I infer from this? And by the way, these… these panels, I'm… I'm experimenting with them, I'm trying to figure out which one gives me the more… Useful number. So far, I'm not I don't think comparing them is is. is meaningful, so comparing the rate of top 10K versus the rate of others, I think it's more important to compare them with themselves, so this panel here shows me." + }, + { + "time": "22:18:30", + "speaker": "russell holt", + "text": "Right." + }, + { + "time": "22:18:39", + "speaker": "Marcos Gurgel", + "text": "how many… it essentially shows me the same as this table. So how many detected versus how many unhandled. for each bucket. So, and this is what… This is what I think would be the ideal outcome. that would result in the least amount of work in putting CPM in maintenance, which is, we see a very low number of unhandled top 10K." + }, + { + "time": "22:19:07", + "speaker": "russell holt", + "text": "Yeah." + }, + { + "time": "22:19:08", + "speaker": "Marcos Gurgel", + "text": "And we see a fairly higher number than others. I think that that's the ideal. Outcome, but I don't know if we're good." + }, + { + "time": "22:19:13", + "speaker": "russell holt", + "text": "Prior than others. Other." + }, + { + "time": "22:19:16", + "speaker": "Marcos Gurgel", + "text": "Yeah, so the long tail would have more unhandled pop ups than the top 10K." + }, + { + "time": "22:19:24", + "speaker": "russell holt", + "text": "Mm-hmm. Yeah." + }, + { + "time": "22:19:25", + "speaker": "Marcos Gurgel", + "text": "Uh, but, I mean, regardless of how they relate, I think having this number in under 20% is… would be a good result. I don't know if, I mean… It's a dice roll at this point. Yeah." + }, + { + "time": "22:19:37", + "speaker": "russell holt", + "text": "Do we do we have it? Do we have the relation? Do we have it? That number? Do we understand its relationship to sites in the dataset?" + }, + { + "time": "22:19:47", + "speaker": "Marcos Gurgel", + "text": "Uh… Let me see if I understand the question." + }, + { + "time": "22:19:50", + "speaker": "russell holt", + "text": "Like, are sites that are, quote, covered… That we have rules for, are they still seeing unhandled pop-ups?" + }, + { + "time": "22:19:58", + "speaker": "Marcos Gurgel", + "text": "Right. No, we don't have that because we don't know which sites exactly people are visiting. If I understand the question correctly. So we can't correlate… Yeah. We can't correlate a domain with…" + }, + { + "time": "22:20:08", + "speaker": "russell holt", + "text": "Oh, yeah, and…" + }, + { + "time": "22:20:12", + "speaker": "Marcos Gurgel", + "text": "That has a rule for it. Versus one that doesn't." + }, + { + "time": "22:20:19", + "speaker": "russell holt", + "text": "Okay, so Conrad asks, why isn't it zero? Why shouldn't it be zero?" + }, + { + "time": "22:20:26", + "speaker": "Marcos Gurgel", + "text": "Oh, yeah. It should. It should. It's just that I was expecting, I mean, honestly, because the total coverage is right now around 22 or 30%. I was expecting this number to be higher. So yes, it should be zero. But if it's less than the average coverage. Uh, I think we're good, because then that would mean that…" + }, + { + "time": "22:20:52", + "speaker": "russell holt", + "text": "What percent? Do you know? Sorry. That would mean that what?" + }, + { + "time": "22:20:56", + "speaker": "Marcos Gurgel", + "text": "Yeah, go ahead." + }, + { + "time": "22:20:57", + "speaker": "russell holt", + "text": "No, I want to know what it means." + }, + { + "time": "22:20:58", + "speaker": "Marcos Gurgel", + "text": "No, uh, because right now, uh… I think… Let me see what I think it means. It means that if this is below the general average for coverage. Then we need to focus more on the long tail. If this is hitting the average for coverage, then we need to focus more on top 10K, because." + }, + { + "time": "22:21:17", + "speaker": "russell holt", + "text": "Okay. But we still…" + }, + { + "time": "22:21:23", + "speaker": "Marcos Gurgel", + "text": "Because we can get it's." + }, + { + "time": "22:21:24", + "speaker": "russell holt", + "text": "But we still want to get it to zero." + }, + { + "time": "22:21:25", + "speaker": "Marcos Gurgel", + "text": "We can get more results. Yeah." + }, + { + "time": "22:21:27", + "speaker": "russell holt", + "text": "Right, because every site that…" + }, + { + "time": "22:21:27", + "speaker": "Marcos Gurgel", + "text": "Yes, absolutely." + }, + { + "time": "22:21:30", + "speaker": "russell holt", + "text": "You know, ranked by popularity, presumably, every site that we then be sure that we. of properly completely covering has a bigger impact on that number then. Like, what's the approach for long tail? You pick." + }, + { + "time": "22:21:42", + "speaker": "Marcos Gurgel", + "text": "Yeah." + }, + { + "time": "22:21:47", + "speaker": "russell holt", + "text": "Just, you just go down the list or you pick them at random, you pick like. You have to do a lot more work in the long tail, right, than the top sites is what I'm kind of getting at." + }, + { + "time": "22:21:59", + "speaker": "Marcos Gurgel", + "text": "Yeah, I agree. And to that end, even at the top sites, this question of, like, which… Which sites do we tackle first? we don't quite have the answer to that, right? But we can… we can make assumptions based on sites' popularity. But… With the current metrics, we don't have a way to see whether a specific site is causing… is skewing the numbers, right?" + }, + { + "time": "22:22:23", + "speaker": "russell holt", + "text": "Sure, sure, but… Sure, but we have, you know, first of all, they are in the top 10K, so they're top 10K, based on our definition of that." + }, + { + "time": "22:22:32", + "speaker": "Marcos Gurgel", + "text": "Okay." + }, + { + "time": "22:22:34", + "speaker": "russell holt", + "text": "But then, you know, you can go through them in some order. Still, just doing them all is, to Conrad's point, kind of what we want to aspire to, I think." + }, + { + "time": "22:22:39", + "speaker": "Marcos Gurgel", + "text": "Yes. Yeah, absolutely." + }, + { + "time": "22:22:50", + "speaker": "russell holt", + "text": "Okay, dumb question. We send this for… Uh, do you know how many people have CPM… Disabled. And do we send the pixel for…" + }, + { + "time": "22:23:00", + "speaker": "Marcos Gurgel", + "text": "No." + }, + { + "time": "22:23:01", + "speaker": "russell holt", + "text": "for when. Do we only send it when a user has the feature enabled? Sorry, that's a dumb question, but we should know that." + }, + { + "time": "22:23:09", + "speaker": "Marcos Gurgel", + "text": "I… I… I don't know the answer to that either, but I'm fairly certain that summary pixels only go out if the user has CPM enabled, but I'll double-check that after the meeting." + }, + { + "time": "22:23:19", + "speaker": "russell holt", + "text": "Okay. Okay, all right." + }, + { + "time": "22:23:22", + "speaker": "Marcos Gurgel", + "text": "Yeah, but I don't know the answer to that either." + }, + { + "time": "22:23:27", + "speaker": "russell holt", + "text": "Okay, so what's your next step here?" + }, + { + "time": "22:23:27", + "speaker": "Marcos Gurgel", + "text": "So… So, next step on… yeah, on this data… on this data is to sit and wait, but the other side of the project, which is adding the user-centric metric, I think is gonna give us…" + }, + { + "time": "22:23:31", + "speaker": "russell holt", + "text": "I mean, we have to wait, get more data." + }, + { + "time": "22:23:42", + "speaker": "Marcos Gurgel", + "text": "some more actionable numbers. Because we're gonna end up with a number of, uh… Number of pages. That a user visits per day. in the top 10K with unhandled pop-ups. So what's missing from this data right now is how often a user is seeing an unhandled pop up in the top 10K or another for that matter. So… So I'm hoping that once the rest of my project is done, we have a panel that says. Uh, number of unhandled pop-ups. per user per day. In buckets, so 0 to 5, or… 5 to 10. And then from that, we can… We can gauge… the annoyance that. these unhandled pop-ups are causing on each user, right? So if… and I think that would give us a more credible signal for attacking either top 10K or other, because if we see that top 10K is… is… Relatively low here. But it's high in number of pages, in number of unhandled per page visits. Then that contradicts what we're seeing here, right? So… Yeah, I think bottom line is, I don't know very much about this data yet. I want to sit on it, but I want to progress with the other side of the project, which is to add the per user per day metric on this." + }, + { + "time": "22:25:29", + "speaker": "russell holt", + "text": "Yeah, uh… But that's still, I mean. You still want to get that 6… like, if that's 16… I mean, it's that…" } ] } diff --git a/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.md b/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.md index 2230e515..e13cb002 100644 --- a/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.md +++ b/work/zoom-transcripts/undated O-E 2026 e5TYWRytRz2WwWSe68BSWQ/transcript.md @@ -15,3 +15,107 @@ source: "https://us01mynotes.zoom.us/e5TYWRytRz2WwWSe68BSWQ" - **22:03:13 · russell holt:** Having a good week? Alright, let me try to figure out where I am. Here's the agenda. Yeah, a few. Thank you for adding some items. Um… So I wanted to start by highlighting this. Quarterly survey. a quarterly browser survey if you haven't seen it. It has some interesting. results from a lot of things that we're working on. we've been working on. Versus the ratings versus other browsers. Often for Windows in particular. for ad blocking has gone way up. People seem to really like that. CPM has made some improvements there with cookie banners aren't blocked. Yeah. And too many cookies sent. So some stuff we've been working on and waiting for for a long time. Pretty exciting if you go check it out if you're interested. So, just wanted to mention that. - **22:04:54 · FD:** Yeah, and just to add, I think… What's impressive to me is that NPS has also increased during the same time. - **22:05:00 · russell holt:** Can you explain NPS, Francis? It's Net Promoter something or other. +- **22:05:02 · FD:** And he had to. Yeah, net promoter score. So it's basically a a signal of loyalty. So it's basically saying how likely would you recommend this product to a friend? And… And so it's like a… It's like a substitute for retention, basically. Um, yeah, so… it's a proxy. So it's, um, since we don't actually measure retention, it's the, you know, it's like a measure that we can take. Which will proxy for retention, so… Yeah, given that… satisfaction with ad blocking and CPM and MPS all raised at the same time. I mean, we can't say for sure, but we can be fairly confident that those improvements helped improve overall satisfaction. And attention. +- **22:05:52 · russell holt:** Yeah, it's gone up 9 percentage points over the past year. I think that's pretty impressive. Yeah, and ad blocking in particular has gone up more than 10. Looks like we had just over 10 points since second quarter, so… That's, um… people… 63% of people in the survey rate. ad blocking on DuckDuckGo better than other browsers they use. That's up 10 points. That's pretty… You know, presumably the work we've done has actually moved that number. Who knows for sure, but… That's what we've been working on, so… +- **22:06:44 · FD:** Yeah, great stuff. +- **22:06:44 · russell holt:** She feel good. She feel good about that. Um, okay, uh, Alex, why don't you… you put yourself on the agenda. Tell us what's happened… happening with the, um… with your project and help us decide what to do about it. +- **22:07:00 · Alex Martemyanov:** Uh, yep, so the, uh, CPM breakage, so I've, uh, summarized… You can find the link in the description. summarize the current project states and refresh the data as of today's state. It's the first day of the last public release measurements. Um, so, um… On the… on the last week progress, uh, I found out there was, uh, some, uh… Post positive sense for error pages for Mac OS and that. lowered our metrics, uh, the 30% on failures, and it is now comparable with iOS, so it's still, uh, higher than 1%, but it's not 33%, it's 1 point. 9 of permanent breakage to our daily. +- **22:07:58 · russell holt:** What, what's… What's an example of an error page here? +- **22:08:04 · Alex Martemyanov:** Any any error page basically any navigation like Wi Fi is not available or. Or some other problems like domain does not exist. So on that, on that page is naturally. +- **22:08:16 · russell holt:** Really? Like, the new tab page? +- **22:08:20 · Alex Martemyanov:** Yep. +- **22:08:21 · russell holt:** Like the new tab page? +- **22:08:23 · Alex Martemyanov:** Yeah. No. Not not the new tab page. New tab page was not measured, but error pages, like, domain name is. +- **22:08:24 · russell holt:** Really? +- **22:08:31 · Alex Martemyanov:** Incorrect. +- **22:08:32 · russell holt:** Oh, okay. +- **22:08:33 · Alex Martemyanov:** So on that pages, natural ACPM won't load. And those, I used to follow the metrics. And, yeah, the the effect was around thirty thirty percent, and, that dropped, around one percent of daily users. +- **22:08:42 · russell holt:** Okay. +- **22:08:52 · Alex Martemyanov:** as expected. Uh, another two fixes, uh, that were a work in progress were merged, so to speak, as well, but they go, uh, to public release only. The next Monday. So, those are… kind of reproduced fixes as well. Still not the main breakage point here. And I expect some observable… expect from those, but probably it won't cross the 1% line, uh, still. And, uh, so we got this, uh, largest group, Neat and Wake, as discussed. And, uh, so basically it shows, uh, normal regular flow, and, uh, it shares around 30 to 40% of, uh, all the failures. And yeah, around 30% of permanent hands. So we need to look into the extension life cycle itself, I guess. And that is the point of today's discussion. Still there is a cleanup planned for the project because there were a lot of fixes implemented and some of them didn't work out because they were kind of fixing things synthetically reproduced but not happening in production. Uh, so, uh, I'm planning to roll… roll back the fixes that are… ineffective. And, uh, we need to clean up the data metrics, because they are… they are sending large chunks of data that we probably won't need anymore. We already collected. Everything that we needed from the current state. But I think we still are going to need some permanent metrics for the feature breakage. The one that's going to be presented in the earlier. page, so we can… Observe the spikes or other stuff. And, uh, the suggestion is to modify. the extension itself to track each lifecycle step, basically. Where do we lose those communications? Whether it's the extension not loading, or it needs not. getting to the browser or other parts of the sequence? Because there are a couple of hypotheses, although they seem not… they should not cause permanent breakage, like, for example. If the config is the… config fetch from the web extension is hanging, it will cause hanging of the whole queue, but it should be reloaded by the worker after, like, half a minute. So it's not validated, and we have no idea where exactly it breaks because other other metrics are all good. And not representative here. +- **22:11:57 · russell holt:** Okay, so it sounds like… +- **22:11:57 · Alex Martemyanov:** Uh, so my suggestion for… +- **22:12:00 · russell holt:** Go ahead. +- **22:12:02 · Alex Martemyanov:** So my suggestion for this week is to clean up the fixes that didn't work and clean up the metrics and feature flags where needed or put some feature flags to permanent state and add some extra metrics. Then we put the project on hold because we have run out of all the hypothesis and current issues we know. +- **22:12:12 · russell holt:** Okay. +- **22:12:25 · Alex Martemyanov:** And after we start receiving the data. +- **22:12:26 · russell holt:** Well, I think you should postmortem. I think you should close it. Yeah, so this is the… um… This is a good point. Uh, to, uh… +- **22:12:35 · Alex Martemyanov:** Yeah. +- **22:12:36 · russell holt:** I think post-mortem it. Rather than putting it on hold, because I don't know what the trigger would be for pulling it back off hold, other than, like. you know, maybe you look at the data. So, I agree with your plan here. I think it's… let me try to make sure I understand. So, there's a bunch of cleanup to do, which seems… You know, to kind of… Things that you have tried here. are still hanging out and need to be wrapped up or deleted or whatever. +- **22:13:05 · Alex Martemyanov:** Yep. +- **22:13:09 · russell holt:** Okay, so there's the cleanup. Then you want to make some of the temporary metrics permanent? +- **22:13:17 · Alex Martemyanov:** I guess, so make… so we got… so we would have some metric that could indicate, like, in the… some future failures, if they happen. For example, something changes in macOS. +- **22:13:19 · russell holt:** Okay. Yeah, okay. Okay. And then there was something about the life cycle. I wasn't sure I totally followed that. +- **22:13:38 · Alex Martemyanov:** then there is two fixes that are merged, but getting released on Monday, and, uh, we'll need an extra day, uh, for data analysis before we can post-mortem, probably next Tuesday, I guess. And, uh, there is an extent. +- **22:13:47 · russell holt:** Okay. Next Tuesday, perfect. +- **22:13:52 · Alex Martemyanov:** Yep. And, uh, there is, uh, this extended lifecycle metrics, so basically wipe out the metrics that we were measuring, like the surroundings, uh, the events of the browser itself, uh, but dive into the extension itself and its, uh, events that it's, uh. +- **22:13:53 · russell holt:** Okay. +- **22:14:11 · Alex Martemyanov:** goes through just to to get an idea where it fails, at which exactly and at which step. Because otherwise, the big the largest group is, looks normal from from the data that we have. +- **22:14:20 · russell holt:** Okay. Okay, I think I follow that. Okay, that sounds good. +- **22:14:35 · Alex Martemyanov:** Okay. So I will communicate this, I'll communicate it, with Max and, probably have a tech design on how to. +- **22:14:36 · russell holt:** Next next Tuesday. +- **22:14:43 · Alex Martemyanov:** How to do it, and uh… Yeah, we'll try to complete it this week. +- **22:14:50 · russell holt:** Okay. Michal, you're still the advisor. You're on board. +- **22:14:56 · Michal Smaga:** Yeah, so, yeah, we synced earlier today, and this is, like, what we discussed, so I fully approve of the plan, and I think this is, like, the most reasonable. +- **22:15:00 · russell holt:** I'm good. +- **22:15:05 · Michal Smaga:** Way to go to use that we can drop up everything. +- **22:15:10 · russell holt:** Okay. +- **22:15:10 · Michal Smaga:** Yeah, great job, Alex. +- **22:15:14 · russell holt:** Awesome. Thank you, Alex. +- **22:15:14 · Alex Martemyanov:** Thanks. +- **22:15:17 · russell holt:** Okay. Hey, Marcus, what's happening with the top sides? +- **22:15:21 · Marcos Gurgel:** Hey, yes. So let me post this link here. Uh, top sites went public to 5% starting yesterday, so… Let me share my screen. The numbers that I mean, bottom line is we need more time to make any definitive conclusions. But the numbers I want to focus for now, given that we don't even have 24 hours of credible data. are these here. Uh, so, unhandled rate between top 10K and other. So, how many top 10K were detected versus how many were unhandled? How many others were detected versus how many were unhandled? And… Right now, it differs wildly between US and EU. So, top 10K in US. for less than 24 hours gave us 16% unhandled. 40% unhandled in the EU, so I think these numbers are still gonna stabilize. I don't think we should take them as meaning anything yet. Just to give you another idea. +- **22:16:23 · russell holt:** What does it mean unhandled here? +- **22:16:28 · Marcos Gurgel:** Unhandled means… +- **22:16:28 · russell holt:** Individual pop-ups? +- **22:16:31 · Marcos Gurgel:** Yes, it means, uh… It means that… We detected a pop up in using regex, but we didn't detect it with rules or heuristics. +- **22:16:43 · russell holt:** Okay. +- **22:16:45 · Marcos Gurgel:** So, yeah, fell through the cracks, basically. We see them in regex, but… +- **22:16:48 · russell holt:** That's not 16. +- **22:16:51 · Marcos Gurgel:** Sorry, go ahead. +- **22:16:51 · russell holt:** That's not 16.5% of sites, that's 16.5% of… +- **22:16:57 · Marcos Gurgel:** Detected. So any page that we think was there was a pop up. For 16% of them, we didn't find a pop up effectively and we didn't remove any pop ups. And… Same for other sites. So this would be the long tail. But I'm not… Very interested in this right now. I'm more interested in the top sites. Just to give you another idea of why we shouldn't… we should ignore all the numbers that came before, uh, because everything was in internal before. These were the numbers of pop ups being detected up until yesterday. So around. 20 to 30 per day. And now we're up to, you know, 30,000. So today was only the first meaningful day of data, and the releases happened. So macOS happened in the morning in the EU. But it happened in the evening in. Uh, in the EU for iOS. So, I would… I would guess that… if we look at the US numbers for yesterday, they're going to be closer to reality, because I think a lot of people were already asleep in the EU by the time the app came out. So, what else can I… can I infer from this? And by the way, these… these panels, I'm… I'm experimenting with them, I'm trying to figure out which one gives me the more… Useful number. So far, I'm not I don't think comparing them is is. is meaningful, so comparing the rate of top 10K versus the rate of others, I think it's more important to compare them with themselves, so this panel here shows me. +- **22:18:30 · russell holt:** Right. +- **22:18:39 · Marcos Gurgel:** how many… it essentially shows me the same as this table. So how many detected versus how many unhandled. for each bucket. So, and this is what… This is what I think would be the ideal outcome. that would result in the least amount of work in putting CPM in maintenance, which is, we see a very low number of unhandled top 10K. +- **22:19:07 · russell holt:** Yeah. +- **22:19:08 · Marcos Gurgel:** And we see a fairly higher number than others. I think that that's the ideal. Outcome, but I don't know if we're good. +- **22:19:13 · russell holt:** Prior than others. Other. +- **22:19:16 · Marcos Gurgel:** Yeah, so the long tail would have more unhandled pop ups than the top 10K. +- **22:19:24 · russell holt:** Mm-hmm. Yeah. +- **22:19:25 · Marcos Gurgel:** Uh, but, I mean, regardless of how they relate, I think having this number in under 20% is… would be a good result. I don't know if, I mean… It's a dice roll at this point. Yeah. +- **22:19:37 · russell holt:** Do we do we have it? Do we have the relation? Do we have it? That number? Do we understand its relationship to sites in the dataset? +- **22:19:47 · Marcos Gurgel:** Uh… Let me see if I understand the question. +- **22:19:50 · russell holt:** Like, are sites that are, quote, covered… That we have rules for, are they still seeing unhandled pop-ups? +- **22:19:58 · Marcos Gurgel:** Right. No, we don't have that because we don't know which sites exactly people are visiting. If I understand the question correctly. So we can't correlate… Yeah. We can't correlate a domain with… +- **22:20:08 · russell holt:** Oh, yeah, and… +- **22:20:12 · Marcos Gurgel:** That has a rule for it. Versus one that doesn't. +- **22:20:19 · russell holt:** Okay, so Conrad asks, why isn't it zero? Why shouldn't it be zero? +- **22:20:26 · Marcos Gurgel:** Oh, yeah. It should. It should. It's just that I was expecting, I mean, honestly, because the total coverage is right now around 22 or 30%. I was expecting this number to be higher. So yes, it should be zero. But if it's less than the average coverage. Uh, I think we're good, because then that would mean that… +- **22:20:52 · russell holt:** What percent? Do you know? Sorry. That would mean that what? +- **22:20:56 · Marcos Gurgel:** Yeah, go ahead. +- **22:20:57 · russell holt:** No, I want to know what it means. +- **22:20:58 · Marcos Gurgel:** No, uh, because right now, uh… I think… Let me see what I think it means. It means that if this is below the general average for coverage. Then we need to focus more on the long tail. If this is hitting the average for coverage, then we need to focus more on top 10K, because. +- **22:21:17 · russell holt:** Okay. But we still… +- **22:21:23 · Marcos Gurgel:** Because we can get it's. +- **22:21:24 · russell holt:** But we still want to get it to zero. +- **22:21:25 · Marcos Gurgel:** We can get more results. Yeah. +- **22:21:27 · russell holt:** Right, because every site that… +- **22:21:27 · Marcos Gurgel:** Yes, absolutely. +- **22:21:30 · russell holt:** You know, ranked by popularity, presumably, every site that we then be sure that we. of properly completely covering has a bigger impact on that number then. Like, what's the approach for long tail? You pick. +- **22:21:42 · Marcos Gurgel:** Yeah. +- **22:21:47 · russell holt:** Just, you just go down the list or you pick them at random, you pick like. You have to do a lot more work in the long tail, right, than the top sites is what I'm kind of getting at. +- **22:21:59 · Marcos Gurgel:** Yeah, I agree. And to that end, even at the top sites, this question of, like, which… Which sites do we tackle first? we don't quite have the answer to that, right? But we can… we can make assumptions based on sites' popularity. But… With the current metrics, we don't have a way to see whether a specific site is causing… is skewing the numbers, right? +- **22:22:23 · russell holt:** Sure, sure, but… Sure, but we have, you know, first of all, they are in the top 10K, so they're top 10K, based on our definition of that. +- **22:22:32 · Marcos Gurgel:** Okay. +- **22:22:34 · russell holt:** But then, you know, you can go through them in some order. Still, just doing them all is, to Conrad's point, kind of what we want to aspire to, I think. +- **22:22:39 · Marcos Gurgel:** Yes. Yeah, absolutely. +- **22:22:50 · russell holt:** Okay, dumb question. We send this for… Uh, do you know how many people have CPM… Disabled. And do we send the pixel for… +- **22:23:00 · Marcos Gurgel:** No. +- **22:23:01 · russell holt:** for when. Do we only send it when a user has the feature enabled? Sorry, that's a dumb question, but we should know that. +- **22:23:09 · Marcos Gurgel:** I… I… I don't know the answer to that either, but I'm fairly certain that summary pixels only go out if the user has CPM enabled, but I'll double-check that after the meeting. +- **22:23:19 · russell holt:** Okay. Okay, all right. +- **22:23:22 · Marcos Gurgel:** Yeah, but I don't know the answer to that either. +- **22:23:27 · russell holt:** Okay, so what's your next step here? +- **22:23:27 · Marcos Gurgel:** So… So, next step on… yeah, on this data… on this data is to sit and wait, but the other side of the project, which is adding the user-centric metric, I think is gonna give us… +- **22:23:31 · russell holt:** I mean, we have to wait, get more data. +- **22:23:42 · Marcos Gurgel:** some more actionable numbers. Because we're gonna end up with a number of, uh… Number of pages. That a user visits per day. in the top 10K with unhandled pop-ups. So what's missing from this data right now is how often a user is seeing an unhandled pop up in the top 10K or another for that matter. So… So I'm hoping that once the rest of my project is done, we have a panel that says. Uh, number of unhandled pop-ups. per user per day. In buckets, so 0 to 5, or… 5 to 10. And then from that, we can… We can gauge… the annoyance that. these unhandled pop-ups are causing on each user, right? So if… and I think that would give us a more credible signal for attacking either top 10K or other, because if we see that top 10K is… is… Relatively low here. But it's high in number of pages, in number of unhandled per page visits. Then that contradicts what we're seeing here, right? So… Yeah, I think bottom line is, I don't know very much about this data yet. I want to sit on it, but I want to progress with the other side of the project, which is to add the per user per day metric on this. +- **22:25:29 · russell holt:** Yeah, uh… But that's still, I mean. You still want to get that 6… like, if that's 16… I mean, it's that…