 Hello everyone and hello to everyone in the chat too. Hi, Greg. How are you doing Aowyn? Awesome. How about yourself? I'm doing fine. Yeah, we missed you last week. Thanks. I'm really really happy to be here. Excellent. We have a full house here today. This is great. We do. We have a wiki tree party going on. It's a wiki tree party. Yes, a tech party. It's super. So maybe I'll just let everyone go around and introduce themselves. I'm Greg Clark, app developer, Hacktoberfestier, and host for this. And over to you, Chris. I'm the founder of wiki tree over here. Okay. I'm Mindy and I'm a team member and I'm in charge of the challenges. Aowyn? Off to one of them. Aowyn or Lesh? I'm Aowyn. I'm a forest elf. I do stuff. She does a lot of different stuff. She's good there. Oh, next. Okay. Lesh? Lesh Tertnick. I'm also a team member and I also develop and support wiki tree plus that is a service running in parallel to wiki tree. Excellent. And I'm excited because we have two people who we don't often get together on these livecasts. And I think it's his first. So if you can out there, you can introduce yourself and pronounce your name properly. I'm Szemek. Yeah. So I'm from Poland. And I'm trying to contribute from time to time, like by programming skills to the community. I'm the author of the like the Pola visualization. If anyone uses that and yeah. And this week I'm calling in from a hotel room. Hello. Hello. That's great. And Brian. I'm Brian Casey. I'm the, I guess main developer and system administrator on wiki tree. Excellent. Thank you. Well, welcome all of you. This is very exciting to have such a full house. And let's see who we have in the chat. We have a more haveline here and Hillary Tommy Buck, Debbie root, Stewart, Kathy Navas here and anyone else who's here in the chat just say hello. And we're glad that you're here joining us as well. So, so Chris, I'm excited to have you here on camera with us. So you said you're the founder of wiki tree. So in programming terms, we would call you wiki tree or zero because in, because what you may not, what you may or may not know when programmers have a list of items, we call that an array, but arrays always start at number zero is the first item. So you would be wiki tree or number zero, the original wiki tree. So that's exciting to have you here. Yeah, I think of myself as number 32 because in our, or no IDs. I see, I see. Well, that's two to the power five, which is a very cool number as well. So nice. You're such a master. I am guilty as charged. So I know what it's like. Okay, good. Excellent. So I'm just wondering. So when we started our Hectober Fest or you and the team came up with Hectober Fest, I'm wondering just, you know, what's or some of the things you were hoping would happen and sort of the some of your rationale behind it. I think it's going great and I'm really happy that it's happened. Yeah, I'm blown away with how well it's going. We really didn't expect this much engagement and, you know, the back and forth has just been incredible, the pace of it, the sophistication of it. Yeah, so it's fantastic. It's not something that we came up with. Hectober Fest is something they've been doing for, I don't know, maybe close to a decade in the general open source community, but anybody can participate in it. So we decided to participate this year. And it was just kind of perfect timing because a lot of things had recently fallen into place for us in where open source fits into WikiTree. You know, WikiTree is all about collaboration. It's always been about broad based community collaboration. But for the longest time, you know, that was primarily about the content, about the genealogy and not the technology. The development was still very centralized. You know, Brian and I and the team have done so much. We did, you know, we have had the API and apps for a while now, you know, and some great things have been developed by you and Jamek and others. But they've always sort of stood aside from WikiTree. You know, we've had WikiTree here, and then, you know, there are these apps and extensions that really feel like add ons. And, you know, we've just kind of recently figured out a plan for really making them much more integrated. And so as you know, and touched on in the past, you know, so it's two basic parts. So it's the dynamic tree views. And it's the browser extension. And those two correspond to the two basic parts of WikiTree. So on the one hand, there's the viewing and accessing genealogy. And that corresponds to the dynamic tree. And then on the other side, there's the research and editing and contributing. And that corresponds to the extension. That's great. Yeah. Now, Susie did have a question here. Will these improvements work on iPads? The I can tell you the dynamic views, the do work, at least the ones that I tested out will work on them. I'm not sure if they all work really well on a smartphone. I can't promise you that. I can tell you if you have a fan chart that has 10 generations, the smartphone may not be your weapon of choice. Now, the browser extensions modify the views a little, but there are a few of them that are a little glitchy in a touch interface. Some of the language is not quite correct. And there's been a few cases where some of the dragging or resizing, it mostly works. You know, we're just using a sort of standard canvas. So it should work. But, you know, as we find bugs, we are trying to add them to the list and get them fixed. The goal is for the views to work in, you know, any device except, you know, obviously, some have so much data in it that the overwhelm a tiny screen, but that would be true of other places on Wiki Tree too. Thanks, Brian. And then Stephen has a follow up question. Will it be used in Firefox or other browsers other than Chrome? Funny, we were just discussing that before it went live. I think absolutely it should. I was testing things in Firefox and it worked, but there's clearly some JavaScript browser dependencies that we I think don't want long term that we're causing some issues with Safari. I think, you know, all modern versions of browsers we should be able to support. It's mostly standard JavaScript, so I'm not sure where we've gone awry and we're not going to try to support, you know, IE9 or something that would be painful. But certainly, you know, Safari and Firefox and Chrome and Edge, you know, the modern versions of browser should, at some point, it'll work. Excellent. Good. Yeah. Yeah, right before it went live. For extension, it will probably develop. It is slightly different development for Firefox and Safari, but that's all part of the plan, although we are still first trying to get it to work. Right. And which browser are you? Most of the users work on Chrome, as I know. Chrome. Okay. And can the extensions work on iPads at all or no? I think Safari supports them, although I'm not sure. Yeah, they were talking about Safari, I think. Okay. Interesting. Yeah. The rest of you don't know is five minutes before it went live, I threw Brian a bomb, a question that sort of made him dive down a rabbit hole, but he got out of that rabbit hole with 30 seconds left to go, so that was pretty impressive. And solved the problem. So, as Chris mentioned, there's two main aspects to this project. And this week, we're going to focus more on the dynamic view, the dynamic tree view. But before we go into that in detail, I thought maybe Alesh, if you could talk about some of the work that's happened this week in the browser extensions, some of the things that have gone on. Yeah. Well, most of the... I'm surprised. It seems that all browser extensions will be reported to this one. So, I mean, all the programmers for the... participate. So, I think we will end up with a single extension that will do everything. So, it's been done a lot of work on organization, and we are trying to get to... for all extension to work in a similar way, make common in-user interface. So, it would... the end users actually wouldn't even see from who some part of the code... who developed some part of the code. So, this is mostly what was happening this week. I think not all extensions are already in the active version, but all our working... all developers are working on it. So, I think by next week, all of existing ones will be functional. That's very exciting. That's very exciting. Yeah, I know... I noticed in the Discord, I saw some back and forth. The wiki tree B, that's Ian, right? He's working on that, and Hay Night is working on... is starting to work on the... getting her biocheck incorporated. Later today or tomorrow, she says, excellent. That's a huge amount of work, but she shared me a screenshot with that, which is very cool. So, when you're in the edit screen... I hope I'm not giving it away. Okay, sorry. When you're at the edit screen, or after you've saved a draft, there'll be a note that'll pop up or a text that'll give you a biocheck synopsis that looks like this is unsourced, or one of the other messages from the biocheck app or something that just sort of magically appears, which is pretty pretty impressive. Yeah, very cool. Jamek, did you do any work with the extensions this week? I think you did one of the things you did was organized, like was organizational, right? Which is key to a project like this. Yeah, so I finally managed to get my change in, like changing the structural directories, like getting the build system running, like modules, so that's people adding more things, don't mess up other people's work. I hope the organization will work better, better since this is going to be a big project. That's great. Thank you for that. That's super. Yeah. So, are there any other questions about the extensions in the chat? I haven't seen any new one yet. I have a question though, Greg. How about for those of us that just love, love, love the current extensions, is the interface going to be any different for us once this is brought into the just the wiki tree? I mean, is it going to be kind of spread out? Do you understand what I'm asking? I do. And I know I've seen some chat about, you know, where we put certain functions or, I said we, but I'm not programming any of the extensions. So, I mean, them, whether that means adding things to menus or making submenus. Alessha, I think you were part of that discussion. I don't know if you can answer that. Yeah. Well, it will be on, it seems it will be in three places. One part will be integrated into existing wiki tree menus. Then we will probably use the line where the categories shortcuts, this and comments shortcuts right under the tabs that will, a few extensions are added there. They usually show in place. And the third group will be on next to the toolbar in edit modes. So, when you are editing any page, you will get the goodies that are needed for editing. So, I think these three places will mainly be, and then there are a few extensions that altered the behavior of the site. So, I don't know that you have space page preview on hover on hint and so on. So, those are just integrated into the page or wherever. They don't have menu, something to start it. Right. Yes. So, Judy has a question about needing to, do you need to reload the extensions? Well, each time, well, after the extension will be published on the store, you will just install it and it will be updated probably once a month and it updates automatically. But now if you want, if you are looking at the preview of the development version, you have to load, download it from the developing site from GitHub and then unpack it and reload it and then it works. So, there are a few steps there described on the GitHub. So, it is possible. But just for those who are interested in development or testing it or because we are welcoming the suggestions to make something different differently than it is done. Right. Yeah. So, while we are still in the development mode, it is a bit more work. You do have to manually reload every improvement update. But the final version will auto, should auto load. Right. So, that's good. Excellent. And Judy does have a suggestion or a question. Is anyone considered adding and in between the parent's names in edit mode? Hmm. That would be an, might be an easy one? I don't know. I'm not going to, I shouldn't say that because I'm not, I'm not doing it in that program. Maybe you can. Yeah, I might do it. Okay. So, let's shift gears and talk about the dynamic tree. And Brian, you've headed up that part of the project. And you get all, you're the one who gets hassled every time that one of us wants to push in or make a pull, which seems funny to me. When I'm done, when I've done an update, I do a pull request. But I think it should be called a push request because I'm trying to push it on to you. But that's the terminology that GitHub uses. So, how are things going from your point of view? I think it's been really neat. The ability for other people to really contribute to the way wiki tree is going to look and work into the future, I think is great. And I'm hoping that it snowballs and that all of the work being put in and now to sort of generalize things and make the view code a little bit more accessible so that other people can either add new views or polish up existing views. Going forward, I'm hoping that that continues to grow. And one of the things I was working on this week was integrating the collaborative version into the main wiki tree website. So, people will be able to see that view that comes down from the menu on a profile when you select dynamic tree, that that view will be the version that updates so that all of these contributions can be seen and stuff. So, there's always organizational bits and bugs show up and things like that, like you do with any sort of rapidly developing early stages project. But I feel like it's going pretty well. Everybody's been congenial about the various issues at hand and it's nice that the views are separate so somebody can throw in a view and it doesn't disturb any of the others for the most part. So, yeah, I think it's been good. Good. Excellent. Okay. Well, I'm going to share my screen now and I'm going to give you a little bit of a sneak peek behind the screen, behind the, what's the word? Behind the curtain is the word. If I could interject, just give a little more context to connect with what Brian said and what you're saying. So, what you're going to look at is sort of like the current development version of the dynamic tree. And Brian was talking about making that be the dynamic tree that people can see on the live version of the site. And then even moving forward, there's another level to this is we actually do plan on replacing our family tree pages with the dynamic tree. So, ultimately, that's what we're going to be moving towards is the family tree and tools pages that you see on wiki tree now, which are really like, you know, the center of that UI for browsing genealogy is eventually going to be replaced with the dynamic tree. You know, that's the plan we have. So, it's sort of like three different, you know, levels of integration. Right. Right. Okay. Yes, I remember you reading that somewhere too, but I sort of, I had lost that thread. So, I'm glad you brought that up. Thank you. Okay. So, first off, let me find, okay, too many screens and they're not playing nicely with each other. There we go. Yeah, to the stream. So, one of the things I, one of the things I asked at the beginning of this, I asked some of the programmers to share what their programming setup looked like. So, I thought I would share, I would show you what that looks like. So, this is Neck's programming this week because he's in a hotel room. So, Neck, you win the award for minimalist, most effective use of small space. I think Jamie was also on the airport. So, she's in the air right now. That's right. Yeah, or in the airport. So, she can't join us, but she didn't send me a picture, but she did mention in the chat that her, she's looking forward to getting back to her home office because the computer she's working on has keys that don't work, has an enter key that just fires indiscriminately. So, halfway through a message, she said the message appears and then finishes in the next line. So, I don't have a picture of that, but you can all imagine poor Jamie having to work on that. Kay sent us, this is her, her setup, very nice and neat and organized. And she also shared, she shared her husband's setup. And this is him, an amateur radio operator. That looks more like my desk, normally looks. But because I knew I was going to be on camera, I cleaned up my desk and this is what I look, this is my setup. There's usually, there's usually stuff covering. You don't always get to see the brown full leather. But anyways, there's my graph pad, you know, in case I need to make graphs. Of course, brand new stereo display monitor that I bought and other monitors. So, and there's my iPad that I can check things out. And of course, my trusty TARDIS mug. Brian, you sent me a picture too. And let's see if I can find that one. Shoot, where'd it go? I don't know where your picture went. It downloaded here, but it's not in my thing. Sorry, Brian. That's right. It's not important. But the winner, the winner of the best desk, the one that I covet is Steve Harris's setup with a quad monitor. Four monitors all going at the same time. And a laptop. And I think he has a full desktop underneath all of this as well. So he's really, I think he wins the award for power user of the week. Anyways, I just thought that might be amusing to share with you. But anyways, for those who aren't programmers who are a little curious about what we do and behind, this is the program that I use to actually write the code in. It's called Visual Studio Code. And so I can click on a file and then type in commands, blah, blah, blah, blah, blah. But then when I need to get that update to the programming language to onto the internet so that Brian can then integrate it into Wiki Tree, then what we have to use is a site called GitHub. And this is the main site. And in fact, right here, I can even make that a little bigger, so you can see. All of the work that we do on the dynamic trees actually fits in these few files. There's nine little text files here and one directory that has a folder for each of the different views. So it's actually, it looks like it's a fairly straightforward process. But all the logic in the program that goes into each of those is a little more complex. So from the main one, nine different people, including myself, have taken a copy of that and we're working our own little copy of it. So here's what my little copy is. And I've got sort of four different little mini projects branching out from that. In fact, they use the word branch. And then when I add a new feature, and it's working and it doesn't break anything else that I know of, then I do what's called a pull request. And then that sends a message to Brian. And then Brian updates, he does, he tests it. And if it doesn't break things on his end, then he puts it through. And then it goes in part of the full, the live wiki tree, or the live version of this dynamic tree that we're working on. So that's sort of how the programming goes back and forth on how the communication goes. Last week when I showed you, so when we first started out, Brian put together this version of the dynamic tree and it had basically two views, the base one and a restyled one, which is the same sort of thing, but with different colors. And that's, that was what we started with October 1st. And then last week, I showed you how pitiful the fan chart was, how sad it was looking. And the next day, I was just so embarrassed by that that I had to at least add the background to it. So this is, I'm showing you basically, in a nutshell, the development, a quick view of my development of the fan chart app on the dynamic tree over this last week. So I'm being embarrassed by how poorly of mine looked last week compared to others. I first did the fan, I did the shell of the fan chart. So you can see, let me just scroll up here, and it responds so you can do the full circle, the fan or the semicircle, and it responds to that. But this version still relied on bringing in people, one pair of ancestors at a time. And then of course, if you did too many, you ran out of the fan. So that was kind of, but you know, baby steps. So then the next day, or see, this is the 11th. So what day is that? So this would be Tuesday, I guess. By Tuesday, I was able to make it so that you could actually go up and down the generations. But you couldn't go past six. Oh, well. But it did still more or less work. But there were some weird things that were happening. Then the 12th, so what do I add on the 12th? This one now allowed you to go all the way up to 10, if you wanted to. And then the 13th, which is today, let's load that up. Yeah. No, let's load it up for here. On the side here, you'll see these are comments. So these are ones. So if I'm needed to debug things, that's one of the things that programmers can do is they can show the web page on half of the screen and then show the comments or debugging. So sort of the information, the data in behind. I'm going to close that up because that's not. So here, now the fan chart looks like this. I colored the button bar, so it stood out a little bit better. And instead of just names and time span, I give you the full name with a picture. And of course, that can go in either one of those combinations. And you can go up to as many, up to 10 generations as well with that. Cool. So yeah, so that's the latest version of what the latest version of the fan chart looks like. That's awesome. Thanks, thanks, everyone. So it took a while. So some of the things that are different currently with this version from the live app is that in this case, for example, I'm just, just to get it working at least at this stage, I sort of made some arbitrary decisions that if you're in the first five generations, then show the picture because there is room in the fan in the wedges for those pictures. But if you go beyond that, then just show the name and the lifespan. Now, in fact, for this one, I could probably put the full dates if I wanted to. But one thing that's different is in the current app, the live app, you either have all the pictures or you have no pictures. This one, it's sort of arbitrary, it chooses pictures until it runs out of room or it thinks it runs out of room. So that's one, I guess one of the questions I have for users is, do you, are you okay with that? Or should there be a, should there be an option to show all pictures or sort of like maybe have an auto mode, which would do this, which sort of would sort of try to do the best it can or make, you know, make some logical choices or have no pictures at all would be an option too, of course. So those are some of the things. That's what I was going to ask if we were going to definitely have the option to have no pictures showing if we just want an all text fan chart. Yeah. And Kay has an excellent point there I noticed. I can't, I don't always pay attention, I can't always pay attention to the comments in the chat, but this one just popped up so it caught my eye. And definitely having only the pictures if the profile has one. And that solves your problem because most there's probably no pictures for people born 200 or 300 years ago. Right. Well, you know, and you know what I've noticed, especially if you go into royalty is you see a lot of the the heraldry used as their profile pic and stuff, which some people like, yeah, Finnegan wants to join in my dog Finnegan. Thanks, John. Or maybe it was too geeky for him here to leave. So anyways, that's one of the questions. But I see that Yuta is in, thank you Yuta, is in the chat. And Yuta actually helped me out by she, I put a call out to ask for help in terms of organizing, you know, prioritizing what features to add. And Yuta responded to that and gave me a nice organized list, which pretty much follows what I would have thought of. But I'm glad that that sort of. So I appreciate your help with that. The big thing, then I think the next thing that I have to tackle with this app is putting together an option screen or a setting screen. So when you click on the settings gear here, what I envision is a window will pop up probably with tabs for the different categories. So names and dates would be one tab. Color palettes might be another DNA highlights or highlighting might be another one, those sorts of things. So I'm welcoming input on how to that how to structure that or and how to make that look so and so if anyone wants to help me with that, I'd be most grateful. The other thing that I did a new view I added is a new is a new a new view. And I'll start with myself for this one. And it's called the fractal tree. So when you go to that, this is what you get. So that is three generations of from for me. And to understand it, it's easiest to understand if you just go back to one generation. So there's one generous. That's me. And then oh, and then when you click on the two generations, you get my parents, my biological father and mother. And then one more generation gets their parents. So every person gets their father and mother added. And it basically alternates between horizontal a horizontal line between parents and child or vertical line between parents and child. And another word for this view is the H tree, because as you can see, it's three generations, it looks like a capital H. But the cool the reason why it's called a fractal tree is because it takes that it takes that form that geometric shape basically and repeats over and over. So you had four generations, it's like two H's, then there's a big giant H now. See, it just repeats itself like a six generations, seven generations, another giant H, and so on. And you can do up to 10. Oh, I added this message here. You have to wait. Okay, and it tells you when you can go on there. Oh, oh, I have to wait some more. Okay, there we go. And that's as far as it'll go. Again, I'm maxing it out at 10. But but because of the zoom and the zoom feature, you can zoom right in on any one of those little family groupings as it were. And anyway, so the same basically the a lot of the same logic that I use for the fan chart, I can use for the fractal tree. And so when I add features to the fan chart, I should be able to add most of those same ones in this one. It just the difference is in the way that's displayed. This one's displayed geometrically like a fractal, the fan chart is like a more circular in. So now Greg Steven had another question. If you click in any of the views on a picture on the chart, will it center that person and then have the them be the focal point? It will. Once let's see if it works now. It doesn't work. This feature did work. Then it got broken, but it's going to be fixed by well, I won't say who someone did admit that they had made an update that broke that functionality yesterday. So I will thank them when they fix that. But yes, it does do that. In fact, I even changed the icon from the ancestor icon to the fan chart icon. So that will work. Yeah. And I will do the same thing for the fractal tree. I haven't done that yet. But again, once that functionality is fixed globally for this whole thing, and that's one of the cool things about a project like this, you change it. If the function exists at the top level and you change it and you change it right, then it just works for everyone else who's used the same function. Of course, if you change it and you break it, then you break it for everyone else. So there's a bit of both. Greg, if I could get in on this point. So not just like switching between people on the fan chart, center that part of the idea of this integrated dynamic tree with all these different views, then is that when you have switched people, that'll carry through. So if you were to show now that you go to a different view, you're still starting with that same person. That's exactly right. Yeah. So this is very different than what we have now where we have these standalone apps where you're always starting from zero. This is a way in which it's much more integrated. Yeah. That's great. Brian, do you want to... So the on and toffle ancestor list, I believe that was here last week, I think. Yes. And so that one just takes you through and gives you a list of all your ancestors with the number. I think I even geeked out about the numbering system. So I'm pretty sure that was here. The surnames list, was that here last week? Maybe a very rough draft. I don't remember when it got pushed. Yeah. I think... Yeah, I just wait about seeing that. Yeah. This is kind of a neat one because, again, it goes through your family tree and gives you the names of the surnames, and the larger the surname, the more people with that name, more ancestors with that last name. So I'm the only one to Clark because I was adopted. So my birth father is actually Douglas. But I guess it put it in big because I was at the top of the tree. The sizing is based... It's made bigger in a given row if it's new. It's not based on the number of ancestors with that name. There's not a surname count going on. This was a replacement to touch back to Chris's point where we have this separate page that was being generated that had this. And so we kind of pulled it into the dynamic tree where it can be accessed with all of the rest of them. And so partly to replicate that and push it forward and to have another bit of example code where it's HTML rather than an SVG graphic, it was pulled in. But at each row, the sizes get smaller as you go further and further generations just from a display point of view. But within a row, like you can see Rob, that's the first time that Rob appears as you go back from your starting ID. And then in the next line, Rob appears, but it's small because that surname has already appeared. And Douglas is big because it's spelled differently. Oh yes, that's right. Yeah, the one S and then two Ss. Yeah, look at that. Okay. Well, I learned something new because I thought it was like one of those word clouds where you know what the size is based on the frequency. That would be a really interesting another view to make actually, because we have counts for surnames. And so if we could expose that from the API, which we can't currently but we could, then you could make a display that showed your family tree and change the size of the names based on either how many of those names were in your tree with that surname or how common that surname was generally speaking there's things like that you could do for sure. Oh, that'd be great. That'd be a cool okay. So some other developer take I don't have I there's no more room for more rabbit holes in this office. The API first because I don't think we have the counts exposed. Oh, we don't. Okay. That's a feature request. We're like, for example, this one's going to be much better. There's a thing in the pipeline now to improve the gathering of multiple profiles. And Greg, I imagine this will help the fan chart and the the fractal one. So we'll be able to leverage some of the other stuff we have going on in the background of wiki tree to grab a whole bunch of profiles at once so that you don't have to iterate through them. It's like this one you can kind of see it gathering each generation and it should just grab them all. You will be able to say to retrieve the cc7 number in basically one or two requests all profiles. Oh, that would be amazing. So my six degrees app, which currently is not integrated into this, that could make use of that. Yeah. Okay, I'll wait till that's done before I had six degrees. Okay. Very cool. Okay. And the timeline now, I think there's an updated version of the timeline, right? This isn't the most recent version. I'm trying to remember what I what the last merge I did, I'd have to look at GitHub. It may have been even today that well, let me see. See if I can go. All were merged today, but maybe it was just documentation. Okay, let's go family timeline. Yeah, this look this does look different. Yeah. So I'm highlighted here. Oh, what happened? Well, if I if I highlight Dwight. Hey, do you see that? That's cool. That's cool. And if I go to Lyle, I can I got to say, I'm growing up, my, my father was Patrick and his father was Thomas and then it was Patrick and Thomas. And on my mom's side, it was Alexander and Donald and whatnot. Having all of a sudden having a Dwight and a Lyle and a Luther in my family tree was wild. Herbert never had a Herbert before. That's very cool. Look at that. You can just go through. Okay, I can't scroll up more. Very neat. Are there other features of this Brian that I'm missing? I think that interactivity is very cool. I don't remember what all got added to it. You know, I wasn't the main developer of this. So I, you know, we're leveraging other people in the community, which is great. But it means that I don't I don't know all of the things that are there. Okay. I have zoom. I'm using the zoom. I'm using my trackpad to zoom in and out. But I'm kind of loose. I've lost track of the top part of it. So let me just maybe go back to this. Now, now what have I done? Just reset the view on you. What's that? It just reset to the fan chart view when you reloaded. Yeah, it didn't. It didn't actually give me this top part here. So but anyways, there we go. Okay. Were there other views, other things you want to talk about Brian, about the dynamic tree that's happened this week, or views that are almost ready to add that you want to tease us with? So most of my work in the last week has been either integrating work that like you and others have done, or in sort of the supporting code, you know, a lot of work that several people have done in making the views easier to add, and tweaking, you know, fixing some bugs that have showed up in that, and things like that, and working on integrating it into the main wiki tree site, and then adding some features to the API to make the apps easier to write. So that's all kind of behind the scenes at this point. I don't have any new views in development just yet, but it's coming along and lots of other people are polishing the ones that we have, and with the fractal view and other things we're getting new views in as well. Good stuff. Any other questions in the chat, Mindy or Aowyn? No, but may I say something? You may Aowyn. I just want to say this is so exciting, and I can't wait to see how it all comes together, and just I want to say a huge thank you to you guys, and to everyone else that's working on this, because it's I think it's just fantastic, and I'm excited. That's good. That's good. It's amazing what you guys can do, because I don't have like that technical skill, and so I'm just... Yeah, we're just here as the diehard fans of the extensions. We like our wiki tree toys. Yeah, that's good. That's good. Well, we like creating them for you. That's great, and you keep us grounded. But we have a giveaway, don't we? We can give away a t-shirt. Yeah, we can. Okay, so do we have a t-shirt winner? That's why I asked Mindy and Aowyn. Between the two of you, you were supposed to pick a winner while I was laughing away. Mindy totally picked a winner. Mindy totally picked a winner. Are we picking out of the people that were here? Yes. I would say Tommy... Tommy Buck. Tommy Buck, you win a t-shirt. We haven't had a time to make it into a banner yet, so sorry. But yes, congratulations. You will get an official Hacktoberfest t-shirt. Is that right? Yes, it's a lovely orange, a lot like this. Very cool. Great, hopefully you'll have yours soon. I'm looking forward to having mine soon. I actually have a green genealogy one, but it's kind of rumpled in, and people came online sooner than I expected, so I didn't get a chance. Sorry about that. No, no, that's okay. Yeah, yeah, yeah, yeah. Excuses, excuses. This is a t-shirt I got from one of the math conferences I helped out with. Most of my t-shirts are from me. So the trick, the challenge is to be involved with wiki tree long enough that I have more wiki tree t-shirts than math t-shirts, but I don't know that's going to be you. This is a good goal. That's a good goal. So Greg, we're going to have you at Roots Tech. Yes, I'm so excited. One of the, really the only time that wiki treeers get together in person. Roots Tech and out in Salt Lake City, we haven't been able to do it for a couple of years for obvious reasons, but so finally, again, is it late February or early March? It's March. Second, third, and fourth. I've got my plane ticket. He's ready. I think Brian is going to be there. Alessia, are you going to be there? I'm not sure yet. I'm waiting to see how Corona will evolve, because I might not be able to enter U.S. Last year we weren't. Oh, no. But I'll be there. Greg will be there. I'll be there. Anyone will be there. I'll be there. Jamie will be there. Mindy. So yeah, it'll be a good crowd and get you a t-shirt. Excellent. Definitely. That's great. Good. Well, thank you everyone for coming out today. Any last words for anyone? What do you want to say? Keep it up. Keep it up. Okay. Well, thanks again, everyone, and stay tuned this time next week, and next week we're going to focus on browser extensions and some of the functionality that's been added there. So we'll take a deeper dive into that aspect of the project, and we're almost halfway through the month. It's the 13th. It's not Friday the 13th. It's not that scary. We're doing great, so we'll continue on doing so, and we'll see you next week.