Enugu State's Governor-elect Vita Mba has again reoccurred his hand of fellowship to other contestants in the election in the state. Receiving a certificate of return alongside his deputy Ifai Osai, he had elected lawmakers from INEC by reiterating that the certificate is a legal document which contains an unwritten pact between his administration and the people of Enugu State. Today's handing over of the certificate of return to us should end all such atrocious politics. It is time to move on. History will never forgive us if at a time like this, when we should be pursuing the interests and development of our dear states in Enugu. We are still immersed in the pursuit of political gains and cleavages. It is why I extend my hands of fellowship to all my brothers with whom I run the race for the hearts of Enugu electorates. Politics has ended. The Enugus have shown their preference. Let us end the politics of our cremation and focus on how to move Enugu state forward. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Today I'm going to be explaining a backroom's level called Red Rock Canyon and this level has just been found by two people and there is so many strange, dangerous, and just insane things that I really don't even know where to start. I'm just going to get into the explanation. Also go so to my second channel, Broogly2. I upload every day. Thank you. So just like I said, this level was found by two people. Their names are Jericho and Marty, or as I'm going to call them in the video, J and M. All the information, all the pictures, all the names and places on these maps in this video come from J and M, who are apparently the only two people that have found this specific backroom's level. The level has been nicknamed Red Rock Canyon and it's been classified as a Class 5 difficulty and it's thought to be sentient because J and M believe that the entire level is alive. Like it's literally controlled by itself, even though it looks like it's just out in nature. The level isn't fully dangerous in every spot, but it is very dangerous in some localized spots and I'll get into all that right now. But first I have a letter from Jericho that describes the basic danger and the basic vibe that he got the second they got sent to the level, so I'm going to read that to you right now. To whom this may concern, I'm writing this letter with an urgency that cannot be understated. I, along with my cohort, Marty, have been in this abhorrent place for what we've determined to be over a year now and we've been unlucky enough to stumble across and undiscovered to our knowledge world. I have no idea how this place came to be or why it's here, but we'll attempt to explore, document and report back with all possible information that can be provided about this location. We've been at location for just under three hours and we don't have much to report at this exact time. Our arrival left us at the mouth of a very deep, red, rocky canyon. It seems to be night time, although a red glow permeates from the rocks of the canyon. As I stated earlier, we'll have more information soon and, God willing, a rudimentary map of the locations we'll explore. Hope this reaches someone that knows what they're doing. Best JNM. So yeah, attached with that letter were all these pictures and stuff that we're getting now, as well as some other notes and that kind of deal. We still don't know much about this level, but we're just going to get into all we do know. As of right now, the level has three distinct zones. There's 100% more zones, but these are just the ones that have been documented and mapped out by JNM. The first part of the level has been nicknamed the mouth. And the mouth is this very beginning part where there's this lake. And here at this lake, there's lukewarm water that kind of leads into the opening to the canyon. The water itself has a weird type of fish in it. The fish is transparent and you can see its organs through its skin, which is pretty strange. The fish glow red at night time and you can hardly see them in the daytime, which is a specific distinction that JNM made in another letter. Now this river that leads from this little lake area has been nicknamed the drink and it leads into the mouth of the canyon, but it stops about a mile into the canyon. The river is very shallow and it's just about knee deep and it cuts through very tall canyon walls. And the canyon walls here at the mouth are very huge and they're very tall and cast steep shadows, but you could climb up to the top of them with pretty minimal effort. And if you do climb up them, you'll be able to look down into the canyon and see things much easier, but you can't really get anywhere because it's just flat up there. Walking into the canyon floor itself isn't dangerous at first. Just seems like a normal empty canyon with a little bit of water, but about a mile into the canyon that water starts to trickle out and disappear and it'll turn into just a rock floor. And this is where the whole level starts to make less and less sense and it gets very dangerous, trust me. So at this one mile mark, the canyon splits off into two paths, one on the left and one on the right. If you go to the right, you'll start to notice really weird rock formations on the walls. It looks like sharp, jagged, pointy rocks that are kind of angled towards the middle of the path and the path itself gets skinnier as you go up in this way, which makes it pretty hard to walk through. And this section of the level has been named the teeth because the rocks kind of look like teeth, but this specific part is very dangerous because at random times, the wall of the canyon in this teeth zone will close in and touch each other and then open back up like normal. JNM described it as kind of like a Venus flytrap closing in on a bug, how it just slowly closes in and then opens back up. The first time it happened, Jericho barely made it out of the walls before they closed in on him. We obviously have no idea why this happens, but it might be how the canyon eats food. They did say that they thought the canyon was alive, so who knows. We have no idea what's passed the teeth since they had to run back before they literally got eaten, so the map on that trail ends, but now we're going to go to the left trail, which is past the mouth, past the drink, and then to the left of the teeth, and this is the third and final discovered location so far. And this area opens up into an even flatter and wider canyon type zone. There are canyons, crags, crevices, literally just every steep, cavey, holy thing. And this zone has been nicknamed the spine because of all the sharp mountain ridges and rocks that run through it. It can be extremely dangerous if you aren't watching where you're stepping because you can fall into a cave or a hole or down into a sharp spike below you. And at the end of this area is as far as J&M have explored because when they got here, they noticed two very weird things. The first thing was a massive snake-like creature that was crawling slowly under their feet through the cracks and crevices and the holes in the canyon below them. At first they didn't even notice this snake because it was moving so slowly, but they assume it has anywhere from two to four mouths along its body because they saw different ones on its entire body. And it's the exact color and texture of every other rock and thing here. And the only reason they even saw it was because its tail was sticking out of the side of the cliff. Maybe the teeth section from earlier is a part of this snake? Maybe the canyon walls don't close? Maybe it's one of the snake's body's mouths? Who knows? Let me know in the comments what you think about that. The second thing they noticed is buildings of some kind, like man-made structures on this random level. And these buildings kind of look like ones you'd see around a mining area from real life. They're medium-sized and made out of metal. And around the buildings there are telephone wires and railways and weird storage tank things in the ground. And the pictures that you're seeing right now are the only ones they felt comfortable taking because to get to the places where the buildings and the wires are you'd have to climb over the spine and up the cliff a little bit to get to the houses and the storage containers on the canyon wall above. As of right now we have no idea if they're mining stuff or what these structures are for or what's being stored in these giant vats. We have literally no clue.  But when more information is available I'll be sure to let you know. So this map here is just the basic outline of the explored parts of the level so far. As you can see it starts with a mouth that leads up to the drink until the canyon splits off into two zones. The teeth and then the spine. And where the map ends is as far as J and M were able to map and document because they didn't want to get eaten or fall and land on a spiky rock. So if we get more information about this canyon I'll make sure to let you all know. It'll definitely be a part two. Alright everybody thank you so much for watching. That was Backroom's level Red Rock Canyon. This was an entire level in lore that I made up myself. Hope you enjoyed it. This was probably one of my best levels. If not my best level. I really had fun making this and making all the images and making all the notes and stuff. It was a great time. Kind of like an ARG in a way. If you want to part two let me know. Comment Red Canyon Brugley if you're watching this far. That way I know you're a real one. Thank you all for everything. Love and appreciate you. I'll see you later.


