I'm Andy from Control Plane, Cloud Native Security Engineering and Open Source Security. We are sec ops for Kubernetes working in regulated industries and financial services. We espouse continuous infrastructure and security principles. I have got various other positions, very proud to be involved in the Cloud Native Computing Foundation's TAG Security, the technical advisory group. We audit and threat model projects that are coming through the CNCF in order to establish a baseline security posture and make recommendations. I also work for a charity called Open UK, along with one of my colleagues here, Dawn Foster, for advocating to the UK government for the use of open source and also the financial incentives to actually pay maintainers. We've seen projects come out of the US, such as the Open NSF's Alpha Omega project, funneling tens of millions of dollars into open source maintenance. We would like to see that here, very keen to talk on either of those subjects, or indeed the one for which I'm here afterwards. I've written a few things recently. Sands Sec 584 is a security training course. I wrote the book Hacking Kubernetes for O'Reilly recently, and we also run capture-the-flag simulations at the official KubeCon conferences. If you find yourself in Detroit or indeed in Barcelona next year, please do come along and play. This is the book. It is available to download for free at the URL at the top. That is the PDF version, which requires less re-keying, of course, than the dead tree book. What I will talk about today is very much inspired and based upon the book. There are two versions of this talk. One is a live demo marathon, which is mildly stressful to deliver and has gone spectacularly wrong a number of times. This version, which deals with the concepts, the diagrams, and tries to tie things together. There are many works on which I am reliant and grateful to my forebears and betas, and also I've linked to some of the demos that I've done in there as well. So what will we talk about today? The shared responsibility model. Kubernetes alleged and promised benefits. Threat modelling. Why is it good? Why does it give us a baseline on which to quantify and build our security controls? The question is answered with another question. The supply chain is so hot right now. What's the actual problem? We'll detail some of the ways that it can be devastating. Runtime hardening. If we're running untrusted code, can we mitigate or control for that? And finally, cluster infrastructure and topology. Where does that sit in the context of our organisation and our cloud accounts or our colo, and the individuals and colleagues that we have working in and on them? So the most important part of a successful cloud native migration is the people. Responsibilities, patterns and practices and skills. Let's dive in by looking at some of the prerequisites. Cloud native is complex. It's an explosion of abstractions. New developers or engineers joining this landscape have a lot of quick upskilling to go. And preventing the last minute security holds on deployments is important to maintain the trust of other engineering teams. So, of course, the biggest problem is a techno-socio problem. It's the people. We probably know this already, underpinning. A way to increase collaboration is by bringing security to the front of engineering decisions. This is a real benefit of threat modelling that we'll dig into later. Part of the shared responsibility model is an acceptance that an organisation's trusted workloads are running on a third party's potentially untrusted computers. So this is a cloud migration. This is renting compute infrastructure from a third party. Under this model, Kubernetes is almost always managed as a service or a platform. There's not a lot of benefit of running an unmanaged service on cloud infrastructure at this point. Cloud providers have proven themselves more than capable of running secure workloads on our behalf, and maintaining infrastructure then becomes their responsibility. Cloud providers are also shipping trusted platform modules to allow the signing of firmware used to boot hardware in the stack that we're running, which compares a hash of each component's firmware with an internal register of signatures and only permits it to boot if the values match. This is generally a higher level of assurance than we would be able to get from our own data centres. So, within our organisation, we want to threat model everything from an application's perspective. A developer only owns the application itself. The supporting tools are provided and managed by teams. The ultimate model of Kubernetes service integration is to have individual teams behave as managed service provider analogs, similar to the cloud model. Why is this so good? Because it segregates responsibility, retains uptime. Many of these components become critical to the availability of an application, and so it sets clear interfaces between the teams. Their responsibilities are clear. This means tools and policies are provided to us by operations and security respectively. We depend upon documentation and runbooks, knowledge bases, training, and teams, hierarchies, and finally the individuals that compose this, which of course are all potential points of compromise for our organisation. So, when we're defining everything as code, this then requires a different model in terms of those shared responsibilities and in terms of how that code is stored. Organisational roles converge upon a common communication mechanism, which is Git. Git allows us to harness automation, and GitOps is a pool-based mechanism for applying configuration changes to software or hardware, often on commit, or on pull request merge, where traditionally organisations have silos of expertise in specific areas of technology, cloud-native organisations strive to evolve the DevOps model of cross-functional teams, configuration, infrastructure as code, and managed services. And of course, a successful security journey requires collaboration on decisions and outreach to affected teams enforcing new controls or policies. Understanding any negative impact of certain security controls may influence the final choice. Automated verification, rotation, and pipeline automation reduces the opportunity for human error and security of systems, as we well know, and containers make automation easier and more repeatable. These processes occur in all environments with tighter controls in automated pipelines as they approach production. So, that is the level set. Let's move into why Kubernetes theoretically has these benefits. I love this diagram. It's from a research paper that's actually linked in the book, but not here. This is the lineage and the tree by which we find ourselves at the point of Kubernetes and containers. The technologies we use come from the 1950s, and we can trace Kubernetes back from Borg, Docker, LXC, Linux, Unix, Multix. Okay. If correctly configured, containers can be more secure than VMs. Dramatically increasing the fidelity of security policy, it's possible to apply to an individual process. VMs more generally work on a system-wide configuration to filter for malicious or unexpected activity. And in legacy systems, system-wide controls are generally too loose. Containers offer a new opportunity to apply filters at a more granular level on a per-process basis. And to recap, a container is just a wrapper for a process. It can be used to apply this detailed per-process runtime configuration, a trusted list of system calls, file system accesses, binaries and libraries, capabilities afforded to a process, and more. Containers are just a microcosm of Linux running multiple times and been packed into a larger system. So the nature of the security context configuration available in Kubernetes gives us this opportunity for very granular security configuration, applying policy just around the process. This highly targeted application of policy serves to reduce the blast radius or the impact of breach or vulnerability or remote code execution in a web-facing application, because the set of available actions available to an attacker is locked down and the container is limited to only those behaviors that are required in order to fulfill its default purpose. This stops, for example, an extract transform load style data workload from being able to port scan other containers or stops a web application from spawning a shell. This, then, is a representation of a Google Kubernetes Engine cluster, isolation at different layers of the Kubernetes stack. This illustrates the principle of security in depth in the centre of the containers at this point, image management and runtime security are paramount and the elements of the developer and DevOps sphere of influence. Moving outwards, layer by layer, we transition into operational responsibility in DevSecOps until we've reached the outside level. The project Googles outer isolation that is partly like a VPC in AWS or like separate accounts. So, DevSecOps, automating operational integrated security assurance. That's tricky to say. In a sense, this is nothing new. It's just sensible testing. CloudNative offers a slew of new tooling opportunities and paradigms that are informed by the lessons learned in DevOps over the past 10 years. Continuously secure delivery principles. OK. So, Kubernetes is supposed to be wonderful. It has a great deal of complexity. But it can be more secure if correctly configured, well tested and well managed. How do we know which controls to apply where and when? Well, in any threat model for any system, we first identify our adversary. In this case, it is dread pirate captain hashjack, 8-bit monstrosity scourge of the internet high seas and control planes archetypal adversary in these situations. He occupies a nation state level of criminality. That might be analogous to a fancy bear or APT 1342. These are organisations that operate in the shadowy netherworld between state sanctioned cyber criminality and private online gangsturing. And as we see on the next slide, they may be involved in anything more or less than physical intimidation. These responses are in personal threat models modulate where we're choosing to apply controls and what level of defence we will go to. And yes, he is also the protagonist of the book, Hacking Kubernetes. So, this is the adversary matrix that control plane uses on engagements with our customers. The aim here is to identify the capabilities and motivations of the potential attackers to our systems and then define our controls appropriately. So, as you can see, at the top, a vandal or a script pity, these may even be drive by attacks. There is minimum cloud native security, minimum viable, should be the avoidance of shipping CVEs to production. If we can be remotely exploited with Metasploits, we have not done our job and in fact we should be embarrassed. Moving down slightly, the motivated individual maybe becomes slightly more difficult because there may be other mechanisms that they choose to employ. But still, modifying open source supply chains is an interesting version of this. But still, we don't expect a great deal of technical complexity with these attacks. Inside is where things start to get more difficult because it relies upon very carefully modulated and configured set of internal security controls. People should have enough access to do their job and be proactive to be able to move beyond their responsibilities without breaching security criteria. But the knowledge of inside information means that this is a more difficult thing to lock down. Organised crime syndicates, this is where our captain hashjack level of adversary is. They probably have reasonably significant resources. They may have access to purchasing zero days on the black market. They may be generating their own, for example. However, as with all things, there is a limited amount of time available to expend upon a given target. By hardening our systems to raise beyond a minimum bar, we help to dissuade or defeat this kind of attack. The cloud service insider is an especially difficult problem. When we look at the Capital One hacks from a few years ago, that was somebody using privileged information. The account identifies for Capital One's accounts. They took that information, they found a web application firewall bypass with a remote code execution with a misconfigured IAM policy. So they were able to perform service side request forgery, which subsequently allowed them to dump customer information and embarrass Capital One. The origin of that attack was not only the knowledge of the remote code execution, but also that vital account information. Finally, foreign intelligence services, there is a level again of personal safety where one questions at what point would one hand over the keys to their own kingdom. With threat modelling, we have identified our adversaries. Next, we would want to look at the data flows and classifications through the system. These are imperative to understand and quantify our controls. This is where the repeatable, the claritive nature of Kubernetes configuration comes into its own as the barrier to entry for this work is dramatically lowered by reuse. Knowing which controls to implement then is a product of the threat modelling exercise and here we're mapping the effectiveness of the security controls against the ease of their implementation. This gives us an order of precedence and a suggested implementation ordering. We can see the ease of implementation for pod level network policy. It's worth doing because it's not difficult to do and it blocks pivoting and horizontal transfer, whereas something like setting up a service mesh is slightly more difficult. This is actually not indicative. Service mesh is a pod level network policy. I would say it's probably slightly the other way around. Service mesh is very difficult to maintain. Network policy is slightly lower. This is one view on how this will land for an organization of a specific skill set. I suppose the thing that I forgot from my slides is the supposition here is that network security engineering is not high on this organization's or this one developer's backlog. Then we look at something like code signing. The security benefit is much lower and the ease of implementation is a little bit higher there. We can then extract from this the controls that we would want to implement a quantifiable ordering. This helps us to balance the business value of spending money to build controls to test them so that they continue to work while the system is on the maintenance or development with the ultimate cost of the ongoing control. If developers are constricted by overly restrictive controls, they will not be retained at your organization. Ultimately, there's no point having the world's most secure system if it's not only unusable and maintainable, but also features are being shipped more quickly by our competitors. From the threat model, the next stage is attack trees. These were built by control planes for the financial services user group in the CNCF three or so years ago. We use these to enumerate the possible failure conditions and we apply controls over the branches of the trees so that we can see the efficacy of a single control in multiple different locations. Again, the balancing of controls and maintainability with the developer or the operator experience or the runtime experience or the socks experience from having those controls alert are fundamental to doing a good job in this way. There is an O'Reilly course on threat model in Kubernetes. Again, written by control plane, a lot of this information is in the public domain and open source. We also deliver it privately if you would like it for your organization. Okay, on to the supply chain. So the three four Cs rather of cloud native security. We start with the code. The code changes frequently. It is the soft underbelly of a Kubernetes cluster. It is meant to move quickly and to have bugs because we're delivering features and we're looking to be competitive in the market. We cannot have slow waterfall style releases. We're looking to operate in an agile for some definition of the term manner. So we shift left. We apply as much security testing as we can, but we also are cognizant of the fact that at runtime the file system of the code is where that sits. A container image is a table that contains a file system configuration with standard Linux mandatory access controls like the owner of the file and its read write permissions, et cetera, along with the application and its dependencies. It should be shorn of anything extraneous because as we can see from things like leaving bash in a shell, sorry, leaving bash within container, remote code execution that's able to invoke bash and spawn a reverse shell quite easily because of the virtual dev TCP endpoints. So we should remove these kind of things. Also, this is where defense in depth. We should always run IDS because nothing is infallible. The point being, the configuration of the code inside that container image is all important, but we expect it to have a degree of vulnerability because we're not assuring it over a long period of time. We're moving quickly. We're delivering business value. This is the nature of modern software developments. Then we have the container. This is the runtime configuration where we can apply discretionary access controls like set comp, app armor, system call filtering, user space interrogation capabilities. This is where we can apply that very fine and granular per process policy in order to secure the runtime of our applications. This then runs in a cluster. A container is just, as I say, a microcosm of Linux. A cluster then orchestrates many small instances of Linux across a cluster and attaches storage, gives it access to service discovery and interpod networking. These, again, are potential positions of escalation. Usefully, because we have this declarative orchestrator, we can reuse the same controls across multiple clusters. Of course, different clouds is the dream, of course. Then finally, the cloud or colo. Obviously, remote code execution into a container with AWS keys or account keys for your cloud account is potentially external remote code execution cloud account compromise. So, threat modeling, carefully delineating what can do, which process can do what. One of my passions at the moment is workload identity, which essentially removes those static credentials. But this is the antithesis of hardened deployments. We would like things separated and certainly not escalatable from remote code execution to cloud account takeover. So, within the supply chain, we have a trusted producer, a third party dependencies. This might be Maven Central or NPM or PyPI. If CaptainHashJack can insert his code into one of those dependencies, then potentially he can fire off a reverse shell. It essentially gains some form of persistence or command control within our organization. So, how do we attack a supply chain? Well, we can get on to the developer's machine and commit as them. We can infect or attack the source repository. Probably easier if that is hosted inside our organization. The build infrastructure itself, this is a SolarWinds type attack where we modify the code as it's being compiled or as it's being built into a container. We can infect a trusted supplier, which is a dependency of a dependency. Obviously that transitive chain continues in perpetuity as long as the time. We can infect a trusted package that runs its roots within the container build itself. All of these things count as things that we are consuming from a producer. And actually, if we publish open source libraries, we de facto become a producer ourselves. This is a wide-ranging and relatively difficult problem. Finally, we infect a runtime environment. It kind of doesn't matter if we have compromised the infrastructure itself. What can we do in this space? There are lots of things. Reproducible builds allow us to build the same package in multiple places. If the build infrastructure is compromised in one, it will have, with a deterministic and reproducible build, the compiled build artifacts will differ in hash. And so we can detect compromise. This is how Debian, Arch Linux, various other places, the reproducible builds.org projects enumerate these. This gives us some certainty that the build infrastructure that we're running on hasn't been compromised. SolarWinds reaction to the Russian compromise was to deploy a cloud-native dual pipeline infrastructure in the same way. Then we've got artifact and build signing. There is some nuance here, because actually it is the contents of the artifact that we care about more than the signature. But the signature will guarantee at least the freshness of the artifact that it's come from the person who controlled the key at the time it was signed. And that it's the same artifact that came from the other direction. This is possible with lots of different tools, but there's some fancy new ones here. Software builds of materials. These entered the US legislature with the Biden ordinances at the beginning of the year. This details the composition of a piece of software. It is the shopping list, the ingredients required to rebuild that piece of software. Again, it's useful when it goes to the right level of depth. These things are nascent, I'd say that, probably three or four years or longer that they've been in development, but they're nascent in terms of adoption. And there are still some intrinsic problems to do with the depth that these trees are walked to. Also, they're currently just shipped by open source software. If they're generated at build time, are they then valid? Do they match what you would then infer by running the same build of materials discovery tooling when it's distributed? What about vendor software that you can't then reverse engineer or something that's been tree shaken or something that's been been packed in some way that obscures it? There's also the question of should these be available for software as a service product? Should our cloud provider provide a build of materials for the APIs that we consume? The answer to all these things should be yes, but there's so much nuance and complexity, especially around validating the contents of these things that we are, as I say, at the beginning of this journey. A contributor analysis that Linux Foundation are doing a lot of work here, it is very difficult to unmask a contributor in an oppressive regime that may put them, for example, a journalist that might put them at risk of reprisals. It is also necessary to have strong identification guarantees to prevent collusion because two anonymous accounts could merge a pull request. This is almost intractable. I don't know where we're going to get to with this. The open SSF, the Open Source Security Foundation in the US, another Linux Foundation subgroup are attempting, well, attempted to fix this with a developer identity working group that's then folded in, I wouldn't call it chaos, but without conclusion. So there is some difficulty here. Without a kind of KYC form of identification of customer, it becomes difficult or contributor in that case. And then finally, SEMGRAP. This is only useful where we have access to the source code. We're at an open source convention today, so it's useful when ingesting third party code into our organizations to mitigate third party code risk. We can run some of these modern static analysis tools that operate on abstract syntax trees. They can find code patterns for ASTs across multiple languages and SEMGRAP is the most interesting one in the space. So there's plenty of things that we can do. The complexity of these is huge. Of course, this is where I spend a lot of my time developing things for customers as well. Without a threat model, it becomes a question of throwing the kitchen sink at something. And so, again, sort of delineating exactly what's needed is all importance. This is the nature of a reverse shell. Just briefly. The ultimate goal of an attacker is to gain command control from within the estates. I guess from a zero trust perspective, we don't like to think about perimeters anymore, but literally we do firewall things. The things inside those firewalls should then mutually authenticate at all times. But nevertheless, this is not what we want to happen. Okay, I will whizz through some of these in the interest of time. This is a little bit more book heavy, so this is my view on container namespaces and how they look in a pod. What is a container escape? If you watch the form of this talk that I did at KubeCon, I demo the dirty pipe container breakouts, that is writing into root-owned memory and firing a reverse shell back from that root-owned memory into a container, which essentially spawns a shell on the host owned by root from inside a container, which is mildly terrifying. There have been lots of container escapes. Ultimately, this is a good thing. We want software that keeps on moving and is developed rapidly. Part of the price that we pay for that is vulnerability. There's no way that we would want to move so slowly that we assure and pen test everything. Everything is a balance, of course. Part of my work with Open UK is ensuring that security professionals are applied to some of the open source projects that are critical to us all and the safety of the internet. This is a view on how a reverse shell from a dependency actually connects back to the attacker. Again, the book goes into a lot of detail on these things and I will not bore you with it now. What do we do with malicious code in a container? Pod security context and capabilities are imperative because they are the security controls exposed to us by the Linux kernel and they're abstracted all the way up from the kernel through a container into Kubernetes. They're low level security tools that we should absolutely use as our first line of defence. Image scanning, minimum viable security is preventing the shipping of those CVEs to production. IDS and intrusion detection because nothing is entirely secure and we can also do some interesting build time behavioural analysis. There are a couple of projects at the moment that we're working on. One is also to do with smart contracts and distributed computer data for very large data sets for IPFS and Filecoin. Identifying a malicious build or an anomalous build is very noisy. Again, I have to talk about that afterwards. There's a lot of things going on there. Control plane test testing. This is my personal view on how to penetration test a container workload. Again, it is just Linux, but the book goes through this step by step. We have this opportunity for next generation sandboxing. This is running virtual machines around containers or a combination of containers and virtual machines using things like Firecracker and Gvisor. These projects do insane things. Gvisor has re-implemented the Linux kernel in Golang to avoid memory safety issues inherent in C. Firecracker takes QMU and slices everything down. It boots a virtual machine with, I think the control on delete keys are the only keyboard, anything supported by the keyboard driver. They boot very quickly. They move untrusted application code one degree back from the Linux system call interface, which is written in C, which is vulnerable to everything that C is. Obviously memory correction and safety and all that bad stuff. By writing things, Gvisor is Golang and Firecracker is Rust. These are memory managed, but low level languages. They come at a cost of some complexity and debugability, which is the ultimate balance. Okay, a little bit of Kubernetes. Again, what is a cubelet? The point of this is more that it's useful in the book. But hard multi-tenancy is difficult and actually segregating our workloads with different data classifications in the same cluster is verging on impossible because nodes are not namespaced. The concept of a node is not namespace in Kubernetes, so we can have a node pool, but we can't have a per namespace node without abstractions and other code on top. Layers of security testing. I'm just whizzing through because I'm almost done for time. Again, sort of expounded into the book, but the point is all these things must be tested automatically. We also care about constraining talents with namespace policy. We should define our namespaces based upon the security controls that they offer rather than the abstraction that it's nice for an operator to interact with. And there are a few different ways to slice this particular pie. Open policy agent and Coverno are very useful. We're almost done here, so what are the risks of using Kubernetes? They are manifest. Here is that list for posterity. Again, I sort of appeal to my own authority in a fallacious way. It's all in the book and there's plenty more in there. It's always worth keeping Kubernetes updated because even though they've extended the lifetime window for each release, things do fall out of maintenance relatively quickly. And control plane do this for a living. It is a passion. We've got 50 people across Europe and Australasia. If we can be of any help, please do come and talk to me or approaches via the contact form. Thank you for your attention.


