Hi, everyone. I'm Anne Gentel and I see customers in the cloud all the time. So I want you to picture this. I'm at my son's preschool in his two-year-old classroom. I'm on a ladder and I'm cleaning the air vents up above for our spring cleaning day. It's a volunteer day with the rest of the parents. So one of the moms who's working with me on the windows turns to me and says, oh, where do you work? And I say, oh, I work at Rackspace here in town, you know, even though corporate offices are in San Antonio, I'm here in Austin. And she said, oh, we use Rackspace. We use it for this refund rebate site that we have for our city of Austin website so that when the rebate time of the year comes around for your air conditioning, you get to use this website. And we only need it sometimes where there's big traffic the rest of the time it's down. I'm like, wow, this woman knows what cloud means and why you have it. So that is my story of finding customers everywhere. I work on a team of about 30 people at Rackspace and we are the developer experience team. We do upstream work, outreach work and open source. We support directly developers using the Rackspace cloud, which is built on OpenStack. And we now officially support certain SDKs. And so what I'm going to talk about today is what is developer support and what does it look like? And I will take questions at the end. So I'm trying to time it so that I give you time to ask me as well. So what is developer support? Why are we here today? What are some of the terms I'm going to use? Developer support is a bridge to users, users of SDKs, users of the APIs. In our case, we specifically support multiple languages. We have some Polyglot developers on our team, but we also have people who focus directly on specific languages and specific libraries that work on basically cross-cloud, multi-cloud, Rackspace cloud APIs. We also do developer documentation. And so most of you who know who I am know that I am the documentation PTL, Program Technical Lead for OpenStack. And I've done that work since OpenStack started four years ago. I also serve on the technical committee. And so I feel like it's a chance for me to talk not just about documentation. Usually that's all I'm preaching when I come talking to Summit. But I wanted to do a deep dive on very specific documentation for developers using our APIs. Now when we at Rackspace do developer support, we actually really love this book called the Developer Support Handbook. It was written by a Google developer advocate. She'd been working there about four years. Her name is Pamela Fox. So definitely look this book up. She has some guiding principles that are right there in the introduction. Oh, and another note about this book. There's an entire chapter dedicated to documentation. It's there. But this handbook talks about how we need to care about your developer's success. We need to put ourselves in their shoes when they're struggling middle of the night on a deadline trying to get something working. Really think about their viewpoint. Keep them informed, right? That's the point of documentation, but not just dry, dull, boring API documentation. Also blogs and looking at what they are working on and helping them collaborate with you on how to articles. That is an important part of informing your developer base. And always listen to your developers. And I'm going to talk a lot about how we're listening and on what channels developers tend to be. And then importantly, appreciate them, send them stickers, send them gifts, give them trips to your conferences, help them really feel like they are building something with you. And when they ask for features, they know they're asking a team that cares about them. So these are some of the supported languages and libraries that we support on OpenStack first than the Rackspace Cloud. So we test against, honestly, our developers stand up at DevStack and make sure the API calls and their SDK calls work against a DevSkat cloud as well as our Rackspace Cloud. I won't read the list to you, but this gives you an idea. J Clouds is across Amazon. It supports AWS. It's across cloud. We can support HP Cloud. We can support Rackspace Cloud. And it's the same thing with some of these other cross-cloud providers like Fog. We're trying to be, I guess, cloud agnostic. And the main point is that when you see something say something, even if it's not in your language of choice, we're not all contributor developers. We're not all Python developers. These are application developers writing apps on an OpenStack cloud. Well, the great thing about the team I'm on is we actually have a good sense of humor about some tooling for developer support. We have a tool called Parall. And it basically watches on all the channels that we know developers to be on. And they actually put really funny messages like, someone needs help. Weep, weep, weep, weep. It's actually something that notifies us. And this is a shot of our internal channel where we can listen to these all day long and scroll back and up. It's like IRC with nicer pictures and better linking, I guess. But we're watching on lots of places, including our own Exchange server where we have an SDK support at rackspace.com, email address. And the funniest thing was one time the Exchange server was slower than our Parall tool. So Parall sent up an alert and we read it online and then the email came through. Happens quite a bit. But I want to say this shows support across a community setting rather than just individuals reaching out one by one. We're able to actually watch a bunch of sites that developers tend to hang out on and ask questions. So what are some of the places where we're seeing people come in? We watch Stack Overflow, and so our tool uses slurpers. Stack Slurp right up at the top, 13.09%. Another big one is Hub Slurp, which is to watch GitHub issues and pull requests against the SDKs that we support. And it's interesting, the largest one is this RSS Slurp, and so that's a grouping of, say, JCloud's issues plus a community site that we're on Rackspace, a community.rackspace.com website where we can subscribe to an RSS feed. And so the kind of keywords we're looking for are Fog, Rackspace-Cloud, Package Cloud, Go For Cloud, looking for the actual SDK names. And I think it's interesting what we're observing, and so that's what I want to deep dive into today is what kind of things are we seeing from application developers trying to work on an OpenStack Cloud as their platform base. So what are we going to see? Application developers in the wild. So who are they? What channels do they talk on? What do they look like? Where do they hang out? Where do they get their questions answered? Where are they talking to us, the OpenStack community? So these are some of the tools where we're listening. And I'm going to talk about each one in turn. Discuss is a message and commenting system that you can add to your documentation. Gotta lead with that. Stack Overflow is one of a collection of sites that offers question and answers for developers, and we'll deep dive into that because they have an API that I could query to find out more. GitHub also provides an API, and we're going to talk about each one of these in turn. The next one is actually TriStack's Facebook page. And I don't know if you know a lot about TriStack, but you actually have to have a Facebook login to use the API. So we're going to look a little bit at that later on. And then the last one is ask.openstack.org. That's the site where you can do a question and answer style posting very similar to Stack Overflow, but it's an open source engine running it. And then I'll be able to talk about some of the questions we're seeing, the answers, how fast we're answering, those kind of, that kind of metrics and data. So Discuss is a threaded commenting system. We use it a lot on Rackspace API documentation, and so I've been observing that for about three and a half years since we had it in place. In OpenStack documentation, we've actually removed a commenting because we could add a doc bug and a link to ask.openstack.org. So we decided to sort of funnel those to those channels more appropriately than just monitoring all these Discuss comments coming in. We really like doc bugs, so that system's working well for us. Next, Stack Exchange is a collection of sites. Specifically, OpenStack questions are on Stack Overflow where a lot of developers hang out. This engine actually boosts motivations for answering questions by having kind of this voting up and helping out others as part of the site's credibility that you get by being on the site, helping other people on the site. And they have a lot of data, and we'll be able to dive into it a little bit more. GitHub issues turned out to be a really good place to look for the actual users and the problems they were having with SDKs specifically. And so when you want to find out why a developer is having trouble with your SDK, this is a place to look. And then like I said, TriStack, we actually get really cool comments on the Facebook page that you have to use to get to your API on TriStack, which is this community cloud with a bunch of donated compute nodes from various people in the OpenStack community. And then the last one is this Askbot. Askbot is the engine running ask.openstack.org. One of the patterns I saw is that if a person can't find the answer on Stack Overflow, where they almost always will ask first, they'll come over to Ask.openstack. So let's do a deep dive on the data. First of all, discuss comments. We definitely see three categories for requests for help on discuss. When something doesn't work as they expect, they will come to the documentation and ask a question. And so that's just like a shout out for help. Hey, I tried this. It didn't work. I expected this. Can you tell me how do I get from what I got to what I expect? I'm also finding that they're asking for features that may or may not exist. So this is a real place to mine that goal of what is the next thing to implement in an API that users are looking for. And then lastly, the request for a docs fix. This has happened on the Rackspace Cloud APIs documentation where one of our build tools removed all of the indents from our JSON examples. Kind of embarrassing, but man, immediately we heard about it from the discuss comments. And I have also seen a pattern where people will ask a bunch of questions at once on a single document. And it's as if they're doing a review of this document all the way through. And so that's really useful to a doc writer to actually know that people are reading and reviewing your documentation is a huge bonus. But it is interesting to see that pattern of, it's obvious you read through this whole thing, because I now have six comments to address in the morning when I came in. And then Stack Overflow, I'm going to look at the frequently asked questions, related tags. That's tags related to the OpenStack tag. Some of the top tags we see and how they're grouped. Unanswered questions, that's a very important one. And also, who are we seeing answering the most? So frequently asked questions. Anybody have a guess? I'll ask you the questions. What do you think is the top question asked on Stack Overflow? And they have their own algorithm for how they're doing a frequently asked question. But for sure, why can't I ping SSH to and from IBMs? This is problematic. And I think that it happens because of security groups. Oftentimes, I've talked to many operators who say, number one user problem is they didn't set up security groups ahead of time. So there is a lot of setup before you actually get to a running VM that gets to the world that can ping Google.com. What's interesting is there are oftentimes these questions with the ping or SSH that have no answer. And I think that that's the type of question that goes past the, yes, I have security group set up. What's next? So that's the kind of deep dive where it is really hard to troubleshoot, because there are so many networking options. You may not know what that user has specifically in their DevStack, in their Provider Cloud. It's just really hard to troubleshoot. How do I change the admin password for the dashboard? That struck me as a surprise. And I think it is one of the top frequently asked. It does have an answer. But it just surprised me that the dashboard itself was kind of giving me hits on the OpenStack user side that it sounds like people actually want to get admin privileges right away. So to me, that points to the real, we need to get to the tipping point where people don't want to administer OpenStack Clouds. They want to run things on OpenStack Clouds. This one did not surprise me. And I'll tell you why. How can I create an OpenStack image by importing an OVF file? This page that explains how to do that on the OpenStack doc site is the most exited page. Now, you might think that means it's not doing its job. I say it is. People got the answer. Left the site. They're good. This is awesome. And then lastly, how do I make an application on OpenStack? And I tell you, this was in the top 10, but not the top three. So I think this is really crucial to understanding where we are in the timeline of adoption of OpenStack. People are running it like crazy. But we still need to make sure that we can serve the application developers who are saying, hey, I looked for Hello World on OpenStack. Never found it. So what is related to OpenStack? This next one shows from the API a data visualization of what is the most correlated tags by percentage of all the tags related to OpenStack. And what's interesting is, I don't know if you caught it on a previous slide, when I did the screenshot of the Stack Overflow related tags, there were 121 OpenStack-swift, 122 OpenStack-nova. So I think even in the week or so when I ran the data, these actually got a little bit out of sync. So what I'm finding is there is a lot of questions, Nova and Swift, for the first two. And here we are four years later. They're still very popular in people asking questions about them. But I also think that the large correlation to Cloud and Python is just that people, when they write tags, are going to definitely group things like, I need a Python person. Well, of course, this is very general. It's related to Cloud. I'm going to tag it this way. Now, this shows the ones most related to OpenStack. But what about the top tags? After you see the ones that are related, which ones are the most tagged questions that are tagged the most often? So the larger bubbles show that definitely Python, I would expect that from an OpenStack tag correlation Python. PyRx is a wrapper for all of the Python-nova client, Python-swift client, which were always meant to be used as libraries, not really CLIs, but that's more OpenStack lore. But PyRx is just a wrapper for Python developers to have objects to manipulate that based on those client libraries. And I think it's also important to notice. Anybody see a Windows relationship there? Next one, right? So I think that's important to note, too, that there are needs for Windows applications on OpenStack. And that is where a lot of questions are coming as well. The smaller bubbles are a grouping of tags that are just so many tags that it didn't show up a bunch, and that's the people who real tag happy. And they're like, I'm going to put six tags on this, and then my question will be answered. So that might be JavaJ, Clouds, Cloud, Amazon, Google. That's going to be a smaller set of questions. But I also think it's interesting that some of these smaller bubbles are related to security, related to networking. And so while there may not be a ton of questions about it, people are definitely looking to relate those. I'm trying to get this thing working on OpenStack. It relates to security problem. Now the interesting one, what about unanswered questions? And it's kind of a long list. Oftentimes, and the top one, and let me tell you, the frequently asked questions had 1,000 views, and these questions had 100 views. So it's hard to say whether these are actually not able to be answered, or whether they just aren't getting enough views. Like it's a small enough set of customers or users trying to figure this out that they're just not getting the foot traffic for someone to actually know the answer. But definitely, I want to say probably, oh gosh, the things that surprised me, I mean, still a lot of these are networking based, which I don't, of course, right? Like that's exactly what I would expect. I was honestly a little surprised to see some of the celiometer questions, getting no answers. But also that they were being asked that much. It seems like a new project to me in my OpenStack timeline. And the questions related to AWS are very interesting. In one case, they were saying they used the same command in Yucca tools. But then when they tried it in the AWS PHP SDK, it worked. So they were doing EC2 credentials against an OpenStack cloud. Very interesting. But also pointing out that our community doesn't always do that and may not know the answers, hence unanswered. So who are our rock stars answering these questions, right? Anybody have a guess? Is anybody in the audience? It's not PTLs. None of these guys are PTLs. And they are guys. I have to point that out. Matt Joyce, Everett Taves, Lauren Hoxstein, the rock star is out on Stack Overflow answering questions. And these guys have been around OpenStack for years. They were very early on. Everett Taves actually set up one of the first OpenStack Clouds in Canada, then flew to Australia and helped Tom Feifield set up the first OpenStack Cloud in Australia. So these are guys who've been around the community a while. They've been on the operator side. They've been on the developer side. Everett is now a maintainer on J Clouds. And so these are people that are all up and down the stack of what I do for OpenStack. So how about Askbot? Askbot is that little engine that's open source that runs ask.openstack.org. There's about 4,000 page views a day. And I definitely see there are way more questions from operators than application developers on Askbot OpenStack. That could be correlated to it's not exactly where developers hang out, because it's so specialized. So the developers are on Stack Overflow. But I think it is interesting to think about how we could start to aggregate and combine efforts across companies for supporting application developers on an OpenStack Cloud. If you think about how also an API call needs to be configured, some of what my data was showing is that even if it was related to an API or an SDK, it was still an operator or an engineer trying to get OpenStack working for their users. And so what I think it would be great to do to collaborate is to figure out how to support those users' users, the super users' users. That's who we need to get to that next level. So a little bit of a deep dive on the data. VMware, what? Why is this even in the top part, top portion? Well, there's this little thing called a VC-SDK that an engineer has to download and install and configure in order to get that particular hypervisor driver working in Nova. So that's why that ended up on the list. But I'm also not surprised to see PHP quite high. And we especially see a lot of popularity with PHP and our Cloud Files product, which is Swift Object Storage. But it was pretty funny to see VMware in the top four. And you can also tell the volume isn't very big. There's less than 30 questions, even in the top one, onask.openstack.org. And then ones that have API in the question or answer set is interesting to me.  I read a paper that said Keystone is Cookie Monster. So it is the way that you have to talk to any of the APIs. So of course, identity is going to have the most questions. Next is compute followed by networking. Here's the one that surprised me. Why isn't storage somewhere in the top three? Well, guess what? Measuring, metering, that's in the top four, right? So that one actually took me a little by surprise. But I think that ask.openstack.org is a logical place for people to ask questions about salameter and its API. How do I set alarms? How do I trigger alarms? All of these kinds of things. And it's fairly new. So again, I was a little bit surprised. So let's deep dive on the next bit of data. Octocat, our friend, let's look at the GitHub issues that we see. The GitHub issues are interesting when you look at specific SDKs. And so that's where being on the team I'm at really gives me a good viewpoint into how our users really putting this into place, putting this into practice. So the one I did a deep dive on, because one of my team members had done it his first week at Rackspace, is PHP OpenCloud. And so he looked through 190 GitHub issues and did some categorization. Were they asking about a particular platform? Were they asking about a particular service? And what he found is 28% were specifically asking about object storage. And then only 9% about the SDK itself. And it's not even so much questions because GitHub issues are very specific bug requests. I thought it should work like this, but I actually got this. Can you tell me where my cognitive dissonance is caused by a bug or actually a design? Some of the users on this platform, I'll go back to another Austin, Texas story. Oh, but first of all, the number one by downloads WordPress backup tool. It's called Updraft Plus, uses PHP OpenCloud. So they are using the SDK to do backups of WordPress. And I also know a statistic where I heard that WordPress sites are 22% of the internet. So this is a big deal. These are people we need to support, keep them running, help the rest of the internet keep up. Right? But Savado Technologies, you wouldn't know it by the name, but they actually make power tools for real estate agents.  And they actually do synchronization of data between, in the US, MLS is multiple listing services. And that's where all the base layer data for real estate listings is found. And in real estate webmasters is another one, and they actually do the websites themselves, and they're hosted on Rackspace Cloud Files, which is object storage. And the house I bought most recently, right after the Portland Summit moved in, was in fact, hosted on this person's account. So, small world when you come to OpenStack customers. Call Fire is a video broadcast, and it actually does reminders and notifications via video, very interesting use of the technology. They also do phone trees, which, you know, any time I call a doctor's office, I'm like, do I need, wait, is it scheduling? I don't know, but anyhow, they're responsible for keeping that going. They also do some of the auto dial leaving messages for political campaigns. And one of the US-based ones is moveon.org, they're actually one of their customers for basically getting the message out to people on political action items. And then Dear Doc is a way for customers, patients to securely transmit messages with their doctors. So next, let's look into TriStack. Last time I looked at TriStack a couple months ago, there were 10,000 members. There are 15,000 members now. So this is amazing, it's this growth thing, and it's basically a community cloud with shared resources. People have very limited quotas, so many of the questions are about their quotas, and I actually had the opportunity, thanks to Dan Redez, who runs all of TriStack, to look through all the logs, and let me tell you, people were querying their quotas or their policies all the time because they get very limited storage, very limited instances. But I think the neatest thing about this particular project is someone posted just the other day, Dan Redez, you're my hero, you've inspired me to build a cloud in my garage, and it is growing faster than I ever expected, so that is really cool. I hope it'll move out of the garage someday, right? So we also found that a lot of TriStack users tend to go to the dashboard, but then we also have services turned on that are API only. So if you want to use load balancing as a service, you must use the API. Another thing that happens commonly, because it's such a small cluster, the floating IPs run out, and Dan has to sort of scramble to reset the database and make sure everybody gets a floating IP again. They also had the open vSwitch database go corrupt, he had to rebuild it, so it's a neat case study in what it takes to run a cloud and serve users. So what do I want us to think about today based on all of this data that we're seeing? What are some of the takeaways? What have we learned from actually looking at what our users are asking? For one, on PHP OpenCloud, we had a person who just said, look, I have these large files, but I'm on this terrible network. Can you do any kind of timeout optimization? So there are very specific things that SDK developers can do to have that empathy for the application developers. We will absolutely be able to think, API and SDK developers will always want to do bulk actions. I'm gonna do things on 1,000 objects. I'm gonna do things on 10,000 objects. Try to think about bulk operations. Consistent naming, this is one of the most difficult things to do when you're creating an API is for projects in their silos, they don't often look over to other APIs that came before them to replicate their naming. So I think that's a really important thing. And anytime I look at supporting developers, a lot of times it's the names or the assumptions about names that get in the way. I think that that will go a long ways. And I also want to make sure that we think about date time formats. I think that's, isn't that one of the hardest computer science problems, whether you start with zero or one and then any kind of date time subtraction, it's pretty terrible, right? So just think about how to make sure that every OpenSec API uses these consistently, thinks about these consistently. And also across services, making sure that, you know, if Celiometer chooses one way but Nova had already chosen another, just not to make the assumption that they would know my API works this way if they're already used to another. And of course, the errors and error messages. This is from one of the PHP OpenCloud users and he's like, yeah, sure, if you've been doing this forever and you're totally great at it, which I'm not yet, you'd know what a 409 means. But in my case, I had no idea. I was just told good luck figuring out. And this is where documentation comes into play, of course, but I would also like to encourage us as a community to make sure that the APIs can tell people more about the errors that they're getting and do customize error messages and don't just make them look up that 409 error HTTP error. So another thing I wanted to discover was I'm really tied into OpenStack releases. I know Icehouse, I know Juno, I know Havana, Grizzly. I know all these code names for the releases. Are SDK and API developers understanding or tied to releases at all? The answer is nope. They do not even know, probably don't even care. And while we are very tied to releases, the users just wanna get their thing running with the SDK version that they're handed. The SDKs themselves have not caught up with the fast addition of projects to OpenStack. So JClouds does not yet have heat support. It does not yet have Celiometer support. It does not have Glance v2 support. It does not have Keystone v3 support. It does not have IPv6 support. All of this is discoverable from looking at their backlog of what they're working on. So I would also like OpenStack as a community to understand they need the resources to get these implemented. Oh, and what's the hot new thing in Swift? Storage policies, not yet in the SDK. And that's just for JClouds. There are some that are ahead and some that are behind, but JClouds is a large one and pretty well supported. So I want us to start thinking about how, look, the adoption of these actual services on the API level are behind and are not, we can't just assume that an SDK is gonna have it right away. So this is my favorite documentation joke. Dockers, the hot new thing. The new hotness. No, documentation is the new hotness, let's go. All right, so these are some links of how documentation is supporting OpenStack and application developers on OpenStack. Last release, we set up developer.openstack.org. You can get all the links to all the SDKs that are known to support OpenStack Clouds. We actually have had an API reference for, oh, three years now. And I tell you, when we first announced it in conjunction with the launch of TriStack, I had people come up to me after the talk afterwards and I was like, thank you for doing that. I finally have the information I need to get going. There's also a new movement toward API specifications. And so I have a series of patches going in that will, onspecs.openstack.org, that will define to the contributor developers what it is that the API itself will do, look for, should be standard. And I'm doing a design summit session about scaling documentation across projects. And one of the things that is really hard to scale documentation across is API documentation, specifically reference documentation. And we're still not serving the application developer very well in the documentation path through SDK docs and that kind of thing because the SDKs themselves, like J Clouds, like PHP OpenCloud, take care of their documentation within their, I guess, community, which makes sense. So we're linking to them. So what is it that we can do also as a community besides documentation? I'm always preaching about documentation. But it is shaping our content strategy. This kind of deep dive is helping us look at other things. And so what is it about the SDKs that we can do? What's another area of activity if you wanna get involved?  It's been around a couple years now, but slowly adding more and more services. And so there's a getting started talk about that right here in this room this afternoon. And then also there's an API-competible mock service and it's called MIMIC. And so there's a talk about that on Wednesday. And so there are things that people in the community are doing to make sure that our API testing can be very robust, very across services, find these inconsistencies and then we'll be able to fix them, right? And then one of the most important ones going on are new working groups. And I mean, literally I was in the OpenStack training on Sunday and there's a new flag that the API working group put together called API Impact. And so a contributor developer can put that on their commit message and then the working group will know to go review that patch for any kind of API. And so API guidance or API consistency across services. And so the API working group is just getting going but we have a lot of sessions to discuss at the summit and a lot of people adding themselves to our Wiki page. And the idea is to offer style guidance, to write a set of draft guidelines so that contributor developers have a place to look it up instead of just kind of inventing it when they write the patch. There's also the application ecosystem working group. They have a bit more of a wider scope, a little bit loftier goals, create an environment where a diverse array of applications built for OpenStack can thrive. And so they're doing a couple of sessions again where we need to start talking. And especially if you are engineering or operating in OpenStack Cloud, please help us understand your users and what you are doing and what you need the OpenStack community itself to make sure that ecosystem is activated and that they can start to talk to each other. And then let's, this is my call to action. Let's watch and learn. I wanna talk about a couple of takeaways. I would like to see us strategically invest in documentation, API documentation, reference documentation, examples, how to run code right away, and how to do community-based docs that are still about this set of APIs that we are providing where we are serving not only the application developer themselves, but also serving the developers writing the J Clouds, the LibCloud, the CrossCloud SDKs. Because we have that opportunity to do community-based support on Stack Overflow, on ask.OpenStack, as a community, I would love to see us work with the contributor developers on ensuring that the application developers are also supported. And also work with contributor developers to make sure that their API design is really robust, really thought about all the edge cases, really has that user empathy, put themselves in their shoes. That's the end of my data collection. Do we have any questions? Go ahead and step up to the mic and ask. And I'll try to do a good job of repeating it back. Boy, I was really worried you guys have asked me the tough questions about the data. Right, the question is, is the Parallel tool open? And I have to tell you, yes, it is. You can write your own slurpers for it, but yeah, it's completely open source and it's under Racker Labs on the GitHub, on GitHub site with the Racker Labs org. So github.com slash Racker Labs slash Parallel. I would love to see us maybe in OpenStack stand up an instance of it. And it's frankly hilarious. So it's really cool to see that stuff. And if we just had it connected to an IRC channel where the notifications came in, just keep an eye on that all day. It'd be really interesting, especially 24-hour round-the-clock kind of support. Yeah. It's like, help, help. Somebody needs help. Weep, weep. It's pretty cool. Yeah. I like that question. So the question is, is there any way we can add on ask.openstack.org a way to identify the type of person asking the question? Is that accurate? We have a really good relationship with the developers of Ask.OpenStack, the Askbot itself. One of the things I'd like to add, that identifier would be great, right? Persona-driven, who's asking what sort of empathy can we have for this particular person? I don't know today, but they're open source developments, so all we have to do is ask. Yeah. Yeah. Any other questions? Right. The question is, how does the feedback we receive channel back to the SDKs themselves? Because our whole team is very in tune to the support aspect, I think it's really neat. Our developer advocates are the ones doing the support. We also have this team of people who are in support teams at Rackspace directly supporting developers. So we have that line from support to product. In Rackspace's case, that's just a direct line to say, we want to be able to boot from volume. We want to be able to have these kinds. So we have an entire backlog of things that came in from developer support. And then there was one more question I can probably go ahead and take. Yeah. So the question is similar to this one, which is, now that we have all of this information, is there a feedback loop to the developers making their products? This is, I think, the first session on developer support at a summit. And it, again, just speaks to the fact of where we are in the whole timeline. We've been supporting operators really well for a little while. We've got to get really good at supporting the application developers and getting that feedback loop. Yeah. OK. Thanks so much for coming, everyone. I really appreciate your time.


