All right, let's get started. So nice to see all these people here, long conference. And I'm so glad to see so many open source contributors and committers and community people who work really hard in making these open source projects a success. We learned a ton about how to enable and engage communities in open source in this conference. And yet I think we have not learned enough about ways to not engage communities in open source. There are people out there that are creating amazing new creative ways of messing with open source communities. Just from a couple of weeks ago, just remove TypeScript and all your downstream dependencies are having trouble depending on the open source project. A more common problem and one that was talked in the keynote yesterday is relicensing. Relicensing is increasingly common and we're not going to talk about the fact that companies are absolutely free to do whatever they want with their open source software. They can totally relicense it under a non-open source license. It's their prerogative. They created something and they can own it. But it can actually happen to you. And so when that happens, you are in a business that relies on open source software and the software is no longer open source. You have real money riding on this. Your business depends on it.  So what do you do?  Do you tell all your customers, sorry, we will not have any more updates for the software? Bye, please don't use our service. You can't. Do you fork it and continue maintaining the open source project that was there? We did it. We had a business inside of AWS that depended on a fairly large open source project. The project changed its license and then we forked it. So I'm gonna tell you about the story. My name is Daniel Dubrovkin. I go by DB. I work for AWS. I've been working on the open search fork for two and a half years and it's a huge endeavor. Driving a project of that size is a lot of work. It's a big investment. It's not something to take lightly. We had to figure out how to do it in a hurry. So let's talk about that. You don't have to fork an open source project into open source. You can actually fork it in closed source and there were plenty of reasons for AWS to take the open source project, the elastic search and fork it into closed source. I'll explain why we did not and why we continued, why we forked into open source. Once you forked, you have to get stable and healthy to be able to accept contributions from other people and I'll give you some details about how we did that. Finally, Log4j was an amazing security vulnerability that affected everyone, all hands on deck, across the board and it has been amazing for open search. And I'll tell you why you should have your own security vulnerability that will affect your product and your customers. And finally, we'll ask ourselves important questions around next steps and the steps we did not take early in the project, in the evolution of the fork, notably things around topics like governance. So let's go back two years. AWS runs a managed service called Managed Elastic Search and there is the open source software called Elastic Search that is an Apache V2 licensed product. There's a number of components, some of which are essential such as security, such as nearest neighbor search, anomaly detection, observability, these are plugins. And these plugins exist in two versions. There is the open source version and there is the not open source version. And if you go to Elastic Cloud, it runs the proprietary non open source versions of that software. So the engine is open source, but then there's a whole ecosystem a zoo of plugins on top of that. The open source package is called open distro for Elastic Search. It's actually maintained by some AWS people and then AWS built a managed service on top of it. So if you think of the software that's open source, we call it the data plane and the software that controls that, it's a control plane. So what does the control plane do? Well, it orchestrates massive clusters of open search, Elastic Search at the time. It makes sure that those stand up, that you can get an instance when you need to, it does upgrades for you. It has a variety of features. You can just go and click a few buttons and it works. So the control plane is actually quite complicated. The reason why many customers like AWS is because you get all that service. You don't have to hire people to manage your infrastructure. And so the tremendous amount of work was done on the control plane, but the core engine itself all the way down to close to the metal is an open source product. So for AWS, it actually made a lot of sense to fork into closed source. Here's why. We have customers who run very old versions of Elastic Search and now open search all the way back to versions like five. I think it's like 50 years old now, something like that. So as a customer, I run an old version of the software and if I'm super happy with it, the only thing I care about is that security gets patched and that performance doesn't degrade. I actually don't want to upgrade. It's very costly to upgrade. So AWS runs very old versions of the software and every time there's security vulnerability, it actually backports the security vulnerability to many, many old versions of the software and deploys them in production. You don't even notice. Now the upstream open source project does not take patches all the way back. Nobody's maintaining those versions of the software. So internally inside of the Git inside of Amazon, there's actually a tremendous amount of the security patches, sometimes even performance fixes that don't affect functionality that backported all the way to many old versions. So that's a lot of work and it would be amazing to get rid of this open source upstream and just do it in a private fork. It would save tremendous amount of time and tons of money would be so much easier. But we didn't fork into closed source. We didn't just go and continue a competitive product that was closed source. And here's why, we just asked customers of the service what would you like to do? And the more we talk to customers, the more we realize that customers like the freedom of open source software. Many of them want to be able to run it on their own laptops, want to be able to deploy it in their own infrastructure. On-prem, they would like to be able to customize the software. It's better for security because open source software is more transparent and things like vulnerabilities are more visible.  There's plenty of companies with developer hands and many times the companies want to at least customize the software to their liking. They want to assemble their own distributions with just the plugins they care about. Sometimes they want to modify the software in ways that works in their organizations. And sometimes they even want to contribute upstream and develop features and then bring them back to the upstream open source project. And all these are great things of open source. And so more and more we see customers, users, people like you, get the open source software, decide to use it and then only afterwards figure out how they're going to run it. And there are many options to run the software. You can hire people and manage it on-prem. You can run in a variety of clouds. You can get open search from a variety of cloud providers including AWS. You can use companies like Ivan or LogZ for very specialized workloads, login analytics or things like that where the real specialists of that particular configuration of the software. So you have a lot of options. So customers prefer to use open source software for all the good reasons for using open source software and then they choose where to run it. And of course, I work for a large organization that hopes we're the best place to run that software and we will continue doing our best to be the best place to run that software. But people want an open source elastic search. They want an open source open search. So, but open source and Amazon, the intersection between those two concepts usually is not that, at least in the people's minds, is not the thing that comes in your brain when they say open source and Amazon. Usually those things don't really go together, it seems. Many have criticized Amazon for not bringing the contributing upstream. And of course, we can do better. But the truth is that Amazon has been doing open source for a very long time. Do you know that OSPO at AWS existed since 2007? And this morning I counted in our system 28 contributors to Lucene, some of which contribute pretty major features. And Lucene is the foundation of open search. And my own experience of four and a half years at AWS has been quite great. There's really no barriers for contribution to open source. You go into an open source project and let's say you want to do a bug fix or add a small feature and you can go read a handbook of contributing to open source on some internal website. And it says, well, if the license is one of these permitted licenses like MIT, Apache V2 and so on and so forth, and it's a small feature or an improvement, just please go contribute. And here's how you should set up your GitHub and here's how you should connect to it. Here's maybe you need to register that you have a GitHub account, things like that. It's super easy. And then even for bigger contributions that are not super easy at all, it is quite easy. If I want to take some core IP that is competitive and super interesting, I have, I'm supported by a team, I can go file a ticket, I have an IP review with people who care about both open source and competitive advantage of the company and the business for which I work. And we can have an honest discussion about whether this is the right thing to open source, not open source, and so many developers at Amazon do this today all day long. So it's not just small things, it's also big things. It's really quite simple.  And when you fork, you need to have people who are going to do this work. So we hire an open source champion, somebody who has actually been at Amazon for a very, a low number of years, I think he's been by that time 12 years at Amazon or even maybe more. And we give them, we give this open source leader, this guy, dozens of people. We allocate these people, and then we consult some design experts because what's a hard problem in software? No naming, of course. So we ask everyone and we come up the most creative name possible for this new search engine. We call it open search, drumroll. People were waiting on the name for like three months and this is what we came up with. It's great, it's pretty straightforward. Open source search. We actually have two products, there's open search and there's open search dashboards, which is the fork of Kibana. So once you have a name, what do you do next? We create an internal Wiki, of course. All right, I hope I don't get booed when I say that we create a GitHub organization. So we create open search dash project, a GitHub org, and then no booze, thanks, Dave, great. So we started figuring out, as soon as we created the GitHub org, we started figuring out the minimum list of problems we need to solve if we didn't add any features. Just bring the project to a state where an external contributor or any contributor for that matter could come and just bring code to open search and somebody would review the code, merge it and things like that. So we said what is the absolute minimum even if we didn't add any features. And there were two kinds of things that we had to do right after the fork, some of which were organizational and some of which were technical. Let's talk about the non-technical stuff first. First, when you fork a project of any size, you got to call a lawyer. And this is a very difficult thing to do for an engineer that the first person I call is a lawyer, but you will have so many legal decisions to make. One of these important decisions is trademark. So Amazon chose to own the trademark and as soon as you say you own the trademark, you have the legal obligation to police the trademark, you have to control it, you have to protect it in the legal sense. So we, from first principles, we wanted the most permissible trademark. Imagine you're building a competitive service to AWS powered by open search and then AWS comes up to you and says, no, you could not build a competitive service. Well, it defeats the whole purpose of open source. We don't want that. So we created the most permissible trademark that ensures the longevity of the project so that we can have absolutely many competitive businesses to us. And then we, at the same time, reserved the right to go after bad actors that might be disingenuous about it. So we really tried to make it super simple, most permissible possible and not be dumb about it. That's a pretty simple TLDR on trademark. It's up there. You can go read it. From the organizational point of view, we have to figure out how we're going to be organized and function. And we had a lot of people who came right after the fork and had very strong opinions about what open search should be. Should it be donated to a foundation? Should it be a self-organizing committee? What should be a contributor ladder? A lot of people started voicing the very strong opinions about what things needed to be.  We needed to get the project in a healthy state for contributors to come so we can ensure long-term development of this open source fork so that we can continue taking patches, security patches and things like that into our managed service. We were operating a business on top of it. We were building the open source infrastructure, but at the same time we did not want to ask, to be in a rush of answering things like governance. So we just said, is that the minimum? We said this is not the minimum and so we did not deal with those questions. Doesn't mean we didn't want to do them, but we said, we'll deal with those later. So for now, we're trying to do the fork, copy the code and get running fast. And while we're doing this, the amount of people that are added to the project as more especially senior people with business sense, they keep coming and they keep asking, why are you doing this? So you have to remind everyone again and again and again, what is the purpose of forking into open source? It is always considered in large companies as a risk, as a cost, as something you don't have to do. But we have to remind everyone that our goal is to create something sustainable, long-term for our customers, something where we can innovate in the very long run. It is absolutely true that once open source software has gained enough momentum, has taken market share, it is almost impossible to displace. It becomes the best software out there. It's very difficult to compete with a successful open source project. And so that's the kind of project we wanted in order for us to also continue building a business on top of it in the long-term. We want to innovate in the long-term and so we had to continue reminding people about that. Yes, it's going to cost a lot of money, but it's important for us in the long-term, take a long-term view of this. And then we needed to divide the land of all the things. So open search is two engines, dozens of plugins, lots and lots of things. So we said we need some infrastructure to support our operation, be able to do releases. We need teams for core engines at the very least. We have teams for plugins. And this actually existed before in the open distro for elastic search times. We had teams that were specializing in writing the K&N plugin or the anomaly detection plugin. And every one of these teams has an engineering manager with whom the puck stops. So why do we have that? That's a very Amazon thing, that's a very AWS thing. When we have a security problem or when we have something where we need to call the person in charge, there's a very clear escalation path. And this is why you can be safe in AWS's hands. We care about security and we have an escalation path to go upstream. And so we use that experience to say, let's have an owner for every one of these components. This is the person who will do the work with their two pizza team. It's a small team that you can feed with two pizzas. And then they have their destiny. They own their components from the beginning to the end. So we actually assigned an engineering manager to everything that we have out there and had an escalation path. OpenSearchCore was at the time 1.1 million lines of Java code according to CLock. So we're talking something like five million lines of code across all the repos, across 35 plus repos. So this is not a small thing by any means. And we POC'd every type of rename. We built some standards around conventions for the fork of how it's going to work. We made decisions about what is going to go in the distribution. We multiplied this across 35 teams and then we went and executed the fork. And finally, once we get the source code, we went and we did a thorough security review of the code. We did a thorough IP review of the code to make sure that nothing that was not open source because the code base had mixed code in it. We made sure that no non open source software and made it so we can have a clean slate from which to go forward. We set up obvious things that you do in an open source project like CICD. And then finally, we made the repos public. We had to figure out how to do common things. So the way of doing it here, I really appreciate the decisions that were made there. We have a .github repo in the organization that has all the common stuff. That's where you'll find a code of conduct that gets copied in all the repos. That's the repo that you inherit when a new public repo gets created. It has things like a friendly contributing document that says, here's how you would contribute in general to the project. And then every repo will modify it and tailor it to the needs. It has things like security so that you can trust that every part of the project has a security escalation path, and so on and so forth. Of course, it has the license, which is very important as an open source project.  For things that are common across some repos, for example, we have 2,000 plugins, and we have a bunch of clients. There's a client for every language. We have a repo called Open Search Clients, or Open Search Plugins. And in that repo, you'll find developer guides for all clients. And we're trying to level up the quality of all the clients across the Go client, the Python client, the JavaScript client, and so on and so forth. Hopefully, somebody will write an Elixir client, contribute it, and will be up to standard of all the clients. We work on projects like code generation across them so that all clients can have support for all APIs. So you'll find developer guides that are specific to themes in these theme repos. And you'll find some tools. We use a tool called Meta to affect multiple repos. Like let's say I need to update code of conduct everywhere. We never had to do that. But let's say I needed to. I could run a Meta tool, and then it would update all the repos at once. So it's super convenient. So we created all these common concerns and created repos for them. So everything went into markdown. And we worked completely in public for those. There are support systems with so many teams with only hundreds of developers just at Amazon. And you need common practices and common infrastructure. For example, how are you going to do branch protection? Should we protect main or should we not? Should we have a pull request that gets merged with a rebase? Or should we have it with squash? Should we have DCO, which is the minimum? I say that this is Apache V2 license. I'm authorized to contribute to this project. Or should we have something else? So all these common things needed to be set up. Open search documentation did not come with the fork. That was a trademark copyright that I'm sure what the exact terms are. But we had to start documentation from scratch for this 10-year-old product. And a lot of people are saying that documentation could be better, yes. And we've had to write it from scratch. We have to host releases and patches, create forums, websites, opensearch.org. All these things, every one of them requires someone to work on it, figure out how to do it, then publicize how it's done, and then iterate, iterate, iterate. Every single one of these things we found as we went and built. So we announced the fork in February. We went public with some repos in April. And we were able to release six months later, so five months later. So it took five months, hundreds of developers to do this operation, repo by repo, copy, rename, set up, all that stuff, do the distribution. So we learned one very important thing. Releasing small stuff is super easy. But releasing not small stuff is extremely hard. Not only had to figure out how to release this big distribution and wrote a tool that assembles a big distribution, but in the middle of it all, we got hit by Log4j. And Log4j was a massive event for a lot of people out there. And just think about, just AWS, forget about the open source project for a second. Inside of AWS, we are running millions of instances, EC2 instances, millions of instances of software that lives on top of it. And just about all of this is affected by Log4j in a big way. So it was all hands on deck. And every single service, every single component, everything had to fix Log4j, see if it's affected and so on and so forth and patch. Because we invested in automation early in open search, it was a breeze for the open search project. We updated Log4j libraries, and then we pressed some buttons and we released three full versions, three patched versions of the software after running all integration tests in something like a week. Every time there was a new vulnerability found on top of Log4j, we're able to release it. AWS also released a live patching tool where you could take an instance of a Java process and without shutting it down, patch a Log4j vulnerability in production in your running code, which is something that has been used across the world. We used it inside of AWS as well. So it's only one basic lesson. You just have to automate yourself out of the job right away when you fork something. You cannot be doing things by hand. It's insane. The first release took us something like two months to do by hand, and then we just understood that it's not going on scale. We automated everything. And so today, you too can go and check out OpenSearch code and build it from the top, all its components, and do a distribution. And in fact, the free BSD distribution is something that no Amazonian is involved in. It's done by a completely different group of people. I don't know even who they are and thank them. So a release of the product takes a village. We've automated. Every time a version is incremented in a main repo, we have automated pull requests that increment versions across all the dependent components. Then we also have GitHub issues that are being filed and that have a checklist, which is actually a template file sitting in the repo that humans need to go and check. Like, okay, are you ready?  And it has dates and has all that. That entire process on GitHub is done automatically, very proud of all the bits and pieces that went into there. And so one single release manager can observe that this is going well and can effectively do the work. And you can join the releases in public. There are public zooms of these. And you can see this process going on. It's mostly supported by GitHub. You don't have to join a meeting. You can follow it on GitHub as well. It takes a lot of components to come together at the same time. It's quite an impressive thing. For security, the topic keeps coming back, especially with Lock4J, which is a security vulnerability. We were very lucky to be able to leverage AWS in the beginning. And so AWS security and organization that is dedicated to the security of our customers has said from the beginning, okay, we don't know how to do this open source thing, but we know how to do security escalation. And so if there is anybody who suspects there is security problem, we'll help you. And so they were our response. You could email AWS security and they would have a process and respond to everything escalated within our organization as needed. So we piggybacked it and we didn't have to deal with it for a while. But this is something you will, if you fork you will have to deal with very, very early. You need to staff and document ways to respond to security. And I'm happy to say today this is actually a community process now. There is a separate escalation path of maintainers that don't work for all for Amazon. And when you report a security vulnerability to open search, it gets dealt with like any open source, any healthy open source projects. There's actually an independent report that was published two days ago that is an audit of open search processes and code. Very happy to see that it only found two minor vulnerabilities and generally commented that the source code and the state of automation and affairs is in a healthy state in open search. It's work that a lot of people have been doing for the last two years. Then you can go download and read this report. Security remains our number one priority and very proud of what we've accomplished. So now what? You've set up the project. You can report security vulnerabilities. You can, you have some community engagement. So you can just accept the contributions. Well, contributions might come, but most likely they will not. The truth is it takes a while for people to decide to go from I'm interested in the project to I actually have a business need to contribute to the project. So one of the big mistakes companies do is that they just don't staff up. We could have prepared the project, just did the dev rel part of it, the community, the engagement. Like here we are ready for contributions, but contributions would not have just come out of nowhere. So we seeded the community.  So we're going to pay people to work on our business problems in this open source product. And we are hoping that others will come and engage with us. We also spent a lot of time, money and effort on using the same people to actually support those newcomers from the outside. So one of the things that happened that I was really pleasantly surprised is that many did not wait for governance decisions to come and contribute. Many folks did not stop at the limitations that were seeded at the fork. We weren't perfect by any means. They just started writing code. And so engineers from companies like Ivan came and started building. And you know what? They started building more. And they have a business that relies on the software and it's exactly the spirit of open source. If you have a business need, come and work on it. And we will help you be an owner of that project along with us and hopefully we can be the same. So people started noticing that the project is moving, releasing, things are happening, started contributing. They started opening pull requests. And so as soon as we saw real engagement from real engineers who are bringing value to the project, we immediately wanted to promote them to maintainers of the repos. So we had to figure out how maintainers would organize and so we let go of the maintainer process completely. And every decision we made in opening up more, we always consulted the community. We always did it on GitHub and it's true. We reserved the right for the final decision as existing maintainers of the project. And maybe we didn't have some of the elements of spelling out how we did it, but we consulted maintainers and we wrote it down in those markdown files. And so today, maintainers self-organize. And in order to become a maintainer in an open search project, it depends on existing maintainers. Some have contributor ladders. They say you must contribute three lines of code in order to be a maintainer. And others say it's just one person or two. So you could be a maintainer if you're just interested in maintaining. Or in open search core, you have to be a distributed system specialist. Have contributed a very complicated system to be part of that project. And maintainers are now groups of people and self-organized in public. You can read about it. It's a GitHub maintainer. So if you have a question about how open search project functions, just go and you'll find it there. So we started also taking some of the internal Amazon innovations and we started open sourcing them. We have a lot of experience running Elastic Search and Production for very, very large workloads. So we started funding the work of taking these innovations and open sourcing them around things like storage, segment replication. There's some really complicated stuff that has been written inside of AWS that never had a chance to make it upstream. And our goal is to have zero patches inside of AWS for the software. We want the data plane of the software to be 100% the same as the open source product. We just want to take it from upstream. And then large companies came and helped us with some of the complicated things. Intel contributed a compression codec that has a 15% throughput improvement. And I took them a year to bring it into the code base. But I think the result is quite impressive. So we're trying to form more partnerships. If your business has business needs and wants to contribute to the code base, we are there to help. We absolutely want you to have real skin in this project. Please come and we will help you contribute. So what's next? Once the infrastructure became stable and we could release, we saw contributors contribute. Great. Major features are being built. Now what? I think at some point soon, we're going to have to talk about governance. And we hope that there is some real partners that are willing to put some dollars and some people into this project and we can discuss what we do with governance. We do not intend to make this project an Amazon open source project by any means. We would like it to be a true community open search. We really care about that. So we are ready to start having these conversations. And so if you have opinions, start writing. Go to GitHub forums, slacks and so on and so forth. Should you invest in a fork? Let's see. You will make promises and you will make mistakes. It took us almost a year and a half to get a public slack. That is super embarrassing. I can't believe it took us so long to get something like that out there. Software is millions of lines of code and so forking will be hard. If you are in a large corporation like Amazon, 90% of your developers have never contributed to open source, they have no idea how to do it. You're going to have to educate them. You will absolutely need help from your Ospo, your lawyers to get any of this off the ground and contributors are just not going to come if you snap your fingers. You're gonna have to do hard work to do that. Stewardship of a project like this, 106 repos today, is a full-time engineering job. You need actual engineers engaging in source code all the time out there on GitHub in forums, continuously all day long. So let's see, how are we doing? I borrowed the title for this talk from a user who came and just opened the GitHub issue and titled it, fork it all if you fork it. And the issue was a little confusing after digging through what the user was trying to say. We helped them with their problem and I'm happy to report that a year after that issue, this person actually went and fixed a bunch of bugs in open search. That's amazing. Someone who was really frustrated from the very early days of open search became a contributor of the project. So fast forward and onward. We went from 73 repo, we've created 73 new repos in open search project. This ain't small. There are over 200 maintainers, tens of thousands of merged pull requests, issues closed, millions of lines of code that have been added to the project. So I'm not even counting the millions of lines of code that were deleted. We did over 100 releases of open search tools, clients, you know, all these things with many, many, many millions of downloads and lots of happy users. So I think it's a success. The measure of success that I use is the number of contributors. I've counted over 1000 contributors to open search and this is a live view of what open search is today. And about half of those contributors do not come from Amazon. These are non-Amazon contributors and this is a very proud moment and it's amazing to see that the community is actually engaging in the project and so many have written code or not code in this project. I also want to finish and acknowledge that the future is AI-driven and all those 1200 contributors are not going to be contributed for much longer and that AI is going to take over and we already see it. In open search, this work is also included the work of at least six bots. So please give a round of applause to the Panda Bot, to Jenkins CI, GCO Bot, Mend, GitHub Actions. These are important participants in our project as well. Thank you. I don't know if we have time for questions. I'm happy to answer some from the audience. There's any. Go ahead in the back. Your takeaways, are they the same if you do not have the financial power of Amazon? You know, the fact that you can hire engineers like, I won't say like that, but you have an attractiveness.  So is your question always special? Is it just because Amazon is a large company? Yes, the fact that you succeed, is it linked to your financial power and attractiveness? Oh, great question. So the question is, is the fact that we are succeeding linked to our financial power and the ability to hire a lot of people? I'd say that, I'd say the answer, someone must pay people to do the work. I don't think we can get away from the idea. I never believe that open source is, that people do open source work exclusively for the greater good of humanity. Now I've contributed plenty of open source projects, which were not part of my job, but I've also contributed to many projects that are part of my job. So I don't think of open source as just a hobby. I want to work for a business that where open source is part of the code that I write. So for me, I think open source is cheaper. It is better, better quality, cheaper to develop. It makes complete business sense. It is just, for me, it's the difference between open source and open source. It's kind of like Java versus Go. These are choices we make. And if you want to have a sustainable business, building it on top of open source I think is a wonderful thing. So Amazon was able to fund development of this project, but it didn't have to be open source. It could have been closed source just as well. Someone will have to fund your fork. And I don't think just community engagement is enough. So if you depend on an open source project and it is much bigger than you, you must find friends, other companies that will be able to put real money into it. And so to finish the answer to your question, I ask other companies, would you contribute to open search? And I get two kinds of answers. I'm already contributing or I get, if I had a business need I would contribute. I rarely get other answers. I think in the end it's what makes sense for your business. Thank you. Can you talk a little bit about converting a large set of engineers who have never done open source over to doing an open, I mean like internal Jira and just talking to the guy next to you and all that. How did you change the culture? How do you change the culture of, especially in a large company, how do you change the culture so that developers who've never done open source contribute to open source? I think, first there are many motivations for a non open source engineer to contribute to open source. I worked for large and small companies and I worked for Microsoft and then I left Microsoft and I went to another company which had the exact same problem as I had inside of Microsoft and I had to reinvent the wheel again. And once you've done that a few times you never want to go and get the third job where you do the same thing again, you want to learn. So this learning, there's a lot of desire in the company to learn and do open source because this is the work you show. There's many good reasons to become an open source developer. In a company like Amazon, I think the key is educate and support and spell it out. So Ospo inside of AWS does a fantastic job being transparent available and being pragmatic about what's possible and what's not possible within a large company. And then you need, the leadership needs to understand why we're doing that. And it's never for the greater good of humanity. I think it's for the business. And the more you say it's for our business, it makes sense to our customers, I think the better it is. So you have to explain why you're doing this, create some kind of vision of why it's important and then educate and support people who are there. So I take engineers who've never contributed and I help them make their first contribution and then I tell them it's okay, it's going to be great and I'm going to be patient with you. I'll be the reviewer of your code if you need me to, if you have a problem, come talk to me, we can do it in private. I can help you if you don't understand something, there are no dumb questions. All the good stuff of any collaborative engineering team. I don't think open source is anything particularly different actually, except that you work in public and so you can be seen. It can be difficult for many people. There's another question right there, just pass the mic if you don't mind. Thank you. Even now that the open search project is a success, it's a successful project, did you still get the internal question of why are we doing this and why are we not building in private? Even though, so the question is, even though open search is successful, do we still get the question of why we're doing it? Well, first important thing to say about Amazon is that Amazon always asks questions. In fact, my job inside of AWS is to be a contrarian. When somebody says, I'd like to do X, my first question is what are the reasons to do X and then what are the reasons not to do X? I'd like to compare the two and then we pick the right option and that culture is very healthy because you can change your mind. You can have something that you've been doing and then if you think it's a mistake then you should absolutely be able to change your mind and just not do it afterwards. So yes, there's always people who ask why are you doing this but they don't ask it because they have a preconceived notion that it is bad, that we should not be doing it. They are asking because they are curious and smart people and they just want to understand something they don't understand. And so yes, you have to be prepared for answering the questions like, should we stop doing it? Now the project will continue existing it's an open source project but of course if we stop doing it it would have a negative impact and the first people it would have a negative impact on is our customers. So of course we're not going to stop doing it for as long as our customers are asking for it we'll continue doing it. It makes business sense for us. Absolutely. I encourage everyone to have a healthy critical way of working with others where different opinions including ones that seem completely bizarre to you can be voiced and where you can change your mind and make different decisions. Yeah, I love to talk to anyone who thinks that we should fork in private. I enjoy those conversations. I take the person who disagrees with me completely and then by the end of the hour I hope they walk away and they start thinking maybe I'm missing something. I heard good arguments. Like now I'm a, I turn your biggest enemy into the biggest fan. That's the opportunity. I probably don't need to convince people here that open source is a better way of doing things but definitely inside of out there. I have to convince my dad that doing open source is a good thing. He doesn't get it. He's like, we come from a communist country. Like why would we be doing open source and giving it away to the greater good of everyone? It has never worked for us. Anybody else? No, do we have time? I think that's it. Thank you so much. I'll be here. Please feel free to come and ask more questions in person. Thank you.


