Hello, happy weeky tree Wednesday, weeky tree challenge Wednesday. How is everyone doing? I know it's we have people from all over the world watching so I can't really say specifically good morning good afternoon or good evening. But I hope everyone is doing well. We have it's going to be exciting live cast. I'm going to just tell you right now. I think it's going to be pretty exciting. So we'll probably just go ahead and and just start. So we'll go ahead and introduce everybody who's in the stream right now. So my name is Sarah. I'm a weeky tree team member. And then next to me we have Mindy. She's the overall coordinator for the weeky tree challenge. We have Emma. She is the the captain for Gina's week. She's can't she can't be with us, but we do have a little snippet from her. She recorded something for us. So she will still be with us. Just not lie. And below me we have Joan, who is the captain for Nathan's week. She is very tired from all the hard work. And then we have Nathan, who we couldn't make it with us last week because he was sleeping, but he has come on today. This is why we have it at a different time. So welcome everybody and thank you for everybody for being here. And so for those of you who maybe aren't familiar with weeky tree or the challenge is your first time watching.  I'm going to let me tell you a little bit about weeky tree and the challenge. So weeky tree is a community of genealogists who are working together on a single family tree. In other words, we collaborate to go and to grow an accurate global tree that connects us all. And most remarkably, it's free. And the weeky tree challenge is our year long event and part of our year of accuracy where each week we take on a team of each week.  Our goals to improve our accuracy on weeky tree, add more family connections and make more friends. So that's pretty much how that goes. And then also if anybody has any questions throughout, please post them in the chat. We'll throw them up in relevant and ask them when we can. Okay, now I'm going to. Go ahead, Mindy. You're ready? I'm going to take it away and tell you about those points a little bit. Now there's two ways you can earn points as a participant. And of course, we don't do it for the points, but that little bit of extra challenge is motivating, highly motivating. So in adding a direct brick wall ancestor, we award 10 points per ancestor than any nuclear family relative. So when you add their siblings, their children, you get one point for each of those. And trust me, those add up. And then can we go ahead and go into collaboration? Collaborate. And this is how we do this. Wicked Tree is a collaborative site. So this challenge event has been wonderful for us. On the left, you see a spreadsheet. We have a new one each week. People can go in, put their names. They have their names down there. They can put the profile they're working on. That way when you have 30, 40 people working on one person's branches, they aren't tripping over each other. They know what's being worked on. On the right, you see the top of the G2G posts that we do. And that's where people can go in under the great-grandparents and say, hey, I broke a brick wall. I found this person. Or sometimes just say, hey, this is what I'm working on. Or this is a question that I have. Thirdly, is Discord. And we couldn't do it without Discord. We have, this is a global site. We have somebody on almost all the time. There are people in there that you can just talk to. You can have them look at a record for you. If you just need a second set of eyes on a profile or you need an obituary. Or you just want to cheer somebody on. Feel free to come and cheer people on if you're signed up in our Discord room because it really does keep things going also. We use Discord a lot. I guess we can, we want to show our, we want to look at the stats first and then the MVPs or we want to look at our MVP and our top five. Let's go ahead and do our MVPs. That would be our most valuable player. So now Carol Keeling was the top five MVP. Yay this week. Carol. Uh-huh. With an incredible 110 bounty points. That was amazing. And then we have Hillary was second. Maddie Hardman was third. Donna Bowman was fourth. And Anonymous Sharky was fifth. And they worked really hard. Let me tell you all of them. So yeah, thank you. Awesome. And the Hillary is watching too. I don't know if anybody else is in the chat. Hillary, yay number two. Okay, let's look at the stats now really quick. I have them. There we go. Let's, let me refresh because who knows what could have happened. I know. We have people that work right up until the live cast working on these profiles a lot of times. So now these are the, the score sheets that we go off of. And it's the status of everything we've done during the week. Now the total points are for each person. Like I said, Carol was our top one. She had 208 points, but total points for all the people working on it this week was 1174, which is awesome. Now we have some people that weren't earning points at the bottom that definitely does not mean they weren't doing anything. Those people that I tell you are maybe looking for obituaries or proof reading or, you know, working on the space pages, which they don't get points for anything else like that. They're going to show up on the list, but because they're editing, but they don't necessarily have points and they're, they're happy that way. It helps the tree. Now created ancestors for you, Nathan was 152 and that's direct ancestors to you. That's amazing on wiki tree. So now I know you had some of these on your own primary tree already and we're counting everything we add in past the great grandparents. But trust me, you're going to find out how many you get that aren't. And then created relatives. Now these would be those nuclear family members I talked about and 412 additional ancestors were added. Amazing work you guys. They just kept bringing them points and it was crazy. Now bounty points. This is a record breaker for us. Nathan, your team did 610 bounty points. That's 61 brick wall ancestors. Ancestors that were not on your primary tree. So yeah. That's not amazing. Now we also have profiles edited and these aren't necessarily the thing you get points for. We have 817 unique profiles edited and then each time you go in and contribute to a profile. So if you add a date, you add an additional source profiles already there, but you go in and you edit it and you improve it. We have 3896 edits in one week from your team. Crazy. And unlike Mindy said, it doesn't count all of those other things people are doing. Right. So those are those are points. Great job everyone. We have a bunch of people watching who were actually participated this week. So great job. They're all going to go collapse after this. So no, you have to work on Gina's week now. There's no staffing. Rest week is not till a couple of weeks. Okay, let's continue now. We'll start to get into the juicy juiciness and Joan, I don't know if Joan and Mindy will probably bounce off of each other about all of everything that we found. Yeah, on the Goodwin line, we had nine great ancestors for a good win. But we didn't break your brick wall. You didn't. Yeah, I'm not surprised. They tried and that one was just solid. Yeah, I think it would be DNA that would break that one day, I hope. Yeah, probably, yeah. Harry Goodwin, your great grandfather was a cement worker in 1901. And then we found him in 1911 and he were a milkman. Now, one of our members have found a lovely picture of him with a milk cart. And we're trying to get permission to use that. So we're still waiting for that. Okay. We also served in World War I with the Royal Garrison artillery. And was discharged in 1919 with two medals. And then we also found a third great uncle, George Goodwin, who immigrated to South Africa with his wife and children. And that one was interesting just because everybody else, you know, stayed in England. Yes, they really did. You were very solidly planted there. Very, very English. I have Caroline Colline. Yeah, this was quite a difficult line. We actually found five direct ancestors on this land on the mother's side of the family. But we didn't break the cold brick wall. We just got to break off the bad news team first. That was one of the brick walls that I looked at. It was just so vague what were happening within that we couldn't find anything. Yeah, I need different information on different censuses. Yeah, it did. Sometimes he was George and sometimes he had a different name. Yes, yeah. I love that picture of her. I'm surprised because she died in 1899. So I was quite surprised to have found that. Family is great. Treasures. Yeah. Yeah. We're a bit fierce though. We're ready for the big busy. Yeah, that one. This is a really interesting line. A lot of stories. One of our members created a space page with the newspaper reports that she found. I think mainly in the Welsh newspapers. Okay. Do I have that space page? Yeah, there we go. Yeah. George Gingel. Job and his descendants. Bigamy Charge. Well, this is exciting. There were actually several really interesting lines on that. Now, Job himself was just a poor agriculture laborer. So he was a farmer, but a few like George that is listed on there. He was a railway breaksman. He was found guilty of Bigamy. And he freely admitted when he got caught with a second wife. Yeah. And when we looked at Job Gringo, we found an interesting newspaper report that gave details of his earnings and his outgoings. They were quite interesting. They were a very poor family. They were agricultural laborer. And we had. We had Sarah, Sarah Simkins. And how do you, do you say that Gingel or Jim Gingel? Gingel. I think. Gingel. Gingel is the way I only say it. Yeah. That one gained new paternal grandparents and the correct grandmother, which makes 10 new ancestors behind her. And there were actually 21 new direct ancestors on George's line there. Now, William Simkins we found and Catherine Christian withers had two sons marry into those lines. So Job and William Simkins married into different lines of the family. And that merged. Wow. And I don't recognize any of these, these surnames. They're all new to me. You're going to have a lot of new names to look at a lot. 661 to be. Wow. For us. There are also some instances in that line of attempted suicide. There were Fred Gringel or brother-in-law Nathan or attempted suicide. They were tied up with the divorce. Yeah. Right after the papers were served. Yeah. So many stories. I can't remember just what happened. Interesting. We got some, we're getting some interesting stories too. Yeah. And then he had a sister, Mary, that committed suicide at the age of 22. So I don't know if that was just a lot of depression going on in the family at that time. You know, because a sign of the times or if that was a physical thing, something that was being passed down. I don't know. But on the story on that, and you'll get to read that they found some really good information on her. And apparently she was poisoning herself with mercury. And so they kind of got the idea. She was poisoning herself at one point. And that's a terrible, painful way to miserable way to die. They got the idea that she was doing this, but they couldn't prove it and they couldn't get her to stop. And eventually she did.  So she succeeded. She succeeded. And she was only 22 years old.  They say they don't know why her state of mind was. They say they don't know why her state of mind was. What it was. She hadn't gone through a great tragedy or anything. She just. Is this the Sarah that's on screen? No. That's the Mary. That was a nose. Gingel's sister. Right. Right. Which is not. It's a. Brother of Nathan's great, great, great grandfather. Got to get all the greats in there. So. Savage. Yeah. We had. Name. All ancestors on this line. Wow. And 17 direct. Ancestors of Ethel Savage. I don't recognize any of those names. Great. Great. Grandfather. Got to get all the greats in there. I don't recognize any of those names. I think I've got as far as. Front to some Maria. And then we have the. The mother. Roseanne. Buxden. Buxden. I guess. Her line too. Yeah. And the parents were found for Maria Wilkins Savage, which it just kind of took off a little bit after that. Her father was a farm laborer. So, you know, not everybody had big stories and that's fine because you had some really hard working ancestors too that, you know, really hung in there and worked those farms. I did warn you that they were mainly. I'm glad we get a lot of farmers. Not very exciting. Well, all family is exciting. I think. They are. Arthur Edwards. We break some brick walls here. I think so. Yeah, I think we did three. Three role ancestors. And we also found the marriage of. William Edwards. And found his wife's maiden name. I can't remember what it is now. Is it gone? I don't have her notes. I don't think she's. People. We have yes. William Edwards. Silver side. That's a good name. Yeah. We can get her parents, but who knows, maybe some, maybe somebody else will come in and find it. And there are a lot of, there are a lot of bread crumb trails on a lot of these profiles too. You know, we don't. Well, some of us keep research logs anyways, but wiki tree is our research log. So you may see sections where it says research notes and it says, oh, I think these are the two possible sets of parents or the parents are definitely these people, but they haven't found enough sources to where they felt comfortable creating the profile. So you may have even more ancestors out there listed. I was trying to find an example of research. Notes, but no, these profiles have its at the moment. Married in Covent Garden. That's interesting. I have to have a look next time I'm in London. Ellingham. You have a lot of Sarah's. That is it. Yeah. Yeah. There were temporary wall ancestors on this line and 14 new direct ancestors. Wow. That's a lot. So. They killed James Shepherd and Sarah Webster. We found new parents for Sarah. Sarah. They had five children and he was a gardener by trade and his wife was only 30 women. She died and James died at 36. So they must have left a young family behind them. Yeah. And it didn't say that the cause of death on the records that we had on the profiles either. There wasn't a correlation with say her last born child. It was a ways after that. So it must have been something else, but she wasn't that old. No. I found a research. Then looking at the ropes line. That's the line that we're in. Centelina. We didn't find anything new. In fact, we used a lot of the information that you've got on ancestry sources. But we did have profiles for the people that we knew about. There's not a lot online at all for Centelina. It's really hard to find. Most of the records are held on the island. So I've had to get the archivists to do work for me over there. Sometimes a brick wall just can't be broken. Just a brick wall forever. Unfortunately. I don't know that we're going to do it again. I think we have a great 10. We found 11 brick wall ancestors on this slide. Super. Plus the correction to Alfred Ashton's mother. Now you had somebody else, but it turned out research show that her name was Ann Wise. Ann Wise Haaland. married an Avery first, then she married Ashton, Thomas Ashton, after being widowed. So I didn't see any records that they found that she may have had children with a first marriage, but she definitely did with Thomas. And they had eight children. And she had actually been running her father's butchery business with her first husband. And when he died, Thomas stepped in and married her. And the two of them ran the business. So that was interesting. It descended through the daughter and not through a son. Yeah, it needs to be. Maybe it happens. And on those lines, we actually wound up with 41 new direct ancestors, 41. On the Ashton side. Yeah. Yeah. Wow, that's pretty. And that's why Silas Thomas came in or the manor still, the Mount Thresher Shrove. Yes. So we looked at this profile, we've added some information, but this newspaper reports we've not looked at yet. And we're thinking we might still make a space page about that treasure trove, but we're not at time yet. There was a lot going on this week. And I did say for people that watched on Saturday, there was talk about a milkman, an excavator and the treasure hunter, but it turns out none of them are related. So they were just all being looked at at the same time, all completely on different lines that turned out. And then somebody found a nice little newspaper report regarding a family reunion in 1939, when a group of brothers got together and their combined age were 457 years. Wow, that's a that's a lot of years. Smith. Sure. That was a fun line to work on. Smith. But did you manage to get past him? Oh, yeah. Yeah, we found a family that we believe is George Angus Smith's family. We hope it's not the family that you researched and went down the wrong way, but we think we found the right family. And I think what gave us the clue were the sisters called Lizzie. Oh, yes. Yeah. And I think Maddie, they were looking at that line and we were talking about somebody's discord and then all at once she says, just a minute, I'll be back in five minutes. Lizzie's giving me a clue and she thinks it's the right family. We all do. Great. It's exciting. Yeah. And the other thing, George Angus Smith, he worked as a lamp lighter in 1911, which was quite interesting. Yes. Yeah. Let's say more about that occupation. His father worked as a clerk and it was interesting that around the time that father was born, it wasn't that long after they actually went from a coil pen to a steel manufacturer pen. So, you know, really easy to picture, put some character into his, just who he is as him sitting there trying to learn the calligraphy and whatnot. Well, what we call a calligraphy pen now was their pen back then. So, I think that that's all of our new exciting finds, 61 of them. That's brilliant. We do have a cool, what was it, this app we've wanted to show? Profile overview. Mm-hmm. It's just super cool. And once you get used to working on WikiTree, you can go into anybody's tree and scroll down below it and look at the different apps that we have, little widgets, different things. But this one was fun for you. Yeah, and if you keep scrolling down. On this? Yeah. It just keeps giving you all kinds of handy. And you can have it start with anybody. You can start with your great grandfather if you want. But it just gives you all kinds of handy links. So you can hover over or click on where it says biography, and it'll show you the biography area in a snapshot. In other words, did somebody write, actually put narrative in there? Or is it just a he was born in 1732? There's links to the BioCheck app. There's links. Source through the sources. It tells you right on there. You'll see a little icon that will tell you like 10 sources. Another profile, three sources. If there were no sources, there's a little red button and it says zero sources. So, you know, that's how we know we need to go to that one. And yeah, I saw one of those go by and it needs to have some sources added to it. Just a really fun way to look at your ancestors. Those shows you the ones that have images. It shows you ones that link off to other sites. Categories. And if you click on them, it shows like connections. Like I see lines behind. Super cool app. We have a lot of great app developers on wiki tree. They're always making neat things to just make it all better. So that's a lot of fun. That's pretty good. And then we have our final chart. Final brick wall chart. That's where we started. That's where we started. That's where we started. When we started, now every one of those spaces that you see the yellow in it, that is where you needed an ancestor. So those were your brick wall spaces that our teams wanted to focus on.  Every single one of those is a brick wall broken down. That's what it goes to. But that's what we work off of. Well, I do. I assess points using that during the week. And you had a lot of ancestors missing, but they were spread out, which was kind of fun. So they weren't all in the same generation. I mean, you had obviously a lot of research done on your tree too, but we had a lot of fun places we could play in the branches. And then, Sarah, can we look at the percentages? Now this is the fun one because we had such a record breaking week. We couldn't resist, Nathan. And you were doing good once again on those earlier generations. And what the percentages you'll see, we have you when you started with us and then what you were when you ended. So the further out you go, the bigger change that we made. And the biggest changes were generation seven, eight and nine. Now for gen seven, you went from 59% to 78% ancestors now. Wow. Gen eight, you went from 17% to 47%. You're almost halfway through that. I don't know how much. Sorry, go ahead, Mindy. Gen nine math, but it wasn't going to work. Yeah. Gen nine, you went from 3% to 13%. Now, of course, if we'd had more than a week, that number would have been bigger, but people were trying to spread out and do those brick walls. And there are spots where there's those direct ancestors added behind them, but not everywhere. But that gives you a really good jump start. Yeah, it's amazing. Thank you very much. Brilliant. Yeah, definitely. Well, so that's all. I don't know. Does anybody have any questions or Nathan, do you have any questions, comments, concerns, inquiries? No, just to say thank you very much to everybody for your hard work and your efforts and I look forward to having a look around and meeting my new relatives. Thank you. You might not actually go to sleep when we finish. Who knows?  So I take it we met your expectations and exceeded them at least a little bit, Nathan. Definitely. Thank you very much. Thank you. Our pleasure. Everyone did awesome. Good job. So, okay. Well, if nobody has any questions for Nathan or for us about anything that we talked about, we might just move on to our next. Yes, or Joan, do you have any last remarks before we switch off? No, not really. I said to big thank you to team because they did a fantastic job this week. It's been really good. That's been super great. It was 61. That's a record raking. Breaker raking. Breaker raking. Just say that's big. We rock. We rock. All right. Okay. So next we have, and thank you again, Nathan. Thank you for letting us work on your tree. Thank you for coming on. You know, it's a little bit late for you, but awesome. Thank you very much. So we have next, we have Gina. Filbert Ortega. She could not be with us today, but I'm going to quickly introduce her. And then we have a little video that she made. She recorded it for us and she knew she couldn't be here. So she kind of answered, you know, the questions we usually ask and all of that. So first of all, I'll introduce her really quick. There's usually a picture there. I don't know what happened. So Gina, she's an author, researcher, instructor who focuses on genealogy, social and women's history. She has a master's degree in psychology and women's studies and a master's in religion. She's published three books, numerous articles published in magazines and online. And she's the editor of the Utah Genealogical Association's magazine, Crossroads. And her writings can also be found at the Genealogy Bank blog. Her current research includes women's reparation and citizenship in the 20th century, foodways and community and fundraising, cookbooks and women's material culture. And now this is exciting that we have a video. I know before we do the video, Sarah, do you think we could have Emma tell us a few of the locations that she'll be working on with her team this week? Yes, yes, yes, of course. So we have a little bit for everybody this week. We have a large line of French-Canadian. We have quite a bit in the United States. We have England, Germany, I believe Sweden and Denmark. There may be some others, but that's just the first, you know, few generations out. Very cool. So it's going to be a, we have our usual experts in some of those fields. That's going to be a good week. Okay, so let's go play the video. Let's see. Let me know if you can hear it. I can't hear it, Sarah. Okay, can't hear it. Hold on a moment. Let me try. I should have, should have tried to do this before. Sorry for technical difficulties, everybody. So loud on my computer. Why? So I'm going to attempt a quick change over. Bear with me one moment. We will be back shortly. Usually it's usually it's so smooth and like there's no problems. Okay. Yeah, we don't usually have to run video though. So let's try again. Okay. So I'm going to do one last thing. I'm actually going to open the video instead of, okay. Instead of screen sharing? Yes. Well, the still screen sharing, but actually open the video in the file itself. And we'll see how it goes. Chris says you can't do it on a screen share. Like you can't. What happened? Let me, I feel like I've done a video, I did a video before though. So let me try one more thing. And then if it still doesn't work, I don't know. So let's try this again. I apologize everyone. Says you need to play it from the link and not the file.  Sorry. I was trying to work with somebody to find out what to do about it because. I thought it was working. I was like, yes. Okay. So. And I'm so okay. I could try to bear with this. Okay. I could. I'm going to download it really quick and stream yard. Let's me actually play a video file instead. Cause I put it on my screen so I couldn't see anything. I just so I, it's very weird how it doesn't. Work because it's so loud on my computer. So. The noise cancellation is causing it. Yeah. Let's try that. Echo there's echo cancel. This is. I am. I'm going to go ahead and put it again. It's still downloading. Bear with me. It's almost done. Almost done. Let's. Hope this works. I am. Yes. And I'm sorry that I couldn't be with you today. Unfortunately, I have other things I have to do at the same time, but I will see you next week. Now, before I answer wiki trees questions for me, I want to say thank you to wiki tree for inviting me to be a part of this. I'm honored and grateful that you're willing to do some research for me on my behalf. Thank you to the volunteers. My understanding is there's about 40 of you who are willing to delve into my family tree and that's very cool. I'm very excited to see what happens and what you uncover. So let me answer your questions and I know the first question is who is my favorite ancestor. You know, this question sometimes makes me a little uncomfortable because it's kind of like when your kids ask you which is your favorite. You don't really have a favorite. And I never know how to answer this. I will tell you that obviously there's some ancestors that are easier to research than others. And so they're a little bit more enjoyable to research. I probably do have some favorites. I don't know that I have a favorite though. One of my favorites just because my grandma used to tell me about her is my ancestor Mary Ann Smith McNeil. She was married to a polygamist. She is my maternal grandmother's grandmother and she knew her. And so I always enjoy learning more about her and I'm fortunate in that other descendants have written about her. So there's a lot for me to read about her. And so she's probably one of my favorites, but I don't know that I have an overall favorite. But maybe you'll uncover someone and they'll be my new favorite. Right. So the second question I have that I was asked to answer is I've got to look it up here. Any interesting stories to share that you found out about your family? You know, this probably isn't going to be real exciting or I don't know, maybe not interesting to anybody else. But what I love about genealogy is obviously we love it and we love the research and the hunt and the puzzle. But I like it when we can pass that on and add that excitement and encourage younger people in the family. And probably a few years ago, I worked with my nephew to do his Boy Scout merit badge on genealogy. And I asked him, who do you want to research? We had done it for his Cub Scout merit badge. So we had already done some of that for that. Or it wasn't a merit badge. It's a loop, a belt loop for that one. He had interviewed my dad, his grandpa and learned about his Vietnam War service. And so I asked him, who do you want to learn about? And he told me he wanted to learn about my great-grandfather, which was my dad's grandfather, Oscar Phillips. And about that time is when his World War II draft card was available. So I pulled that up. We had already looked at his World War I draft card. And so, you know, we knew what it said. But, you know, in between that time, he had served in the Navy. He filled out the World War I draft card. He joined the Navy right towards the end of World War I. And he got married to my great-grandmother. He met her here in California and, you know, had a son. So in the World War II draft card, he's older. And on there, it talks about having a tattoo. And that tattoo is of a Cupid doll on his chest. So when I bring this up, my nephew starts laughing. And he's like, what's a Cupid doll? And, you know, that really reminded me because I'm such a huge fan of social history and adding context to your genealogy and not just looking at name states and places. How important that context is. So I explained what a Cupid doll was to him. I showed him some examples. At that time, my dad was still alive. So I asked him, do you remember this tattoo on your grandpa's chest? And he said, that's what that tattoo was. You know, by the time he had seen it, probably in the 1950s, early 60s, it had not looked as crisp and sharp as it had when he had it done. And so we talked about that. My dad gave his experience of seeing it. We, you know, we did some research on Cupid doll tattoos and actually they were very popular during this time period of, you know, between World War I, the 1920s, that kind of thing. And so, you know, every time I see my nephew, he says, remember that Cupid doll tattoo? And I just, I love that because, you know, names and dates, that's boring. But here's this Cupid doll tattoo that has, you know, made genealogy seem a little bit more alive to him. And so that's probably one of my favorite stories. You didn't know tattoos can be so interesting. And I'll tell you just, you're probably not so interested in this. But so for that research, we not only looked at his military records, but we also looked at the history of tattoos, especially for Navy guys and World War I Navy guys. I looked at the history of Cupid dolls. I looked at the history of Cupid doll tattoos. I looked at flash tattoo flash for Cupid dolls. So we could kind of imagine what it must have looked like based on what my dad remembered and also what seemed logical. So really the only thing we didn't do is try to narrow down where in Southern California or San Pedro, he got it. But it was fascinating research. So now the next question I was asked to answer is when did I first discover wiki tree? You know, I've known about wiki tree from the beginning because I knew people who were volunteers and who worked with wiki tree. I've met Chris many times at conferences. And so I've always known about wiki tree. Now I have to admit to you that I've never had a tree on wiki tree. So I've used it and I've looked at it and that kind of thing. And I've written about it in articles and courses, but I've never used it before. So this was my opportunity to try it out. And so I'm grateful for you guys for helping me. And I will admit I've had to ask questions because I wasn't sure how to work it. So I also want to say before I go on to the next question, you know, you guys are the ones that are so important in genealogy, volunteers. Genealogy has for a long time been a volunteer pursuit. And the reason we have certain knowledge, indexing, digitization, you know, genealogy websites, wiki tree is because of the power of volunteers. And they're wanting to give back and to help others. And so it's because of people like you that the genealogy world is so strong. So thank you. All right. So the next question is what's my current brick walls?  Some of it has to do with materials that are archival in nature, not being able to get there. But but also maybe not even existing. Probably one of the long term brick walls we have. It's on my dad's side. It's his Chatham line. So his grandma, Oscar filibrit's wife was Mary Chatham. And I know quite a bit about her. I knew her. And I know a little bit about probably her grandfather, her great grandmother. So they go back. They go from California to Texas to North Carolina. And so one of our brick walls has to do with the North Carolina Chathams and kind of the Martin Chatham, who is. Oh gosh, he's he's alive around the mid early to mid 1800s.  In fact, one of my ancestors, he is in the he goes to Texas and then he's in the Civil War. And that branch is the one who comes to California. But Martin Chatham. We never have been able to kind of get past him. There's some people in town who have a similar last name. And there's been some people who've thought that maybe they're related somehow, but we've never really been able to tie him back to, you know, any kind of parents, basically. So now I will admit to you that I don't know if some people have used some DNA to do that. But that's been one of the brick walls for a long time. I think for me also on that line, his son, who is my ancestor, Moses Henry Chatham, you know, he leaves North Carolina for some reason. He goes to Texas and boards with a family, marries their daughter, goes off to the Civil War. And he is later murdered once he gets home. And so some of that story, I've gone to Texas. I've done research in the courthouses and everything else. Some of that story is a brick wall because there's just no extant records. For example, his burial. There's no extant burial marker. We're not even really sure. We pretty much have decided he was buried on their land, but you know, there's no proof of that. So there's stuff like that. The nice thing about that family is there have been questions even after we went to Texas and did research. And over time, new things have become available. So that's probably one of those I need to go back and see if there's anything more available or not. But that's one of the ones that I have. All right. Our next question or our last question is, what do you hope to see in participating in the wiki tree challenge? So I thought about this a lot. And when I was initially approached, I thought, I don't know, you know, I was kind of hesitant. And then as I started putting my tree up on wiki tree, I realized a few things about me. And this is probably something you've noticed with other guests or maybe it's just me, but people who work in the field of genealogy often don't get a chance to do their own genealogy. And so I realized that there's been lines that I've done quite a bit on, and then lines I really haven't for whatever reason. And stuff that I thought I knew and then realized I had no idea. So I think for me, what I'm hoping is one of my lines, which is off my dad's side, so it's Filbert, and then it's off my grandmother's side, the Montgomery side, there's a lot there that actually I don't know. The only thing I know is from a family history book and it's not source-sided. And I think what happened was years ago, I just entered the information into my genealogy software program and thought, well, I'll get back to this someday. And I never did. So, you know, there's these families there in, in fact, some of them I didn't even remember where they were from. You know, they're back in Ohio, they're in Pennsylvania, in Virginia. There are surnames like the Montgomery's and the Harshbargers and the Riddles and the Ranks that I really, I don't know anything. It's unsourced, it's from a family tree book and in some cases there's some stuff in that family tree book, but not a lot. And so I think as I was going through this and adding some information and, you know, I was mad at myself for not having explored this, but also I realized just how little I knew. And so obviously I would love to hear more about that and learn about what you find on that. You know, if you find some great stories about female ancestors, obviously that's one of my interests. So that would be cool. So I'm just ready to hear what you find. And, you know, the nice thing about a collaborative effort is some people get interested or have expertise in something that I don't. I don't have expertise in German research even though I have German ancestors. So I'm just excited to see what you uncover and what you can find. I think that's going to be exciting and I look forward to building upon that. So once again, thank you for inviting me. It's great to be with you virtually, but I will see you next week and hear what you have to say. Take care. Okay, it was muted. But after some technical difficulties, that worked, you know, learning curve, learn something new. But that was Gina. We're very appreciative. You end up watching this later. Gina, thank you so much for doing that for us.  Benjamin asked Gina a question pretending she was here if we can use her photos. Did we ask her that beforehand or not? Cindy, Emma? As far as I know, we can. I'll verify it though and I'll let everybody know. Okay, so we'll ask that. It sounds like one thing she's asking for is for us to expand on the resources she already has on some of the already identified family. So that will be a really good goal to meet this week. It should be a good week. Did we have any other questions that maybe or anything for Gina or if we want to ask Gina or, I don't know. If not, we might head off for the evening. Yes? No? I'm going to take that as a no, no more questions. I think they've abandoned us to go work on the tree. Probably. Yeah. So with this week, since we, because we usually have our live stream at eight, but because we were accommodating time zones we started at five. So it did start at five instead of eight. So you can go start working on it. Get those brick walls and see if we can do better than Nathan's week. Can we break more brick walls? Can we do it? That'd be pretty hard. Who knows? When we put our wiki tree or to the test, they always succeed. I'm also amazed at how much we do. It follows my mind. Mm-hmm, yeah. All of you always so. We'll do so. Yes, we'll close up unless there's anything last minute we want to stay asked to. But thank you everyone for watching. Thank you, Nathan again. Thank you, Gina. If you end up watching. Thank you, Joan. Thank you, Emma. We really appreciate you guys being captains. And thank you, Mindy. Nothing they would notice would be possible without you. And so next Wednesday, next Wednesday we'll be at the regular time, 8 p.m. Eastern Daylight Savings time. And we'll have Gina on. And do we have, she's by herself next week because it's a rest week after, correct? Yes, she is. So it's just going to be her wrap up. And then we have a rest week so you can take a breather. So one more week to go. And Saturday at 10 a.m. Eastern time, we have her usually usual Saturday weekly recaps where we talk about everything weekly tree. And yeah, that's, that's about it. And then don't forget people to come back after the rest week for even coiting because she is going to be the most challenging set of branches we've had so far. Yes. That's going to be a very fun week because we've most, she's going to be, we've had Ingle in the United States and Canada. So she's going to be our, you know, different. It's going to be, it's going to be a different week for sure. So I'm excited. We're getting all these new guest stars on. So yeah, and that, that's all folks. We will see you next time. Keep an eye out. We will be posting the highlights on weekly tree, share them around. And we will see you Saturday. So next, next time I'll see you guys. So goodbye all.