The Equitable Life Assurance Society presents This Is Your FBI. This Is Your FBI. The official broadcast from the files of the Federal Bureau of Investigation. Presented as a public service by the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community. Tonight you have a chance to do one of your friends a real favor. If you know someone who needs an ideal home mortgage, you can not phone him and tell him to listen to this program for an important message coming in about 14 minutes. The Equitable Society will give complete details on their assured home ownership plan. This famous equitable plan is a money saver, a worry saver, a home saver because it combines a low-interest rate mortgage with special life insurance protection, all in one package. It's America's finest plan for home ownership by the Equitable Life Assurance Society of the United States. Tonight's FBI file, The Lonesome Lamester. The case from the files of your FBI demonstrates that for the most part, criminals are primarily opportunists. Not many of them plan carefully to commit their first crime. That happens because circumstances present them with an opportunity for illegal gain and either their weakness or their greed overpowers their sense of right and wrong and they plunge into a criminal career. It does little good to attempt to impress upon those people the irrefutable fact that crime can never possibly be made to pay because even if they accept that fact, it would not prevent them from the commission of that first crime. When circumstances conspire to present them with that opportunity to gain something without earning it, they are so overcome by the temptation that they do not stop to think. They grab automatically. Or in that moment when they make that decision, they adopt for themselves the motto of the criminal. The motto of every criminal throughout the world. To take first and ask questions later. Night's file opens in the dimly lit hallway of a walk-up tenement in a large Midwestern city. A man and woman are standing outside an apartment door. Well, thanks for bringing me home, Mr. Snyder. That's all right. I'd ask in but the place isn't this. Oh, well I have some errands to do anyway. Okay. Wait. Yeah? Are you going to be busy later on? I don't know why. I thought, I don't want you to think I'm being fresh or anything. I thought maybe we could go to a movie. So will. Then you'll go? Sure. Where do you want me to meet you? Well, will here be all right? Sure. I'll pick you up then in about an hour. Fine. See you later. All right. Sally. Oh, you're home, huh? Who's the guy? His name is Snyder. I mean, where'd he come from? He's a customer at the restaurant. He's got a pretty nice car. How do you know? I made you out the window. Oh, well. Your dress is pretty good, too. I didn't notice. Throw in your little romance, did you? He's a lonesome guy. Now drop it. I went to bet me today during lunch. Sorry, a nice dress. It was too much dough, but I went for it. Mm-hmm. I won't get it till tomorrow. Haven't it altered? Seems I'm having measurement trouble. They had to let it out about two inches. You know, there's something funny about him. About who? Your friend. Alla, you still. I'm trying to figure him out. Get his ankle. Look, why does there always have to be an angle with everybody? Because there always is. Oh. Look, why would a guy with nice clothes and a good car eat at that hash house? How do I know? You know, the bum must be one of them suburban cheats.  And he comes to town once a week to let off steam. He told me he's single. The guys have been handing that line out since before a silent picture. Well, I believe him. Okay, all right, all right. No, I heard him say he was going to pick you up in an hour. That's right. Where are you going? To the movies. Do you mind? No. In fact, I'm glad you're going. The next morning at the local FBI field office, special agent Jim Taylor is working on a file as agent Vince Cameron approaches. Jim. Oh, yes, Vince. I came over to say goodbye for a couple of days. I'm off to the hospital. Why, what's wrong? I got to have my tonsils out. Hey, it's too bad. I wish you were going to be with me on the Stevens case. He was the teller at the National Security Bank who disappeared suddenly last May. Oh, I wasn't with this office then. Oh, well, the story is, when the bank examiners came in to check the books, they found that Stevens was $62,000 short. He got quite a bit of publicity. I imagine. And as I say, he just disappeared, but completely. How come we're suddenly getting active on the case again? There's been a new development. Mr. Woods at the bank called and said he had some information about Stevens. I see. It seems that a depositor is a friend who took a cruise to South America some six months ago. He showed some movies that he took on the trip. Oh. And the depositor recognized a man who was standing in the background. It was Stevens. Oh. So he called Mr. Woods at the bank and he definitely identified Stevens. That was six months ago, Jim. He could have covered a lot of territory in that time. Maybe he has, Vince, but at least we're six months closer to him. Have you spoken to the man with the pictures yet? I'm going over to meet him now. Hey, what do you do at the hospital? In an hour. Well, I'll take care of the legwork on the Stevens case. You just worry about taking care of yourself. What is it, honey? How do you like it? Like what? Find a dress. Oh. Looks okay. Well, thanks. How'd you like the movie last night, huh? Not bad. Hey, do you like that part about the fight in the mountain cabin? Yeah, I thought... Have you seen the picture? Mm-hmm. When? Last night. Huh? I was sitting right behind you. Oh, now look. I wanted to follow your friend, find out where he lives. Al, I wish you'd... He lives alone at the Kenmore apartments. I went back to the place this morning. He was out, so I let myself in. To his apartment? Mm-hmm. I get a passkey. Al, why? I told you I wanted to find out about him. In case the whole joint. All I could find was a social security card and a driver's license.  What do you mean? Well, according to the license and the social security, his name ain't Snyder. They were made out in the name of Harold Stevens and Cleveland. Maybe they belong to a friend. Mm-hmm. The description on the driver's license fits him too good. Well, what do you make of it, then? I think that guy is a lannister. Oh, that's him and little character. Yeah, I'm going to find out. How? Got me a friend in Cleveland. I'll write him a letter. I'll just ask him to dig around on anybody named Harold Stevens. Hi, Jim. Hey, Vance. Good to see you. Thanks.  I was too healthy. Why don't you look fine? I feel good. Oh, that's new in the Stevens case. Plenty. I went over and looked at those movies and interviewed the man who owned them, a man named Baker. Did he remember Stevens with the trip? Yes. He said he'd gotten quite friendly with him. Fine. Stevens boarded the boat in Rio and went all the way to New Orleans. He said he was going to stay there for a couple of weeks and invited Baker to have dinner with him. I don't know of a better place to get a dinner invitation. Yes, but Baker wasn't sticking around New Orleans that long, so he had to pass it up. I wired the New Orleans office, asked them to check the hotels and see if they could get any lead on Stevens. Any luck? Yes, they found he had registered at one of the hotels, but he stayed two weeks and left. Any forwarding address? Yes, a whole series of them. Here's the list. From New Orleans, he went to San Antonio, San Antonio to the Grand Canyon, Grand Canyon to Los Angeles. Really seeing the world. From Los Angeles to San Francisco, San Francisco to Yellowstone Park, Yellowstone Park to Bay City. You couldn't have gone any more places if you joined the Navy. No. Well, the trail ends at Bay City, and it looks like a dead end. How come? He checked out of the hotel in Bay City, and at that place, he left no forwarding address. I see. He used several different names on the journey, but they weren't too difficult to trace because every one of them were with his real initials. Have the Bay City police been notified? Yeah, they're making a check on him now. You know, Vince, I've got an idea he's still up there. Why? Every place that he did leave, he left a forwarding address.  In Bay City, he just checked out. No forwarding address, no tickets, no nothing. Vince, tell me, do you feel well enough to do some traveling? Sure. Now, let's take a trip to Bay City. I got an answer. An answer? From what? The guy I wrote to in Cleveland about your friend Snyder. Oh. You know what? Mr. Snyder, or to use his real name, Mr. Stevens, a bank for 62 beautiful Gs. Oh, I don't believe it. Oh, honey, honey. I talked to my boy on the phone, told me the whole story. Well, what do you know? Wonder what made him do it. 62 Gs? Look, baby, what do we care what made him do it? We know he's the guy. That's all it counts. Al, if he stole $62,000 from a bank, he's too big for us. No, none of he's got any that dough left, he ain't.  Uh-uh. I don't figure I'm doing it that way. Well, what are you going to do? You just get them up here. I'll show you. Oh, baby, baby, this is the big one. Let's hook them while we got the chance.  Hello, Sally. Come on in. Thanks. I, uh, I'd like you to meet a friend of mine. Oh, I didn't mean to break in while you had company. That's all right. Mr. Snyder, this is Mr. Adams. It's very nice to meet you. Ah, same here. I'm sorry to be late, Sally. I'd have been here sooner, but there was such a crowd at the station. What station? The railroad station. I went down to check my bags. You going someplace? Yes. I wanted to come by here before I left. I'd have come down even if you hadn't called me. You see, I wanted to thank you. Thank you? For what? For being such a pleasant company. For being nice to me like you have. Uh, where are you going, Mr. Snyder? Well, I'm going east. Oh, and I guess we better get right down to business, huh? What do you mean? Well, I'd done something a few days ago which wasn't exactly ethical, Mr. Snyder. I busted into your apartment. What? You don't leave much around for a guy to look at, but I did find a social security card and a driver's license. They were made out to a Harold's students. Look, mister, you had no right... Let me finish, huh? The description on the license fits you real good. The hometown on it was Cleveland, so I wrote to a plan of mine there. I don't want to hear any more about this. Just stay put, brother. I heard from my friend in Cleveland today. Now I know why you changed your name. That's quite a job you did. 62 thou is a real good score. Mr. Snyder, are you really that guy? Yes, sir. Well, that saves us time. Mr. Snyder, we've got a deal. I'll figure out a deal. What are you talking about?  All you've got to do is cut us in. I don't understand. Give us a piece of the 62 Gs and we'll send nothing to the cops. I'm afraid you're too late with that, Mr. Adams. What? I've already decided to give myself up to the police. What? I'm on my way back to Cleveland now.  No, no. But I was when I stole the money. I've been miserable ever since, knowing that they were looking for me afraid of every stranger, every knock on the door. Are you really going to turn yourself in? Yes. I've got $40,000 left. I'm going to give that much back to them and ask for mercy. So, you see, Mr. Adams, whatever your idea was, it won't work. Sit down. What? I said sit down. You got 40 Gs, Mr.  We will return in just a moment to tonight's file which shows how your FBI protects American citizens and American home. Now a word about another type of home protection. Protection to make sure that some sad day you won't have to turn to your wife and say... It's no use, dear. I can't borrow another cent. All those doctor and hospital bills last winter and then losing my job this spring, now they're going to foreclose the mortgage. We're going to lose our home. When a man has worked and saved for a home of his own, it's pretty hard to lose it. And that's why the Equitable Society created its assured home ownership plan. This money-saving, home-saving plan combines a low-cost first mortgage with life insurance to give you two-fold protection against the two greatest dangers in home mortgages. The first danger is hard time. In the Equitable Society's assured home ownership plan, a special cash fund is built up during the owner's lifetime. It's always ready for use of sickness or unemployment, threatened home security. As the mortgage shrinks, this cash fund increases. For example, it can be used to pay off a 20-year mortgage in approximately 15 years. The second hazard in home mortgages is the death of the breadwinner. In the assured home ownership plan, the Equitable Society cancels the mortgage if the owner dies. It's paid off in full. And what's more, every dollar previously paid under the plan to reduce the principal is returned to the widow along with the canceled mortgage. Last but not least, the mortgage interest is only 4%. And there's a liberal allowance to cover title search, lawyer's fees, and other closing costs. So all in all, a man is very fortunate if his health, age, income, his home, and his location qualify him for an Equitable Assured Home Ownership Plan. To find out if you qualify, get in touch with your Equitable Society representative. Look in the phone book or write care of this station to the Equitable Society. That's E-Q-U-I-T-A-P-L-E. The Equitable Life Assurance Society of the United States. And now back to the FBI file. The Lonesome Lamester. The world is a large planet. According to the best available figures, it consists of more than 51 million square miles and is inhabited by more than 2 billion people. But with all of that, it can still be very small when you are the object of an intensive manhunt. Nowhere is there an island of putter safety for you. Nowhere are you absolutely free of the fear that the next person you meet will not be the one to recognize you. Or even that the next knock on the door will not be the police who have at long last caught up with you. Living under those conditions, there is constant terror. Sleep becomes a terrible memory. You stay awake night after night planning your next move, planning which retreat to use until finally you weary of the constant pressure. You weary because you are sure of one thing. You are not sleeping. And you know there are others who are not sleeping. Others who are searching for you. Others like your FBI. Tonight's file continues at police headquarters in Bay City. Well, Vince, I went by the central hotel. That's the place Stephen stayed when he first got to Bay City. Anybody there remember him? No, but we checked back through the reservations. His name was there. Well, that doesn't tell us anything we didn't know before. Except that I learned that he checked out at 322. How does that help, Jim? Well, I figured there was a chance he might have taken a taxi from in front of the hotel because he did have some baggage with him. I see. Now, this box here is full of taxi trip records. Every cab ride that was taken on the afternoon of the 7th is in this box. We've got to go through every one of them? Well, that's already been done. Excuse me. Special Agent Taylor. Yes. You have? That's fine. Just a moment, please. Okay, go ahead. 814 West Jefferson Street. I've got it. Yes, thanks very much, Captain. Vince, that was Captain Lane up at the Second Precinct. A taxi trip record led one of his men to Stephen's apartment. Let's get a search warrant and get up there. Look, it's Snider. I'm going to ask you once more. Where is the money? I can't tell you. You want me to go to work on you again?  I can't, Sally. It's the bank's money, and I'm going to return it to them. Your friend here can hit me all at once. Wait a minute. Wait a minute. I get an idea. What is it? He checked his bags. He's probably got the dough in one of those bags. Yeah. I'm going to fresco him. Stand up, you... No, I said... Leave me alone. No, you... No, right this way. Let's see where we... Easy, Mr. Leave me alone. Wait a minute. Here they are. Look, there's two claim checks. Sally, take this and get those bags. This is the closest we've been to Stephen's. This place looks like it's been cleaned out, Jim. Yeah, the superintendent said it was bare. Any point in our looking around? I want to examine that waste basket.  All kinds of papers. Huh? I wonder what made Stephen's leave. No telling. I doubt that he could have normally were closing in. Hey, Vince. What? Here, look at this. Is it from the basket? Yeah, it's part of a letter. Look at what's written on this piece here. W-O-O and then here on this one, D-S. Woods. Mm-hmm. Isn't that the president of that bank? That's right. Vince, will you take Stephen's picture down to the railroad station? Sure. And see if anybody can recognize him. All right, where'll I meet you? Back at headquarters. I haven't worked on a jigsaw puzzle in years, but I'm going to try to piece this letter together. It might help us. Atchoo, Sally? Yeah. Thought you were never coming back. Well, these things are heavy. Take them, will you? All right, all right. Clear that table up, will you, honey? I'll throw this one right up there. All right.  Yeah. Now the bag's locked.  Look at all that green stuff. Oh, baby, it's all ours. Hey, what happens to him now? What do you mean? Well, he'll go to the cops as soon as we let him free. We ought to blow him. No, no. We can't just sit here. Honey, we got a little deal, a little square, everything. How'd you make out at the railroad station, Vince? Nobody recognized the picture, but that doesn't make any difference now. Oh, why not? Stevens is in a cell down the hall. He's what? He was brought in about 15 minutes ago by a young girl and her boyfriend. The girl works in a restaurant as a cashier and Stevens came in for dinner. Wow. She recognized it from a picture in a detective magazine. One of those wanted pictures? Yes. Mm-hmm. Said she called her boyfriend because she was afraid she wouldn't be able to handle Stevens along. Vince, have you seen Stevens? Yes, I went down and had a talk with him. He's got a story. Oh, what kind? He stated that this young couple stole $40,000 from him. He also claimed he was about to make partial restitution when they took the money. I see. Oh, I couldn't piece those bits of that letter together, so I sent them over to the lab. We shouldn't need them now, Jim. Well, I'll see what the report is on it anyway. Vince, I think I'll go down and talk to Stevens. House tomorrow. Tell him I quit. Yeah. Call that hash house tomorrow. Tell him I quit. Yeah. I'm gonna stay in bed till noon. Oh, I swear. When do we collect the reward? Pretty soon, I think.  I never would have thought of it.  You're not supposed to have brains. Ha. You say the nicest things. Who that? Don't know. Should I answer? Sure, go ahead. Okay, coming. Sherman? That's right. Who is it, baby? I'm finding out. I'm a special agent of the FBI, Miss Sherman. Oh? You're my credentials. He's from the FBI, Al. I'd bring him in. Come in. Thank you. I suppose you'd come to ask me some more questions about that guy, Stevens, eh? Yes, yes, I have. Well, there was no hero stuff in the deal. As soon as I see who he was, I know there's only one thing that they'll call across. Mr. Chandler, what happens with the reward? When do we get it? Well, I have sort of a presentation to make you both right now. Oh? These warrants are for your arrest. What is this? I had a talk with Mr. Stevens. He said he was about to surrender voluntarily to return $40,000 out of that money that he'd stolen.  I don't think so. You see, we found some torn pieces of paper in the wastebasket in his apartment. They proved to us he was telling the truth. Look, Mr. Chandler. The laboratory pieced them together. They proved to be a letter that Stevens wrote to the bank he used to work for. It said that he was returning to Cleveland and was bringing back $40,000. He didn't have a dime on him when we caught him. That's the truth. I'd save that story for a judge, if I were you. And I'd make up another one, too. What do you mean? To explain what those two bags are doing in that corner over there with the chess on them. I believe they belong to Steven. We brought him here before we took him to police station. I believe that. I also believe he took his money. But now before we go, are you going to give me that money or do I have to look around and find it myself? Herbert Snyder was sentenced to 10 years for bank embezzlement. Al Adams and his girlfriend, Sally, also received 10-year sentences for receiving stolen property. And thus, once more, did the laboratory of your FBI publish the proof which was needed by a special agent in order to close the case successfully. The lab, as it is called, does not perform dramatic miracles, but it does do a thorough and partial job of helping to investigate crime scientifically. 16 years ago, the Federal Bureau of Investigation Laboratory started with one man and one microscope. Today, there are 300 trained scientists at work examining evidence of crimes committed in every state. Last year, more than 100,000 such pieces were examined. And in every instance, the lab was not looking for evidence to convict. It was looking for the result of a scientific investigation. And science knows no master. It will prove innocence as well as guilt. And for that reason, the laboratory of your FBI functions the way every other branch of the Bureau does, as an impartial protector of you, the citizens of America. In just a moment, we will tell you about next week's exciting case from the files of your FBI. Friends, if you were impressed a few minutes ago by what I told you about the Equitable Society's Assured Home Ownership Plan, if the idea appeals to you of a low-interest rate first mortgage combined with life insurance to protect your home against death and hard times, then I suggest that you get in touch with your equitable representative soon. He'll show you exactly what this plan will do for you personally.  So contact your Equitable Society representative without delay. Or write care of this station to the Equitable Life Assurance Society of the United States. Next week we will dramatize another case from the files of the Federal Bureau of Investigation. The case that describes the callous operations of a hired assassin, its subject, parole violation. It's title, The Big Guy. The incidents used in tonight's Equitable Life Assurance Society's broadcast are adapted from the files of the Federal Bureau of Investigation. However, all names used are fictitious. And any similarity thereof to the names of persons living or dead is accidental. Tonight, the music was composed and conducted by Frederick Steiner. The author was Jerry Lewis. Your narrator was William Woodson and special agent Taylor was played by Stacey Harris. This is your FBI is a Jerry Divine production. This is Larry Keating speaking for the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community. And inviting you to tune in again next week at the same time when the Equitable Life Assurance Society will bring you another thrilling story from the files of the Federal Bureau of Investigation. The Big Guy on This Is Your FBI. This is ABC, the American Broadcasting Company.


