What is Filipino design or is there one at all? The question of Filipino design has much to do with the question of Filipino identity. And, again, it begs the question, is there one at all? Or we may be prompted to ask, is there really a need for any? In this tightly integrated world where everyone can, when sheer will to do it, communicate with anyone in real time anywhere in the world. So can we leapfrog from wrestling with this issue of Filipino identity to embracing an international global identity instead? To many, this might be a trivial question since we in the Philippines is an open society and they are ubiquitous signs of global integration. Yet, to many, failure to define or develop one will lead to disenfantricement, social chaos, cultural dissolution and economic despair. Far-fetched? I will not venture in directly addressing the issue of Filipino identity but will endeavor to show how Filipino design is one window where we can catch a glimpse of it. There are free agencies that I would like to focus on in the way that they are engaged in undertaking design-related activities in our country. These are education, the industry and the state. Forming our cultural mindset start in the way we are taught in schools but the elementary and school curricula do not provide the platform discussing the multi-culture characteristic of the Philippines and the arts and artifacts that signify this. There is very little or no opportunity to create or participate in creative work or develop styles and techniques in enhancing existing artistic and design endeavors. The K-12 program notwithstanding its art and humanities track does not offer this opportunity either but is more directed to training in employable skillsets rather than creative development. These conditions provide a narrow perspective of the arts and culture of the different linguistic and cultural groups that determine the Filipino. They do not offer the opportunities inspiring and developing the artistic and designing skills of the youth. In the design area, the empowering quality of education does not contribute to their participation in criticizing the built environment including its attendant furnishings, accessories and means of conveyances. Does the learning environment foster problem-based learning or collaborative work? Does it engage the students to work with the community in solving community problems? The lack of this deterred them from critical and to be engaged in creative problem-solving examples. With the gypny, the interior space simulates communal interaction. Good, including the collection of fares facilitated by the exchange of coins perhaps or bills. But does anyone question comfort levels or the tweak up audio that's really searing to the ears or the acrid diesel smell or the acrid diesel fumes? Sidewalks and walkways, for instance. If they're even present, this sidewalks and walkways, for instance, if they're even present, does anyone resent its sequestration by private homeowners or its abject and maintained state? This state is a large stake in education but I would like to touch on state policies that are partial to economics apart from its educational policies. I would like to cite state policies that influence design trading and practices. Let's start with postwar Philippines. Postwar Philippines saw the unrestricted influx of American products following the implementation of the Belt Trade Act also known as Philippine Trade Act. This did not help develop local goods since it restricted the Philippines from creating products that compete with important American goods. In reaction to the marginalization of Filipino business, the administration of President Carlos Garcia in the late 1950s implemented the Philippine First Policy that provided preferential treatment to Filipino businesses, products and services. This led to the growth of manufacturing sector with industries in import substitution creating new jobs and training in new skills. This would have been a strong driver for design development but this growth trajectory was fueled by dependence on imported raw and semi-processed materials. With the decontrol of the Philippine Peso exchange rate, manufacturing became too expensive and by the 1970s industrial production took a nosedive. Foreign debt mounted and unpaid debt had to be paid with debt, paid with much higher rates. So industrial projects such as the illegal steel and the Lissaldi steel rolling mills had to be aborted. The Marcos administration removed heavy industries in its priorities plan and gave emphasis to labor-intensive export-oriented industries. This is also known as the LIEO industries. By 1979, all major Asian countries have developed their basic industry but the Philippines had none. And so noting that the Philippines can't move forward without developing its basic industry sector, the Marcos administration proposed 11 major projects in the areas of manufacturing, agriculture, and power generation. But hostage by world bank debt and its influence on national policy, this were not pursued. The policy of creating labor-intensive products at the export market continues to this day. However, an opportunity for a design-led development strategy may still be forthcoming. The latest State Act, which is the enactment of the Design Act or the Design Competitiveness Act of 2013, also known as the Republic Act 1057, states, and I will read, it is the declared policy of the state to enhance the competitiveness and innovation of Philippine products, create market-responsive design services while advocating for economic and environmental sustainability. The state shall also endeavor to promote the economy and society driven by design and creativity, responsive to our fast-changing times reflective of the Filipino culture and identity while concurrently advocating the protection of intellectual property rights to these ideas and innovations. Big words on how to make this real. This is a challenge now. And so, perhaps we could take a look again at our educational system and we could see that cultural practices, the arts and artifacts that are produced out of these practices must be studied by all Filipino students. They must be provided with creative environment where they can express and they could practice their own crafts. They must learn how to work in communal projects among persons of different persuasions. To expand their knowledge and interest in many facets of life, they must be involved in community projects. They had to immerse themselves in working with communities and in so doing, this is the only way that they could actually learn. Knowing and practicing are the only means of empowering them to be engaged in design issues and be equipped to creatively solve problems affecting their communities and larger environments. Producers of creative works must be familiar with indigenous and foreign technologies as tools for creative thinking. Concepts can materialize without the necessary tools that will be aids in their creation. Students must develop creative thrust fueled by research. This is the only way a culture of innovative designers can flourish. On the side of the industries, industries must be developed so that there will be a mechanism that will feed the manufacturing train. Without the basic industries, even the metals, plastics and textiles, manufacturing of products for the local and export market will not grow. In fact, it will diminish as it is diminishing now, right now. We will still be import dependent and design will not thrive in this environment. These industries must be driven by sustainable technologies. And if we say sustainable technologies, they can't easily be derailed by external market forces since sustainable technologies may be both appropriate and building edge since we're talking here of a sustainable technology in the sense that it greatly depends on human resources in operating these technologies. There's the cultural scene. The Philippines does not lack cultural events. They do not lack festivals. We do not have the earth of these since we are so much in love with fun. And we project in these events multiracial and multi-cultural diversity of the Filipino. But lacks perhaps are events that are integrative and collaborative. What lacks perhaps are events that are integrative and collaborative so that incrementally a sort of fusion may arise that a greater set of stakeholders can open up to. There are inspirational references to Filipino culture and this must be preserved. But their distinctiveness is also the source of segmentation in the identity part of the issue. And that's the question. Is there a Filipino design? I believe there are Filipino designs and they may still be attributed to particular segments of the social cultural scene. But in knowing the roots of Filipino culture in collaborating in a communal effort to solve common problems in working within the Filipino cultural context and in pursuing research-led research practice this may not even be an issue. Filipino design will emerge. I am certain it will be distinct and it will reflect the interweaving of the fabric of Filipino culture.