Cam Newton is the football quarterback for the Carolina Panthers and he's been vegan since February Seeing a sharp decline in his performance with an underwhelming start in two games to begin the 2019 season he now has a lingering left foot sprain that will cost him at least two more games Even a strength and conditioning coach was on to something now You take away the most valuable part of that diet and there's just no way around it He can't recover as well with less nutrients with less calories and with less muscle mass It's just not going to happen There are plenty of examples of other NFL players Tony Gonzalez as well as Gerald McCoy Going vegan and losing size as well as strength But as usual the vegan mongoloid advice of not eating enough calories or Protein remains the consistent message. They weren't doing the vegan diet properly So why do vegan athletes see a sharp decrease in performance and almost immediate injury within months? First we have to understand what muscle building is Anabolism many of you might be familiar with Jim Brose drinking protein shakes right after their workout So they don't go catabolic Remaining in an anabolic metabolism, but anabolic pathways use ATP that is actually produced by Catabolic pathways these two catabolic pathways are the citric acid cycle aka the Krebs cycle and the urea cycle a Very simple explanation of why a vegan diet doesn't allow you to Recover optimally or even perform optimally is because a plant-based diet does not provide the nutrients that your body Requires to run these two processes in an optimal metabolic state It's evidence that there aren't any naturally muscular vegans They all built up their muscle mass before following the diet or they used a combination of steroids and Artificial supplements to get where they are. Let's take a look at the anabolic pathways right off the bat We see that a vegan diet would be lacking both fat and protein a lack of fatty acids in the diet impairs glycolysis and Acetyl Coenzyme a metabolism a lack of protein impairs pyruvate metabolism Acetyl Coenzyme a metabolism the citric acid cycle and the urea cycle these processes are crucial for energy Metabolism as well as amino acid metabolism Ultimately determining energy capacity muscle building and recovery capability a vegan will swear up and down That your body can make all of the amino acids it needs on a plant-based diet and on paper That might seem true But the two main processes needed to synthesize amino acids becomes compromised when you are vegan and these Unironically are those same two processes important in muscle building that we mentioned earlier the citric acid cycle and the urea cycle The citric acid cycle is where our body synthesizes amino acids using pyruvate and acetyl Coenzyme a your body needs proteins and fats to make acetyl Coenzyme a but as a vegan You're depending on the citric acid cycle for certain proteins and the diet is lacking in fats So without question the citric acid cycle is not working optimally a waste product of amino acids is ammonia Which is highly toxic. That's why the urea cycle converts ammonia into urea excreting it through the kidneys the problem is that this urea cycle Requires acetyl Coenzyme a as well and it requires glutamate an amino acid contained mostly in animal foods On top of that plant-based proteins such as soy and wheat are more readily converted to urea When compared to animal-based proteins, but the urea cycle isn't only for removing ammonia It is needed to recycle precursor molecules for the citric acid cycle including amino acids On top of this a vegan diet is lacking in vitamin B12 Vitamin B6 as well as folate which results in high circulating Homocysteine levels another amino acid putting even more stress on the urea cycle as well as the kidneys These metabolic cycles are limited so much on a vegan diet It becomes obvious why athletes can't even recover let alone build muscle and this isn't even going into the functions of acetyl Coenzyme a Every cell needs it to turn nutrients into energy and lack of acetyl Coenzyme a means lack of energy Which means lack of performance it is needed for steroid synthesis all of your hormones And we know a male athlete with low testosterone is not going to fare. Well It's needed for acetyl choline which plays a vital role in our central nervous system as well as our peripheral nervous system Activating muscles and acting as a major neurotransmitter pretty easy to get injured if your muscles aren't firing properly acetyl Coenzyme a is also needed for melatonin production sleep hormone an athlete that doesn't sleep Well doesn't perform well, and that's not even half of it for acetyl Coenzyme a what explains this even better is When vegans use artificial means to enhance their performance by taking steroids You are removing the need for acetyl Coenzyme a in steroid hormone production also likely lowering the need of cholesterol in the body It's arguable that taking testosterone on a vegan diet is the healthiest thing you can do Because you're impairing your body's ability to produce testosterone on a plant-based diet Same thing with vitamin B12 shots You are taking massive amounts of stress off the urea cycle off the methylation cycle when you are consuming Exogenous B vitamin supplements likely increasing overall muscle synthesis But you will never see vegan athletes at the same level as others If you were able to replicate the complete nutrient profile of an animal-based diet with all of the fat soluble vitamins Cholesterol minerals fatty acids then you would see vegan athletes performing at the same level But we don't see that what we actually see is quite the opposite You have all of these vegan athletes claiming. Oh, I want vegan. I feel so much better. I'm doing so much better But that's not what is actually physically happening. Their performance is dropping They're getting injured Novak Djokovic Serena Williams any athlete that goes vegan is seeing a sharp decline in their performance and they are getting injured very quickly because their body is not capable of repairing tissue and Then they are never able to recover from that injury Thank you guys for joining me. If you could please like the video subscribe hit that bell icon Share the video if you can if you guys would like to support me further Please go to Frankie's pre-range meat.com high quality nutrient-dense animal foods at an affordable price We just had a really high quality local grass-fed cow brought in and we're offering a 17 pound local beef box delivered to your door for less than ten dollars a pound limited quantity guys So again Frankie's from range meat.com check that out You can also go to Frankie's naturals minimal ingredients minimally processed hygiene and cosmetic products Thanks again for joining me guys and enjoy the rest of your day