So we could find the chart of accounts by going to the accounting drop down and we're going to go down to the chart of accounts. So when we first set up a company file, we want to be thinking about what kind of accounts do we want in the company file? Some of those accounts are going to be standard across basically all industries like the telephone expense, utilities expense. You would think those would be fairly standardized no matter what industry you're in. Some will be, will be specific to an industry. For example, things like inventory would only be necessary. If you sell inventory, if you're not tracking inventory, you have a service business, then you wouldn't need, say, an inventory account for example.


What would it take to eliminate domestic and family violence in Australia? That's a really big question, and in some ways the answer's simple. Perpetrators have to stop their violent behaviour, but in another way it's very complex because we know that individual behaviour is influenced by so many different factors. Over the last few years we've seen significant momentum in departments of education across Australia in the way that they look at preventing and responding to violence against women. Over the next couple of years we have seen some really good short-term priorities in focusing on embedding what has happened at the curriculum level and around professional development for teachers. As we go to the next decade what we would really like to see is consolidation of what works. So as much evaluation as possible, some longitudinal studies that show the change that can happen in students and in the teaching culture, the teachers and the broader school community. Our departments committed to eliminating domestic violence. So our primary resource in terms of education of students and families is respectful relationships, and we've implemented that across the state for students in P through to year 12 and we have demonstrated a real commitment to that and a real long-term commitment to the impact that can have on eliminating domestic violence in our state. I think it's really important that we understand that there is a lot of support in our schools for students in relation to domestic and family violence. We have teachers in every classroom in our state schools in 1200 and 39 schools. That's the first big bulk support and that's a tremendous support that we have in our schools to assist students. I think it's also important we understand we have principles in all of those schools. We have deputy principles in a lot of those schools and we have a lot of other caring adults in those schools. Apart from that, of course, we have some specialist people like our school-based youth health nurses, our school-based police officers, our guidance officers, our community education counsellors, our youth support workers, our chaplains. So I mean there is a lot of support there, but for me the main support is that are those teachers, those highly-valued teachers in every classroom in every state school. While I've travelled around Australia, I've visited lots of schools and I have a lot of school children actually reaching out and making contact with me and it's been so encouraging because they really move by what I've done since Luke's death and they've done school projects on me and you know they feel so passionate about this story and so you know those are all those encouraging things where you realise you know that children really are interested in learning and and being part of that change. In Queensland the school community is over 550,000 in state schools with a workforce of over 80,000. That is a large proportion of people that can be driving change at the community level but also through the Department of Education at the systematic level. What it will take to end that violence is us working as a society to address those factors. That means through our governments we need to be promoting programs that will encourage equality and respect through sectors such as education, health, sports and local communities. What it will take to prevent family and domestic violence is a long-term effort, political will and the desire of all of us to see a change.


