Family Theater presents Jimmy Duranty and June Haver from Hollywood, the mutual network in cooperation with Family Theater presents June Haver and Jimmy Duranty in Rhapsody in Bomb. Family Theater's only purpose is to bring to everyone's attention a practice that must become an important part of our lives if we are to win peace for ourselves, peace for our families, and peace for the world. Family Theater urges you to pray, pray together as a family. And now to our drama starring Jimmy Duranty as Jimmy and June Haver as Sally in Rhapsody in Bomb. Sure, wouldn't it be? Uh, three gallons of gas please. Three gallons of gas? In your gas tank or in your cigarette lighter? Please, Junior, please, no remarks. Well, I just couldn't help that one. Son, I have three gallons of them away, clean across. What's that young lady crying about? Oh, you mean the girl by the oil can? You whistlerous talk, awful funny. I mean that girl by the Earl can. Well, I don't know what she's crying about. You find out. I can't stand to see a pretty girl cry. What goes on here? Young lady, that's no way to carry on. Well, you can carry on the way you want to. This is my way.  No. Oh, he said he was a talent scout. He said he could get me a screen test in Hollywood. All I gave him the money to buy my ticket to California. And that's the last you saw of him? Yes. Bad day, child. How much did he take you for? $75. Why, it's an outrage. It's Grand Las Cernes. That's the way they got it in even a paper. They got a dash between Las Cernes. Anyway, what's your name? Sally Shannon. Sally Shannon. Seems like I've heard that name before. Glad to know you're Sally on Jimmy Nazzola. Wait, I'll give you my card. Thank you. Jimmy Nazzola, piano's wrecked while you wait. World's greatest ivory-buster Dixieland style. Permanent address, billboard, Cincinnati. That's me. Well, how do you do, Jimmy Nazzola? How do you do? Is this your suitcase here? Maybe we can catch up with that talent scout. Come over to the car and meet Aunt Harriet. Who's Aunt Harriet?  Well, where's your car? Right here. This fine pierce arrow. Oh, good gracious, that thing? Sister, you're speaking of the jalopy I love. Well, it ought to be in a museum. Touch, child, wait a minute. There's a lot of mileage in that old coffee grinder yet. I keep saying what my fingers crossed. Well, where's Aunt Harriet? I don't see any Aunt Harriet. I'll wake her up. Oh. Aunt Harriet, wake up, wake up. Uh-huh, three gallons of gas.  Well, where are we, Jimmy? We're just outside of Albuquerque, New Mexico. Move over, Aunt Harriet. We've got another passenger. Well, well, oh, a pretty young lady. Aunt Harriet, this is Sally Shahanan. How do you do, Sally? Hello, Aunt Harriet. I'll put your suitcase away. My butt is heavy. What do you got in it? I play the piano, too. Well, imagine that. You're among friends, my dear. You see, my husband, when he was alive, used to be a piano tuner. Oh, how interesting. You two kids get acquainted. I've got to check my... Are you going to California, too? Yes, Aunt Harriet. Yes, I am.  Yes, I've lost all my money. Oh, goodness gracious, you, too. What do you mean, you, too? Yes, my daughter, Bessie, wanted me to come to California for a visit. She sent me the bus fare, and, well, I lost it.  Bessie and her husband are not very well off, so I didn't want to ask Bessie for any more. Oh, so you're hitchhiking. Yes, thanks to Jimmy Nazola, he stopped in Topeka for three gallons of gas. Oh, he's a mighty fine man, Sally. Oh, his talk is tough, but his heart is tender. He's a nice awfully nice. Wait a minute, wait a minute. Easy on that hood. He's so kind-hearted, giving people lifts. Why, do you know all the way across Kansas, we had a widow with three children and a pet pig? Oh, it was love at first sight. You mean Jimmy fell in love with the widow? No, the pig fell in love with Jimmy. Say, this is going to be a lot of fun. Of course. Things are never as bad as they first seem to be. We'll get to California after all. There's no maybe about it, young lady. You'll get there. I have money in the bank in New York, so when I get to Hollywood, I'll be all right. I know people there, too. We'll get there. Don't worry about that. Okay, mister. Uh, are you girls all set? Yes, Jimmy, all set. Home, James. Then we're off in a cloud of oil smoke. Sally, what did that fellow look like, that phony challenge scout? The man who stole my money? He said his name was... Never mind his name. He can change that. What did he look like? Oh, it was tall and had red hair, wore a loud flashy sport coat. Tall, redheaded and a loud sport coat. I'll watch out for him. Suppose you find him. What'll you do? We'll make him cough up your dough. In my younger days, I was the champion fighter of part of the school, 29. What if he has a gun? I was also the champion runner. You know, Sally, the kind of my husband's restless soul who was always gentle and patient. I don't think I've ever known a kind of man than Jimmy here. You're absolutely right, Aunt Harriet. Jimmy is just a darling. Always helping others. Oh, wait a minute, kids. You make me blush clean to the end of my nose. And that weakens me. It takes too much blood out of my system. You know, I don't deserve any credit. Oh, that's what you think. Well, I was brought up on each side and there were six of us kids. My dad was a day laborer. My mom washed and ironed and cooked and mended and scrubbed. But she kept our family together. I knew you had a wonderful mother. She made us share things with each other. She used to tell us kids it's more blessed to give than to receive. Poor people know that. When you need help, don't go to rich people. Go to poor people. Poor people know what it means to be hungry. They'll squeeze out an extra dollar somehow to give it to somebody who needs it. That's what she told us. So, I don't deserve any credit, kids. I'm just doing what I was taught to do by the kindest person I ever knew. My mother. What can I do for you? Three gallons of gas. Three gallons? Three gallons. What's the matter? You got that much? Oh, yes, you bet. Jimmy, we're going in for a cup of coffee now. OK, Sally, but go easy on the each. We will, Jimmy. Don't go off without us. OK, kids, in just a minute. Three gallons, exactly. Yes, the first piercerer I've seen in a long time. You've got quite an antique there. Don't belittle my fine car, my fine befitted friend. I'll have you know that they don't make cars like this anymore. No, they don't, sir. Oh, that was a fine car in this day. Some of the modern cars are pretty nifty, too. Take a look at that blue convertible right over there. I was just giving it again. The boy, it's a dilly. Yeah, it belongs to a big Hollywood talent scout. I suppose don't... Huh? A talent scout? Jimmy McGuire, always a nice guy. He's not stuck up at all. Everybody calls him red. He wouldn't have red hair, would he? Well, what do you think? Talent scout, tall, red hair, flashy sport coat. What kind of clothes does this guy wear? Dignified and convoisatory? Oh, brother, not Jimmy McGuire. He's got red socks, yellow shirt, green slacks and a sport coat that looks like a rainbow. That I'd like to see. Where is this walking Easter egg? He went to that little store across the highway. Thanks, mister. I got business in that store. I'd better leave this door open. I may be coming back in a hurry. Jump in, kids. Quick, we got a scam out of here. Jimmy, what on earth? Sally and Harriet, pile in. I'll tell you later. Quit pushing me. I'm getting in. What happened back there at the filling station? Yes, what scared you? And how did you get that lump on your jaw?  What good news? Here, Sally, count these bills. Good heavens, he must have robbed a bank. 50, 60, 70, 75 dollars. That's your money, Sally. I caught up with your talent scout. Oh, Jimmy, you didn't. I sure did. With your description, how could I miss? Tall, red-headed and a sport coat like a rainbow. Didn't I tell you Jimmy was wonderful? What did the man say when you asked him for the money? Yes. Well, after I chased him out of the back door of the store, across a potato patch, threw a mess of cactus into an old corral, he didn't have any bread left to say anything. He shoves his wallet at me, I take out 75 smackers, and I hands it back. Well, then what did you say to him? Nothing. I didn't have any bread left either. Oh, Jimmy, you got my money back. You're so wonderful. I'm going to give you a great big. You know what? I should have given back that to you one dollar at a time. This one is on me, Jimmy. I'm rich now. Service, ma'am. Yes, ma'am. Three gallons of gas, please. Yes, ma'am. Thanks, Sally.  Oh, I owe you a lot more than that, Jimmy. And while we're stopping, let's eat. A real dinner this time. Oh, yes. Let's do that. I'm starved. I could eat a porta-house or two myself. One the way that police car is going. Oh, I guess I'm still hunting that crazy man. Crazy man? The crazy man held up Red McGuire, the famous movie talent scout, and got away with a lot of money. Oh, when did that happen? Oh, just this afternoon. Wait, I think the news broadcast is on now. I've got my radio right here. Maybe they'll have something about it. Was passed by the Senate this morning. Police have not yet captured the maniac who assaulted James Wellington McGuire, prominent Hollywood talent scout. The attack took place on Highway 66 near Sageview. Strangely enough, although McGuire's wallet contained only $75. That's how they knew he was crazy. McGuire is on his way to the Happy Valley Festival where he'll attend the Festival of the Bees. The cattle market today remained... Well, that's all of that. Lunchroom is right over there. A few folks want to eat. That's funny. I don't feel hungry anymore. Strange. Neither do I. How about you, Aunt Harriet? Well, what do you know? No appetite. In that case, we'd better nose you along. Mr. The Radio said McGuire was going to Happy Valley. Oh, sure. To the Festival of the Bees. Yeah, String Trio's beat-oven-bockin'-browns. Beat-oven-bockin'-browns?  But where is Happy Valley? Well, yeah. Turn right at the next stoplight and drive about 12 miles. There's going to be a lot of excitement there today. Son, all right, you are. All right, you are. Well, kids, I think this is Happy Valley. Yes, I'm pretty sure this is it, Jimmy. Now, what do we do? First, we've got to find the Festival of the Bees. We're going to stay in the car while you and Aunt Harriet hunt up McGuire. Tell him the whole story and give him back the 75 bucks. They say he's a nice man, and I'm sure he'll understand. Oh, I hope so. Well, just in case he's still hot under the collar, we'll keep the motor running in case. Look, this must be the place here, this big auditorium. We'll park here and find out. I'll ask that girl. Oh, young lady, is this Happy Valley? Yes. This is Happy Valley. This must be where I came in. Is this the Festival of the Bees? Yes, sir. This is it. You don't seem to be very happy about it. Would you be happy if you lost your chance to play in the festival? No, not in the festival. But tell me, what is this festival? Well, we're having a contest in there for the best string trio in this county, and the Happy Valley trio can't play. How do you know? Because I'm in it. I'm Winnie Jackson, the violinist. I'm here. Our cellist is here. But our pianist, he's got the means. Gee, that's tough. All the contest is going on right now. And when it comes time for Happy Valley to play, we can't go on. No pianist.  Now, Jimmy, don't get into anything. We may have to leave town. Remember?  Can you play Beethoven, Brahms, and Bach? Winnie, Jimmy, and Zola can play anything with notes on it. Oh, that's wonderful. Come on backstage. I hope we're not too late. Jimmy, where are you going? I'm going to man the keyboard in the battle of the beast.  I'll be back later. Oh, dear. That man will get himself in trouble again. Not if we can help it. Come on, Ann Harriet. We've got to see Mr. McGuire And so that's how it happened, Mr. McGuire. And here's your $75. Jimmy's not crazy, Mr. McGuire. He's the kindest man in the world. Oh, you're not angry? Over all that good publicity, of course not, Miss Shannon. Besides that, I've been mistaken for the same man several times before. Oh, then you understand. Certainly. It's the sport coat. My wife warned me not to wear it. Well, we're sorry we had to call you out here in the lobby. In the middle of the contest. Oh, that's all right, ladies. I'm very fond of classical music, but three solid hours of it gets a little monotonous. The Rockville String Trio. I believe Happy Valley is next. By the way, where is this man, Jimmy? Well, get set for a shock, Mr. McGuire. Jimmy's playing piano for the Happy Valley String Trio. No kidding. Well, that I want to see. Happy Valley's my hometown, you know. So come on in, ladies, and we'll all root for Happy Valley. And gentlemen, the final string trio to perform in this great festival of the bees, Beethoven, Bach and Browns, is our trio from Happy Valley. violin, Winifred Jackson, cello, Howard Carberry, and piano, James Nazerlach. They will play for the first number that lovely selection from Beethoven entitled Minuet, in G. Stop the music. I got an idea. Do all those pretty things.  I went to the circus last week. And while I was there, I saw an elephant looking down a little mouse. And the elephant was saying to the mouse, look at the size of me and look at the size of you.  The little mouse looked up at the elephant and said, listen, I've been sick far away, when I'm far, far away from you when I'm far away. You know what? Last night, I'm walking down Hollywood Boulevard, just commuting with nature when I accidentally bunked into a guy. Well, being a gentleman, I apologized, but he wasn't satisfied. He demanded an autopsy. So I upset him. I faced with my right, I faced with my left, I seized an opening. I'm flat on my back. So pick myself up from the gutter, I put the chip in my shoulder, I said, knock it off. Knock it off. Five minutes later, the chip was still there, and the chip was gone. Mr. Nazola, how could you do such a thing? How could you dare desecrate a great musical masterpiece? What's the matter, Junior? Did we miss a note somewhere? Oh, you syncopated wretch. You've ruined Happy Valley's chance of winning the festival. The audience didn't seem to think so. Did you hear the hand we got? This is the festival of the bees, Mr. Nazola. Tell me, please, which one of the bees was that? That was all three of the bees. Oogie and Basin Street. Julie, what's the matter? You're supposed to play two numbers. I know, but this gentleman don't like our interpretation. Oh, we'll never live this down. I refuse to let Mr. Nazola go off on that stage to assassinate another classic. Wait a minute, Cedric. Oh, Mr. McGuire, I'm so sorry. I won't apologize, Cedric. That last number was sensational, but if it's classical music you want, let this young lady play. You mean Sally? Yes, and Harry, what's classical music? Shannon? Are you Sally Shannon? The concert pianist? Yes, I'm Sally Shannon. You mean she's famous? Oh, certainly she's famous. Seven concerts last season with the Pennsylvania Symphony Orchestra. No. Yes. Miss Shannon, the Happy Valley trio would consider it a great honor to have you play the next selection with them. Well, I'll be glad to. I'll introduce this little lady myself. Come on, Sally. I'm with you, Jimmy. Ladies and people, your attention please. That first number we did was just a wee, tiny bit monotonized. Modernized. They can't stick to Ranny. But the second selection will be strictly squared. At the ivories on this number is the well-known concert pianist, Sally Shannon. And kids, this old pierce arrow will have to be rolling along. All right, Jimmy. I'm so glad we helped Happy Valley win the contest. We didn't win it, Sally. You won it. You both helped to win it, and you were both wonderful. Oh, thank you, Aunt Harriet. You were in the act, too. Without your encouragement, we never could have done it. That's right, Aunt Harriet. Until I turn the page. Aunt Harriet, take that again. You gave McGuire back the 75 frog skins. Yes, and everything is all right now. Yeah, that means we're broke again. Oh, no, Jimmy. We're not broke. What do you mean, Aunt Harriet? I found my money. The money I thought I'd lost. You did? Where? Well, I jumped up and down so hard applauding you and Sally that I shook it loose from somewhere inside my throat. Now, I'm the rich one. And from now on, everything is on me. Aunt Harriet, you found the frog skins, huh? Am I a lucky guy to have friends like you and Sally? Well, goodbye, Happy Valley. It's Mr. McGuire. Maybe you want to pop me one? Well, okay. Your book's not leaving, are you? Oh, yes, Mr. McGuire. We're heading for California. Mr. Mack, I'm sorry I chased you through that tater patch. Think nothing of it, Jimmy. There are no hard feelings here. I want to give you this sport coat that caused all the trouble. Oh, for me? Gee, thanks. You were sensational this afternoon. You and Sally both. I have a little contract here. I want you to sign it. Mr. McGuire. Was my piano poundin' that good? No, Jimmy. This contract isn't for your piano playing. Oh, of course. Now, it's for Sally Natch. Here, Sally.  Who has a pen? The contract isn't for you, either. Oh, my star's alive. You don't mean it's for me. Oh, Aunt Harriet. It's for Jimmy's piercero. Oh. As this is just the car I want for a scene in one of our pictures. Now, here's our $100 advanced rental, Jimmy. Then sign right here. Oh, sensory note. Quick, give me that pen. Here you are. Thank you. Now, I want all of you to look me up when you get to California and I'll see that you get a screen test, Sally. Oh, that's a good guy. So long, McGuire. Well, what do you know? Now, laugh at my piercero. I take it all back, Jimmy. It's wonderful, too. Oh, Sally. Give me the high sign when you see a filling station. We'll need another three gallons of gas. Once again, stepping out of character are June Haver and Jimmy Durante. Thank you, Hard. Jimmy, it's been lots of fun being on the show with you tonight. Jimmy, you know I enjoyed being with you and being on the family theater because I think it's a wonderful idea getting together with your loved ones every day and praying together as a family. Would it embarrass you, Jimmy, if I ask the question? Well, June, that all depends. Well, this is about prayer. What do you think is the best way to pray, Jimmy? Do you whisper it or talk right out or just sort of think it? Well, I would say you can pray all three ways, June. But I like to speak right up and say thanks, dear Lord, for giving me a wonderful life and wonderful friends and thanks for all the blessings you've given me. That's a nice way to put it, Jimmy. That's what I like about family theater, June. It reminds us every week how important prayer is and in particular how important praying together as a family can be. That's the way I feel, too. And I think everybody listening in will agree with that, Jimmy. June, to all the family theater audience, I want to say thanks. And I want to finish with that one line by which the program has become so well known. The family that prays together stays together.  From Hollywood Family Theater has brought you Jimmy Durante and June Haver in Rhapsody in Bob with Verna Felton as Aunt Harriet. Others in our cast were Howard McNeer, Lamont Johnson, Martha Shaw, Robert O'Sullivan, and Jack Raymond. The script was written by Harry Lawrence with music composed and conducted by Harry Zimmerman and was directed for Family Theater by Joseph F. Mansfield. Transcribed, this series of Family Theater broadcasts is made possible by the thousands of you who feel the need for this type of program, by the Mutual Network which responds to this need and by the hundreds of stars of stage, screen and radio who give so unselfishly of their time and talent to appear on our Family Theater stage.  This is Howard Culver, expressing the wish of Family Theater that the blessing of God may be upon you and your home and inviting you to join us next week at this same time when Family Theater will present. Join us, won't you? Theater is broadcast throughout the world and originates in the Hollywood Studios of the world's largest network, the Mutual Broadcasting System.


