Hi, I'm Ashley with DAV and I'm joined today by DAV National Deputy Legislative Director Shane Learman. Shane, really big news popped up today on the PACT Act. I just wanted to check in with you kind of get a feel for where we're at and what this news will mean as far as that legislation is concerned. Well, it's very exciting. Senator Tester and Senator Moran have come to an agreement on the Honoring or PACT Act, which is the most historic large piece of toxic exposure legislation ever considered by the Senate. So there are agreement signals that we're probably going to be getting a vote on this in the Senate Veterans Affairs Committee next week, which is really important because then it will become eligible to go to the floor to be voted on by the entire Chamber of the U.S. Great, so definitely forward momentum. Like you said, this is this is a bill where we're very close. We're so close to getting this past the finish line. Can you just really quick remind our audience of some of the highlights of what this bill will do for veterans and their families of all generations. Oh, absolutely a lot of the big things is it'll provide health care eligibility for veterans not otherwise eligible to get health care specifically those post 9-11 who've been exposed to toxins or have been in combat themselves. That's a big piece of this. It'll also recognize for the first time diseases related to burn pit and toxic exposures, 23 different diseases. And one of the more exciting parts of this as well. It's going to impact Vietnam era veterans, because it's going to add hypertension as a presumptive disease for agent orange exposure, as well as add other locations conceding agent orange exposure, such as Thailand, Laos, Cambodia, Guam, America small and Johnston at all. So it's going to do a lot for the Vietnam generation, as well as it'll also recognize three new locations as radiation risk activities to actually encompass another generation of veterans exposed to toxins. So this is really a pretty comprehensive bill. And the other thing I want to point out too, it's bipartisan legislation. It's incredibly widely supported. There's more than 60 military and veteran service organizations that support this the VA supports it. President Biden has said he, you know, he's come out and said he will sign as if it gets to his desk. So really, this is the final hurdle is just getting it through the Senate. So this is the last stage we really need to make a push. How can our audience help to make that happen. They can reach out to their senators specifically, both senators in their state, and let them know how important it is we get this comprehensive exposure legislation through the Senate. We've been working on this DAV since about 2007, but over the last four years, we've been working very closely with the Senate and collaborating with a very large VSO better service organization coalition. And it's exciting to see all of this work everybody is doing is, as you noted, at that last hurdle, and we need to clear it so that the veterans who have been suffering from these diseases can get the healthcare and benefits they need, and it'll help their families as well. Thank you, Shane. This is a really, like I said, historic opportunity, you can as a viewer as a supporter of veterans you can be a part of getting this bill across the finish line. Visit DAV can.org, you can contact your senators right from our legislative platform, send them a message tell them to vote yes on the pact act. And together we can make this happen we can get this done thank you again Shane for your help for your advocacy all your efforts and getting this bill to the point where it's at. But right now we can't let down the fight we have to keep pushing, and we need everyone's help so please again visit DAV can.org and make your voice heard.


Welcome to the BC Library's Core Skills tutorial on primary and secondary source materials. This video will focus on the distinction between primary and secondary sources. It will also give you a glimpse of the variety of primary source material available here on campus. A primary source is a first-hand account of an event created by someone who witnessed or experienced it. Examples can include diaries, letters, essays, memoirs, interviews, photographs, videos, and even newspaper and magazine articles, Facebook posts, and tweets. As long as the person composing them has first-hand knowledge of the subject. A secondary source is created by someone who did not witness or experienced the event first-hand. Thus, the author must rely on other sources of information. Examples of secondary sources can include newspaper and magazine articles, essays, books, documentaries, and even Facebook posts and tweets. As long as the person composing them does not have first-hand knowledge of the subject. Primary sources are closer to the event, but secondary sources are important too. Scholars and scientists continuously develop new ways of looking at events and data. They give us new perspectives on information we may already be familiar with. You can participate in this process by studying primary sources and secondary sources in order to produce your own interpretation of the event or data. Suppose you are researching student activism on college campuses. For historical perspective, you might consult BC's archives. Because Leslie and Nath, the author of this Heights article, witnessed the event she has written about, this is a primary source. To find more recent examples, you might search for posts on social media. This tweet reveals a prospective college student's attitude about campus activism. As an example of young people's views on this subject, it is a primary source. You may also want to search for scholarly sources in the library catalog and databases. In this article, Neil Gilbert relies on other sources in order to develop an interpretation of student activism. Thus, it is a secondary source. Different academic disciplines may use different terminology to talk about primary versus secondary sources. But all are concerned with the distinction between sources close to the object of study and sources further from that object. Perhaps in a history class, you become interested in the role Tip O'Neill played in 20th century American politics. You could study John Ferrell's book on O'Neill. As a secondary source, it would give you Ferrell's perspective on O'Neill's political life. But you could also look at some of the original documents yourself. This is an excerpt of notes taken at one of O'Neill's press conferences. Because the person who took the notes was present at the conference, they are a primary source. You may find something important here that no one else has written about yet. The distinction between primary and secondary sources works a little differently if you're thinking about literature. For example, James Baldwin's essay on the movie Porgy and Vess could be a primary or secondary source, depending on what you do with it. If you're writing a paper on Baldwin's life, attitudes, or literary style, this essay would be a primary source because it expresses his own thoughts in his own words. But if you're writing about the film Porgy and Vess, it would be a secondary source because it is Baldwin's interpretation of the film. Usually, the distinction between primary and secondary sources is clear. For example, in preparing this article on the gluten-free diet, the authors themselves collected the data. For this reason, most would consider it a primary source. However, scientists may think differently about such studies. When in doubt, consult your professor. And don't forget to take advantage of the BC's Special Collections and Archives. From the McMullen Museum to the Burns Library, from the Heights Digital Archive to the O'Neill Papers, you have access to a great variety of primary source material. BC librarians are happy to help you explore them.


One question we could ask of Epicure is right away. What's pleasure? So he defines pleasure, at least at some points. He says, pleasure is the absence of pain. Okay. So, and another place is he defines pain as the absence of pleasure. Now for me, this is particularly annoying. That's like saying, A, what A is, I'll tell you what A is. A is what is not B, and then B is what is not A. This does not tell us anything about what A or B are. Now ultimately, Epicure's answer, I think, might shine some light on what he's doing. I think he might actually be a little sneaky here. A little sneaky. Epicure's ultimate answer of what pleasure is, is not what we think. We think of pleasure. We think of pleasure as your average knight in what? Las Vegas. What happens in Vegas, stays in Vegas. Your evening of visceral, carnal delights. That's something of what we think pleasure is, or all you can eat buffet with actually a decent chef. Okay, that might be pleasure. Yeah, you know, a blockbuster movie that doesn't really require to think very much, right? Okay, yes, that's pleasure. All right, this is not what Epicure's has in mind. Now, he's a hedonist, but he's not that kind of hedonist.  That's not what he's saying. Pleasure. The pleasure for Epicure's is tranquility. Tranquility. Now, when we think about what tranquility is, or what it's not, it's not anything in these other extremes, right? It's not the average knight in Las Vegas. It's also not starving, you know, to death. It's not, you know, the blockbuster movie that doesn't require to think, and it's also, you know, not being devoid of any stimulus whatsoever, being locked in some kind of deprivation chamber or a prison. So, tranquility is kind of in the middle of all these extremes. And what all these extremes are is not tranquility. They all disrupt your mental, emotional, physical states, right? That's what the extremes do. Now, this is me trying to read into Epicure's to try to play at what he means, but he may not necessarily mean that. But ultimately what he thinks is that, you know, this pleasure that's worth pursuing is tranquility. Because anything else that you pursue is going to lead you away from tranquility and it's going to be a pain in the end. It's going to be a pain in the end.