Hey, I'm Andrew Connell. This video is an overview of one of the chapters in my course, Mastering the SharePoint Framework, that's available for purchase on my site, boytanos.io. This overview video is going to give you an idea of everything that the chapter covers. You can learn more by checking out the description and the notes below the video. If you got any questions about this chapter or about the course in general, just make sure you drop a comment below the video and I'll be sure to get back to you. So with that, let me get out of the way. Enjoy the overview to this chapter. Hi, I'm Andrew Connell and welcome to my chapter on Automated Testing of SharePoint Framework Solutions. Implementing automated testing within your custom solutions, be they SharePoint Framework projects or any other custom code project, is widely considered to be a good practice. Projects that include automated tests are more robust and are of higher quality because the same tests can be easily run repeatedly to check for errors. Many developers skip this step of adding tests because it's hard and it's confusing. But in this chapter, you're going to learn the practices of not only why you should test, but the different types of tests, what you should test, and how to implement automated testing in your SharePoint Framework projects. So what are we going to cover in this chapter? We'll start by looking at the automated software testing concept, the what, the why's, and the how's. Then we're going to look at the tools of the JavaScript testing trade as you're going to see there's a lot of different tools. So we'll look at all these different options that we have. We'll then look at how to test SharePoint Framework projects and then work with a tool called Jest to test our SharePoint Framework projects. We'll see how to implement it. Then we'll learn a little tips and tricks and some debugging. And then we'll look at how to report on Jest tests using a concept called code coverage. And we'll have even more tests as this chapter evolves. Now, the challenge with this topic is that it has fingers in so many different places throughout my course. And what do I mean by that? Well, the topic of testing has some core aspects that you need to understand, such as the types of tests, the tools involved, how to configure a project, and how to write the first few tests and run them. But for many developers, this may be everything that you're looking for. But for others, you may want to go deeper and learn about specific things, like testing React projects or faking or mocking and spying. Let me just mention a quick little note here about this chapter. I consider this chapter to be an eternal work in progress. Just like the rest of the course is evergreen, this chapter will be as well. Initially, this chapter is going to cover the core aspects of getting up the speed on testing JavaScript-based projects, all the stuff that you just saw in the last slide. But here's how I plan to move forward with this topic and this chapter. There will be a lesson or multiple lessons related to testing React projects. But those lessons are going to be in this chapter. They're going to get added to the React chapter to keep the React lessons all together. And I expect to do the same thing with the Angular chapter and the Vue.js chapters as well. I'm also planning lessons on dealing with the complexities of dealing with dependencies, such as using mocks, fakes, and spies. Those lessons, they're probably going to show up in this chapter. Now, do you have topics that you're looking for that I haven't mentioned so far that are covered in this chapter? Let me know. Leave a message in the comments below this video at the bottom of the screen. If you see someone else has left a comment for something that you'd like to see, make sure that you voted up using the tools that are provided. Okay, so let's get started.