In case you missed it, the Nets have announced that Kevin Durant will not play in either of Brooklyn's next two games due to a mild left hamstring strain. He was evaluated for the injury yesterday and further updates will be issued as information becomes available. This means KD out for tonight's game and tomorrow's matchup in Phoenix. For more now on KD and other topics, we want to bring in our Michael Grady. Michael, what we know for sure is that KD will at least miss the next two games. Back to back. Tonight in Sacramento, tomorrow night in Phoenix, so the question looms. Could we see Durant back in action versus the Lakers on Thursday? That's the hope. It's unfortunate because it seems like it's one step forward and two steps back for Kevin Durant, whether we're talking about two stretches where he missed time due to contact tracing or as we have it right now, a mild left hamstring strain. Now Steve Nash said earlier, confirmed that it did happen in that game against the Golden State Warriors on Saturday. He does not believe it's going to be an ongoing lingering thing or that it's all that serious, but they're taking the proper precaution right now. As you pointed out, he'll miss tonight and tomorrow. And the hope is that he'll be able to play against the Lakers, but it's not a definitive thing. They're going to reevaluate reevaluate him and then make a determination from there.


Racially charged. Thinking your tweets are racist, sir. Quiet. Racially tinged.  Racially infused with a racial valouté.  Why can't the media ever just use the word racist? This week, 72 female MPs from across the Commons wrote a letter to Meghan Windsor, named Markle, condemning the way she's been treated by the British tabloid press, as well as criticising the red tops for printing stories, which, on further examination turnout, to be nothing more than malicious fraff, the letter also called out what can only be described as outdated colonial undertones to some of these stories. You what, mate? If the main problem here was colonial undertones, then Meghan would never have married into the British royal family in the first place. This is a colonial undertone. This is a colonial undertone. And this is just straight up racism. But the reason why people are so squeamish about calling it out for what it is is because of a fundamental mistake when it comes to thinking about race. Liberal ideology would have you think that racism is a form of extreme impoliteness. Acknowledging the existence of difference is in itself an act of hostility.  So, sometimes you end up in a situation where in order to avoid saying words like black or Asian, someone finds themselves saying something which is way more racist than the thing that they were gonna say in the first place. It's not just about being black or funny, you know, different... Here we see the ultimate incarnation of colorblind ideology. I can't actually detect the presence of melanin, only the relative hilarity of the tinge in front of me. The reason why people pretend that race is nowhere is because in fact racism is everywhere. Racism affects how much you earn, how the police treat you, the quality of the air you breathe and whether you can reliably make it through an airport without the ominous sound of rubber gloves snapping. Race isn't a biological reality, but it is a social one. It's not an outdated colonial undertone, it's the stuff about everyday lives. The fact is, you can't get away from the social injustice of racism the minute you open up a conversation about race. Social hierarchy isn't an accidental byproduct of race. It's the reason why race exists as a technology of governance at all. So, enough with the euphemisms already. Name the damn problem so we can set about abolishing it. If you liked this video, you know what to do, share it, hit like, subscribe to us on YouTube. And if you really like this video go to support.nevaramedia.com You can give us a one-off donation which keeps Gary in premium or you could subscribe for the equivalent of one hour of your wage per month. That way we can keep working round the clock to bring you the stories that do and sometimes don't really matter. Thank you.