Hey everybody, this is Brian and this is our 7th Qt tutorial. Today I'm going to show you how to make a very minimal application. Just go file new project, empty Qt project. And then just give it a name. We'll just call this minimal. Throw it in your usual location wherever you've been building these. And next, choose your framework. See we have an empty project file here. We're just going to right click the project, go to add new, C++ and just say source file. And I like to call my main source file main just so I know where the main function is. Alright, now when you click your minimal.pro you see that it said sources plus equal main.cpp. Meaning it just added this source file into the project so it's going to compile and look for the main function in here. Alright, let's just add our includes. And don't worry if you don't know what any of these are right now. I'm going to go over them here in a little bit. Just kind of follow along here. And of course we need a main function. And if you're wondering what these arguments are here, let me finish typing this out here. Sorry, it's hard to multitask. It's been a very, very long day at work. This is our main function which you should know from C++ programming. Int, argc, this is the number of arguments. And care pointer to an array of characters. Basically that is the individual argument pointers. Alright, let's go queue application. I like to use IntelliSense as much as possible. Actually a very lazy programmer and I don't like to type. I know some people out there like using the most basic programming tools available so they have to type everything out. I am just not one of those people. I like to definitely use my time for other things. Alright, let's see here label. And what we're doing now is we're just going to create a new label. We've created an application object, the line above. So here's our new label and we're going to just say basic hello world. I know we've already done a hello world application but I wanted to do a very minimal application and just show you what is possible here with Qt. Alright, and now label show. Now if you remember right, when you have a widget, remember a Q label is a widget and you do show and we haven't created a window, Qt will automatically encapsulate that inside of a window and show that window. Let's do a return app.exec. And what that does is it returns app.exec. App.exec is just a loop that loops over and over and over again. And it's saying here I have some sort of error. Here we go. Too many little parentheses there. Alright, so let's review real quick. We have a include Q application. This is the very basic lowest com denominator that you need to run a Q application is the Q application object. We are generating a Q label and here we go right here. Q label pointer to label, equal new Q label and we're going to say hello world and we're going to do label show return app.exec. Now you may be wondering why we're doing Q application app. Why are we creating an instance of Q application? Well in order to execute the application, you have to create an instance of it. So the very first step is Q application must be created and we typically just pass the arguments to it. And then we do some initialization here and then we just enter the message loop waiting for the window to process messages. Just go ahead and run this. And it's going to take me just a second. I have to resize the window in order to pull it over here. But as you can see, this is what it looked like when it created it. Just hello world. Nothing fancy, nothing major. You took the label, wrapped it in a window. Now one thing that's very interesting about Qt is that it can do very, very good text processing here. So let's say we want that bold and let's say we want this italic. Now if you're wondering what these funky character codes are, it's HTML encoding actually. All Qt widgets are HTML aware. So you can use actual HTML codes and it'll process them and render them as you run the application. So let me pull this over here and you see how hello is now bold and world is italicized. So that's a very, very easy way to make some pretty snazzy little graphics here. And you can even do things like, let's do, I'm going to cheat here and look in my Qt programming book that I bought a while ago. Oh yes, let's do this. Font color equal red. And you notice how we're not putting quotes and end quotes in here. You don't really need them. The Qt engine would just strip them out and ignore them anyway, so they're not really needed. So what we're going to do is we're going to say hello in very big letters and then we're going to say in red italicized world. Let's compile and run this and there we go. Hello world.  Now if you're wondering why that hard return in there, we're getting that from the header automatically throws in a hard return. I think that's actually part of the HTML standard. So let's throw it at the end, compile, rerun it. Let's see if I can drag it here. There we go. All right, this is Brian. We covered a very basic minimal Qt application, the components you need and the fact that all Qt widgets are HTML aware. Thanks for watching. I hope you found this video educational and entertaining.


of the day presented by Toyota. Yeah, I said ready for two more tonight. And he was giving me the thumbs up. But yeah, looks like everything went well. And he's feeling how he should be today. And with Domingo Hermon, how do you anticipate getting him in the mix? We'll see.  And I'd love to get Domingo in there. But, you know, obviously the game will dictate it. And excited, though, that we're getting a really good picture back in the mix for us to hopefully help us here. And why did you decide to go with Boyd instead of Rizzo at first? I mean, that was the toughest decision coming into today. Just really liked the matchup for Luke today. And feel like, you know, he's still a guy that is going to play a big role for us, continuing to move down the stretch. And I think it's important that he continues to play. And frankly, just wanting to get Judgie another DH day. So, you know, obviously these are the days where you can DH Voight and have Rizzo in there. But I just felt like today I wanted to give another DH day to Judge.  And if so, how do you think it could manifest itself with your players? Well, I hope so. And I think so. You know, to see how the team reacted to him last night, just even when he first came in, you know, being up on the bench and the excitement that guys had, the appreciation for knowing the road that he had been down to get back to that point after missing so much time. And we're talking about, obviously, a really good pitcher in this game. And then seeing after the game, seeing guys kind of rally around him and just appreciate the person and, again, what he's gone through to get back, you know, hopefully that is something that can be a little bit of inspiring or another level of pick me up at this time of the year when you're really grinding.


If I ever had to go into a situation where a lot of brain power was involved, whatever it was, and somebody offered me new peps, I would probably take it every single time. Hey, what's up guys? It's Josh here. Today I want to do another review on new peps. I feel like I reviewed this compound two or three times, but I think I only reviewed it by itself one time. And at that time, I really didn't know anything about new tropics. I bought it because I wanted to try all the bulk stimulants. And so bulk stimulants carried it. I was expecting more of a stimulant-like effect, and it's more of a brain booster and cognitive enhancer, kind of brain protector. I've tried new peps on and off for several years. It's never been one that makes me always want to put it in my routine. But when I look back, I haven't had any negative side effects or any bad time ever taken it up all the times that I have taken it versus anoracetam, oxyracetam. Maybe it was me, maybe it was in my head. I had just never ending bad experiences on those. And I've never really been compelled to do a deep dive into new peps. But I recently got this new tropics bundle that has like five or six new tropics from Cosmic New Tropics. And they sent me like 25 to 30 new peps pills. And I think they were 10 milligrams each. And so I decided to go really, really hard. I'm pretty much only new pep to see if I can get a specific experience, a specific feeling, see if I can use it for anti-anxiety, use it for brain health, memory, all this kind of stuff. And specifically for anxiety, because I did not know that people claim new peps is supposed to help with anxiety. And on top of that, it's one of the most famous new tropics. I have tons of my subscribers right down below how much they like new peps. They get four to five hours of benefits. And I don't really know what benefits they're getting, to be honest with you. But they say, Oh, it works for four to five hours. I love it. This and that. So how I feel about new peps, I truly believe that it helps. If I ever had to go into a situation where a lot of brain power was involved, whatever it was, and somebody offered me new peps, I would probably take it every single time. I have had no bad experiences with it. I do generally think it helps in like a small little sense. It's not really something that for me that I take and I overly feel or I feel this specific thing, but I do believe it helps. And I would take it betting on that it would help my verbal fluency and my memory recall everything that goes along with a healthy brain. But that being said, after all the doses I've tried, I just can't really get a specific effect off this supplement. I mean, I think there was times where I took up to four pills, 40 milligrams, I just really didn't notice much. And again, like if I look back on the days that I took it, you know, everything was pretty good. Everything was fine. And maybe that was the new peps. I don't know. But there's certain compounds where I can pinpoint certain effects or Oh, it helps me with this or I felt unusually good in this area or this and that. And I just don't really feel anything specific with this compound. I'm not going to lie. I'm kind of torn out because I've had no side effects at all. I've never had a bad day on it. But unfortunately, after all the testing that I did with these 20 or 25 pills of new peps, I'm pretty much in the same exact position that I was before. And I actually want to retry paracetam and also cholera acetam, because I felt like they all had a pretty similar effect. I think of all three of those paracetam is the one that I would feel the most. I'd have to retry it. But I like new peps. Maybe you would like it. So it's definitely something to check out. If you're into all new tropics, let me know if you like new peps down below. I have no issues with it. If you offered me some, I would take it. I just don't only have one specific use for it. Unfortunately, although I would take it. So anyways, guys, what were your experiences on new peps? What was your dosage for new peps? What do you use new peps for? Is there any other compounds that are similar to new peps that you find are better or worse? I'd be very interested to see. I'm having a great day out here. Hopefully having a great day at home. See you all in the next video.