Hi everyone, I'm Joe for jasphyscasebreaks.com coming at you with a random number block randomizer For the a group of teams right there that helps sell out pick your team for which will be in a different video If you're wondering how a random number block works. There are the instructions right there But this group knows now If you're watching live, we did promise that we took two spots out of this number block Right, so we're only selling eight spots outright. We're randomizing those two spots to to the people who bought spots So let's copy these names here So there'll be two different dice rolls one for the two-spot giveaway and then the one for the names and numbers So let's roll it and randomize that list Snake eyes two times top two after two easy one And two after two times Gretchen and Grant So you'll have extra spots So Slightly better odds to maybe get the good numbers All right, so now let's copy these names Get them in there. They're the numbers right there. Let's go. Let's roll it and randomize names and numbers three and a four lucky seven times one two three four five six And seventh and final time you remember that correctly chad That was correct I think uh, Tarad Taylor had a bruised rib or something like that And then the team doctor Was getting giving him some sort of cortisone shot in the rib somewhere And then it slipped or something like that and he had a slight lung puncture I mean nothing's slight when it's a lung puncture, but he got a lung puncture and then Justin Herbert started and the rest was history Wally pipped three and a four seven times for the numbers one two three four five six And seven and final time We got three down to six Clear out this list now All right, Sean with three. Well, actually Gretchen you have all the numbers except for three five and six Gretchen has the rest eight zero nine four seven one and two Good luck Gretchen. Good luck Sean and Grant Let's order those numerically And coming up in a separate video will be the break itself jaspyscasebreaks.com. Bye. Bye