Just picked up this beauty from Mountain View Dodge Dustin did a great job looking after us come on up and have a look


So between meals, there must be at least five to six hours of space. The ideal way to live is, there is no sleep in my life. But that's not possible, right now, still body has some inertia, so it sleeps minimally. Rest of the time, it is at ease.  When it comes to food, one of the most important things that you must be conscious of is, on a certain day when you eat a certain type of food, whatever you eat, you must consciously notice how quickly does it digest and become a part of yourself. Any food that you eat, if it lasts over three hours, that means you've eaten bad food and that is something to be either avoided or reduced in quantity. If food moves out of your stomach bag within three hours, this means you're eating something that your system can handle efficiently. It may not be the best food, but your system is able to handle it. And between one meal and the next meal, if you create a clear gap of five to six hours and in between if there is no other ingestion, you will see the cleansing process in the system on the cellular level, cleansing will happen. This cleansing on the cellular level is most important and significant for a healthful life. So between meals, there must be at least five to six hours of space. If you're over thirty years of age, two meals a day, two good meals a day will suffice, one in the morning and one in the evening. After the evening meal, before you go to bed, there must be a minimum of three hours and if there is a certain amount of physical activity, not necessarily very heavy or strenuous activity, just simple walking or maybe a dance or something like this, create something for yourself where about at least twenty to thirty minutes, there is some physical activity after the evening meal. If you do this, largely your system will be healthy. Yeah, means on one level the blood has lost its iron, that means you lost your steel. Okay? You lost the strength in the body. You'll feel exhausted, simply exhausted for nothing because once the necessary iron is not there, your ability to carry oxygen through the body is less.  So building oxygen into the blood is one of the important things because how healthy the body is, how easily it rejuvenates itself depends on a high level of oxygen in the blood and that capability will go down. Particularly women have to be careful on this because of the biological process that their hemoglobin content may go down and their ability to carry oxygen in the blood will come down which will make them unnecessarily exhausted, will make them look unintelligent and yes, if the RBC is low you feel dumb because there's not enough oxygen in the brain and it doesn't function the way it needs to function, both the body and the brain. So to take care of this, one of the simple things is you consume a little bit of honey in warm water on a daily basis and you will see slowly the RBC content will go up. If there's more oxygen in the blood, suddenly you feel a burst of energy. Suddenly everything is active, the rejuvenation system in the body is going up, the dead cells are being replaced quickly. The level of inertia that you feel in the body is much lower, the level of inertia that you feel in your mind is much lower. So honey, it has different types of impacts on the system. If it consumed raw, it has one kind of impact. If it is consumed in cold water, it has another kind of impact. If it is consumed in warm water, it's a different kind of impact. We want to consume it in warm water here because we want the system to open up. If you put it into boiling water, some part of honey will turn poisonous. So you should never put it into boiling water or you should not cook the honey. I know in western societies people are making honey cakes and stuff, they're cooking it. If you... if it crosses a certain temperature, then honey will turn poisonous. So it must be put into... like it's in a temperature that is drinkable. Into that you put. If it's boiling hot, you don't put. This sleep is not a requirement in one's life. What the body requires is rest. Sleep is just one form of rest. Lot of people are beginning to think in Tamil Nadu if somebody says restpani karanga means they're sleeping. Need not be, you can sit and rest, isn't it? Yes? You can stand and also rest. You're running, if you stand, doesn't it feel like rest?  There are many ways of resting. The most important thing is rest means you're changing the energy equation where consumption is lowered, production is going on at the same pace. So after the period of time you feel rejuvenated because consumption has been lowered. Essentially you're managing the energy equation. If you're in equity activity the consumption is more. Whatever you're producing it's not enough after some time you feel exhausted because the consumption has been heavy. If you lower the consumption and increase the production after some time you feel energized. The ideal way to live is there is no sleep in my life. But that's not possible right now. Still body has some inertia. So it sleeps minimum. Rest at the time it is at ease. If you keep this at ease then sleep does not occur to the body unless it comes to a certain point of exhaustion. So body is never ever asking for sleep but it is definitely asking for rest. If you do not know how to sit here in a restful manner it will try to rest like this. If you can sit here totally at ease it'll sit here for hours without falling asleep. Otherwise this is the only way it knows how to rest.  Just move your attention from the top of your head down to your toes and see if everything is low and breezy and relaxed and at ease or you're sitting like this just bring this to ease as much as you can. Not everything is in your conscious level. As much as you can consciously bring it to ease. You will see suddenly if you are the kind who'll fall asleep at ten o'clock if you simply one hour you sit here at ease you will see your sleep will get postponed by half now. You won't feel sleepy at ten. Naturally you're awake.