Hi everyone, thanks for coming today. I'm gonna share with you a little bit more about tech security, what we're doing, the different efforts that we have, what we've been working on, all the cool stuff that we have. And I'm gonna talk a little bit more about how we can get involved, what are some of the security challenges that we're facing today as a community and as a larger industry. My name is Brandon. I am a co-chair for tech security. My co-speaker, Andrew, is unfortunately, something came up and you can't be here today. So I'm gonna go quickly through the slides. Since this is a smaller group, I kind of want to try and do a little bit more engagement. So if you wanna ask questions, focus down on specific areas, we can do that. So just so quickly, who, what, when, where, why, kind of things. So I'm gonna start with, who are we? We are the technical advisory group for the CNCF TOC for security and our task here is really to aid the TOC in terms of helping strengthen the security posture of CNCF projects. So we do both reviewing our projects, kind of helping the TOC understand certain security projects. We also help identify gaps in the ecosystem and try and we write papers, do education, and bring people together and start fostering those collaborations. We basically do everything cloud native. Cloud native security is a work with many meanings because most of the things today are cloud native. So cloud native security does take up a lot of space there's a lot for us to like dig through and talk about. We wanna help in the end develop this mean security requirements and we also wanna be able to kind of get to where we wanna be in terms of auditing compliance. So the group generally works on GitHub. There's a GitHub link there. We are made out of professionals, enthusiasts, people in the community. We like the fresh perspective that everyone brings to the table. So this is our leadership team. So if you see anyone of fellow community members, say hi, myself there with my fellow co-chairs Andrew Martin and Aratna. We have Techleads, Andrews, Ash and Pushka. And we have our newly nominated Techleads, Michael Lieberman, Marina Moore and Raghashree. We are sort of our associate facilitator Matthew and Raghashree is also our community manager. And of course we have our co-chair emeritus, Emily Fox, who is now our TOC liaison. So what do we do? There are two parts that go into what we do. One of them is like creating and breaking things, right? This is where we say, okay, what can we do to help the community? What can we do to kind of like push the boundary of security for organizations and that is creating and breaking. And another aspect of that is also, things we've done with the white paper.  So I'm gonna just dive deeper into a couple of these. If you have questions, we can talk about it later. So the first one that I wanted to highlight is the V2 white paper. This was being worked on by the community in the past six months. It's a revision to of the original white paper that we launched, I think about two years ago now. And what we've done is we've really updated it with some of the newer topics. We also added some interesting ideas in which people were struggling to understand some of the concepts. We provided a framework to them. So for example, one of the things that was added to this paper is the mapping to the SSDF. So if you've heard of the NIS secure software development framework, that was a document that was written by NIS partially to kind of provide some guidance in terms of if in the US we have the executive order on security and the SSDF is there to kind of fulfill like some guidance in the area. So as part of that, we do some mapping to say that, okay, if you want to fulfill which parts of the white paper fulfill which particular requirements or controls in the mapping. So that's one of that that's very useful. We have a whole new section on ransomware. You know, we talk about what is ransomware. We talk about ransom cloud. You know, how do you protect yourself against ransomware? And also we have a new section on EU compliance. So a lot of cool things in the new V2 of white paper. I'll check it out. As usual, these things are living documents. So if you read the paper and you see something that's not in there, something that you're really, really interested in, it's like, okay, we need to cover, I don't know, like micro VNs or something like that. You know, we need to cover confidential computing deeper. We can add it to the white paper. Whenever we get kind of like a backlog of topics that we see come up, we then decide, okay, you know, here's the, now is the time to do V3. As V2 launches, also a couple of cool things that have happened is we have now audio book version available of the V1. So if you'd like to just put on something in the modeling, just listen to it, we have audio book that's available. We also have translations of the original white paper in both simplified Chinese and Brazilian Portuguese. And these are kind of important pieces of work that the community has done because, you know, for example, in Portugal, you can't use the document unless it's written in Portuguese. So that's why we had like members of community to the translation. We have a Spanish translation in progress that's being currently led by Carol, one of our contributors. We are still looking for more contributors there. So if you're interested in kind of helping to translate the white paper, you know, all the issue numbers on the slide, so just click in, put your notes there, say that you wanna help out. Another thing that we've been dealing a lot with is supply chain security, right? So back a couple, like a year, a year and a half ago, we first published the best practices white paper which talked about, okay, what should you do in order to get a secure supply chain? Your Ryan and company here have done a great talk during the security call and talking about that's how they used it and that's how they mapped it into 3M and kind of like pushed it out throughout the organization. So the second step of this is that we were working, now it's in progress, it's actually done. So I'm gonna show you what we have is the Secure Software Reference Architecture Paper. So this was just launched 30 minutes ago. So yeah, we had a lot of things churning in the pipeline, so it's gonna, it's a very eventful week. So the Secure Software Factory Paper talks about, it provides a reference architecture, it tells you what are the aspects of a Secure Software Factory, how should they work together? It talks about it in terms of concepts. We don't really dive deep into, oh, this is what technology, you should use and blah, blah, blah, because these things are gonna change. So the idea is we provided a framework, we've provided the language so that people can communicate with each other, so that people can reason about what exactly is this project doing, right? Because a lot of people have projects that say, I solve supply chain security, right? But essentially they are solving part of supply chain security. So it provides a way to communicate about that. We have a couple of authors co-authors here in the room, contributors. So if you're gonna stick it around, we can chat with that. As a side note, there is a project that was built with the reference architecture in mind called SSF, which will be renamed to Fresca. But so I have it linked here. This is actual code implementation using different projects, which provide the open SSF, but all the concepts are all tied from the secure software factory paper. Another quick thing to mention, we have a NIST controls mapping. This was phase one that's now completed and it was launched earlier this week as well. Basically maps everything in the white paper to the NIST controls. So if you're looking to target certain NIST controls in your products or implementation, you can kind of look at this and say, okay, this is how I can do it. We do have a phase two that's coming up and part of being cloud-native and cloud-native security is that we want to have automation. We've understood that we can't do security manually. And so the next step of this is to create container-based compliance. And so one thing that we're looking at is OSCO. And the way we get that is to first figure out what are the evidence that we have to gather, how do we actually audit these controls automatically? And so the phase two of this is gonna come up soon. It's gonna talk about how can we automate all these things and hopefully phase three further along will be implementing that framework. We also have a serverless white paper that's currently in RSC. Talks a little bit about serverless more, focus on the function side, what are the unique security considerations that you have to deal with in terms of access control and management. Also talks a little bit about what goes on in terms of your segregation or your risk transfer into your cloud provider. This is RSC, I think I forgot to put the link in here, but I will update the sites. Cool, so what else do we do besides writing papers? So we engage with other communities within the CNCF as well as outside the CNCF. So we talk to the Kubernetes Policy Working Group, we have six security, we have a cross members, one of the TL's Push Guy is a member of both. Cloud Security Alliance, we talk to them pretty often as well as OpenSSF, SELFSA as regards to the supply chain and reference architecture. Another thing we do is we interact with other CNCF projects. So if you are a CNCF project and you're thinking, okay, I need to do security, like I have a security project and I kind of want to kind of reach into the community, find end users, get some feedback on what should I do, how should I make security better? This is something that we do. We do something called security pals where we have a one-on-community member kind of guide the project along, like how do I create a self-assessment while the security considerations have to think about. And we have self-assessment and joint reviews which are analysis of the security posture of the project. So this usually comes in the project pipeline, although we encourage projects to just come up and do it. You get a very, very well fleshed out document and of it that says if you're interested in using this project and you are thinking about security, this is all you have to know. Track model, what are the considerations you need and really it decreases the barrier entry for groups to just pick out the project and use them. So this was just what I talked about. We have two projects that are coming up for this. We're looking for a security power for flux multi-tenancy. So for those that are not familiar, flux is a multi-tenant Kubernetes multi-custer deployment system. And so one of the things they're doing in graduation is they have this new multi-tenancy proposal. And part of that is we wanna be able to make sure that that's good. So we are looking for security power for that. We also have the captain drawing review which will be coming up soon as well. So nothing that the group has been working on is an event called Global Security Voluntary Summit. I'm pitching an event for another conference. This is gonna be in June next month and Austin together with the Open Source Security Summit. And what we are thinking about here is how do we solve, we always talk about Lock for J, Lock for Shell, all dirty cow, am I affected by this vulnerability? How do I manage this vulnerability? Or even how do I report this vulnerability? How do I get all the data sources and how do I make sense out of that? This is where we see efforts like effects. Like OSB coming out. So this event hopes to gather the community together, talk about it. We have governments involved, certs involved, and boundary-based databases involved. So that's gonna be a good forum. And also, we're looking to future topics like how do you do analysis now? Assuming that I have the graph all together of all the information. Is there any analysis that I can do, differential analysis to find certain classes of bugs or try and pick them out before they happen? Two efforts that are currently going on with supply chain security now, post-reference architecture. The first is obviously S-Bombs is a very hard topic now, but there's some gaps in terms of like, what does S-Bombs mean in certain contexts, right? When you have a piece of, you have a package or you have a software, S-Bombs is pretty well-defined, right? You're defining what's in that package or what's in that binary. But when you talk about cloud-native, when you talk about microservices, you talk about software as a service, infrastructure as a service, what does it mean to have an S-Bombs, right? If I'm hosting a service on a software as a service, it's my S-Bombs, the Python code that runs on it. Is it the container that it runs in? Is it the VM that it's running in, the Kubernetes cluster that it's running in, bad metal machine that it's running in? So you can see kind of like, there is that kind of open questions where we, as a community, we have to come together and provide some guidance for this, right? I think there's gonna be trade-offs, there's probably gonna be your practical guidance that we can provide there. Another part of this is the S-Bombs community and supply chain community kind of have been going on in their own tracks, and we wanna tie a lot of this together because generation of S-Bombs and the use of S-Bombs, right? We talk about generation of S-Bombs, and great, we have them, but do I know they're from the correct place or do they all generate that accurately, or can I trust this S-Bombs? And it's the same with can I trust this binary? If I'm using the S-Bombs as a basis to make my security decisions, I have to trust the S-Bombs as much as I trust the binary. So that's where you see a lot of overlaps with the supply chain practices, and that's where you see kind of cross-pollination there. Also, there's a lot of big open questions in the industry like distribution of S-Bombs, which have not really been talked that much about. Another thing that we're looking to do is to apply the best practices and the reference architecture to CNCF projects, right? So the idea there is to run an instance of the reference architecture that's the project for OpenSSF, and now pick a few CNCF projects to say, okay, we're gonna try to bootstrap you into this. We're gonna say, okay, we're gonna figure out how this works, how we can get there. And hopefully, based on those proof of concepts, try and scale up and kind of make this a thing that CNCF can do. We need to put money into security and open-source security, but no one knows how to use the money. Or we don't know how to efficiently do it. So that's the idea, and I think hopefully, also can influence OpenSSF alpha or mega project where we say, okay, look, we've provided some ideas that we have been able to execute in the CNCF context. How can we take this and bring it to other projects that may not have the kind of same kind of practices or the same kind of tooling and pipelines? Cool, so if any of these interests you that we have multiple avenues that can get in contact with us, we have a mailing list, like say everything that we do is GitHub, everything is issues, anything that we talk about goes into issues. We do meet every week on Wednesday. Right now is 10 a.m. UTC minus seven. I think that's probably about 7 p.m. this time, but I think what we are thinking about doing as well is we're thinking about starting up at EU meetings, so we may kind of bounce between those two. If you're interested in hosting one of these tech meetings, please do contact us as well. We're looking for people that really, you know, we are looking for people that want to drive the community here as well, because we can set up a meeting, but really it is the people that are there, that are on the ground, that really provide the context for the work that's done. We have a roadmap as well as we are on Twitter, so you can follow us, so you get news on the different papers that we are publishing, the different efforts that are going on, so you can get involved. And yeah, that's all we have for today. Thank you. So we don't have any questions online, but if you have any questions in the room, I'll run over, raise your hand, I'll run over with the microphone. So I saw a presentation yesterday talking about the different types of S-bombs and maybe some relational links between them and how they could come with packages of evidence and other things. So I noticed you had a line that says, give guidance on how people should be using, consuming these S-bombs, because we don't want to just generate them and have people go, oh, thanks, and check a box, right? Yeah. They should be machine-readable and other things. Any efforts along those lines that you're working on? So from the perspective of the CNCF, we are trying to start that up. There are other efforts that are going around in the community, so there is the S-bombs coalition, which is part of the cybersecurity group that's providing some guidance. We are going to have a workshop, so we have at the risk of self-promoting, we have this, no, it's not this one. So this is part of the coalition group. We just published a policy paper a week ago. Can't seem to find it now, but we published a policy paper about a week or two ago. So this talks about, okay, as a, this is more for like NIST OMB to provide guidance so high-level, what are the problems that we have to work on? Too many standards, distribution is a problem. What does S-bomb mean? I think it was also kind of like three of the main takeaways. And then we have kind of these specific technical problems, which is storage and distribution of S-bombs, using the S-bombs to answer the security question, implementation of S-bombs throughout the ecosystem, as well as like a clarity of what S-bombs mean. And SPX, for example, we have a, so within the SPX community, we have a built profile group, we have a defects group. So we are looking at kind of like these different pockets of documents and how they link together. But I think eventually what we're seeing in SPX 3.0 is like how to bring all these things together. So yeah, I think the S-bomb coalition is a good group from the how to consume this part of it. It is also the VEX working group, which I think is a great one to be at. That's really, how do I take S-bomb plus CV data plus VEX data equals policy engine and action. So they're looking at the action part of it, right? So VEX talks about affected, not affected. Not affected means zero, nothing to do. And if you're affected, they provide guidance on like what you have to do or how are you affected. So that really ties in to your consumption question, right? How do we eventually get to, how do we take action on these things? Yeah. Any other questions? Hi, I was just wondering if there'd been any activity in tag security and considering the use of trusted execution environments and the impacts on whatever, maybe this is something we can talk more about later, but I was just curious if there'd been anything so far. Yeah, yeah, so we talked about this and I remember like about, this is about two years ago, you know, Ava was coming in and talking about it.  So we have a couple of interesting use cases. I think one of them obviously is a regulatory use cases. I think we have a very interesting set of use cases with identity. I think the Spire community is kind of looking at that. Initially, they're looking at SGX, how do they securely provide identity into the microservice, right? I think that's a very big use case for us. I think the isolation use cases we are also looking at in supply chain. So this is something that we talked about in the supply chain reference architecture paper. But we didn't include that much in this one because the technology wasn't really there yet. So we couldn't really talk about it that much. So I think there are valid use cases. I think it'll be nice. I know that you all have done a lot of great work. I think it'll be nice to share the community. We can also help talk about some use cases, maybe write a blog post or something about. Yeah, some use cases and then kind of spread it within the community, get some more feedback and maybe get more users around that. Yeah. That sounds good. I mean, we're keen from the confidential containers side to clarify our use cases, but also to relate what we're exploring back to the documents and the work from the tag security. So I can follow up. Thanks. Go both ways. Hi, Prenton, a quick question from my side. It's also a bit in the contrast of confidential containers. Do you have ideas use cases to use HSMs? Okay. For security modules, specifically local, for security modules at scale to improve security, key management, or go even into, let me say, secure keys and rep keys. I didn't quite get all of that. HSMs, scaling key management. Exactly. Local HSMs, not specifically talking about network attached to the HSMs, but specifically locally available to, for example, for containers exclusively. Is this kind of like, you have a amount of HSM and you use PKCS 11? For example, for payment crate transactions and key management. Yeah. I think we do talk about HSMs in the cloud native security file paper. I don't think we dive deep into the different deployment models of HSM, although I think that's interesting, right? Because essentially you're creating a trap model based on the authorization of the key and who is access to it, right? So I think there'll be interesting thing to discuss. And I think we can add more guidance. And I don't know whether there would be, I guess there will be specific recommendations on like when do you want a local HSM versus a remote HSM? And it's also like, you know, the security usability leave as well, right? Yeah, awesome. Okay, thank you. Any other questions? Brandon, can you describe to everybody what it's like being in a leadership position within tag security? You see a lot of things. No, being a leader in tag security is very great. You get to talk with a lot of people. You get to see different perspectives of security. You obviously get to work with a great community. There is also like, especially in open source, you learn a lot about how open source ecosystems work. Like how do you get contributors? How do you keep contributors? What are the factors that matter? And it kind of like, for me, it's benefited me in a way that like, the way I operate in open source is a lot more intentional. Like I understand, okay, these are what matters in open source community. This is how we get there. Here are all the factors. And so like, as like, you know, initially from contributors to project leads to tag leads and to now chat, you kind of like see the different levels of it. I feel like it's a very good experience and also great networking. And I know the security reviews are extra critical within the CNCF because it helps products prepare for those code audits. And I can see that there's not a lot of security experts within the ecosystem. What is the biggest challenge when performing a security review? Is it finding people to assist or is it the technical part of that review? It is exactly the point. Like finding people to assist with the security reviews is something that has been difficult, right? We already have tried to scale down. We noticed that people that come into open source that want to work on a specific project attention span is like three to four weeks. So we've scaled down like the review to two weeks. It's really bite-sized, it's really simple. And we are looking for people and whether you're super deep, a security review can be going deep into, okay, let's take a look at what parcels they're using to kind of let's look at how they're handling security events, how they, do they have a CICG pipeline, what are they generating, the S-Bombs and things like that. And so I think it's a good gateway project because they're involved in the tech. I know that was the first project I worked on. This was initially we were starting out these reviews for like Intel and things like that. I will encourage everyone, it's a very low commitment way to like get into the tech, learn about a new project that you're interested in. And that's what I did, right? I needed to work on Spire for one of my work projects. So I was like, okay, I'll do the Spire review. And that way you get, you know, you learn about the project, you get direct access to maintainers, right? And then you make friends with them, right? You create the connections there. So yeah, I will encourage everyone to do that. I would say, you know, put it on one of the security review issues or, you know, you can contact any of the leadership directly and say that I'm interested in doing XYZ, you know, there may not be something right now, but when we, when something comes up, we can, we can talk to you and you'll get you involved in what you want to do. Yeah, let me show you how our usual processes, you know. If you wanna, if you wanna, if you are interested in doing something, you just hit new issue. Or if you want to do a presentation, new issue, get started, fill in all the details, proposal, suggestion, if you want to do something to group, you know, you can go to here, look at all the assessments, go to this, scroll down, command, and then you're set. Yeah, cool, yeah. So, any more questions? And I don't think we have any more online, so I think that's it for questions. Thank you. Thanks everyone.