How's it going everyone? Caleb here with Leighton Sports Guards. Next night we're gonna be working on the Obsidian Basketball full case break tiered random team style this time. This will be break number 13. Thanks again for joining everyone. I do appreciate it. Here are the results for you one more time from that random. Let's get right to it. Good luck all. Obsidian Basketball. You're in good time. How's your knife blade looking? Sharp or not sharp? You're in bed? Yeah. I'll just need it before the Almanac that's all. I know what the Almanac can do to the knife blades. Here we go. Here we go guys. Good luck. This should be a fun time here. One person? No problem. Cable clips? No maybe it's up there. Yeah they're around. They're definitely around. All right here we go. Good luck guys on Obsidian. Tiered random teams. All right we got MoBomba, Magic, Wontoskano Anderson, Warriors Rookie, and Keras Levert Cavs. Next up is gonna be a Green to buy his hair at Sixers. Green is gonna be number to 25. We go Sixers. Nice green. And then Herbert Jones. Nice that's gonna be purple. Number to 99. 73 and 99 for the Pelicans. Nice one there Pelicans. Solid purple. 77 of 99. Autograph is Kevin Werder. Hawks. We go Hawks 77 and 99. Kevin Werder. Yeah we do UFC as well Judd. Yep and it's gonna be numbered here. 87 of 149. Latrell Spreewell Autograph. T Wolves. Nice hit T Wolves. We go nice Latrell Spreewell. Next one Here we go here we go. Yes Spreewell. Cool player. Cool player. We got guys. All right we got Kareem Abdul-Jabbar, Lakers, Shrey Young Hawks, and Lance Stevenson on the Pacers base. There he is. Shai-Gilgis Alexander. Thunder. Number 27 and 99. And Josh Giddy. Nice one that's gonna be green to 25. Yes it is 23 at 25. Nice Josh Giddy Thunder. There you go. Good start for you O.K.C. Chris Pete. There you go man. Awesome card. Next one up it's a Kevin Werder Autograph. Again Hawks this time. Again 16 of 50. Another one. So nice we got him twice. Two times there on the Werder. And Volcanic Autograph to 149. Mike Bibby Kings. There you go Kings. Mike Bibby. Not too bad. Next one up. I think I've used the same knife blade at home for like five years though. So like they can't be that bad right? Like you could always get it done you know. They get bad but like you can always get it done. Yeah. Is the point.  That's correct. Fred Van Vleet Raptors. It is Ari. It is. What's up Art. Harrison Barnes Kings. Jonas Valentinus for the Pelicans. We have Blue Flood. Akema Lyjewan Rockets. Nice one. Not numbered. Blue Flood. Sick card rockets. Those are awesome looking. Randy G. Nice Blue Flood. You don't want the Akeem the Dream. And then we have Pitch Black Anthony Davis. Number 17 of 99. Next one up here is going to be numbered 118 of 149. Galaxy Autograph Nuggets. Zeke Najee. There you go. And there he is. How about Jalen Green on the rookie patch autograph. Boom. Four of five. Huge card rockets. How about that one Randy.  Oh man.  Congrats on that. Look at the patch. Once again looking at numbering four of just five on the Jalen Green RPA. Congrats man. There you go Randy. There you go. Great hit. That card is sick. In addition nice color match. It's called long just so you know so it will not be magged. It will be top loaded and handled with extra care. It will not be magged like I said for that reason. It's cut a little bit long. Happened sometimes with obsidian and a handful of other products. All right. We've got Kyrie Irving Nets. Right Randy. That card's nuts. Steph Curry Warriors and Jericho Sims Nicks. David Duke Jr. now that is Nets. Once again red. Two of five. Nice rookie there. Two of five. And it's going to be a James Harden on the pitch black. 51 of 99. James Harden. Matrix material. Two of 25. Patch autograph of Nicholas Batum. Clippers. Three color patch auto. Batum. And it's going to be this time 132 of 149. Heat. Galaxy autograph Duncan Robinson. There you go Heat. Nice one there. Very solid. Yeah I love that one Dave. That's great stuff man. All right let's keep it going guys. Brushy. Cool. You're the man. Effortless. Effortless I tell you. Yeah. Let's keep going. All right here we go. Duncan Robinson. Josh Giddy base. Thunder. Nice. Tobias Harris. Sixers. Akema Leijewan on the purple. Number 1099. And JoVal Pelicans there. Number 19 of 50. Pelicans. JoVal. Next up here it's going to be Maverick. Spencer Dinwiddy. Purple autograph. Six to 75 there. And we've got King's autograph. Number 38 to 50. Mitch Richmond. For the Kings. Go Kings. Just that one huge box so far. Let's find another huge box like that one. That one was ridiculous. Let's get back over to those boxes. Come on. Good luck all as we continue. Base cards. Harrison Barnes. JoVal again. Scotty Barnes. There you go Raptors. Patrick Beverly. Timberwolves. Number 22 of 99. And Nikola Vusevich. Red for the Bulls. 3 of 5. Another red. There you go Bulls. 32 of 75. For the Nets. Rookie autograph. David Duke Jr. Nets. And autograph. Jazz. 74 of 149. Bojan Bogdanovich. Jazz. Go Utah. Guys next up tonight National Treasurer's Basketball Case Break. What are we hitting? I want to see a true man with just like a four color patch. Something that'll really sell for big money. I want to see a big true. Any rookie will do. Any of those. There's like 10 good guys that you can grab up from this class. Kaminga Warriors. That'd be one of them. Yeah logo man's are beautiful of course. Bojan Bogdanovich. That's Jazz. And Stephen Adams Grizzlies. Fred Van Vleet. Raptors. Number 299 there. 11 and 99. And magnitude Clay Thompson Warriors. It'll be 8 of 75. Magnitude there. Very cool card. This is true. I just pulled Trevor Lawrence cards. That's it. 23 of 149. Grizzlies autograph. Tony Allen. Nice one there Grizzlies. That seems to be it. And autograph for the Spurs. Number 8 of 35. David Robinson. Go Spurs. Nice lightning strike auto. Sick auto that he has. Very nice. David Robinson. You can see it right there. David Robinson. You guys see it. Nice sit there. Next one up. I got Sean looking at it. Oh man. Let's keep it going. Good luck. Good luck. Let's see what else we can find guys. Omar Yurt 7. Heat. Kintavius Caldwell Pope Warrior. Excuse me Wizards. And Austin Reeves Lakers. Jonas Valenshunis. That's Purple Pelicans. Number 7 of 99. And pitch black. Donovan Mitchell for the Jazz. Uh 19 and 99. You go Jazz. Not too bad there. Wow another one to five. Two of five. Pacers. Awesome rookie patch auto. Isaiah Jackson. There you go. Check out the patch. How about that one there. Indiana Pacers. That's Simon H. Nice hit Simon. It's a beauty. Two of five. Yeah two of five. Very nice. Letter patch. Part of the A there. Very cool man. Nice card. Like that one Dave. And here we go. 23 of 75. Herbert Jones. Uh Magnet. Sorry. Uh Herbert Jones is 75. Nice one Pelicans. Patch is kind of cool. Yeah. Pretty dang cool. Not the top rookie but I mean to five him with a patch like that. I'm pretty excited to see something like that. Arrive in your uh package. Next box up guys. And good luck everyone. This again for getting in. Been in good time so far. Deontay Murray Spurs. Trayman Thunder. And Patrick Beverly T Wolves. We have another red. Kyle Kuzma four of five. Red City tonight. Taking that trend from last night again. And tunnel vision is the metal ball. Very cool. Nice one. Going to be number 24 of 35. There you go Hornets. Nice card. Lamello tunnel vision. Heaps three of 50. Max Truce autograph. Come on give us a nice patch here. 18 of 35. Patch autograph. John Stockton. There he is. Nice purple color match for the jazz. Yeah man. We pulled a red grogu last night. So now it's uh now we're just continuing on the red from that. It appears. Here we go. Maybe there's a big red in the Almanac that I'm going to pull. Sean's thinking about it again. Oh boy. Oh boy. Only a couple breaks away from the Almanac guys. Literally only a couple. I'm going to take this one right off the back first here. Supernova. Kevin Durant. Nice one. That's numbered 48 to 75. I saw Supernova.  Not a die cut here. That's right. There you go. Rest of the base cards here in the green. Green to here in Fox. Nice one there. It's a 25. 23 to 25. Kings. There you go. We got Bradley Beal. Wizards. Face. Quintin Grimes. Nix. And Kelvin Johnson. Spurs. We have Hawks Autograph. Onyeko Okangwu. Galaxy Autograph. 27 to 50. Here you go Hawks. Nice. Yeah cool. The mellow card there. And there it is. It's going to be a Carl Anthony Towns for the T Wolves. Galaxy Autograph. 11 to 25. Nice Carl Anthony Towns. Very cool. Two to go. Let's see another RPA. Come on. RPA time. Empty. Lock and lock guys. Drew Holiday Bucks. Montres Herald Hornets. And Luca for the Mavs. There he is. Damian Lillard. Trailblazers there. That is numbered 16 to 99. And Supernova of Josh Giddy. Sick one. One of 10. Nice hit Thunder again. Thunder with a couple of nice Giddy cards. One of 10 this time. There you go Thunder. Very nice. 13 to 50. Jazz Autograph. Nikila Alexander Walker. 13 to 50. How about that one? T Wolves again. Anthony Edwards. Galaxy Autograph. 17 of 75. Boom. That's sick. Nice hit Jose. There you go man. Nice ant man. We'll mag that for you. That's beautiful. Like the Galaxy Auto. Nice ant man. Congrats on that. Last box. Let me take that. Solid case here. See what the last one has guys. We're moving on to National Treasures Basketball next tonight. That's one. This is going to be a card man. This is a sick one for sure. We have Vitrious SSP. About one per case here. Yanis for the Bucks. Congrats there Bucks. Nice one on the SSP inserts. Congrats there Milwaukee. Awesome card. From the back here we have a Tunnel Vision Trey Young. Solid there. That's numbered to 75. More base. James Hardin base. Shack base for the Lakers. Yeah that's a sick card Greg.  I'm a big fan of that one. Big Bucks fan. I am very jealous of that hit. That is a really cool card. Jose again on the Bucks. Jose did well. Welcome Brogdon Pacers. We've got Bogdan Bogdanovich numbered to 149 on the auto there. Hawks. That's a sick card for sure. You know Hawks. Autograph 10 to 25 Kelly Ubre. Looks like we got an extra hit. Nice. 10 to 25 Hornets. And last one here is TJ Warren. Yeah extra hit. One of 10 on the gold autograph. Nice hit Pacers. One of 10 Bubba Warren. Very solid. Yeah Greg that seems so low. Very nice. Good stuff guys. All right let's do a recap here of the hits. Thanks again for joining all. Appreciate it very much. Let's go right over these autographs again. All right we had autographs. TJ Warren. Pacers. Kelly Ubre Jr. Hornets. Bogdan Bogdanovich Hawks. Nikhil Alexander Walker Jazz. Carl Anthony Towns T Wolves. Onyeka Okangwu Hawks. John Stockton Jazz. Max Drew's Heats. Herbert Jones Pelicans. David Robinson Spurs. Tony Allen Grizzlies. Bo Yan Bogdanovich Jazz. David Duke Nets. Spencer Dinwiddy Mabs. Mitch Richmond Kings. Nicholas Batum there. Clippers. Duncan Robinson Heat. Zeke Najee. Nuggets. Mike Bibby Kings. Kevin Werder Hawks. The Trell Spreewell T Wolves. And Kevin Werder Hawks. Hey what's up Schlager? Once again that Magdianis. Vitrious.  Congrats again. Box on the hits. Beauty. Ant-Man there. This is autograph number 17-75. We've got the Isaiah Jackson patch autograph. Number to five. Two of five. And the Jalen Green. This one is cut a little bit long so we are not going to be magging it. It will be top loaded and safely protected up for you. This is RPA four of five. Congrats Rockets. Thanks again everyone. Appreciate it. We'll have them all well protected and right out to you.