Chitosan is a natural biopolymer derived from crustaceans and has been used as an antibacterial agent due to its ability to bind to bacteria and fungi. In this study, researchers investigated the antifungal properties of chitosan and its derivatives, trimethylchitosan, TMC, and chitosan nanoparticles against three common fungal pathogens, candida albicans, fusarium solonii, and aspergillus nausea. They found that chitosan nanoparticles had greater antifungal activity than the solution form of chitosan against all three species. Furthermore, they observed that the antifungal activity of chitosan nanoparticles was dependent on their particle size and zeta potential. Additionally, they found that TMC did not have any antifungal activity against these pathogenic fungi. Overall, this study suggests that chitosan nanoparticles may be a promising alternative to synthetic antimicrobial agents. This article was authored by Lin Yaning, Norazia Mohamedzin, Teef Sawa, and others. We are article.tv, links in the description below.


Hello, and welcome back to the craft box. My name is Brenton today We're an episode 62 of the wizard 101 death walkthrough last episode if you haven't checked it out. We went into the Grand chasm and It's past and we managed to get the portal stone and we're about to talk to leslote and deliver said portal stone Good work. You found yourself at portal stone. I hope it wasn't too much trouble Now that you have acquired a portal stone, it must be a tune to you.  Okay Congratulations, you now have a portal stone and can travel to the necropolis as you choose With that portal stone, you can now go through the grand gate and into the ring of battle Proceed up the road to the necropolis Okay This way We're gonna use the teleporter to get there quicker And we're gonna figure out which way it's just over here cool This is the necropolis so we are hitting on into the second ring of Yeah second ring of the three Look at this. So this allows us to get to the drake hatchery the crucible and the labyrinth which is a crazy dungeon But yeah, we are talking to Cyrus Drake and the Basilica to start with which is back here So we now have access to the necropolis, which is fantastic Yeah Lude, thank you Excellent work. You've gained access to the next ring Events are proceeding as planned. I have Interesting news My brother cared deeply for his wife Sylvia Drake so much so that he brought her body with him to Dragon-spire and entombed her within the necropolis You must venture forth to the necropolis and find her remains The path of the hero is not as glamorous as you thought Hmm take this knowledge crystal find her tomb and use the crystal there It will store her spirit within then you must return the crystal to me and I will take the necessary next steps Okay, let us head over to Sylvia's tomb Which Basically Yeah Yep, we defeat Sylvia and she becomes very important later on So yeah, this is another gauntlet another one of dragon-spire's crazy gauntlets With silver at the end and she is life because she used to be the life professor if you didn't know that See her. Let us go and head on up to her. How many floors is there roughly? Oh Not too many 4400 which means usually it's about a hundred of floors. So that's four floors. She'll be on the top one So, yeah, not too many. What are you your death and balance? Just need one of you We want to get a couple vampires Three vampires two blades no faints needed And we'll just make that treasure cards and yeah, that should be good Let us do this blade Bu bu bu bu bu bu bu bu bu bu bu bu bu bu bu bu bu bu buaam Okay, um, we will hopefully be able to put on a How much are nine fifty? Okay? Well? We found out that with double blade We can kill with a vampire and we will Definitely be able to kill. We won't need to heal.  I don't know. I was too slow there. That was a slight bug Okay Let's do this Evil snowman what no, please no Oh Here we go, so it's very not too bad and hit no fizzle. No fizzle No fizzle. Yeah, that's good Please kill kill Yep, that's a kill da da da da da da da da Dragon spy music is actually really good, um yeah really really good okay we'll do this and probably won't kill but we will use a poison on him so he probably will be killed 600 that's pretty good that's only meant to do like 650 and that did 663 so that's pretty good or 662 one of the two so I'm not too worried about that actually we'll want her and then more poison and he should be dead okay that's right that's not too bad not a worry 91 okay oh no fuzzle yay and hopefully in a couple rounds he should be dead how much is that 99 whoa he's nearly dead uh let's see because he didn't have yeah 93 he's dead bye yay nickel that's pretty good next level down more okay both death that's annoying nope I didn't want that now stop please weird okay let's do this wow double weakness okay that's cool well I hope you guys are ready to die because they're dying they are dead soon just because they put double weakness on me doesn't mean I'm not gonna win haha okay do that and know the bleed we are actually kind of long health for some reason kind of shopping low on health you guys what are we gonna do we can break so we want to do that we can and we will probably be able to destroy but to get most health we're gonna do that just to get her out because she's got a lot of health she's got more health than the other ones so we'll get her out first also she has no purpose but she's probably gonna use yeah you're gonna use online of course we go half out from just under there we go that did a lot that did it all there we go nearly full health perfect and we will probably try for a and we'll probably go for I don't know a vampire maybe I'll use one of my one it's like I think I did I just got all of them maybe I did so I just got all my want it's okay please no discard one hits all of sent in the structure is fantastic okay we didn't watch is good we can get off that weakness and then we will just play we can just just hit it okay boost on life yay one thousand one hundred and two what a perfect number one yay nearly full health which is good no no copper and nope okay what's on this floor nothing important so I'll be back in just a sec okay I am back yeah Sylvia Drake's trying to talk okay um so never gonna get her to betray his her beloved husband that's surely a thing we'll do some of that we don't need it yeah we do we will do this did it up yep let's go okay let's see how hard this is gonna be to I put feints in I didn't put feints in well that was smart of me Brent you are a fantastic human Brent look at that you're so smart I am so smart up well you know what that's fine we will go without feints we're gonna be professional anti-fainters if that's it that's not a thing yeah it's not a thing we are gonna discard one of you did it uh did it uh this won't kill probably not but you never know no blades just a prism vampire let's see she's got like 1,000 health yep nope didn't kill unlucky well well that's fine we will try again soon okay oh we did put feints in whoa I'm smart ha didn't know that one burn 95 okay then what's this display okay then oh I was about to say you're never gonna use a diff diff thing but apparently apparently she does it's gonna do a bit yep 295 that they're quite a bit feel like what to purpose whoop okay okay then do do do do let's just pass why not hmm why not man go okay think you're good at gaining health back that's cool 79 that's much of bad as long as you don't heal good don't know the dirt don't know the dirt okay well that will kill that'll kill ya died I died I died I died I died I died I died I did oh you're dead did did did did did did did did okay I was like like just panicking for a second because I didn't hear her like die and like I was actually what worried okay let's double blade and poison or single blade poison depends on what we get probably hopefully double blade I would also love to get this weakness off as well but I mean poison be fine for that and it looks like we're gonna have to use poison for that we will double blade just for laws don't don't don't don't don't don't don't don't don't don't yeah and then we're right hopefully faint and right yeah we're gonna just cut the heel where you should need to heal we're gonna enchant you gonna put up another one of actually we're just gonna pass just gonna pass just to get this lemon poison on and then we will get in for the wraith yeah sounds like a good idea and shards of poison good no fizzle no fizzle yay boop boop boop boop first it's gonna do nothing seven that actually did quite a lot considering four hundred and twenty three okay surprisingly that's doing a decent amount each time do we have a we do have one that is perfect you can get that off and we will blade and then we will faint and then we will hit with a wraith hopefully we will have pips by then 400 that's quite a lot she only has three thousand so yeah maybe I should have just cut it my heel oh well it's fine it's fine half health and she's gonna do a death shield oh look at that what a surprise ha ha well that caused for another poison just as well we can haha yay thank you for not discarding that poison Brent you're a fantastic human Dun-A-Duh Dun-A-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh-Duh Boop Boop, 68, okay I just don't know this Okay, stop weaknessing me, it's weird Weakness spam is bad uhhh, we oh yeah we have another blade we will do this take it off that Lemon Lemon weakness Get some damage on it Boop, 71 50 cyclops, yeah, yeah, yeah, boob, boob, 207, okay, and 400, wow, it's dead, but you know what, we're just gonna put a faint on just to make sure, just in case, in case it, I don't know what it can do, but just in case, look at this, there we go, 700, then definitely, yay, you capture Sylvia's spirit within the knowledge crystal, as you trap her spirit, a strange badge falls to the ground, her wraith-like form takes on solidity and color, soon Sylvia Drake appears as she did while alive, okay, let us head back to the Basilica and talk to Cyrus, and I think it'll kind of be the end of the episode, nearly. Now the ring facility should function normally for you, I've discovered something more significant about Dragon Spire, within the innermost ring is an academy, and only students of the Dragon Spire Academy may enter that ring, go now to the Necropolis and see if you can discover a means of becoming a student of Dragon Spire Academy. Okay, let's do that, and then we'll end off the episode just because might as well get preempted into the next area, yeah, explore the plaza, we've done that, crystal guide, hello, hello guide of crystals. Congratulations for taking the first steps to become a student at Dragon Spire Academy, to begin your trial of admittance to the innermost ring, you should visit the Dragon Master in the hatchery and learn all that you can about Drakes. Okay, so that is all welcome to the academy, so yeah, next episode we will head on into the Drake hatchery, it gets some drakes which are basically dragons, which is cool, so yeah, we'll head on in there. So yeah, thank you for watching, remember to leave a like and subscribe, and if you've already subscribed, press the little bell down below so you know exactly when I post another video. And remember, craft, outside the box.


