Okay, I see it's 6.30. So I would like to convene this special meeting of the Board of Directors of the San Lorenzo Valley Water District on March 11, 2021. Holly, would you call the roll please? President Maygood. Here. Vice President Henry. Here. Director Pulse. Here. Director Smalley. Here. And Director Tu is absent. She did contact both the president and myself to say she would not be available this evening. And so we need to take a vote on whether to excuse this absence. Is that correct? Yes. Yes, that's correct. Let's just make that a voice vote. All in favor of excusing Director Tu's absence today say aye. Aye. All in favor. Abstain. Okay. Director Tu's absence tonight is an excused one. All right. Are there any additions or deletions to the agenda tonight? Staff has none. Okay. Any from other members of the board doesn't look like it. Okay. So now we go to oral communications which is the portion of the agenda that's reserved for oral communications public on subjects that lie out, lie within the jurisdiction of the district but are not on the agenda tonight. If you would like to address the board, please hit the raise hand button. Let's see. I don't see any raised hands. So I guess we don't have any oral communications this evening. So let's go ahead to our new business and the only business tonight which is a discussion of reviewing and discussing notice of petitions that were filed by the city of Santa Cruz that change their water rights. And I'd like to give you just a little bit of context for this. I first learned about these changes when I looked at the packet that was the backup material for the February meeting of the Santa Margarita groundwater basin. And I noticed that the new modeling showed that we had only about half as much water available for in lieu recharges we did before, which surprised me. So I went and tried to find out why and it turned out because of some of the changes that were in accord with these petitions that have gone to the state water board. I read them and had a couple of concerns and then Mark Smalley, my other compatriot on the Santa Margarita Groundwater Association also had some concerns. And so he raised it at our last board meeting and we had learned that in fact, Carly and Gina and Rick had been working on this issue. And we thought it was important to discuss it here at a board meeting. Director Foltz asked us to agendize it because any protest letter has to be submitted by tomorrow. We had to have a special meeting and that emphasizes that tonight is just for information only. There will be no action taken. We won't be voting on the letter. The letter has already gone out to the board for any comments. So it will be sent in tomorrow by the deadline but we wanted all members of the board to have an opportunity to understand what is being done here and also so the public can be informed as well. And Rosemary Bernard who is Rick Rogers counterpart at the city of Santa Cruz is with us tonight. She's not here to speak or anything but she's just here in case anybody has a question that they want to direct towards her. So with that, I'll turn it over to Rick. Thank you, Chair. As we start, we have a short presentation that we'll put up. You're going to be hearing us discussing and referring to several water supply facilities, mostly pertaining to Santa Cruz, Santa Cruz water. And we thought it would be a good idea to start this presentation with some mapping to kind of give folks some ideas where these facilities are located. And if we can pull the PowerPoint up, that would be great. I'm sorry, I haven't received the PowerPoint. Carly, do you want to share your screen? I'm not sure. I think Holly, could you share? I think we share Holly's screen or maybe you can't do it. But I think Holly has the current presentation. Okay. No, I have not seen the presentation. I actually saw earlier a little flash that said Becca Reed sharing her screen. So she should be able to do it. Hello, this is me. I'm on Becca's account for CTV, but I haven't received the presentation for today. I can pull it up. Do you want to pull it up? Yeah, I can pull it up. Great. My apologies. That's okay. It'll take me just a moment and I'll have it. That's all right. While you're doing that, just let me add one more little comment. And that is that the petitions that are being put in by the city of Santa Cruz are a large change to the places that are able to use the water. Some changes in where water would be diverted and also changes in the use. And this is actually an effort that city of Santa Cruz has been engaged in for quite a long time. And we're also engaged in our set of similar sorts of changes, which are probably only a half a year behind at most. So there's not anything bad about this. This is good. We all should be revising our water rights to be consistent with new needs as we have to sort of eventually start to think about water in a more regional way. And so both Mark and I just found two little things that we were sort of concerned about. And that's what we're exploring here. We're not actually in any way opposed to city of Santa Cruz changing where they're using it because this is just modernizing things. Okay, I'm gonna hit screen share now and let's see if this works. All right, next slide please, Gina or whoever. No, hold on, it's a technical issue here. Can you see it? Yeah, I see screen one, slide one, yes. Okay, great. Now we're seeing the other ones. Hopefully you can see this map. We're gonna be talking tonight about the Loch Lomond Reservoir. We're gonna be talking about the Felton Diversion which the Felton Diversion is located on the San Lorenzo River adjacent to Henry Cal Park right across the street from George's log cabin. We're gonna be talking about the Big Trees Gauge which is located underneath the entrance bridge to Henry Cal State Park in the San Lorenzo River. We'll be talking about the Tate Street Diversion in Santa Cruz. What's not on this map, we'll be talking about the San Lorenzo Valley Water Districts Fall Creek Diversion, which is located at the end of Fall Creek Road adjacent close to the proximity of the San Lorenzo Valley Felton High School. We'll be talking about the Santa Cruz's Belts Wells in Santa Cruz. So we're gonna be talking about a variety of locations spread out through the San Lorenzo Valley and the city of Santa Cruz. And with that, I will turn over, we have one more slide that has a little better mapping that the show the Felton Diversion, the city of Santa Cruz, the service area, et cetera. And with that, I will turn the presentation over to a district legal counsel, Gina Nichols, to proceed with the presentation. And I guess I'll leave it here on the map for a moment. Well, I do some, make some introductory comments and you may or may not know that I'm not only the district's general counsel, but I'm also a water rights attorney. That's kind of the primary area of practice that I focus on. So these are the types of issues that I work on in addition to general counsel type matters. And here, by way of a little bit of background, as I understand it, the city of Santa Cruz's petitions for changes to their water rights have been in the works for more than a decade now. What has prompted this latest effort is that on about February 10th, the district received formal notice of the city's change petitions. So there have been a lot of prior iterations of the change petitions, but public notice was formally given in February. And when that happened, of course, the district staff took a look at the actual notice of the change petitions and the underlying petitions, which are now in presumably their final form or near final form. And they asked me as district legal counsel and water rights counsel to take a look as well as some technical consultants who work with the district. So we reviewed the notice and the underlying petitions and working together identified a couple of areas of concern for the district. And again, echoing Chair Mayhoed's comments. These aren't broad concerns about the city's proposed changes to their water rights. These are specific concerns as to issues that appear to have an impact on the district and its customers. So the two issues that we identify that are the subject of the draft protest that you see in the board packet are these. First, there's potential implications for the district's contracts, contractual rights to obtain water from the city's locker room and reservoir. And that arises because some of the conditions that had been proposed in the city's petitions would, well, they require certain minimum flows, but more importantly, they appear as they are written to prevent the city from providing lock loman water to any water supplier other than the city itself during certain drought conditions that are defined in tables through the petition. So, of course, we took a look at that and there's no way to know exactly how often those drought conditions that would restrict delivery of the water to San Lorenzo Valley Water District may be triggered. I mean, you might be able to estimate that but there's no way to know for sure. But what we do know is that the district is most likely to need the water when the water supplies are most scarce. And so it would be a concern if the district couldn't call upon that water during drought conditions. So that's the first issue we identified in the protest letter. The second one is a little more complex and it has to do with the proposed stream flow requirements for the city's water rights. And these, we pulled out kind of the key tables from the petitions themselves and included them in the board packet for anybody who wants to look at them. But in a nutshell, the issue here is that the city's petitions are proposing a table of minimum stream flows for the San Lorenzo River at Big Tree's Gage that wouldn't allow any diversions during three months during the summer and would have a 40 CFS minimum flow in the river for I believe six months of the year. And that minimum flow requirement is higher as I understand it than anything the district has seen in the past. And the district itself has water rights permits for the Fall Creek area of Felton that have stream flow requirements measured at that same point at the Big Tree's Gage that do not approach the 40 CFS in stream flow requirement. So this is kind of a tricky issue but the concern is that the city has worked out these minimum stream flow conditions with some of the resource agencies and that are now proposing to approve them with the state board. And the district hasn't really been involved in that process. The district is undertaking its own process to review its water rights. But there may and there may be a lot of assumptions built into those stream flows that the district hasn't really had a chance to examine or consider as they may be applied in the future to the district's water rights. So we're simply raising the issue that whatever new proposed stream flow requirements that are for the city's permits at Felton need to be harmonized in some way with the district's rights and what the district plans to do with its rights. And exactly how to accomplish that isn't entirely clear at this point. There's a number of different ways that that may be accomplished. But what we're doing by filing this protest is taking the first step to make sure that the district is taking a close look at this issue in conjunction with the city and the resource agencies to try to make sure that the district is involved in this process and doesn't kind of get left behind. So here for the last slide, we have kind of a flow chart that shows the effect of this protest letter. So I've outlined the two issues that the district has raised in the draft protest letter and the attached protest. And this flow chart indicates what that means for the water rights petition process. Essentially where we're at is kind of in the middle of the flow chart, excuse me, public notice has been issued of, as I said, you know, the notice we got on February 10th here in the middle of the slide. That's the public notice of the proposed changes to the city's water rights that we received about a month ago. What you have in your packet is a draft protest that the district plans to submit tomorrow. And so the next step is you kind of go down the flow chart is protest negotiations and division review. So there's a number of different things that could happen here. We could work with other parties to resolve the protest. The protest could be canceled or revoked in some way or we could end up going to a hearing over some of the issues raised in the protest. And there's a lot of variables before we get to one of those outcomes. But at this stage, what we're just trying to do is make sure that we're looking out for the district's water rights, its customers and the ability to serve water and meet the needs of the public a little bit upstream of the city's water rights in the San Lorenzo Valley. And Rick, did I have I missed anything that you think I should cover in this part of the presentation? No, I think you've covered it pretty well. The city has been working on this process. I think for about 15, 14, 15 years, it's been a long process. So with that, we will take questions from the board and at the board's discretion from the public. Okay. Director Faltz, do you have any questions you'd like to? I do. I wanna start out by saying though that at least I think this is the case. Rick, for at least several months out of the year, are we not already in violation of our Hilton water rights at the big trees measuring gauge? We are in violation from time to time, not all the time, but there are certain times that we are in violation. And keep in mind the Feltin water rights, under the Feltin water rights, Feltin is its own individual water system. And by permit, we are not allowed to remove that water from Feltin. So we are at times, yes. I understand that. And so the meta question for me is unless Santa Cruz is going to be releasing greater flows out of Loch Lomond, I don't see how we can possibly address a higher requirement at the big trees measuring gauge than what we currently have. We're gonna be out of spec even more. So this is deeply troubling that that would be, that that would be negotiated. Just a couple of other sort of meta questions. Bob, would you, I would just like to follow up on your question and just clarify something with Rick. Are we out of specs in terms of the measurements at the big trees gauge? Or I thought we were out of the rules in terms of the amount of water we're bypassing at the fish ladder. Well, it ties into the big trees gauge. Okay. So at certain times of the year, we can't make the requirement of our discharge with the big trees requirements that we have now. So my understanding is generally speaking, we're okay on fall creek bypass, but certain times of the year and certain years where it's drier, we're not okay at the big trees measuring. That's correct. And generally speaking, obviously Gail, we'd have to look at the- No, thank you for clarifying that. So Rick, I understand that we extract about a thousand acre feet a year from surface sources on average. It varies from year to year. What is the total volume of water that goes out the San Lorenzo River Mount? Do we know what that is? I don't have those numbers in front of me, Bob. We know what they are, but I don't have them in front of me. And in terms of Santa Cruz's petition, how much are they able to take out now and what are they going to? Is that an increase or is that a decrease? I do believe it's a decrease, but again, I don't have those numbers in front of me. Okay, but I mean, the numbers I saw in the petitions I thought added up to something around 6,000 and 7,000 acre feet. And so it's substantially more than we're taking out. And it would be, again, I tie it back to this flow requirement. You know, we're taking out a fraction of what they're taking out. And yet somehow there might be a need for us to reduce surface water use more. That just doesn't seem fair. Am I correct in thinking that, Rosemary, maybe you can clarify this, that there is no change in the total amount of water being removed, 3,000 acre feet per year, which in fact, that's the limit that the existing and the new petitions have. Is that correct? The 3,000 acre feet is the amount of the Belt and Permits. So the city has water rights in several places on the San Lorenzo River. One is the Tate Street Divergence is about 12.2 CFS. And then the Belt and Permits, which are time limited to winter time only use. One has September one to April 30th. I think the other one has October one to April 30th. Those are permits that are not fully licensed or they're not fully, you know, perfected. So we've used, we've demonstrated over time about use of about half of that. We're not asking for additional water there. We are asking for a time extension to be able to use that water over time. And then of course we have the dual creek rights that really affect that upper part of the system and there's a fish flow release from that facility that's been in place since the dam was built in 1960. So the request is not for more water. It is for a different flexibility for the where we might take the water, mostly lower in the system, as opposed to further up in the system. And we are integrating into the request a whole fairly complicated regime of water rights or flow improvements by past laws. Yeah, okay, but just let me clarify, so far you have not been using, in other words, did you just say we've not been, you have not been using the 3000 that you potentially could take out. You've been, what did you say about 1500? About 1700, yeah. But not really on a routine basis because the current provisions for the Belton permits, I'm sorry if we're going into a rabbit hole and you don't wanna go here. So just say stop if you don't want to. But the current provisions for the Belton permit are a diversion to storage in Loch Lomond. Which is one of the reasons they haven't been used very often because when Loch Lomond is full, you don't need to divert water. And when it's not full, as is the case for example, this year, there's often not water to divert that would allow you to meet a bypass flow even that the 20 CFS that existed. Thank you. I think what we're just trying to get clear here is that you could end up taking more water out of the river than you have been even under staying with not asking for more technically. Well, I think it's really important to know that the commitment we're making to the bypass flows is quite substantial. So the answer to that question about are we gonna be taking more is actually probably no because we might be using a different right but we're actually leaving a very significant amount of water in the system for stream flows. Okay, thank you. Bob, did you wanna follow up? Yeah, I guess I'm just, I'm really confused here. So when I look at the permits, I do see the 3000, which is sort of bundled on I think a couple of the permits. And then I see the diversion for Newell Creek, which is 3620. Now again, I understand you may not be taking it every year just as we vary in our take out of the surface water sources as well. So I'm trying to get an idea of what is your map or 3200, what is your maximum draw that you can take every year? Actually, this one here says 5600 acre feet per annum max diversion to storage at Loch Lomond. Maximum withdrawal not to exceed 3200 acre feet, maximum amount stored 8624. So, sort of worst case, that's where I came up with the 6,000 to 7,000 acre feet that potentially could be extracted from the river. So that's sort of one thing is just understanding where we are now and what you're proposing to be your maximum. And then the second part is I still don't understand how if we're not meeting our flow requirements of big trees now, all the time consistently, how we're possibly gonna be able to do that going forward if those flow requirements are increasing unless your district or your department is going to substantially increase the flow out of Loch Lomond in order to get up to that 40 CFM. That is how much are we going to have to contribute to that beyond what we're already contributing to it? Let's, I think the point is made. Let's go on and go to Director Henry. Okay, Rosemary's saying there's going to be more water in the river. And that's if they increase the flow to 40 and right now is it 20 to 25? Did you want me to answer? Let's go ahead Rosemary. Thank you. So the current bypass flow requirement at the Felton's version, the big trees gauge which is sort of for us the Felton's version is a 20 CFS bypass flow. We can't operate that facility at all unless there's 20 CFS going by that site. The proposal is to increase it to 40 CFS not because we, you know, want to but because that's the quantity of water needed to support the upstream passage of salmonids such steelhead and coho and the downstream passage during the sort of winter and the spring and fall when they're coming up into the freshwater system to support the passage in the reach between the Felton's version or the big trees gauge and the lower part of the river. So I think it's extremely important to realize that that flow is driven by a biological need that the fish have. Okay. And as I mentioned, the current requirement is 20 CFS it's been that way for quite a long time and we cannot operate that facility unless the flow in the system is 20 CFS or greater and it will increase to 40 CFS. Okay. And thank you. How, then how is that going to affect us in San Lorenzo? Like taking water out of any of the streams that go into the San Lorenzo River is that gonna, are they gonna think about changing our requirements from 20 to 40? I know you don't have a crystal ball but maybe you can tell me what you think about that. Well, I think the real issue is as sort of a little bit discussed at the Santa Margarita meeting a couple of weeks ago, I guess now is whether the current control point on your system is the right control point for the management of your rights and it may not be. And I know that's one of the things that is being discussed in your consideration of how you might ask for changes to your water right. And I don't have a problem with separating those things in the event that that's the right thing to do that works for you and doesn't result in basically having what you're gonna do to make negative impacts on what the city is trying to do. So there's a sort of a two-sting. I don't wanna affect you and I don't want you to affect me, right? So trying to figure that out, I think is the place where your attorney and Rick and I and others have been talking about this for a while but you've been as noted on your own path to look at how your water rights need to operate. Carly, you're sort of shaking your head as if maybe you have some ideas about what would be a more appropriate place to take that benchmark. Did you wanna comment on that? Right, right now we are having those discussions with NIMS and soon to be CDFW. So that is up and coming and we will be determining those by-pass flows for our system. And like Rosemary saying, we will have to consider what those effects will be on their rights as well as a downstream user. So that is up and coming in our own system. Okay, Lois, did you wanna add anything? No, I don't really have any more questions. Director Smalley? Yes, I also have a concern that the 40 CFS flow may affect our rights to what we can take out the Fall Creek diversion. But I think that the letter, the draft letter that we've seen that Gene has provided to us addresses that as best we can at this point. I would hope that the State Water Research Control Board takes that letter and the accompanying protest application into account before they make changes. And I would hope that they engage the district in these discussions, but we can't at this point tell the State Board what they should be doing. So I don't have any further questions. I think the letter is good and it has addressed my previous ones. I would just echo that and add that one of the things about the bypass flows, which is sort of the 40 CFS is it's a little bit ambiguously stated in the petition. As footnotes, it refers to the fact that you need the 40 CFS only under certain circumstances in terms of whether the fish are migrating or not. And yet it looks like it's being applied across the entire six months. And I think that would make a big difference to us whether it actually should be just applied during certain times when the fish are migrating or spawning or whatever and who determines when those time periods happen. And so that may be something that needs to also be worked out. Director Fultz? Yes, thanks. I just had one other comment. I am concerned about our felt and permit obviously in terms of the bypass flow requirements there, but I'm also concerned about whether or not this might potentially impact our other surface of water sources. That is if there's some sense that in order to achieve 40 CFS, we're going to have to not use as much surface water, and from all of our sources, not just Felton, but the rest have been Loma Mountain sources. That's a serious strategic concern. I mean, on the one hand, we have ground water loss saying don't use ground water. And on the other hand, we have sort of this doubling of the bypass requirement there that makes me concerned, are we being told don't use surface water? And so then I understand the fish requirements, but I also understand the people requirements and our ability to serve our people. And this, that doubling seems, especially given that we aren't meeting it now, just seems like we have a very large potential issue here with our ability to use surface water. If this is really past the way that it is, I'm deeply concerned. But the letter is good. And hopefully they'll pay attention. Okay. Are there any other questions from the board? If I'll go ahead and see if there are any questions from the public in the audience. If you have any questions or comments, please go ahead and raise your hand. Cynthia Zenzel, can we unmute Cynthia? Go ahead, Cynthia. Thank you. I'm concerned because I heard Perrette Harman say at a meeting of her ratepayers that they were in a better situation than us because they depend on groundwater, not on surface water and that they could simply deplete the basin during drought years, whereas we would simply be out of water because we wouldn't have rainfall. And I am concerned in hearing this discussion if we are going to be limited, if we're going to be expected to make up for the lack of flow in the river by decreasing our use of surface water rather than city of Santa Cruz being required to allow more releases of water from Loch Lomond, then we will be in a very precarious position. And I'm wondering whether any of the water that's going to be used from Loch Lomond is going to be diverted from the Santa Margarita aquifer or whether it will be used to recharge the Santa Margarita aquifer. Thank you. Rosemary, did you want to respond to that? I can't speak to what you might plan to do with the Loch Lomond water that is in your allocation. The city has a very sort of well articulated problem statement related to what it needs to do for its drought supply, which we're looking for places to put either Loch Lomond water or surface water in the wintertime when it's available in the local aquifers, but we would want to be getting a fairly good sized chunk of it back. I think the other issue has to do with the reality of when the crunch is on in most cases in the system, the Santa Margarita system is in the dry season, notwithstanding having a dry winter, typically there's enough flow in the system through even the dry winter conditions to meet needs. It's in that period of about, you know, April through the end of October that the problem exists here. And really because that's not a time when we can take water out of the Felton system in any case, we're not required to produce 60 CFS all of the time if the natural flow conditions in the river are not being affected by withdrawals are lower than 40 CFS, then that's the way it is. But it's kind of in that timeframe when additional flows would be being taken in the winter season that that's probably most constraining. I don't know if that helps to elucidate some nuances here or if it makes things worse for confusion. Well, I'm not sure if you quite answered Cynthia's question or at least what I thought her question was, which is, is any of this water that is being removed from Locke-Lomond or taken from the San Lorenzo River going to be put back into the watershed of the San Lorenzo River or into the Santa Margarita groundwater basin by injecting it into, for example, the Lompeco formation or I think one thing that immediately struck me when I read the petition was all this water was being taken out and being put into the wells, the belts wells, which are not within your service area and are not within the watershed. And so that, I mean, it might be legal for you guys to do that, but it kind of breaks my heart. So I guess I think that's kind of what Cynthia was getting at is any of this water going to be used in such a way that it will help with our groundwater sustainability plan. Right, okay. A couple of things is the answer to that question is, if possible, yes. And we have from the 2014, 2015 Water Supply Advisory Committee process recommendations to use aquifer storage and recovery in both basins to create a groundwater supply that would be a supplemental supply for Santa Cruz during droughts, but also to contribute to the restoration and the sustainable management of the basins, if possible. And I want to comment that the belts well-filled in the Mid County Basin is in our service area. The customers over there all the way to 41st are our customers, we do use that system now. I will tell you from four years of work, five years of work on looking at aquifer storage and recovery and understanding the nature of these aquifers, there do seem to be some opportunities, but there also are some challenges and constraints. So the answer to, is any of the water going to go into the Santa Margarita Basin that we might take to the extent that we can create a drought supply that works for Santa Cruz and that makes contributions to the sustainability of the basin, that would be something we would want to do. So it's not an either or in our case, but the system has to function in a way that water doesn't just go into the basin, it also can come out of the basin in circumstances where our storage is inadequate to meet our long-term supply. Thank you. Are there any other questions or comments by members of the public? Let's see, I don't see any. With that, I'll go back and see if there's any from the board. Director Fultz. Yeah, just one of the things I wanted to point out, I know we all know this, but it's important to, I think, talk about it. The Santa Runs Valley Water District customers have done an outstanding job in reducing their water use, not just during drought times, but even now. We are about 20% below the state's long-term goal of 50 gallons per user per day indoor use. And I would really not like to, that is something I think that a lot of districts around the state wish they could be at. It would be really great if that were recognized by the folks that are making decisions on this so that our continued conjunctive use of surface water and groundwater, what we've been doing for decades, well in advance of anybody else, can continue the way that it has been. We've shown ourselves to be responsible in our use of water. We've shown ourselves to be aggressive in how we reduce that use of water. Let's make sure that gets recognized and rewarded. Thank you. Any more comments or questions from the board? If not, does anybody on the staff wanna pipe in and say anything at this point? No? Thank you, everybody, our attendance tonight. It was a special meeting and a little short notice. Thank Rosemary for attending and working with the district on this issue over the last week. I appreciate everybody's time. Great, yes. Thank you again, Rosemary, for coming and answering our questions. I think it was really helpful. Happy to. With that, I think that was all our only item of business and so we can go ahead and adjourn, okay? All right, good night, everyone. Good night, everybody.