So, this is my first talk in a conference. Be kind to me, please. So, I'll be talking about the mistakes that we fixed. A retrospective of the TRIBO mobile app. So, a little bit about me. I'm Kashesh Grover and I've been building with React Native for about two years now. You'll find me speaking about React Native to my fellow developers in our local React Bangalore community. I also like to play drums, drink beer and cook. So, about me at TRIBO, I've been here for one year almost and I've been solely responsible for our consumer app. And I joined when the project was orphaned. So, basically I got a code base which I had to fix for them. And the developers at the time, they had left and they brought me in to take care of this app. So, at TRIBO, we absolutely love React Native and we've been using it for about two years and our consumer app is completely React Native. So, all that said, it's been a super bumpy ride for us and even though it has been a really rewarding one. So, today I'm here to talk about our experience with React Native. I'm here to talk about some mistakes so that you don't make the same mistakes that we made. The mistakes I'll be talking about are three of them which is unhealthy code, bad developer experience and poor performance practices. So, I'll be talking about all of these in detail one by one. So, let's get started. So, talking about unhealthy code, I'll be talking about engineering baggage, chaotic rules, improper app versioning, confusing project structure and unsystematic components. So, starting off with engineering baggage. Now, any not so simple app needs third-party libraries to implement different features. So, our app, it was an experiment at the time by people who didn't know anything about React Native. So, a lot of libraries at the time were chosen just to save some time. I mean, we already had a React ecosystem and we just wanted to be able to copy-paste code. So, but some of these libraries would end up causing us so much trouble later that I had no idea. And it was difficult to fix them because I didn't code them right. So, it was difficult for me to fix all these issues. And things like this would prevent us from going to a newer version of React Native. And React Native development is super fast.  And some of the newer libraries, they also required us to update to the newer React Native version. So, we were sort of stuck in a loop. And I mean, so, let's talk about an example. So, we had a library, we have a library called React Native RazorPay, which helps us facilitate payments in our app. Now, this particular update, it required us to update to the latest version of React Native. And it says this package has been tested on version React Native 0.58, which is a very newer version. Now, you may ask me, why did we need to update this in the first place? I mean, it was working fine, but still, why did we have to update it? That's because a few months back, Google changed their permission requirements around SMSs. So, we couldn't ask the users for SMS permissions anymore based on our use case. We are a hotel booking app. We cannot ask the users to be able to read their SMSs. So, we cannot take this permission anymore. And this permission was being asked in this library. And these guys, they went ahead and removed that permission. And so, we had to update it to the latest version. But to make our app compliant again, we had to update React Native as well. Now, you know, we all know what an app experience is like. Some libraries were chosen to make it easier for us to copy page score. For example, we have a navigation library, right? We had a navigation library which didn't even save the scroll position.  I mean, that's just really poor user experience. That's not like an app at all. So, in our case, it was primarily visible when we went from search page to hotel page. And then we came back. The whole search page would get remounted. So, imagine you are on hotel number 40 and you just go back to the top right away. So, these kind of libraries, they got stuck with us for a very long time. And we also had been using a few component libraries. But tell me one thing, is it fair to use these kind of component libraries if we hadn't been using all those components that React Native gives us out of the box? And we weren't even using these component libraries completely, right? So, figuratively, this is what our app used to look like. So, to fix this kind of an engineering baggage, we have four options. Update it. I mean, is this library better now? Is this something which is popular and does it continue to have good support? Remove it. Can we make an alternative for this in the existing codebase? Replace it. Is there some other library which does a better job? Absorb it. Okay, so we cannot get rid of it and we cannot keep fixing these issues. But maybe we can fix some small things. So, why not we copy that in our codebase for now so that we can replace it later on? And we ended up building a few abstractions as well for things like components for load-ash functions and other utils, for services that work with business logic so that it becomes easier for us to change these abstractions later on. And we ended up replacing this old navigation library I talked about with React navigation. And now that Skoll thing is not there. Skoll position is saved because React navigation works on a stack. So, after getting rid of most of this engineering baggage, we spent some time to upgrade our stack. And I'm happy to tell you this that we are on the latest, I mean not latest as of two days ago, but the latest version of React Native now 0.58.5. So, the latest version is 0.58.6 as per what I read. And after making our package.json as lean as ever, it has become much easier for us to upgrade our dependencies for 90. Next thing I'll be talking about is chaotic rules. All our front-end projects are based on React. And this React Native app didn't even follow the same LinkedIn guideline. That was just super bad developer experience. Imagine you are a web developer, you are taking a look at my PR, but it doesn't look the same. So, PR reviews were super difficult and because at the end of the day I'm just writing React still, it should be easy for other front-end folks to be able to jump to the app and probably implement a feature or two. So, also the same business logic was there between three projects, which is our website, our mobile site, and our app. And it was being written thrice, right? So, how do we fix that? So, what we did was we shifted all our front-end projects including our app to our monorep. And we now follow the same LinkedIn guidelines. And we, you know, some code is shared now through some common utilities and some common service functions. And there's even a possibility now to share business logic. This is what our front-end monorepo looks like and that's the mobile app. Not sure who came up with the Transformers naming convention. Then I talk about improper app versions. Now, the app was, the way the app was versioned at the time was really bad. Even if something was a feature, it sometimes was released as a patch. It was just really annoying.  While the developers, they did try their best to write the commit messages properly. Something was still missing. And, you know, as you know, React Native supports on the air updates, right? Which basically means that you can manually release a JavaScript bundle, your app, which will, which your app will download and apply it on runtime. The most popular way of doing this is using code push, which is an open source project by Microsoft. But you cannot code push any native changes. So, with React Native, you can also write some native modules, right? You cannot code push anything which is with respect to that. So, how safe does this look? It says code push, release, React, Vivo, Android, deployment name, production, target binary version 2.3.0 to 2.3.8. Rollout 100%. How do I know, without any proper versioning, that there were no native changes which were released as patches? There were no features that were released as patches, between 2.3.0 to 2.3.0. So, to become much more aware of what was happening and to be much more confident, we decided to follow a simple semantic versioning of major.minor.patch, which is something we were already doing. But now we decided to put some rules around that. Now, Commitize and Forget is an amazing software which helps name each commit properly. And so we started using that. Even though we still update our app versions manually, it is easy to automate this using the Commitize and Naming convention. Let's see how that looks. So, say I run a command, npm run commit, which internally runs a Git, a CZ, which is Git Commitizing. And now I have some things to select, right? Whether it's a test, whether it's a feature, whether it's a fix, so that this particular tag gets added before my commit message. And obviously, you can easily run a script on that, right? Because all your messages now follow the same guideline, you can easily write a script around this. So, if I select a feature, some script should run later to increase the minor version number. And at the moment, even for any native changes that we make in our app, we increase this particular number because it's just a convention that we follow so that we don't code push anything wrong. So, if I select fix, it should increase the patch version number. How safe does this look now? With all those native changes not being code pushed anymore, I will be only code pushing a patch in this particular code push. So, it's the same exact command, but I'm much more confident about it. Confusing project structure. So, earlier we used to follow a type-based structure. And this is a project structure you get out of the box in most of the boilerplate projects out there. It's a very good project structure. It aims to solve a very nice thing that, you know, everything which is a container will be in a container folder. Everything which is a component will be in a component folder. Everything which is related to Redux will be in a Redux folder. Similarly for styles and assets. But this made it difficult for us to plug and play features. Now we are a product-based company. We sell hotels, right? We sell room nights at hotels. So, if I'm, you know, releasing a feature which is, you know, to get more users, I'm adding a wallet. So, something like a wallet. Let's see how that looks like in this project structure. You have your assets which is, in images you have wallet image. Containers you have your wallet page which has all the other components with that. In Redux you have something called a wallet duck. A wallet duck is basically just actions and reducers together, which are related to wallet. And then in services you have wallet service. I mean, how about we move all of these to one single folder called wallet? This is the question we ask to ourselves. So, that's where we came up with the project structure that we use today. We now use a feature-based project structure. And it makes easy for us to plug and play features. And the context of the features belong to one single folder now. Now it's also much easier for us to, you know, search for code snippets and locate files which are just related to wallet. So this is what it will look like now. You have a wallet. You have some components inside a wallet. You have a wallet image, a wallet duck, a wallet service and every other file which is related to wallet. Then you have user pricing, booking, hotel navigation. Everything is just a feature. Even if I talk about navigation, it's just a feature at the end of the day that my app follows. So earlier it was sort of like this. Assets, components, conflict containers. On the left you see how it was like before. Then in containers you have all your pages. You have Redux and services. But now it looks sort of like this. So if I added AB testing, it will go to the AB folder. Something related to analytics goes to analytics. And obviously this is still being refactored. It's still in the works, but you get my point. Then in unhealthy code, I'll be talking about unsystematic components. Over time as we progress, we noticed how unsystematic our components were. Even between our react-based front-end projects, code would look extremely different. There was no single pattern being followed, which would say, make my app portal page look similar to the mobile site portal page. Why did this have to be a case? At the end of the day, it's just react that I'm writing. To bring in some system and how we write components in our applications, we decided to invest in a component library. And I think everyone should do that. They should have even a components folder where you get your components from. Have your abstractions ready. In our case, we call it leaf UI. And we set some ground rules. This is where all the basic components are exported from. We import everything from leaf UI and we rarely write styles anymore. I'll show you how we do that. Instead of doing that, we use something called enhancer components. And these enhancers simply pass down styles as props to their children. Take a look at this example. You see a screen which has a center-aligned card. Card has two components, a tag and some text. Notice the code from top to bottom. Flex enhancer passes down some flex properties to a view which makes your full screen. Then flex once again passes down some flex properties to a card which is elevated. And it renders a tag and a text in a row. Now the space enhancer takes care of the padding and margin. Numbers that pass down to it are multiplied by eight and it takes an array. So if you see space margin over here, see over here, space margin 0, 2, 0, 0. That's basically top, right, bottom, left. That's being multiplied by eight. So I said that to the right side, apply a 16 margin. Other than flex and space, we have enhancers for size and position. This kind of a change obviously takes time. You cannot do this thing overnight. When you decide to set up some ground rules, it will take some time. Now my code base is like my room. It gets dirty.  That's because it's my room and I love it anyway. So what I mean to say here is that we are always refactoring and we don't ask for extra time to refactor. It's just a part of our daily life right now. So if I'm working on say a hotel page, I will make sure that I refactor that as well as per the new leaf UI guidelines that we have in place. The second mistake I'll be talking about is bad developer experience. So I am able to speak to you over here today in this talk is just because how confident I am about my releases. I now rarely have to give any production support and the practices I'll be talking about here are what gave me a work life balance. Let's get started with point A, bad local debugging experience. So when I joined, I noticed that there was no proper tools. There were no proper tools for debugging in place. And myself was rather new to quality tools for react native. I used to mainly rely on console statements. And at the time the local debug flow in general at Revo heavily used Chrome developer tools and console statements. And there was no information regarding Redux actions, API calls, local storage, among many other things. So fixing this was really easy. I just had to Google to find the right tools. And locally, there are two amazing tools available that I use personally. It's react native debugger and reactor. Both of these are open source. And they give proper feedback around API calls, Redux actions, local storage and a lot more things which are just related to react native. So debugging locally has become a breeze now. And they're both awesome. And I would suggest that you use both of them. So this is what reactor drawn looks like in its timeline. What is how beautifully displays all the actions. So on top of where it says get landing page content, then you have some other Redux action, then some async storage actions that took place.  So log image, custom display, connection, benchmark, API, mutations, actions, and even other things. But I personally don't use reactor drawn that much because of this. Now this is called react native debugger. This is again an open source project. And this is something that I use every day. It gives me a combination of Chrome developer tools, react developer tools, Redux developer tools, and certain features which are specific to react native. So say for example, if I have to make my internet slow, I have to test my app on slow internet. I just use this tool like I would use Chrome to do that. Basically set it on 2G or 3G connection. And on the right side, you see the API calls properly similarly similar to Chrome. And on the left side, you see the Redux actions. So it's just too easy to debug locally. But the nightmare for me was production debug. Since the beginning, we have used bug snack to track our crashes. But our production crash reports on bug snack, they were paralyzed. I tried to upload react native source maps to bug snack, but the result just wouldn't help me enough. Even after uploading the source map, the stack based bug snack would point would give me used to point to a different line.  That's your error statement. And the line it is pointing to is some import statement in some library. That is something that used to happen. But so, you know, I stopped, uh, stopped uploading these source maps and the report would now show me, uh, obfuscated code. A line number in the obfuscated JavaScript bundle. Luckily for me, we were using test IDs and accessibility, accessibility label. Most of the components. So this is how I used to debug at the time. You know, uh, I would get the line number pointed by the bug pointed by bug snack and manually find it in the JavaScript bundle. I would then copy this line of thousands of characters to a new file and then carefully go through it. I would pray for something like a test ID or accessibility label, which wasn't obfuscated. I would then spend a few hours trying to reproduce the crash using all this information. But they had to be a better way. So this one time I got so pissed. I decided to post this roses are red. My app is red and handle JS exception type error and defined is not an object. This is what my life was at the time. But, you know, as it turns out, bug snag is awesome. It's a brilliant platform for tracking crashes. Why it didn't work properly for us before was because of my own point. As I said earlier, source maps weren't working correctly, right? But it turned out that my builds and source maps weren't clean. Clean builds, they deserve clean source maps. So after setting up our CI CDs, I basically added a source map upload script, which runs after every clean release. So we have a clean release. It deserves a clean source map. And so we also added some slack integrations on bug snag. And now each time there's a spike in crashes, we get some slack alerts. So take a look at this snippet from bug snag. It says on top, it says null is not an object evaluating E dot measure. And over here, you have some stack trace. Now, after the source map is working, it's telling me everything properly, evaluating E dot measure points to component dot measure, which is something that was crashing every once in a while. But wait, it said null is not an object. Let's go to the next slide. Go CI CD. This was another pain point. Now, even many months after I joined, we still were releasing to production from my own laptop. Imagine the amount of problems that could have caused them. The folder I was using to release was the same I used to work in. And you don't eat where you take a dump. Did I do a clean npm install? Did I clean Xcode or Android Studio before releasing? I think you understand what I'm trying to say. Now, we tried different CI CD solutions and we decided to stick with Bitrise because it gives Mac machines. Over time, we set up multiple workflows in it. An example is an idly bird. Here also, we get Slack alerts for everything, whether the build failed or whether it was successful and releases are also made using Bitrise. These are built on clean instances and so there's no chance of them being dirty. And Bucksnack source maps are also uploaded from here, as I mentioned. So this is what my app dashboard on Bitrise looks like. On the left side, you see proper builds that ran every single day. I talk about no test automation. In general, I'm a sole developer for the app at Revo. So I don't have time to write unit tests or any kind of test for that matter, but we did have some QA bandwidth. So let's see what we did. Now, all releases that we were making at the time were being tested manually. And due to human error, sometimes test cases could get missed. We also came to realize over time that certain bugs were device-specific and all this uncertainty was hurting us. Because of all this, we decided to invest in building a test automation suite on Amazon device map. A colleague of mine from the QA team wrote down a bunch of test cases of four flows in app. For example, the booking flow. You go from your home page to your information page to booking. Everything's there. And they achieved that by using test IDs and accessibility labels because those are what point to that particular component so that you can write automation on that. Now, nightly builds on bitries are followed by multiple device regression. There's high predictability in app stability, which has resulted in very good business. And this has also freed up some QA resources for better work because you cannot just expect them to keep testing everything manually. Now, they're writing test cases and they often do better things. So let's see what this multiple regression I talked about looks like. You notice six different devices on Amazon device firm, which ran about 20 different test cases. And you can see how for every different device they were failing. This could very well be some UI mistake that we made because devices have different screen densities. Maybe some component was overflowing, wasn't rendering properly. Something happened. Maybe even the API is crashed. You don't know what this meant at the time. So let's go to the next slide. And I'll be talking about some performance practices. So three things, bad school performance, overdraws in Android and poor APM is app performance monitoring. React Native has its own performance issues. It does. But you know, if you follow the correct practices, you don't have anything to worry about. It gives you a very nice platform to build amazing mobile apps. But you cannot keep on blaming React Native or whatever problems it has if you don't take a step to improve your app performance. So let's go through these one by one. And the issue that we faced back then and to some extent we still face today was the highly janky scroll experience we had on the home page and search page of the app. After some digging in, after some spikes, we were able to find some factors which were at least visible to us. Now, we were using a library to render SVGs, which internally used web views. Since React Native doesn't support SVGs out of the box and we were fetching these over the web, this seemed like a simple solution, right? The card component which was being listed out on the search page, it was rather heavy and didn't follow proper, you know, warning signals that React Native gives us. And the flat list wasn't well optimized. We hadn't read the documentation around flat list properly to be able to put some optimizations which helped you a lot really. And the animations on these pages were poorly implemented. Wait a minute. I said web views rendering SVGs. Let that sink in, okay? This is probably the most embarrassing thing that we ever did. So you see those scroll bars on top, right? On that particular component. Those are SVGs. And that's a web view. And on Android, you cannot even get rid of those scroll bars. It's probably still an open issue somewhere. You just cannot get rid of that on Android. So for a better scroll performance, we got rid of these web view-based SVGs. And now we use PNGs. And we simplified the flat list cards and removed some extra animations which were there in them. We added some simple to implement optimizations to flat list which are clearly mentioned in, you know, react-native documentations. But we still haven't done, you know, enough gestures to the animations. And we might just remove them for maybe a better and easier to implement UI. While I spoke about all these visible factors, there was also something really big, you know, a big invisible factor which was in the play. I'm talking about overdraws in Android. It's a major performance issue. It's not specific to react-native. Open any app in your phone, and I'll show you how to debug overdraws. It means that a single pixel is being rendered multiple times in a single frame of rendering. It happens when two components overlap. And it happens primarily when, you know, there are two different color components which are overlapping. So fixes for these overdraws, they can be too easy to be true. And they have a very high return on investment. Basically, just don't overlap your components. Don't overlap your background colors. You have to overlap your components.  Take a look at this example. This is, say, for example, a root of any app. It has, it is mounting root navigation inside some view which is a container. Now that has some styles on top which says flex is equal to one. Flex is one and background color is white. But don't do this if possible because you can always write a background color at some point later. So how do you debug this GP overdraw?  Now there is some color convention which is followed here. True color, I mean no overdraw. Blue overdrawn one time. Green overdrawn twice. Pink overdrawn three times. And red overdrawn four or more times. This is what our overdraws used to look like back then. And I started debugging this. This is what it looks like right now after the app looks exactly the same. There are few places where, you know, I could have used some extra background color, but it doesn't impact the usability of the app at all. This clearly still room for improvement. Say, for example, in the hotel space, last screenshot is from the hotel space. Still room for improvement, but we have, we have reached we have crossed a long way here. So I also decided to do some performance profiling of our older app version before we did all these performance improvements. This is the profile of the user opening the app, selecting a city, scrolling, going to a hotel, booking it, the whole major flow that you would expect the user to do. This is what the profile looked like. That's, you can clearly see the CPU and memory usage. Whatever the numbers are. I mean, I didn't go into detail as to what percentage this thing denotes. I just decided to do a performance profile of the newer version. This is what it looks like. So profiling GPU rendering. How do you profile that GPU rendering? You go to developer options. Select on screen as bars. Let's take a look at these demos. So this is our older app. And just let that sink in. This is our page and I go to my search page and I was talking about janky scroll experience. Do you see those bars crossing the roof of the phone? This is how bad it was at the time. So let's take a look at the GPU rendering profile at this point. So not much of a difference on the home page or landing page. You still see more or less a similar graph. But wait till you go to search page. Much better, right? It's at least far more usable now. It wasn't even usable before. And we must have lost a lot of business just because of our performance practices at the time. This is nothing going through the roof exactly. So last thing I'll be talking about is poor app performance monitoring. We didn't have any statistics to measure apps' performance in production. This would make it difficult for us to convince business to implement performance improvements in general. There was no way that we could relate these kind of performance improvements with conversion improvements. And there was no way to tell whether the app was slow or whether APIs were slow. And we were already using New Relic for all of our other apps. So we decided to integrate their Android SDK with the app along with the native module, which we built to trigger it from React Native. We connected our pre-existing analytics events for which we used segment for that. So segment analytics events also now connect with New Relic so that we now get some performance metrics in place. We can now relate analytics events and performance and we then prepared some relevant dashboards and we now have some well-defined benchmarks. So I'll go through that. You know, this is part of the dashboard. All these shots I'll be showing are part of the dashboard. So this shows crash rate by version, which is already there on Google Play, Google Play console. But it's good to see it all in one place so that you can track your releases properly. Then you have, again, crashes. Another graph for that. Then you have number of users by version. And then you have number of users by OS version on Android. Now, here you see four different dashboards, four different tables. ATFI, it stands for time-to-first interactive. It means the amount of time it takes for something to become interactable. You know, how often, how soon can a user start using that page? And this dashboard, it shows exactly that for both Wi-Fi and cellular on both our search results page and hotel details page. And this can directly impact user conversions if the numbers are too high, right? So if it's taking more than 30 seconds on a particular page for a page to become interactive, that's a really bad warning sign. And this is where we had some benchmarks in place and this is what we strive to improve over time. And you have prepared bookings day-wise. Can't show you the numbers obviously here. Then you have error rate by domain. So API crashes. Something went wrong in the API. Were there any 500s there? So you get to know all of that. Then prepared bookings by app version. Now, since this directly comes from segment, I can even track my iOS app here, which is something we'll be working on at some point. So finally, the conclusion of my presentation. We have an updated stack. We have much less dependency on third-party libraries. You have a great debugging flow. You have a proper CI CD setup. You have automated regression testing. WordPress is thriving in the Monorepo. Great component library in the name of Leaf UI. And easy to read components. You have a much better navigation experience, much better performance in the app, greater understanding of the native side. And now we actively monitor performance. But we still have a long way to go. But where we wish to see React Native is, you know, we'll continue to use React Native, no matter what. I absolutely love it. So as long as I'm there, I'll be using React Native for sure. So we wish there was some great performance out of the box. Maybe the newer architecture of React Native will solve that for us. And I wish there were some more warnings on preventing overdraws in Android. And more warnings on preventing some general bad practices which I noticed were wrong in how you write opponents in the first place. And it should be easier to upgrade. I spent about 25 days to upgrade to a newer version of React Native. Meet me in the cafeteria or somewhere outside. I'll tell you how we did that too. And improved animated performance. And an easy to implement gesture system. I don't know how to use the gesture system even today. So I done it. I think we all deserve a cake. That was a long presentation. Thank you, Krishna.