but that changed from last year, so can't call it a routine yet. The basics? The basics. Okay. Guys, we're looking at you differently for your second and third game. Really, our first game went great. So did our second and third. We didn't want to change anything. We wanted to keep everything the same way. We hope that they're going to fight like hell to get that fourth game for us, but if we keep the same game plan, we won't let them. So as a pitcher, did you notice anything that Irvine's pitcher wasn't doing properly? Irvine's pitchers did well overall. It's just our hitters were locked in this weekend and I feel like they were hitting good pitches. What staff carries the baseball team especially for our team? I feel the pitching staff is doing great, but again, the pitching staff is only as good as their offense and our offense is phenomenal. So we're weighing the games because we're keeping them down and our hitters are just crushing balls that they need to. So aside from baseball, I heard that you're a pretty adamant ping-pong player and that you have a $90 ping-pong paddle. Can you tell us a little more about that? Our ping-pong table is in our cages. We play before practice, after practice, and I just want to, you know, have a little unfair advantage against my friends. So some of the guys on the team have told us that you happen to be in a country. Where does this come from? This came from a lot of different ways. My hometown is Auburn, California, and it's a little past Sacramento and there's a lot of hill folk and whatnot, if you want to call it that. They think I'm a country boy. Awesome. Well, thank you so much for speaking with us. Great job today. Thank you. Okay, thank you.