The latest weapons, coupled with the fighting skill of the American soldier, stands ready on the alert all over the world to defend this country. You, the American people, against aggression. This is the Big Picture, an official television report to the nation from the United States Army. Now to show you part of the Big Picture, here is Sergeant Stuart Queen. It can truly be said that today the sun never sets on the American soldier. For over the wide stretches of the world, somewhere, at some time, day and night, he is performing his duty to this country. For example, it is now 345. In military language, that's 1545 hours. Let's visit some of the military installations here in the United States and elsewhere in the world and see what the men and women of your army are doing at the precise moment of 1545. At this very moment, at 1545, a practice warning alert is being sounded somewhere in Long Island, New York. And the men of Battery C, 505th Anti-Aircraft Artillery Battalion, one of the many links in the steel ring of America's defense, go into action, as though this were the real thing. Training and preparing themselves for any eventuality that might occur, for any intruder who might erupt from the skies. Although these men are stationed in the peaceful United States, they are on combat status day and night, seven days a week. For their mission is one that vitally concerns all America, protection against destruction from the sky. Yes, theirs is a long vigil, but a necessary one. At 1545, too, at Fort Monmouth, New Jersey, men of the Signal Corps, the eyes and ears of the army, are learning the rudiments of split-second electronic warning devices and of high-speed communications. For modern global warfare requires a worldwide communication system which must outspeed the fastest plane and out-distance the supersonic rocket. At the same time, in the Pentagon in Washington, fully-trained Signal Corps personnel are operating the complex mechanisms which link Washington with the Far East, with Europe, and with other outposts of our far-flung bastions of defense. It's 1545 at Fort Belvoir, Virginia, too, home of the Corps of Engineers, where army recruits are being trained in a multitude of combat and technical skills, which contribute to the engineer's bag of traits. Here, for example, a demonstration is being conducted on how to lay a hasty type bridge across a ditch, or tank trap to permit the continuous and uninterrupted movement of armor and other heavy vehicles. While here, a small class of trainees is learning the basic principles of repair, maintenance, and the operation of one of the many types of engineer earth-moving equipment. At this moment, too, men of the 79th Engineer Group are learning how to handle the DeLong Pier, a floating, portable pier that can be towed into position, sink its own piles, and raise itself out of the water to any desired level. This new device can save many days of costly and time-consuming construction in future military operations. Meanwhile, at another part of the post, other trainees are working with carrier pipes, learning how to apply hot bends. Speaking of pipes and hot bends, at exactly 1545 today, this soldier is learning how to work with a different kind of pipe. While the rest of his buddies get off a few licks on a hot bend of their own, and as these musicians of the First Army Band practice for the Evenings Concert at Fort Jay, New York, down in Fort Benning, Georgia, these rangers are practicing the grim business of warfare. American rangers must be proficient in everything and prepared for anything. And everything includes everything from the use of the long knife and the bayonet to judo in hand-to-hand combat. In this kind of fighting, it's your life or your enemy's life and no quarter given. Everything also included survival in the jungle with the possibility of a light snack of Wrigley but life-giving snake meat. It takes a lot of learning and know-how to be able to descend a sheer cliff. This is called rappelling. Even the Ranger mascot is impressed. This one would impress even a Swiss mountaineer. But at this moment, the rangers aren't the only American soldiers who are being developed into the world's toughest fighting man. Close by at 1545, Army paratroopers are being trained in the vertical concept of modern warfare. This maneuver is called slipping. By pulling on his risers or slipping, a parachutist can control his descent. Everybody travels on the double in Fort Benning, Georgia, especially at officer's candidate school where the pace is fast and everything is streamlined. Streamlined right down to the very last hair. A man's got to be more than just a good soldier to graduate from infantry OCS. He's got to be a leader of men. The kind of a man soldiers will trust and believe in. The kind of a man they'll follow into battle. Before graduation, each candidate must prove his leadership qualifications by commanding a group of his classmates in a tactical situation under combat conditions. These future second lieutenants are engaged in a mock assault on an enemy fortified position located on the opposite bank of the Chattahoochee River. Across the nation of Denver and California, tanks and infantrymen are also conducting a mock assault, blasting a simulated enemy fortified position located in the hills. The time, 1545 of course, Pacific time that is. In the American Army, teamwork is the keystone to success and these tank infantry teams really practice at it. They know that this kind of practice teamwork may someday become the real thing. May mean the difference between life and death. In time of war, replacements must be made. Continents must be spanned. Oceans must be crossed. For a never-ending flow of men, equipment and supplies must be kept ever moving into the zones of combat. This is the job of the Army Transportation Corps whose mission is to move the army, its food, ammunition and materiel by every type of conveyance from truck to helicopter. That's why at 1545 this afternoon at Fort Eustis, Virginia, on a training dock located on the James River, men of the Transportation Corps are diligently training to acquire the skills and techniques necessary to accomplish the Corps mission. Learning how to load cargo into the holds of ships is only part of the job. The men also have to know how to stow the thousands of different sized crates of equipment, supplies and other material properly. How to make every inch count. But that isn't all. If a seaport isn't available, they must know how to unload the ships anchored off foreign shores. Offloading cargo into amphibious trucks is no easy job especially if the seas happen to be choppy or rough or if you're being strafed and bombed by enemy aircraft. As soon as the amphibious trucks or ducks as they are called are loaded, they speed quickly for the shore. Here they move up onto the beach to a dump area where the supplies are unloaded and stockpiled. Later to be shipped by rail to the various army depots where American soldiers are stationed. Since the shipment of supplies by rail is a responsibility of the Transportation Corps, many of the men have to learn railroading. Most of their training is accomplished at one of the big railroad yards like the B&O or C&O. Here under the tutelage of old-time railroad men they learn the ABCs of railroading. From the ground up and down to the last detail. A delay caused by a broken coupling could affect the progress of a major battle. But soldiering isn't exclusively a man's job anymore, not in the modern American army. This afternoon at Fort McClellan Alabama the women of the army are also learning the know-how of jobs that will contribute not only to their country's defense but to themselves as well. I was wondering when you get around to us women. For a moment there I was afraid you'd forgotten all about us. Learning how to live primitively in the field is also part of our training program because we wax very often perform a man's job and expect no preferential treatment. Like the troops we eat our chow out of mess kits which can be used for the satisfaction of the outer woman as well as the inner woman. This kind of exercise not only takes off fat it also puts on the kind of muscle we need for the art of self-defense. Remember when they used to call us the weaker sex? Wax must also be prepared to perform many jobs in many lands. If for instance any of us should be assigned to a far northern post we're trained to survive in severe subzero weather. Like these girls who at 1545 Alaska time are roughing it in special maneuvers to test arctic equipment in materiel for wack use. You sure got to give those girls plenty of credit because it can get mighty rugged up here in Alaska. Even for us guys especially me on account of I'm from Texas and all this working and training and maneuvering in 30 degrees below zero weather sure leaves me cold but I'm not complaining no sir because we got a real good compared to the Joe station way up in Tule Greenland. Talk about the rugged life even the Eskimos give these frozen wastelands in Greenland to go by and look at that weather well that's Tule, Tule Greenland at 1545 where you can't even see the nose on your face. I bet those Joe's wish they were stationed down in Schofield Barracks, Hawaii right now living it up with all those pretty gals on Waikiki Beach or maybe watching the sweet Lilani's do the hula if you ask me I kind of wish I was down there myself living it up my foot does this look like Waikiki Beach and what do you think we're doing here digging for clams in the sand? Yes 1545 and in Hawaii the same intense realistic training goes on only the scenery is different but until the Kremlin disarms and wear old pieces and establish fact every American serviceman must continue to receive the kind of training that will enable him to survive in the battles that may come in war some must die so that others may live the men who died on the once bloody island of Okinawa are proof of that today however Okinawa lies peaceful and serene surrounded by the calm waters of the pacific it is a perfect setting for this baptismal ceremony which at 1545 this afternoon is being conducted with holiness and with reverence and of course with the appropriate organ music and as these soldiers receive their baptism in the blue lagoon of Buckner nearby at another part of the island these soldiers are preparing to receive another kind of baptism learning how to hit the beaches the same bloody beaches where thousands of young Americans underwent a baptism of fire in a war that is gone but not forgotten like the war in Korea where at this very moment at 1545 the men of the 159th field artillery battalion are hey that's my outfit setting up some simulated preparatory fire before the inventory moves in you know it wasn't so long ago we were mailing out the real stuff for the commies now it's just an exercise some people may wonder why we keep on training like this the way i look at it is if you're a soldier well you got to be a good soldier the only way to be a good soldier is keep on soldiering what are these guys expecting Korea Marilyn Monroe is Marilyn Monroe yes Marilyn Monroe presented by courtesy of army special services who at 1545 tokyo time have arranged a ball game for the benefit of american gi son and japanese son another of the army's peace offensives not with cannonballs but with baseballs and with footballs like baseball football has captured the imagination of the japanese and it is fast becoming one of their most popular sports being a member of a football team however is no excuse from military training and when the paratroopers of the 187th regimental combat team stationed at camp chikamanga japan go on a practice jump the members of the football team are expected to jump with the rest of the regiment ordinarily the men would make the jump with their respective units and in full field equipment but today just for the novelty of it they're going to jump wearing their football uniforms probably the first time in football history yardage will be gained straight down within a few minutes the men are ready and enter the plane as a team for these men not only play as a team they fight as a team because of japan's proximity to russia and communist china and because she is coveted by the soviet union american troops stationed in japan must constantly be alert and prepared for any sudden move of aggression today at 1545 these americans are carrying the ball and holding the line so that the free world may live in peace the kind of a peace that would allow the world to open wide its doors to all who appreciate the beauty of scenic grandeur and respect the dignity of man like these american soldiers who with proper reverence respect the japanese religious shrines and in true democratic fashion the customs and traditions of the people even to eating such strange foods as sukyaki or kareebayaki or eintenbraten mit kartofoklas in germany we're at this very moment at 1545 democracy is still at work as our troops work closely with their former enemies the german police learning the techniques of riot control at this time too in spandau prison which can find some of germany's most infamous war criminals and is guarded alternately by american, british, french and russian troops an american officer receives command of the prison from the russians this is the only place in the world except for vienna austria where there is even an assemblance of amicable relations between the world powers here in vienna in front of the hapsburg house at 1545 another american officer is taking over this month's military control of the international sector from a stiff and impersonal russian officer those russians shaking hands with everybody and acting so nice and polite may fool some people but we know better that's why we never let ourselves get soft why we mountain troops in solfeld and austria keep ourselves in fighting trim like today it's 1545 and we're taking in some of the mountain sites but who's got time to look at the pretty waterfall especially when you've got to get across a mile high gorge on a shaky rope bridge or maybe only a single rope whoops don't worry folks he's just demonstrating how not to do it beautiful scenery isn't it yeah if you like waterfalls personally i like this kind of scenery better of course there's other nice things to see in paris at 1545 in the afternoon for instance there's the famous eiffel tower then there's the lubra where they've got some nice paintings and statues but me well i still like this but there's something else to be seen when you're in paris soldier something of vital importance to the civilized world it's shape supreme headquarters allied powers europe military headquarters of nato the north atlantic treaty organization an organization which was set up between the united states and 13 other democratic nations to frustrate any aggression by the soviet union or its satellites here at 1545 american servicemen and women are working together with the other free peoples of europe banded together in a common cause an attack on one means defense by all should mankind through our solidarity our prayers for peace and through the mercy of god be spared the catastrophe of another war then this organization will have served a noble purpose it will have demonstrated that an alliance for peace rather than for war is an entirely practical measure that the power generated in an alliance of such magnitude can bring competence not fear to the hearts of men yes all over the world the men and women of your army are alert and ready not only at 1545 but every minute of the day every day of the week every week of the year ever vigilant in the defense of the free world now this is sergeant stewart queen inviting you to be with us again next week for another look at the big picture united states army in action the big picture is a weekly television report to the nation on the activities of the army at home and overseas produced by the signal corps pictorial center presented by the u.s army in cooperation with this station you can be an important part of the big picture you can proudly serve with the best equipped the best trained the best fighting team in the world today the united states army