Hello and welcome to the session. In this session we are going to discuss the following question and the question says that a. write each expression in radical form 1. 2 y whole waste 2 part 3 upon 4 2. a b whole waste 2 part 2 by 3 and part b says write the following expression in rational exponent form and then simplify it and the expression given is 4th root of 16 into x raised to power 8 into y raised to power 16 the whole Let us start with the solution of the given question. In the a part of the question we have to write each expression in radical form We know that for any real number a and positive integers m and n with n greater than 1 we have a raised to power m upon n is equal to nth root of a whole waste to power m is equal to nth root of a raised to power m So here we have 2 y whole waste 2 part 3 by 4 Now comparing it with a raised to power m upon n we have a is equal to 2 y m is equal to 3 and n is equal to 4 So using this property 2 y whole waste 2 part 3 by 4 can be written as 4th root of 2 y whole cube Now this is equal to 4th root of 2 cube into y cube by using product power rule of exponents which says a b whole waste to power m is equal to a raised to power m into b raised to power m and this is equal to 4th root of 8 into y cube So 2 y whole waste 2 part 3 by 4 is equal to 4th root of 8 into y cube that is 4th root of 8 y cube That is we have written the given expression in radical form Next we have a b whole waste 2 part 2 by 3 Again we have to write this expression in radical form Now again using the same property that is for any real number a and positive integers m and n with n greater than 1 We have a raised to power m upon n is equal to nth root of a whole waste 2 power m is equal to nth root of a raised to power m So using this property a b whole waste 2 part 2 by 3 can be written as cube root of a b whole square And again by using power product rule this is equal to cube root of a square b square So we say that a b whole waste 2 part 2 by 3 is equal to cube root of a square b square That is we have written the given expression in radical form Now we move on to the b part of the question Here we are given an expression that is 4th root of 16 into x raised to power 8 into y raised to power 16 Here we have to write this radical expression in rational exponent form and then we have to simplify it We know that if a is any real number and n is a positive integer where n is greater than 1 Then nth root of a is equal to a raised to power 1 by n Here we restrict a so that a is greater than equal to 0 when n is even Here we are given the expression 4th root of 16 into x raised to power 8 by raised to power 16 Now using this property it can be written as 16 into x raised to power 8 y raised to power 16 whole raised to power 1 by 4 Now using product power rule that is x y whole raised to power m is equal to x raised to power m into y raised to power m where x and y are non-zero real numbers and m is a rational number We have 16 raised to power 1 by 4 into x raised to power 8 whole raised to power 1 by 4 into y raised to power 16 whole raised to power 1 by 4 Here we have now 16 can be written as 2 raised to power 4 whole raised to power 1 by 4 into x raised to power 8 into 1 by 4 into y raised to power 16 into 1 by 4 Now this is equal to 2 raised to power 4 into 1 by 4 that is equal to 1 and 2 raised to power 1 is 2 into x raised to power 2 that is x square into y raised to power 4 So we say that 4th root of 16 into x raised to power 8 by raised to power 16 is equal to 2 into x square by raised to power 4 Hence we have written the given radical expression in rational exponent form which is the required answer to the b part of the question This completes our session hope you enjoyed this session