How safe should self-driving cars be? This question is becoming increasingly important as companies like Waymo, Uber and others test their self-driving vehicles on public roads, but answering it turns out to be more complicated than it might first seem. Around the world, something like 1.3 million people are killed each year by vehicles. If self-driving cars could put a dent in this, it would be a great achievement. Many of these deaths are down to human error. In contrast, self-driving cars don't drink, they don't text and they don't fall asleep at the wheel. Reducing deaths and injuries from these causes shouldn't be too hard for self-driving car manufacturers, but it'll only count if their technology is so good that it doesn't end up killing or enduring people in other ways. Here, manufacturers are going to have to work hard to ensure their cars don't fall into human-like behaviors like misreading road conditions or missing important safety cues, but they're also going to have other challenges to grapple with, like sensors that fail to detect pedestrians or algorithms that misinterpret what the car sees or even machine brains that just plain make bad decisions. Because of these new and as-yet poorly understood risks, manufacturers are going to have to take great care to ensure their vehicles are acceptably safe, but this still leaves us with the question of how safe is safe enough? Human drivers are a good place to start here and where better to look than Arizona where many of these vehicles are currently being tested? It's also sadly where the first pedestrian was killed by a self-driving car. In 2016, 952 people were killed in vehicle crashes in Arizona and many of these were down to human weaknesses. For instance, 21% of the drivers involved in these crashes were impaired by alcohol, drugs or medication and 2% of them by illness, sleep or fatigue. Imagine what these figures would look like if 30% of those vehicles on the road were driving themselves. There's a chance that around 90 lives a year could be saved as long as the self-driving technology was completely safe. But what if it wasn't? What if these autonomous vehicles also ended up killing some people who otherwise would still be alive? In this case, how do we work out what acceptably safe means? One way to approach this is to use the number of fatalities per billion miles traveled. In urban Arizona, there were 518 people killed by cars in 2016 or around 11 people killed per year for every billion miles traveled in the state. This is equivalent to around a 1 in 13,000 chance of being killed by a vehicle each year if you live somewhere like Phoenix. Maybe this should be the benchmark for self-driving cars or maybe a slightly lower number, say 8 deaths per billion miles traveled. This sounds like a reasonable target. The only problem is it's not that easy to prove if and when it's been reached. According to research from the RAND Corporation, if a company had a fleet of 100 vehicles driving around the clock and wanted to show a 20% improvement in car-related deaths somewhere like Phoenix it would take around 15 and a half years of testing with no fatalities to achieve this. Things look even worse if a tighter standard of a 20% improvement in pedestrian deaths for self-driving cars compared to human drivers is used. In this case, it would take closer to 53 years of death-free testing with 100 vehicles on the road. These sort of timelines are clearly unworkable for demonstrating safety. Ironically, they're so long because relatively few people are killed by cars compared to the number of miles driven in the US and so it takes a long time to build up statistically significant data. An alternative approach is to rely more on performance standards that ensure self-driving cars are designed for safety under the toughest of conditions and to monitor for early warnings of potential failures, ideally before anyone's killed. And because this is an evolving technology such performance standards should evolve along with it. This would help develop the technology safely while not slowing it down unnecessarily but on the way there will inevitably be crashes and this is where regulators and manufacturers need to start working with local communities so that they can work together on what being acceptably safe actually means. For instance, it may be decided that testing around residential areas is OK but not around schools or it may be agreed that testing where pedestrians are likely to be paying less attention college campuses for instance is not such a good idea. On the other hand, it may turn out that local communities are pretty risk tolerant when they see the potential benefits, you never know until you ask. The bottom line is that while self-driving cars could make roads safer if the technology is developed responsibly it's up to manufacturers, regulators and everyone else affected by them to decide how safe is safe enough and what they're willing to risk to reach the benefits the technology offers.