Hi guys, this is Dr. Ahmet Ergin. I'm an endocrinologist and a diabetes education specialist. Today we are going to talk about 10 ways to reduce your blood pressure. Now in our previous video if you missed it you can go to the description below at the end of this video to find out what is causing the high blood pressure to begin with. But today we are talking about how can you reduce your blood pressure. As we discussed in the previous video every 20 over 10 blood pressure elevation will double your risk of heart attack and stroke. So it is as important as blood sugar control. So you have diabetes or not, blood pressure control is essential. Now I am kind of in a feeling that you may be looking for a magic solution but there is none.  Hopefully. Let's get started. Okay, so number one we have to lose weight. So why? So you're like easier said than done, right? Yeah, it is. But when you have extra weight in your body unfortunately those fat cells screed a lot of inflammation. They screed a lot of angiotensin. They screed interleukins. They screed fatty acids. All result in drive of the blood pressure high through kidneys, through damaged endothelial cells, etc. etc.  And as a simple terms, you know, if your heart is trying to pump more blood you can realize that that's gonna need more pressure. So that's number one. Now, how do you lose weight? That's a different story. We have videos about intermittent fasting. We have videos about calorie control, etc. But that's number one. Number two. Yeah, it kind of sounds cliche, but exercise. Exercise has similar benefits to intermittent fasting or for you guys who are doing keto that also has similar benefits where you are basically reducing, shrinking your fat cells.  Exercise will reduce your blood pressure. What else exercise will do? When you exercise, your body screeds something called the nitric oxide. Your endothelial cells, your vascular system screeds that nitric oxide. That's a vasodilator, which means that your blood vessels will dilate the venue exercise. If you do this regularly, which is 30 minutes every day, five days a week at least. If you do that, your body will continue to secrete that hormone and it will allow your blood vessels to dilate open up so that the blood pressure is not going to raise the rise. So that's number two. Number three. Very, very important. Extremely important. Reducing the salt content in your food. Now the easiest way to do that is stop eating canned foods. Stop eating TV dinners. Stop eating frozen stuff that is processed. You know, I'm not talking about frozen peas or something that's not processed, but if it is made into a meal, if it is put in a can to try to protect it and preserve the life of the thing, they use a lot of salt. And you may not think that you are using salt, but they are highly saturated with salt in order to preserve the life of the product. So always eat fresh fruit, vegetables and meat. That will be your best bet. Always eat fresh and real food. And also, remember how much salt you should really get in your diet is recommended that you go below 1500 milligrams. If that's not possible, I will say 2300 milligrams. Now, how do you measure the milligrams? So well, one teaspoon of salt is equal to 2300 milligrams. So just one teaspoon of salt can put you over the limit. In this case, you need to make sure that your food does not come with salt to begin with, and you should never add salt to any food. And moreover, if you look at the labels of the foods that you purchase, hopefully it will not have a lot of salt, but you can tell how much salt is in their proportion and you can have an idea about how much salt you're getting. Another problem with salt, if you continue to eat salt, you will not get the benefit from medications. Even the medications will be difficult to work, although you may be on 2, 3, 4, 5 blood pressure medications and your blood pressure may still be resistant to go down. Number four, increase the potassium in your diet. So if you have more potassium in your diet, your body will screed and get rid of the sodium. So where does the potassium comes from vegetables and fruits? When you're in a keto diet, that may be a difficult to achieve, but even when you're in a keto diet or any other low carb diet, I would strongly recommend to have high potassium in your diet. Again, that comes from vegetables and fruits. You can go with the low carbohydrate vegetables and fruits, which we have videos about. Definitely check them out as well. Number five, number five is limit the alcohol.  But when you do it excessively, it will definitely cause the opposite and it will cause high blood pressure and it will cause insulin resistance as well. Now, smoking is the number six. You got to stop smoking. Smoking definitely kills your endothelium. We discussed about this before. Your blood pressures will be destroyed, will be stiff. When your veins and arteries are stiff, your blood pressure will continue to rise, no matter what you do. So you have to quit smoking today. It's easier said than done, but yes, you got to do it. Number seven, you can cut back on the caffeine. Caffeine is definitely something that can raise blood pressure in some people, not always. It's interesting that it can raise your blood sugar as well. That's another problem. But if you're a regular coffee drinker, you may not see that problem as much, but you can test it yourself.  Number eight is reduce your stress. So if you are a type A personality always stressed out about different things, it could be your family, it could be the money, it could be the life, health, whatever it may be. The more you stress yourself about things, the more stress hormones you will make. And those stress hormones, unfortunately, will definitely put a toll on you. All this adrenaline discharge, all the sympathetic nervous system activation will definitely keep your blood pressure high. And you will have to pay for the consequences. Unfortunately, number nine is, like we said, monitor your blood pressure regularly. Now, your blood pressure will change during the day. It may be high, higher in the morning in some cases, or sometimes it goes high in the afternoon. When you first start to get blood pressure, your blood pressure will be a little mobiles. It's going to be going up and down labile. So basically that's your way of understanding where your blood pressure stands. And maybe if you're in a medication, take the medication accordingly. If your blood pressure tends to spike in the morning, maybe take it at night. But having an understanding of blood pressure spikes at different times of the day will help you understand. And of course, to understand if you're getting benefit from your exercise and your diet, you may want to keep checking blood pressure to see that it's coming down. Which will give you a great motivation to keep doing it. Number 10, get the support. You know, you need to really share with your friends. It's not something to blame or something to be ashamed of. If you have a blood pressure problem that you're watching this video, that's great. Share this with other people. Make sure you understand. They understand. Your family should understand that you have a blood pressure problem. So they should probably change their diet as well. Reduce salt, reduce sodium, more potassium in their diet, exercising together. Definitely, as a whole family, getting into this healthy pattern will definitely help you. I would suggest also supplements can help. For example, garlic is a known remedy for blood pressure. Hibiscus is another one. It's a great tea. Weight protein can help the blood pressure reduction as well. And interestingly, weight protein can reduce your triglycerides as well. Fish oil can also reduce your blood pressure, especially the EPA. So I would definitely suggest using fish oil. Some pharmaceutical fish oils are better than the over the counters because EPA component is a little bit more beneficial than the DHA, although they're both beneficial. But having a high concentration enough may be difficult with the supplements when it comes to fish oil sometimes. I hope this video helped you guys. And if it did, please give it a thumbs up and share it with your friends and subscribe. See you in the next video.


