Proudly we hail from New York City where the American stage begins. Here is another program with a cast of outstanding players. Public service time has been made available by this station to bring you this story. As proudly we hail the United States Army. Our story today is titled The Face of the Enemy. And perhaps it is well as we shall find out for a soldier to realize that his enemy in combat will be no cardboard target in a field. He will be thinking, aggressive, resourceful and ruthless. And when we meet him, we will not only be matching weapons, we shall be forced to match wits. Our first act curtain will rise in just a moment, but first... Right now, here is an important message for young men who are high school graduates. Never before in history has there been such a need and such an opportunity to serve your country and yourself as there is today in the United States Army. If you're qualified, there are careers open for you in radio, radar, weather, communications, and many, many other fields. So pay a visit to your nearest United States Army recruiting station without delay and get full details. And now your United States Army presents the proudly we hail production, The Face of the Enemy, who are in training in a camp in the South. They were learning to be infantry soldiers. They spent their days in classes and in the field. After several weeks, they had a fair idea of what their equipment was, how to use it, how to take care of it. They were learning a great many things. They are your infantry soldiers who develop a vast reservoir of knowledge against the day each may have to draw on it. Their officers, combat veterans for the most part, were fairly well pleased with them because the platoons and their companies were shaping up. Of course, they had a long way to go, but they were getting there step by step. They had reached the point in their training, but they were going out on problems. And in all truth, here for the first time, things weren't going too well. For instance, a platoon would be told to occupy a hill. Another platoon would be told to capture it. Well, he would get a scene something like this. You're dead. What do you mean I'm dead? You're standing up in the open.  I got you first. You're dead. You're captured. Why are we captured? Because we're in back of you. Yeah? How'd you get here?  That's how we got here. You couldn't have crossed the field if we was firing real ammo. All the same, you're captured. They were grown men learning a grim business, but you couldn't help smiling. It sounded for all the world like children playing cowboys and Indians.  But basically, there was nothing funny about it. Men have to learn the principles of attack and defense. And the only way you can learn anything is to practice. It's like music, for instance.  If you want to learn how to fight, well, you have to fight. But how? After all, what are you going to do? Well, the colonel who commanded the training regiment was quite unhappy about it, too. But men aren't taking this seriously. And I don't see how you can blame them for it. We haven't digged foxholes and sit around for hours slapping at mosquitoes. We explode a few firecrackers here and there to simulate gunfire. We send some artillery a mile or so over their heads to give them an idea of what it sounds like. Then we tell them to move up a hundred yards to the left or right and dig new foxholes. We tell them that enemy paratroopers have landed. And they know it isn't true. All they know is that they're out in the cold or the wet getting miserably uncomfortable and nothing is happening. I think a new system of training is definitely in order. So for a while all the so-called field problems are called off. Instead, intensive courses were held in physical conditioning and proficiency with weapons. Officers and uncoms who had fought the Nazis in Europe and the Reds in Korea. Men who had been up against master specialists in the art of infiltration and sabotage gave exhaustive lecture demonstrations of how to fight an unorthodox enemy of what to expect of people who don't conduct combat according to the book. There was a unified purpose behind all of this, and it was apparent at that time. Then the regiment was told it was going to participate in a large-scale war game. Well, none of the men were really excited by the news. As a matter of fact, most of them were quite bored. Unit commanders who were briefing their platoons could sense it. First battalion will be on our right. Third battalion is back in reserve. Actually, you can forget about Third Battalion because we'll be surrounded by aggressive forces. Our mission will be to hold until Third Battalion aided by elements of the 22nd Regiment can break through to relieve us. Now, I've given you the whole picture, so... Wilson, where's the aid station? Well, sir, the... I see you don't know where the aid station will be. Maybe you can tell me where the reserve ammo will be. Well? I think, sir, the lieutenant said...  Miller, suppose you sum up this problem for me? Well, sir, an invading army has landed, I think, in Virginia. They've been moving south and they captured all of North Carolina. Now, our outfit is supposed to try to cut their left flank. Ah, yes, sir, that's it. Cut their left flank in half and relieve the pressure on Washington. Well, that's the gist of what I said. Now I'll say something else. You men weren't paying too much attention. You figured, well, here comes some more of the same old stuff. Only this time, instead of going out overnight, we'll spend a week with it. We'll dig a couple of hundred foxholes and we'll walk up and down for hours. And umpires will be running all over the place like this was a World Series ballgame. You're not taking this seriously because... let's admit it, you don't believe it. I believe that a foreign power has actually invaded the U.S. and that we're going out tomorrow night to fight them. Well, I want to give you some very good advice. Be on your toes. That's all. I think you like what you said. Hey, Miller, we got time to go to the P.X.? Nah, I'll be closing in five minutes. Might as well hit the sack. Oh, did you hear all that business? Who's on the right? Who's on the left? Nah. He said Virginia. We'll be out in the field over the weekend. No passes. What's with this whole bit? I know how to fire a rifle.  I can dig a foxhole. Anybody wants to start a war, I'm ready. Why do I have to sit around on a woods in a mud puddle all week? So what do you want from me? Catch it! Uh-oh, he's here again. Hatties, I've just been informed by Captain Clomb and there's a slight change in plan. We'll be to the left of the 1st Battalion, which means that our firepower will have to control the river crossing if the enemy plans to counterattack from that direction. We'll have to work out new positions for the aid station and supplies. All non-cons will report to the orderly room in 10 minutes. That's all. No, we've just found out that the troops who lack the part of the aggressor in this problem are elements of the 74th Regimental Combat Team. How'd you work? Hey, who's the 74th Regimental Combat Team? I've never heard of him. Ah, you know, Miller, there's lots of things about the army I don't mind at all. Oh, gee, that's big of you. No, no, I mean it. A lot of it's okay.  I can see that one stripe on your sleeve right now. Hey, when you make PFC, will you still talk to us common people, huh? Not just between you and me, take the lieutenant. He's okay, too. It's just these field problems, these maneuvers.   Now, what could be nicer than sleeping out in the open under the stars, huh?  I don't want to be ashamed of you. Hey, tell me, where's the aid station going to be? Where's the ammo dump going to be? Who's going to be on the left, the right, and the front, in the rear? You tell me. Well, I can tell you, buddy, is that this is the last night we're going to sleep in the beds for a whole week. Just watch me roll into that sack. Yeah, that revelry's going to roll around mighty fast. You know, I could even learn to like the army if everything didn't start so early in the morning. In a while, a quiet descended. And then a few minutes later, the clear, sweet notes of tapas echoed through the camp. The barracks' lights were out, and the trainees were all asleep. Except for the men on guard mount and a few others on special details, there wasn't a single private awake in the entire area. That's one thing about the infantryman. Nobody has any trouble getting to sleep when he has the time for it. Such thing isn't somnia in the infantry. And that has to be considered a solid credit. Well, they were all asleep. But not for long. Oh, no. Hey, whose bright idea is this? The aggressor staged a surprise attack. Oh, listen to that, will you? He sent patrols across the river and established a beachhead. They're going to have that smelly creek for all of me. Come on, now get moving. Hey, Millie, you want to be sitting down and dressing? And beyond those trucks and rolling. Hey, ain't we going to have chow this morning? The men's squad leaders sent one man to the kitchen for canteen for coffee. He'll pick up rations for the squad. Come on, now shake it up. They piled the trucks and rolled off into the night, still half asleep. They sipped coffee, which spilled all over them in the swaying trucks. They chewed at sandwiches and puffed at cigarettes. No one was comfortable and no one was happy. As far as they were concerned, the men who was were getting off to a bad start. Finally, the vehicles came to a halt. Orders were passed down the line and proceeded on foot. They went in one direction, then turned and went in another. There was the usual amount of backing and filling. And then platoon leaders and non-coms pointed out places for foxholes. And the orders were given to dig in. Yeah. Okay, Miller, okay. What do you want to do? Wind up in China? That's deep enough. Oh, man, I'm beat. Me too. Let's jump in. The other guys are still digging. Maybe we can grab an hour of shut-eye. Miller, Wilson. Yes, sir. You can't dig a hole here. You're too close to the B.A.R.T. Now go over 20 yards over to the left. Sir, you said before... Get moving. Great guy, isn't he? When I die, I'm sure going to leave them something in my will. Well, what's that? A shovel. Finally, the positions were all dug and satisfactorily. The platoon settled down to await the next move, which would probably be to go somewhere else and do the whole thing all over again. It certainly looked that way to Miller and Wilson as the lieutenant approached their foxhole. Hey, wake up. Somebody's coming. Who? The lieutenant. Why didn't you challenge me? Well, sir, we recognize you. We'll go into that later. I got a job for you, too. We're not sure whether the aggressive forces maintained their beachhead on this side of the river. They may have pulled back when we came up here. We have to find out. Now, both of you, make your way down the hill to the river until you can see what's what. Don't get too close. Just find out whether there are any of them still on this side. And get back here as fast as you can. Hey, we better not go much further. Maybe we can peek through those bushes. You can see the river from there. Why don't we just walk down the road? What's this plain soldier bit with dragging through the bushes? Well, if the enemy is there and spots us, we'll be captured, Saul. So what's bad about that? Let's get captured and sit the week out. Well, the trouble with that is you get put on KP in details. They don't let you do a week's worth of bunk fatigue. Hey, hey, where's all that smoke coming from? On the road, I guess. What could be burning there's no houses around here. It's too wet for a forest fire. Let's take a look. Can you hear somebody coming? Listen. Sounds like one guy. Better get out of here. No, no, wait a minute. If it's only one guy, why don't we capture him? See what I mean? We bring us back a prisoner. That should go good with the lieutenant. Hey, look, it's a civilian.  What do you think we are? And who are you? I don't know. Must be thousands of guys in the army these days. What are you so excited about?  The country's been invaded. What does this guy say, Wilson? Don't look at me like I'm crazy. There's foreign soldiers all up and down the riverbank. Now tell me, is there a nut house around here, Wilson? This guy's keepers must be sweating them out. I was driving along in my car. Guys in dark uniforms and funny insignia stopped me. They burned my car. Don't believe me, huh? Well, just walk down that path here and take a look. You got the guts to do it. Goodbye, I ain't hanging around. Oh, it takes all kinds to make a world. What do you suppose he was talking about? I don't know, but I see smoke. Come on. You see what's burning, Wilson? Hey, Miller, that's a car, an old beat-up civilian auto. Hey, and look at those guys standing around. Those are soldiers. What's going on? You see what I see, they're soldiers, but those uniforms, they're not American soldiers.  Am I? Those aren't our type helmets. We don't wear uniforms like that. Look at those insignia. Both of us are nuts. We got to be. We're dreaming. They're talking. Can you hear what they're saying? Oh, Miller, buddy, one thing I can tell you, they're talking all right, but they're not talking English. All right, what are we going to do? What you're going to do, I don't know, but all I got in this rifle are blank cartridges, and I'm getting out of here. Kid, you ain't alone. Sir, they burned this civilian automobile. They're in a funny kind of helmet. What do you mean funny? Well, it was a kind of a wedge running across the top of it, not like ours. And their uniform's kind of dark. They weren't Americans, that's for sure. We could hear them talking. It wasn't English. I don't know any more about it than you do. Let's get the CP. Sergeant Myers, hand me the phone. Little Acorn calling Oak. Little Acorn calling Oak. Oak, can't you hear me? Sergeant, the line's dead. I think it's been cut. Send two men out to trace the wire. Hey, what's that? Hey, look, that's Salman from G Company. Where are you going, soldier? Hey, Lieutenant. Lieutenant, they're a foreign guys. They came out of the woods. They captured all of G Company. We didn't know what to do. We had no live ammo. Lieutenant, has the US been invaded? What is this? I don't know. It's a sense we can't stay here. Sergeant Myers, round up the platoon and be ready to follow me. Where are we going, sir? Back to the trucks. We can make it to camp. We can get ammo and find out what's going on here. Sir, those soldiers, Wilson and I saw them with our own eyes. They're part of a foreign army. How'd they get here? All right, men, follow me. First platoon, first platoon. Hey, that's Jates. They're surrounded by some foreigners that captured the trucks. The trucks? Now what are we going to do? Now we have to stay here. Sergeant, pass the word. Fix bayonets. You are listening to the proudly-behaved production, The Face of the Enemy. We'll return in just a moment for the second act. High school seniors, ensure a secure, well-paying future by preparing for it now. The United States Army's Reserved for You program will guarantee you a classroom seat in an exciting army technical career course before you enlist. You'll get top-notch training and on-the-job experience while serving side-by-side with America's finest young men and women. The choice is wide open, and it's all yours to make. High school graduates can take their choice from more than 100 interesting courses, everything from atomic technician to welding. The fact-filled booklet, Reserved for You, tells you all about this program. You'll learn of many other fine army benefits too, like regular pay increases, promotions, exciting travel assignments, and unbeatable leisure time activities. Get in on the swing. Get your free copy of Reserved for You by visiting or writing your nearest United States Army recruiting station. You're listening to Proudly We Hail, and now we present the second act of The Face of the Enemy. An infantry regiment training in the south is sent out on what was supposed to be an ordinary everyday combat problem. But an unbelievable thing has happened to them. Right here, in their own United States, foreign troops have appeared out of nowhere. Prepared for a mock battle, the regiment is armed only with blank ammunition. What is happening to them must be incredible. But they know they're not dreaming. One platoon on the extreme left flank has not yet been discovered by the enemy. Bewildered, off-balance, unable to credit their senses. They wait for their lieutenant to decide on the next move. They're invaded. How did it happen? I guess everybody knows it by now. If only we could get to a radio or a telephone. Ammo, wait. There are some boxes of live ammo in the supply dump.  Yates, did you get them unloaded from the truck? Yes, sir. I brought them to where the map said. Okay, you know where they are. You and Omen and Green and who else? Captain Miller. Go get them. American soldiers. American soldiers. We are the army of the Liberation atomic attack on your east coast last night. We now control your entire Atlantic seabed. A pest. There are still scattered units of you hidden here in the woods. As the commissar for the newly proclaimed Free Eastern States of America. Okay, I always had bad dreams before, but I always woke up.  Hey, Yates, where's that ammo at? I better tell all you guys just in case. You know where that cave is near the rocks where we got off the trucks? Well, it's just behind it. Hey, hey, fellas. Who's that? Fellas, I'm an L company. That's 3rd Battalion. Yeah. The enemy, they got us surrounded. Me and my buddy broke away, but I lost him. Hey, where are you guys going? Back toward the road. Oh, that's where they are. Well, where aren't they? I don't know. I'm getting out of here. But we can get some ammo. Look, they probably got that ammo by now. Now, listen, I figure there's nobody off to the south. That's where I'm making tracks for. Now, if you're smart... Yates, we can't leave the lieutenant the rest of the guys. That's where the guys were. Yeah, even if we could get the ammo, there'd be no point in going back there. Listen, fellas, last month, my outfit had a problem with the woods here, and we discovered a little trail that takes you right back to camp. That's our only chance. We've got to hook up with the guys back there. Okay, buddy. Lead the way. Yeah, gee, I hope I remember where it is. Alt! Hey, who's that? Alt! That don't sound like our guys, Miller. It's me, Red 7. I've got prisoners. Prisoners? Yeah, buddy, prisoners.  Who are you?  You're surrounded. Hey, Corporal, pick up this batch. I'm going out after more fish.  Listen, that guy, he wasn't in 3rd Battalion.  Who are these jokers and the black uniforms coming? I'm afraid we're going to find out. Well, good afternoon. And this is a good afternoon. After almost 200 years of tyranny, your country is free again. You can remain our enemies or become our friends and join us. You have seen how quickly we have struck with what complete surprise. And there are a few things you can tell us so that we all may be better acquainted. You there. What is your name, rank and serial number? Wilson, Private. 32272642. And where is the rest of your company? How much strength is left at your camp? What sort of weapons? Sir, all I have to tell you is my name, rank and serial number. You have to tell me everything I ask you. You will see. Sergeant, conduct one of these other most excellent soldiers back to the command post and ask him a few questions on route. You mentioned the smiling instead of frowning. You have an opportunity to join the winning side. Your outfit has been completely infiltrated. A group of you are still holding your camp but not for long. Half of your officers have been captured. We know their names. We are now using the telephones and radio to give the orders we want given. Ah, poor, ill-advised fellow. Probably try to escape. What happens sometimes? Now, will you tell me what I want to know? Think very clearly and very carefully. They form the nucleus of a prison compound and every few minutes their numbers increased. Men from every outfit of the regiment will lead into captivity. And all told similar stories. How they were infiltrated, surprised by sneak attacks. How those of them who found ammunition discovered it was of the wrong caliber for their weapons. How they received contradictory orders on the radios. How they encountered enemy agents disguised as American soldiers or civilians who led them into traps. Clearly they had all encountered a daring, ruthless and powerful enemy who had too much skill, strength and savvy for them. A radio was set up at the edge of the compound and an announcer informed them that the entire Middle Atlantic seaboard was now controlled by the invader. They were shocked. They were dazed. They never knew what had hit them. By me they saw the officer who had addressed them first and walking by his side was the colonel of their own regiment. Oh, Miller, look, they got the old man, too. Stand in attention! Man, I'm sorry to see all of you here. You're sorry? I knew this was going to happen and I'm glad. Let it be a very good lesson. What kind of lesson? What's he talking about? This officer in strange uniform happens to be a very good friend of mine and of yours, too, after this afternoon. Now that you've all been thoroughly scared, let me introduce him. He's Colonel Downing of the 74th Regimental Combat Team. Colonel! American soldier! You men can relax. Smoke, if you've got him. You have just been given the full-dress treatment by my outfit, the 74th RCT. We specialize in playing the part of the aggressive force in maneuvers. We train our men to wear the uniforms you saw to speak what sounds like a foreign language, to act the parts of saboteurs and spies and theft columnists. I know we fool you.  If our army ever has to fight for real, we'll be up against an enemy that's ruthless and has no rules. Our outfit trains to simulate this enemy. For purposes of maneuvers, we train to pretend we belong to a totalitarian government. In other words, we want you to get the feel of the real thing. Well, next week, we're going to run this problem again. We hope you've learned a few things from us. Next time, who knows? We may learn a few things from you. Meanwhile, isn't it great to know that this has all been in the family? Nobody got hurt? We're all free men still living in a free country. There was an excuse for you this time. You were green and inexperienced. Next time, give us a run for our money. That's all. Pick up your equipment. Fall in the company. How do you like that? It's all a game. I knew it all the time. There's the Lieutenant with our outfit. Well, if it isn't Wilson and Miller. Hey, Lieutenant, were you in on this? Well, I'll tell you the truth. I knew it was going to happen, but the 74th made it look so good I almost believed it. Sir, I'm not ashamed to say so. I believed it. Hey, sir, would you say it was fair? Of course not. But what's fair about war? You men are lucky. As the colonel said, we do this again next week. Let's see how you make out the second time around. Next week, huh? Well, sir, as the colonel said, make me learn a few things from us. Seven days later, they tried it again. And we're happy to report the aggressor was turned back. There was no panic and no retreat. The 74th RCT taught them a lesson that needed learning. But the American soldier learns fast. With outfits like the 74th, the American army makes it seem real and earnest. But the best way to teach a man to fight is to show him the face of the enemy. Here's something that says, for women only. And here in small print, it says, for women only between the ages of 18 to 34 and single. Why, that can only mean one thing. An appeal for young ladies like you to join the women's army corps. Get full information from your local United States Army Recruiting Station today. This has been another program on Proudly We Hail, presented transcribed in cooperation with this station. Proudly We Hail is produced by the Recruiting Publicity Center for the United States Army. And this is Mark Hamilton speaking, inviting you to tune in this same station next week for another interesting story on Proudly We Hail.