and why you should not run away from it. You should understand it. It's a lot of maybe fad in this ecosystem and that's why the Postgres room yesterday was also fairly crowded. I think it's worth noting that we have a very good diverse community. I work at Prokona, we make 100% open source tools and before that I did MariaDB server and MySQL. So most importantly, I think MySQL is nearly 23 years old. It's basically past being a voting adult. Prokona server is also about nine years old. MariaDB, eight years old. It was probably worth mentioning Drizzle, which we can learn some stuff about. How many of you heard of or used Drizzle before? Heard of, okay. Okay, how many of you heard of or used WebSkill SQL before? Okay, significantly a lot more. So you kind of learn in these experiments that companies need different things and WebSkill SQL actually posted a very good, sort of goodbye message in December of 2016 and they still meet up every year at the Prokona live and actually a lot of the features in WebSkill SQL probably also made its way into MariaDB server as well as Prokona server and some even directly into MySQL itself. And we don't have much learning from Drizzle. Besides the whole don't have all the core developers hired by a single company argument. So at some stage we will learn more about that. Also a shout out to MariaDB, who just celebrated its eighth birthday. February 1st was the GA release, so kudos, Monty. This cake is not obviously mine. It's Lixon Peng's cake. I stole it from his LinkedIn profile. He works at Alibaba and on MariaDB as well. He's not here, but he is at Five Foster. So Daniel Van Eden is also not here, sick. He actually created this and I ended up modifying it to give you sort of an idea of where we are in terms of a branch. And I know it's really small. So this one should be better. Not by much maybe. How do I do that? It's fine, you don't need to see me. No, you don't want that.  Anyway, very nice graph. It's generated. Daniel started this project like five years ago. It was based on something else on relational databases. And it's very worth noting that in MySQL 55, which is what started lots of things, you'll realize that that's when InnoDB scalability was focused on. And I think we have a talk later about performance from Dimitri who's here somewhere. And 56 also brought along a lot of optimizer improvements. And in fact, MariaDB 53 also did that as well. Prokona server 55 brought in group comment in the binary log, which is parted from MariaDB server. But then after that, Prokona uses the regular 56 implementation. MariaDB server 10.2 actually gets some things from MySQL 57, which is InnoDB. Yes, Monty. Yes, that was in the previous slide. I didn't want to focus on that. It's very hard to see. Very hard to see from afar. So anyway, this graphic is available at Daniel Van Eden's GitHub repository and the pull request for the modified version which now includes the GAF cluster MariaDB 10.2 pulling InnoDB. So this line here means it's pulling InnoDB as opposed to pulling extra DB. And obviously we're both waiting for 8.0 and 10.3 to come out. So 8.0.4 is in the second release candidate. So my presumption is we will see a generally available release soon. And MariaDB server 10.3.4 is in a second beta. So I guess soon we'll see a release candidate as well. But this is a general idea of where the branches and forks and community has spread really. And of course, just to annoy Mark a little bit, there is also a bit about Drizzle there. So in terms of the open source community, I think MariaDB is excellent, taking external contributors as well as committers. So you can actually commit code directly to the MariaDB tree. Also participates in Google Summer of Code, which helps get younger blood into server development. MySQL 5.7 has taken patches as well. Save virtual columns from MariaDB from the same guy called Andrew Jakov, which became generated columns but was also heavily rewritten. And MySQL also takes lots of contributions from Prokona. So actually if you look at, and even Facebook and so forth. So if you look at the release notes, you'll find that there are all these companies that are credited, and those tend to be like 70 pages long if you look at the PDF of where the credits come from. And it's actually quite a long list from MySQL. Contributions are obviously welcome, but you can't commit directly to the code base, which is something that's probably more or less always been true. There's also MySQL community contributor award program that Oracle runs. And actually the two people probably running that are sitting right here in the front. And they are also running this room. So kudos. Prokona, it's similar. You can report bugs. You can ask for features, but you can't commit to the tree either, even though it's all on GitHub. Also these things are contributor agreements that I probably was noting. Oracle requires you to sign an Oracle contributor agreement. I understand some corporates have issues signing that. MariaDB also has a contributor agreement or the option of contributing with BSD-New such that you don't have to sign a contributor agreement. And that maybe makes things easier for people. But also when it comes to contributor code, code is not just something you drop and then you run away. Code is something that requires maintenance actively. And what is the state of community maintain code is also really important to look at. People ask, is MySQL dying? So I stood out at the Prokona booth yesterday and lots of people are like, MySQL is dying. No, we don't wanna use MySQL because Oracle owns it. Those are not technical reasons why you should not use MySQL. And MySQL is far from dying. It's clearly exaggerated. We're getting better MySQL all the time. Every time there's a new release, it gets better. There are a lot of external contributors. I think pretty much everyone in this audience is an external contributor of some sort. There's lots of people using it. There's tons of shared knowledge. Look at the amount of shared knowledge on making InnoDB work well. It's amazing. And Oracle has been actually a great steward because they've not actually killed MySQL development. They've just enhanced MySQL development, which you can see in 5.6, 5.7, 8.0 even. The release candidate is actually worth using. In fact, there's this website called the complete list of features run by a guy called Morgan Tucker who used to work on MySQL as well. And just list features in 5.7 that are highlights. And I think there are more than 150 features that are highlighted on that list. The documentation is now so complex from MySQL that I think if you print out the PDFs, you might actually hit some 4,000 pages. And a couple of months ago, I think Giuseppe, Fred, and I were having a chat with someone who wanted to know more about grants. And actually, if you look at the documentation for grants, it's actually fairly complex without knowing, without having years of experience dealing with grants, it may not be super easy for a newbie to pick up on it. As such, they do grant all asterisks and asterisks, which is not what they're supposed to be doing. So actually there's a lot of new features that a lot of people don't know exists and maybe don't use yet. And it's kind of sad because it's been out for more than two years. So one of my favorite ones is online buffer pool resize and how everything starts becoming more online as we are able to grow things nowadays. And of course, things like multi-cells replication, even though it came to MariaDB first, it is also present in 5.7. I personally also like the JSON, MySQL shell and the XDEV API and the X protocol because I think it's super cool. Lots of people nowadays like to do stuff with MongoDB and this sort of gives you an insight from that standpoint. Also GS functionality. I spoke to people yesterday as well saying, hey, we're using Postgres, we used to use MySQL but then we use Postgres now because of GIS. But the GS functionality in MySQL 5.7 is actually heavily underrated, right? It's not only is it good, it can also do stuff like Google Maps can do. And I think Norvald, who may or may not be here, has also given a great talk at the GIS track about GIS and MySQL. So there are lots of things that people don't really know about, which is unfortunate. And that's also true for MariaDB. So, 10.1 brought a whole bunch of new things. Start transaction with consistent snapshot to be fair is now also in MySQL 5.7. Galera cluster being integrated, very cool. The first thing, introduce table space encryption. InnoDB defragmentation, parallel replication, we probably haven't talked about that as well later. The thread pool is highly useful from being open source as well. And roles, SQL-sided roles, which Giuseppe will talk about later as well. Not the MariaDB variant, but the MySQL variant. 10.2 also brought other features, like InnoDB as the default InnoDB. Now, that may be a play on words because nowadays, when you ask for something, you get something else. So for a long time, if you ask for InnoDB, you got extra DB. And in many Linux distributions, if you ask for MySQL, you get MariaDB. So. Pyrox is in alpha. There are obviously window functions and commentable expressions. Two things that are probably very useful.  Highly useful if you're gonna use encryption because you don't want to use the File Key Management Plugin. And of course, Oracle style execute immediate where you start seeing new stuff. And this is obviously not, these are not comprehensive lists of what's new. It's just stuff that's worth noting that you may not necessarily see in other distribution of MySQL. Pocona server for 5.6 and 5.7 also introduces other things. Pocona server mostly focuses on wanting to be more manageable, more usable, more operationally useful. So things like the utility user, if you're running in like say OpenStack for example, you may find useful, something like the utility user where you have system access, but you can't actually look at the schema. And if you, the proxy protocol support, if you want to use maybe HA proxy, which supports the proxy protocol, backup locks, improvements around backups and extra backup. Then of course, since we're gonna talk about the ecosystem, the server ecosystem anyway, here's a base blog post. I don't know how many of you've read it. It's worth reading. Compatibility largely means that things are supposed to exist, or occur together without problems or conflict. And this is true even in computing. Why it really matters is because if people ask for a feature in one server, they may not get it in the next server because they did not necessarily drop in compatible. And MariaDB server is after all the default in pretty much every Linux distribution except Ubuntu. The latest Ubuntu does ship 5.7. I think it's worth noting from a Linux distribution or a more pragmatic standpoint, we should take a page out of the cloud operators. The cloud operators don't pass off MariaDB as MySQL or vice versa. That is true for Amazon. That is true for Microsoft. That is true for Rackspace. They actually offer you multiple choices. And choice is actually probably a good thing because you realize very quickly like, hey, maybe I want to use innerDB memcashd for putget and that's not present say in some server. So Monty did ask a question earlier and he is in the audience. He did make a verbal commitment a while ago about MySQL 5.6 should be comparable to MariaDB server 10.1 as well as 10.2 comparable to 5.7. And till today, you actually get the description that it's an enhanced drop-in replacement for MySQL. And this is true because the data directory is the same, the port is the same. But in terms of feature compatibility, it may not necessarily be equivalent. Governance is obviously worth talking about. MariaDB has a cooperation as well as a foundation and I think that's really important that the foundation gets stronger. And today you'll notice the foundation has foundation members from booking.com, Visma, Alibaba Cloud, IBM, WordPress.com, Microsoft and even Tencent. So diverse representation in a foundation is a good thing. MySQL for better or for worse is actually governed by Oracle. And as I said, people have negative connotations to a company that actually does good things. And Procona is governed by a corporation called Procona Inc. It's also privately held and has never raised any funding before and has been around for like 11 years without funding. So you gotta know who's funding what. And if you ask, is there vendor lock in an open source? That's something to also always think about overall. And that's a bigger for them thing.  You'll notice that 10.1 and 5.7 were released may basically two days apart. And as I said, 10.3.4 is in beta, beta two now and MySQL 804 is in release candidate two now. So I suggest if you are interested you should start looking at this stuff because if I'm a guessing person you're gonna see these generally available in like three months, give or take. And Procona server, I don't list it here because it generally follows from a major release anywhere between three to six months behind. And for example, a good example is MySQL 803 is already being worked on by the developers. Replication is important. And this I took straight out of the MariaDB Knowledgebase. It is definitely easier to migrate to MariaDB server but it's harder to migrate away from MariaDB server in terms of from a replication standpoint. So I don't wanna throw any hotel California jokes here. There are obviously things that are different. So the default bin log format in 10.2 is mixed as opposed to being row in MySQL. The annotation of row events is on. Time-delayed replication is available in MariaDB 10.2 as well. This I think is an extremely unique feature. DML only flashback which allows you to roll back instances to an older snapshot. Synchronous replication. Lots of people are very interested in things like Galera cluster and Galera cluster has spawned two branches so to speak. One's called MariaDB Galera cluster which is built into MariaDB server. And of course there's Procona XDB cluster with proxy SQL and an admin tool. And synchronous replication is probably gonna play even more important role going forward. And Oracle has come up with something possibly similar. It's called group replication. And it's very tied with MySQL LSH. It's also very tied to MySQL router. And the product around it is called MySQL InnoDB cluster which one could actually launch. And Fred has a nice little video I think on YouTube.  So let's talk about the X protocol. MariaDB server does not have that at the moment. So you can't use MySQL LSH. And this consequently means you will not be starting up an InnoDB cluster. So this definitely means from a synchronous replication standpoint things are diverging. Encryption. MySQL 5.7 and MariaDB Server 10.1 and greater both have encryption. The MariaDB version does table space as well as table encryption based on the Google patch. And MySQL only does table space encryption. You are required to use InnoDB file per table for MySQL but this has been the default for quite some time now. And as logs, logs don't get encrypted in the MySQL variants today but they are in the MariaDB variant. So MySQL bin log obviously has a bit of an issue in MariaDB but you can do read from remote server and use the encryption plugin API as well as a plugin but it obviously adds some load to the server. I actually mentioned that it doesn't encrypt tables or logs, yeah. Yeah. We'll do questions later. Security. MySQL native password which has been around since four or one I think but renamed later uses double SHA-1 based authentication. And I guess that's not useful any longer so MySQL has this thing called SHA-2B6 password since MySQL 5.6. You are more than encouraged to probably turn this on going forward. In fact, there are some good blog posts just last week about SHA-2B6 as well as MySQL 8. So we were. MariaDB follows this thing called edit25519 which is the elliptic curve digital signature algorithm used by OpenSH. This is another implementation. Naturally they're both obviously not compatible so probably worth noting that if you're creating users and migrating from one server to the other you have to reset the passwords. Validated password is on by default in MySQL 5.7 so if you by default provide a poor password it will actually tell you not to do that. And SSL also has various differences so SSL in 5.7 is pre-generated keys and you just need to turn it on in the client. And there's also a utility called MySQL SEL RSA setup that's provided with MySQL 5.7 that you can use. Libraries are changing. So Yazzle I guess changes name every few years to Yazzle, Yazzle, Wolf SSL. Anyhow ignore the name changes. It's all going open SSL going forward. There are also user table changes. So if you write scripts, oh dear. If you write scripts it's worth noting that you need to actually make note of the fact that there are changes in the MySQL user table. Password expiry does not exist yet from last I checked. Password last change as well as lifetime is available in MySQL. Account locks and unlocks also probably important. Slides will be online so I provide lots of links. Stuff that might matter to you. MySQL has an optimizer hints, query rewriting, optimize the trace which could be very useful I think at one stage someone from Wikipedia Hemi wanted it and he's speaking here later. I don't know if he's here later now. MySQL super read-only mode. Ah, he's here. MySQL super read-only mode, very important when you're doing automatic failovers to ensure that super user doesn't accidentally write also something we're looking forward to. And a newer performance schema. When it comes to tools, if a tool requires the MySQL global transaction ID, so MySQL failover, replication admin, MHA for GTID based failover which Yoshi writes. MySQL router, all the stuff will not work with MariaDB server. This only works with MySQL and Pogona server. The external ecosystem is alive and kicking, right? So many good things. You've got toolkit, extra backup, proxy SQL, max scale, what else? Vittes, I think we have a talk for Vittes later. Orchestrator, definitely Shlomi will probably talk about it later. Sandbox, now in a new language even. So lots of people actually pay attention to making tools around MySQL. And I think that's why you should use it, right? Because it's very vibrant, it's a great ecosystem. When do you want to use MariaDB server today? So everything's about today, right? So I'm not talking about the Vittes or the release candidates. A whole bunch of reasons why you'd probably want to use MariaDB today that you may choose over say MySQL or Pogona server. Also a whole bunch of reasons why you'd want to use Pogona server over say MySQL. So maybe you want to use Myrox, which is fully generally available. You want to use the key ring vault plugin for encryption. You want column compression maybe. You've outgrown MySQL for some reason. Pogona server, great, great choice. And for everyone else, I think the best is actually for you to use MySQL 5.7. It's been out for two years, it's pretty stable. It's well worth using. There is obviously the very near future, which I estimate to be less than three months. MySQL 8 also brings you things like roles, commentable expressions, window functions, histograms, MariaDB Server 10.3 brings you Oracle support as well to some extent. System version tables I think is extremely cool because it's coming out of the SQL, I think 2011 standard possibly. You also got the semi sync stuff merged in via Alibaba. SQL mode equals Oracle I think could be a game changer for people who are migrating from Oracle to another open source database. So what should you use today? I think you should care about the innovation today and most of the innovation I spoke about has already happened for at least two years, so both 5.7 and 10.1 has been around for about that long. Think about the features you need today. You definitely want freedom from vendor independence. You want to always make sure that there are multiple vendors supporting your product, know the difference between a branch and a fork. And some might recognize this, Michael Stonebreaker said that for Facebook, MySQL would be a fate worse than death, so they made t-shirts. I think mastering the ecosystem takes a lot of time, which is something that you should invest in if you care about MySQL, and it's definitely not a fate worse than death for anybody, so let's stop with the thought and let's focus on good stuff and making sure we are a strong ecosystem where people look at us as a first choice, as opposed to saying, hey, let's try Postgres or MongoDB. Thank you for listening. I have some time for questions. Yes.


