Hi there lovers and friends, so I want to bring back a video that I previously deleted from my YouTube channel because it garnered way too many critical comments in a very short amount of time and Jared made the call to just pull the plug and just remove it all together because of the backlash that Namely he was getting from this piece of content, but it has been on my mind quite a bit and so I asked Jared if I could republish it. I am not doing this and I know that you're doing it like oh but I'll probably be there for the birth. I am making this decision with you because I love how it can be made together, but I'm making this decision with you acknowledging that you're probably not going to be there. That to be said, it's not you not being there for the birth, it's you being gone for so long that if I do sit in that, I'm going to ball my eyes out when you leave. You need to be very prepared for that. And I hope it doesn't come out the wrong way, but I hope that you know that you could have said this is not the time. Of course. Without it, 100% I know that. I know that. This video is brought to you by Squarespace, an all-in-one website platform for entrepreneurs to stand out and succeed online. Whether you're just starting out or managing a growing brand, Squarespace makes it easy to create a beautiful website or engage with your audience and or sell anything from products to content to time all in one place, all on your terms. Go to squarespace.com slash shambudy to start your free trial, no credit card required. And when you're ready to launch, make sure you go back to squarespace.com slash shambudy because that is how you get 10% off the purchase of a website or a domain. And it's been on my mind quite a bit because welcome to my bachelor pad. I am currently solo for the next two weeks here in Turks and Caicos solo from Jared and also away from my two very young kids. One is three and one is one years old. And the reason why this has me thinking about this video because in this video, we talk about Jared and myself's decision to allow him to go on tour to perform with Jade Nova during the time that I was meant to give birth. And we did this in knowing that this is a critical period. And furthermore, that it's very likely that he'll miss the birth because without ample notice, which, you know, births don't always give you that, he wouldn't be able to fly back in time, especially depending on what city he was going to be currently in. So we had spent a lot of time talking about this and I'm really proud of this conversation. And moreover, I'm proud of the decision that we made together, which is why I wanted to share just to model how different families have to shift priorities in unique ways to make it work for everybody. And I'm going to be honest, I knew that it was a controversial or unconventional decision, but I didn't know how much projecting people would do. And I'm not faulting them for it.  So I got that it was much of it was in defensive me, but it also felt like, damn, one, have some faith and two, give us space to write our own script. And that's why I thought it was actually important to re-put this video out. I do agree with the decision to take it down when we did because as Jared noted at that time, we didn't know what kind of birth we would have. And if God forbid something happened, having that piece of content out there just would have been painful for many different reasons and something that people would utilize to not offer compassion during a time where we would probably need tons of compassion. But, you know, everything has worked out wonderfully. Our two children are healthy. Ziya was born into this world. Myself and my sister were there. Jared was not there.  I won't go too much into detail about it, but I will just say, you know, my sister is one of the most important figures in my life and someone I just love so, so deeply. And while I was laboring with her in the hospital, she said to me, did you ever think about how powerful this is? Because one day, Ryu, my first born, might be doing this with Ziya, my soon to be second born, which just waterworks, right? It was just so symbolic for many, you know, reasons.  Like maybe this wasn't our plan, and maybe this was challenging for me, and it was confronting me with a lot of identity issues. But the thing that I treasure so much in my sibling and having that sisterhood, I was now going to give that gift to Ryu and then to Ziya, who I was soon to meet and fall deeply and madly in love with. Long story short, it ended up being the right decision for us to make, but doesn't look like the fact that it was hard. And it's the kind of hard that never goes away.  Where are you? When are you coming back? Why did you leave? Are you going to stay good night to me? Like all of those things, right? And it's hard, but it's also wonderful to have the gift of being able to still pursue the thing that I feel like I was put on this earth to do, to be able to do it at a large level, and to have the network of support, to have the husband that I have, the family that I have that allows for me to have an amazing family that I trust is being taken care of while I am prioritizing my dreams and my goals. And obviously, one hand washes the other, because I'm able to then provide for my family. But nonetheless, it's hard, and it doesn't just, I guess that's why I want to put this video out, because this is just a reality for many parents. I read a beautiful book that Kelly Rowland wrote, and the book really just highlights a working parents conundrum. The joy that you get in providing for your family and for some people, the joy that they get from their job because they enjoy what they do for a living, which I fall into that bracket, while also the pain that you feel from having to separate from your kid and having to explain to them why you can't be with them, because they want to be with you all the time, which is something beautiful that you don't want to take for granted because it obviously doesn't last forever. And I think that this video between Jared and I is just an extension of that same story of that tough spot that working parents are put in and the tough conversations and decisions that they have to make. So I thought it was important to share and model how we came to a decision like that. So that's why I wanted to bring it back for you. The way that I really feel about it is I am really happy. I'm really happy and is a great timing. No, but there's two things that I'm holding right now. One is the fact that I didn't choose you to be there for the first birth because I wanted somebody in the room who could advocate for my health needs and either one of us had done the research in order to be true advocates, to know the health care system, to know the birthing system, to know the different options, to know why you would choose to go one way versus the other. So I had elected to have my mom who has 10 years of labor and delivery nurse experience. And so for me to turn around now and be like, so important that you're there when I was advocating for you not to be there last time, I think would be very hypocritical. I'm so grateful. Don't get me wrong. The fact that you were there and the experience that we had with Riu was beautiful and I wouldn't change it for the world. And I would have loved to have repeated that again, but not at the cost of you not doing this to any capacity. And it's so unpredictable, birth, right? So that's kind of the tricky thing with tour. You're doing 21 dates. And every third day you're in a different city, every second day a different city. Yeah, some days the next day. Yeah. So it's not as if I can say to you if we were maybe at a different hospital where that option was presented to me, but at Kaiser it's not been presented to me that I can just plan to have the birth induced in a certain day. So that to be said, I could give birth tomorrow. It could be August 4th, could be August 12th, could be August 14th, could be the, I think we have up until 10 days after, could be up until the 20th. But I did mean what I said before, I am not doing this and I know that you're doing it like, oh, but I'll probably be there for the birth. I have making this decision with you because I love that we made together, but I'm making this decision with you acknowledging that you're probably not going to be there. Yeah. Yeah. I mean, that would be, it would be painful. And to your point, the reason why it would be so painful is because of the last experience that we had and how magical that was.  All in all too, I think I saw the Instagram comments from some people. Yeah, yeah, I was getting hit. I was getting hit. Yeah, that we're just like, this is that it's rightfully so, but I think it's important for people to realize that we make meaning out of the things that we want to. Yeah. I have never made meaning out of the labor and delivery process. Not last pregnancy, not this one. Everybody's like, what's your birth plan? I don't have one. Just want to have a baby, go to go to the hospital when pregnancy is so long. And I actually found it very bizarre last pregnancy that everyone's so obsessed with this day. You're pregnant for like 200 and some odd days. Like it's a long time. So I commented to somebody who was like, man, I just feel so sad for you that your partner doesn't value this really special experience enough to make that sacrifice. And I was like, I'm happy for myself that I have a partner who's there every single day as a father. You have shown, you're here every day, day in, day out, day night with, you're a true 5050 parent and partner with our baby. So that's what I make meaning out of. I make meaning out of the fact that this pregnancy you have been emotionally there for me and physically there for me in ways that you weren't last pregnancy and not a lot to do with the communication that we improved upon together. But nonetheless, like the fact that you're not going to be there for the day, I'm not making meaning out of that. And if it means something to somebody else, I'm happy for them to advocate for that and to push for their partner to be there. I'm not going to make those same pushes just because other people think it's not a good look. Yeah. And, and, you know, I think it's, it's to me, like when I read some of those comments, I was just kind of like, yeah, I get how you can look from your vantage point. I understand. That's fair to say.  It wasn't like I just said, hey, I'm going on this tour. So you gotta luck, you know what I mean? You gotta just do this. We actually had a dialogue, your opinion mattered on it. That to be said, it's not you not being there for the birth.  As I was saying to you guys, I recently used Squarespace to purchase a site for our professional emails and for our production company. And then I also use that same website, their domain shared entertainment.com to start their appointments feature, which has been a game changer for me. I thought I needed an assistant at one point, but this just makes it so easy to manage. Now Squarespace provides everything you need to manage your business to accept secure payments to send automatic reminders. And of course, to beautifully showcase your services and more using their website platform, but it's so much more than that. And speaking of beautiful, you really have to check out their fluid engine. This is their next generation website design system that allows you to unlock unbreakable creativity from your browser or do it all from your phone. Lastly, if you have been considering doing merch, like I have and top of next year, y'all hold me to it. I really think I should do this. I think that I've got some interesting things to share with the world. That's me saying it. Squarespace can help you do that. They can actually help you to design your products, handle production, inventory and shipping. Again, when we think I want to do it, but I don't know how or with who see if Squarespace can fill that gap for you. Again, e-commerce, I can go on and on about their services. So if any of this has piqued your interest, go to Squarespace.com to start your free trial. No credit card required for this. Just play around and see what's options, what's available for you. And when you decide you want to launch what you have made in your free trial, go to squarespace.com slash sham booty and get yourself 10% off the purchase of a website or a domain. You need to be very prepared for that. I will.  And so I automatically go into fight or flight thinking of you not being around. And I am like, you know, I know that you know this. I'm really scared about this second kid. I am really scared about managing time. I'm obviously also basing this off of the capabilities of my body right now, which is very limited. So I'm like, will I be enough of a parent to do this by myself? And what will I do when Jerry's not there? I mean, thankfully we have, oh man, this guy, my mom is going to be here for a week and my cousin, Alana will be here for a week. And then obviously my sister Lauren and her family are not far down the road. So I'm not isolated. But I think the fact that it makes me emotional is more of the reason why I'm grateful that you get this experience. Because you give so much. You give so much to me and to this family, to my career, to my dreams. You have sacrificed and given so much. I am glad the universe is giving back to you.  I hope that you know, and I hope this doesn't come out the wrong way, but I hope that you know that you could have said, this is not the time. Of course. Without it, 100% I know that. Yeah. I know that. And I would have completely understood. I knew how the perception would be. I knew the perception would be this is irresponsible. This is something that's not fair. You know, all of that thing. And I remember, you know, thinking about that social pressure when Ryu was two months old, I had an opportunity that I wanted to take up for a job. And it would have me being away from home for 17 days. And I couldn't bring Ryu. I couldn't bring you. And it was a huge decision for me because in essence, when we decided to have kids, we were acknowledging that there would be a life that was more important than ours. There would be goals, shared goals for this child that would be more important than our individual goals or even our shared goals. And it felt like, man, two months in, I'm already quitting on the job, you know, when she's young and she needs me the most. And I was going to say no. And you were the one who was like, you need to go. This is going to be an opportunity that we're going to see the benefits for for a longer period of time in those 17 days. And you need to do this for you. And I am here as your equal support system for this reason, so that you can do things like this. Now, I didn't put it out there online. You have to because you got to sell tickets. But I, for this reason, I didn't tell anybody. You know, and my family knew, but I didn't put it, I didn't post on social media. I didn't tell anybody because I knew that the backlash and the perception of me would be negative. But the opinion that mattered, of course, and only ever matters is yours. And so that's why I made that choice ultimately. Yeah. And it's something to be said. It's like, you know, going to your point earlier, it's like, this is a short window. I'm going to be in our child's life for forever. And if you're going to judge my ability to be a father or the way that I look at you or our family based off of a month of me having to be away, then it's just like, your opinion is no void to me. Because that's your feelings and that's your opinion. And you probably already had that about me before I even made this decision. Now, let's not mince or cross hairs here. It's going to suck. Yeah. I actually remember that when I went away for that job and you were with Ryu. Sometimes you would call me and you wouldn't be speaking and she would just be screaming. And I'd be like, why is your calling me? And then I realized that you just needed someone else there. Yeah. Someone else to go through it with you.  Yeah. So I know it's going to be hard. There's no part of me that is disillusioned about the fact that not having to raise a one and a half year old by myself, doing that to going to having a one and a half year old and a newborn at the same time while I'm recovering from delivery, it's going to suck. Yeah. But, and if I complain to you, it is never to make you feel guilty. It is only because you're the person I share the authentic lived experience of me with. Yeah.  Yeah. What's up? What's up? But I'm going to be like, thanks for calling me apart. I'm so miserable. I'm overwhelmed. You're going to be like, yeah, babe, I know. Cool, cool, cool. I'm coming. I'm going to play beer pong in a second. Just give me two minutes. Beer pong. What am I waiting for college now? Well, whatever. You're going to be having a great time and I want you to have a great time. Yeah. And here's the thing too, Jared Brady.  And the reason why I'm encouraging you right now to go to the gym, to rehearse, to take time away is because do not make this for nothing. Yeah. It's, it's a funny one of our followers reached out to me because I shared about this on my podcast. Not as fun as I am now. I was a little bit more emotional there. But they had reached out and they sent me a message and they said, Hey, if I were Shan and I would want you to go, you have to go and kill it. Like, it has to be like, yeah, that made sense. If you come back and there was no growth, there was nothing there that nothing, nothing moved forward. And it, and you were dwelling on the fact that you weren't there and that stopped you from performing at your best. This would be a waste. So if you make the decision to go, you have to make that decision 100%. Yes. That one hit home because it was like, I was kind of entering this with a lot of guilt, a lot of feelings, a lot of like, I'm so happy, but this hurts. And I can't really like explain that and do this. And it's hard for me even right now to promote it. And like, how do I show up and with knowing this and all these things. And there were so many things weighing in my head that when I saw that message, it was like, okay, if you are saying yes to this, go hard. Yes. Because it would be worse if you said yes to this, and you weren't going hard because you felt guilty and you let your guilt get in the way of you actually making this moment. All of it, I want you to get the tour experience that you want. You're going with your brother, you're going with Mike, a friend who's a DJ, you're going to be amongst people that you have a good time with. Like I want you to have fun. I want this to be when you were in high school and you decided that I wanted to make music because I love the feeling of being on stage. I want, and you dreamt of one day getting to do that. I want this to be the realization of that dream.  Yeah. And I'm going to be suffering without you. Go have all the time in the world. You have to be able to hold. But I'm going to be suffering. You have to be able to hold both truths. I will both. You've got to be able to hold both truths. And one is not going to take away from the joy that I feel for you. I'm going to feel compersion. I might feel resentment sometimes.  I need it to be awesome for you. Thank you for watching or rewatching that video. In closing, I want to share a brief story. So I was talking with another parent and before that conversation, we had just come out of parent-teacher conferences with Ryu's preschool. She's three years old. And the teachers were saying that they want Ryu to get to preschool earlier. She usually arrives around 9.30, 10 a.m. But preschool opens at like 7 or 7.30. And I didn't, I wasn't able to attend because I was at work, but Jared was able to go and he was relaying that to me. And I was like, man, I wish I could be there to tell them that I have no intention of bringing my kid earlier. That I really value the fact that I've gotten to a place in my career where I am an entrepreneur that I can choose when my day starts. And I choose to start it around 10 or 10.30 a.m. That way I can wake up when we want to. I don't want to start the rushed hurried morning. I remember growing up, I'm just naturally a late riser and I feel Ryu's the same way. I remember growing up, having anxiety when I slept, like waking up to see how much more time that I had. So getting freedom over when I could wake up was one of the most impactful things when I turned over from a life of working for others to working for myself. So I just like really like I very much treasure that gift. So I don't want to impart that on my kids, especially if it's unnecessary because you know, she doesn't even have to be in school right now. So they, I don't want to speed it per morning. And on top of that, we usually do one activity together before she gets to daycare. And then I bike her to daycare. So the pace that we have is consistent with the culture of our family. And I don't have any plans of changing or speeding it up. And I was expressing this to this other parent. And then I was basically saying like the way that my work is set up too is once I start, it usually gets really filled up very rapidly. And the next thing I know, I look up and it's 5pm. And I just can't imagine dropping my kid off at daycare at 8am and then picking her up at 5pm. Like that's an incredibly long day. And that parent like nodded and listened along and then turned to me and said, well, my kids went to daycare from 6am to 6pm because of my commute to work. And I just immediately felt so bad because I wasn't telling that story to emphasize that like anybody who leaves their kid at daycare for this long as a bad parent or just to put any shame on a parent who just honestly and genuinely was trying their best, doing the best with what they had, with the circumstances that they have. And we all feel the exact same way. We all have the same challenges and feelings. And I just want everyone to keep that in mind. And especially with this generation. And I just want to say this on record, I am so proud to be a parent in the cohort of parenting that I'm in right now. I am in awe of all of you. When I see you at the park playing with your kid, something that I didn't experience growing up, but I know many of us, you know, our parents were there to raise us and instruct us, but like physically play at the park or physically play with us. That's just to me, maybe it's culturally that just wasn't very common. When I see you at the airport, taking a second to yourself to gather yourself before you address your kids, because you know you're in fight or flight and your immediate reaction may not be the best one. When I see you show up at parents in classes, when I see you at the libraries, like when I see you online and I read your comments, I just know how deeply you care. And we live in this very conflicting generation where it's like sky is the limit, hustle, achieve all you can, rise to your potential while also being a 100% present and devoted parent, while also putting your child's needs first. And that doesn't just include their, you know, their food, water, shelter needs, also their emotional needs. And we're trying, like we really, really are doing a really, you know, we're really, really trying. And I just want people, you know, not just to retroactively see that in myself and Jared before making comments that could make people feel bad about a decision that was already hard to make, but just in your everyday life in general, when you're reflecting on and talking about other parents, or even talking to yourself, just applaud yourself for doing the best that you can, because I just genuinely know that to be true. That's all. Take care. Bye.