Hey everyone, this is Dan with another episode of my videos on the Federal Reserve Banks. In this video, I will talk about the Fed Total Assets, QE, Quantitative Easing, and QT, Quantitative Tightening. Let's get into the details. The Fed or the Federal Reserve Banks are the central bank of the United States and they are certainly in charge of printing money. But in addition to printing money, the Fed has some other very important responsibilities. According to the mission statement on the Federal Reserve Banks website, it says the mission of the board is to foster the stability, integrity, and efficiency of the nation's monetary, financial, and payment systems so as to promote optimal macroeconomic performance. But that doesn't say much. The more telling information is really in the Fed's strategic goals. There are six stated strategic goals by the Fed. Number one, conduct monetary policy that promotes the achievement of the Federal Reserve statutory objectives of maximum employment and stable prices. Number two, promote a safe, sound, competitive, and accessible banking system and stable financial markets. And then there are four more additional strategic goals. I highlighted a few key words. They are maximum employment, stable prices, the banking system, and stable financial markets. Certainly if you invest in the stock market, you care about the stable financial markets as much as the Fed. But in addition, you need to know that the Fed has other strategic goals including maximum employment and stable prices. So what are Fed's assets? The Fed assets include Treasury securities that the Fed buys from the primary dealers. So who are the primary dealers? Here's a list of them. They're only about a couple of dozens of them. According to the Federal Reserve Bank's website, they are mostly the major banks. And then the Fed also has in its total assets mortgage-backed securities also purchased from the primary dealers. And then there are other assets including repurchase agreements or repo and discount window loans to banks. And then on the other side of the balance sheet, the Fed has the liabilities and that includes of course the money in circulation and the bank reserves on deposit with the Fed as well as reverse repurchase agreements. Now these are the Treasury securities that the Fed sells to the counterparties, which is the opposite of the Fed assets. What happens when the Fed buys assets? When the Fed buys assets, it receives Treasury securities or mortgage-backed securities from a primary dealer. And then in exchange, the Fed issues credit to the primary dealer. This is a graphical representation of the transaction. This is the Fed. This is the primary dealer. The Fed receives Treasury or mortgage-backed securities from the primary dealer and a Fed issue credit or money to the primary dealer. Of course, this is not paper money, it's an electronic form of money. When the Fed issues credit to the primary dealer and the dealer can turn around and loan the money to its customers or invest the money or credit in other instruments. Therefore, when the Fed buys assets, it's in effect printing money or creating money or adding liquidity to the overall market. If you like what you've seen so far, I'd like to encourage you to click the like, subscribe and notification button. Thank you very much. We will continue. Let's see how the Fed total assets have been increasing over time. If you look all the way back to 2004, you can see that we had back then less than $1 trillion of Fed total assets. And then the Fed went through several rounds of QEs or quantitative easing by adding more liquidity to the market or by purchasing more assets. The first round happened during 2008. That was during the great financial crisis. As you can see, the Fed assets doubled during that time from $1 trillion to $2 trillion. And then the Fed went through another round in 2010 as QE2, yet another round in 2012, QE3 and the last big round was QE4 that happened during the 2020 pandemic. In QE4, the Fed total assets went from about $4.5 trillion to $9 trillion, double again. As you can see, the Fed has added a lot of assets just in the last couple of years. In other words, the Fed has been adding a lot of liquidity to the market, a lot of money into the market. What's an added effect to the stock market? If you look at the two lines here, the orange line is the Fed assets, a double between 2017 and today. And the blue line is the ETF SPY representing the movement of the S&P 500 index, SPY almost double also during this period. So there's definitely a very strong correlation between having more total assets for the Fed and the stock market being higher. What's happening now is that the Fed will be going through the opposite of QE, it will be QT, quantitative tightening. From this chart, you can see that since after the pandemic, the Fed total assets had been increasing at the rate of $120 billion a month. But starting April of this year, it has flattened out. It has not increased anymore and actually it's been decreasing in the last two, three weeks. During the Fed's latest plan, in the months of June, July and August, the Fed total assets will be decreasing at the rate of $47.5 billion a month. It's starting to head down like this. And then starting September, it'll go down even faster. Starting September of this year, the Fed total assets will be decreasing at the rate of $95 billion a month. With QT, I expect the stock market to be dropping in the next few months. In addition to subscribing to my YouTube account, I'd also like to encourage you to subscribe to my Twitter account, which is DanMarketL. I share almost on a daily basis some of my trades or any important news development with my subscribers on Twitter. For example, on May 24th, I tweeted that I saw my SQQQ share at 2.6% gain because it looks like the market is rebounding. And then on May 25th, the following day, I said that because the GDP price index was 8%, higher than April 7.1%, I expected the May CPI, which will be posted on June 10th, to be higher than April's 8.3%. That means the Fed will be motivated to step up the rate hikes to tame inflation, which will make the market more bearish. And then on May 27th, I said I saw 2.3% of my UCO ETF shares, which I bought on May 19th, and I realized a 9.5% profit. If you like what you're seeing so far, I'd like to remind you again to click the like, subscribe, and notification button. And as usual, I very much appreciate your comments, questions, and suggestions. I'd like to remind you that I'm not a financial advisor. I share my analyses and stop trading strategies for educational and entertainment purposes only. If you want to buy or sell stocks, you should definitely make your own decisions, and you should consult with your financial advisors before you do so. This wraps up my video for now. I will chat with you again in the next few days. In the meanwhile, I'd like to wish you the very best of luck with your financial investments.