Greetings everyone, here we are two weeks into the new and we trust that very temporary era here at Purdue. I thought it might be time for another update. I cannot say enough to praise our faculty, our staff, our students for the way they have tackled the new remote learning era. We've had fewer problems than we would have thought. Each day this week over 40,000 students and faculty logged on to the system meaning that real work and learning was going on even on a largely empty campus. So thanks to everyone and let's hope that that kind of progress continues. We hope that campus will be full again before long and certainly by fall. No one can know at this point. One thing we do know is that even when we are back to full complement things will not be the same. This fall there will be a flu season, there always is. But this fall the COVID-19 viral strain will be part of it. We won't all yet have natural immunity and there won't be a vaccine. And so we intend that Purdue be as well prepared as any school in America to manage our way through that season. Every year the FBI and other authorities put out a report on the safest campuses and the safest communities in Purdue and West Lafayette are always near the top of that list. We intend to be at the top of anyone's list for the safest places from a public health standpoint too. I've started a task force this week to look at everything we do with the question how can we be a little better protected and better able to deal with problems that the flu season might bring us in this unusual year. We'll look at how we teach, how we learn, how we house people, how we feed people and how those of us who support teaching and research can do our work in ways that are maybe a little different and more protective. Let me close with a word about finances. Under the very best of circumstances our revenues are going to take a significant hit this year. Even if we have as many students as we expected, which is far from certain, our state appropriations are very likely to go down, our revenue from events, our donors will not be able probably to be as generous as they would have otherwise. You know throughout its history Purdue has been careful about finances and that can pay off at a time like this. For one thing as one of the more affordable schools now in the country we will I think remain attractive to students who are having second thoughts about college or where to go. And secondly at a time when millions of our fellow citizens have already lost their jobs as you know we've not had to take that step here at Purdue and it's our fervent hope that we won't no matter what comes. But the more careful we are now the less severe the measures we will have to take later if things do not recover as we hope they will. So things we've already put in place restrictions on travel and purchasing and hiring are going to continue into the next fiscal year. And I'll tell you right now that the pay raises that we intended to make starting in July will have to be postponed indefinitely. If things improve enough maybe we could put them in place before next fiscal year is over but no promises because nothing of us can see the future. So that's it for now we'll do what we can to continue these reports and keep you current on an occasional basis. We want you to know as things change how we're thinking about them and the decisions we're making trying to make in the best interest of the institution and everybody who's a part of it. We are all in this together and we will get through this together.