This is stock number 9J58A. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and use Jeep headquarters today. We are checking out this super clean 2019 Jeep Cherokee limited This vehicle has the 2-liter turbocharged four-cylinder motor which pumps out 270 horsepower From this HD video, you will be able to tell just how clean this Jeep is all the way around inside and out Diamond black is the color we shoot all of our videos in 1080p So if you have HD capabilities on your computer tablet or a smartphone device turn them on right now because it is like you're right Here looking at the vehicle with me and definitely your best way to check out the vehicle without actually being here Driver's front rim painted and polished 18 inch Absolutely perfect. No scuffs or scrapes on that has continental pro contact 225 60 r 18 tires with just about all the Tread this vehicle and has 5500 miles on it. So Just about as all the tread that came on a brand new No dense things or scuffs on that front bumper does have the LED running lights the LED fog lamps Passenger side fender no denser dings on that and honestly, I don't I didn't see one single dent on this vehicle No scuffs or scrapes on that rim and as you go down this side of the vehicle You'll notice just how clean the body is how reflective and mirror like that paint is We take these HD videos So if you are far away or even if you're close by and just cannot make the trip down You can still see the vehicle hear the vehicle and have confidence in what you're looking at So you can make a smart buying decision from the comfort of your own home and when you get here. There's absolutely no surprises Very clean down this side didn't see one single dent or ding and This back rim is just as clean as the rest and the back tires are just as new as the front In fact, you can still see the little wear knobs from when the tire was brand new As we come around to the back of the vehicle You'll notice that it does have the dual rear exhaust backup sensors and that the rear gate is an excellent condition This is a power gate So you just press the button here or if you got the key fob You can press that and that gate will open up for you back storage area is very clean Those seats do fold down which we'll check out in just a minute and underneath here you get a full-size spare tire Get that gate down. You just press that button. It'll beep at you three times and then it'll come on down As we come around to this side of the vehicle just as clean as that passenger side Once again, no dents or dings. No scuffs. No scrapes very very clean The back rim is an excellent condition as well and Continuing down this side. You'll notice just how clean the body is And how nice the paint is this one does have the blind spot and cross path detection system Also has the built-in directional signals in the mirrors as long as as well as the heating element has the enter-and-go system Inside the limited package gives you the black leather interior. There are no rips. There are no tears on the seats Both of these seats are heated you get a power driver seat with factory lumbar and factory floor mats throughout This seat is also memory driver seat Power windows power locks power mirrors and it does have auto headlamps as we hop in You'll notice the seven inch tft display, which is completely configurable on the corners And it has a digital Spedometer here and you can see that this one only has 5,528 miles and that the instrument cluster is very nice and clean Has the heated leather wrap steering wheel cruise controls on the right bluetooth audio controls on the left and information center controls Has the 8.4 touchscreen radio with the 4c radio, which means that it has Android Auto and Apple CarPlay capabilities Also has heated seats and heated steering wheel buttons, and this is where your backup camera shows up AM FM and Sirius radio Sirius is always a really nice feature dual climate control you get your stability control and your start-stop feature Which you can turn that off by just pressing that button Has the 4x4 active drive one with the select terrain you get auto snow sports sand and mud Settings USB and aux jack. This is the nine-speed automatic transmission Passenger seat is in excellent condition as well. No rips or tears on that This vehicle has never been smoked in and this one does have the panoramic sunroof So the dual pane roof there and then this glass in the front actually opens up as a sunroof has the home link Buttons right there, and there are your map lights and controls for the sunroof and the sun shade has all the owner's manuals and Original window sticker with this vehicle Back seats are just as clean as the front seats no rips no tears back here It does have the latch child safety system for your car seats two cup holders in the center console there And it does have a 115 volt 150 watt plug-in two USBs and two USB C's Right there as well These seats like I said do fold down for extra storage and they go just like that almost completely flat Which is nice if you have to haul a bunch of extra stuff, and there are those cup holders Side curtain airbags of course as well And we'll take a quick look under the hood. I would personally like to thank you for checking out the video today Hopefully from this HD video you will have been able to tell just how clean this Jeep is all the way around Inside and out under the hood like I said we have the two liter turbocharged four-cylinder motor 270 horsepower engine maze very clean runs very smooth as you'd expect on a 5500 mile car This vehicle has been fully safety and inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off and This super clean Jeep is 100% ready to go to see more pictures of this Jeep or one of our other 450 new and used cars trucks SUVs minivans Wranglers you name it. We got it go to our website www.summitauto.com full pictures and descriptions of every vehicle on our lot and our beaver dam lot All in one place all at summit auto.com and if you'd like to check out more HD videos You can go to youtube.com slash summit auto remember to like subscribe and share on this video and all the videos that you see there In fact in a second you will see a link to subscribe to our YouTube channel on your left a link to more used inventory videos Like this one on your right if you have not been to our website on the bottom link to this vehicle on our website Click those check us out and we really look forward to helping with this super clean 2019 Jeep Cherokee limited. Thanks again