Senator Tina Smith's staff was in Bemidji this afternoon to meet with local parents and activists to discuss the child care shortage. The meeting was a part of the senator's statewide child care access and affordability tour. Community members brought up various issues to Senator Smith's staff including challenges in finding workers, low pay and keeping child care providers in the area. According to her staff, Senator Smith has been working in Washington D.C. to bring all these problems to the forefront. With her position on the health education, labor and pensions, the help committee, Senator Smith is uniquely positioned to work in D.C. on issues focused on access to child care. She has signed on to bills that will help families afford child care and help child care providers get more in terms of funds from families. Senator Tina Smith's staff plans to host more meetings on child care in the region in the future.


Mentors are senior leaders who provide you with a safe space to share some of your thinking to get bounce off your ideas such that you are not too conscious about whether your thinking is right, wrong, whether you can express the full breadth of it so they could give you perspectives. So mentoring is very, very important, very useful, very powerful to be surrounded by mentors. In a mentoring journey, I would say it is also very much up to the mentee like myself to be very open with the mentors what areas you want to work with. So the ball is in the court of the mentee to drive that learning and what areas you want to focus on for the mentors to help you. The difference between sponsor and a mentor is a sponsor is someone who will be there speaking for you, rooting for you, for opportunities that will be great for your department. So sponsors are very important as well as you go further into career. Many of the top positions are done through discussions. So how are you being represented? How are you being heard without being in the room? That is really where your sponsors come in.


I think, I think Future's brain is getting better because I think the more people start to learn about like how long he's really been around, you know, because it's surprising but I saw this thread. The one he wrote was like Blueberry Yum Yum by Blueberry, that was one I learned about. That's like 2004. So to be from 2004 to 2011, seven years of career, that's already impressive. And then to go from that 2011 to today, which is another 13 years, that's also impressive.  You know what I'm saying? Like when you think about it. This industry especially. Yeah. But remember, he came up with a dungeon family. Yeah. And that's what brings us to the next topic because that man Pluto, he dropped 250 bands to break his music. Last year I was getting 3,500 shows at this time and this year I'm getting 20 because I always wanted to see myself go up to here nigga.  If you really on your grind, man, it can happen. The only thing you got to do is believe. So when I'm throwing numbers, I'm throwing numbers for the dude who ain't getting the 20th show, who trying to get it to let them know it didn't take me a number to get. But the only thing it did take a lot of hard work. It took 24 hours being in the studio. It took my girl being mad at me. It took me not being around my kids like I want to be. It took me doing interview after interview. It took me doing phone calls. It took me doing drops for different DJs. It took me to go to the club, throwing goddamn over a quarter million just blowing it every time I go in the club, making that impression, making sure everybody on the music and doing it for a cause. You got a hot song. You get whatever for it. You know what I'm saying? Really, I want to spend my money, my own money out of my pocket every time I go into the club. It took a lot to get that 20. It's just then calm just for me just rapping in the studio then the next day I performed and they told me they was going to give me 20.  I'm selling this audience is rich lifestyle before I got in it worked. But to be fair, he's spending it wisely for what his brand is. Right? Yeah. Some of these artists being broken, not having the money. Well, what are they spending it on? Him, his was specific path. He was spending it to make more money. His goal was to go from 3,500 a show to 20K. He did that in a year, doing exactly what he just did. So yes, his audience, we know that a part of the perception is throwing money in the club. Right? But that's marketing. Right? So he was spending money on marketing while in some of these cases, you're just talking about straight up maintaining a lifestyle and perception, which is, it's such a fine line. Right? Such a fine line in Fantasia's demographic, I don't think would benefit from that perception like futures would. Right? So that's a whole another thing. There's a lot of artists who are caught in that loop who don't get a direct impact and level of growth from appearing to be rich futures, you know, and then type of music you got like, come on, that's what it is. And that's the environment that he wants his music to play in. You know, you're throwing it in a strip club. I wanted to play in a strip club, so I'm setting the tone so I can experience. So it's a little bit different, but I think bigger than that is just his mentality. He's talking about even the sacrifices that he made. You know, I know a lot of people like to be like a future guy, a lot of kids and I like to kind of give him like a fuckboy brand. But he said this right here is early on. I don't want to miss my kids. I mean, I'm not not be with my kids, but I got to work. He talked about it as a sacrifice, which I think I feel like me and kind of like get a word am I looking for? Like this for that a lot, like the entrepreneurial man is like, no, just because I made the decision to do it. It don't mean that I don't miss the thing that I'm not doing. I might I really want to be at that birthday. This hurts me too.  Yeah. So for those people who are inspired by that and need to, you know, get that understanding that you are going to have to miss some of those things and you want to have some of those discussions, which actually leave a lot back to what we were talking about before we started.  It's a real thing. There's moments that you miss, right? So like the way future moves, like people said, couldn't have been Pluto. I think it's very clear. This is why we questioned. I think that was last part why we were like, future wouldn't turn down a million dollars. He's very much so about his money. And very strategic, although people wouldn't give future smart. A lot of people wouldn't think smart just because of his brand. Yeah.   Yeah, that's true. I think I think futures brand is getting better because I think the more people start to learn about how long he's really been around. Yeah. You know, because it's surprising. But I saw this thread on Instagram the other day. There was like just songs that were written by artists and you didn't know it. And like it was going through a future on there, bro. Future wrote some stuff back in the day. I didn't even realize he was in the music industry yet. You know what I'm saying? Like and it's like, bro, like old Ludacris songs. He's in like the video for like Bubba Sparks and this new blue. Like a point in time when I didn't even know I didn't even know he was in music industry yet because I feel like for most like future fans, like he started to appear familiar around, you know, I'm probably like. Well, Rax, you know what I'm saying? Well, Rax first came out. That was the first time I ever heard a future. Well, that's where it came out. You know, and that was like 2000, like 11, 10, 11, something like that. You know what I'm saying? Yeah, definitely like 2010, 11.  But blue, that was the one I learned about. That's like 2004. So to be from 2004 to 2011, seven years of career. That's already impressive. Yeah, and then to go from that 2011 to today, which is another 13 years. It's also impressive.  You know what I'm saying? Like when you think about this industry, especially, yeah, but I remember he came up with a dungeon family. Yeah, that's true. You know, like being around, you know that. So some artists and managers are just waiting for lucky moments when the ones who are killing it have systems to consistently take artists to another level over and over again. And if you want to see what that looks like, we just did a collab where we not only show the system that we use. That's resulted in Billboard hit some of the biggest viral moments on TikTok, Instagram and YouTube. But also we got J.R. McKee to break down how he took an artist from zero to one of the biggest hit songs of twenty twenty two and getting a Grammy in January of twenty twenty three. This is recent stuff, not old tactics. If you want to check it out, go to www.brandmannetwork.com slash Grammy. Don't forget the WWW or it won't work because J.R. gets into the details of looking at the data, decisions that got made, how much content got created and how they adjusted the content over time for different parts of the campaign. This is real behind the curtains type of stuff. So again, go to www.brandmannetwork.com slash Grammy. If you want to check this out and apply it to yourself, back to the video. Different. He wasn't technically in it, but he saw some different things. And that probably is what allowed him to navigate and get that game. He just doesn't present like the rest of that, that your family, you know, so people don't know where you came from because you're not presenting like where you came from. And that's what shocks him. Yeah. Because then if you think about what Future does, and again, because of the category he's in him, the data originally, when they first came out, they didn't get the respect for the creativity that they had. He was like, Oh, what's this one blue rapper? Like a lot of people got thrown in that category when it wasn't even all the same, right? And like, what is this? They just making noise. But then if you rewind and then you say, Hey, some of his lineage is a dungeon family, and then you look at a Andre and Celo and people like that.  You know what I mean? Just like get me talking about it. Like, I mean, we were street dudes, a lot of us and we had street things going on, but we just didn't talk about that in our music. So it was just like you repackage the same type of creativity. So, you know, Future, I would love to see his story when that one come out. Yeah, his documentary. His would be dope. His would be dope. But yeah, man. Look, like he said, some cases are spending money in this and that perceptions make it don't go broke. Some of them are spending to win and it actually is helping them level up. But I think there is like just a fine line and how you do it. Strategic brand spending is what it's about. Like I'm going to buy this $10,000 outfit because I have two shows and an appearance that I can make while making that money back versus I'm going to buy this $10,000 outfit to sit in the house. Thanks. One is going to help you go up.  So that's why I got it up. And we'll leave it at that for today. I'm Red Man Shine and I'm Corey and we out. Peace.