The LED definitely delivers the photons, no doubt. But many are unaware of the LED's ability to detect light as well. Truth. Most light-emitting diodes can also play the role of photodiode. Specifically, a photodiode which responds to the same color light it emits as an LED. Sort of satisfying symmetry. It's less sensitive compared to an actual purpose-built photodiode, but will still pass enough current to be detected by a microcontroller pin. This water-clear LED normally emits red. Since the white light from my phone here includes the red spectrum, I can use it to trigger the LED's photosensitivity, which is in turn detected by the microcontroller. In fact, it's possible to connect two LEDs in a loop. And by exposing one of them to light, produce just enough current to power the other. It's like poetry.


Hi guys, this is Jason Zach from Nathaniel School of Music. In this lesson, we are going to learn a very rock piano technique, something which has been borrowed from our guitar friends who play a lot of the head banging, rock and roll and hard rock and heavy metal. So in teaching you the rock piano technique, you're not just going to learn rock piano, you're also going to learn how to develop accents over a chord progression. And these accents are not going to be too tricky, I've chosen them over 8th note patterns. So you're going to count 1 and 2 and 3 and 4 and pretty much that. As you heard in the intro video, you saw my left hand playing a chord progression, very power chord driven because I'm playing it very low on the keyboard. And the same story on the guitar, when we play the lower register notes, we can't afford to play minor chords or even major chords, they sound very cluttered or very muddy. So instead of that, we tend to prefer a power chord, which is the root, the 5th and the octave.  A very simple chord progression and the right hand is going to support the left hand by embellishing the accents or doing whatever it can do really, maybe some arpeggios, we are going to leave the right hand as organically moving as possible so that you can do it in your own comfort zone. So the right hand will just be the chords with a good inversion set, but this lesson will focus more on the concept of accents and how you can execute those accents in both the left hand and the right hand. Great guys and the notation for this lesson, my handwritten notes as well for a lot of other lessons and the lessons we are going to do will be available for you on our Patreon page. You'll find the Patreon post link in our description. So let's get cracking. So the chords for this lesson are E minor, B minor, C major and D major. So the way I am playing it is E minor, any old way in the right hand, you could do E G B, you could do G B E, you could do B E G. I am choosing B E G, I like the vibe of that, B E G. The next chord is B minor, B D F sharp and the next chord C E G, C major and then you do D major which is D F sharp A or else you can do A D F sharp. And with each of these chords you could probably start off by doing it four times each just to get a feel of it. Something like this. So those are your right hand chords. Now the left hand is going to play power chords. So power chord will be the root, the fifth and it's octave. Quite a power chord used a lot in rock songs. So the pattern here will be E minor, E's fifth will be E B high E, E B E and then B F sharp B. Then you have C G C which is C major, D A D which is D major. So I am playing everything as eighth notes, C major, D major. You could actually start by playing them as a pulse which would be 1 2 3 4 1 2 3 4. I am using my pedal at the four to kind of make it sustain more but releasing it before the next chord. I need to have that responsibility right. So that's your quarter notes.  You can support this with chords in the right hand. You could just play semi-brieves or whole notes which last for four counts in the right hand. Check this out. And we can focus on accenting the left hand which I am going to come to very shortly in the lesson. Maybe go back to simple pulse, pulse quarter notes, crotchets but with a nice sustain at the end if you want. We are playing it straight, no swinging back to eighth notes or quavers right. So that's the scope of what you are going to do in this lesson. There is only one thing which is going to change and that's the accents and now let's get to that. So let me quickly try and define an accent for you. An accent is a relative change of any property of music. So if it's volume for instance, the volume of something which would ideally be a note, a chord or anything will be louder at a given point with relation or in comparison with what's coming up next or what came before. The stuff which is very close to it in time. So you can start off by just accenting or playing. In this lesson we are going to accent with just volume. We are not going to do pitch based accenting or other such accenting which by the way I have done in a few other lessons which we leave in our description. So make sure after this video to consider watching some of our other accents lesson and I am a huge rock music lover as some of you might know in my riffs and if you have heard some of my original music there is a lot of rock in there. So we leave some of the links in our description. Some of the rock riffs which I have composed and also a link to my solo album which you should check out. I have quite a few albums which you need to probably listen to at some point. So getting back to the chords. The first accented pattern or the first accented method would be the beat one. The first beat of the bar. So let's see how that sounds. One. Two and three and four. One. Two and three and four. One. Two and four and one. Two and three and four and one. Two and four and one. Right. Two and four and one. So what's happening there? You are playing the eighth notes in your left hand but whacking the one a bit harder. One and two. Watch your shift. One and two and three and four and one. And the right hand can kind of support that goal or that purpose of the accent by just hitting the chord only at that accented point. So kind of what we did earlier. Maybe play if you are not able to play the thing hard then play everything else soft with respect to the thing which you couldn't play hard you know. So I am playing the other stuff softer. Two and three and four and one. Two and three and four. One and two and three and four. One and two and three and one. Rather simple accent but very important to start off with that. So the next accent would be the next on beat as we are calling it. That would be beat number two. One and two. Three and four and one. Two usually where the snare drum hits. One and two and three and four and one and two. Three and four and one and two. Three and four and one and two. Right hand support. Maybe play the right hand a bit choppy if you wish. Two and four and three and four and one. You have to wait for the one so. Two and three and four and one and two and three and four. And two and very glam rock progression actually. If you like glam rock. Two and three and four and one and two. Four and one and two. Three and four and one and two and three and four. Okay, what's the next beat? We have beat number three. So let's accent at beat three and eventually get our right hand to support the accent by hitting only at beat three. So. As you can see the groove completely changes. One and two and three. There you go. One and two and two and three. One and two and three. So as you accent it, now let's follow the three in the right hand. Two and three and four and one and two and three and four and one. Three and one and two and three and four and one. Three and four and one and two and three. Little choppy up. And the last on beat in a four by four sequence would be beat number four. So here goes. Quite like four. Like a very important slam. The whole band plays that hit with something. Lot of power in the four. While the power chords. Two and three and four and one and two and three and four and one. Four and four. Okay. So those were all the down beats. Beat one, beat two, beat three, beat four. Now let's combine some of the down beat combinations together. Let's do beat one as well as beat three. So that's one and three and four and one and two and three and four and one and three and four and one. Let's see how that goes. Two and three and four and one and two and three. Supporting with the right hand. And what you could do for variety in the right hand, you could do one chord staccato and one chord legato. Like I'm doing now. Choppy. Long choppy. Long choppy. Long all. Long choppy. Long choppy. Long choppy. Changes the groove and the vibe. Long choppy. Long choppy. Legato staccato. Legato staccato. All the other way. Staccato first. Legato second. Okay. Now let's do two and four which are our snare, general snare hit points. Very important to catch the two and the four. So I'm going to try and accent the two and the four. Try to hit that louder. Try to get the left hand first. Imagine your drums. And now the... You can obviously do all the four if you wish. That'll be very busy. Three and four and one and two. This is all the down beats played together. And just as an additional bonus challenge if you want, you can do different inversions at each beat in the right hand. So that's the accents. So before I move into the off beats guys, you must have heard the intro video and you must have heard me playing throughout the lesson where I'm jamming along with a backing track. Now if you'd like the backing track for your practice and a host of other tools to help you with this lesson, especially for DAW users who might be interested in this particular concept where you can import everything into your production software, you can consider heading over to our Patreon. So in this post, you're going to get the backing tracks, you're going to get the notation, you're going to get a lot of things. So do consider heading over there. And like I said earlier, even the midi. And also this particular performance is supported by an incredible guitarist by name Geeth Was from the band Laguri. So check him out and check out a bit of Laguri's music as well while you're at it. So to focus on the ands, let's just look at one of the ands, which is the and of the two. And if you combine that with two of the ands which we've learned earlier, it'll sound something like this. One and two and three and four and one and two and three and four and right and three. So we call this the thresio points or the thresio accents. I've done a nice lesson on the thresio pattern. You should check it out in the description. So you go one and two and three and four and one and two. So the accent points are at the one, the and of the two and the on of the four.  That's a nice way to get the flow of the beats as they go accented, non accented, you're grouping them into packages. So, Thakit, Thakit, Thak. So, these are Indian conical syllables which are very often practiced in Indian rhythmic culture. One and two and three and four and one. So, this is the Thresio. Let's bring in some right. So, the Thresio took us over a one bar sequence. Let me now give you a modified Thresio or just another assortment of three hit points or accent points in the second bar. So, it becomes a Thresio plus the second bar hit points which are going to be quite interesting. Let me play it for you. So, the second bar we are doing. So, pretty much the first two beats of the Thresio got moved a little bit to the right. So, let's put that together. Thresio plus the modified Thresio. Totally two bars. So, the last accented variation would be four accents. The end of the one, the end of the two, the on of the three, the on of the four. So, two ends and then two ends. And then if you wish you can kind of take this and permute it in different ways potentially as homework and see how that goes once you've got all these variations. So, one and two and three and four and one. I'm just trying to hit it first because it's a bit tricky even for me to remember. One and two and three four one and two and three four one and just that's a nice pattern actually. But we are here to play rock with power chords. So, right guys. So, those were all the variations with this rock piano exercise covering a bunch of our 8th note accents using a simple chord progression E minor, B minor, C major, D major. As I said earlier, the riff is available featuring my friend, Geet was the incredible guitar player from Lagoori. Do check out the video and there's a lot of supplementary material waiting for you on Patreon, a backing track to help practice this exercise midi and notation. Quite a bit of stuff. So, do consider heading over there and look at some of the related videos in our description to help you learn rock piano and thus accents a lot better as this genre allows you to really dive into your accents very well. Right guys, thanks a ton for watching. This is Jason Zach from Nathaniel. Cheers.