Hello and welcome to the session. In this session, we will learn about relations and their representation. First of all, let us review what is order pair. Order pair is a pair of objects whose components occur in a specific order. It is denoted by, that is, the elements which are related are put inside the parenthesis and separated by a comma. For example, the order pairs are 1 1, 1 2, 2 1. Now, let us review what is a relation. A relation is a set comprising which satisfies a certain rule. Now, let us take some order pairs 1 1, 2 1, 4 2 and 3 1 and let the relation r is equal to the set containing order pair x y such that x is greater than y. Now, the order pairs which are satisfying this relation in order order pairs, the first component is greater than the second component. And here the relation is mentioned to us as the set containing the order pair x y in which the first component is greater than the second component. So, the order pairs satisfying this relation are 2 1, 3 1. So, we can write r is equal to containing the order pair 2 1, 4 2 and 3 1. Therefore, the relation is a set of order pairs which are satisfying a certain given rule. Now, the components of the order pairs is called equal to the set containing the first components of the ordered pairs. So, it is a set containing the elements 2, second components. So, it is equal to the set containing the elements 1, represented by Osterfaq error driver in the equation form. Now, let us take a relation which is equal to the set containing the order pair x y such that x is equal to 4 y are natural numbers less than 10. We have to find first of all the order pairs which are satisfying this relation by our natural numbers less than 10. So, first of all for y is equal to 1, we have x is equal to 4 into 1 which is equal to 4. So, for y is equal to 1, x is equal to 4. Now, for y is equal to 2, x is equal to 4 into 2 which is 8. So, we are getting for y is equal to 3 into 3 which is equal to 12. Now, in this case we do 12 but here it is mentioned that x and y are natural numbers less than 10. So, we will not take this case and we will take only this relation in the Roasterfaq relation r as the set of ordered pairs. So, here r is equal to the set containing the ordered pairs 4, 1, equation r which was given to us and this is the representation of this relation r in the Roasterfaq. Present this relation by an error diagram on one side. Now, domain is the set of the first components of the ordered pairs. So, it is 4 and 8. So, we are writing 4 and 8 here and the range is the set of the second components of the ordered pairs. So, we will write 1 and 2 here. Now, in the error diagram add and connect it by arrows. So, it is related with 1. So, we will connect 4 and 1 with arrow and 8 is related with 2. So, it will 2 by 2 4 times 2. Now, let us see how to represent this relation equation form. The second component that you can see here equation form, we can write this relation as the next is to represent the relation by a rule. Now, the relationship. Now, here the second component is this component is 4 times y. Therefore, we can write. So, this is the relation we have learned about. We have enjoyed the session.