All right, welcome back. I hope everybody had a great lunch. My name is Thomas Graf. I'm C2N co-founder of iSurveillance, but probably more importantly, one of the creators of Cilium and a maintainer of it. To me, I would like to share my thoughts on how we, I think, should be securing infrastructure going forward by combining network security and runtime security together. Because Cilium already has a partial answer for this, because if you look at the Cilium ecosystem overall, it actually consists of multiple projects. Most of you know Cilium as the CNI, as a Kubernetes networking solution. Some of you may have seen the Tetragon talk this morning talking about runtime security and point security, defining rules on what a process is allowed to do and not to do. We, of course, also have Hubble from a network observability site and Cilium service mesh to offer service mesh features. In this talk, we will focus on these two projects, Cilium as a CNI, implementing network policy and mutual authentication, as well as Tetragon for the runtime enforcement side. For those of you who have not seen the Tetragon talk this morning, so what is Tetragon? Tetragon is a project as part of the Cilium family and it offers security observability as well as runtime enforcement. What does that mean? It means that we can run Tetragon as an agent on any Kubernetes node and it will install EBPF programs to extract telemetry from the system such as what files are being accessed, which system calls are being done, what network calls are being done, when does a container escape from its namespace, what sort of privileges or capabilities is a process run with and so on and can export that via logs, traces or metrics into whatever observability stack you're running. And it can then furthermore take policy where you can define what processes are allowed to do. For example, if it attempts to read or write certain files, you can kill the process or you can say this process shall never take particular capabilities or maybe it should never run with root privileges and so on, that's Tetragon. I'm sure most of you are already also familiar with what Scylium can do from a network policy perspective. Of course, Scylium implements Kubernetes network policy. That's what we see on the left side here. Kubernetes policy allows us to define intent declarative labels or policy based on labels defining what pods can talk to what other pods, right? It does so on the granularity of a pod. We also have, we've heard this in the keynote this morning added mutual authentication to Scylium where we can not only enforce this on the network level by either allowing or disallowing particular packets, we can now also perform a mutual authentication handshake using MTLS to mutually authenticate the identity of pods before they allow to talk to each other. But again, this is done on the level of a pod. So we can only think about things right now, pods. A frontend pod talking to a backend pod or a fluent D pod talking to some other pod. The granularity is on the level of a pod. That's what both network policy as well as service authentication have been defined to work with. Well, the reality is that Kubernetes pods are actually quite complex or they can be complex. We often think a pod is a little bit, we see on the very left here, it's a pod and there is one container running inside and that's it. And in that world, the net or policy implementation that we have today would be fairly decent, right? But the reality is that we actually have pods with multiple containers running inside, multiple volumes mounted in, a pod has a complex inner life. By the way, this picture is from the Kubernetes IO documentation. If you wanna dig deeper into why that is, you check out the Kubernetes documentation. This is one such example from that documentation, a very, very basic example of a sidecar, a logging sidecar. So we have a workload that's running as a container in that pod and we have a secondary container in that pod that performs the logging operation. You can see the YAML on the right side on how that it's actually done. That's a very classical, typical use case. And that's even a basic one. So let's look at a bit of a more complex, practical example. And let's look at what TetraCon can offer us here, what's actually going on. And don't worry, I will now digest this picture, what we're actually seeing here. We're actually seeing the inner life of a pod. So let's jump in and look at this. We of course see that there is a namespace name and the pod name. So far so good. Then we see a process called init. That's the init process on the Linux node, pit one. We then see the container runtime, which was started by the init process. In this case, that's container D.  So this entire blue service area, that's the Kubernetes pod, which is named crawler. And it actually has a node application running inside. But you can see that there's a lot more going on in that pod. So let's look even closer. We can first of all see that the actual node app, that's the binary running in the app, that's the actual workload that's running in there, is making two network connections. It's reaching out to api.twitter.com and it's reaching out to an elastic search service. But then we also see another line, which is invoking a shell and it is using netcat. That's the NC binary that you see in there. That's a reverse shell that was installed. So somebody compromised this workload, the node application and was able to sort a shell and then use netcat to reach out, to then receive instructions back in to do something inside that pod. That's a classical reverse shell attack. And then we also see a lateral movement attack because this shell, this reverse shell is now used, again with curl to access the elastic search service to probably extract data from that. And that's of course allowed because this curl process is running inside of a pod that's supposed to talk to the elastic search service. So if we're looking at this from a pod level, the network or the network policy construct does not make a difference between the actual workload that's running in there and the curl binary that's running inside of that pod. They're both the same path. They have the same identity. They have the same IP address. On the network level, this will simply be allowed. And then last but not least, we also see data exfiltration where the attacker is using curl to probably copy the data that they have received from elastic search and upload that onto an S3 bucket. That's kind of a snapshot of a successful attack that was performed in a Kubernetes cluster and it's showing how complex the inner works of an actual Kubernetes parties and that while using our policy is fantastic, way better than not doing anything, we can actually do better as we look into this. Hence the idea and the thought that in the future, we will combine the network enforcement capabilities that Sillim already has with the runtime context. So this visibility was extracted with Tetragon. So Tetragon has all of this context. How can we bring those two concepts together to provide even better security? So let's see how that actually looks like in practice. How could you as a platform operator or as a potential application developer actually look at this and configure this? And we'll start fairly simple here by looking at the most simple example, frontend pod talking to a backend pod, right? And we give them both IPs, 10, 0, 0, 1 and 10, 0, 0, 2. And right now they're just running one container each, the actual frontend and the actual backend application. At some point the application developer may decide, I want to start now to log certain things into FluentD. So they will actually run a FluentD container. It's great, that's one, a bit of YAML and the image is running in there. Well, in reality, you're now already running a third-party image as part of your application. You're not actually, you haven't developed this FluentD image, you're just using third-party software. It's great, but it's not really trusted, right? You're now accessing the logging pod. Well, this looks pretty innocent, but you have already created a situation where the FluentD container could also access your backend now. That's not desirable at all, right? Like FluentD could be doing whatever, it could be running whatever code you may be running or updating that dependency all the time. You have granted access to the FluentD container to the backend pod because the frontend container obviously has to talk to the backend container, right? We definitely don't want this. But let's get a step further and think about more sensitive data. So let's say your backend pod has to talk to a database. It's running outside of Kubernetes, right? And in order to access it, you need to have a certificate, right? So you need to fetch a certificate. So a very common practice is to use an init container to actually pull the certificate from a certificate server so it can be used by the backend container to talk to the database. Great, but again, this is unintended consequences that the backend container can now also talk to the certificate server and the cert init, the init container, can also talk to the database. And the cert init may just be a bath script, right? And it may not be reviewed as thoroughly as other code, but it could actually directly access the database. So we definitely don't want this. And then when the developer decides now my backend also needs to log, of course, we're adding a FluentD container. And you can see the pattern as applications on Kubernetes evolve, complexity of parts evolve, evolve, evolve, and more and more containers are being added into parts. I've seen constructs with more than 30 containers inside of a part, right? Like very complex. They're all meant to do something, right? But very thought has been given to actually granting least privilege access to these containers. Of course we want to prevent this, right? But can we take this one step further? I mean, if we could implement all of this, that's already a giant step forward, right? If we could have identity at the level of containers instead of just parts, we would be significantly more secure in general. But can we do better, right? Can we actually use the full potential of Tetragon? Let's look at that. So let's simplify our example. We're down a little bit, remove the logging part and actually look a little bit closer to what's actually going on inside of a backend container, because there's an actual binary running inside of that container. I've used slash user slash bin slash backend in this example. That's the actual binary that's stored in the container that's being executed, right? Well, what happens if that backend part, that backend binary gets compromised? An attacker might be able to spawn a shell. So this bin SH shell binary will now run as a child process of the backend binary, right? Obviously, we want to avoid that this shell can access the database or the third server. So what we want to shoot for is not only allowed to actually leverage and allow enforcement of the container level, but to actually encode the binary names inside of the policies that we can restrict with specific binaries can access which specific destination identities. So looking at it from a container level or container identity level only will not be sufficient. We need to really lock down and also figure out how can we understand when a container itself gets compromised. Very similar, the application or the attacker may actually spawn a reverse shell. Very common is using net cap and C would also run as a child process. And obviously we want to disallow any connectivity from the front end to that reverse shell, even though of course the front end container would need connectivity to the backend container just for normal operation. So that's our vision on how we want to combine the security of Syllium's policy enforcement with Tetragon's runtime enforcement going forward and as a combination of the two provide meaningfully better security in your infrastructure. If you are interested in this, this work is starting right now as part of the Syllium community. If you are interested in this, if you want to have a say in how we will develop this functionality, how we will shape the policy, what are the primary main use cases that we want to address in the beginning. Come talk to us. We're here all week. We have a couple of, we have a booth out here where you can talk to us. There's a Syllium project booth. We have an ISOvalent booth. Many of us are walking around in the hallway this week. Come talk to us. We would love to hear from you if this is interesting to you and if so, how you would like to use this going forward and what are the specific use cases that you are worried about and would like us to solve first as we implement the first version of this. If you want to learn more about Syllium and Tetragon in general, I'm sure you've seen the URLs a couple of times already but you can of course find more information on Syllium using syllium.io, the main project page. You can find information on Tetragon using the website Tetragon.io as well as the GitHub repositories and if you want to learn more about ISOvalent, feel free to visit our website. And if you want to provide feedback to this session, you can scan the QR code up there and give feedback to myself and to CNCF. And if that, I think we have plenty of time to answer questions or receive comments on the proposal made. Thank you very much. I think you can step up to the mic if you want to ask your question. Or I will repeat it for you. Yes, excellent question. So the question was looking at the pain that Assylinux induced. How are we going to avoid this? And I'm very familiar with the pain of Assylinux. I was on Reddit's kernel team for 10 years while Assylinux was being developed. I think one main difference is that we're not intending to ship a default policy for all of this along with Syllium. Assylinux very much tried to worshiping a Linux distribution and it includes a policy that exactly says what you can do and what you cannot do. And what we will do with Tetragon and Syllium is the ability to define the policies at the granularity that you want, very similar to how our policy does this today. But there is another aspect on how we will make it simple to use. I think we will, as we already do with our policy, we give tools and control at different levels of complexity. So if you want to go really deep and tie down to binary or maybe even binary arguments, then you can do so. And maybe you even want to restrict it on UID and lots of additional attributes or maybe you choose just to do it at the container level. And it is you who will be able to decide how much complexity and how much work you want to take on. So that's how we're currently thinking about this. But I would love to learn if you have specific ideas what could be challenging and actually know about this before we start implementing it. Yes? Yeah, I will repeat the question. So the question is whether we're planning to implement some sort of webhook or some sort of like notification where if you observe something we could translate into policy or maybe I didn't understand the question correctly. Absolutely, okay, now the question is can we observe what's happening right now because we know it's good to turn that into a policy and yes, we can already do that separately for network policy and also for Tetragon but not for the combined version of the two but we will, if feasible, definitely also allow doing this for these combined policies, right? Absolutely. Yes? So the question is given that we also control the network can we do something to prevent locking yourself out of the box as an example? Power over this. Exactly, using the commit and confirm model. So it's currently not implemented but it's definitely something that we would be interested in exploring and learn more about. We do have policy right now for Tetragon to protect Cilium so that we prevent others other than Cilium components to actually change Cilium infrastructure and Tetragon can also protect itself. We're not using the commit model yet in any way but that could be interesting for us. Yes, yes. Other questions, yeah, back there. The question is do we have any thoughts about tampering of binaries? Yes, Tetragon can do this already. Tetragon has file integrity monitoring where you can detect changes to files and execute actions thereof. So you can, for example, calculate a digest of a binary and then only allow execution when the file digest is unchanged. So you can, for example, calculate the file digest in staging environment or in your CI CD pipeline and then enforce a policy that only allows the execution of the binary if it's not tampered. So it's not, the Tetragon's capability is not limited to binaries. We can do file integrity monitoring for any file on the system. Do we have time for more questions? Any other questions? We definitely have time for questions. All right. But maybe everybody's happy. All right, there's one more question, yeah. So the question is, Suleyman Tetragon are currently low-level tools with amazing capabilities but requiring to write specific policies. Yes. And then the question is, have you thought about getting more into application lifecycle management or provide like a better user experience to the whole system? And I think the answer is part of, that's part of what our company sells as well. So if you do not want to write your own policies at low levels, you can ask Isabelan to help you with that. That's part of the value we provide. But I also think the automatic learning is definitely like a key aspect that we believe that policy, manual creation of policy is definitely something that will not scale long-term. So an automatic detection of what is the desired state capturing of that, whether it's in the supply chain or CITD phase or in a staging environment and then automatically translating that into policy is the way to go forward. But definitely I think in general, we're trying to not only build better capability but also to make everything easier to consume. Absolutely. Do we have time for another question? Or are we running out? I think we can take one or two more questions. All right, they're in the back. Can you repeat it? I couldn't fully understand it. Do we have any dashboards? Yes, so we have tons of dashboards. If you want to see some dashboards, we will show some of them in the Cilium session during KubeCon. So yes, there are dashboards on network policy on Tetragon, what's allowed, what's not allowed, violations, all of Tetragon's data can be fed into an SIM like Splunk or Elastic and so on and visualize it there. I simply did not focus on that today but that of course exists. We have particular very strong Grafana dashboards thanks to a great partnership with Grafana Labs and of course all the major SIM providers as well. All right, final question here. Are we pushing for unified standards? So yes, absolutely. We believe that Kubernetes is the place to standardize whether it's network policy, whether it is upcoming gateway API that's being developed, whether it's mutual authentication identity with Spitfire. So yes, we strongly believe in the standardization of all the policy that we're doing. We often tend to use a custom resource first to actually try out and understand what are the use cases worth covering and learn with our early users how policies should look like and then bring that into the Kubernetes standardization process. So standardizing through early users and then set it in stone via the Kubernetes APIs. That's how we think about this and how we'll ensure an open ecosystem. All right, very quick. Running Tetragon out of Kubernetes. Yes, you can. What you will lose is the custom resources that define a policies. You will need to use a REST API, but there is nothing specific about Tetragon in terms of Kubernetes. If it runs in Kubernetes, it will show you pod labels and namespaces and all of it. And otherwise it will show you C group IDs and stuff like this. But it's right now a Linux based technology can run on any Linux and in the future with EBPF on Windows will also run on Windows when Microsoft is ready.