Okay. Hi. Good afternoon. Who's enjoying the conference? About half of you. Who's learned something new? Well, that's great. Yep. That's the reason we're here. And I have one more opportunity to maybe try to share something else that's a little new. So, welcome to my session on taming attestation for the cloud-native world with Pasek, a title that was so long that it actually had to be truncated off the end of the digital display just outside of the room. It is a long title, but I'm going to try to justify all of the parts of it as we go through. So, quick business card. So, my name is Paul Howard. I'm a principal system solutions architect with ARM based out of Cambridge in the UK. I've been with ARM for a little over four years now, and I focus on solutions that span hardware and software and try to get the best out of both. So, if you're wondering what is somebody from the CPU architectures company doing at a cloud-native conference, hardware and software working well together is very important. I clearly need a higher resolution selfie, or maybe the picture's fine, and I just look like that in real life. So, a lot of my work is investigations and prototyping, but also open source development, and I'm actually one of the founding maintainers of the Parsec project, which is a CNCF Sandbox project. Other facets of my online presence, you can see there, and you're welcome to make use of them, so if you want to connect with me or follow up on anything you hear this afternoon, please do. So, here's what I'm going to cover. So, this is a session on Parsec, but it's a session on new directions in Parsec. So, there isn't going to be time today to cover Parsec in depth. It's not going to be a deep dive on Parsec architecture. I will introduce it. I'll go through the motivations for it, because maybe not everyone here is familiar with it yet, but also because some of that context and introduction will help with the main topic of the afternoon, which is attestation. So, I'm going to talk about some future work in Parsec to expand its feature set into the world of attestation, and I'm also going to bring in another open source project called Verizon. Now, Verizon lives and breathes attestation and is concerned with the verification of attestations. So, I'm going to be talking about Parsec for evidence gathering and Verizon for verification, and we're going to see how these two projects can be combined. And then we'll see to what effect, and I'm going to focus on two examples that I think are particularly interesting and hopefully relevant to us. The first is the use of attestations as part of establishing a secure channel between two entities where we're working with the industry on an extension to TLS 1.3 that builds attestation into the handshake. And the second is going to bring in another CNTF project, namely Spire, and talks about how I think that Spire can consume the work that we're doing in Parsec and Verizon to do a new way of doing hardware-based node attestation. I will, I hope, leave some minutes at the end for Q&A. I don't mind being interrupted briefly, so if I need to clarify or just repeat something. But let's save more involved questions for the end just in the interests of running to time. Okay, so let's begin here with the cloud native edge. So what does this mean? Well, edge computing nodes were traditionally gateways. So in an IoT application, the role of a gateway is to sit between the endpoint devices that are typically non-IP devices and to talk over those local protocols. So think of your Bluetooth, your ZigBee, Modbus, those kinds of things. A gateway can gather data from endpoint devices and it can deliver actions or commands over those same protocols. And then, of course, in turn, the gateway is an IP capable device. It's on the internet. It can go and talk to services in the cloud. As for the kinds of compute workloads that would run on gateways, well, those tend to be embedded, very tightly hardware integrated, singular of purpose, flashed in the factory. And they would be doing things like protocol translation. And the compute power of devices like that would generally be quite modest. So that, if you like, is the gateway model of edge computing. So what's a cloud native model? So as the number of connected devices increases, so too does the volume and the complexity of the data that they generate. And backhauling that kind of volume of data for processing centrally in the cloud starts to make less sense economically or in terms of performance or even sometimes for regulatory reasons. And what this means is that we see a drive towards processing more and more of that data locally at the edge. On edge computing nodes that have more compute capability built into them, able to run more sophisticated workloads doing things like ML inference or sensor fusion. So if our workloads are more sophisticated, then it means that they are looking more and more like stuff that we're really used to deploying in the cloud. The edge becomes more like an extension of the cloud rather than this very rigid, locked down embedded gateway that we have over here. So the edge becomes a place where we want to roll out and orchestrate applications and services just like we can in the cloud. And so for this reason, we can call this a cloud native edge. So gateway model, cloud native edge model. And that's great. But we do hit a challenge when it comes to security and it's because we encounter this collision of worlds. So the edge sits precisely astride to very different engineering paradigms, the world of the cloud and the world of IOT devices. In the cloud, we have rich workloads in high level languages. We have multi-tenancy. We have CI, CD. We have containers and orchestration. Everything is very fluid, very portable. We don't even really see the hardware platform much less care about it. We're just writing and deploying software. Now, in the world of IOT, it's very different. We're dealing with devices that are running outside of the cloud. They may be in temper prone environments. They're also far less uniform. There's lots of platform diversity and suddenly you can't escape needing to know a lot about the platform and the hardware. And a great example of where this is true is in the application of hardware backed security. If we are in a temper prone environment, then secure assets like secrets and private keys are really going to need hardware backed protection. And hardware backed security is very platform specific. Some edge nodes will have something like a trusted platform module, the TPM. There could be some other kind of hardware security module or a secure element. And there's also the possibility that discrete hardware of that kind is not cost effective or it complicates the design of the device too much. And we might then choose to build secure services in software but isolated from the rest of the system using isolation features that are built into the CPU. And we'll see an example of that later on. So we have fragmentation. And this throws up road blocks when we want to be cloud native. The APIs that they offer are very low level. They're very device specific. They mean that you're writing code in the C language with an embedded mindset tightly coupled with the hardware and needing quite a bit of specialized knowledge. So it's a world away from that high level portable code that we aim to write if we really want a cloud native edge. Now, up until recently, the best available solution to this fragmentation problem with hardware security was the PKCS11 interface, also known as Crypto Key. And even today, you're going to find that that is the incumbent solution for cases where application code needs to be bridged to hardware security. And we find that all manner of shims and bridges have sprung up both proprietary and in open source, making it possible to use PKCS11 to talk to TPMs, to HSMs, secure elements, and so on. And it's okay as far as it goes but it doesn't go far enough for a cloud native edge experience. And this is for a few reasons. You'll find actually as soon as you try to deploy in this way that PKCS11 implementations are notorious for following the standard imperfectly. And even with that aside, it's still a very low level developer experience. We're either having to write code in C or we're having to use something like a foreign function interface to bring that up into another language. All those crypto and key management functions. So it's still a very close to the metal way of interfacing with hardware security. So improving on this status quo is the role of Parsec, CNCF Sandbox Project. This is why Parsec exists. Now Parsec is more than just an API like PKCS11. It's a microservice that handles all of that interop and all of the low level details of hardware security on a whole variety of platforms that is growing over time. Where possible, it cuts out all of those nasty PKCS11 shims. It can talk natively to the TPM API. It can talk to secure elements and other hardware security solutions. And if you need a new one, it's open source. Go contribute one. And if you have an interop bug, go fix it. Go contribute the fix and everybody benefits. Now the Parsec API is not defined in the CNC language. This one is language neutral. So Parsec defines it as a set of serialized contracts on a wire. And this means that it can be surfaced into programming languages in more creative ways, ways that are more fluent and idiomatic for consumption in that language. So at the lowest level, we're only transacting bytes on a transport with system calls. We're not bringing in a lot of C crypto functions. And the use of IPC and a microservice means that the client applications can be in containers. We can even have multiple logical applications sharing that service in a multi-tenant fashion if we need to. And the vision for Parsec is that we just want it to become part of the platform, really. We want it to become a supportive package in Linux distributions, in Yachto recipes. It becomes a pervasive low friction path, convenient, portable, high level, and evolving and improving over time through expert community contribution. Okay, let's look at a reason why all of that's useful. So suppose we have an edge computing device that's going to run some workloads that are rolled out to it from the cloud. These workloads could be containerized modules, for example. So think of a technology like AWS Greengrass or Azure IoT Edge. And we want these devices to be provisioned and registered securely with the cloud. We want to be sure of their identity and the provenance. We can do the provisioning step like this. We can create a private key on the device and a corresponding public certificate, which is then chained to some CA and shared with the cloud so that the cloud can trust the device. And then at run time, when the device is in the field, it can talk to the cloud securely by means of a mutually authenticated TLS connection. The cloud and the device share their certificates with each other. The device proves ownership of that private key by signing for the TLS handshake. And then finally, the secure channel is established, which is foundational to whatever else needs to happen in the product stack and deliver and execute those workloads. So you'll see this pattern or some variation of it in systems that need to do secure onboarding. And it's a great fit for Parsec, because on the Edge devices, those private keys are resources that you absolutely want to protect. Ideally, we would want to provision these things directly within hardware-enforced secure boundary and then access it later to do the signing. And then if Parsec becomes the default low-friction path for achieving this, then I think there's a greater chance that customers will adopt hardware security, because right now, the lowest friction path is the out-of-box provisioning solution that's offered by the product stacks. That normally means generating your key pair in the cloud and then importing it onto the device. So it was never provisioned within the device. And you don't know where it's been in the meantime. And it could be stored just as a file on disk protected with nothing more than file system permissions. So what Parsec aims to do is offer a comparable level of ease and simplicity, but gaining a stronger security stance as a result. And this is the kind of use case that it supports already. And so we take the next step. And this is one of the more exciting opportunities that we have with Parsec. And we have it precisely because Parsec is not locked against a fixed crypto API like PKCS 11. It's its own project, its own microservice. It has its own API that can grow organically. And the opportunity that we have is to grow Parsec beyond doing only key management and cryptographic operations while still providing those crucial platform abstractions for portability. So we've seen that we can provision our private key with hardware protection. And we can use signatures in TLS to prove ownership of the key. But we are only proving ownership of that key. We aren't proving anything else. Now TLS is going to work whether that private key is hardware protected or not. So the signature proves ownership of the key, but has nothing to say about the history or provenance of the key and nor does it have anything to say about the overall state of the platform, its hardware, its firmware or any of the other components that are running on it. And so the answer to that is to ensure that the private key is attached to a platform that we can vouch for. We can vouch for it because we have a chain of measurements of all parts of the system going right back to the device's hardware route of trust. And we can verify all of those measurements remotely. You may recognize that. That's remote attestation. It may be familiar to you. And the remainder of my talk is going to be about how we can take the existing portable key management and signing capabilities of Parsec and grow those out to include the kinds of primitives that we need to support remote attestation flows while maintaining that abstraction and that portability. And then I'm going to talk about how we can make use of those capabilities once we have them. Okay, let's look a little closer at the components of a remote attestation flow. There are essentially three aspects to it. So we have endorse, attest, and verify. And this flow diagram indicates where and how those stages take place. Endorsement is the process by which a manufacturer or provisioning entity can make a statement about what is valid. If a device has these properties, this platform state, this configuration, then it's trustworthy. And the provisioning entity makes these statements to a separate entity, the verifier or the verifier service. This verifier service then becomes the authoritative database of valid devices and measurements and configurations. Manufacturing can then deploy a device to the field and that device might then go and register with a cloud service, much like we saw a couple of slides ago. Only now it can do more than just prove ownership of the private key. It can also supply a package of signed evidence to attest to its own state and its own configuration. The cloud application or service then relies upon that, so it becomes the relying party. And that reliance is based on this critical final strut in the triangle, which is verification. So the device's signed evidence is presented back to the verification service, which receives the manufacturer's endorsements for that device, which had received the endorsements previously. The verification can then match up the endorsed characteristics with the actual presented characteristics and if they match, the verifier can tell the relying party, yes, we can trust this device, it's a known good device, it's in a known good state. Now verification services exist in the ecosystem, some device vendors provide them, some product stacks come with them as being readily available. But I want to take the opportunity today to bring in this other Linux foundation project called Verizon. Verizon is not a CNCF project, it's actually being nurtured within the Confidential Compute Consortium, which is a different branch of Linux foundation, but it is open source and it is relevant to us here because Verizon is concerned with the verification part of the process. Verizon is in fact a set of reusable components or building blocks that can be used to accelerate the development of verification services that offer a high degree of ecosystem compatibility by adhering to open standards. It defines APIs for provisioning and for verification. Now I can't go into detail on Verizon today, but I do want to bring it into the conversation because the work that we're doing on attestation in Parsec is aimed at matching the capabilities of Parsec to those in Verizon. So in essence it's making it possible for a Parsec enabled a testing device to bring its evidence to a Verizon based verification service. Okay, let's come back to Parsec. So why is Parsec in the picture? Well we've already seen its role in key management so that we know that the role of Parsec is to provide simplicity, abstraction, portability in the face of a diverse hardware ecosystem. And these things continue to matter once we're talking about attestation because it turns out that attestation is also device specific and causes us similar problems if we want to code, if we want our code to be portable. Okay, concentrate on two different route of trust technologies, not the only two that Parsec can work with, but we are focused on these two for attestation, at least to begin with. So we have trusted platform module the TPM here on the left and then on the right we have an implementation of the PSA route of trust. Now PSA stands for platform security architecture and PSA certified is a widely adopted security standard for IoT. The PSA route of trust allows the device's foundational security to be built in a way that is cost effective and not necessarily reliant on discrete hardware module like a TPM. So we can be built out of software or firmware components typically integrated by silicon vendors into their SDKs and isolated from the rest of the system using an isolation technology that's built into the CPU. So ARM TrustZone for example would provide that kind of isolation. And then we have these small packets of functionality we call trusted services that run within that architectural isolation boundary. Conceptually it's comparable to the TPM but the implementation is different and then of course the API's are different and the data formats are different. And so again it's a fragmentation problem and we're back very much in Parsec territory needing a common abstraction that allows client code to be portable and simplify it. So when I talk about taming attestation in the title of my session that's what I mean. In those boxes we can see examples of the data formats used so a TPM will use the TPM 2.0 data structures. A PSA platform uses something known as the entity attestation token or EAT. And we're doing some work in Parsec right now to expose both key attestation and platform attestation API's that can work across these distinct route of trust backends and they're going to work in terms of a common encapsulation format that uses something called the conceptual messages wrapper. Now this wrapper is being nurtured by the Rats working group which is one of the IETF working groups that focuses on attestation. Now these wrappers are self describing and they're keyed on a registered media type which makes an ideal format to convey between the components that don't want to hardwire themselves to any single physical representation. So they can deal with multiple representations they can dispatch to the correct kind of processor by peaking first at that media type and then assuming that the rest of the data is organized according to that type. And the slide has a link to the IETF draft that goes into much more detail on how that works because I'm that was really just a lightning presentation of it and there's a lot more to it. So these common encapsulation formats can be applied end to end also throughout an attestation flow for all stages for endorsement for verification as well as for gathering the evidence. So Parsec can provide them for all platform types beginning with the two examples shown here and Verizon can consume them so it's a nice story for bracing these two open source projects together. OK so for the last part of the presentation I'd like to look at two areas where we are applying this work. Let's look at the attested TLS proposal first. This is another one that's being developed within the IETF. Some of my armed colleagues are contributing to this but also in collaboration with engineering teams across the industry. So there's a link to the top at the proposal in the IETF data tracker where you can go and read in much more detail and go and go and look at the lovely ASCII artwork diagrams in the proposal. We looked at TLS before it's obviously foundational to the connection between an edge computing node and the cloud. So until you have a TLS connection you can't really do anything else. TLS by its nature excludes any peers that cannot prove ownership of the correct private key. Now the attested TLS proposal goes beyond proof of key ownership and brings attestation into scope for the handshake phase. Now there's a real elegance to this because it makes attestation a prerequisite to the establishment of the secure channel. It means that by the time you have a secure channel the device has already been attested and verified so it's a very neat way of excluding devices that can't prove themselves to that level. It closes a threat window that might otherwise exist if you set up the secure channel first and then do attestation afterwards. It doesn't mean it's going to necessarily suit every kind of workflow for secure channels but the onboarding use case is one example that I mentioned earlier that might benefit from this kind of approach. So the diagram is a simplification. The IETF proposal has all of the details but I do want to stress what's essential about the proposal. You'll probably be familiar with TLS based on X509 certificates but what this proposal introduces is a whole new credential type. So it means that attestation evidence can be used as an alternative to X509 making use of some of the extension facilities that are present in the design of TLS. So that then allows us to make use of the common abstractions and wrapper formats that I talked about on the previous slide. The secure channel can be established based on that same trust relationship between the manufacturing entity, the attesting device and the relying party on the verification side which again I've indicated can be built using components from the Verizon project. Okay, other details I've had to gloss over. You can go and read about them. Follow the link. All of this work is of course being done out in the open. You can follow along with the POC effort for this and that's going on in GitHub. I've got some links assembled on my final slide which we'll look at in just a second. But before that, let's just finish up and talk about another potential application of this work which I was discussing with the Spire community just towards the end of last year. Now Spire and Parsec already share a little bit of history and there is a YouTube video with myself and Andres Vega talking about the use of spiffy identities when calling Parsec so that Parsec can work in a multi-tenant fashion. That was in 2021 I think for the CNCF production identity day and it's on YouTube. But for today, so let's look at Spire Node Attestation. So Spire has workload attestation and Node Attestation. Node Attestation is to verify the provenance of the compute node on which a workload is running and Spire has a plug-in architecture that allows nodes to be verified via different characteristics. So one of those verifiable characteristics could be a hardware root of trust that is on the node. And there are Node Attestation plug-ins available today that can already use a hardware root of trust if it's based on a TPM. But with the new attestation functions being added to Parsec, which is portable, it raises the possibility of doing Node Attestation based on an abstract root of trust using a TPM when it's available but using other technologies that might be on the platform such as the PSA root of trust that I mentioned before. And you have that similar client server separation that we saw in the case of TLS. So Spire Node Attestation is separated into an agent plug-in and a server plug-in. So the proposal here is to create an agent plug-in that consumes the Parsec APIs and a server plug-in that consumes the Verizon APIs. And there are go-client libraries for both Parsec and Verizon. Now there isn't a POC of this in the works just yet, but I am really hoping to get one started and it would be great for the Parsec and Spire communities to come back together. So if you're interested, do please come and talk to me because I'd love to engage. Okay, so that's it. Some useful resource links there. You can follow all of these if you download the deck. Thanks once again for coming. Thanks for listening. And if I've done this right, you should still have some minutes left for any questions or comments. Yes. Sorry, can you ask again? Okay, so the question is, is there anything for runtime attestation as opposed to boot attestation? So I think anything that you can measure is potentially in scope with this work. So yes, boot attestation is generally what you think of when you think of hardware root of trust and platforms like a TPM, for example. But with what we're proposing with Parsec and Verizon, both are extremely flexible. So there definitely is scope for measuring components within the system that are not just the boot loader, not just the firmware, but potentially going beyond that to encompass other things as well. Okay, if there are no other questions, thanks very much. That QR code is my session feedback code. If you love the session, please go and tell me. If you hated it, please remember how busy you are and you don't have time to fill in feedback forms. And enjoy what remains of the conference and have a safe trip home.