Hi guys, welcome back to this YouTube channel. This is Daniel Rosal here bringing you this video tonight from Jerusalem. I wanted to record a video about this YouTube channel actually and what kind of iteration is going to be put out here. Now the subscriber count at the time I'm recording this is 365 so by the standards of YouTube this is a diminishingly diminutively minno minno tiny tiny channel. So it's very small. I don't show that number because I feel like it's kind of puts me under a bit of pressure when I know everyone can see that and they see it's bouncing up and bouncing down a little bit so I just keep that number to myself for the moment but that's the subscriber count. Last night I was cleaning trying to attempting to clean up this channel a bit adding descriptions where they were missing and creating some playlists and something that really struck me as I was doing that is that there is really no coherent theme whatsoever to this YouTube channel. So if people have subscribed and you're kind of expecting there's going to be a focus here just an FOI there is there's going to be no focus and I just want to explain just for once I've mentioned this in a couple of videos what I'm doing here with this YouTube channel. There's a few reasons I decided to finally get going with YouTube and start putting some videos up here on the internet. Reason one was I've been mostly involved professionally up to recently in writing that's like my thing that's what I get paid to do in substantial part by my clients and growing up I was actually quite interested in video I used to play around with Lego cameras with a friend and it's just been something I've really wanted to get back into for a while so that's reason number one. Professionally as a marketer I see video as being really really where it's at or where it's going at least so that's another reason I just kind of feel like it's a very important skillset for content marketers to have to know how to edit video to know a little basics of production. I'm learning these every single day and enjoying that process a lot and the third reason is this is just fun for me to do this I'm just sharing things I know and I discover and I do have a lot of quite different interests which is probably why this channel has been varying so far I'm interested in technology and Linux and cloud computing I'm also interested in backups I live in Israel and I've done some videos showing both my local surroundings and also things I discover how to do in Israel that I think might be helpful for people and I've a boatload of other weird interests there as well so that's kind of reflected in the channel going forward if I get past this kind of learning phase and get more focused I might actually run a proper YouTube channel that's got a niche and whether that's about Israel or tech or marketing that's definitely something I'm sort of shooting towards but this channel for now for the time being is going to be pretty much stream of the YouTube equivalent to stream of consciousness I just whatever I have to say goes up on this YouTube channel and therefore it's really really mixed bag so I just want to put that out there for people who have subscribed and are wondering what is this about what kind of videos are we going to be getting that is the answer there's going to be a lot of it's a it's a mixed bag to say the least so for those who have stuck with the channel so far just wanted to say thank you I really enjoy getting comments from people and people also send me emails which I love because I'm a massive email fan email is like always my favorite form of communication an email address that would reach me is in the about tab so if anyone has any questions or we just like to say hi feel free to drop me an email always sort of makes my day when I'm working to just get an email from someone on the internet and make connections that's what's so cool about YouTube is it can just bring people together across continents and I'm enjoying that aspect of it too thank you guys for watching more videos coming soon