Be brave. Be strong. Be bold. Become a golden bear. Be the first. Tony Ann Williams was the first Jamaican woman gymnast to go to the Olympics in 2016. Stand out. Our rugby team has won 28 national collegiate championships in 15s and another 5 in 7s. Be exceptional. Abby Weitzel not only became Pac-12 swimmer of the year, but also won two medals at the Rio Olympics. Surpass the standard. Andrew Vaughn became the first winner of the Golden Spikes Award from Cal, making him the nation's top amateur baseball player of 2018. Be an outlier. The women's rowing team was the only Cal team to win an NCAA championship in 2018. Persevere. When Robert Paylor became paralyzed and was told he would never walk again, he defied all odds and walked out of Craig Hospital 11 months after the injury. There are constantly bears who are setting and going beyond to achieve new levels of excellence. Believe in yourself. Believe in those surrounding you. Believe in Cal. Here at CalTV Sports, we cover the incredible and hardworking athletes that make up the athletic community at UC Berkeley. We strive to represent these talented athletes and accurately portray their dedication to their sports.


Hey everyone, my name is Radu and in the next nine and a half minutes we're gonna talk about web assembly and machine learning and We're gonna have a quick look at WASI NN and a new proposal for neural networks in web assembly I'm a software engineer. I work at Microsoft Azure if you've seen a bunch of Deus Labs projects mentioned today I work on the team. We also do a lot of work with the bytecode alliance and the CNCF and TLDR I'm interested in everything that has to do with web assembly machine learning distributed systems and Most often the combination of the of the three I'm a maintainer or contributor for waggy crosslet hippo Bindle the HTTP extension to WASI and WASI NN This talk and a lot of WASI NN has been Contributed by Andrew Brown and Mingq soon from Intel. So this is a Shoutout to Andrew who's I think on a sabbatical. Hope he's enjoying his time off We're gonna talk about a little bit about web assembly and WASI and then machine learning in web assembly. I Paid very close attention. No one actually mentioned that web assembly is neither web nor assembly today And that is absolutely a given at any web assembly conference. So I think a Lot of people talked about what web assembly is and what web assembly isn't But in short, it's just a binary instruction format for a web for a stack based virtual machine But in short, it just lets us run cool stuff on the web. That's not JavaScript only But on top of web assembly, it's web assembly has no mention necessarily of the web You can run web assembly outside the browser pretty well, and that's where WASI cam comes in it's a capability oriented API and essentially is designed to standardize the execution of web assembly outside the browser and What web assembly and WASI give us outside the web is a portable lightweight fast and secure way of executing semi-trusted or untrusted code and If you're just getting started or interested in getting in depth with Anything that has to do with WASI you have to live to read the Lynn Clarks code cartoons They are probably the best resource for anyone getting into web assembly and WASI Why would we want to run Machine learning in WASI? Well, mostly for the same reasons we want to run anything in web assembly We want the portability that web assembly gives us we want the flexibility to run the same web assembly module anywhere and Specifically for machine learning. We want to run the same machine learning model across different architectures We also want to have language Agnostic access to different machine learning run times and more importantly We don't want to keep re-implementing the same CPU instructions and machine learning operators But there are a couple of problems that makes that make running machine learning in web assembly today not ideal First and most obvious is we don't have GPU access in web assembly run times There's also no multi-threading or other hardware acceleration. There are obvious missing missing CPU instructions from web assembly that's Probably no one's gonna add for each machine learning framework and then in general deploying machine learning in production It's just difficult So this is where WASI and N comes in the web as the WASI neural network proposal It's a way of allowing us to load a neural network model into a runtime and Essentially run inferencing on that particular neural network model It's framework and format agnostic. So if you have an implementation, you can run it for By torch tensorflow or any other machine learning framework or model you want to run it for It's much faster than running inferencing in pure web assembly and it's really portable we'll see a recording of The same machine learning model and neural network and runtime on across Raspberry Pi's and Intel CPUs and AMD and GPUs as well the current implementations are for the open Vino model and the onyx runtime and Essentially, it's a pretty simple API. It lets us load up an opaque byte array as a neural network model We can initialize the execution context and bind some inputs as tensors We can compute the inference and then get the output tensors using a Specific get output result the API is written in Wittix Which means for anything that you have either a code gen or you want to manually write bindings for Wittix You can do it. It's not fun But in essence if you want to write the low-level implementation all you have to do is call the four main API functions that Wazian and gives you and you can implement that for any web assembly run time the interesting part is and Here yeah, we're gonna see the same neural network and the same runtime and the same web assembly module run across an Intel Mac book using the web assembly runtime first using the Wazen time Hope that's visible I'll just let it run essentially it takes the same machine learning Model built with PyTorch that does image Inferencing and now runs it on a on a Raspberry Pi the great thing about this you can cross compile web assembly from anywhere and I mentioned earlier we essentially can take the same model and the same Run time and run it in something like waggy The one of the important things is it's more performant than running pure web assembly So you can have a look at the at the benchmarks The actual inference is really really fast it's around two milliseconds tensor Pre-processing is the slower part. It's around 10 times slower than the actual inference The other part is you still have to run pre-processing in non-python, which is not ideal one of the other really interesting proposals we've seen recently is Waziparallel and One of the ideas is running the pre-processing using Waziparallel You can find most of the implementations and resources about this on github Any questions? Go ahead and repeat the question. The question is why it's faster than pure web assembly Essentially there are ways of running inferencing in pure web assembly And the way that usually done is a re-implementation of the machine learning framework That's compiled to web assembly Waziann what it usually does is essentially you can Offload the execution and the inference to the runtime and the runtime has access to hardware acceleration GPU or anything like that So what what you do is through the Waziann API you pass the model bytes You pass the input as a tensor input the runtime does does the inferencing using GPU access And then you get the tensor back Okay, thanks, Radio. That was great. Thank you