Welcome back to our lecture series Math 1220, Calculus II for students at Southern Utah University. As usual, I'll be your professor today, Dr. Andrew Misselvein. We are starting lecture 13 today, which will be a continuation of our lecture we started in lecture 12 about trigonometric substitution, which will be based upon examples and content we can find in section 7.3 of James Stewart's Calculus textbook. Now, in the previous lecture, we introduced this ancient codex, this Rosetta stone that helps us translate from our modern language of, and this is of course just an analogy here, our language of algebra to the ancient cryptic language of trigonometry for many of us. And so what we've seen so far is we've seen examples where we've done a sine substitution and a tangent substitution. If you want to see some examples of those, click the links that you can see in front of you. But now I want to consider what happens if we do a secant substitution. So coming back to this right here, when we see this integral, the integral of the square root of x squared minus 4 over x dx, the fact that we have a square root with a quadratic polynomial inside of it indicates to us that we want to do some type of trigonometric substitution. For which case the secant substitution is what we want to do. Here, a equals 2, and so we have the square root of x squared minus 4. And so we're going to want to do the substitution that x equals 2 secant theta. Now, the reason we want to do this is because we have this difference of squares, if we utilize the Pythagorean identity, secant squared theta minus 1, this is equal to tangent squared, we can turn a difference of squares into a perfect square for which case the square root will then dissolve itself. Now, one has to be cautious here because the secant substitution is very similar to the sine substitution. You will notice with the sine substitution, you have a constant minus a variable. But with the secant substitution, you're going to do a variable minus a constant. The order of the difference makes a difference. And these two things are not the same difference. I know those are horrible puns there, but you're going to have to deal with me. You don't have any other choice right now. So taking the square root of, given that we have this square root of x squared minus 4, we want to do a secant substitution. And this square root is going to turn into a 2 tangent theta from this identity right here. All right, let's go back to the problem here. So getting rid of this loop-de-loop for a second, how is the substitution here going to work? Well, based upon what our codex said, we want to take x to equal 2 secant, that's what we agreed upon, 2 secant. Then dx, when you take the derivative, you get 2 secant theta, tangent theta, just using the derivative of secant there. And then we have to take care of this square root, the square root of x squared minus 4. You can use the identity that was on the previous slide, as we've seen before. What I'm instead going to do, as usual, I prefer this triangle approach, right? We have this right triangle, and inside the right triangle, we're going to label the angle theta. It's a right triangle. And because we have the secant ratio, we know that secant of theta is equal to x over 2. Now, if you don't like secants, we can always switch it to cosine by taking the reciprocal. Cosine theta is equal to 2 over x. However you prefer, it doesn't matter to me. Cosine is adjacent to over hypotenuse, excuse me, 2 over x. Just make sure things go in the right spot. Using the Pythagorean identity, we can see that the other side is going to be none other than the square root of x squared minus 4. Honestly, I don't calculate it because I know every time you do this argument, the third side is the square root that started the whole process. But if you have any doubt in that, please work it out yourself there. So if we try to combine together the square root side with the constant side, we can relate that using a tangent, right? Tangent theta is going to equal the square root of x squared minus 4 over 2. And if you clear the denominators, you're going to see that the square root of x squared minus 4 is 2 tangent, like we predicted earlier. All right? So sort of a rule of thumb is the reason we choose the substitutions we do is that whatever you set x to equal, the square root will equal the best friend of that function. So sine and cosines are best friends. Tangent and secant are best friends as well. One could do a cotangent or cosecant, but that just complicates things with negative signs that we don't need. So using this substitution, let's translate the integral into the language of theta. The square root on top is going to become a 2 tangent. Don't forget about the dx because that translates as well.  And then this sits above x, which x is 2 secant, like so. There's typically a simplification that happens at some point here. So there's a 2 that cancels. There's a secant that cancels. This thing will simplify to be a 2 integral of tangent squared, theta, d theta. How does one calculate the anti-derivative of tangent squared? I think actually switching it over to secant is probably our best move right here because secant squared is a anti-derivative. It's more obvious. Tangent squared, notice 1 post tangent squared is equal to secant squared. Therefore, tangent squared is secant squared theta minus 1. The same identity we mentioned earlier, d theta. And therefore, the anti-derivative of secant squared is tangent theta. And then the anti-derivative of negative 1 is a negative theta. We have a plus a constant here. And so if we distribute the 2 through, we're going to get 2 tangent theta minus 2 theta plus a constant. We have to translate these theta's back in terms of x. Now, one of them we already know, right? We already know for a fact that 2 tangent is the same thing as the square root of x squared minus 4. We could ascertain that using the triangle right here, but as it's already on the page, I'm just going to use that and save us a little bit of computational effort right there. You're going to get the square root of x squared minus 4, like so. How do we do with the 2 theta? Well, again, come back up to the original identity. We have x equals 2 secant theta, which you can see right here. That translates to secant theta equals x over 2. So we could take theta to be arc secant of x over 2. People don't usually use arc secant so much. You don't see that on your standard scientific calculator. So I'm actually going to employ cosine right here. Cosine theta equals 2 over x. So theta's going to equal arc cosine of 2 over x. That one's a little bit more palatable there. And so we record that down here. We have arc cosine of 2 over x. And don't forget our constant. And this gives us the anti-derivative we were looking for. So notice that doing the secant substitution is not fundamentally different than the tangent substitution or even the sine substitution. Once you get the hang of one type of trigonometric substitution, the other two are very, very comparable. And they work very nicely together. So just give yourself some patience and practice and you'll get this trigonometric substitution stuff, that I'm sure of.