All right folks so listen up. So a couple of weeks ago I filmed a video on how to film a cinematic b-roll anywhere and that got over half a million views which is totally crazy so I thought why not make a similar video and show you guys how to be more creative with your b-roll shots using your iPhone. So right now I'm at Greifensee which is a beautiful lake here in Switzerland and I love coming here and currently we have really cloudy skies which is perfect because the clouds act as a diffuser, softening the light which makes our videos look more pleasing and also it's not that hot and I think it's a perfect day to film some b-roll, have some fun and give you guys five easy tips on how to film creatively with your iPhone anywhere. See this over here? This my friends is a mosquito bite.  Now in the previous video I showed you how to film a cinematic b-roll video just handheld but this time we're actually going to use a tripod as well because this gives me more freedom to position my camera. And the tripod I'm using right here this is the one from Sandmark. This is the carbon fiber edition. The reason why I like this tripod so much is because it's super lightweight making it great to travel around. It weighs only one kilogram so it's really lightweight. Now this is more of a pricier tripod since it's made out of carbon fiber. It's around 300 dollars. There's certainly cheaper ones out there which I will leave links in the video description below but if you're like me who needs to bring other gear to you know create these tutorials you know every gram counts so I'm super happy about this tripod. And of course we have our camera. I'm using the latest iPhone as of making this video. This is the iPhone 14 Pro. So in terms of camera settings I'll be shooting on the default camera on my iPhone. I'll be choosing the standard video mode and the resolution I set to 4k which provides me the highest quality possible and the frame rate I set to 60 frames per second. This way I can slow down the footage. Now it's not always necessary to shoot in 60 frames per second. You will have to ask yourself if it's really necessary to slow it down but it's a good idea to mix up different frame rates to create a more interesting video. Now what I also like to do before I start recording is to tap hold on the screen until AEF lock appears. This means that your auto exposure and autofocus is locked. This will result in a more professional looking video as no exposure changes will occur while recording. So now that we have the basics out of the way let's get started with the first tip. So the first tip I have for you guys when it comes to getting creative b-rolls is to include a time lapse in your video. And this is where a tripod becomes really important as I can position the camera how I want it to be and also keeps the camera still. And I think including a time lapse at the beginning of your video will be a great opening shot. So the first thing you want to do is head over to the default camera app, select the time lapse mode function. You want to make sure your horizon is leveled and to get the best results possible you want to tap hold to lock the focus exposure and white balance. Now the time lapse works really great for moving subjects. In this example I'll be focusing on the clouds. Now keep in mind that the time lapse function on the iPhone currently supports only up to 1080p. If you want to record your time lapse in a higher resolution you might want to consider Filmic Pro. Now you can see that I have some foreground over here just to add some depth. Once I'm ready I'm going to select the record button and what it does is it takes a picture every two to three seconds and then compiles these images to create the illusion of time passing by. I'm just going to wait now for maybe let's say 10 to 15 minutes. You really want to take your videos to the next level you also want to include a macro shot in your video and on the iPhone 14 Pro I'm able to get really close to my subject to create those detailed shots. So you can see that as I come closer it now switches to the macro lens and you can see that I can get really close. Now the problem with capturing these detailed shots is that the shakes are more apparent. Now I could increase the frame rate to 30 frames per second however the shakes will still be apparent and increasing it to 60 frames per second will disable the macro lens. So in that case you could either use a tripod and then maybe digitally zoom in to add camera movement to your shot or you could use a third-party lens like the one from Sandmarc the 100 millimeter macro lens. So this is the lens right here which I find looks even better than using the macro lens on the iPhone and also for those who do not have a built-in macro lens on their iPhone this is a great option. So I've attached Sandmarc's case and also screwed on the macro lens which looks insane so let's look at it right now. So I'm recording in 4k 60 frames per second so I'm gonna start recording I'm gonna do a push in slowly and you can see how nicely the focus shifts as I move the camera. So this creates a really interesting shot a nice natural-looking shallow depth of field. It really mimics the human eye and counteracts the artificial sharpening of the iPhone making your videos look more cinematic. Now Sandmarc does have a 25 millimeter macro lens but you have to be really close to the subject to capture those detailed shots while this one provides an extended focus distance. So when you're out on a shoot it can be helpful to search for the music in advance as it can drive the creative process. Have you ever listened to music and then all of a sudden got inspired to create something? Well it works for me and I get ideas of how the visuals can interact with the music and that is why I like to use Artlist who is our sponsor of today's video. Artlist offers a wide variety of high quality royalty-free music and sound effects that you can download and use in any of your projects. You don't have to worry about copyright issues as it's all taken care of. What I like about their music platform is that their search function is super easy to use and allows you to find the perfect soundtrack based on mood, video theme, genre and instrument. What's even better is that you can also find similar tracks to the ones you like. For me having good music not only drives my creativity but also helps plan out the b-rolls. Knowing what kind of music you want to use in your video can help decide what kind of shots you need. For example, if the music you picked has a lot of energy then you might want to film shots with intense movement like a person running. On the other hand if you picked something more relaxed and calm as I did for this video then you might want to focus on slower and smooth camera movements. Now big part is also adding sound effects to add more atmosphere in your videos and enhance your transitions. You can choose from different categories like ambient, realistic fully and more to narrow down your search. Now if you use the link in the video description below you can get two months extra for free. I highly recommend you check out Artlist and search for the music beforehand as it can help with your creativity and make planning your b-rolls much easier. Once again I want to thank Artlist for supporting this channel. With that said let's move on to the next tip. So the next tip I have for you is called the three shot rule. That's what I call it. You want to make sure to capture wide, medium and close up shots and in order to be more creative with your shots try to avoid shooting from eye level and think about how you can make your shots look more interesting. So we have this beautiful tree over here and we have the sun peeking from behind. So I'm going to start recording and go. So I'm going to get low to the ground. I'm going to set focus on this one over here and then create a push-in shot. As a bonus tip I've captured now a medium and a close-up shot. For the wide shot I'm actually going to create a masking transition. So what I'm going to do is move the foreground object and let it pass by the lens completely. I'm going to use the tree for that. So this is going to be the wide shot. I'm going to tap hold to lock focus and exposure. Once I'm ready I'm going to create a slide shot and pass by the tree. So this will be the second shot. It's going to be a static shot of me looking into the distance and I think it's going to fit well with the slide shot I created in the previous video where I'm going to mask the part out to reveal the shot. So I'm currently using the apple watch to frame myself and I think it looks good. Yeah I'm just going to start recording and look into the distance. All right guys it has been a long day but I'm happy we captured all of the shots. Let's now look at the final edit including the behind the scenes so you guys can see how I've shot the video. All right folks you made it till the end congratulations. I hope this tutorial helped you become more creative when it comes to capturing b-rolls so make sure to find a force nearby and implement those techniques that I showed you in this video. Now if you're wondering what colors I used they're from my premium mobile lutz which includes 10 creative mobile lutz that you can instantly apply to your mobile videos to make them look cinematic. So if you're interested I'm running a 50% sale make sure to check out the link in the video description below. Now if you want to learn the editing process behind it I have an online course called smartphone filmmaking.com where I break down some of my popular cinematic videos shot on an iPhone and walk you step by step of how I edited the shot and of course I have more tutorials similar to this one all available inside the course where I'll be showing you everything I know on how to get the most out of your smartphone. So if you're interested in that make sure to check out the link in the video description below. Other than that thank you so much for watching guys take care and I'll see you in the next video.