Hey, what's good y'all? It's your boy Dom from the Dom's Show on Friends. I'm back with another K-pop reaction. Now, check this out. I have a special guest first off. I know you might have been where I've been. If you went to Instagram, I've been busy. Been doing a lot of work and the semester ended and I had to do a lot of greats. So I love you. I'm back. We're gonna get into it. We talk about the new projects. But I have a special guest. This is my friend Tiffany. She's here in Toronto, Ohio. You know what I'm saying? Artist, activist, creative director. She does a lot of music production work. And so what I wanted to do is that she's our K-pop. She know little songs. Okay. So what it is is that we're gonna actually do some reaction videos. And if y'all love Tiffany's energy here, you know what I'm saying? Please go in the comments and tell me. Let me know to bring her back and I'll bring her back. Because if y'all bang with her, we bring her back. No. Okay. So what we're gonna do today is this y'all. We're gonna do choreography video. We're gonna do John Cook standing next to you dance practice. So this audience love dance practices because they know I'm a dancer, a t-shirt, choreographer. So that's what's gonna happen. So please make sure you hit the like button. Please share and ring that bell. James and Alani Carter will be back. So don't worry. I know what's out there. I know y'all talking about it. The usher. We're gonna have them do the usher music video. But if it's a dance practice, I'm gonna attack that. Cool with that. Okay. And I do a part two with the bros in there. All right. So what we're gonna do is gonna get into this. Now if you don't hear the music, you already know what this is. It's because you two be petty towards me and they have blocked the video. So I'm gonna do my best. All right. So let's get into this. Y'all know how to do this. Ready? Okay. Here we go. And three, two, one. Is that Ian and Brian? Is that Ian and Brian? Is that Ian Eastwood? Okay. All right. All right. All right. Y'all pointing out heat. Let's see what y'all working with. It's giving Michael Jackson. Okay. Okay. All right. You know what? Intro is everything. All right. So anybody that doesn't know your intro is everything in this intro is crazy. Intro is crazy. And anytime you see something you like, you don't have to wait for me. Hit the space bar. And I'll just wait. If James was here, y'all know, y'all know I'll be talking here. Just be like and still keep going. So I'm just going to say I love the intro. To be honest with you, Brian and Eastwood and other choreographers that's in this piece, they just got the skill from World International Touring. The resume says for itself. And I think that if you don't know who Brian Pusspost is and Ian Eastwood, do your homework, got a lot of production work behind them. Do you have anything to say to it? I have a question. Oh, let's go. Who choreograph is? We can find out. Hey, any comments? Okay. I'll let me know who actually choreographed it. Was it Brian Ian or was it the whole company that did it? Please let us know because I don't want to be wrong. But I'm going to try to find out. But you might be able to find out based off the choreography. So let's see. Let's go. Come on. Musicality. Musicality. I see that. One, two, three. Okay. Okay. Okay. Okay. Okay. What did he just do there? He slid right out. I'm on the right side, y'all. On my right. Watch my man. What type of, he got the no sleeves on. Watch what he does. Is he dancing? One, two, three, four. Time that on the one, two, three, four. Look at that again. Standing next to one, two, three, four. One, two, three, four and go. Nice. Now, this lets me know this is either, and I'm guessing because I like to do blind reaction. Y'all know how I get down. For me, it's giving tour, right? And music video. The reason why I say music video or award show is the camera. Watch the camera. Y'all saw the camera. Watch that. Watch the camera zoom in. To me, I'm guessing it's giving that I'm going to get ready for a music award. I'm going to get ready for a tour and a music video. Yeah. And the productions already sounded good. Yeah. Yeah. I already know what's up. I see the leather pants. I see what's going on. Do you have anything to? I mean, you mentioned the beat production, right? Right. I'm listening to it, but for me, it's not giving me anything different. And then since it's giving me very much that song with Bruno Mars. Oh, yes. Yes. Yes. Yes. Yes. You know what I'm talking about? Okay. Yeah. So for me, it's just giving something I've already heard before. You're like, there's very basic chords, patterns that you're hearing that you would hear in a lot of these songs. And that goes into a lot of, I don't know if y'all can hear me because my mic, I'll be doing a little weird stuff sometime. But I think that's the one thing about, you know, when it comes to the music, it's like music would pick up a trend. It was like you'll get like lean with the rock with the music. You'll get everybody trying to do trap music or so it's like what in your production that's going to make it actually stand out for us? Yes.  And I have to say this because I was a BTS fan. And I got put on when they had their, the most beautiful moment in life part two that album. I know y'all remember that. If you remember that and I just felt like their production and their impact was significantly different. And what we were talking about and the types of beats that they were experimenting with. Hey, after this video, you should get in the comments and talk to them, talk to the fans. They will love to have this discussion with you. Hmm. For real. I love my supporters because that is the topic that they're ready to get down. Okay. Okay. Y'all down? No, because I've been having like these little inside takes, especially about BTS, but we can get into that at another point. Let me wait for you in the comments. I'm gonna make sure y'all get the tag for our Instagram. And then we'll make sure she got the YouTube. Y'all make sure I support. Okay. You're back in this. I wonder if you're going to have multiple artists on this stage. Now, at this part, y'all already know that I'm going to keep talking because I cannot get copyright straight on this. So we're probably going to cut this part. Y'all know we're here for the choreography. Did he just tie them in? Hold on. Let's go fellas. Yeah. Three, four, one, two, three, four, one, two, three, four, one, two, three, four. That lighting will probably be crazy on stage because you got that lean. I wonder if they would do the lighting this way to shine towards filming. I followed that. I followed that. Hmm. Let me look at that again to see the visual. One, two, three, four, one, two, three, four, one, two. Okay. I see it. You're right. Don't course. Yes. I see it. I see it. One, two, three, four. This is definitely getting ready for a stage. This is stage. Come on, Brian. One, two, and three, and four. Yeah. Clean. I'll be talking to y'all all the time about clean. Talk to y'all all the time about clean. Yes. Yes. That was very, very clean. Two, one, two, three, four, one, two, three, four, one, two, three, four. I'm not mad at that. Yeah. We got to run that back. Oh, go ahead. You just hit this right here. Yep. There you go. Yep. Okay. Come on, man. Wait, wait, wait, wait, wait. You see how he timed? Yeah. But he timed it with their feet. What's disrespectful is that if you watch every artist also on this page, we never call dancers backup dancers. We believe on this channel that, no, they are artists too. They're not backup. You need the music production team, the videography, you need, those are no backups. They are part of this as well. So the artist, check my man's in the back because my man's in the back with the trucks. Everybody did something different. Everybody did something different. So you could just see the improving. So like, even right here, let me see, because I love what you did with the hat. Efferless. One, two, two, two, three, four, five, four, five, six, seven, eight. Nice. Yeah. And Ian is just the OG with it. He just knows. He just knows, do, do, do, do, standing next to you. Give me a real Michael. You could tell the love for Michael. And we know this, but it's like, you got to call it out. You got to call it out. Let me see how they got into this next step. Two, three, four, one, two, three, four. One, two, three, four, one, two, three, four, one, two, three, hold on. No, I want to see that. One, two, three, four, five, five, five, two, three and four. What are y'all doing over there? Onstage, offstage, downstage, upstage. Okay. Yo, he getting it. Yeah. He's, I'm going to be honest, you know, we're not going, we're not going to cap on this channel. My man's in the back with the snapback that he's doing this effortlessly. This is not challenging him. And I know this is a dance practice, but he's really, you can tell his background in dancing has been probably crazy because you can tell how he's dancing. It's effortless. Like just turn and meet the music real quick and watch the video. He's playing around. It's too easy for him. It's too easy. I hate that. Yeah. He's real smooth. Yeah, he looks graceful almost. It's effortless. That's effortless. He's playing around. Did you pee the breath that he took? No, no, no, I didn't. How do I go back one? And then you can change it if you want to. He timed it. You didn't see that? Look at, ah, he like, why didn't they not slew that? You know what? The fact that he timed his breath, that just reminded me of crown. But also I think of, I think of composition and like where you have to time, like if you're composing something for brass or woodwinds, you have to put where you want your breath marks. So you can time the musician's breath marks. Yes. But? They look like ticks. Yeah. And so I find this interesting because I'm like, that was a moment not only where he timed it with the music, but where you could just tell he's really good at managing his breath. Like you said, this is light work. Yeah, he's good at managing his breath. You have to learn that as a musician, as a dancer, singer, athlete. Okay. Yeah. Time of breath. Yep.  You do. Or you'll burn out. Yep.  And Brian was doing the same thing, but this is smaller. But my man said I'm back with a snap back. No, he was ready. Oh, it's too easy for him. He was in his core ready. Come on.  One, two, one, two, three, four, one, two, three and four. One, two, four. Did you see what he just did again? He nasty. He nasty. Yeah. Yep. Ah, he grind that in. This too easy for him. It's too easy. Yeah, this is where he want to eat at. He's in the front now. Deep, deep, deep, deep, deep, deep. One, two, three, four. Wow. This crazy. That's crazy.   And I'm going to tell you what I'm talking about. I'm not going crazy because it's like I grew up with them. I grew up with in Eastwood. Watch. No, respectfully watching in Eastwood and Brian Pooze will come up and witness in them, go by the storm in choreography. So it was like much love and respect all day. But it's, if you watch this choreography, this signifies like why Brian and Ian was dangerous because they created these moments that were in between of the groove. Look at that. Let it flow. He's got it crazy. Yes. Gotta figure out the choreography. I'm definitely thinking it's Brian and Eastwood. Let's go. And if you're going to do something, and now he's starting to look familiar. Hey, did my best dance for all? He danced for somebody I can't remember, but this group of artists are dangerous. And Cook, he knew what he was doing. They know who to book. Whatever is about to come out is coming heavy. Definitely. Yeah. And this does look like his work. Oh yeah. And this part is connected to the whole usher and everything. You need heavy hitters. You need heavy hitters. Good work, y'all. Good work. And I know it's a dance practice. I know they didn't go full out. But it's sometimes the people in dance practice that are so good at the choreography that literally that they would be effortless. Like my man's here. I'm going to play this in the back on music so y'all can watch this. But doing off this choreography, he just had these moments that he really stood out. Not saying the other artist wasn't killing it, but it was just like he was really, really effortless in the movements. And that's what I appreciate. So in the dance practice, what was your thoughts about that? And then also, what else are y'all starting to notice with the trends that's going on in the music? Because not only does it affect hip hop, it affects the R&B, it affects the K-pop, it affects what's going on. Because like right now, I'm starting to see a lot of more artists coming out with the leather pants on. Fashion and hip hop and R&B and K-pop, like this stuff continues to like have an evolution of like what is the trend and happening. And then for them to pull out, you see from the very beginning, he was already in his bag already. To me and Brian are just like OGs now. So they've been, you know what I'm saying? They're OGs when it came to the choreography game, doing their work. Oh yeah, that's a Brian thing. Like yeah, silent to them making a mark for themselves. So what are your thoughts about this? Is that music video for this? Y'all want me to look it up? You want me to look it up? Okay, I'll look it up. Is there anything else? Don, just look it up. All right, cool. I'll just look it up. So listen, without with that being said, y'all, I'm going to go ahead and check out what's the next video for y'all. Upload that. I know, yes, I am back. Got the schedule back together. A lot of dance practice coming up. So, oh, we'll talk about that next video. I got a new channel for the vlogs. So I need y'all to subscribe to that because they're really dope and I like them and I hope that you watch them. Okay, so I love y'all. Thank you so much for putting up. You might see her in the other video. We'll see. But other than that, y'all take care. Peace.