WeRUA is the university's faculty and staff giving campaign to support colleges, schools and programs across our campus. By participating, faculty and staff enable our institution to achieve its mission of advancing teaching, research and service at the highest level. When thinking of the question what gift can you give, I think it really shapes your perception on how you can engage with people in any given situation. So that's not only with students but we could also think about that of the Institute as a whole. The university has given back not only to me but I think the university has given so much to all of us. So I think to be able to pay it for and to give back to this institution that I think has given so much to us is one of the great reasons why I think this campaign is important. Visit weRUA.UA.edu today to make a gift to support the college, school or program of your choice.


Consequence it's something that happens is the result of something else You get I'm pretty good with that, but if we could get a little more technical that might please me and my partner here So a stimulus change that follows the behavior of interest some consequences Especially ones that are immediate and relevant to the particular behavior have an effect on that behavior in the future Sometimes it increases it sometimes it decreases it sometimes the consequence doesn't do squad to behavior The point is is the consequences are the result of behavior. They don't have to be good They don't have to be bad. They are just things that happen. No moral value at all No matter how many times your children tell you the consequences are bad. It's not true consequences. It's just consequences Thank you very much. Have a good day


Really quick, I forgot to mention when I first recorded this video that this was inspired by a question from Hard K. And I'll do a few more videos based on that question as well. Bah, what's up everybody? Once again, it's Brand Man Shawna. Today, we're going over the one way that's really important to get a record deal. And what's that one thing? Leverage. What exactly does that mean? We'll get into it as we break it down into two separate versions of it that works to get that record deal. The first one's pretty old school, which is finding that person, that kind of connection. You network, you find that person who already has relationships established. And then they become an advocate for you, almost like that old school and our nurturing relationship. They give you connection and put you in front of the people, the right people. And they also kind of nurture and start to give you that fan base or at least that experience that you need until they think you are ready to be put out. Yes, that's still happening in some places, people. Me, I don't really like that, Rob, because you're putting your fate into someone's hands and that's just not my thing. And plus, even with that first relationship, you're still going to have to do a little bit of number two, which is way more important. Build a fan base. Build leverage by getting directly to the people. You create a buzz. If you look at somebody like XXX, Tintacion, he has a lot of buzz going around in knees and gel, which kind of amplified the fan base he already had because people went even more crazy. You can think about 50 cent early on in his career. When he started beefing with Jarl Rull, he created a lot of extra buzz around him. You can think about G-Eazy. He created a lot of buzz and a fanatical fan base before he got signed or started working with labels for distribution and things like that. There is nothing more powerful than actually having a fan base. Why? Back to that leverage. Having connections, powerful connections, that's the form of leverage. But having a fan base and using that fan base to generate buzz is the most effective form of leverage that you can use to get a deal. Not only a deal, but a deal that's best for you. Because what's leverage, you really at that point are saying, I don't necessarily need you, but I want you to help accelerate what I already have going on. In the other first example, when you are using these connections to really create everything for you, you're basically asking me to do it for you. You say I have this talent, but I need you. Number two is saying, I don't need you, but I want you to help me because what I already have going on, I know you pour that fuel, things get burning. And at the end of the day, once again, you're going to have to build a fan base. No matter what, so why not just start now? Consider the independent route and as you are independent, you can decide if you want to get with the label. But start learning those things early on because ask yourself a genuine question. And most artists don't really think this through enough. What is your goal? Is it to get signed or is it to be a successful artist? Those two things are not necessarily the same thing. Think about all the people who've gotten signed and well as a matter of fact, you might not even know about them because that's the point. Getting signed is not a bad goal, but don't let it distract from the ultimate goal of becoming a successful long-term artist in the game. Build a fan base, generate buzz, or you could just have a hot song and generate buzz that way. But create leverage how you can. It's that simple. That's it. Hit that subscribe button. Bam.