Hello everyone, welcome back to the live coverage of theCUBE here in New York City from Mongo Local, the beginning of a 20 plus city tour. Mongo.local is originating here in New York City, Packed House, a Mongo local. I'm here with the CEO, David Sierra, who's going to break down with me his vision and kind of what's happening in this next gen data platform they've built. Dave, great to see you. Thanks for coming on. Thanks for having me, John. Love your keynote here at the beginning of the show before we get into the specifics. Mongo is, you know, born in the crowd, developers, bottoms up, consensus is, that's where the developers are. You have the platform, document winning strategy, document database, variety of other tools. The format's changed for your show this year. You're going to do originate here in New York and then do a multi city tour. Take them to the streets. Yes, yes. So what, Candly, our business is so global and we realized that while it's great to have one big flagship event and then have a bunch of satellite events that we really need to take the show on the road. So we're going to be in 26 cities between now and the end of the year, places like Sydney and Sao Paulo and Milan and Frankfurt and Tel Aviv and London.  So, you know, having in-person interactions, connections, rebuilding old networks is going to be great. Well, you hear the Java Center in New York City and certainly it's packed house here. As many people as was last year were here, so you certainly got the local crowd in New York and people flew in for kind of the flagship inaugural beginning, yes. Yeah, no, I mean, but we purposely, in some ways, we're actually scaling down New York because we're moving dollars from New York to some of the other cities because there's so many markets that we're in that we feel like we need to make a bigger presence on. I mean, obviously we're pretty well known in New York and New York is always going to be a very important place for us. But there's some, you know, big markets we're going after and we have a big opportunity in front of us. Digging the streets, that's what the developers are. This conference, your keynote, specifically touched on some of the things that I had on my exclusive preview with you and that was this developer-led data platform. It's a platform, it's not a point solution or an analytic tool or an analytical platform. So you have a world, the platform's emerging very quickly. You guys are really the first to lean in on this developer, changing software industry, not something else. Explain the strategy behind the developer data platform. Really focus on the coder.  And who builds that software as developers? So everything we do starts and stops with developers, right, in terms of making their lives easy. And what I try to communicate in the keynote is that when you look at where developers spend their most time, it's working with data. In fact, you know, depending on the appellation that they're building, they could spend between 30 to 70% of the time just working with data. So if you want to make them incredibly productive and make a big impact, it's all about making it easy to work with data. So our whole raison d'etre is to be able to enable, to simplify working with data, which is to start with a document database and now it's with the developer data platform. And I think the other thing too, I want to get your thoughts on it around the market share and some of the data market is, you know, you look at all the successful companies like AWS as one example, it's an easy one to jump out. I remember talking to Andy Jassy in the early days, they were very misunderstood. And he said to me one time, you know, you got to be misunderstood for a long time, sometimes to kind of hang in there. You guys have been on a trajectory with Atlas and a platform that's different than some of the other players in the quote database market. You guys have a 2% share in that database market that seems to be changing very quickly. I even predicted there going to be winners and losers and new brands emerging. But yet no one really has got a dominant share. Amazon's number one by the quote, Gartner stat, but like that's just databases. So like, how do you see the market? Because clearly you see something here that's a little bit different than chipping away at that 2%, by the way, not a bad time either. It's still a huge market on the database side. But do you see something else going on here? Well, what we're, one, this market is so large to your point that you can have less than 2% share and be close to a $1.5 billion revenue company, right? So it tells you how big this market is. But it also tells you that we have a long, you know, path for growth, right? We have a big road to go up. So we started with the database and what our customers told us was like, we love your technology. It's so easy to use. It simplifies my life. I would love to use MongoDB for other use cases. So we slowly added more and more capabilities. So as people think about building really sophisticated applications and now even AI-based applications, they will think about MongoDB first as a place to build those applications. And that's what we want developers to think about. And so when you look at our customer base, we have some of the largest companies in the world running their business in MongoDB to cutting edge startups who you may have never heard of who are just building their business to either create, transform, or disrupt different industries. I talked with Chris Grooser, who runs the marketplace for AWS earlier. And I said, hey, you know, the classic cloud model is land adopt, expand. Your business model from dorm room to board room is almost the same motion. Get coding, grow. And then you grow into this base. It seems like you have so many customers on the self-service side growing up into full-blown enterprise-like capabilities. Is that a feature or a bug? I mean, I mean, it's obviously a feature because you have a lot of headroom there. Talk about that dynamic. You're seeing more growth than is Atlas picking up that share. That growth's there. So talk about the power dynamic of landing, adopt, and where's the expansion come from? Yeah, again, it starts with developers. I mean, the workloads in general tend to start, new workloads tend to start small because the app has just been built. There's very little data. There's very few users. And over time that workload grows. But as you win more and more workloads is that snowball effect happens. And all of a sudden the business in that account. And so now we have, you know, so many seven-figure and six-figure customers who are really running the business among them to be. But it didn't start as seven, six-figure customers. It started as four and five-figure customers. To your point, sometimes some from self-serve. And over time, they've grown into that because they've slowly given us more and more business. And that's the way we operate. We want to build a long-term relation with our customers. This is not a quick bang.  We're building a long-term relation with our customers that we think is incredibly valuable to them. And as they grow and as they see value we're the beneficiary of their growth.  They're all trying to figure out what to develop on and then how to stand it up and run it. Right.  You got the LLM and AI. What's that story here? So for us, what we are doing is, when you think about AI, for us that's all about building more intelligent and smarter applications, right? And a key part of that is thinking about semantic search. How do I really understand and intuit the intent behind that query? Which needs vectors, right? So vectors basically are a mathematical representation of all forms of data. So you can do things like nearest neighbor searches. And so by enabling vectors or vector searches you enable developers to build these very interesting AI applications based on either LLMs or the public domain and being able to marry that with your own proprietary data. So the fact that we can offer a vector search on our platform means that on one platform you have your source data, your metadata, your search indexes and your vectors which creates a very unified and compelling experience for developers and it makes their life essentially so much more easy. What's the reaction from the investment community around your keynote, the platform play? What are they saying? They seem to be impressed. I think a lot of the investors are quite impressed with our platform story. Obviously as you know we announced some strong earnings in Q1 but we don't get obsessed with where the stock is today or tomorrow. We're thinking about long term where we're taking the business. And given that, we're just focused to keep our heads down. We know what we need to do. We listen to our customers carefully, build those capabilities, try and execute well in terms of going out and winning more business and just do that over and over again. I mean you've got the platform now for multiple years. You've got a trajectory. What are some of the learnings that you're seeing come out of the business from this multi-year platform journey and what's your view right now as you talk to customers? We had an inflection point, more growth. What do you see happening right now with the platform? So I think there's definitely been an inflection point when I joined MongoDB which is almost nine years ago. There's still some questions about what's the winning technology? Is it MongoDB, is someone else? Well nine years later it's clear that we've won the modern database or data platform space. Now customers are much more comfortable trusting us to be able to do more. In fact they're coming to us and saying, enable full tech search. They come to us, give us a time series solution. They're coming to us and they enable us to do in-app analytics. And now, stream processing and vector search. So this is all driven by customer feedback to us because we have 43,000 customers and so that gives us a lot of confidence and conviction about what we're doing because over time the challenge for customers is that when they use a bunch of point tools they get a ton of data sprawl. They get a very fragmented developer experience and so their architecture is both very costly and very complex and hard to manage. And so given that they're grabbing to a place where they say I need to have much more elegant architecture that enables me to move fast but it's much more cost effective and easy for me to use. Talk about the dynamic now when you have customers building in native. A lot of choices you've got streaming now announced today. There's streaming solutions out there. I'm seeing this platform pattern emerging on the big players.  Native services platform and integrations with other services. A lot more, I won't say rubbing up against other vendors and other platforms but the integration stories are coming out. We heard about AWS, Google Cloud, Microsoft Azure and 19 other clouds out there, like other clouds. So integration is a huge part of it. What's native, what's not? How do you see that playing out for the customer? Well again, we start from the point of view of the customer that worked backwards, right? So customers told us they want to expand in these areas but we also recognize we need to be a good participant. You know, where Amazon and Google are sponsoring the show and also sponsoring the world tour that we're going to do for the rest of this year. So they're great partners. Azure is also a good partner and we're working with them. We're winning customers collectively but we know that we need to be a good partner. So different technologies integrate with MongoDB. We work with VI tools. We work with OLAP tools, et cetera. So on the streaming side, while we've introduced stream processing, we do work with the transport companies like Confluence, RedPand and many, many others who offer the transport capability to basically enable these event-driven applications. And so we have to be able to work with these people. We try and build our services in a very composable way and extensible way so we can add more integrations when we find that customers are really demanding that. And so we take a very open approach of how we build our product. You look around here, it's packed house in New York City. You got an ecosystem. Yes. That's a platform, check. Growth, platform. Right now I think you're what, going to do close to two billion maybe this year? Estimates are about 1.5. Little bit. Upside, over 1.5. You got an ecosystem checking in. Mark Porter was telling me your CTO earlier that the failover response time is less than in the milliseconds in Atlas database on all clouds. So there's a trend where this whole distributed systems architecture is paying out dividends. Are you seeing that in the numbers? You see that in the uptake? Is that yet resonating with customers from an impact standpoint? Is it more of a revelation now? Or what are some of your thoughts on that? Because there's a lot of value in that ecosystem and that distributed global platform. Yeah, I mean John I would say that we're really excited about the future but I'm so cautious. Like the economy is not firing on all cylinders but in Q1 we added more customers than we've had in the last two years. So it's nice to see us adding a lot of customers. A lot of other companies are struggling to add more customers to their portfolio. We're showing great operating leverage so we continue to grow our business but also do it in a much more efficient and effective way. But we're, and then we're also planting seeds for growth with all the product announcements we made. So we feel like we are building a very healthy long-term business but doing it in a very disciplined manner. I've been sitting on theCUBE now and I'm on our podcast with Dave every week. AI's hot all the time but developers are setting the standards. There's no de facto standards bodies in this era. Go back to the old era when we were breaking into the business, you know IEEE, a lot of physical layer standards. Now you got the hyperscalers out there. The developers kind of playing that role defining kind of what tools and open source projects will be getting picked up. So we're seeing the developers leading how to purchase or buying decisions or adoption decisions because they're coding in line to the application. The applications are in charge. The developers are driving that. You've kind of brought this up in the keynote and love your developers as your campaign that you just released. Developers are setting the agenda. How do organizations and customers you talk to flip that script because the script has been flipped but not maybe not in the companies yet? Well our approach is to really think about how do we make developers be able to do more and be more productive. Like if you just start and look at where the developers spend their time, look at how they work, you know if you build tools that make their jobs easier they're going to use your tools. If you build platforms enable them to do a wide variety of, address a wide variety of use cases they're going to use your platform. If you enable them to easily go to different deployment models whether it's your own data center, the cloud, multi-cloud, mobile, edge and embedded devices and you can do it on one platform they're going to use your platform. So the more you can make the developers life easy the more they're going to gravitate to you. But they're smart, they're cynical, they don't like hypey marketing so you really have to prove it in terms of building real product that adds real value and that's our goal. And developers do talk very frictionlessly on the internet, they can share their commentary of course you see that. Final question for you as you look over your nine years at Mongo, take us through your mind like kind of how that journey progressed where you are now because you look at it's the same game building software at a whole nother level because the data game AI, it's software. Right. Silicon advances are still software. I would say there's really been three chapters to the MongoDB story. The first chapter when I got there was to really prove that MongoDB was not like a cool toy but that people could really trust their crown jewels, their mission critical workloads on MongoDB. And it took time, we had to build tunable consistency models, transaction guarantees, enterprise grade management security and then over time to start believing. Then the next chapter was like okay the cloud was very popular the cloud redefined how applications were built and how they were managed. So we had to prove that we could build a cloud business. When we went public, cloud was in the single digits of percent of revenue. Now it's almost two thirds of a revenue. And a lot of people were skeptical. They said how can you partner and compete with the hyperscalers? And we showed if you build a great product, have strong product market fit and execute well you can do that. And one of the other things we did that no one else did is we built a truly global distributed data platform that runs across all the major providers with one single elegant interface. So we made it very easy for developers to manage workloads and build applications no matter what cloud they were using. And now the third chapter is all about building out the platform. So we started with a database and saying customers said okay I trust you to run these mission critical workloads but I want you to do more. I've got all these cool new use cases, time series, you know more sophisticated in-app analytics, full tech search. I want to be able to do that all in one platform and based on feedback also now do stream processing and build the next generation of AI applications. So that's the third chapter that we're on today. We were riffing earlier about data scalers. Hyperscalers was the cloud, you guys are the data scalers. And so I guess my final question and the segment with you would be what's your vision for the platform next level and generative AI's role in the future of scaling data for customers and making developers the driver of value extraction and insights that we've never seen before. What's the vision of the platform and your view of how generative AI is going to impact developers? Our vision is that MongoDB is the first choice for developers everywhere to build modern applications. Those applications are now even more intelligent and more smart and AI enabled and they're going to choose MongoDB to do that. Dave thanks for coming on theCUBE and thanks for your time. I know you're super busy with customer visits and investors, thanks for coming on theCUBE. Really appreciate it. Thank you, thank you very much John. Thank you. And congratulations on your continued business success. I think you could be 10 billion revenue but I know I got to keep the expectations down. Keep those earnings coming. Congratulations. Thank you. MongoDB data scaling for customers is what's happening here in theCUBE bringing you all the data here live with theCUBE. I'm John Furrier, your host. We'll be right back with more coverage at MongoDB local after this short break.