You can only eat one for the rest of your life mother Here to dear folks a kind of cheese You can only eat one type of cheese for the rest of your it's easy. It's easy. Yeah Can I have bread? Oh? Yeah, this is just you can have anything you want with the cheese, but you can only have one kind of cheese for the rest of your life Sheep's milk marinated goat cheese This is this is not even a hard question. Oh, you've had it well, I know that but there's so many Magnificent I would be so sad. Oh, I would be too.   Thank you. They're you sports on patreon. So it counts good but cheese. It's what's for breakfast Bup Pick it up Bobby Bobby. Yeah Bobby doing Bobby dole. No just little Bobby decided he was gonna have some goat but cheese Bobby dual What do we do in a day at Corbin? Heck if I know today, we got to read this today. We got to read this today. We got to read this This is the glimpse of the yet to be released to public movie seven Kedal seven by lie Which premiered in Rotterdam film festival and has received lots of accolades from audience and critics The movie is directed by Ram The perinbu director And this will be the dammel debut for niven ball as a lead And it has Anjali and Suri from vidu tali in lead roles. Please watch this movie when released. Well It's probably not releasing here. So you know what you know what is releasing here mass-dress If the meals gonna be with that menu is offering I want to see that well, I don't if you remember that I vividly remember The song the song that yeah had the painting yep Vibe to it because there were a couple images from this that were in that. Yeah. Yeah same film. Yep Looks good, man. Looks really nice Looks intriguing visually. It looks different and unique. Yep. Um and intriguing And coming from that director who at least from what we've seen is a good director Um I'm looking forward to it. I am as well At least seven. Yeah color money. Do we have uh, I don't see it anywhere The uh When I'm not coming up with that name titled wrong movie, you know seven seas seven So seven seas seven release date 21st Of last year it didn't he said it's not been right. Yeah I wonder what the hold-up is With this film. I don't know Suri isn't it? Nice. Um Yeah, it Films can be delayed for a billion different reasons. Yep funding They're waiting for festival circuit to end distributor drops out distributor drops out covid Or just just wait requests from yeah a correct request from a star's publicist to hold off because another film is Going to release at the same time and they want to change the release date because of it or they had a release date And now another film's coming out. They don't want to compete with yeah A million reasons and also like a lot of times It's not up to the artist at all No, so like if a studio like I just did this podcast thing And they have a deal with audible slash amazon and so I was like, when do you think you guys are we done with this? It's a 12 episode second season of a podcast. Um And I was like, oh, they're probably done June July, but then she's after that It's up to audible for their release date of when they're Kind of do it. Yeah, it could be a month from then it could be next year at sundance. It could be Because like it's not up to us at that point No, and it happens on a small scale too Like the short film that I did Yeah, that won the awards at the Sherman Oaks film festival and has gone to a couple of the film festivals We wrapped we filmed that a year and a half ago and it still doesn't have public release yet And that's just a short and that's just a short. Yeah. Yeah, that's coming But for those of you who are wondering that's coming in late may early June that that'll be able to share that publicly Um, but yeah, there's a million reasons why so whatever it is look at that runtime Oh, good lord 90 minutes if that's real That is amazing. Yeah, that doesn't happen in Indian cinema usually No, very very rare even I can't I can't believe that's true. Um It's funny. I've I watched um somebody's TikTok review that was apparently at our monkey man. Um Um screening. Mm-hmm. And it's like I liked it. It was nice But man, did it feel long? I was like Then you don't watch indian cinema It's not an indian movie obviously, but no, but still I did not feel the link that well It was two hours It was long not hold on not only do you clearly not watch enough indian cinema to understand how long indian cinema can be But have you not noticed the trend in hollywood lately? Yeah Most films now since Marvel said okay, it's we can do two and a half hour films Well, scorsese has been doing it since I was born, but Everything's over over two hours now Yeah I uh I did not feel as lengthened and then when you add all of the advertisements and stuff you might as well bring a tent Um But yeah, the uh had to be a short runtime. Yeah Uh, it's tamo though. I do believe um, and so we have a If it comes here It's small though. So that it could go to see me that would be my uh, that would be my worry Because it's it's a small film. We that might that other Small to lugu film which we always get to lugu films didn't come here at all. Yeah, it was a small. Yeah, um independent once again all the more reason For us to have our stupid movie theater Which would be a multiplex that can play all regions at all times and everybody could come to it and enjoy Unfortunately, we don't have those millions. Uh, no, but we know people who do Anyways, uh, let us know about this. Let's do it and uh, what should be the next from this director or some of the stars that we should Watch and anything else we need to know down below