So for us we're really excited to be in India, to be working alongside a very similar like-minded business. We are very much an entrepreneurial business like action. We see great synergies in our partnership. We've got together because we've seen a real opportunity for India friends, a successful India friend. We are part of one of the world's most exciting growing economies, an economy that's taking its place in the centre of the global economy. We see great opportunity for those brands to now start investing in media and campaign and advertising outside of India. We want to work with likes to give those brands value in that regard. And for us, similarly, the Indian economy has become increasingly important for our clients. So we are at a tipping point where we feel it's important for us to have our best-in-class presence in the market as well under the media keys brand. So we're really, really excited to be here. Thank you. Okay, back.


Green Turtle Classic powered by SFM sports.net joined now by Nazareth head coach Rob Randall a tough 13-8 loss here today to York Day one of the classic and this was a 7-7 game coach in the third quarter It seemed like what really changed everything was the face-off X and just their dominance there in the second half Yeah, you know that was that kind of caught us off guard. It hasn't happened to us yet And and while we dominated the first half yeah face-offs we we really struggled in the second half And that's a tribute to the adjustments that that York made their defense also I thought as the game went on you have so many you know talented Scores and two of the great scores in school history obviously, and it just seemed like defensively They managed to come up with the answers when they needed them. Yeah, they did I mean they they made some good stops and we were making some mistakes on offense that we hadn't really made Too many turnovers, you know, I think we had 12 turnovers on the game And it's just too many especially when your opponent has six and we just have to do a better job of Drawing and dumping and getting back to basics How do you pick a team up when they they have a loss like this a game? They were in and they've got to turn around and play another really good team less than 24 hours from now I don't know we're gonna find out You know, I mean it's a battle. It's you know, um, that's why we're here Yeah, and when loser draw well, that's why we're here when you want to put our our kids in this environment And expose them to the pressure and see how they handle it and one of the things that did jump out at me in this game Scott Brown made 10 saves and you know, it really did about as much as he could to try to keep you in this one Yeah, you know, I thought he let a couple in early But he made a couple big saves later in the game and in the fourth quarter We just didn't do a good job of generating enough offense and that's you know, that's a tribute to To York and and their defensive play they did a really good job and and they've got a lot of weapons And you know my hats off to York and they've done a really nice job with with that program and Brandon's done a nice job Coaching them up and they're well coached and they're respectful and and you know We have a ton of respect for for York and what they've done just your thoughts on the event being here again and Now eight teams in this thing and just an unbelievable day for division three lacrosse. This is it's awesome It's it's you know as disappointing as it is After that game it's an awesome event And it's what you want to expose your kids to because you want to see how they can handle themselves and in the pressure Situations against great competition coach. We appreciate you taking the time after the game best of luck tomorrow against Dennis and thank you Go coach Rob Randall from Nazareth. This is the green turtle classic powered by sfm sports net