What is regularization trying to do with linear regression? This is the residual sum of squares. Y i is the actual label. This yellow term is the prediction. If the learned parameter theta i is way too high, then even small changes in the input x will lead to large changes in the prediction. This is overfitting. We can curb this with the penalty term in the form of either ridge or lasso. Theta 1 and Theta 2 are some learned parameters of a model. And let's say that the values that lead to the lowest mean squared error is some very high value of Theta 1 and Theta 2. This is indicative of overfitting. But with ridge regression and lasso, we want the values of Theta 1 and Theta 2 to be confined into a very small region. For ridge, it'll be the circle, hence the equation. And for lasso, it'll be this diamond, hence this equation.


Thank you very much. Thanks for coming. So this talk is going to be about secure communication And of course the most prominent example being Alice connecting to Bob the ICR web server wanting to establish some HTTPS connection and as we talk about secure communication Well, we expect there is an adversary spying on the IC web server or Alice maybe and Well in the crypto community as well understood that secure communication needs some form of a secure channel So in particular these two Alice and Bob will derive some shared secret for example through a key exchange But the topic of this talk will be what is this secured channel in practice precisely? So the first idea of course that comes to mind is let's encrypt but as we are at crypto let's encrypt authenticated So what we want to have is both Confian shallity either in a weaker chosen plain text attack in distinguishability sense on a chosen cipher tax attacks But you don't only want to have a confian shallity, but also integrity Either for the plain text or the cipher text or the cipher text integrity would be the stronger notion And this forms roughly what we call authenticated encryption Now if we engage in a longer communication then the order of messages becomes relevant And that's where statefulness comes into the game So you can lift these notions to a stateful setting capturing both confidentiality as well as integrity under First stateful encryption schemes, and this then would be called stateful authenticated encryption and which was in particularly Used to analyze the SSH protocol and confirm its security back in 2002 however, a few years later in 2009 there was a plain text recovery attack Discovered against SSH where the basic idea is that an adversary can use the fragmentation of the underlying network in order to Inject into a SSH connection cipher tax in a fragmented in a block wise manner and by doing so in a very careful way Observing mac failures that occurred to due to modifications to the cipher tax This can be used to leak cipher the plain text which will actually be sent So this clearly constitutes a confidentiality break, but hey, I just said SSH was analyzed to be Stateful authenticated encryption schemes so confidential integrity protecting So what's going wrong here? Well, the main point is the attack is essentially relying on Crucially relying on the adversary being able to feed in cipher taxed in a fragmented in a block wise manner where these models capture only Decryption only in an atomic fashion for atomic cipher text So this is why coming back to the models a few years later in 2012 Well, the river de grabiella Patterson and Stam came up with a notion of symmetric encryption supporting fragmentation Which is essentially a generic a general security model which captures such cipher text fragmentation So on the encryption side everything stays as before you have a standard encryption algorithm According with an according left or right oracle for the security notions, but on the decryption side You now require that this decryption algorithm is able to Process cipher text in a fragmented way and still should be able to reassemble the original messages as they were sent then in this model the authors define according notions for confidentiality as The SSH attack was primarily on confident with a confidentiality attack The question is are we buried does this already cover all the practical attacks? one could have on secure channels The answer is no because there are further attacks in particular. There is the kubicator attack from last year on the TLS protocol The basic idea here is that in TLS an attacker is able to truncate a TLS connection by closing the under some underlying TCP connection and by doing though in a Yeah carefully He's actually able to chop off certain parts of transmitted messages And if you have an HTTP connection running or this attack was focused on is the cookie that is sent and by cutting off parts of that cookie You get security attacks on the actual communication So the bit more be a bit more precise here the cookie cutter example is the following when Alice and Bob Communicates Bob being the server and Alice authenticated and at some point Bob will probably send over to Alice an Authentication token to remember her and say please send this back to me when you're talking to me again So that I know you that's still Alice talking to me, but be aware. This is a secure security critical Cookie, so this is what this secure flag indicates. So in particular, please only send this back to me over a TLS connected TLS protected communication channel The cookie cutter attack in the simplest Representation just means now that an adversary is actually able to chop off this part of the cookie string And then Alice interpret this cookie as a standard cookie and happily sends it back to the to the web server Even over a non-protected communication and there the adversary can just grab the thing from the wire So way again, this basically means that the adversary is able to delete parts from within a cipher text So how can this be possible? To explain this let's have a closer look at how the quick cutter attack actually works So on the server side at some point the server will with encrypt its response Including this cookie and what we expect and would more than crypto is that there is a cipher text coming out of that So if you go one step closer to the implementation layer There will be some SSL library doing that job for example open SSL But that's not specific to open SSL and you will use some function of open SSL to encrypt or write data into a street into the channel Turns out route that for properties of TLS that I'll come to in a second This encryption might actually turn after it might be turned into two separate TLS records And if they are now sent over the the wire the adversary is able to truncate the connection at the right point Shopping off the second record product the record packet and Ellis will be left with a fragmented cookie and Miss may misinterpret that in a way that it's not a secure talk token anymore Many important more main important point here is that this fragmentation in TLS is actually implementation specific So any library might do that fragmentation up to certain boundaries in its own way And this means that an adversary is actually able to enforce this split potentially at any point of the message you send So the receiver will not see messages anymore, but fragments of messages With no clear message boundaries preserved Well, this might sound a bit strange. It's actually a behavior That's okay because the data send is a stream and that's what specified even in the TLS IRC so if you go there and look at to Fragmentation specification says that message boundaries are not preserved within TLS Records or TLS ciphertext, which means that either two messages might go into one record packet or a single message might be split up to Into several ciphertext So in the end the support is that TLS actually never promised you to treat message in an economic way And TLS is not alone in that sense There are more and other important channel protocols which do treat data as a stream without boundaries so there's SSH in tunnel mode, which does that and also the Quick protocol proposed by Google two years ago does treat data in a stream-based manner So what we have here now is then a gap between What the channel models we have capture atomic message sending and receive our time message receivable basically and The behavior that this channel in particular here TLS actually exposes to the application And this is why we came up with a notion of stream-based channels and a model for that Where the idea is well first of all what you receive on the sender side What the channel receives and supposed to process is a stream And it might get fragments of that stream in an arbitrary way Then we have a sending of you wish an encryption algorithm Which takes these fragments and converts them into some ciphertext fragments and again forming a stream Important point here is that this in particular allows for buffering So not on every column of the sending algorithm might lead into a ciphertext being or ciphertext fragment being output But there might be the sending algorithm buffer until you provide enough output and then to allow the application to say Okay, now I'm done with what I'm going to send. There's a specific flash lag that we allow for in the sending algorithm telling Now I'm done. Please make sure everything is out on the wire So then this constructed ciphertext stream will be transported over to the receiver side Where some lower layer transmission protocol for example TCP But as there might happen fragmentation Bob on the receiver side will potentially see a Differently fragmented representation of the very same stream as long as there's no modification And we now ask that the receiving decryption algorithm Is able to process this stream again in a fragmented in this fragmented way and Reconstruct the message stream that was sent. However, notice that We do not require that message boundaries are preserved. So as While you will see the same stream if nothing goes wrong The fragments that you will see on the receiver side Will potentially probably not coincide with the boundaries you had on the sender's calls So for correctness We acquire that whatever you receive is a prefix of what you send. So basically there's nothing else coming out and to capture what the The flushing flag should do is well everything that you put into the sender side up to the last Flushing call should also appear on the receiver side. So for security confidentiality we define Indistinguishability under chosen plain text fragment attacks. So we allow fragments on the sender side Basically in a very straightforward way using a left-to-right oracle, which is additionally well the additionally the adversary is able to control the flushing flag More delicate is the chosen cipher text case So the general idea to step back for a moment in chosen cipher text attack You want to allow as much decryption as possible while preventing trivial attacks so in the standard in the standard Stateful authenticated encryption setting the idea was to have this decryption or receiving oracle So the oracle simulating this receivable algorithm that oracle can be in singer out of sync where in sync means It's still receiving the correct the original cipher text or in our case the original cipher text stream And well, this is the challenge cipher text stream. So there should be no output given to the adversary However, as soon as the stream goes out of sync. So as soon as there is a deviation from the original output cipher text stream The output of the receivable algorithm should be given to the adversary The interesting and complicated question now is at which point exactly should this receiving Oracle be considered out of sync. So to consider again the work from 2012 and cipher text fragmentation The definition there is consider you have four fragments received And processed and the adversary Flipped starts flipping bit in the third fragment then This paper defines synchronization to be lost at the beginning of this third fragment the affected fragment Basically meaning that the first two out outputs of the first two fragments will be suppressed That's those challenge cipher text Whereas the second two outputs will be given to the adversary You know think back to the at the cookie cutter attack and this way that a message is potentially split up into a cipher text containing independent parts What you might end up with is that you get two independent parts here and you can modify the second part while still keeping the first one basically untouched So this means in this mobile The first part the first TLS record will be given out to the adversary But that's then challenge message bits So in that sense TLS in this fragmenting way would be considered insecure as it's leaking challenge message bits So the key insight for having a fragmented encryption algorithm as well Is that there is no inherent structure on a stream in particular the boundaries the cipher text fragment boundaries Do not have an implicit intricate meaning So that's why we define the receiving the decryption oracle as follows First of all for the in sync or already out of sync case everything is as before as long as you're still in sync The output is suppressed. That's definitely a challenge message part Challenge cipher text part. Sorry If you already have gone out of sync the full output will be given to the adversary The interesting part is now the fragment which contains the deviation So here we first we process both the only the genuine part and the full fragment using the receiving algorithm which will lead to two message outputs Then we know from correctness that on the genuine cipher text part by correctness There will be only genuine cipher message bits coming out So now we can compare the longest common prefix or check for the longest common prefix of this challenge message part and The full output on the actual fragment that the adversary wanted to have received And we know this part must be challenge message bits So we suppress this this part of the output and give the remaining output back to the adversary To in order to leak the the modified part of the cipher text fragment and for the TLS example, well the unmodified part would be still a common Long a common prefix whereas the scrambled part would go to the adversary Coming to the relations of the notions we define our work. Well, first of all the classic implication Sorry implication still hold so for confidentiality the chosen cipher text Security notion implies the chosen plain text security notion and for integrity which I don't have the time to define and show you here As well cipher text dream integrity implies integrity of plain text dream By the way, this is the first non-atomic treatment of integrity as the 2012 cipher text fragmentation work focused on confidentiality And then there is the classic composition result for Channel so that CPA confidentiality and cipher text integrity gives you the stronger cca confidentiality Here the idea is that basically whenever in the cca in the decryption oracle The out the L the adversary is able to make anything else than an error come out it breaks integrity So basically you can simulate this oracle by outputting the error Then in 2003 that's what sorry in 2013 the multi-error setting was Considered so what happens if you have more than one error that potentially is output and there you can resurrect the composition result By assuming that at most one of these errors is actually visible to the adversary and then you can still simulate the output in this one So we would like to have the composition result also in our setting meaning that we want to have chosen plain text fragment attack security Confiniality together with cipher text dream integrity give us the stronger chosen cipher text fragment confidentiality However in this stream-based setting we are inherently in a multi-error setting Because the receiving output might be buffering and we don't know whether on a deviating Part of the cipher text stream it will already give you an error or it will still give you nothing because it's buffering and Both of these will occur with non-negligible probability depending on your input. So what we do to Get the composition result in our work. So we require an additional property, which we call predictability of errors Basically says if you're given the send cipher text stream and the receive cipher text stream as well as the next fragment to Be processed you can predict the errors coming out Together with this we can resurrect the composition Well, this notion might sound intuitively a bit strong It's actually achievable in my natural constructions and I will now present you with a generic construction. We give you We give in our work This construction is based on AAD authenticated encryption with certain data so state less Version and achieves both the strong confidentiality and integrity notions And the basic idea of this construction is well if you receive a message stream The sending algorithm will chop up the messages into blocks of a certain length and as well keep a sequence number So the idea is up to a certain length you put these the message blocks or parts of the message stream Into a single a AD call using the sequence number as authenticated data And you put an unencrypted length field in front of the construction If you have to flush maybe this encryption will get less bits in this call And then on the receiving side because the length field you can you know How long you have to wait until you get the full a ad block for a certain part and the ad Security will basically tell you well as long as everything is fine You will get this message part coming out Otherwise the ad scheme will tell you hey there was an error. This is the error of the stream based channel as well in particular this scheme Satisfies this error predictability notion and we need use it to prove security Which basically Results from the length field being unencrypted. So in this way you can predict at which point the ad scheme will come to an error notion Interestingly more over this construction But it's kind of the natural construction you can think of of getting state for a stateful channel running It's actually pretty close to what TLS does in the record layer design if you're using an ad scheme as your encryption algorithm So first of all you as well have an unsent sequence number, which is authenticated as the associated data field You have a length field with us, which is sent but not authenticated at least that's the case in the latest TLS 1.3 version drafts However, it's not claiming. This is TLS. There are definitely differences the most important ones There are more fields for example in TLS particularly version number for example in the content field which allows kind of a multiplexing of data These are both for the record send and authenticated So to conclude data is a stream and we believe that we should treat as such a model is that such in our works for Formula lenses So we formalize what we the notion of stream based channels and come up with adequate notions That cover security in the setting more over we're able to reconstruct the composition theorem also in this world And then should you sketch of the ad base construction? We have which is relatively close to the TLS record layer design proving kind of a validation of that for the stream based setting and Well in the end this work constitutes kind of a formal light on how where the where recent attacks in particular the cookie cutter attacks stem from which is basically the application as well as the models capturing received messages as atomic whereas the Channel in that case TLS actually provides a streaming interface and never promised to give you back atomic messages from the receiver side So this work can be considered a start. There's still ongoing work particularly we explore the exact relation Between the atomic notions for channels and the stream based one we come up now There are additional properties that might be worthwhile to consider first of all length hiding is established notion for Authenticated encryption in the atomic setting Question is however what length hiding can or should mean on a stream And I said several protocols allow for multiplexing TLS is an example quick is a more prominent example where several data like message data streams go into the same Secure channel and in the end well if your application is happy to send a stream That's fine. But what if your application actually wants to transport over atomic messages? How can that safely probably secure be done on a stream? This concludes my talk. Thank you very much