Type 2 diabetes, T2D, is a metabolic disorder caused by high levels of blood sugar and insulin resistance. It is believed that oxidative stress is a major contributing factor to the development of T2D. Oxidative stress is generated when there is an excessive amount of free radicals in the body, which can damage cells and tissues. Mitochondria are the main source of these free radicals, and they are also responsible for generating energy in the form of ATP. When there is too much glucose and not enough oxygen, the mitochondria become overloaded and generate more free radicals than usual. This leads to increased oxidative stress, which can then trigger endoplasmic reticulum, or stress. ER stress is also a source of free radicals, and it can further exacerbate the situation. Furthermore, the tight connection between mitochondria and the ER allows the free radicals produced in one organelle to spread to the other, leading to a vicious cycle of oxidative stress and mitochondrial dysfunction. This can ultimately result in insulin resistance, which is a key feature of T2. This article was authored by Estefania Burgos-Moran, Zayda Abad-Himenez, Franceso Martinez de Marañón, and others. We are article.tv. Links in the description below.


Hi everyone, Joe for Jaspy's casewrakes.com. Happy Monday. Happy first of the month as well. No happy November already November Coming at you with a prison basketball break Salo pack rate number 104 this edition right here with the final five Basketball mixer spots being given away This that sells out the mixer and we'll be doing that in the next video separate video big. Thanks to this group right here For getting it on the action. I appreciate it Don't grab the right list. Yeah, I did and there's the Team list right over here. Let's roll it. Let's randomize it two and a one three times or names and teams That's just for names and teams different dice roll for the giveaway part two and three three times for the teams one two and Three there's the first half of the list right over here There's the second half of the list right there I've got thunder clippers on in the background for your wondering what the background TV noises Thunder up for 52 47 With nine oh five left in the third quarter. There's the printout right there Thanks everybody for spending a bit of your Monday with us Let's see if you can see if there are any surprises here. Oh Surprise autograph and a surprise rookie silver Robert Woodard. I sure did David Robert would have penmanship autograph going to Michael and the Kings there's Isaiah Stewart rookie silver and the red white and blue Nothing too crazy there, but an auto in a cello pack. That's pretty nice. Let's flip back over here Let's grab everybody's names and Let's see who's gonna win those mixer spots top five after 11. Good luck one two three four nine Ten and good luck 11 the final time. So it's top five So from six on down No dice But I preach sorry Parker very close. No dice though. I appreciate everybody giving it a shot. Thank you So sad times for this group happy times for Parker Michael Parker Brian and Parker I guess I don't feel so bad for Parker. You got three out of the five spots Congrats to you and congrats to Brian and Michael. I'm Joe. I'll see you next time for that mixer Bye-bye in the next video