Hi everyone. Welcome to this session on science in cloud native. My name is Ricardo Russia. I'm a computer engineer at CERN. Today I will talk to you about the usage of cloud native projects in the scientific area and give you an overview of the status of this, but also the challenges that are still existing in terms of using this type of software for science. I'll start by giving an overview of the status of the usage in this area. Cloud native is really fastly changing the ways that scientific infrastructure is built and maintained. There are a couple of areas where this is really already very significant. The first one I would highlight is reproducibility. The fact that container is a very well-defined unit that can be easily deployed in different environments also helps a lot with reproducibility, which is a key for science. The fact that we can take an existing component, even an old component and deploy it in a current or say a more modern infrastructure that will come up in 10 years, this is really making a huge impact in terms of redoing all the analysis and making sure that things can be taken forward in the future. The second part is this idea again of having a container being built once using a well-defined way and being able to run it anywhere in different platforms. So in scientific infrastructure it's very often heterogeneous. Scientists will try to use as much as infrastructure is available to them and this means having to comply with different systems underneath. So the idea that people are standardizing in containers and container orchestration APIs really means that this task is being simplified for end users. And finally, which is also related to what we just talked, once you have this single unit where you have wrapped your code and data, then sharing these units with your colleagues is much easier. This means this is something that is really, of course, key to scientific collaboration, the fact that you can have your analysis and share it easily for your colleagues to reproduce. So all of this together means that the infrastructure itself is very much simplified and by doing this and having access to these tools, scientists can spend a lot more time doing actual science than maintaining the underlying infrastructure. One of the things that is also coming out of this is the access to a much larger set of resources thanks to these standardized APIs around cloud-native tools. There are still, of course, a few challenges and I will highlight three today. The first one is software distribution. When we start thinking that these scientific workloads are made of thousands or tens of thousands of individual pieces, pushing the software to where the analysis is going to be done is key and doing this in efficient manner is, of course, key. The second one is rootless environments. A lot of the infrastructure scientists have access to has very strict policies in terms of what and how people are able to run their workloads. These are shared environments so running them in unprivileged is a requirement. And third is the advanced scheduling. This is where the biggest differences towards compared to traditional IT happen when you're doing scientific workloads and this is things like batch-like workloads where queuing and priorities and fair share are very important. I'll cover a bit more of that as well. Starting with software distribution, ideally, container images will be very well layered and optimized. Having images that are over 10 gigabytes and not really well layered is really not uncommon in the scientific field. In reality, even images like that are, for example, 15 or 20 gigabytes. In total, the actual workload will require less than 6% of that to run properly. So it's very inefficient to have to download a full image before starting a workload. If you think that these clusters can be huge, hundreds or thousands of nodes, then this problem is even bigger. You need to pull the images across all the nodes. If the images are very large, this imposes a huge pressure in terms of network and storage. If you think that, in addition, you're running thousands or tens of thousands of parallel jobs, this problem is even made worse. To help with this, as I mentioned, the ideal would be to have optimized images. This is not always a possibility. The second one is caching. This is particularly important if you have geographically distributed clusters or nodes in your cluster. This will help a lot with efficiency. Of course, peer-to-peer distribution for offline distribution of the software is also a key. But one thing that really helps is this concept of lazy pulling. This is the idea that instead of downloading the full image before deploying your workload, you will instead do a remote mount of the image and gradually download only the content that is actually required and requested by the workload after the container is running. This means that you could have a flat startup time of your container and then access the actual container image contents as the workload requests it. One example of an implementation of this is this remote snapshot in continuity. This uses a concept called seekable tar, which basically, if you know how a Docker image works underneath, it's pretty much a set of tar bowls, each one for each layer in the image. But one smart concept that is used here is that a tar of tar is still a valid tar, so it's fully backwards compatible with the existing container image formats. But by doing a tar of tar, you end up with a seekable tar. So you can basically navigate the tar to find, for example, individual files that are being requested by the workload. This is pretty much how it happens. The runtime will, instead of downloading the image before launching the workload, the container will launch the container and expect that the data will be made available when needed. In terms of performance, this has a dramatic impact. You can see pretty much flat the startup time, no matter the image you're using in these cases. It's actually pretty small images. But if you extrapolate these two images of 15 or 20 gigabytes, the startup time will be very similar, of course. Then the workloads can be a bit slower as they request the data. But considering we are only requesting a very small amount of the total data, there's a very big impact in terms of reduced network pressure and storage needed under notes as well. The second challenge I mentioned earlier is this idea of ruthless environments. And this is particularly important for high performance computing clusters. A lot of the scientific workloads are deployed using these massive supercomputers, which are shared machines between multiple end users. So there's very much restricted access on what the end users can do in these environments. This is not a good fit for the way Kubernetes and other projects around it are built today and the expectations they have. But there is this effort to have what's called ruthless containers. And this is a possibility of helping to onboard more of these resources into this ecosystem. So a link here to the project. The goal is really to manage containers as an end privilege user. And here is not running the container, only the container itself and privilege, but to run the container runtime as well and privilege. And this will really lower the barrier of onboarding HPC environments into cloud native deployments. They have a very nice definition of what an end privilege user is. It's a user that is not in the good graces of the administrator, which is a very nice definition of what we expect here. There is support already for this kind of deployment in Docker, Pubman, Buildkit, container D. So there's already quite a lot of things that can be done using these projects. Having support in container D also means that tools like kind, Minikube, and Kubernetes, using a distribution called usernetys, as well as K3S, K3S, are already an option to try out this type of workloads. Finally, I'll mention the third challenge, which is advanced scheduling. And this is really, again, the key of the differences towards, compared to traditional IT deployments. These are features that are really required for traditional HPC or HTC high throughput computing type of workloads. I'll mention here priority queues. This is the idea that as you want to maximize the usage of the clusters, you're actually allowing workloads to be queued before being submitted. And these queues have priorities for higher and lower priority workloads. This is also meaning that there is a requirement for preempting running workloads to replace them with higher priority ones, since these workloads can take a few hours or even a few days. This is something that is not existing in the built-in schedulers, but there are multiple projects that are focusing on this. The second requirement is fair share. This is the notion that you want to optimize again the usage of the cluster. So you allow some teams or users to have more workloads running than what their usual quota would be if other users are not using completely their own quota. But over time, this should compensate. So you want to balance this for everyone to have what their expected quota should be in a longer period of time. The third requirement is gang scheduling. This is the idea of submitting multiple jobs at the same time. This is critical for workloads like MPI, where you need communication between the different pieces. So you need to be able to schedule multiple workloads at the exact same time, otherwise they wouldn't run properly. This is also something that has to be built in this case. The last one I will mention is, again, we talked about workload distribution in multiple heterogeneous environments. Another requirement is to do this across multiple clusters. Again, the goal is always to maximize the access to whatever resources are available. Multi-cluster is one of them, of course. So there are some projects that are really putting an effort into providing this in our ecosystem. The first one I will mention is Volcano. It is the cloud-native batch system. And it really tries to offer all the functionality from a traditional batch system, but using cloud-native APIs and tools. The second one is Admiralty. And here, the focus is more on the multi-cluster part. And they do this by having this notion of proxy pods on a top-level cluster that then have the actual workload pods running on child clusters. The third one is Armada. And this is, again, focusing on batch workloads. And they focus on scheduling and running of these workloads specifically on Kubernetes. And finally, I will mention the virtual kubelet. This is kind of masquerading the kubelet or the node in a Kubernetes cluster from the actual resources that serve the node. And in reality, this can be an actual node, but it can also be a remote API, including the API of an external Kubernetes cluster or a serverless platform. So all of this together really tries to make these goals of improving the access to all types of resources to scientists in using the concepts that scientists are already used to. There's a lot more going on. One of the really promising developments comes also from SIG scheduling, where they try to onboard all of these concepts into the Kubernetes scheduler. And this is something that will be evolving fast and then really looking forward to see progress there. So this comes to the end of my talk today. I hope I gave an overview of what the excitement towards cloud native in the science area is and what the challenges that still exist are as well. A lot of this discussion happens in groups like the CNCF research user group, and I put here the link. And also this project fall under the technical advisory group tag runtime in the CNCF. So this is also where a lot of the discussion happens. So I hope this is only a teaser. And I look forward to Cogon in May in Valencia with a lot more news in this area. And for everyone listening, enjoy Cook on China. And I hope to see you all soon.