Hi everyone, I'm Becky Swan Athletic Therapist for the Vancouver Police Department. You may recognize me from videos such as Pacing is Key for the Agility section. Today we're going to talk about strengthening for the agility. Set up cone or markers in a pattern on a field or in a gym. Practice going through them various ways. Focus on quickness and staying tight to the cones. At a track, make a circuit running hard for 25 meters, jumping over a six foot space, jumping over an object and doing jumps on and off a step. See how many times you can get through your circuit in two and a half minutes. Practice standing long jumps with both feet and then with one foot. This will help develop power for the mat jump. Track workout, five squat jumps, sprint 25 meters after landing your last jump, five push-ups, five sit-ups. Rest for 60 seconds, repeat two more times. Warm up and then you're doing interval runs. 30 seconds max effort, 30 seconds rest. Repeat six to eight times. Thanks for stopping into this training session. Remember you have full control over this part of the training.


Let's get over to our man, Mr. Steve Rose, as we do each and every Monday at 20 past the hour. And don't forget, folks, Steve's has an outstanding show here every trading day, 11 to 12, Eastern Standard Time. Also has a great newsletter and mastering probability. Now, come over to our website at TFNN. You're going to newsletters. You're going to see mastering probability on the right hand side. You can just hit that subscribe button. And the bottom line, folks, Steve has a huge amount of information out there. You can get mastering probability. The way it works is that you can get it for 29 days for free. That's the reality. That's how bottom line, it's a 30 day subscription. You want to keep it great, awesome. If some reason something doesn't work for you, guess what? You can get all that great information over there. You can take a look at his TD9 count. You can take a look at his oscillator and change line, the huge amount of information that you can learn just by subscribing. So come over to our website at TFNN, hit that subscribe button. Steve Rhodes, what's going on? Well, inflation for sure.  Still over five bucks a gallon here in the Boca. Is it? Yeah, so it's 509 or 510. And it's been like that. It hasn't really changed much. It's gone, maybe I saw it just under five a few weeks ago. But eggs, you know, the eggs, so I like to get it some protein. I like to get my protein if I can for eggs. So I typically will purchase organic eggs. And they're now over 11 bucks, the ones that I buy over there. So you've got huge prices over there, man, because we're at 93, we're only at 390 over here. Yeah, you know, the... And our eggs have only 883. And that's the same deal that you are talking about. It is. So you guys have more money. That's what's going on. Well, it's... You do. Yeah, they like... But hey, this inflation is pretty intense, isn't it? Oh, it is. Oh, big time. Yeah, absolutely. Hey, the grand slam breakfast at Denny's eventually is going to cost a grand. Well, hey, what do you got two eggs on there? That's too much. Hey, you know, it's so funny. He's bringing up Denny's folks, okay? And I just got an email. Jack in the box is coming into Florida. And I'm telling you, when we were in the Marines, right, between Denny's and Jack in the box, we lived there. So you should have seen me, Steve. I'm going to the Jack in the box. I'm saying, is there any money in this? Well, there's no money. Don't buy a franchise, folks. There's no money in it. The average Jack in the box is 50 to 75,000, and you're going to put up 350 grand. Yeah. But I was cracking up. I... Both of those places, they used to live in, man. Well, I would add Taco Bell to that. I was always... Taco Bell was, for me, was always good to hangover for me. I love Taco Bell. Loved it. Yeah. A little grease. A little grease to go with that hangover. Totally, man. Totally. So you mentioned that the newsletter has a lot of information. Yes. This is one of the, this is one of the, in essence, charts, graphs that subscribers get. So each morning, they get to understand what the current market outlook is for multiple time frames. So those time frames being a monthly, a weekly, a daily... Look at that thing, folks. 30 minutes, 65, 130 minutes. So it tells you, for that specific time frame, first, what the market condition is as of the time that the newsletter goes out. Yeah. It tells you where we're at. You mentioned the TD9 counts. It tells you where we're at with regard to the counts. The ones with stars next to them are identifying that there's a potential for a top or a bottom out there. We've got even part of the Chapman Wave counts. We've got different levels of support. So it provides you with all the information for... And this covers equity futures, metals, oil and gas, debt, commodities, the index ETFs, the diamonds, the Qs, and so forth, the sectors inside the S&P 500. So it really provides an individual with an opportunity to understand, to answer their own question, what is this, is the market bullish or bearish, and then specifically for the time frame. And I use these different, different intraday time periods that most people do. So if we take a look at a stock or an ETF, what we know is that what we're looking at from a trading standpoint is six and a half hours worth of data. So what I've done is I've just taken that... When I take a look at a bar for my tools, for my pattern recognition, I like to have equal time frame bars. So there's 295-minute bars that make up a 390-minute day. If we're trading for six and a half hours, it's 390 minutes. There's 330-minute bars. There's 665-minute bars. There's 1330-minute bars. There's 2615-minute bars. So I just suggest for anybody that's analyzing a chart and trying to compare apples to apples, that they make sure that the bars are used in the same types of time frames. So that's why I use these different time frames out here. The current scan that we took a look at showed a potential TD9 account, well, it actually showed a TD9 account bottom for the XLB, for the healthcare sector. So let's go investigate that. So here are the multiple time frames. And on a monthly chart, what we can see, and that's in the upper left, price was just consolidating with inside its TAS market profile. If we look at the weekly time frame chart, what we see here is this identified, this formed an actual TD9 account bottom. So we've got a bottom pattern for the weekly. The daily confirmed a TD9 account bottom pattern on Thursday of last week. The 195-minute confirmed a TD9 account bottom. So, and all these other intraday charts out here have bottoms. That's really what you want to see when a daily, so if a weekly time frame gives us a top or bottom signal right now, we'll just talk about a bottom signal. What you'd then like to see is the shorter term time frames, come back and confirm that.  So in summary, the multiple time frames are suggesting the XLB was absolutely bottoming. And that is where the use of this 15-minute time frame chart comes in. 15-minute time frame chart or 15 or 10-minute. But here we're going to take a look at a 15-minute time frame chart for the XLB. So these green lines that I have on this chart here, Tom, these are what I refer to as TD9 account breakdown resistance levels. The cool thing about the TD9 account pattern is it gives us a objective level of where price is broken out from or broken down. So if an instrument on a daily time frame is going to form a bottom, we will see resistance levels fail on those shorter term time frames. So it's nice to have that daily signal and then come back and see is resistance failing. Well, here we take a look at the XLB, we can see two resistance levels fail. Now, I don't know where it's trading right now at this moment, but the next resistance level is up at $133.01 for its 15-minute time frame. And if price starts busting through, now this is to the downside, TD9 breakout support and that's identified here with these red lines, well then that's going to tell us that there's a short-term change in trend because we're using a 15-minute time frame chart out here. But this is really helpful in trying to put the daily time frame together with intraday. I'm not asking people to trade intraday, I'm trying to show them the useful benefit of where an intraday chart can really help to confirm the outlook that you have on something that you're trading. Right, because you're getting confluence basically. Exactly, exactly, exactly. And so here, this is an afternoon report that, oh, I've got the wrong one in there. Shoot, sorry about that. Well, so in the afternoon they get a report similar to this, it shows the top 10 instruments, apparently I didn't copy that one in here, but it shows the top 10 instruments for the S&P, the Dow, the Nasdaq, the Russell, and the Summice, which are the most popular instruments that are traded there. So it gives you the same type of information that here is in this morning report. Now, this is still the XLB. So let's take a look at the Amazon because in the case of Amazon, it was also breaking through resistance level. So Amazon had established, well, I really screwed this up in my presentation, sorry, Tom. No, no, we got it, we got it, man. Yeah, yeah, yeah. But here we can see on the short-term base, again, Amazon, which had bottom patterns out there, and that was really part of the signals coming from the top 10 charts out there. We can, again, see how this has broken through short-term resistance areas. Here's a typical retirement account, a set of charts out there. So people wanting to manage their long-term funds, it tells them exactly what the current conditions are using my set of tools, whether things are bullish, they're bearish, they're consolidating. So it really helps an individual to manage their assets, which is really what it's all about. And folks, it was so cool when Steve was showing those top 10s, okay, it's really tough when, you know, you get a couple of those top 10s that have large weighting structures.  I mean, that's the bottom line. Get over to our website, folks, at TFNN. You're going to go into newsletters, you see master in probability right on the right-hand side. Steve, you have a great one, safe one, we look forward to show tomorrow. Thanks, son. You're going to have some action too, because Paul's going to be talking. Stay right there, folks. Come right back.