Welcome to the Opta workforce identity developer podcast. Today, I'm pleased to welcome back developer advocate, Alyssa Duncan, and welcome to the show SDK engineer, Jared Peralt. Hi there, Alyssa and Jared. Hello. How are you doing. Doing great. Thanks for being here. I'm obviously spoken on this podcast with SDK engineer Laura Rodriguez. So returning listeners will be a little bit acquainted with Octa's SDK work, but Jared brings us a different perspective on it. So, Jared, what does the SDK engineer role look like for you. My job is to write SDKs that conform to the OAuth spec and specifically implement Octa. Obviously, Octa is an OAuth offering and so there's, you know, certain implementation details that Octa has chosen to implement and such. And I think one perspective that I'll have that's a little bit different than Laura is that she is a backend SDK author and I work on predominantly front end SDKs focusing on JavaScript. And that you called it when we were talking about your role before was a career of reading docs that other people didn't want to read. So you're really doing that interpretation, aren't you. The docs, the specs specifically can be a little bit dry, but you know, it's just part of the gig. Yeah, absolutely. And so you're mostly on that Octa auth JS. Who is that for? Who should use Octa auth JS. Octa auth JS is basically for any JavaScript needs can reach for that SDK. It's made to execute in browsers in no JS environments. I believe there are some people that even use it in like electron apps and other things. It is quite monolithic. We do kind of plan to break it up a little bit into smaller chunks. It's kind of like the work that we're, we're looking on in the horizon, but right now, for any JS application. It's a one stop shop for bringing OAuth compatibility to your JavaScript. So this SDK work is all about making it easy for people to use OAuth and to do OAuth right. How would you describe the relationship between that spec and the SDKs that you work on the SDK is kind of trying to position itself to do all of the work for you in the areas that we can.  So we try and handle all that kind of stuff for you so you can store tokens and all you have to worry about is integrating the SDK into your app and then, you know, everything else is already done for you as much as we can possibly do. So if you look at the spec, you see, there's not that much about clients compared to servers and the general protocol. What's up with that. I don't know. I think that in a lot of ways that the spec is written for like zero trust clients I know we're going to talk about that a little bit but I think that the spec is kind of written to be suspicious of clients on purpose right you have to authenticate, you know, approve who you are. So I think that's, you know, kind of the kind of the reason why there isn't a lot of detail about it where a server is presumably a known entity so you have already have like a trust relationship with your with your own servers, I would hope anyway. We hear a lot about zero trust. Would you like to define how you use that term here. The way that I think about it because the way that OAuth is kind of positioned is everything is kind of from the perspective of the authorization server. I think that was something that took me a little bit of time to get my head around because I always think of everything from the perspective of a user right like I'm giving a ticket that says user needs to log into this application so I'm thinking like all right they enter username enter password, you know, what do I do with the user and password and then you know you look at the spec and it, and it doesn't say like oh give the username give the password. So the way I kind of think about it is that the authorization server has no reason to trust the client that is saying I am Jed Perot. So if you're integrating a lot from a server, you have a little bit, you trust the computer the server that is then making that request so it's a little bit more reliable to it the authorization server can trust that you are who you say you are, where a browser could be anyone anywhere anytime. There's, there's not a lot of rebuilt trust before you're identifying yourself. You're saying that zero trust means that one you always have to make sure that the person or that caller is who they say they are and they have the access to whatever resources that they're requesting. And maybe we shouldn't trust browsers. Yeah, essentially, you know, anyone, anyone can go to any website, you know and type in credentials and you know see what happens so you know yeah you have to do a little bit of due diligence and obviously you know there's there's a whole internet in between, you know the browser and the computer so you know there are many attack vectors and such that can be done there. You know these payloads are going over an open internet, you know, so you have to make sure that everything is is you know encrypted and secured and you know in transit and all that kind of stuff as well. Yeah, definitely. And so is zero trust the only way that we can do authentication or are there other tools for situations where it might only be partially applicable. So it all depends on where you want to actually interact with the authorization server. Okay, that's kind of why I'm saying I try and think about it from the perspective of the authorization authorization server. So if you want to implement OAuth directly in your your web application like on the browser. Then that would be considered a zero trust client but if you want to have your web server established like a more traditional like session between the web app and your server, you could then implement OAuth on your server. So the session basically represents some kind of UI UI ID or whatever to then access the tokens and then those tokens can be used to be sent to resource servers or whatever you're protecting. Obviously then you have to do things like manage state because sessions are you know based in state and all those kinds of things so obviously it's always more convenient to do, you know, like, I don't want to say less security but you know the less the less moving you have the simpler application isn't somewhat obviously so it is often more convenient to implement OAuth on the browser directly but it is theoretically less secure because you know the reasons we've stated when we start talking about using SDKs. It's often kind of like being trails through a park so following a trail gives you fewer choices than just like taking off into the underbrush and hiking across the stream instead of going over to the bridge and just getting straight to where you're going, but the trails are put in places where people would probably prefer to walk and often you still come to this fork in the trail and have to choose which one you're going to take. This might take you quickly where you're going another one might take longer or might not even go where you want to. So, in that metaphor, where are the big decision points when someone starts using the off JS SDK, where they'll have to basically choose their own adventure for how they want to use it. Well, they just like right at the beginning if I'm being honest like as I was saying I think if you're if you're comfortable with implementing OAuth on the client, then you know you would reach for the SDK methods that are designed to be running a browser. It is ultimately a isomorphic module which means it will run you know in in a browser or in node like on a server, but there are certain methods that are only going to execute in a specific environment. If you prefer to do something where you have a more traditional session established between the client and your server and your server implements OAuth, then you know you'll you'll reach for those no specific methods. For the most part, once you kind of choose a path. I think, you know, it's it's kind of like, you know, there's not a lot of forks on the paths themselves but I think you know it's, it's kind of like, I guess to extend your metaphor is like a ski slope, you know, you're choosing what ski slope to go down and once you're on the ski slope you're not going to suddenly you know chunk to another one. I mean, I hope you wouldn't anyway. So one of the early things that someone who's setting up the SDK may encounter is the choice of app type. So what should a developer know in order to pick the correct application type for their use case. The main app types that that we really deal with would be either spa single page app or a web app. So a web app means that the relationship to the off server is on your server it's a it's a trusted computer. And then the advantage to that is that you can use a client secret. So back to the zero trust conversation that when you have a zero trust client you don't want to provide that client a client secret as client secret is supposed to be, you know, a secret. So if you were to put that into source code that would be distributed on a browser people could easily look that up you know examine the source, the payloads that you're sending back and forth and like the JavaScript debugger. It would no longer be a secret. So if you choose, if you want to implement OAuth on the client in a browser, you would choose the spa option for your app type. The spas taken me a while to always the reference that as a single page app. We're not just sending it off for some relaxation we're actually trusting it less. The problem is it if you guess wrong about what app type you're going to use and how would you go about fixing that. It's not a big problem at all you can just very simply create another app and then you just update your off JS config with the new client ID and or client secret depending on which way you're going. So when you say create a new app you mean set up another integration in octa. Yeah, yeah we'll talk a bit about how that part of the process works in a few minutes. So what you want to make sure is that if you're running JavaScript within your own like within your own user right or your own machine so you're having a spot you have a spa you have a view app you have Angular you have react whatever. And everything is basically public right with the JavaScript application. That's what you want to make sure that you don't have any secrets in it it's called a public client versus if you have something like a, let's say a dot net NBC application or something in like Java spring, where it is all running within the context of the server, you can then store client secrets there and it could be considered confidential. So that's the way I think about it if I might if I'm writing something that is completely public, or is there a way that I can keep a secret from somebody else right to piggyback off of that you can still use like Angular view, like a traditional spa framework as a spa but still protect it from from the server. So that would be establishing a session, as I was saying and then having the server itself, then interface with the authorization server. There, there's a few inconveniences to that because one of the things you'll get from the authorization server is an ID token, which often represents the user's profile information so you can say you know like, you know, hi Jared and all that kind of stuff. But you can solve that very easily by just adding an endpoint to your server that your web app would hit upon a successful authentication. The next thing once you've decided whether your app is going to be handling secrets or whether it's going to be a public app is that you're going to start thinking about the flows that you're building. So, if this is someone's first exposure to the idea of flows in the OAuth context, how would you describe what flow even means? Yeah, I think this is something that kind of took me a little while to get my head around as well. So I, I kind of trying to think about it from the perspective of the auth server.  So it, it kind of describes how the flow of data to the off server and then back to the requester like flows flows through the system. So, you know, all of the components in the in the system so if it's a browser it would be a browser if it's server server. I mean if it's a if it's a browser presumably you're interfacing with your server as well at times. So it kind of just describes the transfer of information to the various, you know, actors in the in the system. I like to think about flows from, like I guess the user perspective that so maybe the opposite of the off server. I think of it as use case. So I think about how I want to authenticate into the system. Am I doing it as a user on a web browser, am I doing it as a user, you know, was it using and using a spot application am I doing it as a user from a different sort of web server at page p ad perhaps, or am I doing as a command line or you know whatever it is I'm thinking of it that way and then saying okay so now I have these associated a lot of flows that goes with that use case. So what are the most common flows that you see people using in the SDK for the client, it's going to be authorization code with pixie. That's by far the most common one. I think we do technically support authorization code without pixie, but we absolutely do not recommend that pixie is essentially a mechanism to compensate for the lack of the client secret. So that the off server has some proof that the original requester is the one that is fulfilling the request, essentially if you don't have pixie. You're sending a, you're being sent back a code and that code can be exchanged for tokens by anyone that has that code.  Yeah, when I was checking the docs for what flows we were likely to end up talking about. I noticed that in the pure off code no pixie flow, it said just set the response type to code and pixie to false in the s config and I went, uh oh, that looks pretty deprecated. Yeah, absolutely. And so in the pixie flow which is spelled pkce and stands for proof key for code exchange. That's what we recommend for the single page apps that can't store secrets. So what actually is pixie. So what it what it is is it's a cryptographically generated string.  Yeah, when I looked into the docs. So as far as we make a random string and then we use a hash of the random string. And because you, I think kept your random string secret, then by being able to hash it and hash it with things, you can prove that you're the same person who originally generated that So you keep someone else from jumping in partway through the conversation that you're having with the server and going, oh, well, yes, I'm totally the same person as before. They go, oh, you don't have the right hashes you don't have the same secret as before let's fail out here. Exactly. And then that would be an example of something that the SDK would do for you so anytime you would make a request with with an SDK method we generate all of the the pixie the code challenge the verifier we write it to local storage so it can be an entry later, you know, all the all the things that you would have to do to implement that for yourself that's an example of something we can do for you. Yeah, we talked about using pixie in this context with the spot but pixie should be used for anytime use authorization code blow, including for confidential clients as well because it's, it's just so awesome I like to think of it as like it is pixie powered, powered by woodland creatures sort of thing and so I'm a fan. Yeah, it's such a relatively small thing that you can do for such huge security gains that why wouldn't you enable it. Another flow that you see written about quite a lot although it is deprecated is the implicit flow. So I thought it might be worth asking, what did the implicit flow used to do back in the day. So the implicit flow can still be used today but it's not recommended for spa applications. The reason is that the way that it returns tokens to the requester is it does so through a redirect that includes the tokens in the URL as a query parameter. So your tokens are essentially just out in the open for anyone that can see the URL and that's possibly the most fundamental part of the internet protocols URLs so it's the reason it's not recommended anymore for spa applications is that I think you can still theoretically use it for more traditional web apps that are going to do like a true browser HTTP post, because then the tokens would be returned in the post body rather than as a query parameter. But that doesn't really interface with spa apps very well that's more of like a traditional web app sort of approach so you can still use implicit flow in some cases but definitely not recommended for spa. And how urgent would you say that is for somebody to switch off of implicit flow if they had ended up with it on a spy app. Yeah, I would say take care of that sooner rather later for sure. Yeah. Anybody watching your web traffic is just getting all your tokens and you're hoping that they don't decide to impersonate you. I also want to add that there's some really great YouTube videos and blog content about the implicit flow and why also to switch over to like that some of the more deeper context on that I highly recommend it it's great stuff. Is there any other flows supported in off JS that someone might see in the docs and be like, Oh, should I should I care about that is this for me. I noticed that there was an interaction code flow like would that ever beat off code. Pixie. So interaction interaction code flow is actually a extension of the OS spec that was written by octa and it's heavily based on authorization code flow. So it uses Pixie as well. But it's, it's, it's made more for a better like user experience I guess is the way I would phrase it. It you kind of interact with the authorization server in multiple interactions, rather than collecting all the data from your user like you know one form username password hit, you know, hit submit. You can, you know, first collect their identifiers return that's the server ask for your password return that's the server they may now ask for a secondary factor. You know, it may return to the user all of the factors that they have already set up so they could choose to, you know, authorize with email s mess, whatever. It all depends on how you set up your octa org but it's a much more dynamic. Well, I mean it is an API, but it's not truly a rest API so I don't, I don't usually when people say API they're talking about rest API is and it's, it's not quite that. It's all, it's all post responses. But the way you would use that if you wanted to is is the easiest way is to use the IDX client that off JS offers. The, the end result is essentially the same in an authorization code flow you get an off code authorization code back interaction code you get an interaction code back but those codes can be both exchanged to the token endpoint in the same manner. And they're both protected by pixie as well. So, for the most part when you're implementing either one of these flows they're, they're mostly the same as far as how they interface with your application. So it's under the hood, when I get this really elegant like behavior shift to using the right local verifier if I'm on my phone versus on my laptop kind of thing, the web page, and the identity server are just trading that extra little bit of information that wasn't mandatory per OAuth, but makes things run a bit smoother. So that like an extension to OAuth for humans where OAuth is a little bit more for machine to machine communication. So thinking about having that better user experience, then let's talk about authentication user experience right, because that's like a big thing people want to have highly customized pages. There's a lot of advantages of redirecting to an identity provider and then have had having them, whether it's octa whoever handle that for you. What are the options and why would you pick one or the other over the other. You would always choose, as we call it redirect model which is you redirect to octa and octa collects all the credentials from your user and then we redirect back to your application. The other thing is that then your users credentials only ever exist in an octa system where if you implement the IDX SDK yourself or some other OAuth flow, the credentials at some point will be in your system, whether it be on the browser, on your server, however you're implementing OAuth.  The other advantage is that, you know, at the redirect model that all the octa sign in widget and such it's always patched it's always up to date you don't have to worry about maintaining any of those types of things. Honestly, just a lot simpler to implement. We have things like the, you know, the octa sign in widget that is, you know, a preassembled UI with any authenticator you could possibly imagine we already have views and, you know, all those things for it. So, and if you were building an auth experience from scratch, you know, that would be a pretty heavy investment compared to taking one right off the shelf. Another perk to using redirect auth is that people's hardware tokens can work on the correct URL. Like we talked about in a prior podcast with Megastogi. If you do try to do embedded auth, some tokens just plain won't hand out your creds if you're not the domain that they issued those creds for. There's been a crackdown in the third party cookie for browsers. I believe the motivation is to try and prevent like, like ads from, you know, spying on all the websites and things you're visiting but unfortunately it does break some existing OAuth flows as well. What excuses do people use to keep the embedded auth when when redirect is so much more secure. You get a lot more control so you can customize the views and such a lot better. I mean obviously if you're going to if you're going to write the view yourself right you can make it look however you want to where if you're using the redirect model you're using the the octa sign in widget. There is a theming API and things that you can use to make it look, you know, closer to your brand colors or what have you but you know there's obviously going to be limitations to how, how much it can look like you know your existing web app, where if you were to do it yourself you can control it a lot better. That can sometimes be a little bit of user education going a long way as well with understanding that talking directly to the identity provider is better than giving your creds to whatever website asks for them. I would be a little bit suspicious if I'm on a website and you know it's like black and purple and then I, you know, get redirected to a page that's suddenly white and blue, you know, so I do think in a lot of cases theming is important, because it's very jarring when suddenly the page is completely different. So I would say that that that is an advantage but yeah the keeping the credentials in in only octa I think is probably a better argument for redirect model but with the brands API you really can have it both ways. You can also add the custom domain for your for that redirect to octa so it can look like a seamless experience still within your own domain name so that's also pretty helpful. And I feel like it's the days of just using a username password field is your only two authentication fields are over right so the amount of work that it takes to integrate the higher elevated security levels that we need now it's it's way beyond just a simple username password. If we're using off JS to talk to an octa tenant the docs will walk us through using the octa admin console to set up what we call an octa application. And I've noticed that that term application is really overloaded, but the way that I like to think about it is that the app that you create is kind of sort of like making a user account for the integration but it's not a user account for a person it's not where permissions management is done in a way that makes sense for a machine talking to a machine instead. You have any tips for making the right choices when you set that up. Yes, I think we kind of touched about it a little bit earlier. If you do choose to implement OAuth on the browser directly then you'll want to choose spot application as your app type. But if you want to implement OAuth on your server then you would choose web app.  But in some cases can be a little bit less convenient than having the tokens directly on the client. And then yeah you'll have to select which grant type you want and that will correspond to what off flow that you're trying to implement. Maybe I'm a little biased, but I don't think it's all that hard to set up. Like my first week at Octa I had an app up and running in like a few hours. So it's like I was going back to the ski slope example once you kind of get started you know you're going to reach the bottom of the mountain one way or the other. I've definitely found that whenever anything goes wrong setting up an app it's because I skipped the step following the directions. When you do each step in order it works great, but you do have to make sure that you match between what your code is configuring to try to ask Octa for and what Octa is told. This is what I should give to this client because any mismatch there could represent someone attacking you trying to misuse your creds. And then we've also got a lot of framework specific SDKs for various JavaScript frameworks. Do you have thoughts on when a dev should choose the framework specific SDK or just use pure off JS? The way I would describe the framework SDKs is they're a little bit of a opinionated implementation of I guess off JS. So they're set up to heavily favor redirect model and I think all the samples and in such even only really illustrate using the redirect model. If you want a more customizable experience you may just want to use off JS yourself.  So you can still reach for off JS methods when when you need to. Yeah, if you're just trying to get something built very quickly using the framework SDK with a redirect model is the fastest and easiest way to do it. So you were talking a lot about spas here in this example but what about other sorts of JavaScript based applications like maybe just node to save an express API or if you have. So you're writing a web app in express, you know, using a templating ancient like what are other options there as well. Yeah, so that really goes back to where you actually want to implement a lot. So you can have a express server serve, you know, server react app, but if you are protecting a resource server that's independent of that express app maybe you want the clients on the server so the client can reach directly to the express app.  So in that case it might make more sense to have your tokens, your OAuth integration on the on the server in the express app itself. In that case you might just establish a very traditional session between the express app and your react app and your react app at that point wouldn't need any octa SDK, it would just be the session as as everyone knows it today. So you could use off JS on your within the express app however to do interface with with octa to actually get your tokens on the server side. Where would one use like the JWT verifier SDK I think I saw that as an option, and the OIDC middleware. OIDC middleware is similar to like octa react octa view where it is a opinionated implementation off the top of my head I'm not sure what flow it uses but it uses past uses an open ID client under the hood and passport integration. So you can just add it as middleware directly onto your express app and the idea is that you get all that all that stuff for free. And the the jot verifier would be used if you want to verify a token so if you have a token on the client and you're sending it back to your server and you want to verify that the token hasn't been tampered with, etc. JWT is like ID tokens are ultimately signed. If for whatever reason you need to verify that your your token hasn't been tampered or you want to verify further verification of the token you would reach for the job verifier. But the job verifiers is only ever made to run in a node context that would be a server only application. Thank you so much for joining us today and educating us all on the front end of the SDK world. Is there anything else that you would like developers to know as they're using off JS. One thing I do think that off JS does a poor job of is is there's not an easy linkage between the off flow that you're reaching for and the methods that you would be utilizing in the SDK. That's that's something that we're we're trying to fix that I think I mentioned at the, at the top that we're thinking about breaking apart off JS to make it a little bit more digestible. I think it can be a little bit overwhelming of an of a library right now because it's made, you know, to to run everywhere and do everything. So there's so many methods in it and you know they're all named after authentication so they all sound the same so it's it can be difficult to determine which method you want to use and when. And I think part of it most of that is is a documentation issue I think we could definitely revamp though the read means a lot and link them more carefully to the OAuth spec. The OAuth spec just kind of keeps moving we need we need to keep our docs up to up to date specifically the the read me but I think that's that's probably a big, a big thing that we need to we need to address on our end. So I don't know patients maybe but. Yeah, I think that's something to keep in mind if if you're trying to link your OAuth flow to methods in the SDK and you're you're struggling to link the two I don't think you're alone in that. I myself and I read the docs sometimes go like, huh, and I have to go look into the code to figure things out so you're not alone. If you have any problems though, make sure you let us know you can add comments you can file a GitHub issue you can add a comment to the developer forums and we'd love to hear about it and help make it easier a better experience for you. And thank you both for joining me today and thank you to our listeners for sticking with us through this and learning with us. So go ahead and let us know in the comments what you'd like to hear about in future podcasts. And to go into more depth on the SDKs are there other options tools that you'd like us to track down an expert on we would love to hear about what you would like to hear about.