This video's from a little bit ago, the Phillies were playing the Dodgers, they were up to nothing, but the Dodgers have two runners on in the fifth inning, trade turners up, they're threatening. A little behind the scenes. I make these videos, sometimes I edit a ton of them, and I feel like the timeliness is gone, and this one's been sitting on my timeline for a while, and in the past I usually just scrap these because I feel like I missed the moment, I missed the window. On some places that matters, on some it doesn't. YouTube doesn't seem to care, Facebook definitely doesn't care. On Twitter, there will always be people replying like, this is so long ago, blah, blah, blah. But I like making videos, and I edited it, so I'm just going to roll with it. We'll see how it goes. It's about the umpires, and it's a good one about the umps, I think. A lot of people suggested this. First pitch, that's a nice pitch, in there for a strike. Next pitch, swinging. 0-2 to Trey Turner, that's inside, and so inside the runner's advance, you don't want to do that, because now you can score a run on an out, 0-2 pitch, waste job, not great. Up the middle, Didi makes the play, backyard Brad with the snag, ump calls them out, but there's a reason this got suggested as often as it did. One, two big fan bases that request breakdowns a lot. Two, when they went to replay, it really looks like Brad comes off the base and does not catch that ball, and it's not an out. Looks like his foot gets pulled off once the ball's in the glove, and it kind of does, but it kind of doesn't. This guy's sweating it out, wondering what's going to happen. It's a big moment in the game, need to stay cool and smart, need to stay hydrated, smart. He's just drinking some water through his bald head. Brad's looking at the replay, everyone's looking up, the umps come back, and they say, yep, we got it right. He's out, and everyone's shocked in live time. The announcers for both teams don't understand what happened. It's hard for my eyes to go from, when does it touch the leather? I'll tell you when it's off. He's off. He's off now? Well, it's, yeah, he's off then, period. Yeah, how did, I don't get it. Yeah, no, he's off. I don't know what they didn't see. We'll take it. I don't know. He was off right there. Let's take a look at what I think the umpire saw in New York. So there's the ball in the glove, right? And now the ball doesn't have to hit the back pocket. It just needs to be in the webbing of the glove, which I always thought was really weird that they made the replay rule that because when you, when you're taught how to call out at first base, you stare at the base and you listen for the ball to hit the glove. And that's how you make the call listening to the ball hit the glove, watching the foot hit the base. And if you're listening for that, that means that we're counting it when the ball hits the glove, not when it just enters it. So I always was confused why they made it, but at this freeze frame, the ball is in the glove there. And then we slide over to his foot and I think they're going to say, that looks like it's still on the base to me. That looks like there is one frame where the ball's inside his glove. It hasn't hit the back of the glove yet and the foot's on the back.  But at this point, it's not unclear. The foot may be on the bag there. It looks like it is. And at that point, the ball is in his glove. Foot glove, foot glove, foot glove. We're dancing, we're dancing, we're dancing. So I think they got it right. I mean, in the spirit of the rule, the fact that replay is going frame by frame, I think the umps got it right, but this got requested a ton because both announcers were like, how'd they get that wrong? Maybe they didn't get it wrong. The rule's odd, but I think that rule, they got it right. Anyway, Dodgers got one run, but they ground out afterwards. That's the video. See you guys.