of the many names that Shiva is referred to. Soma is one of the important names. Soma literally means intoxication. If there is no intoxication, you will never be mad enough to jump into the ultimate void, which is only leverage. So, Soma like Soma Sundara is one of prominent names of Shiva. Always in a great, but fully alert. So, the story goes like this. Shiva was sitting near Kailash in a completely inebriated state. Then you spread all over India that there is a man sitting, so magnificent a man that slowly year after year, year after year people started making the pilgrimage. There was a girl who was a princess in the Himalayan kingdom. Her name was Parvati. And when she heard this, she said, I want to go and see him. The moment she set her eyes upon him, she just so completely overwhelmed by him. She said, if I marry, I marry only this man. Then somebody else played a conspiracy and he decided to get married. A big wedding was organized. Anybody who is anybody is there. The bride is all decked up. Everybody is waiting for the groom to come. And the groom came. Shiva walked in, ashmured, dreadlocked, fully inebriated. And all his friends, these goblins and demented beings making all kinds of noises. Parvati's mother Meena saw this man and his friends. And when she thought that her daughter is going to marry this man, she just fainted and fell. Then they revived her and she was completely heartbroken. How can I give my daughter to this man? He's wild. He's completely uncivilized. He's not even a man. He's something else. So Parvati went and begged Shiva for me, whichever way you are. For some reason, you put on a hideous form and come. This is also okay with me. But for my mother's sake, just saw a better form. Then he said, okay. And then he turned into a very graceful and beautiful form which was referred to as Soma Sundar, drunk but beautiful. Completely inaugurated eyeballs up. But he became utterly beautiful. Then Meena revived and looked and looked at this magnificent man standing there and she said, I would like to give my daughter to this man, not to that one. So inauguration, intoxication is an essential quality of meditativeness. If that's not there, if you're not drunk, how can you just sit? It was the most torturous thing. Simpliciting there like this, trying to concentrate on something. So that's his essential quality. So he carried the moon. That's his embolism that he is always drunk upon himself. No substances. So when we said, Shiva constantly drank Soma Darshan, he was not an alcoholic. He just imbibed the moon beams which he carried always in his hair and constantly drunk. But this blissful state is not a goal by itself. This blissful states eliminate the fear of suffering. Only when the fear of suffering is gone, only when this idea what will happen to me is completely eliminated from you, you would dare to explore life. Otherwise you only want to protect it. Whether a carrier or a business, it's all about security. Marriage is about security. Everything is about security. As long as the fear of suffering is constantly playing its role, now you will not dare to really go into deeper dimensions of life.  Now, there is no fear of suffering. You're willing to go anywhere.


Hi everyone, Joe for JasperJasperCaseRakes.com coming at you with 2023 Panini Absolute Football Blaster Edition number six. It's the last filler. It unlocks the mystery crate. It unlocks the Kobe giveaway. The break itself will be a separate video and the giveaway video will also be a separate video. You got a chance to win a mystery crate in this, ladies and gentlemen. So big thanks to this group right here getting it on the action. We did a little mini promo too. They're the winners of that mini promo. That helped the break get kick-started a little bit. Now we've got all 32 spots to account for. All teams are in. Let's do the break first. That's our first dice roll. Three and a six. Nine times for names and teams. One, two, three, four, five, six, seven, eight, and ninth and final time. And three and a six. Nine times for the teams. One, two, three, four, five, six, seven, eight, and nine. All right. So here's the first half of the list right there. No trade windows here in these little filler breaks. And the second half of the list right there, Chad, Jimmy is saying a week and a half compared to Jimmy. We're in Jimmy time. JT. JCT. All right. So let's print that out. And let's rip this box here. That's the last mystery crate that's coming up in the next video. And there's the final printout. Hot off the presses. Wow. Shots fired. Chad, Chad's just like, yeah, go big like me. Get into those, get into those NT first off the line breaks. Someone did remind me that it was Owen, I think that kabooms are a possibility in here. I want winners. I want players I want to win. There's an Anthony Richardson and a Pooka Nukua in that green foil. All right. All right. James with the Rams, you'll get that rookie and the Anthony Richardson rookie card for Damian and the Colts. Nice. Get well soon, Anthony Richardson. It'll be hashtag good for the hobby. All right. Now, the moment of the moment of truth, the moment we've been waiting for, who is going to win that final mystery crate spot? Good luck. Let's gather all the names again. Let's roll it. Let's randomize those names one and a four, five times name on top gets a mystery crate spot and a guaranteed hit and a chance of the Kobe one, two, three, four and fifth and final time. Now a lot of sad faces here, Brian, very close, just not quite, but I appreciate you trying, two through 32. Thank you. I really do appreciate you trying. It's not easy, especially when we're only giving away one spot, but nothing ventured, nothing gained. Sad times though. Name on top, happy times. The only happy person in this rake. It's going to be James, James L. Number five, you are in the mystery crate. You got a shot at the Kobe as well. We'll see you in the next video. Jasper'scasebrakes.com. Bye-bye.


The thrust to inculcate a culture and love for reading amongst the nation's students received a shot in the arm with the publication of writings by students and teachers as part of the OECS USAID Early Learners Programs Write to Read initiative. Hermadi Mark has that story. The OECS USAID Early Learners Program celebrated a significant accomplishment with the culmination of the Write to Read program. The program was established in 2017 and provided students and teachers across the OECS the opportunity to become offers of books using the region's early childhood curriculum. After a rigorous process of collection and evaluation of submissions, winners were announced and their submissions were published. The St. Lucia Early Learners Program of the Department of Education held a book launch on May 28, 2021, where the student and teacher offers from St. Lucia were recognized and provided with copies of their books. Angel Caglin, the curriculum officer of English at Camdou says, this is the beginning of localizing the literature used in schools. Really we want to look at this as a first step to having more locally authored texts in the classroom, in our classroom libraries, in our school libraries and in our instructional curriculum. So for anyone listening to this program, whether it is today or tomorrow or sometime in the future, consider this the opening ceremony for more publications authored by our students, by our teachers and by our community members. 18 books were displayed, written by 19 students and teachers. The books were published by Caribbean Reads and covered a variety of genres. By providing locally made reading resources, the initiative aimed to create an authentic reading experience for students at the OECS and increase their love for reading. Rafa Gauden is the education specialist in the Education Development Management Unit of the OECS. We recognize that we're putting so much emphasis on buying books from the outside to have children to read. And I know from being a former teacher and working with the Ministry of Education, working with teachers directly, that we have so much talent out there. We have teachers who are superb writers, we have students who are superb writers. And I remember some of my students, when I taught at the Iris Simon Secondary School, students that persons may underestimate, may assume are not necessarily the most capable. And I think back to some of the writings that I got from some of those students and we realize that rather than putting all the emphasis on getting commercial material that is being produced by people who are, for the most part, outside of the region, we need to celebrate our own. Chief Education Officer in the Department of Education, Dr. Fiona Philip-Maya, encouraged the student-office to celebrate their successes. She expressed gratitude to the agencies involved in the initiative and commended them for their dedication to improving education in the region. We cannot live without me on behalf of the Department of Education extending my sincerest gratitude to USAID, UNICEF, OECS, a partner who is family to us, always there with us, as we continue to forge ahead. For me, always with the most significance of children. Education must be about children. What else? Sometimes it's really the others that take the forefront, but we must focus on them. So let me say to you, to everyone here, a job well done. The book launch coincided with Reading Month 2021, which was held under the theme, readers as creators. From the Government Information Service, I'm Hermitie Mark reporting.