All right, welcome to the Q2 2020 hackathon kickoff plus May courtee meeting. So just like we did in February where you decided to combine the kickoff with the courtee meeting, obviously the world has changed slightly since the last time with their hackathon. But good to have all of you on the call to give at least me a sense of normalcy. So I definitely appreciate that. So the first half of the call, we'll just talk about the hackathon that's already off to a roaring start. I don't know if people notice. We're already up to 20 plus MRs. So that's pretty awesome. So we'll spend about 15, 20 minutes talking about a hackathon and logistics. And then we have regular courtee meeting topics that we have at the second half of the call. And for those of you that are joining for the first time, please feel free to stop me if I'm not being clear about something. Or if you want to ask a question, and please feel free to type questions on the chat as well if you don't want to verbalize. So a quick intro. I mean, David, do you want to quickly introduce yourself? And then I'll do the same and we'll get started. Cool. So yeah, I'm David. I work on the community relations team. I'm based in Europe. And the way I participate in the hackathon essentially is covering for a time. Well, Ray is not there. Feel free to ping me on any issue with my handle diplomat. Cool. And I'm Ray. I'm based in California. And like David said, I think we have a decent coverage in terms of time zone. So if you ping either one of us, particularly on Gitter, we should be able to jump in and help out. And believe it or not, I think this is the eighth edition of the hackathon. So glad to get this thing going. And I don't know how many people are joining for the first time. We're sort of sticking to a usual routine for the hackathon with some tweaks. So this is the agenda. We'll talk about logistics, schedule, prices. And I also want to spend a decent amount of time on there are a lot of good issues that people have suggested from the GitLab team members. So I want to highlight those as well. I mean, a number of people who already started working on those. So I think we have a number of good ones, particularly from like a UX in front end that are good for like a hackathon, good bite size chunk issues. So make sure you'll spend a decent amount of time talking about those. Just a quick reminder on the community code of conduct. I mean, this is obviously a virtual event. But like we do at all the events at GitLab, like to remind community members about the community code of conduct. You see the link there that you can read the full text at your leisure. But I mean, just want to iterate that just like any good open source project, we want to foster a welcoming and opening and open environment for everybody to work together. And I mean, if you see any concerns or inappropriate behaviors, I mean, feel free to use that email alias conduct at GitLab.com. The email should come to both me and David. I mean, fortunately, we haven't had any issues in past hackathons and hopefully it stays that way. But just want to give people a quick reminder on the code of conduct. Moving right along logistics, I mean, obviously, this is a two day virtual event. I mean, we want to respect you at the time zone that you're in. So I mean, a lot of the MRs that came in, I mean, so far that I already mentioned, they came from Asia Pacific time zone for obvious reasons, like even before this kickoff session. I mean, the kickoff session is just sort of there to sort of kick it off to mark the beginning of the event. We'll also have a wrap up session Thursday evening. I mean, you're at the end time. But obviously, if you're in the Pacific time zone that you are like I am, you'll have several more hours to work on it. But that's just sort of unofficial demarcation of the beginning and the events. And just like we have done in the past, in addition to people working on MRs and hacking away, we do have a couple of office hours. The package and runner teams are back. Those teams have been doing monthly office hours. And I mean, it just made sense to coincide them with the hackathon to get more people participating. So they're back. And GitLab Monitor Health, there will be a tutorial on GitLab Monitor Health. I mean, there are a number of contributors that have been contributing to that group over the past couple of months. And I've already seen a couple of MRs for the health group. So definitely looking forward to that.  She'll be talking to the community members about in case you're not familiar with the stage or the group. I mean, you should be able to get more familiar with it and where she's looking for community members to help. And if you're not able to participate in those sessions live, those are all posted on the hackathon playlist. I'm going to do my best to post them as soon as the events are over. And I mean, I've been pretty really pleased with not only the people participating in those sessions, but I mean, typically within 24 hours I'll typically see like 100 plus views on each of the recordings, which is pretty amazing. Whoops, I think I have a typo here. Let me just advance the slide. Sorry about that. I mean, that's just sort of a, I don't know, that suggested issues to work on. Bullet ended up there. But I'll talk about that in a few slides. And here are the tutorial sessions. You should have all the Zoom links. And this isn't the latest and greatest screenshots, but I think there will be links to the presentations or issues for office hours. So you'll have the latest information on the Hackathon Tutorial Sessions page. Let me pause here for a sec. David, do you think I, let me know if I miss anything here. Can I apologize for that? Yeah, go ahead. By the way, it was me doing the Ninja edit adding the same issues, bullet point in there. I just wanted to highlight it. But yeah, we can cover it later on the slides. I just wanted to make sure that people are aware of the fact that they can work on there on the issues that they're interested in. But there's a list of, there's great at least that product managers and engineering managers and also Ray essentially put together for that might be interesting for people to get started on. Cool. OK, thank you, David. Yeah, I mentioned Gitter earlier. So I mean, we're well over like a 500 people that are in the community in the contributor room. This is usually the best place to get help. I mean, not just during hackathon, but during regular times as well. I mean, there are not just me and David, but there are a lot of community members there. I mean, they can help answer questions on, like if you get stuck with something on GDK, for example. I mean, this is usually the best place to get help. So I mean, feel free to use it. And then I mean, during the hackathon, feel free to ping me or David that we can jump in and try to try to help you out during the event. Oops, hit the wrong button. OK, and just want to talk about the MRs and prizes. So when you submit an MR, a number of people have already done it. They've sort of used the routine. In the comment box, it just mentioned me or David. I mean, just mentioned that this is for the hackathon and we'll continue to track those on this issue. Let me just click there and show you the page. So yeah, your MRs will be sort of added to the list. And this is where we get to count of, as of at least 30 minutes ago, I counted like a 21 MRs and three of them already merged. Takuya, I think I was able to merge a couple of your quick documentation fixes. So thank you for that. So this is where we'll create a list of MRs to track. And then even in the issues directly, like a lot of people have done, just feel free to just ping me here as well. And then just bring it to our attention and we'll be happy to add them to the list. Let's see. And then on the main hackathon page, we have an MR counter. So you'll see it here. So you'll see the running tally of how many MRs have been submitted so far or during the hackathon. So and the prices. So this is pretty similar to what we've done in the past. I mean, we have a grand prize for most number of MRs merged and we also have a prize for a second place winner. And as I noted, I mean, in terms of like doing the work during the two-day event, I mean, we want to make sure that you're able to work during your normal whenever you normally contribute to GitLab. So it's just work during your normal time zone. The only time we'll have is like a deadline, enforce the same deadline for everyone is a deadline for MRs to be merged. And that's 2,300 UTC on May 26. It should be a Tuesday because Monday is a holiday in the US. I just want to get people on this additional day for MRs to be merged. But if you have any issues, like for whatever reason, you feel like there's a delay in MRs getting merged. I mean, feel free to reach out to me and I'll make sure that we'll find a way to expedite the review or count them as a MR that's been merged. And then I'll open a separate issue to notify the winners. And if you go to this link under the hackathon project, you'll probably be able to find issues from the past hackathons where we announce winners. So that's a quick logistics on prizes and MRs. So here's a quick screenshot of the prizes for the Merge MR and the second place prize. And the grand prize is like we've done in the past. This has been pretty popular, like $100 to spend at the store. So, and actually, Samantha's who's on the phone or who's online, she's going to help us with that. So thank you, Samantha. Appreciate that. Cool. Yeah, so hopefully you'll like the cross body bag. I was looking for something that when things sort of get back to normal, people can use either during commute or when you're traveling. But hopefully those days will come pretty soon. And also a charger, a wireless charger for your mobile. I mean, most likely your phone. But it's covered in fabric, which I thought looked pretty nice. So hopefully people will enjoy that. OK, just some quick stats. And obviously, we've been having like a phenomenal growth in terms of like MR submitted. And what you'll notice from Q2 of last year, actually about a year ago, we had a disappointing drop. And I think one of the issue was I actually, I think if I remember correctly, the Keith Hackathon last year was scheduled during the last week of May. And it turned out that, I mean, not just in the US, but several countries had a holiday that week. So I don't think a lot of people were very active. So it'd be interesting to see what happens this year. That's why I consciously decided to sort of pull it closer to the middle of the month versus like doing it in latter part of May. And a lot of people ask about, you know, in terms of grand prize, like how many Merge MRs were involved, so I just went to sort of share that data. I mean, we had a really high number in Q4, 28. But so you'll see the record there between like 7 and 28. So it would have been the number for the grand prize. All right, so yeah. And this is something that David brought up earlier. So if you go back to the issue where we track the MRs, if you look at the top of the page, this is where we have sort of recommended or a short list of issues that we think would be good for hackathon. And there's a query that you can easily do for issues that are good for first time contributors. That's one of them. And the second one on Gitter, I mean, this is something that I added. I talked to Eric on the Gitter team. And if you use an iPhone, like you'll notice that if you try to log on to Gitter, you can't use your GitLab ID. But you can on Android. So for selfish reason, because I have an iOS device, one thinker is community members to work on that. And then here's an MR that actually a community member did for Android last year. So hopefully you can use it as a reference. And that's one of the issues that we have for Gitter. And then here's an issue just like a cleaning up like old feature flags. And then if I go to this issue, I mean, one of the contributors from Indonesia already started working on this earlier today. But here are relatively quick and simple ones that you can help out with. This is also labeled like a good for first time contributors. So I marked off the ones that Gilang is already taking care of with his MRs. But here's a good one. And if you're interested in the front end, I mean, here's an Epic that's got a lot of issues listed here.  I think last quarter we had about 50 MRs that were merged with a couple of Epics that the front end team created. So there are tons of issues here that you can tackle. I think our ruins probably started working on this even for some of these, even before the hackathon. But this is probably a good one for you to look at if you're interested in front end. And then we also have about a dozen or so UX related issues that UX team added here just a couple of days ago. So here are the ones that you can probably tackle. I don't believe anyone's started working on these yet. So these should be all available. So I encourage you to take a look at these. And then as David mentioned, I mean, if there's something that you want to fix, but I mean, you can't necessarily find an issue that's completely fine. It's not like having an issue is not a requirement. But if you're looking for guidance on things that are good for hackathons, it should be a decent list of things that hopefully will be good for a lot of new contributors and good buy size issues that people can tackle during the hackathon. Natalia, actually, do you have any thoughts on this epic for view event hub submit? Or I think it's like pretty. Actually, I've created a better epic for this. This is a part of the bigger epic. You can see an ancestor-refector-deprecated part. And then we can take another epic from there if we don't have enough for the front end, because we also want to get rid of slots in the view also lot syntax. So if you look for more front end epics, there is one more epic here. Yeah, a migrate view slot attribute. But I believe this should be tackled. And we need to add issues there, because there is only a list of components. OK, cool. All right. Yeah, it looks like Scott opened this couple of weeks ago. Cool. I think it would be cool to add some back end related issues to the list, because I've seen only front end. Yeah. Right. Yeah, I think, I mean, actually, Natalia and I talked about this probably a little over a week ago, because I think I reached out to the back end team, or at least on the back end Slack channel, and see if there is something similar we can do on the back end side of things. And I haven't necessarily heard back. But I think the part of the challenge is there's a lot more dependencies on back end related work. But yeah, I can certainly reach out to the Slack channel again and see if we can come up with something. But that's a good point. So OK. I think that's all I wanted to say about the issue. David, was there anything else that you wanted to mention here? Or I think there's also one for internationalization that's always been there for a while. Yeah, I wonder if we should. I mean, we had in the past a big list of internationalization issues on an epic. So that reminds me whether we should have a look at that. In any case, no, I don't have anything else to add to that. I'd be, given the progression that we've had with participation and a number of issues, a number of MRs submitted, it'd be awesome to aim for 200 MRs submitted on this edition. I think it would be great to showcase the work that our community is doing. Yep. Cool. OK. Sorry, though. Just a small note, if you've mentioned it already, apologies. But in the past, I've had a tendency to accidentally start work on an MR for an issue that maybe already has someone working on it. So that's something maybe for people to look out for and just triple check that not only, you know, it might say that it's accepting merge requests, it might not have a sign-e, but just double check whether anyone's made a note to say they're picking it up or if there's an MR in progress, and maybe just to add a note yourself if you are going to be picking it up. Yeah. Yeah, that's a good point. I mean, unfortunately, that does happen. I mean, it doesn't happen that often, but it does happen once in a while. I mean, if you're not sure if the issue is still, I mean, something that you need to work on and feel free to ping me or like other GitLab team members that are on the issue. And yeah, I mean, I think double checking is not a bad idea. I mean, what I typically try to do is when somebody expresses an interest, I would assign it to them. But yeah, a lot of times like issue sometimes doesn't get assigned right away to folks. But yeah, that's a good tip. Okay. Moving right along, in terms of getting help, I think I got like a one or two slides left here. I already mentioned Gitter. I mean, that's probably the best place to start in terms of getting help, but there are other resources as well like GitLab. There's a merger request coach that you can mention on MRs with this, you know, with this mention. Whoops, sorry, I hit the wrong key. And then you can also like a ping reviewers and maintainers. If you go look at this page, you'll see a table of like all the maintainers listed. And I mean, I say these over and over again, every time I talk to contributors or community members, it's a completely fair game to mention anybody at GitLab.  I mean, I'm a GitLab employee, but before that I'm a community member. So we owe it to everybody to get back to people. So don't be shy about like I mentioned people in issues or MRs. But I mean, during the hackathon, I mean, feel free to mention me or David, that's probably gonna be sufficient. But in general, you can always like reach out to merger request coaches as well. And they should be able to help out and answer your questions. I mean, we do have like, I think the numbers up to 10 coaches right now. So we have a decent coverage in terms of number of people available like the front end, back end and other areas as well. So I think that's it. Wanna make sure, let me see if people have any questions on chat, don't see anything. But if there are any questions on the hackathon, just let me know. Pause for about 10 seconds for any remaining questions or court team members, if you have any feedback or comments that you wanna provide for hackathon participants, let me feel free to chime in as well. So if not, we'll just transition to the court team meeting. And as usual, I probably need some help with the note taking here. So let me post it on the chat window. So Google doc with court team members, if you can help out with note taking, I appreciate it. Yeah, all right. So in case people are just joining the court team meeting for the first time, I just wanna give a quick introduction of what a court team is. I think I did the same thing last quarter, but I'll spend a minute or so talking about or explaining what a court team is and the rest of the agenda topic that as I listed on the issue, excited about the two court team members. A couple of people already chimed in, so wanna welcome them to the court team. And I wanna talk about GitLab Commit, that's a virtual event that's coming up in, I believe that's the last week of August. So I wanna encourage people to participate on GitLab Commit, particularly with the CFP that's open till June 1st, I believe.  And one of the things that we want to talk about was improving GDK documentation. I opened an epic for that topic. So I wanna spend some time talking about that and any other topic that people wanna discuss we'll make sure we cover those as well. So moving right along, just a quick intro on the court team. I mean, the first link is a link to the court team page. I mean, basically we're up to about 10 people now, I think with the two new additions. I mean, basically the main charter or the court team is to be the representative of the rest of the code contributor community. I mean, these are a group of people, I mean, that have made sustained contribution to GitLab for a number of years. And so, I mean, they bring a lot of experience and not just in terms of like contributions and not just in terms of like using our product, but you know, representative community, I appreciate the feedback that you've been able to provide over the past couple of years that I've been at GitLab. So, I mean, think of the court team members as representatives of the community. And the monthly meetings that we typically hold it on like a second Wednesday of each month and the meetings open to everybody. And then the agenda topics and all that is discussed in the public issue. So, if you click on the like a court team group link there, you'll see the meeting agenda and discussions from the past. And then we're one of the few groups, I guess, like GitLab that use a wiki. So, I post all the materials and notes on the wiki page for people that I think it makes it easier for people from other communities to consume. And then we also have a playlist of all the meeting that gets recorded. I mean, this has been pretty fascinating. I'm like, with very little marketing I'm amazed at the number of people that typically view the recording within a couple of weeks. So, I know this is, people are listening and watching the recordings. And so that's all available publicly. I mean, anybody can join the discussions anytime. But yeah, so this is, just wanted to give you a quick introduction on the court team. David, anything you want to add here on the court team? I may have like bumble along in a couple of places, but. No, I think, anything else that I can think of right now? All right, so as I mentioned, we have two new members. I mean, I couldn't, I think it's been, at least been more than a year. Last time we added new people to the court team. So, I mean, the other thing I didn't mention about the court team in the previous slide was that we have up to two people that are actually GitLab team members, but rest are from the wider community. So, I'm definitely excited to welcome Lee from the wider community and Natalia from the GitLab team. And I'm gonna, I don't wanna put you on the spot, but Lee and Natalia, if you wanna give a quick introduction, because I don't think you met other people on the court team or other people on the call. So, Lee, I'll, sorry to put you on the spot first, but if you wanna just tell us about yourself or you're located and how long you've been contributing to GitLab, that would be great. Yeah, absolutely. So, I think I'm based in the UK and started using GitLab a couple of years ago. I've run a small software development company and yeah, essentially probably six months after that. So, 18 months ago, I wanted some additional functionality and found out that, you know, through the open source project, I can actually contribute that functionality. And then got rather hooked, I guess. Cool, thanks for sticking with it. And I think, I mean, I think George and David, you may have had a chance to meet with Lee in London. I don't know if you did have a chance or not, but I mean, Lee, it was definitely nice to meet you at GitLab in London. Yeah, it was a great event. And looking forward to normality when we might get the opportunity to meet another. Yeah, well said. All right, well, Natalia, do you wanna do the next introduction yourself really quick? Sure, so I'm Natalia. I'm a senior fountain engineer in the process of promotion. So hopefully soon to be stuff. And I'm working for GitLab since November, 2018. And I actually met some 40 members at GitLab contribute last year. Hi, George. And also outside of GitLab, I'm a view core member. So it's one of the major JavaScript frameworks. So like two core members, I feel like a dual core right now. And thanks. There you go. Welcome. One company in Natalia. I like the dual core. Like some of the processor companies may try to hire you. All right, cool. So yeah, speaking of GitLab commit, and yeah, I mean, unfortunately this, I mean, a lot of the events, pretty much for the rest of the year, it sounds like not just like GitLab, but rest of the industry is probably moving online or virtual. So the GitLab commit, the only one we have on schedule is on August 26th.  And then I have a link to the event page. And I mean, definitely wanna like encourage everybody, not just to participate in the event, but we also have a CFP that's open until June 1st. So got like a two to three weeks for people to come, like I think about like a sessions, I believe there are four tracks. If you go take a look, why don't I just go there really quick and make sure that I'm not just making this up. Yeah, I think there's DevOps, key studies. And so you'll see the details here in terms of event. So I definitely encourage people to think about like a submitting a CFP if you have an interesting topic that you wanna talk about. And I mean, George, you've done this a couple of commits last year. I mean, if you need help with the CFP or even putting the presentation together, I mean, feel free to reach out to me and David. I'll be happy to introduce you to folks in the marketing team. So I definitely encourage you, wanna encourage you to do that. And also, I mean, some of the things that I, I mean, what I've done in some of the events and the commits in the past is I think I've done like a two different panel type discussions. So if you have an idea for that and if you need me to help or participate in that, I mean, just please let me know as well. So I think like if you've been on Twitter, I think the announcement started going out in the past week or so. But let me know if you have any questions, but definitely wanna encourage people to participate or even think about giving a talk. I have just a link there on the presentation. There's also a virtual meetup. I think Emily Chin are organizing to provide some guidance on how to get selected to speak at heatlock commit. So essentially there will be some discussions and guidance around writing a good call for papers, CFP and then having good topics as well to, if someone is interested to submit a talk and then definitely suggest to check out that either the session live or to order recording afterwards.  Like it could be taxing at times. So hopefully, I don't know if we have information on the time zone for the event, but unless the time zone is on or us, I think they might make event participation easier because you can just do it from your desk at home. All right, well, thanks for that. I might join that meetup myself. Cool, so moving on to the next topic. I mentioned the GDK office hours. We also have a playlist for GDK. So, I mean, I unfortunately forgot to record the first office hour that we did two months ago, but the one we had like last week that Lee participated in, that recording should be available there. So we talked about a number of things. I mean, not just about documentation, but also about ways to improve GDK in general. I mean, we actually have a team of people that are actually dedicated to GDK. It used to be more of a volunteer effort within GitLab, but with Lucas and Ash that are actually working on improving the GDK itself.   So there are a number of activities that Ash and people are working on. So that's pretty exciting. And one of the things that I felt like an area for improvement was actually improving the documentation. And I'll go to that link for that EPIC, which I opened last week. And then Patrick and others like added a lot of different issues as part of the EPIC to improve the GDK documentation. I mean, one of the things that I think that's relatively easy to fix and I'm probably gonna start working with the docs team on is we don't have a dedicated page for GDK on docs.gitlab.com, which I think is unfortunate because I think a lot of times people can get sort of directed to the GDK read me page, which I don't think is ideal. So that's one of the things that I wanted to talk to docs team about updating and there are a number of things. I think Patrick actually went through the exercise of installing GDK on a couple of different operating systems and there are some corrections that he wanted to make on several sections of the doc. And I think Ash also talked about right now the setting up of GDK is separate from like the prerequisites in terms of documentation. And that seems kind of unnatural. So there are a number of issues here that you can probably take a look at for improving documentation. But obviously we welcome your ideas and feedback because you probably are a lot more experienced than actually using GDK than I am. But Lee, anything else that you wanna add here that I probably missed like a lot of details that we talked about last week with Ash? I think the survey is interesting to kind of collate some information around how everyone's developing, what operating systems, what tools they're using and kind of work out where some of the focus is. And certainly from my point of view, I believe I'm in the minority being a Windows developer. So kind of understanding the best way to get up and running and streamlining that kind of process. Yeah, I think like one of the things I talked to, I mean separately because Patrick couldn't join the office arrow last week was like, I mean, even like some of the operating systems that are listed there, we're not quite sure how well all of those are supported in terms of like GDK actually functioning well, but that's obviously worth investigating. So any thoughts from like other core team members on GDK documentation in particular? Yeah, hopefully we'll tackle some of these, at least some of the issues that are captured in the Epic in like this quarter, next couple of months. And I'll keep people up to date, but definitely welcome any feedback or ideas that you can add on the Epic or any of the issues that are listed there. Yeah, so I think that's about it in terms of the two or three major agenda topics. There are other topics that people want to discuss. Let me make sure that. Oh, one thing, God, sorry. Sorry, a little off topic, but this morning when I woke up, I had a quick look on my mobile phone at the HackFond page. I suspect this isn't specifically the HackFond page. I imagine it's the whole of gitlab.com, but it isn't very mobile friendly. I think the table was the specific part where it said about the prizes. I could only see the left hand two and a half columns. There was no scroll bar. So again, maybe that's an easy for a UI person, little MR to maybe pick up for the HackFond. OK, that's a good feedback. I mean, I have to admit, I don't think I checked the HackFond page on my phone, but something I probably need to do. Yeah, it seems that the table is responsive, but then at some point it stops me. Responsive, but yeah, I think that's a really good point. So contributions are welcome, not just on issuesforgitlab.com, also on the website and particularly on the HackFond. It's a page that gets more visibility during the event. I mean, I personally, one of the things that I would like to see in there would be more visibility on the list of suggested issues, so rather than them being a link that could be buried within the page to have the actual list on the front page itself so that people can just visually see the list of issues. But yeah, I'd say any contributions would be really more than welcome. Thanks for the feedback. OK, any other topics, anything else? Perhaps one last thing. If people are interested in knowing what's going on at the HackFond, or then refreshing the page to see the list of MRs submitted, then they could also subscribe to the HackFond label as well. OK, any other topics or feedback? All right, I guess we'll wrap things up. Happy hacking. I'll talk to you guys again soon. Thanks, guys. Thanks, everybody. Have a good day. Cheers.