back to another XO's Heroes update. So today we'll have an update for tomorrow. So to start off this update, we have Quantum Challenge. In a way, I think guys, this is the Quantum Raid. So they just changed it. I hope there are content changes as well, aside from the name change. So yeah, it's still Quantum Raid. It's just named as Quantum Challenge. I do hope that this game mode is going to improve a bit because again, if it's going to be the same, a lot of players are not going to like this. And more or less, this is just going to be a, you know, a rerun, a again, a more a kind of boring rerun of a content. So again, I hope that they have new changes to this. Moving on. Sorry, this will be up tomorrow. August, I think August 12. Next would be the Air Squadron battle schedule. So the schedule will start on August 15. So as you continue to September 12. So again, we are actually waiting for this and hope that you'll be ready for your squadron for August 15. Okay, next would be your hero battle, which will be Monica's story. So for those who don't have Monica, you can actually get her here. Next would be summer vacation package announcement. So new package is here. So again, the packages, if you can see the one that stands out the most would be the summer vacation recruit package, which is of course 5,000 priced. And but it has a lot of things going for it, nation recruit 50 and more or less 20, 20 zest. And also the summer vacation zest package, which I used to get at 5,000, which gives you 4,000 zest just in case you need zest for your recruitment. The rest are more or less just basic. Those are the two recommendations that I have. If you really want to get these packages, attendance pass package, one per account, exclusive weapon crafting. This is also good because this has an exclusive weapon on the 14th day, nation recruits all around. Kind of kind of good as well. Zess 700. So the kicker here will be your exclusive weapon crafting ticket. So again, this is also good. So more or less the 5,000 ones, summer vacation recruit package, summer vacation zest package and attendance pass package is actually good. Next would be our fate core chance up, which is going to be the black fate core of gin. So gaze of the white girl gin, gin's summer bikini or summer get up or summer outfits or recruit gin from a parallel world who is able to easily meld into the surroundings with the gentle mood. So again, artwork splendid. I can't say more. And the weapon is actually very, very nice. So, but let's proceed first to the skills of gin. So for gin, the black fate core summer version, passive effect, finishing blow three attacks if an enemy takes damage and its health drops to 10% or less to gain swan mana. So he also has life jacket in terms of the theme. So buff, if an ally is affected with a debuff, remove all debuff from that ally and increase critical hit for all allies by 300 for eight turns. Upon successful removal one time per battle can't be stacked. Okay, imitate, imitate, right dive. So special grand stealth to sell for two rounds and increases own attack by 10% for each mana on self upon, upon reviving. Yeah, yeah, pretty much good. Next would be surfing debuff when an ally besides self attacks a charm enemy attacks one of the targets together and decrease the target's attack speed by 30 for five turns. So S1 would be shadow dive slash deals 180 damage to one enemy resets own turn. If targets, if target dies, a flake's target would silence for three turns mana burn. This is actually his usual kit. If the target is charmed, so mana burn and turn reset, S2 as well, active, required mana is two deals three five seven damage to an enemy ambush inflicts target with silence for four turns and mana burn. So again, silence, mana burn, pretty much a manual skill to use. Pretty much you can disable your enemies if you're if actually you're using stories. But again, I'd like to go back to his passive. So for his passive, he has let's go with surfing first. It's a debuff with an ally besides self attacks a charmed enemy attacks one of the targets together and decrease the targets attack speed by 30% can be viable as well. So I may look at it both both gold version and black version of of Jin or FC Jin. It's actually pretty useful. So it will really, really be up to your core memory. If you built up his core memory, then he is actually viable for people. You can swap out both. I'll have to test him out if I do someone for him tomorrow. I'll try to I think I will. I'm still thinking about it. Next, we'll have to go to his other passive. So again, a re-review, imitate dive, grand stealth to self or to round increase on attack by 10% reach mana on self upon reviving. So again, this is also a good spell to have and life jacket as well. Okay, so my thoughts on FC Jin, the the the black fake core version, he is he is going to be at par with the gold version of FC Jin.  But in terms of the passive, they're kind of there. They're kind of there. Different utilities, different kind of similar play styles. But there are a bit more sim differences. Like for example, for the life jacket, he gives a buff to all allies of 300. So again, and also decreases attack speed as well. We're surfing. So he is, I think he is more. I don't want to say this now because I have to test him and compare him with the gold FC Jin. But I think they're at par. If you ask me if you're going to pull for him. If you don't have the gold version of FC Jin, and if you're planning or you're using a storage right now, then I think you should pull for this dude. Because again, he will be valuable both your stories. I'm currently building a storage and really tempted to pull for the black fake core version just to test it out just to see if this is going to be better than the other one. So again, at this point, I'm saying yes to pulling this black fake core could be a good replacement or could be your first FC for FC Jin if you don't have the gold version of course. And again, kit is solid. I think it's solid. I don't think, I don't think it's it's not as good, but it's actually worthy of PVP as long as again, you have built signature force for your stories and core memory for this black FC Jin. Okay guys, so those are my thoughts for FC Jin. So again, I'll be I'll be doing a I'll try to do a summon video tomorrow for FC Jin and probably compare who is better him or the gold fated version. Again guys, thank you very much for staying this long and also please consider subscribing. Click the bell icon so that you don't miss any episodes of XO heroes. Also guys, please put a like to this video. Stay safe, take care. This is The Warden and I'm out of here.