Okay, welcome back everybody. Before we move on to a new topic, this is a summary slide. Again, just trying to pound this information into your heads. Amino acid molecules are connected to each other to make protein molecules. That's all we've been talking about so far. Amino acid molecules that are connected in this way are sometimes called polypeptides, usually called protein molecules. The new topic here is essentially biology. What do protein molecules do? Well, they do anything and everything in the cell. If you can think of a job that your cells need to do, there is probably a protein molecule that is devoted to helping out or doing that job. Just some examples. Your cell is basically like a room or a house. There have to be beams that hold the ceiling up and hold the roof up and things like that in your house. Well, there are protein molecules that help keep the cell to be a certain shape. In other words, there are protein molecules that help prevent the cell from collapsing on itself. That's one job that a protein molecule might do. There are other jobs that speed up chemical reactions. Molecules in living cells that speed up chemical reactions have a special name. They are called enzymes. We will talk about that in a later video here. Some examples of enzymes. There are enzymes that carry other... So there are protein molecules that carry other molecules around in the cell. That might be the job of a protein molecule that pick up another molecule and take it somewhere. There are protein molecules that are involved in copying your genes. Whenever your cells divide and each new cell needs a copy of your genetic material, there are protein molecules whose job is to help make those copies. That's another job. There are protein molecules that help make your muscles move. Obviously, that's a job. There are protein molecules that carry oxygen from your lungs to other parts of your body. You may have heard of this particular protein molecule. It is a molecule. It is a protein molecule called hemoglobin. Hemoglobin is a special protein molecule whose job is to pick up oxygen from your lungs and carry it to other parts of your body that need the oxygen. That's just another job that a protein molecule might do. And there are many others. The punchline of this slide is that there are many different types of protein molecules and each type has its own special job. Just to talk about human proteins in more detail, the estimate is that there are about 25,000 different types of protein molecules that humans can make. So every one of your cells is basically capable of making about 25,000 different types of protein molecules. Each type has a specific job that it is supposed to do. Now for any one particular cell, if you have a cell on your skin, it's probably not going to make all 25,000 different types.  And if you have a heart muscle cell, it's going to make a different collection of protein molecules that to help it, to help the heart muscle do whatever heart muscles do. Again, each type of protein molecule has a different job. The thing that makes protein molecules different from each other is the order and the type of amino acids that you connect to each other. For example, if I connect a proline amino acid to an alanine amino acid to a glycine amino acid, that is a very tiny protein molecule. Probably doesn't really have a job. I just made it up, but maybe if I connect these amino acids in this particular order, then that protein molecule might do one specific job. If I connect different amino acids in a different order, I might make a protein molecule that does a different job. The type of amino acids and the order that you connect them in has a special name. It's called the sequence of amino acids in your protein molecule. So if I had these particular amino acid molecules connected to each other in this order, and I said what's the sequence of the amino acids in my molecule, you would say, oh, it's proline connected to alanine connected to glycine. Usually you'd put a little M there and a little C there from a previous video. So that's what sequence of amino acids means. It means the kind of amino acids and the order that you connected them in. The only thing that's really different about those amino acids is the side chains, right? All the other parts of the amino acid molecules are identical. It's basically the order that you connect the side chains to each other in that makes different protein molecules have different jobs. Now, on this particular slide, I'm just going to try to show you an example of one specific type of protein molecule doing its job. This weird picture here, this is a frog embryo. Each of these things that I'm circling here, these are cells inside of the frog embryo. So this is very early on for the embryo. If this got enough food and the cells divided enough, this would eventually turn into, I guess, a tadpole, then that turns into a frog. But right now it's just basically a blob of cells and just to orient you some more, right? This is one cell, that's another cell, another cell, et cetera, et cetera. These yellow things, these yellow stuff, is the DNA inside of each of the cells. So this is little froggy DNA, this is froggy DNA, et cetera, et cetera. The blue things that you see, this blue stuff here in the cell, those are one type of protein molecules, many, many copies of the same type of protein molecule. The job of this particular protein molecule is that when this cell divides, this blue protein molecule is going to yank one of the copies of the cell's DNA to the new cell. So if there's going to be a new cell that forms over here, these blue molecules have to pull one copy of this yellow stuff, one copy of the DNA over into the new cell. And these blue molecules over here, they have to pull on one copy of the DNA and yank it into the new cell as well. And basically, that's the job of these blue protein molecules. They have one specific job, it's to pull the DNA into the new cell, so that every new cell gets the correct amount and the correct type of DNA that all the cells need. And I'm just going to show you a video of that. This is a time-lapse video of the frog embryo cells dividing, and you can see that you'll be able to see the DNA getting yanked into the new cells. It's probably good to focus on this one over here. You can see that they got pulled, that yellow stuff got pulled in opposite directions. I think it'll repeat. Here it is repeating, so this cell is going to divide, and then that yellow stuff gets pulled in opposite directions because the blue molecules are pulling it. The blue stuff that you're looking at in those cells, that's just one type of protein molecule. There are thousands of others running around in each of those cells that are doing other jobs. You just can't see them because whoever made this video found a special way of highlighting just one protein molecule. Like I said, there are many other types of protein molecules in those cells that you just can't see that are doing other jobs. And this is the last slide in this particular video. There are other videos coming, but this is the last slide for this video. This is just kind of a silly mind game, but here are two words you may have heard of these before. Usually students have heard the word rabies before. That's a disease that you can get from certain animals. That's not the greatest disease for people to get. Serbia is certainly not rabies. It is a country in Eastern Europe. But the point I'm trying to make with these two words is that they are made of the same letters, but they mean different things because the letters are arranged in different ways. With English, we have 26 letters in our alphabet. But we can make hundreds of thousands of different words with just 26 letters, and each word means something slightly different usually. But the only thing different about the words is the way that we arrange the letters. If I arrange the letters this way, I'm talking about a country in Eastern Europe. If I take the same letters and I arrange them in a different way, I'm talking about some disease. The point that I'm trying to make here is that you should think of the amino acids. How many do we have universally? We have 20 of them. You should think of the 20 amino acids as kind of like letters, like letters in our alphabet, and the way that you connect the amino acids to each other gives you different protein molecules in the same way that we connect letters and we get different words that mean different things. Different protein molecules have different jobs. What do I mean by different molecule? How are they different? They're different in the way the order that the amino acids are connected to each other in. For example, I'm using the three-letter abbreviation here. If I take valine and connect it to leucine, connect it to serine, proline, alanine, and keep going, I will make hemoglobin, which its job is to carry oxygen from your lungs to other parts of your body. But I only get hemoglobin if I connect these amino acids in that particular way. Hemoglobin keeps going on. That's what the dot dot dot means there, but this is the beginning of it. If I connect different amino acids in a different order, if I connect lysine to lysine to glutamic acid to glutamic acid, etc., I make a protein molecule called myosin which helps your muscles contract. And on and on and on. If you connect the amino acids in a different way like this, you make a protein molecule that helps to copy your DNA. I'll stop with the examples there. The point I'm trying to make here is that each different type of protein molecule has a different amino acid sequence. And again, sequence just means the order that the amino acids are connected in. And different sequences give you different behaviors for the protein molecules, give you different jobs. The fancy way that chemists and biologists say this, they love saying this, is they say amino acid sequence dictates function. That is just a fancy pants way of saying the order that you connect the amino acid molecules to each other in controls what job the protein molecule does. That's all it's saying. But you might hear that. You might hear that in A and P for all I know. And that's the end of this video.