Hello, and welcome to the session on TCP flow control. At the end of this session, students will be able to uniquely identify the phases in TCP flow control. Windows in TCP, TCP uses two windows, same window and receive window, for each direction of data transfer, which means four windows for a bi-directional communication. However, to make this session simple, we assume that the communication is only unidirectional, that is from client to the server. Same window and receive window. Now, the figure shows an example of a same window. The window shown in this figure is of size 100 bytes. Normally, it is thousands of bytes. The figure shows how a same window opens, closes and shrinks. The same window in TCP is similar to one used with the selective repeat protocol, but with some differences. The first difference is that nature of entities related to the window. The window in TCP numbers of bytes, actual transmission in TCP occurs segment by segment. The variables that controls the window are expressed in bytes. The second difference is that TCP can store data, receive from the processes and send them later. Here, we assume that the sending TCP is capable of sending segments of data as soon as it receives them from its process. Another difference is the number of timers. The selective repeat protocol may use several timers for each packet sent, but the TCP protocol uses only one timer. Now the receive window. Figure shows an example of receive window. The window shows here is of size 100 bytes, normally thousands of bytes. The figure also shows how the receive window opens and closes, but in practice the window should never shrinks. There are two differences here. The first difference is that TCP allows the receiving process to pull data at its own pace. This means that the part of allocated buffer at the receiver may be occupied by the bytes that have been received and acknowledged, but are waiting to be pulled by receiving process. The receive window size is then always smaller or equal to the buffer size as in shown figure. The receiver window size determines the number of bytes that receive window can accept from the sender before being overwhelmed. The second difference is the way of acknowledgments used in the TCP protocol. Now the flow control. Flow control balances the rate of producer creates the data with the rate a consumer can use data. TCP separates flow control from error control. Figure shows unidirectional data transfer between sender and receiver. Figure shows the data travel from sending process down to the sending TCP from the sending TCP to the receiving TCP from the receiving TCP up to the receiving process that is path 1, 2 and 3 as shown in figure. Flow control feedbacks are travelling from the receiving TCP to the sending TCP and from the sending TCP up to the sending processes that is path 4 and 5. Most of the implementation of TCP do not provide flow control feedback from the receiving process to the receiving TCP. Flow control feedback from the sending TCP to the sending process that is path 5 is achieved through simple rejection of data sending TCP when it windows is full. This means that the flow control concentrates on the feedback sent from the receiving TCP to the sending TCP that is path 4. Open and closing window to achieve flow control TCP forces the sender and the receiver to adjust their window size. Although the size of the buffer of the both parties is fixed when the connection is established the receive window closes. Closes means moves its left wall to right and when more bytes arrive from the sender it opens means moves the window right wall to the right. When more bytes are pulled by the process. The opening closing and shrinking of the send window is controlled by the receiver. The send window closes when a new acknowledgement allows it to do so. The send window opens when it receives window size advertised by the receiver allows it to do so. A scenario figure shows a simple example of unidirectional data transfer from client to the server. Assume that no segment is corrupt lost or duplicate or arrive out of order. Eight segments are exchanged between the client and server. The first segment is from the client to the server that is sy segment to request connection. The client announces its initial sequence number 100 when this segment arrives at the server it allocates a buffer size of 800 and sets its window to cover the whole buffer that is the receiver window size equal to 800. The second segment is from server to the client this is an ack plus sy segment. The segment uses ack number is equal to 101 to show that it expects to receive bytes starting from 101. The third segment is ack segment from the client to the server after the client has set the window with size 800 the process pushes 200 bytes of data the TCP numbers these bytes 101 to 300 it then creates a segment and send it to the server. The segment shows the starting of number as 101 and the segment carries 200 bytes. When the segment is received at the server the bytes are stored and the receive window closes to show that the next byte expected is byte 301. The fifth segment is feedback from the server to the client the server acknowledgments bytes up to and including 300 expecting to receive byte 301. The segment also carries the size of the receive window after decrease it to the 600. The client after receiving this segment and acknowledged bytes from the its window and closes it window to show that the next byte to send is 301. The segment 6 is sent the client after its process pushes 300 more bytes. The segment defines sequence number as 301 and contains 300 bytes. When this segment arrives at the server the server stores them but it has reduced its window size after its process has pulled 100 bytes of data the window closes from left for the amount of 300 bytes but opens from the right for the amount of 100 bytes. The result is that the size is only reduced 200 bytes the receiver window size is now 400 bytes. In segment 7 the server acknowledges the receipt of data and announces that the window size is 400. When this segment arrives at the client the client has no choice but to reduce its window again and set window size to the value of receiver window 400 advertised by the server. Segment 8 is also from the server after its process has pulled another 200 bytes. Its window size increases the new receiver window is now 600. The segment informs the client that the server still expected byte 601 and the server window size has expanded to 600. Here the sending of this segment depends on the policy imposed by the implementation. Shrinking window the receipt window cannot shrink but the same window can shrink if the receiver defines a value for receiver window that results in shrinking the window. Some implementation do not allow the shrinking of the same window. The limitation does not allow the right wall of the same window to move to the left. New acknowledgement plus new receiver window is greater than or equal to last acknowledgement number plus last receiver window. The left side of the inequality represents the new position of the right wall with respect to the sequence number space. The right side shows the old position of the right wall. The relationship shows that the right wall should not move to the left. Now the example. The part A of the figure shows the value of last acknowledgement and receiver window. Part B shows the situation in which the center has sent bytes 206 to 214. The byte 206 to 209 are acknowledged. The new advertisement defines the new value of the receiver window as 4. When the same window shrinks it creates a problem. The receiver forces to maintain the right hand wall of the window to be shown in a part A because the receiver does not know which of the bytes 210 to 217 has already been sent. One way to prevent this situation is to let the receiver postpone its feedback until enough buffer locations are available in it. Here pause the video and attempt the MCQ. The answer is B. Now attempt the second MCQ. Here the answer is B. Here are my references.