 Thank you for joining us. We're at Rootstack at the Victory booth and we have Lesh, Jamie, Chris, and Brian, and Greg is joining us from his cruise. Hi Greg. Hi there. How was everyone? Busy. Busy. Oh, is the booth really busy this year? Yeah, you're now. Can you guys hear me okay? Can you hear me? That's good. I thought I heard Azure's voice but I don't see Azure anywhere there. Yeah, I'm off to the side here. All right, so we have some questions from the DGG post. The first one that was asked is not sure if this is a technology issue or not. A few times I've searched for a person they don't appear on the list. I try and without a date and with and without a location. Then I search for one of their parents and they appear on the list. When I open the parents profile, the original person I was searching for is listed as a child. The name and date match what I searched for but they did not appear on my search results. I'm sorry we came over here. We couldn't hear you guys so I think we're going to be out of the conversation. I apologize because Azure set this up beautifully. We have two angles of the booth and that's a beautiful monitor over there. Actually you are twice. So now everyone speaks that. Did I ruin it when I joined in? I hope somebody else is going to answer. So it was about somebody searching and the person not showing up to search results. So I think sometimes that happened. I was going to say but they said that they searched for the parents. The parents show up. Yeah so I think sometimes that happens if the first name, if it's spelled slightly differently and it's not one of the known variants. So like before we added first name variants if you search for like Elizabeth with an S and Elizabeth with a Z it wouldn't match. So that could be it sometimes. Actually we would need an example to test it out. Yeah if there's an example it's always good to have. Should just be a five minute delay like with space? Yeah so when you're doing a search on the back end because there's so many millions of profiles we use an index that updates regularly. But if you create a profile that won't immediately be in the search index. And so if you create a profile even with an unusual name and you know the spelling because we've just created it. If you go over to search and try to search for it it won't be there immediately. It's a few minutes delay and then it should show up. And then in terms of the spelling we use variants that are known for both the first name and the last name to try to help find them. But it won't do sort of every misspelling or every variant. So if it's like Jamie was saying if it's a different spelling than what the code is expecting it may not match it up to what's in the tree. Gotcha. Judith said in the comments that it was an exact match. So it'd be helpful to have an example just so we can see if there's a bug. So yeah I mean it is also important to know like we've made a large number of infrastructure changes recently. So we broke a lot of things that needed fixing. So Jamie's been very busy and Brian's been very busy like we've had a long queue of real legitimate bugs. And so there's a possibility that this is one of those bugs. But probably just got to like post the exact example in G to G Jamie will look at it and then she'll try to replicate it see if you know she can establish when it happens and if she can then that'll be something that's easy to fix. All right. Okay the next question is when will wiki tree's new quantum computer with advanced? Oh rich data. So I think that's a good team got a question. Well actually I went to a workshop on quantum computing last fall it was really interesting. Oh okay. But I don't see a direct implementation path yet for wiki tree but it was it was interesting. I don't again I don't see where it fits in yet. But the fact that you're able to write code to run on a quantum computer is I think it's exciting. It's not useful in our world yet but it's it's pretty. And the AI like you know I mean there are because it's the buzzword of the day you know at a conference like this there are many people selling something or promoting something AI related talking about it and and Rich is I think part of like Rich's point in that post that I saw you know was maybe asking about what is the future of AI and wiki tree in collaboration. So I think there's a serious thing to to talk about in that. You know what what could be replaced in a few years on wiki tree. I really did discuss it last year as I remember but we couldn't find any useful use for us. Yeah so we like we had a narrow discussion about how how it could be used to help write biographies. You know would that be helpful if there was an app that took what's on there and automatically reformatted what's available you know into plain language and then you would look at it and say yeah you know okay I'll change something where I'll keep it and and maybe that would be helpful and I think some some developers have even looked at creating that. So I'm sure we return to this in the future but at the moment it's not suitable. Yeah I think that probably help how non-geniologists search for their families you know could change with AI you know I guess that becomes more how people are interacting with search engines you know like like I remember you know 10 years ago I envisioned like why doesn't why doesn't Google you know take information on different genealogy sites to put together a family trade like if somebody just wanted to browse that you know why can't they pull public information already just if it's identified you know this is the person of this person and it's easy to prepare this person on another side and we took steps on wiki tree that might try to make that easier you know by linking you know with family search that you find a grade on other sites so that it would be easy for any computer to know that this is the same person right like that's a lot of what you're doing with wiki tree plus when we're connecting those find a grade of memorial pages and search engines haven't done that Google never did but but probably with this next generation of search I can see that happening because there's like Google person ID right there is something like that but it's not I mean it's you can see that in on wiki data they usually replicate there but I don't they don't really use allow this to be used externally very much it's more like Google things okay so the next question is from Denise Jarrett she asks it would be nice to see a schedule of the updates you have planned this year would you please share what is coming during the second order wouldn't that be nice Denise yeah yeah um so Denise and everybody like you know we're a small team like this is most of the tech team right here essentially you know and nobody here is full time so we do our best um and there are so many different things that happen that interrupt you know like like let's say there's this bug that we just got reported about search and maybe that's an important one because it's it's causing a lot of matches not to happen and so then we shift gears and we try to fix that bug and then it's not easy just to release it you know we have to Jamie you know has to do the QA after we fix that bug to make sure we haven't broken other things right and so we don't know how long that's going to take to make sure that we haven't screwed up anything else so then we released that and the thing we thought we were going to do today we didn't do right because it got it has to be pushed out yeah just like in hospital if the emergency situation happens after these surgeries are scheduled for that day so probably a better answer I mean I will say an update of what I said in December or January some of you will have seen that I posted this once ahead for next year we are working on a redesign you know we're working with a separate design firm so that is ongoing it is going a little slower than I would hope and it is a long and painful process that has just begun and that that interrupts a lot of other things because other things have to be set aside while that's going on there are other things we have wanted to get done somebody could remind me what we there's some search improvements that are right there's that short list of search improvements and those should be coming in soon those got pushed because of the infrastructure updates that were required you know to stay secure stable and everything we had to make some changes to the underlying operating system and database and that took a lot of effort because there were you you know some wiki trees been around a long time and some of the legacy stuff didn't work as well with the newer versions as might have so those all needed updates but that's knock on wood etc largely I think in our review mirror there are always things that I think would be good to do but the big stuff is done so I think the the search improvements are good the invitation is a lot of progress was made on that last week yeah I'm not even caught up with you because of root set so so one thing I'll briefly mention is the improvements to the invitation system some of you might know especially if you try to involve living family members in wiki tree our system has become convoluted you know we drew back on privacy a couple years ago and that when you carry out the consequences it was essentially you know in order to invite invite somebody you're you're recommended you're supposed to create a profile for them but then on the privacy side we also sort of figured out well wait a minute our privacy rules mean you can't create a profile for somebody without getting their permission so essentially you're we were asking you to ask somebody if you could ask them to join me so we're gonna fix that you know like we've we have in place what I think is the the technical changes and also the policy changes that will enable that and that's pretty close to being released hope to get that out but there are a lot of things that get away is there anything else that's close most everything in my call and other than the search improvements are bug fixes so yeah yeah there was the the variant names you know something that's relatively easy to do that we've wanted to do for a long time you know is a way for wiki treeers to edit the variant names database that we use so those alternate alternate first names and alternate last names that we were just talking about with search we've relied on what was a very good database um from this variant names project uh but it's to edit that is difficult because the maintainer of that it doesn't doesn't really isn't able to focus on that so we ought to be able to allow you know members to edit that and that's probably a fairly simple thing to do but we have to make thank you he's not in this conversation before I was so rudely interrupted the other variants making that accessible to wiki tree users in some way yeah so at least at least certain members with certain permissions would be able to edit that variant names database so that's something we hope to get through um but but everything really is going to take backseat to the redesign for a while and so there's going to be very little uh that probably is changed on the front end because of that until we can start working out that and then patching and solving the innumerable bugs and problems that is going to cause for the community but the reason I should also it's going to modernize the html uh it's going to be more accessible uh both in terms of devices and in terms of uh other accessibility issues navigating the page by keyboard all of the things that I think are important for a modern website to have and it's going to have internally better books so that people working on the victory browser extension and so that our own developments can better manipulate the contents on the page so there's going to be a lot of uh both useful and technical improvements that come along with the redesign I think yes we're hoping to do a lot of this simplification you know I mean as Brian was talking about with the code just with you know the html you know and the front end stuff gets layered over time you know you make one change you don't necessarily go back and re-examine everything to make one improvement and over 16 years you end up having a lot of things that are inefficient that are doing things that aren't done the right way so we hope to take this opportunity to simplify a lot of that in part because as Brian said um an increasingly important part of wiki tree in the future of wiki tree is what independent developers are doing what people like Greg are doing with apps on the browser extension is going to be made easier through this reason but the browser extension will need to be redesigned a lot yeah and then and then the browser extension is going to be completely broken and before Ian and many others are going to have to yeah he told me yesterday he wasn't looking forward to fit wasn't looking forward to these improvements and what about the tree apps will they be broken to or are they still going to be more quasi independent means that there's anything should change there in the apps section that should be that's pretty self-contained why design it uses the api to gather the data and it builds its own content in uh you know a frame essentially uh that's contained within the wiki tree page and so uh that should be relatively unaffected the stuff around it will change with the redesign uh but it doesn't talk generally to those external elements we might need to adjust the index page a little bit for where like we have the the name and the view selection you know and then when we hit go then it draws things and so that part of it might need a little bit of an update for the new design but that'll be very small and it won't affect the view code itself really there are going to be aesthetic UI things that people will have to adjust um that's one of the hard things about doing this redesign is that because of so much decentralized on wiki tree so many people even just you know creating project pages and free space pages and profiles where maybe you're doing something it isn't just plain text um one of the reasons you know years ago we set a style rule to to try to minimize the amount of creativity members could have in these ways is because of this because it makes it those pages fragile when then we try to change something in our style you know the basic font used on wiki tree will change you know these basic button styles and things and and that's all going to cascade down and have possibly little consequences and and most of that in the big picture is easy to fix but it does create a burden on people like Greg you know maybe just because you know this one view now it doesn't all lay out correctly anymore and he's going to have to spend some time on that I'm sorry Greg that's okay that's okay as your just before I leave is are there any questions in your in the gdg post that might be of interest tree apps more related ones that I can answer um no no okay no questions about the tree apps okay well I'll let you know while I was on the beach and uh and trying to relax I relaxed by programming things in my head so I've got some notes there's some updates at least you didn't have your computer with you you were just doing it on paper yeah I was just doing yeah and there's no bugs at all in this in this version of the program you've run it and it's fine yeah I run it it's gonna work anyway I'm gonna say goodbye for now and maybe I'll pop in tomorrow but uh enjoyed the rest of your rest of the day at roots tech and I'll see you later wish you were here hi see you Greg see you bye bye so we did have one question that's shown up on here and on the gtd post but it it's actually relating to the roots techs class chef sessions and they have a post on the top of their page that they are experiencing technical difficulties with the classes so um just watch that main roots tech page for updates about that um we do have a question a couple questions from Stephen in the chat one person submits three dna tests of his upload three dna tests with three different misspelled surnames how can it decide which name is correct I don't understand any misspelled surnames so so it's so let's say I have taken three different dna tests so I attach them to my profile what are the misspelled surnames yeah so maybe Stephen if you can elaborate a little bit further on that one and we'll go to your next question um which is can't read it so I found a find a grave ID and when you search it it's not available anymore wonder where it went uh I wrote them and they didn't seem to know either suggested searching again well find the grave on finding find the grave uh uh the person who created the profile is able also to delete it so that's most likely the case that happened there's also a possibility that it got merged into another memorial but in those cases uh they they do present a link where you follow to the new memorial so most likely this was delayed deleted by a creator or you got to lean on the end of the last one you talk okay let's see if we've got any more here okay here Stephen's talking a little bit more about maybe AI the test with them point to each other and make three surnames acceptable is these well in wikichree with the dna test the the name is uh irrelevant because it's attached to a profile by that profile's id if you don't uh use the names directly with the with the dna tests so i'm not sure i'm trying to think what's uh i'm not sure i understand what's going on there right maybe he's talked about um in the when you go to the dna um correct uh sorry where you can see all of the people who've taken a dna test for that surname oh oh okay you know robinson dna or yeah right all right and so i bet we don't account for variance right we don't and that well that's an interesting question yeah yeah because that just pulls up the dna test attached by profile with their names right it doesn't suggest that you know smith versus smite or something like that uh is on there i don't think we use the variance there which that seems like that surname usage like i almost forgot we had we did this i remember doing it but i haven't looked at those pages and ages so i kind of forgot they were there um but if you're doing uh a wide dna is a surname project um you would probably be just as interested in those variants yes so i guess you know as it is now you would just have to go to the different variants yeah you that's interesting you can use wiki 3 plus uh for that uh you can also search there for wide dna tests and profiles with wide dna tests to replicate it on them and uh combine that with any last name search so you can try all three variants of the last name and you'll get different results hey thank you denise that's a very nice post oh and rich had another question about uh when and how wiki data is updated so a lesh can speak to that uh wiki day wiki data is updated once a week uh so after uh after show your face like your number after i uh get the database done from wiki 3 and then during the processing i import the all the wiki data info do additional connections that are possible based based on the uh data enter from profiles and if there's something new on wiki data itself so it's usually updated on monday uh and when the i publish the results they are accessible in wiki 3 plus for searches so all right does anybody else have any other questions from the i haven't even followed most of the comments i missed the most of directly but you've been calling out the questions yeah yeah no i i mean i will uh i will say you know just for those of you who aren't here you know i mean i know very few people can come you know what what makes roots tech cool i mean there are 20 000 people here so so what makes it valuable is is different for different people there are you know all kinds of presentations going on there are all these parallel tracks so people learn a lot while they're here uh for me personally like i i end up never going to a presentation even though i would like to go to some because i just have these conversations with the other team members you know with wiki 3 years you know it's like my one opportunity once you're here to speak to anybody face to face um and then also with other people in the industry uh you know wiki tree does collaborate does work you know with other organizations in certain ways and we're always you know working to integrate better like our approach is very open you know we don't have a closed garden and we want the data we want the tree that all of us are growing together to be used forever um and and i think that uh to make sure that happens in other people other genealogy sites and services need to be able to use it you know like so so others seeing the value of wiki tree and us knowing you know how it can be integrated if not now later um is is valuable so making these connections is valuable here and to anybody who's who's thought about coming to utah uh this is the time to do it and and we'd love to see you next year okay we do have another question looks like from yoke if your schedule was totally free what would you like to work on um so i can't answer that because my schedule is free i mean i i do work on what i think is most important wiki tree um as as to most wiki trees and to some degree everybody on the team um but but we all have our disagreements i guess sometimes about priorities what should be prioritized for maybe what what we didn't do i doing um it's all so i think everybody should answer that question if they want to thank you would you be doing something different well it's always a balance of needs right because you know one of them the satisfying things is to make something new for users right where they they see something on the page and they're like oh wow i didn't know i could get this out of wiki tree or that i could do this with wiki tree that's very satisfying to be able to make right you'd always be you'd always be adding something new it never fixing something right because you never really fixing something in the bro but it's satisfying to say okay that box fits but not in the same way as someone buys lighting up at a new feature right and so uh and in the same way that there's a lot of background engineering that you know we've accumulated over time there's some technical tech and if i could suspend the world you know and do like a time warp and spend a few months re-engineering some things absolutely i would love to do that because that would also be very satisfying and would set you know wiki tree up but you know it's always a a balance of where do you spend your time and stuff like that so hopefully you know we fix some bugs we add some new things we keep the infrastructure running and so i just try to respond to what everybody else has seen from the sort of important thing at the moment and jamie you would probably like to hear more complaints i would imagine if it was up to you then you know you would you would want to hear about more problems i mean they are good to know about it's better than like someone not reporting something and going like oh yeah this has been happening for two years that's okay sometime ago i delegated all the listening i do to jamie you know like that sounds horrible i know that sounds really bad and and that of course is an exaggeration it's mostly true you know it's like so that is a very hard job jamie is on is on point on bugs and and hearing from the community what we're doing wrong uh or what features and problems you know are overdue to be fixed and then and then she also does qa like a lot of people wouldn't know what that is um and almost everybody would underestimate its importance um qa stands for like quality assurance right so that's ignore what it means it's testing to make sure nothing is broken um and this this is like critically important as far as i'm concerned because wiki tree has private information on it you know like our our most serious obligation is that we don't reveal private information that has been entrusted by users you know if if maybe you're like a genealogist who just works deep in the tree on open profiles maybe this doesn't matter to you and and that's awesome but it does matter to to many people who participate on wiki tree and we have made promises right you know like like we make promises every day on every web page that we protect this information on living people and so every little change we make you know we were talking about the search engine so we're going to fix a bug in the search engine what if we revealed you know now that search engine is revealing private information about living people that it's not supposed to we have to make sure it doesn't and because wiki tree is so vast you know at this point you know has so much going on in so many different ways there can be something that emerges uh that we completely did not expect you know i'm pretty much anytime we make a major change all these things that we did not expect to merge and so jamie is on point on on that you know making sure that we didn't break something and fixing it so so jamie really has to do a lot of things that nobody would want to do is there anything you get to do that that you would like shoes to do i mean you love genealogy and you'd love wiki tree yeah deep love yeah i mean like if i could choose to do anything out wiki tree would just say genealogy all the time but i do enjoy working on this on this night and i think i think you said something to me which really you know years ago made made me want you to be a team member like you said that the wiki tree is what i would design you know it was like what i would want to genealogy today you know and that doesn't mean it's perfect but you know pretty much like that's your vision that would be your vision if you had started it um so so i love that um so i hope you know even though a lot of what you have to do day to day you still get some satisfaction definitely and denise asked if i needed well leshton gets an answer that one i do work on what i want yeah because of the way wiki tree plus um is set up like a lot of people will get confused about wiki tree and wiki tree plus part of the reason we set you know a lesh started not as a team member he started just doing wiki tree plus as a developer like using the data that was public and even though he became a team member and does some things on the core of wiki tree most of what he does is still in this sandbox that he can't break for the most part like what i was just saying about the qa being so important that we don't break things a lesh can't really break important stuff on wiki tree plus i mean he can but it only affects wiki tree plus and because most of that data he's working with is not private he can't expose private data accidentally and so he is able when he when he hears from one of you that you need this he can do it in a way that is very different from the process that we do on the core like on the core you know we go through this process of like we hear about it we think very carefully about it it goes into the q we prioritize it at some point makes it to the top of the q and gets fixed and then it gets tested and then it gets pushed out and and back to what you know denise said about that schedule that's you know subject to all these different things and lesh actually has this freedom if maybe it's the middle of the night and he does think it would be fun to just solve this problem that somebody had he could do that and ignore the rest of wiki tree because it's on wiki tree plus so we did have another question on the g2g post um that's pointing to another g2g post it is um from t stand in what has happened with g2g week so um okay that's something probably we broke right like jenny you would know if anybody would know it's the rss i know there was something about like not enough days showing up here's the here's the original post i don't know if you want to yeah i need to look into it okay still so i read that before we came here that's the one that i'm thinking of in terms of the number of days showing up in the first uh first what was expected um i would need more detail and this is something that jayme is great at she'll look at things and so i don't always look at the bug bugs that are in g2g i i get them filtered through jayme and chris and get assigned to me and whatnot um because when i was looking at it it was doing what i expected it to uh it's possible that the system upgrade that we did uh which changed the underlying uh php engine there were some very subtle things that uh got deprecated and so some of it just broke and those were obviously we fixed and then there's some things where it broke more subtly and those are harder to find and so it's possible that there's something going on with that that now the feed is not uh working the way that you expect for various tags uh my only suggestion would be to give specific URLs that you're going to or like what what tags you're following and what you're seeing versus what you expect to see and all of those details because it's a complex uh system all of those details make it a lot easier for us to make it happen and if i can make it happen then i can figure out why it's doing the wrong thing yeah that's great okay and then we had one more question from the g2g uh what useful changes or features might we expect in the night next six months from peter robbers from peter where's peter first of all we already answered it and apparently he wasn't listening the second of all like he's around here somewhere okay so we have another question here that's what i need to develop for this i mean that is a challenge go ahead chris i'll read out loud here uh resolving technical debt could be satisfied to the developer so is it uh but the community doesn't give the feedback on those successes because they don't see them yeah yeah exactly dr yeah i think it was just like making um explaining really so this one's me would be possible for a member of the team to respond saying that they saw the bug when it is posted in g2g sometimes i forget to go back and post what usually you do i remember yeah and like especially if like there's a bunch of different reports on the same bug uh i'll miss it so definitely make sure that it's tagged bug and not tracked bug because i don't usually go back and look at the track but sometimes people tag it with that and i think it's already yeah and i think it's already looked at um so i'll try to be better about that sorry um yeah send send me an email they're nice very nice jamey at wikitree.com thank you james uh is there likely to be a capacity issue in the near future for wikitree if so are you in addressed decision well there's there's more than one kind of capacity right i mean there's the technical capacity in terms of what the servers can handle what the number of users the number of pages viewed per day and the how many profiles are stored um and you know that you can expand infinitely if you have the money to pay for it uh and so that's the balance there is trying to make sure the page is performed and right now i think we're in a good space the recent upgrades gave us improved performances from the underlying uh services and and flexibility to add new servers yep so uh you know i will get seamless way yeah so i think we're in we're in good shape there to handle growth of wikitree more profiles more users i don't think that's the another few thousand then we'll look again there you go no i think uh from the the site in the database we're in good shape for growth of wikitree absolutely the community part of it you know that's a whole separate social thing you know the making sure that as people come in they become part of the community and in terms of the group here you know managing the qa and the the future development stuff like that that's a separate thing yeah technically speaking um you know as as brian said we have a lot of flexibility we're on aws that's amazon's you know cloud hosting service and so the way this is set up it's very easy to expand capacity as is necessary that costs money um most people you know wonder how wikitree or if wikitree has any money we're we're very low budget you know we keep things as inexpensive as possible and that's very important to me to keeping wikitree free forever um you know maybe even if we could pay for it today what if we can't pay for it tomorrow you know if you run up your expenses in the short term that could cause you long term problems and we on wikitree care deeply about the long term but i'll tell you that the balance is very comfortable right now like you almost everybody participating in the discussion doesn't see any advertisements so you have no idea how wikitree has any revenue but if you log out you will see some advertisements i still love the opinion that those advertisements are relatively inoffensive and in most cases fairly useful because it's mostly genealogy stuff most of the people who see those ads are people who might be interested in what's being offered so i don't feel bad about that balance um i hate most of the internet these days when i go to a web page and it is overloaded with ads and you can't see the content and so um we don't do that you know we could raise revenue like we could if we had to expand capacity you know we could always dial up those ads a bit if that's what it came to so when i say we're comfortable that's what i mean is that like right now we're not over commercialized we're not hacked with ads so if we had to you know so i think we're good on capacity okay the next question from duck do you have any customer view of your backlogs is that what it says i think partially this is a question that's been asked and considered many times like at at one point we had like our queue in a more public way and to some degree we were trying to use g to g as the public queue so that like uh members could see what we're working on the tough thing about doing this um you know partially is is the privacy aspects like the team we need to be able to have conversations on the core about the core that can't be exposed to the public um and so so yeah we we can always do better of a better job of communication you know but that's not without cost right so if the team spends extra time communicating about what we're doing that's time that we're not doing other things so it's always a balance you know because wikitry is the evolution of the site is so collaborative with the community it can't be done you know development can't be done in isolation uh but you know it also can't be done all out of you okay and there's another question from steven about listing the siblings and half siblings and separate lists when wikitry lists siblings can it separate the list into halfs of them full sibling lists rather than hovering over the names yeah you're gonna say something wikitry plus does that the extension i mean the extension well the browser extension yeah yeah the browser extension does some stuff listing siblings and children yeah the main site does not um and i i love the way we have the browser extension working with wikitry right now um you know part of the philosophy of wikitry is that we want it to be relatively simple and accessible so it's got to be kind of lowest common denominator in some ways you know you don't always want it we try to be very careful about adding computation you know so so what what might make perfect sense to steven and 25 percent of the other users of wikitry might be visual you know clutter for 75 percent especially yeah and it and it's a balancing act that we never know for sure so maybe this is something all users should see but the balance i love about the wikitry extension is that you can customize what you want to see yeah yeah so if that is something that one of the independent developers can add if like ian can make that change pretty easily it doesn't have to go through this queue of considering well is that what all users want or is that just what steven wants you know like we have to think about this um and like many of you have participated in discussions on g2g like style and policy discussions that's a very long and painful process some of these things we might go to g2g like do you want to see the siblings listed like this you know and then we would have this discussion you know maybe make a proposal about how we're going to change it go through this long conversation okay well maybe we're going to propose something slightly different this might take months and that's all before any changes happen but as far as the extension is concerned maybe ian just hears from steven that this would be a cool thing and he adds it and it just becomes an optional feature on the extension just like that so i love that yeah so um another question here for just a comment i guess yeah thank you rubber all right i think that's all the questions that we had and i think we'll be stopping soon for the three photo we're gonna take oh oh that's happened too yeah so if there's no more questions from the chat let's just double check here okay i have something for me but all about yeah okay so i guess we'll go ahead and uh sign up be sure everybody to tune in at 2 p.m mountain standard time which is noon eastern time for the next live cast we're going to have vetsy co and hopefully you and i'll be able to join us we're going to be talking about events and challenges the question and answer session for that and then tomorrow morning uh 10 a.m mountain which is uh new no yeah noon eastern is going to be the usbh project talking about the 1880 census work that's being done so we can ask all your questions about that there that's a big thank you everybody for tuning in we'll see you later thanks guys