By transcription, Bidwell McCormick takes you behind the scenes in Hollywood. There doesn't seem to be anything that escapes glamorizing in Hollywood. No matter what it is, sooner or later, they'll get around to making it appear more attractive. Well, the latest subject to undergo the Hollywood glamour treatment is ice. Yes, ice. The kind you skate on. For a recent picture, they needed pretty photogenic ice. Oh, the kind needed for Sonya Haney's picture. It's a pleasure, which was recently made in Technicolor. Yes, that's it. So the studio set out to glamorize the ice. Now, how on earth could ice be glamorized? Well, first, the freezing base was painted a brilliant green. Then, after water had been turned in and frozen solid, the color showed through and it looked mighty pretty under the powerful lights. However, when the first skater took off, it left a white trail behind him. Multiply that trail by 40 skaters, all crisscrossing, and it's easy to imagine how quickly the ice would become de-glamorized. Then that was the cue for the technical crew to get in the bright idea, huh? Yes, they first raised the temperature a little to melt the ice to a depth of about a half inch all over the rink. That accomplished the crew of workers equipped with spray guns, loaded with a vegetable dye, literally painted the ice itself. Then they froze everything solid. When they were finished, the skating surface was prettier than ever, and what's more, the skate marks didn't show on the thin layer of ice and it all photographed beautifully. Here are a few briefs about what the stars are doing. Boris Korloff will star in a picture titled Chamber of Horrors, inspired by Hogarth's famed drawing Bedlam. Dick Powell, currently on the nation's screens as co-star of RKO Radio's Murder My Sweet, will star in Cornered. This will be his second character role since he foresoaked crooning parts in pictures. Rohyd, story of a cowboy's rehabilitation in the most colorful period of the west, will continue the combination of John Wayne as star and Edward Demetric as director, which currently is making back to Batan. Tom Conway and Audrey Long will play the leading roles in RKO Radio's The Lie Detector, romantic comedy drama. New product of international pictures will include Gary Cooper's Western, along came Jones. Tomorrow is forever, starring Claudette Colbert, Orson Welles and George Brent, and the Sonya Haney Technicolor film, Countess of Monte Cristo. Philip Terry, currently featured in the gay romantic comedy with music, Americana, looks Irish, sounds slightly English and was born in San Francisco, spent his boyhood in the oil fields of Oklahoma and Texas. He likes clothes, but isn't foppish about them. He majored in English Literature and Math at Stanford, where he was a member of the Kaisai fraternity. He made good grades without studying too hard and became interested in acting through campus theatricals. Philip Terry is courteous and a little shy around strangers, slow to make friends but responsive and warm once he feels he knows people. Climbing ladders bothers him because height makes him nervous, and yet oddly enough he's a licensed pilot and a good one, passed his tests with unusually fine grades. He likes English and continental cooking, doesn't care particularly for hunting or fishing, has no yen to retire to the country or even live anyplace but a metropolitan area. His screen tastes run to the heavily dramatic. He's an avid football and track fan, follows Stanford's athletic fortunes closely. He studied the classics and modern drama at the Royal Academy of Dramatic Art in London and toured the provinces playing stock. Philip Terry landed his first film contract by a screen test at one studio who turned it down but through an error sent it to another who signed him the following week. He calls Mrs. Terry, who is better known as Joan Crawford, twice a day from the set. But if you want to make him flair, refer to him as Mr. Crawford. And now a word from your local announcer. By transcription, Bidwell McCormick takes you behind the scenes in Hollywood. Securing the props for a motion picture production is a gigantic task and has to be started long in advance of the actual shooting schedule. There was a case, for example, of RKO's radio screen version of Pearl Buck's novel, China Sky, which was assigned for propping more than a year ago. Yes, and even before that, Gene Rossi, RKO property man was preparing notes and collecting props against the actual time when they would be needed. For instance, such items were secured as a real hand-pumping fire cart, the kind which was used during the early days of the Jap attacks on Shanghai. That cart, I understand, had to be brought to this country by a carnival which fled the Orient. Yes, and the Chinese carrying poles had to be secured, the kind on which the Cooley's balance loads for carrying over their shoulders. And real Chinese baskets had to be secured and laid away against the time they would be needed. A bamboo dipper with cherry wood handle, a Chinese water bowl and bathtub were some of the other items supplied, and they all had to be genuine because they're bound to be someone and often many in the audience would notice a difference. Hollywood's storage rooms are chock-full of quaint and interesting pieces. Many of them are not used for years at a time. And now here are some news briefs from the studios. Skinny Ennis has been signed for RKO Radio's musical, Radio Stars Unparayed. Back to Batan is the final title chosen for the John Wayne starring story of guerrilla warfare hitherto called the Invisible Army. Lee Harline has completed the music for Bouquet of Lace, the feature ballet number in George White's Scandals of 1945. Joan Davis and Jack Haley will sing, I Wake Up in the Morning and It's You. Voice of Japan's premier, Kuniaki Kouiso, will be heard in RKO Radio's First Man into Tokyo. A transcription of the voice exhorting Japs to sacrifice everything to repulse the enemy has been secured by producer J. Robert Bren. It will open the story. Definite and final plans for Danny Kay's next picture initiated by Samuel Goldwyn before his departure for Europe and completed since his return were announced by the producer. Goldwyn stated that the kid from Brooklyn starring Danny Kay would go before the cameras in Hollywood within the next few weeks. Randolph Scott, big blue-eyed and six-foot-two, learned to ride to Fox and Hounds in Virginia. He's had a lot of adventures in sports such as clinging for hours to an overturned sailing boat in shark-infested waters near the Bahamas, but he modestly says, of course I'm not the adventurous type in private life. You're likely to overlook Randolph Scott's versatility on the screen. He's probably at his best in roles such as that of a love-muddle doctor in Pearlbuck's China Sky, a romance in which he overlooks the charms of Dr. Ruth Warwick at first, though she's right at his side in a remote China village, and he falls for Ellen Drew in far-off America. Scott's personal romantic history may have no bearing on such oversights, but to look at him you'd guess he might be the fellow to do just that sort of thing. Follow a principle, right or wrong, and admit his mistakes, if any, later. Observers of Randy's private life in Hollywood point out that outside of his working hours he's living the life of a southern gentleman just as though he'd stayed in Virginia. He even had a plantation in San Diego County for a while, but sold it when labor couldn't be obtained to run it. He now lives on a big beach mansion which norm a townage formerly owned. Scott takes an early morning swim in the ocean regardless of season or weather, finds time for a lot of golf with his friends Kerry Grant and Fred Astaire. His domestic life is happy. He's now married to pretty youthful Patricia Stillman of San Francisco. Randolph Scott is very democratic in his taste in literature, art, and in the people he likes. His modesty has buried in the past an excellent school athletic record, and he can still start on most folks by his ability to kick and pass a football. An hour word from your local announcer. By transcription, Bidwell McCormick takes you behind the scenes in Hollywood. Colored water has always been used on the Hollywood movie sets in place of wine or hard liquors, but now a substitute seems to be needed for cigarettes. I understand that Columbia Studios resorted to corn silk recently when they had to film so many scenes in which cigarettes were smoked in the Irene Dunn Alexander Knox picture over 21. Well, that's what I've been informed. On account of the studio's fast dwindling stock, a new system was worked out by the property department whereby cigarettes were hand rolled, and only the outer one-third section was actually tobacco. So that's how the corn silk came to be used, hm? That's the way the story goes. Studio experts recommended that the remaining space be filled with corn silk because a survey showed that in 99% of all movie scenes, cigarettes are only smoked for a few puffs anyway. When Chester Morris and George E. Stone had to do a jitterbug number for a scene in the new Boston Blackie film, Surprise in the Night, the studio assigned Jewel McGowan, former California State Jitterbug Champion, to coach them and act as their swing advisor. Jewel spent a couple of hours teaching them the proper steps and the rhythmic cavorting. I think I have it clear in my mind, panted Morris at the end of the instruction, but I'm not so sure my feet understand. Convinced that there's nothing an actor worthy of a name shouldn't know, Patriarch Charles Coburn, who's been a trooper for more than half a century, is putting his spare time between scenes on Columbia's Over 21 to good use and he's learning to do the Samba. Shirley Temple will be the model for a national comic strip. William Henley, New York cartoonist, disclosed in Hollywood recently. Henley has been commissioned to draw the strip, which will be based on the character of Coralus Archer in Kiss and Tell for newspaper syndication. Cornel Wilde has found Douglas Fairbank Sr. an inspiration for his last two movie roles. In order to get atmosphere for his part of Aladdin in Columbia's Technicolor Fantasy of Old Baghdad, A Thousand and One Nights, Cornel purchased a 16-millimeter print of Doug's old silent film, The Thief of Baghdad. Recently, when Cornel was cast in the bandit of Sherwood Forest on the same lot, he sent out an SOS for a print of Fairbank's Robin Hood. Born in New York City, October 13th, 1915, Cornel Wilde crossed the Atlantic a year later with his family when his father was called home to Budapest to join his regiment as a captain during World War I. In the Revolution, which subsequently ravaged Hungary, Cornel remembers a harrowing ride in a horse-drawn cart bound for a refuge in Budapest. Soon afterward, in 1920, Captain Wilde managed to obtain passports to return to his family in the United States under the immigration quota. Cornel advanced through grade school, New York Townsend Harris Hall High School to Columbia University and then to City College for pre-medical course, finishing the three-year curriculum in two and winning a scholarship in the College of Physicians and Surgeons at Columbia University. But his career in medicine faded as he became active in the Theodore Irvin School of the Theater. He gave up his scholarship to join a stock company at Segerty's, New York. Next came Moonover Mulberry Street. When the company went on tour, Cornel dropped out to go into a theater guild production. Love is not so simple in which he played opposite Ina Claire. An engagement in Romeo and Juliet brought him to Hollywood where he went to work for Warner Brothers, after which he went on contract to 20th Century Fox, which company his contract is now shared by Columbia. Cornel Wild will shortly be seen in A Thousand and One Nights and The Bandit of Sherwood Forest. And now a word from your local announcer.