Hello everyone my name is Mariela and today I'm going to be showing you how to attach a regular stop loss to any of your trades. So clients have the option to attach either a regular trailing or a guaranteed stop loss order to any of their trades. However today we're going to be focusing solely on a regular stop loss order. If you are interested however please check out our other videos if you want to know how to place a trailing or a guaranteed stop loss order. So the target price of a stop loss order on an order ticket can be set by specifying a price, an approximate amount to lose or a number of points away from the price that the parent order is executed at. So once you've chosen your direction you're happy with your stake size and your stop loss. Confirm your order you'll get a confirmation here on the order ticket but you'll also be able to see that stop loss in your positions tab over here. If however you want to add a stop loss after you've placed your trade you can do that by going back into your positions tab, clicking on the stop loss section here and attaching it whilst the trade is already open the same way that we did before. So if you're happy with that amount you can press modify and that will then appear again in your positions tab down bottom here. So that's everything from me today. Again if you'd like any help please feel free to visit our live health section over here to the lab. Thank you.


Welcome. We're now going to go through the entire process of calculating a confidence interval by hand, and then we'll actually start using technology to create our confidence intervals for us. So the first step is to verify that the required assumptions are satisfied. And in order for us to be able to use the methods that we're about to use, the sample must be a simple random sample, the conditions for the binomial distribution must be satisfied, and the normal distribution can be used to approximate the distribution of sample proportions because there are at least five observations and then at least five non-observation. So for instance, if you're looking at M&Ms and you're looking at the proportion of M&Ms that are like brown, for instance, you must show that there are at least five brown M&Ms in your sample and at least five non-brown M&Ms in your sample. We don't focus too much on verifying the assumptions in this class. We learn more about the process and procedure. Step two is to find the critical value. Remember that's the data value whose area to the right is alpha over two. Alpha is the significance level, alpha is one minus the confidence level. And then you'll calculate the margin of error. Then step four, we'll take our sample proportion, our point estimate p hat, and we will literally subtract the error from it. We'll add the error to it, and then we will literally, that's our confidence interval. You have a lower bound, you have an upper bound, you're done. And make sure you round accordingly. So if it says round your confidence interval to two decimal places, make sure you round to two decimal places. So in the Twitter example, we noted that a poll of 1,007 randomly selected adults showed that 85% of respondents know what Twitter is. The sample results are a sample size n of 1,007 and a sample proportion p hat of 0.85. So that's going to be the starting point of our confidence interval p hat. The first thing they want you to do officially is to find the margin of error e that corresponds to a 95% confidence level. So there's a formula for margin of error. The margin of error is equal to your critical value, that's z sub alpha over two, times the square root of p hat times q hat over n. Alright, so for a 95% confidence level, the critical value is always 1.96. There's a shortcut table from the previous video you could use. Another way you could find the actual critical value is if you drew your bell curve, and you're trying to find the positive critical value, and you know that 95% is the center of your bell curve, which leaves 2.5% for each of your tails. So in order to find your critical value, you'd have to use technology where area to the left is 97.5%. In general, you can assume that a 95% confidence level has a critical value of 1.96. Alright, also we need to know, we got our square root, p hat is 0.85, what would q hat be? Well, q hat is actually 1 minus p hat, 1 minus 0.85, it's 0.15. One sample size n is 1,007. So what this ends up giving us is literally 1.96 times the square root of 0.0001266137. I'm scared to round until the final answer because even rounding the two decimal places or three or four might cause your error to be a little bit off, it might cause error in your error. Let's just say that. So if you take the square root of that long decimal, multiply it by 1.96, you will actually end up getting 0.0221. So that's going to be your error. If you ever have to give the margin of error, if a question asks you to find our margin of error, you must calculate the error by hand. The technology will not tell you the specific calculation, it'll tell you your confidence interval, but it won't break it down and tell you what the error is. So now find the 95% confidence interval estimate of the population proportion p. So literally we're going to take p hat and we're going to add and subtract the error from it.  When you subtract those two values you'll actually get 0.8279, then you take your sample proportion and you add the error to it, 0.85 plus 0.0221 and that's going to give you 0.8721. So this confidence interval will be lower bound 0.8279 is less than p is less than 0.8721. You could also write it in parentheses with the two values separated by a comma. So one's inequality form, the other's interval notation form. So that's how you actually create or calculate a confidence interval by hand. And that's telling me that the true proportion is between 0.8279 and 0.8721 with 95% confidence. So based on the results can we safely conclude that more than 75% of adults know what Twitter is? And the answer to that would be well since our interval was 0.8279 all the way through 0.8721 we can say yes and that's because the true proportion is between 0.8279 and 0.8721. And so that's basically 82.79% and 87.21% just as a FYI there which is way more than 75%. So now assuming you're a newspaper reporter write a brief statement that accurately describes the results and includes all the relevant information. So in order to describe a confidence interval in words we use the following format. We say with 95% confidence so we state our confidence level the proportion and in this case we're talking about the proportion of adults who know what Twitter is. It's between 0.8279 and 0.8721 you literally list your values. That's always the structure for writing your confidence interval statement. If you write a confidence interval you must write out the description. The two go hand in hand. So now let's look at technology. So I'm not going to read this to you I'd rather just show you on the next page but it's literally as easy as typing in three pieces of information into the Google Sheets spreadsheet. So the colors from a sample of 100 M&Ms because who doesn't like M&Ms? Yeah I know some of you don't but a lot of you do. We collected a sample of 100 M&Ms and 8% of them were brown. Use the sample data to construct a 98% confidence interval estimate of the proportion of brown M&Ms. And Mars candy claims that 13% of its M&Ms are brown so is this claimed rate wrong? So all we have to do is write down three pieces of information. We're talking about brown M&Ms now. So the first thing I need and this is for Google Sheets we're going to go to a tab that's called the data list tab and we're going to go to the region that's called 1 prop ci p value. It just means you're finding the confidence interval for one proportion. And the first thing you're going to put is your number of observations remember we're talking brown M&Ms. You want the discrete number of observations. How many M&Ms were brown? Well it said 8% but we need an actual count. Well number of observations is out of the 100 M&Ms 8% or .08 or brown. So that's 8 that's going to be X on your spreadsheet. Your sample size in is 100 and then your confidence level is the only other information you need it's .98 or you could literally type 98 with the percent sign it'll recognize it as a percentage. So let's type these three values into the Google Sheets spreadsheet. So we're going to go to the data list tab we're going to focus for proportions one proportion confidence interval p value and you type in a value for X. So there are 8 M&Ms that were brown. You're going to type in your sample size in which is 100 the only other thing you need to do for a confidence interval is put your confidence level 0.98. So I have 8, 100 and I have 0.98 don't worry about any of the other information you just need to focus on the confidence interval lower bound and confidence interval upper bound. Those are the two things that you need from the spreadsheet the rest will come later on so let's do three decimal places 0.01 the six rounds to a seven because there's an 8 in the following place and then 0.143. So that is our confidence interval 0.017 0.143. So that's anywhere from 1.7% to 14.3%. So is Mars's claimed rate wrong? Well I would say I would say that since 13% is in the interval. 13% is literally 0.13. The claimed rate is not necessarily wrong. The claimed rate is not necessarily wrong because 13% lies in that interval there. So the only other thing we need to do here is write out the one sentence interpretation of our confidence interval itself and that interpretation is with 98% confidence the true proportion of M&M's that are brown is between 0.017 and 0.143. There's one more thing we're going to do here and that's determining sample size. Sometimes you need to make sure you determine the correct sample size to use to estimate a population proportion because you can't just go out and randomly pick a certain number of people if there's certain quality or certain things or requirements that must be met by your boss or by the company that's contracted you out to do these calculations you need to make sure you use the appropriate sample size to meet those requirements. So solving for N in the margin of error formula gives the following two formulas for determining sample size. So the desired sample size will be the critical value squared times p hat times q hat over the error bound squared and that's when you have an estimate of p hat. If you don't have an estimate of p hat you still square the critical value but you then multiply it by 0.25 and the reason why is if you don't know anything about p hat which means you don't know anything about q hat what's 0.5 times 0.5 that's 0.25 that's where that comes from and then you still divide by the error bound if the computed sample size is not a whole number you will round up because if you need to have a sample size of 40.2 40 is not going to make the cut you have to bump it up to 41. So many companies are interested in knowing the percentage of adults who buy clothing online. How many adults must be surveyed in order to be 95% confident that the sample percentage is an error by no more than three percentage points and we're going to use a recent result from the Census Bureau that 66% of adults buy clothing online. So the important thing here is we're using a 95% confidence level which means instantly that our critical value for a 95% confidence level is always 1.96. All right p hat our point estimate here is going to be 0.66 that's our sample proportion what about q hat well it's one minus 0.66 so that's 0.34 and what else do we have to know we need to know that error they said they want the error to be no more than three percentage points so that means the error e would equal 0.03 3% would be 0.03 now all you have to do is plug and chug so you have 1.96 squared times 0.66 times 0.34 over 0.03 squared it's up to you to do this calculation use a calculator but on top I got 0.86205504 and on the bottom I got 0.0009 so you divide these two things and you get 957.8 for the necessary sample size although it would anyway remember you must always round up and you need a sample size of 958 people and that's in order to meet those requirements and to have that certain error bound so that's pretty cool well now let's assume we have no prior information suggesting a possible value of the proportion so we have to use the formula where p hat times q hat to replace with 0.25 it's still the same confidence level so it's still the same critical value of 1.96 and it's still the same error of no more than 3% so even though we have less information here formulas actually a little bit easier which is pretty awesome if you ask me so the critical value squared times 0.25 over 0.03 squared so you perform this calculation you get 0.9604 divided by 0.0009 and you're going to get 1067.1 so if you go out and ask 1067 people that's not enough remember you must always round up for this sample size always round up so that's actually going to give you 1068 people so notice that in part a of this question we only needed 958 in part b we needed 1068 so notice the fact that just by knowing some prior evidence of the sample proportion it saved us from having having to ask around 100 people about so anyway that's all I have for now thanks for watching