To celebrate the sacred spring, the blue hole that is the source of the San Antonio River, a local nonprofit organization is hosting reception March 9th from 68th for the opening of Art of the Sacred Texas Springs, a month-long exhibit at the Kelso Arts Center on the University of Incarnate Word campus. The exhibit, Organized with Headwaters at Incarnate Word, features 38 artists and more than 60 pieces, including photography, sculpture, and painting. As the artists stage their pieces for the exhibit, Diana Roberts, one of the organizers, part of the art collective, sets her hopes to exhibit both awareness and an often overlooked space in the city. It's very easy to forget in a bustling big city and an urban setting like San Antonio that we have these amazing natural resources around us, and they are these wonderfully quiet magical pockets that you can go to get away from everything. By viewing all of this artwork, you'll get a sense of that connection between the artist and their connection with water, but also to reflect on one's own connection to water and the resources that are around us. A lot of the artists that we ask are not necessarily artists who are already doing water painting to work, but they took the opportunity to kind of do some research about it. I have a little over 14 acres is covered in limestone rocks, so the idea of using what you have hit my head is a good idea. When cleaning them, they put out the smell you get when you're in a grotto here in Texas. I was trying to get all the life that springs out of the water here in Texas and springs that are so important. Part of the sale proceeds go to support the nonprofit Headwaters and Incarnate Word. The executive director, Alexandra, talked about the significance the spring has to the region and shared the background and mission of the organization. We're a nonprofit earth care ministry of the Sisters of Charity of Incarnate Word. They had originally purchased all of George Brackenridge's land in 1897, which was 283 acres, and they developed it. They sold it off over years to build their ministries, and then in 2006, they had 53 acres left that weren't disturbed, and they decided to set it aside as a sanctuary. There's evidence that people have inhabited here, have visited and utilized the loophole for 12,000 years at least. We continue to have folks from all different indigenous backgrounds coming to perform ceremonies here, pay their respects. We focus on environmental education, ecological restoration, and then being a space for personal reflection. Everything we do is free for the public, from kids to adults. We want everyone to have access to the head of the river, and similarly, we want everyone to have access to both natural environments and cultural and artistic resources. 150 years ago, it was a geyser, and 150 years before that, it was a geyser 20 feet high by the Spanish records. And what's happened over the years is that as San Antonio's population has boomed, the Edwards aquifer level has dropped, and it no longer has the pressure needed to push the loophole out as a geyser. And in fact, some years, if we're in drought or if people are really overusing water, it doesn't flow at all. So unfortunately, right now, at the time of this filming, it is not flowing presently. The aquifer is not high enough. But the spiritual and creative energy is still there, and we're thankful that these artists are sort of channeling that and sharing it in a different way, keeping the idea of the springs flowing even when they're not. The Council Arts Center is on the University of Incarnate World Campus. The celebration is part of a pilgrimage of sacred springs in southwestern Texas, which include the headwaters at the Comel River, Barton Springs, San Marcos Springs, Tripping Springs, and San Pedro Springs. To learn more about the other events in the series honoring San Antonio's sacred spring, check out www.headwaters-iw.org.


I thought, oh man, if the Lakers make it into the playoffs and if the Lakers figure out how to beat the Grizzlies, like this, anything could happen. And we're getting there. Awesome acidity, I mean.  But Eddie, are they contenders? Is this a possibility?   That is their matchup if they win this series. And then Denver will talk about, it looked great yesterday and they have a favorable matchup, obviously. But I mean, it's kind of lining up for them. I hate the Warriors' matchup for them, but if they're getting going, LeBron played bad yesterday in my eyes. Like, he couldn't hit a shot. He definitely was really passive.  I'm shocking when they had five turnovers, felt like he had way more. Anthony Davis was okay. He was pretty good defensively. Obviously had the injury and dealt with that. They had Ruiz score 29 points. They had Austin Reeves take them home down the stretch. Also, that little final 90 seconds where they had like four leakouts in a row and just kept dunking it. Usually a team might turn the corner and kill some clock. They're like, no, we don't like the Grizzlies who are gonna keep dunking. We don't care. There's something to this Lakers team. There is. They just have a good energy about them and they defend. And that's what you need in the playoffs. You gotta defend.  So are they Consenders? Yes. Do I think they make it? Do they run the whole way? I don't think so, but... But man. There have been crazier things that happened. I was gonna say, the league office is in on this. I mean, I think we all agree that there's something going on. No, I'm just kidding. I'm the only one who thinks that. But John Morant, the big story as well, got injured. Any news on that? So Michelle, I'm told he will be re-evaluated today. They're gonna see just how bad that hand injury is. He did say it's not a wrist injury. It's a hand injury. But he said his game two-status is very much in jeopardy. He's not sure if he's gonna play. And that looked nasty. I mean, his fingers literally all went back. Oops. And just imagine doing that just normally. Now just imagine doing it when you're full speed, going down all your body pressure landing. So it doesn't look good for John Morant right now. And I don't know if this team survives without him. I don't know if they survive with him against these Lakers. It's funny, because during the regular season, they had a lot, obviously, and they had a lot of games without him. And they did okay, but this just feels like a different animal, right? Evan, when I do that, you know, when the ball hits you and it pops your finger, I'm out for like two weeks. Oh, we get you. You guys are different. I don't know how he's gonna make me back for this. I don't know what they're about to do for him or anything, but I just hope a speedy recovery.  Oh, sure. I don't think if the Lakers beat the Memphis, this is an injury argument more so than it is. The inevitable. So, you know, I kinda wanna see both teams full strength. Yeah. I agree. It was that moment, too. For the last two seasons, we talked about Jaumarant's style of play. That play is what everyone was always afraid of, like so athletic, and then we see that happen. There was another upset yesterday. Okay, goes in for layups like this, and I have no comment. I mean, he's been going reckless abandon his whole career. He's had injury after injury, it's unfortunate, but that's what makes him so great, but there's also a curse to that as well. That is, that's the fear. A lot of combo yesterday saying, should we get rid of block charge? And, you know, it's plays like that, it's plays like the honest play. I don't know, I don't know what you do. If you can't, as a defender, like actually getting people's way, I mean, you're just giving up dunks at that point. And they already put in defense with 300 keys. And we're already scoring 187 points per game. But can we get 200 at Evan? We want 200. I mean, that's what the Pans want, right? Vivek Manadeva believes we'll be scoring 200 points soon. The customer is always right. Customer is always right. Speaking of, Giannis, heats, heats, heat and buzz.


All right in this video I'm going to show you how to bookmark your dynamics pro to your Firefox web browser. All right so the first thing that we're going to do is we're going to go up to this address bar up here at the very top and we're going to click on it and we're going to type in mydynamicscrm.com hit enter then it's going to ask you to put your email address right here. I have a test account so I'm just going to put test account this is where you would put your email address and you're going to put your password and then secure login. All right so it's going to log into your dynamics pro. Next what you're going to want to do is at the very top there is a what they call a hamburger menu so up here at the top right where my cursor is you're going to click on the hamburger menu and you're going to see library and you're going to click on library and then you'll see bookmarks right here so click on bookmarks and then you'll see a bookmarking tools click on bookmarking tools and then you can view a sidebar which would be over here on the side or the toolbar so I'm going to click on the toolbar which is going to go right below your address bar so I'm going to click on it it's going to bring down your current options because I already have my dynamics pro bookmarked on here. All right so next what you want to do is after you have your bookmarks bar right here you're going to go back up to where the address bar is and go to the right hand side you're going to see the star and if you have your mouse over it'll say bookmark this page you click on it and then you'll name it so you can name dynamics pro and it'll ask what folder you can either do other bookmarks I like to do the bookmarks toolbar which will put it up here so bookmarks toolbar and then you'll see right there you're going to hit done and then now it changes to the dynamics pro right here now if you want to move now if you have a bunch of bookmarks there may be a arrow over to this right hand side over here letting you know that you have more bookmarks and you can just click on it and then you'll see the dynamics pro listed and you can click and just drag it to the front and since mine's right here I'm just going to click and I'm going to drag it to the left and you'll see these little kind of separators that in between and it says you know where you want to drag it to so keep on dragging it I'm going to just drag mine at the very beginning and release and then now my dynamics pro is on the bookmarks toolbar at the number one position but you could of course move it to the second position wherever you want