Over life, SCP-5093 is an anomalous relationship between the force of an explosion in Drawing County, Wyoming and the efficiency of the New York City subway. The larger the yield of the explosion, the faster and smoother the subway will function for the day. June 27, 2016, explosive yield 0.05, no significant statistical rise in efficiency. However, researchers noted an unusually no number of complaints filed on the MTA's website. By 23rd, yield of two trains were ahead of schedule by several minutes. MTA staff took active action to maintain this, and the employee once pulled a suicidal individual away from the tracks. It is unclear whether SCP-5093 affected this decision. August 1, yield of 3.5, trains seemed to regularly defy reality and physics to reach destinations quickly. In one instance, a train began to simply teleport between stations, and then there's 292 lines of tests submitted, so we're just going to move on. SCP-2678 is an extra-dimensional space, solely accessible to those holding Catholic beliefs through a previously barred door in the basement of the Siena Cathedral in Siena, Italy. A metal placard beside the door reads, SCP Foundation Department of Adnormalities. Those who enter the doorway will emerge into a small, tarped outpost built around a freestanding exit. Inside the outpost is, a biomedical laboratory refrigerator, stocked with samples of blood and bone taken throughout SCP-2678. Several audio recorders, ranging from wax strip models to magnetic tape machines. A computer terminal requesting Foundation credentials. All attempts to access it have resulted in rejections for insufficient clearance. The score for a choral prelude titled Soul Gogata, the incomplete skeleton, hyoid, hip bone, and both forearms omission, of a pre-pubescent male, covered by a sheet on a steel table, caused death unknown. Covered by the SCP Foundation from plans retrieved, SCP-711 is a device assembled from several highly modified, high-energy physics equipment. Its primary function, in short, is capable of sending data into its past and of receiving data from its future. Transmission is strictly one way. Independent operation of the item is therefore causally impossible. Any message it receives will necessarily be sent at some point in its future. All SCP-711 messages predetermine their own existence and content. To date, exactly 17 messages have been received via SCP-711. The first string was received at 1,300 hours on f***ing f***ing f***ing f***ing f***ing the day the item was created, and sent 4 minutes later. It consisted only of the character's test. With successive operations, signal quality is declined dramatically. Ah! SCP-5909 is a crustacean measuring an estimated 2.1 light-years in length, located 7.5 light-years from the solar system. Aside from its size, SCP-5909 possesses features congruent with those found in the Alaskan pink shrimp, genus Pandalus Eus. SCP-5909 has shown no signs of life or movement, remaining in a fixed position since its discovery. SCP-5909 was originally discovered by astronomer Julian Martin at Sault on May 20, 2020. The Foundation became aware of the discovery when Mr. Morton attempted to publish his findings. All evidence was confiscated and Mr. Morton was administered Class A amnestics. SCP-5535, previously known as Mateo Velez, is a Hispanic male born on July 5, 1986, who suffers from an anomalous version of Alien Hand Syndrome. The subject completely lacks control over its left arm, which is actively hostile toward the main body, as well as any surrounding individuals, despite not having sustained any damage to the corpus callisum, the posterior parietal cortex, the supplementary motor area, or the anterior cingulate cortex, which is usually the cause of AHS. SCP-5535 was arrested for the murder of its wife and the attempted murder of its child on July 13, 2016. The subject claimed that it lost control over its left hand, which had then choked its wife to death against its will. SCP-5535 was released by the police and delivered to a hospital. It was further detained by the Foundation after its anomalous brain chemistry was discovered by the hospital, following containment. SCP-5535 claimed that it had been possessed by some sort of incorporeal entity that took control of its arm. The liveable researcher Theron Sherman. And if you're watching this briefing, it's because you got lucky and get to supervise one of our very, very good boys. SCP-5530 is a male eastern goddess snake, approximately 6.7 meters long, that has had 48 legs from an eastern blue-tongue lizard, thomically grafted onto it. Its length and legs are its only anomalous attributes. Aside from its predilection to use these legs for locomotion and increased appetite, the anomaly behaves like a non-anomalous male eastern goddess snake. SCP-5530 was discovered in New York City Central Park on following reports of hysteria in the park and sightings of a massive centipede like lizard in the area. Mobile Task Force Lambda-12, co-named pest control, were dispatched to contain it. The anomaly was found pursuing rabbits on the western side of the park and restrained with minimal difficulty. SCP-5950 is a parasitic subspecies of Pacific flying squid, capable of fully integrating themselves into human hosts. Users of SCP-5950 use organic jet propulsion to enter a human host's rectum. After entering a host's anus, the SCP-5950 instance will position itself so its head will remain protruding from the host, functioning as the new visual center. The eight legs fuse to the host's rectum, at which time the SCP-5950 instance will secrete a complex toxin. This toxin puts the host in a semi-comatose paralytic state during the duration of the infestation. The SCP-5950 instance then attaches its two tentacles to the host's spinal cord and assumes full control of the body. SCP-5950 instances will consume food and water using the host's mouth, excreting waste from the same orifice.  SCP-5805 is a Zenith brand AM radio, which has been playing an improvised small ensemble jazz since at least 1982. The branding and construction of the radio are consistent with manufacturing in the 1970s. There are otherwise no anomalous components to the device, aside from its ability to operate indefinitely and without an apparent source of power. SCP-5805 was initially discovered in 1982 at a campground in the Cascade Valley Park near Akron, Ohio, when a fangationing foundation researcher and his wife were unable to locate their assigned rental cabin. Unintentionally entering a portion of the park not intended for public use, a couple overheard jazz music and traced it to an unmarked cabin obscured by brush and overgrowth. The interior face of the cabin door contained a number of crude etchings. Several personal effects were also located inside of the cabin. SCP-5149 is a radio signal of unknown origin being received by LunarSight 34 every 24 hours. SCP-5149 consists of a short repeating message in UTF-8. Decryption of SCP-5149 is considered a class A priority, a team of cryptographers, linguists, and radio technicians are stationed at Lunar 34 for this purpose. Attempt 1 ran it through all modern language translation systems for similarities. Translation failed. Manipulated based through flips, rotations, reflections, and several stretches and compressions before putting it through previous suite of analyses. Translation failed. Attempt 2-49, Greenhorn suggested we run it through nonverbal languages screener. Poor guy thinks it'll really be that easy. Translation success! Within 0.5 seconds of the scanning, Screener produced an English translation of SCP-5149. It was realized that no individual on the project had recognized the transmission as a form of braille. With a cryptid message on SCP-5149, HELP! I CAN'T F***ING SEE!   Alright staff, that ends our broadcast for today. Use your foundation in cryptid YouTube account to like, comment, subscribe, hit the bell, support our broadcasts at Patreon.com, so Site 42. See you guys in quarantine. Thank you for listening.  Please become a patron or visit our merch store at the link in our bio to support our work. Secure. Contain. Protect.


Welcome to All Hands Update, I'm Petty Officer Ian Cotter with your headlines from the fleet. A first generation malaria vaccine could be a reality thanks to Navy research. The Navy Medical Research Center recently finished a clinical trial of a potential vaccine that showed 100% protection against the disease. The vaccine will go through several more phases of testing in the next four to five years before it will be available to warfighters and people in endemic areas. The Navy is entering phase two of reducing administrative distractions. After collecting a list of sailor identified distractions, Navy leadership needs you to come up with solutions. Visit navyred.ideascale.com to weigh in on ways to streamline or eliminate the administrative processes that can take away from mission readiness. You can read more about these stories at navy.mail. From All Hands Update, thanks for watching.