Hello all, welcome to Sonobas. I am Dr. Mohit Shah and I am going to take you through the basics of Vitalico and touch upon few advanced features of Vitalico as well. So I am going to talk about the basics of Vitalico which I am following by the ISOA guidelines and all my images are basically from Alfredo Mohamed and Rabi Choy's book. So it always boils down to a correct protocol and methodology and therefore we need a sequential segmental analysis where we assess cytos, identify arterial arrangements, AV valves, ventricular arrangements, ventricular arterial connections, identify the arterial trunk arrangement at the free vessel view and the systemic and permanent venous connections. Now if I have to look at the abdominal cytos, I would actually go down into the abdomen and look at the arrangement of the IVC and the aorta. The aorta if you draw a line in the midline just falls to the left of the midline whereas the IVC is more anterior and it is to the right. So this section is of paramount importance to assess the cytos. Of course there are various ways where you could have otherwise assess the cytos but I believe imagining yourself to be the baby helps you better assess the cytos abnormality than relying on the different formulas. So you have got to actually check the checklist for cytos where the stomach and the cardiac apex has to be the left, the aorta anterior and the aorta is posterior and to the left of the spine. The IVC is slightly anterior and to the right of both the aorta and the spine. So the relation of the aorta and the IVC is of paramount importance. The axis is slightly pointing to the left by 45 degrees. There could be a range of 20 degrees here and there to the right or the left. You calculate the size by eyeballing but actually measure it by calculating the cardiothoracic circumference of the ratio which has a mean value of 0.45 at 17 and 0.5 at term. So roughly the heart has to be the half the size of the thorax. You look at the four chamber view and you look at the atrial chambers. You have to have two atrial chambers approximately of equal size. The forearm and the valve flap opens into the left atrium. The interatrial septum has to be seen and the pulmonary veins enter the left atrium. Similarly the ventricular chambers in the fetal life have to be approximately equal in size. There has to be no ventricular wall hypertrophy. The modulator band is seen at the right ventricular apex and the interventricular septum has to be intact right from the apex down up to the cucks of the heart. The right atrium is anteriorly located to the right of the left atrium. It receives the IVC and the SVC and also the coronary sinus. It contains the sinoatrial node and the AV nodes. This information is important in cases of isomerism. In the bicable view you can see the IVC and the SVC opening into the right atrium. The right ventricle is the anterior most chamber of the heart abutting the sternum. It has got a modulator band in the apical region. The tricuspid valve is more apically inserted on the septum than the mitral valve and we will as we will see later that the cordy tendon is inserted directly over the apex. The left atrium is the posterior most cardiac chamber just lying anterior to the aorta. It receives 4 pulmonary veins. However, when you see in the 4 chamber view, you see the inferior ones opening into the left atrium. The left atrial appendage is actually narrower than the right one. You can actually look at the normal coronary sinus. It is situated behind the left AV groove and it is seen as two parallel echogenic lines that open into the right atrium. So, all you need to do is identify the mitral valve and try and take a section posterior to the mitral valve when you see a coronary sinus which normally has to be between 1 and 3. If it is larger than 3 then it is dilated and then you have to look for a venous abnormality like an persistent SVC or pulmonary venous drainage abnormalities. The left ventricle like the right appears apparently larger because it does not contain a moderately band. However, it is of equal size as that of right ventricle and it is more conical because of lack of again the moderately band. The biker speed valve is slightly placed higher or inserted over the septum than the tricuspid valve and as we will see the cordy tendon of the biker speed valve insert onto the lateral aspect of the left ventricle. So, the differentiating point always remains that left ventricle is longer because the moderately band is absent there and the tricuspid valve is more apically placed than the mitral valve. You look at the AV junctioned valves and the semilunary valves and you appreciate the offsetting there. The tricuspid is more apically placed inserted than the biker speed and you should be able to see good movements opening and closing of the valves that it actually denote the anatomy and the function of the ipsilateral chambers. So, tricuspid valve in fact is more apically placed and the biker speed is not biker speed is slightly higher inserted on the septum, but more important feature is that called a tendinane. This is appreciated on the lateral fore chamber in the case of right ventricle go right up to the apex. Now, this is a feature seen only in the right ventricle and becomes important when you have cases where you would have a morphological right ventricle on the left side and a morphological left ventricle on the right side. This feature is extremely important that the chorda tendinane on the right has to insert on the apex of the heart whereas the chorda tendinane on the left side insert midway to the apex either anteriorly or on the lateral valve of the left ventricle. This is a feature that was best seen in the lateral fore chamber. So, always appreciate the offsetting and the opening and closing of the AV valves and this and the sebilunar of course, have to continuously blink. If you see the valves opening and closing in real dynamic screens and you know that the valves are functioning normally. If you see them persistently throughout the cardiac cycle then we are talking of atresia. It means that the valves are failing to open and that is an abnormal scenario but normally you would see them opening and closing in with every cardiac cycle. The interventricular septum is best seen left in the lateral fore chamber view. It consists of four parts. The inlet septum is at the level of AV valves. The muscular septum is the one that actually separates the chambers. The perimembranus septum is seen only at the five chamber view under the origin of the ascending aorta and the outlet septum is seen under the origin of the pulmonary artery. So, denoting terminology is extremely important when it comes to abnormalities of the septal defects. Interatal septum has two components, septum primum and secondum and the foranimate oval lies in the septum secondum. What is the most important feature here is a septum primum is embryologically related to foramen ovale. So, whenever you have a doubt whether you are seeing the septum primum or is it present or is it absent look at the foramen oval flap. If it is seen then the septum primum has to be present because they are immunologically derived from the same entity and the foramen oval flap opens into the left atrium. The direction of flow is from the right to the left to the flap has to open there. Crux of the heart is the heart of the matter. It is where the interatal septum joins the interventricular septum and the two AV valves insert. So, you have to see the crux in each and every patient. The great arteries have to be seen in all and seen to arise and to see the origin of the arteries. See the size, patency and flow, ventricular connections and position relative to the aorta. Now the PA divides into the left and the right branches. This is an important feature that differentiates it from the ascending aorta. So ideally the aorta curves to form an arch whereas the pulmonary artery you know after it comes out of the right ventricle immediately divides into right and the left branches. This is how you identify the great arteries and venous system of course you have the SVC and the IVC. So the key spanning planes include a four chamber view, the LVOT and the five chamber view, RVOT3, vessel 3 with each view, the archer's view and the bi-caval view. So basically the four chamber view can be seen in three planes, the apical, the basal as well as the lateral four chamber. But all you need to know is that you have to have a checklist and the checklist should start for the four cardiac chambers where you see the two atria and the two ventricles, the ventricles and the atria have to be equal in size. They have to be two patent AV valves moving freely with a normal offset. There has to be a modulator band in the RV. The crux, the IVS has to be intact right from the apex to the crux and you should see the foramen ovale flap opening into the left ventricle and you would see the descending aorta in front and to the left of fetal spine and the pulmonary vein should drain into the left atrium. So once you've seen the four chamber view we prefer the apical four chamber view for all our cardiac evaluations except that the lateral four chamber gives you a better perspective of the interventricular septum. When you switch on color with the normal heart, if they both AV valves are functioning well, you would see a parallel inflows and outflows without any flow across the interventricular septum and that's the normal flow. Never forget to look at the area behind the heart. As I said the left atrium is the most posterior chamber. The most posterior valve of the left atrium has to be not more than four millimeters on the anterior valve of the aorta. This is a space that you need to watch for. You can have masses that actually invade this space and widen it but more often than not you would have abnormalities of pulmonary venous circulation that is going to increase this space and you got to watch for this space in every patient. The LVOT begins mostly in the center and you should see the semilunar valve and the aorta goes forward without dividing till the arch and that's the differentiating feature. You have to look for the septo aortic continuity in the sense that interventricular septum is parallel to the anterior valve of the aorta. They are in continuity there. But if you lose the continuity there and if you see that this forms normally an obtuse angle but if it almost becomes parallel to each other then you are looking for an aortic override where the aorta is overriding the interventricular septum and therefore this angle instead of obtuse becomes more and more 180 degrees or so. The RVOT is shorter as it comes out to the pulmonary right ventricle. You will see that the pulmonary artery divides into the right and the left ventures and it continues as a doctor's arteriosis opening into the descending aorta. The aortic arch arises in the middle of the thorax is more circular in shape and the most important differentiating feature is it gives rise to cranial vessels from the arch. As opposed to it the ductile arch begins more anteriorly because it comes from the anterior chamber that the right ventricle. It is more angular as compared to the aortic arch when it does not have any branches in the chest. We have discussed the bicavel view where you see the SVC and the IVC opening into the right atrium. The three vessel view is one syphilag section about the fore chamber where you will see the pulmonary artery the aorta and the SVC in line and from the left to the right in descending order of size. So what it means is a pulmonary artery will be slightly larger than the aorta which will be slightly larger than the SVC but all will be in one line. If you go one section above you will actually see that the aorta and the pulmonary artery joined the descending aorta in the form of a V to the left of the spine. Everything that I say is here is important. The PA connects the aorta by the doctor's arteriosis and the part of the aorta beyond the origin of the subclavian is called isthomas. So you have the three vessel and the three vessel trachea view when we switch on color both these vessels should be of equal size and should show anti-grade flow direction. If there is a discrepancy in the flow direction then we talk of a valvular abnormality of the heart. So if you measure the PA to aorta ratio normally the PA is just about larger than the aorta and the ratio is 1.16. So any discrepancy in the sizes of the PA or the aorta points to a four chamber abnormality or valvular abnormality of the heart. So you look at this vessel size alignment arrangement number of vessels abnormal location of transverse aortic arch as I said both have to have an anti-grade flow and if anyone has a turbulent flow it all points to abnormalities or the four chamber that you can pick up on the three vessel view. So normally you should see a criss cross which happens immediately after both great arteries originate from the ventricles. If you try and look at the criss cross more distally, more distally they come parallel to each other. So look at the criss cross just after they have originated from the ventricles. If you do not see them crossing remember that to look for the parallel walls. If the walls are parallel to each other that means you are dealing with parallel outflows. So the more stringent definition of outflows is when you see that the semilunar walls are parallel to each other that denotes a parallel outflow. So when you look at the three vessel view the structure anterior to the three vessels is the thymus and this is an important anatomical landmark that you know is bored. You have the thymic box on color where you see the intramamary arteries on either side of the thymus and this feature is important. Thymus is important because an absent thymus points towards 20 to Q11 deletion. But of course the machines have more advanced now you have sticks you have multiple technologies where you just draw a line and the machine actually gives you all the information all the sections that we just discussed at the click of a button. So I would advise patients on perseverance remember methodology is important. So sequential analysis and following guidelines will help you actually identify normality better to pick up abnormalities in a much accurate way. Document your heart images in magnified sections and as I said prove normality and that is what we are seeking here. Thank you so much.


feel the power in you, that yes, I have the power. Once you feel that you have the power and ask yourself the question, what use am I going to make this power for? And that will be your answer, that this power has to be used for this purpose. So you find out the power and put the use, make use of that. If you don't use it, if you don't use your power, you will be just wasted away. Another person born and died, that's it, nothing to say in between because you never used your power. But the moment you use your power, you become a unique person in this class. You use your power and change the world. And everybody will be grateful to you. So this is one thing I want you to remember that you are the most unique person.