The process of working with the professional learning project can be broken down into six steps. The first step is looking at the goals of the project and considering the competencies involved, as well as the knowledge, skills, and attributes that educators can work on developing. The second step is looking at success and defining what does success look like within your own educational community. The third step is creating an inventory, looking at all of the professional learning opportunities and resources you've already explored and creating a list. This inventory helps inform step four, areas of strength. Areas of strength identify mentorship opportunities that you can provide other educational communities within the province. The inventory also informs step five, areas of focus. Areas of focus form the foundation of your professional learning plan. And finally, the last step is creating the professional learning plan and creating the scope and sequence of professional learning opportunities that you're going to explore.


Wait, wait, before you get mad, the title is clickbait just to get you to come look and you did when I say new Ghostbusters I'm talking about these guys 1984. They were not the originals for the first Ghostbusters You have to go back to CBS Saturday morning 1975 To this But I'll get to that in a minute first of all I got to tell you that I'm not one of these people who feels like my Childhood is sacred or that it's being stomped on or that it's being killed The reason I'm making this video is to tell you about the original Ghostbusters But I'll get to them in a minute. First of all, let me tell you about how I saw the 1984 Ghostbusters I had just graduated high school 1984 I was talking on the phone to a classmate of mine and she said that a group of them were going out to see a Movie and I invited myself along and it turned out to be Ghostbusters I had seen the commercials on TV, but I didn't know anything about it. Everything in it was a surprise It was great fun. We laughed all the way through it in 1988 This was decades before the word cosplay wasn't vented. I built my own Proton pack out of foam core and poster board and spray paint and scrap from a plumbing store It had a switch on the handset and lit up and everything so yeah I liked Ghostbusters, but honestly I enjoyed the real Ghostbusters cartoon more than I did the movie Speaking of the 1984 movie a couple of years ago when it was shown in theaters all over the nation as part of its I guess 30th anniversary. I went to a local theater that was showing it. I was really looking forward to it It was very poorly attended. There was just a handful of people there There was nobody laughing The movie itself wasn't as funny as I remembered it. It had been years since I had Sat through the whole thing but the most notable thing about watching it today is that Peter Vinkman's behavior is Completely unacceptable his sexual harassment of Dana Barrett and it is sexual harassment is constant and unrelenting and It's just not funny anymore. So yeah, like I said before I don't consider the 1984 movie to be sacred And speaking of which those original Ghostbusters I was telling you about before yeah 1975 CBS Saturday mornings produced by Filmation studios the premise of the show was exactly the Ghostbusters that you're familiar with some ghosts would show up and start making trouble The Ghostbusters would be called in they would use a scientific device called a dematerializer to send the ghost back to the spirit realm It was the Ghostbusters There was plenty of science fiction going on on Saturday morning in the mid 1970s a lot of it was coming from Filmation They had produced the animated Star Trek cartoons and they had just produced this bizarre post-apocalyptic show for kids called art to and Then Space Academy came a little later and those were great science fiction Really lofty ideas that was bringing kids up to a high level of science fiction appreciation Ghostbusters was not like that This was talking down to kids straight down.  I did Tracy took me to see his doctor. Well, what did the doctor say? Well, he said to eat 12 bananas and go sleep in a tree Yeah, it doesn't get any better than that. I'm sorry to say I can't even watch it Nostalgically today or ironically. It's just unbearable to watch I remembered it because I had watched everything on Saturday morning throughout the 1970s But by the time the 1984 Ghostbusters movie came out I was the only one of my own generation my own generation who remembered the originals Everyone else was like what what are you talking about? I was saying wait, there's already a Ghostbusters One of the reasons I remembered it was because my dad laughed at it every time the show started You notice at the beginning of the show. It says I'm Spencer. He's Tracy. I'm Kong Kong is not the gorilla My dad laughed at that every time So that's one of the reasons I remembered it The headlining co-stars of the show were Forrest Tucker and Larry Storch Who had been the headlining co-stars of another sitcom 10 years earlier called F-Troop and That is still how they are introduced today Forrest Tucker passed away in the 1980s Larry Storch is still with us But this is the year 2016 But what happened? What about this original Ghostbusters that you've never seen and nobody's ever told you about? I got in touch with an actual expert who is the official unofficial historian of Filmation Studios His name is Andy Mangles. Let him tell you the story In 1982 Columbia Pictures announced that they were doing a movie of Ghostbusters written by Dan Akroyd and The lawyer for Filmation whose name was Ira Epstein Immediately got in touch with them and said you're infringing on our title We would Hold you liable if there's any kind of similarity in concept. So Columbia pressured Filmation and its parent company to drop the letter and then they didn't get anywhere. So Nothing was really done in October 1983 Ira Epstein the lawyer was in New York and he was actually walking down the street and Walked literally walked into the filming of Ghostbusters So he as soon as he got back to the office. He sent off a letter to Columbia and said, hey We told you that we own the rights to Ghostbusters and you don't so and now you're filming this movie and We have an objection to that and Columbia said well you're doing this animated Saturday morning show And we're doing this live-action movie and it's called it's called Ghostbusters There's nothing to do with your animated show and Filmation said whoa, wait a minute. No The Ghostbusters was a live-action show It has everything to do with your movie because it's the exact same concept You just don't have an ape in yours or a gorilla in yours. So Columbia had apparently been filming the movie with Alternate dialogue where they were called ghost breakers or ghost smashers or things like that In anticipation of exactly this problem. So Columbia knew there was a problem They just kept trying to stonewall Filmation and kept saying no, no, no, that's not it They released the movie in June 1984 without having made a deal with Filmation Filmation went after Columbia in court and Columbia settled with Filmation ended up paying $608,000 for the use of the concept and The use of the name and title Additionally, Filmation was supposed to get 1% of the profit for Ghostbusters and any future Ghostbusters Property merchandising, you know, etc Now in Hollywood, you may know that That profit percentage is a tricky thing No movie has ever made a profit as far as Hollywood accounting is concerned including Star Wars including the Wizard of Oz etc The way the accountants work it is that that no movie ever does make a profit So although Filmation had 1% profit They actually never saw a dime no matter how successful Ghostbusters was and there was another mistake that they made in the Settlement they did not lock down the rights for ancillary animated properties Because they didn't think That Ghostbusters as a movie would be popular enough to create an animated series in 1985 Filmation announced a syndicated series for their own Ghostbusters cartoon based on the original live-action series and a week later Columbia announced they were going to be doing their own Ghostbusters cartoon series now Columbia was already in multiple legal issues over Ghostbusters they had Harvey Comics was suing them over the logo similarity to one of the characters from in the ghost Casper's ghostly trio and Huey Lewis was suing them over the fact that the theme song by Ray Parker Jr sounded so much like one of his songs and Then they had this lingering thing going on with Filmation So Filmation went to them and said Hey, we're an animation studio. You already need an animation studio We're also the people who own the Ghostbusters, which you do not Except for our agreement But why don't you just do the Ghostbusters with us? The problem was that there was an executive at the company Westinghouse that owned Filmation And they said why do we need to do an agreement with them? We'll just continue to do our own Ghostbusters. Let them do their own. They won't ever get anywhere with it Of course as we know both Ghostbusters shows hit the air the real Ghostbusters was Columbia's version based on the movie and Ghostbusters was the Filmation version based on the old live-action TV series both of them are on the air at the same time It really confused people neither neither company was tremendously happy with the outcome Because in 1984 when Columbia settled out of court for the use of the concept and title and name for Ghostbusters They there was no blockage of an animated property. So It was a costly lesson for Filmation to learn in that sense because had they just put in language that said you may not produce an animated property without Using utilizing Filmation Studios or you may not produce an animated property at all Then that wouldn't have ever happened But because in the settlement there was no provision that said Columbia couldn't produce an animated property. They were able to go ahead and do so because they had paid that fee $608,000 for the concept the name and the title Nobody would argue that Ghostbusters 1984 was the biggest hit of the year and the biggest moneymaker According to box office mojo, you had a budget of 30 million and over its lifetime It's made almost 300 million but according to the Hollywood accounting by Columbia Pictures as Andy referenced They say the movie has lost money Hollywood accounting is a very real and recognized thing. It's so well recognized that it even has its own entry on Wikipedia Take a look. You'll be horrified So my thing is I liked the new Ghostbusters when it came out in 1984 But today I have problems with it because of the sexual harassment content and because Columbia pictures never paid the Creators and I always have problems with people who don't pay creators Marvel and Disney So this new new Ghostbusters that's coming out later this month. I see some people who say it's a Sony picture I see some people who say it's a Columbia picture. I don't know. I'm not interested in it I'm not interested in general in new movies, especially new comedies They're not good. They're not funny But I do have some free movie passes for donating blood. I may use that I Want to thank Andy Mangels for his help and I want to thank Jerry Beck for putting me in touch with Andy This has been fun for me. I hope you've learned something and I'll see you next video And don't get me started about Monster Squad Please remember to press that like button it helps my videos get seen and then subscribe so you can come back next time I do science fiction book TV and movie reviews all the time and please consider becoming a patron There's a link in the description below