This is Witchspace news for Friday the 16th of October, 2020 I'm CMDR Buur In this weeks news The return of the Thargoids F-DEV moves the Monday supercruise news livestream The problem with combat The problem with mining If you enjoy this video remember to subscribe to the channel and turn on notifications and if you'd like to support our work you'll also find us on Patreon Links to everything you need are in the description below The current round of community goals continued apace this week after last week's shoving match between the Marlinist refugees and the Empire finished on Wednesday The latest community goal hit a full hour earlier than usual at 1300 UTC and it sees the much anticipated return of the caustic alien menace, the Thargoids In what appears at least right now to be yet another concurrent thread running in the galactic storyline the Thargoid appear to have begun an attempted infestation of the fairly recently colonised witch head sector As soon as the news broke the anti-Thargoid community sprung into action and began loading up fleet carriers of eager combat hungry pilots The current infestation stops short of the pattern of invasion we'd seen from the Thargoid before There are no combat zones or burning stations but rather the meany greenies are swarming five key systems controlled by the Alliance in the region the Anoros, Lembas, Haki, Wellington and Shenvi systems Quite what the Manderbilt Horrors beef is with the Alliance specifically in this instance and why they've chosen to leave the feds or the imps alone for the moment is anyone's guess Could it be related to the recent use of Thargoid biotech in the bombing of Imperial stations that was claimed by the Imperial's Neo-Marlinist group? We've no idea but someone looks to have jammed a stick into the Thargoids nest and the area is crawling with non-human signal sources as a result If you're ever mined to join in the fight then there's rich pickings for all regardless of your Thargoid combat ability Even if you've never taken on one of the danger daffodils yourself you can still go scout-plapping and make a difference in the CG Just be sure to look for non-human signal sources of a threat level 3 or 4 and you're pretty much guaranteed to get nothing but scout vessels The CG runs until Thursday the 22nd of October On the regular Monday UK lunchtime supercruise news livestream this week Frontier announced that they were moving the livestream as of next week to a new slot at 2pm UTC on Tuesdays The primary reasoning for the move is simply because Monday mornings are a flurry of activity and meetings for the community team and pushing the livestream back to Tuesday afternoons will give them more time to collate news for the show and give it the attention it deserves Over the last few months the Monday livestream has very much evolved from what was a fairly simple let's play session to a more structured community catch-up with news featuring as it does the latest winners from the Weekly Stellar Screenshots Competition as well as news of community events and content creations If you've not seen the show recently give it a look in the new slot next week from 3pm UK time or 2pm UTC live on YouTube Prolific YouTuber and serial tutorialist Commander Exegius created a video last week highlighting the gaping disparities between the credit payout for combat versus other activities in the game such as exploration and of course mining It's a fairly well recognized fact in the community at large that combat just doesn't pay and the huge difference in rewards is all the more glaring when you factor in risk as well Suffice to say losing a very expensive ship and facing the rebuy screen is fairly rare when mining or exploring but with combat it's almost a given and if combat is the thing that keeps you coming back to Elite which of course it is for a large section of the community the lack of reward when you are successful in combat is forcing players towards gameplay that they wouldn't choose to engage in normally just because they honestly can't afford not to If you've not seen the video as with all of the content from Exegius it's extremely well researched and presented and does make an extremely compelling and not ludicrously unreasonable case for a modest increase in the credits earned through combat Regular watchers of the ED community will know that the issue surrounding combat credits earned versus other activities is of course not a new one What is interesting in this instance however is that after the video was very widely circulated by the community at large and almost certainly slid under the nose of frontier more than once over the last week or two They have actually acknowledged the video and the cries from the combat community surrounding it They've promised that they are listening and that they are addressing the feedback they hear from the community in general terms Right now the game is obviously bearing down quite heavily on what is undoubtedly a huge update in the early part of next year when Odyssey launches Here at the pit if we had to guess we think it unlikely that we'll see a massive change in combat payout balancing between now and then However Odyssey we're hoping does present an opportunity for frontier to address a number of extremely long standing issues in the game in general Whether those fixes and balance passes are part of the Odyssey package we don't yet know and for now at least frontier aren't saying Whilst we're on the subject of fixes at least some point in Elite's recent patch history the pulse wave analyser used for mining got well broken If you don't use the scanner yourself then let me just fill you in on the uncomfortable details It now appears that the scanner fires backwards out of your ship Yes really if you weren't to observe where you'd been you'd think nothing was occurring at all when you pulse but in actual fact the good stuff is just going on out of sight to your rear In the burpip discord we actually have one or two miners that have started flying backwards in an attempt to combat the newly introduced bug Which is obviously less than ideal to put it mildly This week however frontier have acknowledged that the bug is an issue they are aware of how important it is and whilst they can't commit to a date for a fix They have said they are at least working toward a fix for it That's it for now. Thanks very much for watching. We'll be back later this week with more videos until then O7 commanders follow the greens on the way out and do keep clear of the toast rack. We very much look forward to seeing you next time