Hi you guys! Lindsay here. Welcome back to my channel, Inside the Hymn. I really had a great time putting all of these together. These are in the wooded section of the craft store. You can find all kinds of little wooden shapes like this. So I have this gift tag shape. I have a circle shape and I got something that looks kind of like a Christmas dove type of shape and I just kind of got really creative and I used some gold scrap fabric in the back and then I put a strip of my gingham scrap fabric down the middle and then I just cut up a little strip of this natural kind of woven material. I cannot remember the name of what it's called. It's very common. Again, you can find it in any fabric store. I just made a little bow and thought that that was really sweet. Kind of like a gift tag, you know, gift looking thing. I should say that the fabric here is adhered using Mod Podge. Really simple, straightforward. You just kind of slap it on. And for the circle ones, I had a lot of fun. I wasn't done with my pom-pom maker just yet. I ended up making a blue yarn pom-pom and then just flattened it out on one side and hot glued it to the Mod Podge fabric. I also got some like cinnamon scented pine cones and just kind of like organize those cutely and place those on as well. The cinnamon scent doesn't stick around very long just so you know.  The cinnamon, I feel like is a little bit of a gimmick. Like it smelled great when I opened the bag and then now I can't smell it at all. Probably couldn't smell it at all like the next day if I'm being a hundred percent honest. But I thought this one with the pom-pom was super, super cute. I think this would be adorable too if you could make it. Like if you have one of those like nostalgic trees, if you could make it like Rudolph's nose, like if you made this pom-pom red and I don't know just did like a brown background and maybe a couple little eyeballs. I don't know. Doesn't that sound like that would be really, really cute? Maybe for next year I'll do like a vintage tree and be able to make some fun nostalgic ornaments like that. But anyways, the circle ones are a lot of fun too. And the dove ones again I did with the fabric mod podge but then I used a little button for the eye and I thought that that was super, super sweet.  So if you have a little, a little bit of a power tool experience or your husband or any of your friends have some they could drill a little hole in there for you no problem. If you don't have that no problem just do like we did for the cinnamon stick and just glue it in a knot. Just glue it on the back and that will work too. You don't have to have power tools to make any of this work.


You'll experience patient care that is specific to you with exceptional follow-up care that ensures your hearing and balance needs are being met. Audiology Associates at 1428 Northlake Drive in Prestonsburg. Billie Jean Osborne's Kentucky Opry is returning for the Christmas season with five holiday filled shows. The shows will feature holiday classics, giveaways and more. We have a very exciting show. The Junior Pros has an hour long show and we're doing something really exciting in the shows. We're giving away an electric guitar at every show and a month free lessons. A whole month they can come in and have lessons. So we're doing that all season and then after that in the lobby, our little group, the Rising Stars will be performing out in the lobby. So and then the big opera will be on stage. So we're super excited. Tickets are $25 and can be purchased at the Mountain Arts Center box office or online. Everybody can expect when they come to the shows is to hear a lot of great Christmas music that they know and that they love. They can sing along. There's a lot of audience participation going to be involved. We're giving away prizes. It's just going to be a great, great Christmas show. And that everybody needs to come support us. We work really, really hard and it's a great show. For more information or to purchase tickets, go to MacArts.com. Reporting for Mountain Top News, I'm Brianna Robinson.


By constructing infrastructure, for example, fencing off a water pan or drilling a borehole, which can actually be closed off and opened up at certain times, and also in view of the existing traditional natural resource governance institution called the DEDA oversees the grazing patterns. Now the DEDA system guides the community members as to locations where to go to during the wet season, and then as the season changes and moves to dry, they direct them on to start moving to the dry season grazing areas, and then when there's a drought, again the DEDA and there's also a Rangeland Users Association and now directs communities on which sites structurally go to in the drought season. The pastoral areas, the communities own land communally, and so pastoral communities from other counties as well, you know, move their livestock, looking for pasture and water, and often actually end up in some of the wards in Isiolo County. And what I've actually learnt over time is that Isiolo, because of the DEDA system, and you know this natural resource governance, has over time been like quite a big refuge for herders or pastoralists in the wider northern Kenya region. So during drought especially, her pastoralists coming from as far as Mars a bit from Ojiya, even Mandera sometimes, I think even Somalia, you know as the neighbouring country north-west, and Samburu and Turukana, so it's really, it's open land, and so being able to actually manage the water enables governance of the Rangeland User, and that has a direct implication on, you know, let me say the resilience of the pastoral community. So in a drought situation especially, if the drought reserves, you know, are conserved and conserved well, you find that now, you know, with the instructions of the DEDA and the Rangeland User Association, the water ponds and the bogals are then open, but when the hadas actually now move into these areas, they'll find that the grass is there, their livestock to feed on, but then there's also water. And the system is very regulated in that for each hada who brings their livestock, they're given a certain amount of time to water their livestock, and then they move away, and then, you know, the other group comes, so it's really done in a very, it's a very organised system actually. And so because droughts are intensifying, more frequent now, such an organised management system should enable the pastoralists to minimise loss of livestock. The infrastructural interventions together with information on climate, you know, so the climate information, for example, timely provision of seasonal weather, focusing on whether there actually is meaningful to them, can help them make decisions. Or, you know, for example, should I actually start selling the, you know, not very strong livestock at this point in time. So, and if we actually provide access to a market, you know, fairly close by, that should really help, you know, be able to actually do the off-take early enough. But there are other aspects as well. There are lots of other governance aspects. So there's the markets, there's the pasture and water, there's the management system for grazing, there's the use of climate information services, all this really, you know, meshing very well together. And, you know, our hope is that as we proceed, things like value addition as well will come in more strongly, so, you know, capacity development to the communities there on value addition to livestock products, because that will enable them, you know, increase household incomes, hopefully. And for me, I think that, you know, with greater household incomes, people actually have perhaps more options, even for decision making, so they don't have more options to consider and can actually take perhaps stronger decisions.


The form in a bin will bite. Last time, the obituaries told the story of Charlie Watson, the bookworm who sadly died due to the insane connection of the figure who looked like Marina Mordegard Glassgård. That was only proven when someone took a picture of the figure and connected the two pictures together and, sure enough, yes, it was indeed Marina Mordegard Glassgård. Somehow, someone, or something, became something more than just a short video, instead, something in reality. On October 1 of this year, a new update was released. It started by mentioning the connection between the figure and Marina Mordegard Glassgård, pointing out its 1700s look and the man's outfit matching perfectly. Another death was recorded exactly in April of 2023. The reason why it took so long was that police found an unmarked box and a laptop buried in the central park of New York City. The FBI later checked the laptop and found out that said laptop was strangely clean. Nothing illegal or anything suspicious, just a single folder named, Figure. That's when they heard a click sound, almost like a PC mouse clicking and the DVD player in the laptop slowly opened up, revealing a new CD called, Behind You, in messy sharpie. As the FBI chief pushed the tray back in, the same Figure folder popped up, so everyone in the FBI sat down on their chairs or on the floor and clicked on the anti-for-file. As the video started, it started with the normal Marina Mordegard Glassgård, but there was more as soon as the Figure smiled. It had an ominous robot voice. It said, Greetings. I am the Figure that watches people. All I want to say right now is, The Figure paused and everything grew silent. The chief was about to get up when the Figure charged at the screen as a loud pop and a distorted snap was heard from the video. The Figure said, almost sounding demonic. Behind you. Everyone in the FBI rather let out a scream or jolted from their spots, even some ran out of the office to use the bathroom or to just run. What happened next was what could only be described as a criminally disastrous report. On April 23, 2023, three of the FBI officers were murdered in an unmarked location in the outskirts of Las Vegas before their bodies were chopped up and heb in a box buried along with the laptop. The laptop to this day had been recovered, but everything from said laptop was cleaned off, even the CD from the DVD drive. To this day, the FBI and a new entire group foundation, the NCPS or the National Cyber Police Squadron, all joined together to find the Figure or the remnants of the CD before the Figure harms anyone else. It became less of a simple creepypasta, but a full-fledged manhunt.


And also thousands of Tunisian opposition supporters demonstrated on Sunday in the capital against President Kaisaid's power grab and economic crisis in the North African country. Protesters held up signs in English and French reading, Tunisia wake up and Tunisia state is on the verge of collapse. Said's last July sacked the government suspended parliament and moved to rule by decree spacking fears for democracy in the birthplace of the 2011 Arab uprisings. The latest demonstration was called by the free Dasturian party which is led by staunchly anti-Islamist lawyer Abir Mosey.