Dw i aelod, mae'r Nasiad yng Nghymru yn ystod yn gwaith o fwylo'n gyllidion gweld, yn cael ddawol wrth gwelwyd. O fynd i'r ddweud y gwaith, mae hynny'n fwylo i'r gwybod ar gyfer carbonyddol o fwylo'r gwahau cyllidion. Mae'n bwysig o 62% yn rhan o'r llaw o'r gwahau. Yn dahl, mae'n bwysig o'r gwaith, mae'n ddweud ar hynny'n ddod 38%. Mae'n ddweud ar y buswch ac yn eitbwyd o'r cyffredigol yn cymaint â'r CO2? Mae'r 1 cadwiat yn ychwanegau a mae'r bysfyrdd yn bwysig y bysgwyr yn gweithio'r bysgwyr. Felly, credu'r 46% ddweud y CO2 yn ei wneud, rydym yn ei ddweud mae'r bysgwyr yn cael ei ddweud. Mae'r bwysig yn llwyddoedd ac mae 30% yn ddweud y bysgwyr yn cael eu ffordd. Ond mae'r bysgwyr yn sicr o unig o'r bysgwyr yn cael ei ddweud. A gyrsgwyr, mae'r event yn yr El Nino a'r bysgwyr yn gwneud y bysgwyr yn dweud y bysgwyr. ddiddio eu hunain yn gymryd ymlaen. Mae hyn yn ddim yn ddiddordeb yng nghydfod y Lennu El Nino yn cael ychwanegu yng Nghymru. Yr unrhyw gwestiynau, mae unrhyw o'r ddweithio â llain a'r bysfyrdd y bysfyrdd yn ei hynny a'r chalen llunio lleddau bryddol yn gwneud o'r ddweithio'r ddechrau ffyrdd anhygoel. Yn y bysfyrdd ymlaen, mae'n ddweithio i'r rhain cyllid. Mae'r hoffi'r hoffi ar gyflawn o'r rhain. Mae gweithio gweithio'r cyfnod CO2 yn yr adnysg. Felly mae gweithio, y dyfodol cyfnodd cyfnodd cyfnodd C02 ar gyfer ar gyfer y gweithio Gwyrdd. Yn y gallwn gwneud hynny, mae'r meccanidd. Yn y gwirionedd erioed, mae'n cyfrifwyr ar gyfer y cyfan sydd cyfoedd cyfnodd cyfoedd C02 ac yw'r cyfnodd cyfnodd cyfnodd cyfnodd cyffredig. Yn gwybod i'r meccanidd ac yw'r cyfeidliad ar gyfer y cyfnodd cyfnodd C02 ar gyfer El Nino. For this work we've worked with lots of local partners and students and technicians we work in places for arranging from the top left for the slopes of the Andes and the Amazon to the savannas of Brazil, to the temperate rainforest of Chile, the Congo basin and Borneo. At each of these sites we have researchers spending one week every month tracking in detail the carbon cycle of these forests. We look at the microbial activity in the soil. The activity of the plants. The rate of tree growth and the flow of CO2 a we also collect local weather data and try and correlate variations in the carbon cycle with variations in the weather. And then we can take global satellite based weather data and extrapolate our observations to planetary scale and come up with this sort of simulation of the sources and sinks of carbon in the tropical biosphere. So when areas are red they're emitting CO2 to the atmosphere, when they're green they're absorbing CO2. And month by month you can see variation as the weather changes at a local scale, but for the first time we're able to see this source and sink of carbon in the tropical biosphere at scale. And when we integrate over the time of the El Nino we can see that in red are the hotspots where CO2 is belching out to the atmosphere during these events. And we see the northern and eastern Amazon is a particular hotspot, but there are also smaller hotspots in the Congo Basin and in Borneo. So what are the mechanisms that are driving these hotspots? One key aspect seems to be the soil, the soil microbial activity. When it gets warmer the microbes are more active, more carbon is being metabolised and released from the soil. This is probably not a tipping point as temperatures warm microbes tend to adapt in their behaviour and activity. So this is interesting into annual variability, but this part of the story probably isn't a dangerous early warning of a tipping point. So how well are we doing when we take our observations and try and predict this global rate of rise of CO2, which you see in the black line there. We see our observations, we're capturing a lot of the variability, not everything. Broadly we are able to explain a fair bit of that CO2, but the last two peaks we are failing to explain. There's more CO2 going out than we can explain by directly our microbial observations. What's going on there? Well this is what we saw in Brazil during this El Nino. Fires were leaking out of farms into these temporarily flammable forests and burning the litter layer. These are tiny fires, you can kick them out, they're just litter soils, but they seem to affect the forest, they destroy the root mat and the microbes in the soil and that seems to cause tree death years later. This is drone footage that I took last month, flying over pristine Amazonian forest near Santarem in Brazil and then flying over adjacent forests that was primary rainforest where these fires had gone through and 60% of the trees are dead in this landscape. Also the forest is now more open, much more vulnerable for the next fire to come through and burn them further. We can map these fire scars, here they're mapped around the city of Santarem in Brazil and the total area burnt by these fires was larger than the total area deforested in the Brazilian Amazon in that year. So we're seeing this coupling between climate change and fire is now turning into the larger agent of change in the Amazon compared to direct deforestation and so this could be the potential tipping point that we need to act on. One thing though is fire is something that is directly amenable to policy intervention. We can create early warning systems, we can create fire prevention systems on the ground to try and preserve the forest and stop this potential tipping point in the biosphere that would give us much less room to manoeuvre in terms of our two degrees climate change targets. Thank you.