Here's what's new this month with Passport. Whichever way I turn there's a trap. Let's set this palace on fire. She's to be married. She is not married yet. It's never a burden to love or give. The mother is at the heart of everything you do. These and all your favorite shows are available with Passport. Support your PBS station and stream more with Passport on the PBS app.


Here's some details of the palm straight back of the DIG so you got one, one, two, three. Now from here we're going to expand your chest, pull it back, this will be dropped, okay, and we're going to do it this way. Notice that most of my weight is on my back leg and make sure that we are in your spine straight, so expand your chest and this way. Alright, this fits your bottom of the chin, of your opponent, and when you fox out, you're going to do this one, good pivot, and we fox out up to here. I don't have to look there, I'm still looking this way. So the point of this is that if there's someone behind me, I don't know where he is, I can hear him coming, so I'm just going to fox out. All the way back there. Okay, maybe he's there, maybe he's not, but at least I can get there faster by just doing a fox out. I don't have to look because if I can feel something, then that means he's there. If you don't feel something, then I can look. Okay, so if I feel something, then I know he's there, then I can turn, I can attack him. Okay, so this will move faster than your head can move, so that's why we fox out there first, so that our hand will tell us whether there's someone there instead of our eyes. Okay, because if you turn your hand, you're going to lose balance. You turn here first, fox out, there's someone there, then you can turn and face him. Okay, so fox out, come back. In our other forms, after the fox out, we actually do a monster out like this. Okay, but in this case, you can go across horizontally with a hand or a leg, then do a jump style like that. That's the difference. So we're going in the other direction. Okay, so after one, two, three, we're going to expand our chest, pull back, and palm fox out, across jump style.  Okay, the power comes from the elbow and with the sunk shoulder. Okay, so the power is there. To the south, circle, and back. So that's some details on that section.