Now you'll hear a lot about the normal the tangent normal coordinate system Now it plays on the strengths of what we've just done here this curvature and all these things actually Go together and you can use them together. So let's go for it First things first. I just want you to consider a circle Consider a circle Circular motion goes round and round and round It is the only kind of movement that oh, that's what that's our unhorrible circle. Anyway It's the only movement that you can find in which the magnitude of the position vector never changes It just as it goes that the magnitude this radius there the stays constant all the time So it's the only type of movement that you can really think of in which in this initial difference frame where this The magnitude of this position vector never changes and as such it's first derivative The velocity vector at any point is always going to be perpendicular To that the position vector that the velocity vector always going to be perpendicular and For us to look at a body coordinate system now imagine we've all seen these action cameras mounted on a helmet on a motorbike or bicycle and It's as if the helmet of the person is absolutely still that's a body coordinate system and this whole world is moving Around now imagine if you are in a particle Point moving along this trajectory as far as you are concerned you have your own coordinate system And the whole world is moving around you and that is a coordinate system that is different from this World view this Cartesian coordinate system. That's a body coordinate system a coordinate system that is going to remain static for from the point of view of Someone or something on that body on that particle that moves along so for that we have this Tangent normal tangent normal Bynormal section some people put the B in and I'll show you what the bynormal unit vector is That is a coordinate system that is fixed on this moving particle and it's fast It's concerned the whole world is moving around it now. We already know this tangent normal vector The tangent normal vector is just the norm of the velocity vector So at any point that I can that I have a position vector at any point that I have a position vector I take its first derivative and I have the velocity vector in other words I have our prime of t That is the first derivative there and if I just expressed its magnitude divided by its magnitude Prime of t So I have a unit vector if I do that its length becomes one And all it now shows me is the direction and that is the tangent normal vector We've seen that the tangent normal vector Now I Want to construct as I have with a Cartesian coordinate system? I have here this it is perpendicular to each other So I want to construct the same sort of thing there. So at this point. I want if that's my T of t there. I want something that is perpendicular to that at any time and I'm going to call that the principal normal Principal normal vector. It is perpendicular to that and At any point I sort of instantaneously want to see that as This sort of scenario if I have a position vector and I take its first derivative in this sort of scenario Which is happening instantaneously at every kind of point you can see it is something like that I want this kind of scenario so that this is my t and this is my n And what do I do? I take the derivative of that So we're going to have this principal normal unit vector principal normal unit vector that is going to be for us t prime of t over its Magnitude so again, it's going to have a length of one So what it basically tells us it's this it's a prime there It's the it goes together with this. It's the derivative of that And divided by its magnet. It's magnitude just to make a unit vector again But it shows us for this side type of scenario now Don't mistake this for this this particle is not moving in a circle But as it stands right at the spot to view it as instantaneously as looking like something like this and if you were to do this You can you can do we can do a problem or you can do problems where you can just take the the dot product Of these two vectors is going to end up being zero in other words. They are perpendicular to each other Now you can well imagine in two-dimensional space that this Normal principal normal tangent vector can point in this direction or it can point in this direction And what it tends to do is it always points in the direction in which This is changing if the slope is changing in this direction at the moment Okay, so it's concave looking from this side. It's going to point in that direction Over here suddenly it's going to swap over looking in that direction in three-dimensional space. It's actually even More difficult because it can not only point in one of two directions But it can point anyway in a circle And there is something called the oscillate oscillating circle in the in the circle in the plane We need to be too concerned about these These things now But what the point of it all is that this usually points in the direction in which The curvature is going at the moment. Okay, it's easy enough to see And then we have this binormal unit vector b That you just have to know about And that is just the cross product That is just the cross product of these two vectors Just the cross product of those two vectors. So nothing here is too difficult too sinister Now we are going on to another form of The another derivation so that you have another equation to play with to determine curvature And for that we're going to make use of this tangent normal Or body coordinate system That stays with the particle wherever wherever it goes


