 Hello, everyone. Hello. We've got another full house this week. So this is wonderful. Welcome to Hacktoberfest Week 2. It's wonderful. Now, Sandy isn't able to join us. She is traveling, and she can't find good internet wherever she is. So we're going to miss you, Sandy, but we'll see you next week, hopefully. But once again, we have Alesh and Jamie joining us. And we've got two special developers joining us as well. We have K Knight, author of the BioCheck app, and Riele Schmitt, who's joining us, who's working on the CC7 app. So we're looking forward to lots of neat things there. So how's it going, everyone? Busy week for you? Looks like everyone's tired. Everyone's been up late, hacking away, and fixing things. Riele came on. He said he just finished his latest update in the last hour. Good stuff. So great. So I thought, I'm going to start off this week just giving you an update on the SuperBigFamily Tree app, which is the one I'm working on. It's not live. It's not in the Tree app. It's not even on the test server. It's only on my folder in the app's server, the one I actually gave the link out to last week. It's looking a little better than it was before. And what's really exciting is I've got Steve 80 as a programmer, and he's volunteered to help me out with the settings area. So once he gets his hands on a computer and gets it all set up, then I will have a conspirator in this whole thing. So let me just quickly show that, because all these other wonderful people are going to show you stuff they've been working on. So I'll get my boring stuff out of the way, stuff that you've already seen. So it's not new. It's just a little bit better than it was before. So here we are. So I'm going to refresh it. And I guess I should put it in here, right? So you can see it a little better. So it's loading. And I've actually got a loading message up here now so you can follow along the process. So if you're impatient, well, something is happening. OK, so here we have now one of the things I've added is I've added this Zoom button. So if you click on it, it'll automatically zoom in and out at various levels. No, I guess because I didn't. There we go. And actually, if you do a custom Zoom and say, OK, that's about the level I want. And then you hit the Zoom again. As it does the zooming in, it actually tries to center the people. So that's the Zoom factor that I like. So I can read that with my aging eyes. But anyways, you can see that here's the tree. And last week, if you recall, descendants worked fine. But the ancestors, not so much. But this week, I've got the ancestors working better. We'll go up to four levels of ancestors. Well, let's stick with three levels of descendants. But what's working better this time is now the cousins and the aunts and uncles are showing up. And if I wait one more, you can see there's the first level of first cousins. And we should be able to get a level of second cousins as well. So anyway, so you can see that there's a Zoom. You can see you can actually get quite a few people. And if I click on in-laws, oh, I have to wait for the loading cousins to finish. You can see you can get quite a few people packed into this super big family. Anyway, so that's about all that's new there. What's the total number of people on the chart at the moment? That is an excellent question. And that would be a great stat to have in the bar here, wouldn't it? OK. But I don't. But I will have to add that. Thank you, Aleš. OK, let me write that down. New people request, number of people. Yes, why didn't I think of that? Of course. Well, you are always busy clicking and writing and watching for the details. And now we are just viewing the preview. And that was the first question. That was the first question. OK. Anyone have other questions? So when Steve comes and joins, the settings area right now, all the settings that don't actually work, I put an exclamation star right next to them so they stand out. So he'll be able to find out what it is. Now, there are some things that do work. So you can actually change the font. That works. That's kind of boring. I mean, it's not really very exciting. But that's one feature that still worked. It's funny, things that do work and things that don't. But anyways, that's it for that's all I have to report on the progress in that app. So I'm going to stop sharing my screen. And turn it over. Who wants to go next? Let's see. Jamie, do you want to talk about some of the other stuff that's happening? Yeah. So I don't have my computer ready to screen share. OK. So I know Ian added a few things to the browser extension this week, including something that a lot of people were asking for, which is the ability to see which people in your CC7 have been changed. So that's cool. It's very exciting. Yeah, and he's testing that right now. So it isn't live in the live version, right? Yeah. It's in the preview version. And actually, I made a post in G2G that links. It's like a testing post, which links to the three preview versions of the browser extension for Chrome, Firefox, and Safari, and also the preview version of the Tree App, just so people can test. So I will find that link and post it. What changed in your CC7? Yes. Yeah, that's right, Chris. I tried it this morning, and unfortunately, I hit an API limit. So it said limit exceeded, so it wouldn't tell me. Yes. Yeah, Ian and I were all trying to figure out why that's been happening lately. I think we finally figured it out, and so I sent the information to Brian. So hopefully that won't happen as often now. Like once Brian fixes that, because I know it's been annoying for some people where they try to use an app and it won't let them. But we think we're getting closer to why it's happening when it shouldn't. So let me find that link. Here's a testing post. OK. Wow. Well, Jamie is doing that. I've got exciting news for you. Because we can, let me see here, we've been allowed to give away a free t-shirt. So the way we're going to do it is anyone who's in the chat who types the word hacktober is entered into the draw for a free t-shirt and will do the draw at the end of the live cast. So there we go. So type hacktober and just double checking. I'm spelling it the same way that the person collecting the, yep, there we go. Hacktober, there we go. OK, did you find what you were looking for, Jamie? I did, but for some reason, it says that it fails to post when I try to put it in the chat. So I guess I'll add it. Put it in the private chat. I did. OK, let me try because that works for me. OK, it's in. Yeah, so that's the post that tells you how to see the preview versions. Great. And did you mention Ian also has done the wiki-table wizard feature. And I haven't practiced, I haven't played with it enough. So I don't want to make it look bad. So I don't want to demo it and mess it up. Ian's here looking at us, too. So we've got other things to show. And I'd rather demo it next week and not make a fool of myself or get someone else to do the demo than do it live. That's OK. Sorry, Ian. But so the wiki-table wizard is new. And the CC7 changes are coming and are available in the preview. Anything else, Jamie? No. Pardon me. Jamie's also taking more of a lead on the TRIAP. So when we finish a TRIAP, we can give it directly to Jamie. And then that'll get posted on the test server and then the TRIAP. So it's all great. So, Riel, do you want to go next? I'm sure what you've talked about. Sure. I'm working on? If I can figure out to share my screen. Click on the Present button down there. Yeah. OK, while you're doing that, Chris was asking about what are the features on the CC7 changes. So basically, in the Find menu, there's a new option that says CC7 Changes. And it will tell you which profiles have been added or removed since the last time that you checked your CC7 changes. It basically keeps track of them in your own browser, not on the server, but in your browser history. And then when you hit that, it'll update. It'll go and check to see what's new since the last time you checked it. There's already documentation for it on the Space page. Oh, perfect. If so, we'll go from here. Oh, really? The documentation's there before it actually goes live. Well, because it says Preview. Preview, yes. I love when that happens. And then you get all excited and they, oh, it's Preview. Yeah, I still can't post links in the comments for some reason. So if Alish can move it from private to comments. There are screenshots and everything. I'm assuming Marie did it. She's very good at documentation. Yeah, yeah, he's good. That's great. OK, take it away. Maybe I'm going to hide the banner for a bit. But if you haven't typed Hacktober yet, make sure you do so, so that you can, oh. Sorry, Alish, I didn't. OK, so I want to show three things that I added to the CC7 app. The first one is just the cancel button. The CC7 app remembers which degree you retrieved the last time. And sometimes you retrieve the CC7 of somebody and they may not have had a very large CC7. And you go away and the next day you come back and you just want to retrieve a CC3 of somebody else. But when you go to the app, it will automatically retrieve the degree that it got the last time. So what you can do now, select me, take this guy. And I said, OK, I accidentally wanted to get CC7. And it's going to take a while. I said, oops, that's not what I wanted. Now you'll see that these two, the get buttons are disabled. Otherwise, the system gets confused with all the gets that's going. And you decide that this is not what I wanted. I can just say, oh, cancel. And the thing is just almost immediately canceled. And the API call is aborted. And the servers are saved from Excel work. Nice. Then the second thing you can do is you can ask it to run the bio checks on the profile as they are being retrieved. So before I do that, let me just set this back to something the same for this person. Choosing a small numbers just to make the demo easier. And you'll see under the settings, in addition to the dark young icons that you can set, there's now a bio check tab. And you can say, oh, what I forgot to mention is if you don't have the bio check on the top here, you see that there's a message that tells you bio check is disabled. Bio check is disabled by default if you haven't disabled it before, simply because in order to do bio check, we have to retrieve the profile biographies. And that puts extra strain on the servers and on your data. And it takes longer to pull the CC7 with sort of superficial tests on my CC7, which is a little bit large. The retrieval time was about double what it was before. So you may not want to have it on always. But anyway, so I can enable it. And remember to click the apply changes. Otherwise, it's not applied to the app. It just sits there in the config, but it's not applied to the app. Greg can explain to you why that happens. Since it's these little settings app that was code that's very useful. Anyway, so now I've got noticed that that message has disappeared at the top. So bio checking will be done when I get the CC7 for this person. We should retrieve about 68 or so profiles. Actually, it retrieves more because in order to retrieve a CC2 and show all the counts correctly, it actually has to retrieve CC3. So it always takes a little bit longer. So now you'll see that down the left-hand side here as part of the title of that thing over there, which was just P before, is now P slash B, which is privacy and biocheck. And over here, it will tell you that that tells you what the icon means, but if you click just the left of it, it tells you click to see the biocheck report. And if you click that, it tells you what it found or what biocheck found. Very nice. And I think it was, yeah, or things like this. And like with all the other pop-ups, you can either just click the same things again, or you can double-check in it. Or you can check the X at the bottom to make it go away. And that is about it. As far as the biocheck is concerned, and then if you turn it off, you come here, turn it off, and you apply it. Then you can remove all those things immediately. However, if you now go back and turn it on again, or at some point later, it doesn't run the biochecks. Because if you turn biocheck off, if biocheck is off while you're retrieving profiles, we don't retrieve the biographies. So it could go faster. And therefore, we can't run biocheck on the data we already have. So this is also why that sentence is there, to tell you that it's only the next time you press the get button that the biocheck will run if you've just enabled it. Right. If I run it then again, then it will appear. And this also happens for, like, you just get the degree only, the one degree. Then it should also show you a biocheck run just on the degree. And you only have one issue. That's great. That's it. Yeah. Let's say now that I'm on. Oh, no, you have more than one issue. You're only showing us that you had one issue. But yeah, these are not necessarily my profiles, but that's a lot of people just at the second degree. Wow. I think it's one of my. This person is in my tree somewhere, or in my season seven somewhere. Now, the next thing is not on the test server yet. And as Greg mentioned, I just finished got it to work as I wanted it to work about an hour ago. And this is to allow you to select subsets of view of your CC in view to display. Because sometimes there can be quite a lot of profiles. So this is just the CC2 of one of my great grandfathers or somebody. And already, there are quite a lot. And you may want to limit what you're looking at just for some sanity. So I've added this filter for selection box at the beginning here that allows you to, as the pop-up says, select which profile should be displayed. And you have five options. It's all of them. Or you can say you want to show only the direct ancestors or direct descendants, or what I call all everyone that's above the current person or the central person, where above is kind of defined by anyone that can be reached. Whoops. Are you showing the pop-up? Because I can't see the pop-up right now. Can you not see the pop-up? Do you? Does anyone else see the pop-up? It's showing on my screen, but it doesn't. I don't see it on the shared screen. Pop-ups don't show up on the shared screen. Depends what you select it in after pressing Present. If you select the whole screen, then it would show. Otherwise, it's just one application. I selected Window. OK. For some reason, the pop-up registers a different window when that happens. Yeah. So yeah, I try to create pop-ups of just about everything. So if you just hover about something, be a little patient sometimes, and something will pop up and tell you what it's about. So the All Above is basically for anyone that can be reached by first following the parent link. And All Below is anyone that can be reached by first following non-parent link. There is a but to be added to those two statements. Because if you start with a parent link, and thereafter, you can follow anything. So can it go back down under to the children? Yes. And similarly, when you go down in your CC7, when you follow children, and thereafter follow any parent, you can circle back to some of your ancestors. So they are actually circles, if we want to call it that. But you can get to the same person going up or going down. And so the decision I made was that anyone that can fall in both of those groups, you compare the age of that person with a central person. And if it's the same age or younger, then it's in the below group, otherwise it's in the above group. OK. No, so sometimes you'll see weird things where. So you'll get some older brothers and younger sisters in the different groups. Yes. Or you'll get a great, some uncle, great grand uncle or whatever in the below group. Simply because you don't have a leave team yet going upwards. So it depends on how your people are connected. So here is I selected ancestors. And these are just the parents and grandparents of this person. And this ancestor view also work on the list tab. You go to list, so those are just the ancestors. It doesn't make sense on the hierarchy list because it just creates chaos if you remove, if you don't show some of these people because of the hierarchy. So you can't see it there. But the moment you go back to list or to table, then, oops, sorry, the table, you will see it. And while you're in that thing, you can still select, say, all above, and it was everyone above. Or you can go to the table and it will show you. And what's the difference between table and normal table again? OK, normal table is just I have what is here now a wide table, wide display normal table. Just makes it fit in the screen. So it's either wide or normal. It's just the width of the table basically. If you select wide table, it doesn't wrap the lines inside the cells. And you have to scroll it and right to see everything. But you get more people per screen. But you can get, yeah, exactly. And that is it. That's great. I wasn't sure whether this subset thing, how useful it was, or will be, and whether people will actually use it. So maybe people can get feedback and say whether they have a good idea or not. So that's maybe another reason why I haven't created it. I haven't submitted it yet. Debating whether it might be useful. It seems fun. I like it. It'd be interesting to play with. So yeah, give us feedback in the chat or on G2G about these new options. Excellent. Well, this is a nice segue since you've incorporated BioCheck into the CC7 app. CC7 app. Let's hear from Kay and what she's been up to this week. OK. Have I unmuted OK? You have. All right. Well, it's all about collaboration. That's wicketry. And everybody's been showing it already. Somebody said they wanted this, and so we'll add this to it. And then people tested it and said, yeah, that's working. Oh, that's got a problem. I don't understand that. The same happens with the documentation. Well, the developers are doing the same thing. And so the developers are collaborating to all work together. I don't have a lot of new stuff to show for BioCheck, but I wanted to show a couple of things. Let me see if I can share my screen correctly, and I'm going to do the whole thing. So it's going to be kind of strange. OK, so is that showing the whole screen? It is. It is. All right. So we're going to go first here. There we go. To BioCheck. And the bolding is one of the things that somebody suggested that a long time ago. If I could do a wicketry plus search for profiles that were born in 1880 that are orphans, and say 1,000 of them, and say, check. I've had this cancel button for a long time because I'm impatient. But real taught me how to make it a lot quicker. So that's just an example of the collaboration. Also, the little tiny thing is that I added some bolding and a little bit results maybe incomplete when you cancel just a couple of minor things. If we go look at this guy, Franklin Dill, go check him. It's a quick way because he's not a profile manager. I see that he's unsourced, marked unsourced, but he might have sources. That's a new check that's been added. And if I scoot over here because I don't have the preview version of the web browser in my Firefox, it's only in my Chrome. So when I go down here and I go over Save Draft, you will see that it's saying this guy is unsourced, but he has a source that's not clearly identified and then references this down at the end. And if you go look at the change history, somebody went in and clicked that, did it a long, long time ago and got the default, and I added a source and never cleaned it up. That was a complaint during Sourcet on this year that many profiles are actually sourced, but still you have the template. So now we will know which one are those. That's great, yeah. They asked us about that on Ask A Lech this week too, didn't they? Yeah. So this is great, Kate. This is really answering a call that's needed, yeah. Another one, if you get some real... In order to find sources, BioCheck has to look at the style of a profile. It's a side effect. BioCheck is to see if a profile's sourced, but it's a side effect that checks the style for the health that's out there. So if we look at May, she looks like, well, yeah, she probably ought to be unsourced, but she's easy to source. If you go look at her brother, Tom, Dick, or Harry, whatever his name is here. I just saw that. I know. But if you look at May, you will see that the biography heading is before the category Boulder, Colorado. It used to just say that category isn't the first thing. And there were some really messed up profiles that had multiple categories that were interspersed among all the little things that are template stuff that's in between the squiggly brackets, like a research note box, the project box, navigation box sometimes. John is the same way that he's got a couple of categories out of order. I think that was all that I really had to show about it because there's not that much more that's new. Does anybody have any questions before I stop sharing? I noticed in the GitHub messages that you had done something with the bio check to it with fan chart and the fractal tree, but was that just moving code that didn't change how it worked or did it change how it worked? I did change, hmm, I cleaned up the code. Oh, well, there was lots to clean up, I'm sure, sorry. Yeah, yeah, well, a while ago I did start, now the references is out before. I cleaned up the code and the help because the code is the help. Right. Regenerated the docs because working with Vriel, I found, oh, wait, that doesn't make sense. That's not quite right. I need to go through the fan chart and the fractal tree and make sure you're using it right. I need to do a code review of your code to see if the issue's there. Now I'm afraid. It's always scary letting someone else in and checking your code. Well, I want to look at these. Is it using BioCheck correctly? Exactly. I have too many plates spinning right now. I got a suggestion from the Profile Improvement Project and working with Alash on maybe adding some new stuff and had a thing out there a long time that people wanted to know how many sources are there on a profile. I got it. I just have to figure out how to squeeze it into that table that's getting reported. I already report the number of inline references and I thought, well, I could just put the number and then put the angle brackets and inline. But that's no good because then you can't sort that column and you might want to report your watch list and sort how many things have inline references. But I do want to go back and look at the tree apps and see if there's anybody else that now that we know there's a cost of grabbing the Bio when you grab the profile, when you actually get the profile, I think it's tied to how long the Bio is. I think that's what drives it. Probably. Because I did one and it went from like 60 to 80 seconds. 20 seconds is an eternity when you're waiting for it. Yeah. Why my app has a cancel button? That's right. Yeah. But I don't want to see it anywhere else that it might make sense to add that and it should be fairly easy to do. It's just a matter of, I think figuring out how to set the options and how to display the results is the hard thing. Well, you did it, you know. Yeah. Yeah. And by default, I do grab all the Bios from the get go. But the fan chart, I mean, it's a lot smaller than a CC7 in terms of the number of people you're gathering, especially since you only gather five generations at first. So that's only 63 names. And then you're gathering one generation at a time. So it's fairly small and incremental. So I didn't think I needed that to turn it off and then turn it on. But I suppose we can, if people find that the fan chart has slowed down since I've added that, you know, that's an option. I was testing the CC7 app with Riel and with my own family, my own CC7, which is only black 3500. Right. So it's not as big as his. And a lot of them don't have very lengthy biographies. I think a lot of his have really long bios. So that's the cost of being a really good wiki-trier. I'm not known for being succinct. Well, neither am I. You've looked at my health page. I'm not known for being succinct. Yeah. So, well, that's something I'll keep in mind. Okay. Well, that's great, Kay. We're really enjoying the integration. Chris, I mean, Chris mentioned it in the chat already, but I'm excited to see how that... I'm glad that it worked with the fan chart. That was a nice test case. One of the really cool things is that Unsourced gets sticked down to profile when you use Autobio and WB, but it's finding out if it's unsourced by using BioCheck. And... Really? So Autobio uses BioCheck? Yeah. We had a little bit of a race trying to get into the browser extension. That's great. Who's first? Who's there? Maybe that was change options. We raced a little bit. But the results that are reported in the CC7 amp and the browser extension and in the BioCheck amp itself, the details, it's the same text. That's awesome. It's all the same. Because we're lazy. We just want to do it once. Well, it makes sense. Yeah. Let's be consistent. That's great. Okay. So, Alesh, should we do the t-shirt giveaway now before Alesh goes or should we wait till after Alesh? What do you think, Jamie? I don't know if anyone else is going to enter. Yeah. Okay. So if you haven't already typed in the word Hacktoberfest, now would be the time to do it. Folks, I'll give you a few seconds. Alesh, what are you gonna show us today? Well, my working environment for wiki3 browser extensions. So how do I get the data from github and how to edit it in visual studio codes? And then also compiling, testing on the page, debugging, and so on. Excellent. Okay. That sounds wonderful. I'm really keen about seeing this. It sounds funny because yesterday someone posted and actually asked that exact question, like, oh, I haven't done browser extension programming. Like, how do you debug and stuff like that? I was like, perfect timing, Alesh. Perfect timing. Oh, wow. Okay. I won't show how to install everything and so, but just so you'll get an idea of how it looks. And maybe some that are already doing it might see something new. Or give me some idea in discussions later. Okay. Hacktober, not Hacktoberfest. Just Hacktober is what is the word. And I'm about to, it looks like we have 20 entries. So there's five. You've shared the screen? I'm gonna share my screen. Yeah, I was just checking there to make sure. Oh, you know what? Yeah. Am I still sharing my screen? I know. I guess I closed it on my screen. I'll go over here and I'll move this over to there. Not that you guys, okay. And there we go. Oh, someone hit, okay, 21 entries. There's Hacktober. I'll give you a five second countdown to type it in if you haven't already done it. Five, four, three, Hacktober, one, okay. Ready or not? Here goes the draw. Who's gonna win the free t-shirt? It will be... Azure. This is great. Azure gives away all these things, but she never wins herself. So now she's gets to win. Hey, Azure. Well, I think Azure knows how to win the prize. You have to email aowin at wikitree.com. Well, that's great. That's super. Fantastic. Okay. Take it away, Alash. Okay. So for getting the... So as you most likely probably know, we have on GitHub, we have wikitree browser extension. And here you can actually see all the files, each file that represent the source. They are all mostly, most of them that are being developed are in the source map here. And then in the features, each feature has its own folder. So you can check how somebody did something. This is always interesting to see. So, and here you can come on the internet to how something is written. So this is just a view only. Although you can edit here, but usually we don't do that. It's just too... I mean, things need to be tested and so on. So to get all these files to my computer, I initially installed the GitHub desktop. This is the application where you can set it up and now here I can easily see all the history of the pull request and so on. And now here, for instance, I see I'm five instances behind. So five new things were already published since I last clicked here. So I just click here and now it will pull all the new request from the internet. And I will see here actually... Let's maximize this. Okay. So here they came and I will see for each pull what was changed in which file. So you can overview things here. So on CC7 there were the bugging locks changes and so on. So you can check every detail here. And usually I'm working directly on the development branch because since I have the rights to do that, but usually one needs to create a new branch and download the files, write what he wants and then publish that branch back to the GitHub and it gets then merged into the main development branch. So here with this program you can do everything that I do, that you have to do with GitHub to do. And then afterwards I use Visual Studio Browser, Visual Code for developing. And here again, all the files you can... You have to install a few extensions to the visual code. To the Visual Studio to make things nicer. But here again you can see every file that is up there. And you can actually do the edits to the code. So let's go to Wiki3 Plus. Okay. And okay, here I program what needs to be changed. It's very nicely colored everything and so on. And then once I want to test something, you can do here in NPM scripts. I run this built developer environment. So this will compile the actual component so that I can use it in the browser then. So in the meantime it takes a few seconds. Then in browser, first thing you need to do is to... In browser you actually need to manage extensions. You have to install the developer mode in the extensions and then install from local hard drive the extension. So this is the extension directly from my drive. And this is the official published extension here. So I have the official one turned on, often this one is turned on. Here it also collects the errors that occurred during testing of the extension. So here I can see what was wrong lately in the extension during my runs of it. But the only thing that I need to do is hit this refresh button. So this means that the extension got reloaded. Now in... So okay, let's go to some page. Okay. I think Wiki3 Plus is here. And when I'm checking it, I always have the debugging mode turned on. So here I can see all the errors that occurred during the extension and so on. So you can then tend to it and see what's wrong. So this is how the process goes. And then here I try the... So I don't know, add any... We can go to add any category and okay, it goes like this. Then here in the extension, I can turn on the debugging. So this is... I do this by... Here if you go to section sources, here there are two. Wiki3 browser extension. This is Wiki3 browser extension with... Okay, I'm missing something. I know what I'm missing. So I have to select first here the... Sounds over. No? Okay. Yeah. Here in the context script. So here I get all the extensions that I'm using. Although the Wiki3 browser extension is usually just this... Let me increase this a bit. It's just this code that is not really readable. But if you turn on the... So here the debug... If you run the debug mode. So this debug icon. In that case, you get another Wiki3 browser extension here where it is actually... All the files on this car are actually here present. And you can work debug through them. So here I can go to Wiki3 plus and let's see Wiki3 plus. I think this is the main unit. And I can then here set a breakpoint. And so we were in the category something. Okay, I can for instance... Okay, this is main loop. I can put here the breakpoint. And now when I will select add any category. Okay, it didn't come to the main loop event. Oh, now it did. And it stopped the execution of the extension. And now I'm here in the bugger. And I can examine all the elements run code line by line and so on. So here I see elements. All the properties and so on. So this is very useful once you're looking for for something that doesn't work as you want. And then you just continue the execution and set the breakpoint. And okay. And continue the work. So this is generally what I do. Any questions? Wow, that's neat. I think a lot of us might want to have to rewatch this video maybe on half speed. And I don't know because of the video, the program that we're broadcasting through, that only takes up a quarter of my screen. So it's very tiny font. So I'm going to have to blow it up on my big monitor to see it. But as someone who's only programmed the tree apps, I've downloaded this stuff for the browser extension. And we got it all installed at Roostec, actually. And it was ready to go and I made one little test comment. And I haven't done anything in the browser extension since then. Well, I know that you can also hear if you install a GitHub, even from the studio, you can get the, you can examine the changes you did. That's right. I should be because I installed it once. So here I can examine what I changed before. But I don't do commits from here. Although I think it's possible, but I got used to this program. So I'm using this one for now. The GitHub desktop. Yeah. See, I use Visual Studio Code for programming my tree apps. And I commit directly from there. But then I go over to the GitHub web page just to make sure that I do the pull requests from the GitHub web page. Here in GitHub desktop, you have all the options to create the repository change, create push pull requests and so on. So it's kind of, most of the things that you can do on GitHub are also here. But for a few details, I also need to go directly to GitHub. Especially now, if you want to examine the history of some file, how did it change in the last year? Right. That's, I think, easiest directly on GitHub. Yeah. Okay. Well, that's great. So people have questions. You can put comments on the GGG post. I suppose you could put comments on this video as well. Or if there's something more specific. I don't think any of us will see the comments on this video. So add them to the GGG post. That would be better. Or Discord. Or Discord. Just send us a direct message in Discord if you have questions about that. But I think, so if you want to stop sharing your screen, we can see Jamie and her sister Corgi in a bit bigger frame. That's what the audience wants to see. I just need to find my share. I also have here our cookie. Oh, you've got your dog? My finnigan's just sleeping away over there. He's bagging me here to go on a walk. Yeah, I'm visiting my sister in North Carolina, and she has two Corgis, and this one wants to sit on my left. Oh, that's not nice. We're still on the golden retriever rescue waiting list. Get a new puppy. Missing our Manali. My dog is sleeping on this carpet there. He still smells a bit like the skunk that he got sprayed with last weekend. So, Real, do you have a dog? Are you the only one without one? No, no dog. No dog. Okay. So you don't get distracted while programming? Yeah, but they're very distracting sometimes. Lock up and go. That's my motto. Yeah, that's right. Azure said that she wanted to donate her prize to someone else. So we get to do this, draw again. So let's draw again to end off our show. And who's going to be the winner? Hopefully someone who's still online. Mad Max. Where'd it go? Mad Max? So, Max, what you have to do is you have to type in, you have to email Aowyn at, let's see, there's going to be a banner with her name on it here somewhere. I don't see it. I'll just put it in Aowyn. I'm going to have to spell it right. WikiTree.com. If you email Aowyn at WikiTree.com. Oh, I should have known Azure would have put it in. Anyways, there we go. She will set you up with your prize. So, free t-shirt. Generally, you have a choice between a t-shirt and a mug. I suspect that's still the case, but Aowyn will let you know. Chris, okay, that we can give away the prize. So, that's great news. Congratulations, Max. Mad Max. And I think that's it for, that's all we have lined up. Jamie, any other things that I missed? Something I missed when I was talking about the browser extension. Yeah, Chris just mentioned that David Weinberg was a new contributor. Oh, right. Yes. In the chat. So, thank you, David. Yes. Excellent. What's David been working on? My mind is blank. It was like the category migration helper. I think he made it work with the advanced editor. So, that's right. Yes. Now I remember seeing that go by. Yeah. So, very nice. David's in the chat. Very nice. So, that's good. Yeah. And I've got someone who'll be starting to help me shortly. And you've already mentioned, you mentioned something else. Anyways, there's been lots of people working together. So, that's very nice. So, that's great. Oh, yeah. I forgot the other thing that I was going to mention. Yeah. Go ahead. I was stalling for time. I was waiting for you to think. I have a cord in my lap. So, I'm thinking of how cute she is. That's right. It's hard to think. Stephen Harris has been working on a portrait view. So, you can see all the portraits. I'm not quite sure if it looked like it wasn't just your ancestors. Maybe ancestors and their children. But it will just show you all their portraits on a page, which is kind of cool. That's right. Cool. So, when I tested his version yesterday, I think he had been working on it. So, it wasn't there. And then I only have it on the test server. So, it's not available for other people to look at now. But I will do that as soon as we're off the live chat. Okay. Yes. So, we'll look forward to seeing that previewed next week, then. Yes. Yes. Murray Maloney. That's the name that was stuck in my head. I was thinking Maloney Maloney. No, that's not. It's a different first name. It's not Maloney Maloney. It's Murray Maloney, who was helping a lot, the documentation and stuff too. Anyways, thanks everyone. Thanks Kay and Riel for joining us. And Dilesh, as always. And we'll see you this time next week. And let me just find our outgoing video. See you later.