Bloomberg's CIA Apologia accidentally vindicates China's strict domestic policies. In a new article promoting the CIA's new mission center focused on China, and the need to pour more resources into countering Beijing, Bloomberg also accidentally makes the case that many of the Chinese government's controversial domestic policies are entirely justified and completely necessary. Citing anonymous government officials alongside bloodthirsty psychopath John Bolton, the article, China is evading US spies and the White House is worried, argues that a stronger pivot to China can't come soon enough, and reminds readers of last year's House Intelligence Committee report which claimed that, quote, absent a significant realignment of resources, the US government and intelligence community will fail to achieve the outcomes required to enable continued US competition with China on the global stage. End quote. But in their efforts to justify the need for greater focus on espionage campaigns in China, the article's multiple authors explain that the US intelligence cartel has been floundering on that front precisely because of the authoritarian policies which Western institutions have been aggressively criticizing China for implementing. Xi's sweeping efforts to change China's domestic politics and consolidate his control have also taken a toll on American intelligence, the article says. The shift from a system of collective leadership under former presidents toward one dominated by Xi means that the CIA has to go from focusing on the inner circles of seven or even nine top leaders to effectively just one. Chinese academia, the media and civil society organizations are all closely controlled by the government, further compounding the challenge of reporting on the country, the article adds. CIA officers in China faced daunting challenges posed by China's burgeoning surveillance state, which has blanketed Chinese cities with surveillance cameras and employs sophisticated facial recognition software on track threats, claim the article's authors. Bloomberg explains that China's anti-corruption measures have made it much harder to recruit CIA assets. Writing, Xi's broad anti-corruption campaign, which has punished more than 1.5 million officials, has also led to greater scrutiny of Chinese officials' income making payments to potential sources far more problematic, two former officials said. Those efforts were detailed extensively in 2017 by the New York Times, who said as many as a dozen US sources were executed by China, while others jailed, and what represented one of the worst breaches ever of American spying networks, the article also notes. So Beijing's anti-corruption crackdowns, widespread surveillance, and strict control over Chinese society is making it harder for the CIA to undermine that nation, and now the CIA is expressing its frustration through the billionaire media, which shows that China is acting entirely in self-defense when it implements those policies. When people complain about Chinese authoritarianism and lack of transparency, what they're really complaining about is that China is defending itself against a nonstop assault from the US centralized empire which seeks to bring Beijing to its knees. The heavy-handed domestic policies of US targeted nations like China are not morally comparable to the censorship, propaganda, secrecy, surveillance, and other authoritarian measures you see in the US in its lackey states, because US targeted nations are actively defending themselves against a hostile foreign aggressor who won't be content until all nations on Earth bow to its dictates. These are not the same thing. One is a weaker government acting defensively, the other is a globe-spanning power structure that, if given the opportunity, will topple your government using mass-scale scyops, espionage, special operations, color revolutions, and proxy conflicts to force your nation and its people to subordinate its interests to those of the US empire. Sure it would be great if all the world's populations were free to say and read and do whatever they want without government interference, but to pretend we live in a world where populations aren't deprived of those freedoms in response to a nonstop assault by a global juggernaut is to live in a fantasy land. There is a slow-motion Third World War underway between the US centralized empire and the few remaining nations which have successfully resisted its aggressive attempts to absorb them into its folds. Nations like the US use propaganda, censorship, secrecy, and surveillance to advance imperialist aggressions, while nations like China use them defensively. This is a fundamental difference, and to pretend it isn't is to ignore the reality of the power dynamics at play.  Department of Defense, the defense industry. The US war machine doesn't defend anything, it attacks relentlessly and maliciously. Defense is what the nations who resist those aggressions are doing.


2022 Tampa Bay Buccaneers Tom Brady is back, which means the Bucks are going to be back to their winning ways. And they start that with opening the season with two wins against the Dallas Cowboys and the New Orleans Saints before losing to Green Bay and Aaron Rodgers. Now after that, Patrick Mahomes and company come to town and the Bucks pick right back up where they left off, winning their next four before losing to the Baltimore Ravens who I just think are going to be a thorn in everybody's sides this season. The defending champions come to Raymond James and the Bucks take them out and they go to Germany against the Cialice Hawks and they win over there too. Now after the buy, they are in Cleveland where they're going to win before losing to the New Orleans Saints at home. It's just one of those divisional games that I feel like they're going to drop. But fear not, they're going to win out and finish the season with a record of 14 and three back in the playoffs and potentially another Super Bowl for Mr. Brady.