Good afternoon. Thank you for coming. If you are interested in storage in OpenStack, then you're in the right place, because we're talking about sender and Swift and how they work together. By way of introduction, my name is John Dickinson. And I'm the PTO for Swift. I work for a company called Swiftstack. And when we were putting this together, preparing for the summit, John and I were talking about just realizing there's a lot of confusion about how the storage projects inside of OpenStack work together. So we really wanted to clarify a lot of that. So my name is John Griffith, the other John. So I work at SolidFire. And I'm currently the PTO for the sender project. And that's the block storage side. So as John said, we wanted to get together and talk about how the two different storage platforms work together. And then also, there's a lot of confusion amongst a lot of people about what the differences are. So we're going to talk about that as well. So the reality is we need something new. And we all kind of know this, which is why we're here and looking for some sort of storage system. Applications have really changed recently and, I mean, recently in the past 10, 15 years or so. And we need to move beyond something that is just silos of data storage. And we need to be able to have the flexibility and the scale that's demanded by what applications are using today. So if you need to go beyond the capabilities of a single hard drive and you want to get beyond the pain points caused by large raid volumes, then the reality is you need something new. And we know that there are people writing new kinds of applications all over the world, building massive websites that are the larger scale than they've ever done before. We've got the proliferation of all these devices, mobile devices, laptops, all of this kind of stuff. And we also need to make sure that our infrastructure changes to meet that. And I think the fundamental promise of the cloud, one of them, is that you have the power to tailor your infrastructure exactly to your use case. We've seen this happen a lot with the compute side of the house, and I think we're also seeing that happen with the storage side of the house. And the basic idea here is you need something to abstract away your data apart from the media upon which it is actually stored. And that's the fundamental thing that I think that both Cinder and Swift bring. We have a system that is able to break that connection, which means that even if a particular piece of hardware fails, your data is still there. You're not intrinsically tied to what's going on. You know, you can think about in the past, people have always kind of assumed, you know, if you can drop it on your toe, it's a thing. And you know, if you've got these ideas, you put it on something that you can drop on your toe like stone tablets or books or something like this. And you know, think back a thousand years. Somebody wanted to kill an idea. What did they do? Well, they rode into town and they burned all the books. You destroy the media and then you have destroyed the data, the information, right? Well, what's really interesting now is that we're faced with a rapid proliferation of different types of media that they come and go, new protocols. You need to be able to swap those out and grow over time. So what we need is something fundamentally different than what traditional storage has been able to give us. And that's why we have systems like Cinder and Swift. And with that growth, the reality is that you have to solve this on distributed systems. Why? Because one storage system is not big enough to handle all of your storage needs. You're gonna run out of space if you put it on one hard drive or if you try to just keep it even in just one server. So you need something that goes bigger. So how do you do that? You have to put it on more than one system. Therefore you need something that's distributed. And in the distributed systems, there's a principle, it's called the CAP Theorem, stands for consistency and availability and partition tolerance. And what the CAP Theorem says is that you can choose two of these. So let's go over them very briefly.  So when the two pieces of your distributed system are trying to talk to one another, they still work when they can't talk to one another. The consistency is what happens if making sure that both of your systems are all of the pieces of your distributed system have the same view of the world. And availability means that it's always going to respond to requests when it gets them. So you can choose two things. You have to choose partition tolerance. So this puts you into two buckets. You can either have something that is eventually consistent and this is something that means that even when you have a hardware failure, the system is still going to be able to respond to your system. This is what we see a lot with object storage. And I gave a couple of other talks already this week about Swift and how that's put together and we'll cover it a little bit here as well. And then the other piece is you have an enforced, a strong consistency system. And this is what we're really used to as far as putting in boot devices for your servers or building databases and things like this. You need to make sure that you have strong consistent storage, generally used with like block storage to build out things that you can't change what's happening underneath them. So what you sacrifice in that sense is when half of your distributed system is unavailable, well then the whole system is unavailable sort of thing. So that's kind of where we fit into these two schemes. Swift is designed as being an eventually consistent system. Cinder is designed to provide you strongly consistent block storage for OpenStack Compute. So I want to go ahead and talk a little bit about Cinder and kind of give you a little more background, kind of talk about how it came to be, what it replaces, and how things work. Basically everything in OpenStack, basically we talk about this all the time and we think about it. It's basically a pool of resources, right? So it's no longer a stand up a disk array or stand up a server or stand up whatever this might be. It's okay, just provide a pool of resources for the end user to actually check out and utilize on their own. So the two important things here are these two first items on this list. We're talking about pools of resources and we're talking about self-service and that self-service is from an end user's perspective. The thing about Cinder, one of the biggest things is the whole idea as again with most of OpenStack is what we're doing is we're abstracting out all of the hardware and everything else that's behind that. So that pool of resources could be a completely homogenous set of different back-end devices and it doesn't matter because what we're doing is we're abstracting all of that and making it easier and simpler for the end user to use and for them to be able to use it and allocate it on their own. So this is kind of a quick comparison of sort of the traditional model versus say let's call it the OpenStack model in using Cinder. So you can see traditionally it was always you had some storage device that was actually dedicated to a specific server or maybe a specific user. For example, you had a server that was running a MySQL or an Oracle database. You had a certain storage device, block storage device with certain characteristics that you would deploy and set up and connect to that based on those needs and based on those requirements and what you needed there. The problem with that is what happens is you end up underutilizing capacity, right? Because what happens is you try and plan ahead, you try and build it for what you're going to need in the future and everything and it's pretty monolithic, it's pretty static, you set it all up and you're never really going to use it to its full potential. Either that or you go to the other end of the spectrum and you overutilize it and that's even worse because then you start to have performance issues and you have all kinds of things that you run into and you've got a serious heavy investment and heavy effort that you have to do to actually extend that or expand it or actually migrate it all off onto something, maybe a bigger device. So in the old days of disk arrays and things like that, that's the kind of thing that you had to worry about a lot. The other thing is when you start trying to do things like take a single backend device like a disk array in a traditional environment and share it across multiple users and multiple use cases, you start to run into all kinds of things in terms of your planning, how to deal with capacity, and most of all, as you get more and more workloads, trying to deal with performance, different applications, different workloads, they're going to have different performance requirements. And the other thing is some of those requirements or some of those workloads are actually going to take more performance away from your device than others and they may actually steal performance from other people that need them as well. So that creates a significant problem. And then one of the things I love to talk about all the time is the whole going back to the self-service thing, in the old days or in the old model, you had to go through and you had to actually do things like go through IT or go through a storage admin or go through a requisition process or whatever it might be. And you had to actually set things up in requests or do a purchase order or whatever it was to actually get this storage, have it set up by IT, have it configured, get access, and then have them set it up for you the way you want and hopefully everything comes out right, so on and so forth. Either that or you just get what they give you, either way. The bottom line is in that model, everything is very static, very monolithic, it's not flexible, and it's just kind of a pain. It's the bottom line. So what we try and do on the open stack side of things and in Cinder is we try and make all of this more agile, more flexible, and also we try and make it scalable. So what you talk about now is a pool of devices. Anybody can use them. We do scheduling inside of Cinder so that you can do things like say, hey, I need a volume that has these characteristics. I need storage with these particular characteristics and it can go out to your pool of resources and figure out how to allocate a volume or some storage on the correct device so that you actually get what you need. You don't get more than what you need, you don't get less than what you need. So that's kind of the idea. The architecture and the design is completely designed for multi-users, multi-user environments and multi-use cases. So like I was talking about before, how you have to worry about, I can't mix this workload with that workload on this device. So the idea is by using a pool of resources and being able to split that out and select differently, you can eliminate that problem. And then of course, you know, back to the self-service. That's probably the biggest thing is letting the application developers or wherever it might be, actually go ahead and make these provisioning requests and everything else on their own. So I wanted to talk a little bit about, you know, for those that aren't familiar, kind of how Cinder is made up and what some of the components are. So the idea, you know, most of the, if you look at this and if you're familiar with OpenStack or if you've been in other talks this week and seen some of this stuff, you'll notice that this looks really familiar, right? Because we kind of all try to follow a pretty similar design here. So you know, at the top level, we have an API. Basically all your requests come in, whether that's through the Python Cinder client, whether it's through the dashboard, horizon, whatever it might be, or curl requests, whatever. You know, you may write something on your own. So those requests come into the API and they get put out on the message bus. The default for that is RabbitMQ. Can we do that and send that out? It gets picked up by the scheduler service and the scheduler service will then go ahead and send it down as an RPC call to one of the volume services. So this is where I was talking about before. We have a pool of resources now instead of just a static monolithic device. You can have multiple backend devices all set up and configured inside of Cinder and the scheduler is gonna go ahead and figure out where to send that RPC call to get it to the right device. So that's the idea there. So one of the things that I've realized is a lot of people have never actually looked at this, right? From a user's perspective on the dashboard. So this is just a couple of screen captures here to show you what's available from the GUI, from the web interface for OpenStack. So this is pretty simple. This is the volumes page. You get just a summary of what volumes exist, what their status is, their size, availability zone, so on and so forth. You can see here we have what the type is and whether they're attached. So the whole idea of this storage from Cinder's perspective is we're actually creating storage that can be consumed by Nova and by compute instances and that consumption can either be by attaching them as additional storage block storage devices or actually attaching them and using them as the root partition for the boot device on the instance. So go to the next slide. So this is the create process. So you can see it's fairly simple. There's not a whole lot to it, right? We go through and we select a name, we give it a type or we give it a name and select a type, give it a size and then the option on the volume source, there's two different things you can do here. You can say, I just want a raw volume with no data on it without any information or anything like that. You can choose to make it an image and what that means it's gonna actually go out to glance and it's gonna download that image and make that volume bootable. So then you can now persistent instances. From Swift. From Swift, yes. So yeah, so then you have persistent instances, the whole ephemeral versus persistence. And then one of the other options is from volume. So the other thing that you can do is you can actually clone volumes inside of Cinder. So if you have a certain bootable image or written down to a volume already or you have a development environment, you have a database, whatever it is, and you wanna actually replicate it, you can actually go in and just say, okay, just clone that volume and give me all of that same information again. And then of course we also have snapshots. Oh, wait, sorry. Over here, these are some of the extra things that you can do with a volume and this is where things really start to diverge a little bit, right? Because when you look at the old way of doing things, trying to do things like extend a volume, that can be a little bit difficult on an old system. So we can let you do things like extend a volume. We can let you, if it's bootable, you can go ahead and launch it from here. So then you have an instance that's running on that volume inside of Nova. The edit attachments is if you have existing instances already up and running, you can go ahead from here and you can just attach it and you give it the mount point and attach it as a VDB file or whatever the path might be. And then of course we let you do snapshots. So the snapshots currently are tied to the parent volume. You can't delete the volume if you have a snapshot currently, which causes some people some heartache. But, and you also can't actually use the volume, the snapshot as if it were a volume. So it's sort of a backup device. The reality is what we use it for is a vehicle to get things done more efficiently. So a snapshot is typically very fast. You get a consistent copy and then you can do things like migrate or clone or duplicate or whatever you might wanna do. So to talk about some use cases, you know, most people are pretty familiar and have a pretty good idea, but typically what you're looking at with Cinder is the buzzwords to kind of keep you thinking here are when I need additional persistent capacity for an instance that I've built. So I have an instance in Nova. I've got my ephemeral disk and everything else, but now I wanna attach something else and put a whole bunch of data on it, right? So it's just like adding another drive into your instance. And you can do this dynamically on the fly. Add them, take them away, move them, attach them to another instance, whatever you wanna do. You can also use it of course, as I said, for the actual root storage. So you can put your root partition there and actually boot your instance off of it. Use it for file systems, databases, and you know, anywhere that you need a raw block device. And of course, like I said, you can attach multiple Cinder volumes to a single instance. Thanks, John. So if you've got to put a database someplace, you're gonna use Cinder Swift. Cinder, that's right, good. So just making sure you're paying attention in and awake and everything. So Cinder's really great for deploying your volumes and your block devices and making sure that those are dynamically attached to portable and snapshots and all those really kind of cool stuff that you really need directly attached to your compute. So why do we have Swift? If we've got all that kind of stuff, then why do we need Swift? Swift is still vitally important. And the reason is because you need to have application storage that is globally available. You need to be able to directly talk to your end user. You need the applications to be able to directly talk to the storage for that application assets. You want to be able to have that storage system offload some of those hard problems of storage. People who are deploying the IT, like the IT group, your sysad men who are out there building your storage clusters, like I said earlier, they're gonna want to have a lot of agility to be able to respond very quickly to the needs of their applications but also have shared storage across different applications. And then finally, and this is one of my little soapboxes that I like to talk about a lot and one of my reasons that I like OpenStack so much is that open systems matter. You need to have ownership of your data and you need to be able to know who and what is touching every part of your data from the hardware to the storage engine all the way to the client tool chain. And you can only do that with open systems and that's why we're here with OpenStack. So I wanted to talk about a couple of really cool use cases, just three of them just briefly here, thinking about maybe giving you a real world picture of where Swift is being used today. Pack 12 was something that I talked about a little earlier this morning and it's really kind of cool. They were using a traditional sand device for their application storage and they were running out of space but they still needed to have highly available storage because they needed to be able to access this all the time. And when they were running out of space, what they did is they decided to archive some of that to tape and then stick it on the shelf which makes it pretty much not available and they needed to solve both of these problems and so they built out their Swift cluster and they migrated their stuff from their archives and their sand to their Swift cluster and what that gives them is a lot of new power and flexibility in what they can do. So when the Pack 12 is doing video recording of 800 sporting events a year then they can actually respond very quickly to that and put, know that their storage is available but they can even take that old stuff and introduce new revenue models and things like that because it's now available instead of being gathering dust on a shelf someplace. So if you wanna go see some old football game or something like that then maybe it's possible now with available storage that you can just ask and they don't have to worry about getting a tape robot to plug it in the right place and all this kind of stuff. That's not a scalable model but something that already is storing it and highly available storage does allow you to do that. The next use case I wanna mention very briefly is something I just heard about this week which was really kind of cool and I've mentioned it to a few of you I know already this week. So when the Malaysia airline flight went down people were scouring the Indian Ocean for the plane and one of the things they were trying to do is figure out well if a plane crashed then where would the debris be? Well there's this site that's hosted in Australia and it's called adrift.org.au and they were discovered basically by a newspaper that the cool thing is you can go click on any point in the ocean and it just shows you what the dispersion pattern is for the next 10 years. Really kind of a cool thing. It's really fun to play with. But apparently a newspaper discovered it and then they got overwhelmed by request and they decided they had a couple of options. One, they could continue to build out their web server and just add more engine X nodes or something like that and that's kind of a traditional fine way to do things but it has extra operational cost and it's just a little more complex to build that system out. It turns out that their data was already stored in Swift and so what they were able to do is instead of having to build out their web servers just point the browsers directly at Swift and it automatically worked and boom their scaling problems are gone. And this is a really great story and I was when I first heard about it I said some stuff on Twitter about it and I got a response from one of the guys who ran it and he was saying that Swift has been a great way to help make our site scalable and so it was just really great affirmation. I love hearing that kind of story and I think it's something that's just about all of us can really make use of on almost an everyday basis. The last use case I want to show is kind of a little different one moving from the video streaming and active archiving sort of use case looking at something like web content and then this one from Fred Hurch Cancer Research they were speaking earlier today. They're in cancer and AIDS research and as part of that they have to do lots of gene sequencing and store massive, massive data sets and they need to be able to share that internally but they need to be able to have something that they own that is gonna last a long time but it gives them pretty relatively cheap storage across that much data and they were able to build out a Swift cluster and get really, really low price performance price points for that. There's some numbers earlier this week it's less than two cents a gig for their use case on their large scale storage which is really impressive. So how does Swift work? Well I wanted to point out something very important well I'll get to that in a second I'll get to the important part in just a second. So the first part, the first important part is let's talk about the API. All of the services in OpenStack use a REST based API and so that's a commonality between all of our stuff and in fact this week we're here talking and one of the conversations earlier today was how do we make sure we come together as a project and make really good unified decisions on that. This is what a URI looks like for Swift. You have an account to container and object and this is really just where you place your data throughout the system and an account keeps a list of containers a container keeps a list of objects and then the objects are where you actually store your data. So let's say I have an account on a Swift cluster and I want to create my images folder and then I want to upload cat.jpeg because the internet is for cat pictures. So if I upload a cat.jpeg then is that going to be is that going to be stored as an account, a container or an object? The object that's right. So this is where your data actually is and if you're storing, you know, cancer gene sequence, whatever, that's going to be some object someplace. This is what it looks like just to add a new object and to get an object back. Simple HTTP verbs and response code. So it's very easy to integrate into existing applications. It speaks the native language of the web so it works very, very well with existing web technologies like caching and CDN and browsers and things like that. And this is the important point that I really wanted to drive home and I think it's one of the biggest differences in something like Swift and something like sender. Swift implements an object storage engine. Swift is responsible for making sure your data is effectively stored across a large set of hard drives and does that and keeps them securely stored, durably stored and highly available. Swift is not a provisioning system for other object storage systems. You do not ask Swift to give you a pool of object storage with vendor object storage system X. That's not the way Swift works. Swift's purpose is to abstract away the storage volumes away from the application in such that you have your data and it is very durably stored, highly available. This is the design of Swift. This is how we implemented this object storage system. The client talks to what's called a proxy server. The proxy server implements most of the API and then passes that onto a, passes request onto the storage server. The storage servers are responsible for abstracting away those storage volumes. So in this case, if a client, let's say a web browser, we're trying to talk to a Swift cluster, does the web browser ever directly touch a hard drive? Yes or no? No, it does not. Because this purpose of Swift is to abstract away those hard drives so it never has to worry about it. This way hard drives can come and go intentionally or not and the system still remains available. And so the other purpose of the proxy server is to make sure that the storage nodes are, the responses there are correlated and the client gets the right response code back. So when we're writing out data, make sure it's durably persisted in several locations and then you can get that information back and the client knows as soon as it gets a response code that says this has been successfully written, it is available for you to use. It's not that it's going to write it later. That's not what eventual consistency means within Swift. What it means is it's going to be written right now. It just means that when you have something that is, when you have some failures, Swift will recover from that in the background. And so there's no single point of failure in this, in this design, there's no centralized message queue, there's no centralized database, there's no centralized index of metadata of location placement or anything like that. So it's a fully distributed system that really just continues to get better the bigger you add it out. And the last point I want to make about Swift here, I think it's the last point, is that it's optimized for massive concurrency across the entire dataset. So in the example of the adrift.org site, it is designed so that not one request is going to be as fast as possible, but it means that it can handle all of those requests pouring into it from all around the world. That's what Swift is really good at. Another use case I really like to talk about sometimes, and I mentioned it here at previous summits, is the fact that Wikipedia is using images stored in their own Swift cluster, because you can think about it, they need something that's going to be that massive concurrency across all of their articles. So I want to talk a little bit briefly about the data placement here within Swift and how we do this, because as an implementation of the object storage system, that's kind of an important piece to understand. So this is a little more technical info, but we use something that is called consistent hashing. It sounds like it's a complicated topic, but it is a lot that goes into it, but we're all really familiar with it. Imagine it's a set of encyclopedias. You know how to look up something in encyclopedia, you find what letter does it start with, then you go to that volume of the encyclopedia, and that's how it works. That's just a basic, simple hashing algorithm. If you want to get a little more complicated, then you can use what's called a hash function that evenly places things throughout this single, what's called a key space, and so you hash a value and you're given an output, and that output is just some really big number. Now the way that consistent hashing works is we call it a ring, because if you go to the biggest number you could possibly get and add one, well then you just loop back around to the beginning. So basic consistent hashing means that you hash something and it shows you some point on this ring. And for example, you can walk clockwise around the ring, find where that first node was, that first storage node, and then that is now responsible for dealing with that storage. We've optimized this a little bit inside of Swift to have a little bit better data placement because you want something that's a little more reliable and robust against failure. You don't want all of the copies of your data to be stored on the same hard drive. You need to be able to make sure that it is stored across different failure domains, drives, servers, racks of servers, even entire DCs. And so this is very important to understand so that when you are going to place a piece of data, let's say Swift is gonna store multiple copies of that data in the system and it chooses where to do that based on this principle that we call as unique as possible. What that means is that if you have more than one server, we're gonna make sure that it's stored across hard drives on those different servers. In fact, we're gonna make sure it's not even stored on the same hard drive, then it's not gonna be stored across different, the same server if you have more than one server. In this example here, if you have just two racks, it's gonna make sure it uses both of them. And if you're just in one region, naturally everything's gonna be there. But if it will use as much as you have available, in this way, it means that you can lose, for example, an entire rack or even an entire data center and still have available durable data. And this is something that I wanted to highlight a little bit, especially in relation to talking about Cinder and the other object storage, I'm sorry, the other storage systems inside of Swift. Sorry about that. OpenStack has several different pieces and components and some of them are storage and there's other ones as well. And so it's very important to talk about the extensibility points within Swift. So as John was talking about and hinted at, that Cinder is this provisioning layer for block storage that may call out to a particular storage implementation, a storage driver. And that's their primary way of being extensible is you're able to add in different implementations of block storage that you can then attach volumes to your virtual machines. Well, Swift has a couple of important places to implement extensibility. And two of them that I really wanna talk about are the middleware and the volume extension. And remember, this is the design we had about Swift. So let's break this in two. So if you take the front part, the communication between the client and the proxy server, there may be some API extensions you want to add into that. And so we can support middleware that will allow you to write your own custom code that you can run on the proxy server that for example could implement something like searching or transcoding a video or caching or something like that. And the other end, and this is where it gets really interesting I think, we've had a lot of active development lately to improve this, but on the backend, how does Swift actually talk to these hard drives? How does it talk to a storage volume? And we've seen a lot of improvements in the flexibility of the system within Swift. And today I can think of at least four places where we have different volume implementations for Swift. For example, we've got the default that we use, which is just a local POSIX file system. We recommend XFS, but you can use anything just about. We also have people out there, the Red Hat specifically has contributed to ensuring that Swift can run on top of Gluster volumes. We know that the zero VM team has been exploring the possibilities or the exciting opportunities around keeping compute and storage tied together. And they've implemented their own zero VM volume abstraction that allows them to execute code securely right next to the data. And then the fourth one is the, oh, you could think about, for example, some other abstractions that may include let's do encryption or let's do compression or something like that. So as it's passed down onto the storage volume, you could actually compress it and get a little more efficient storage. You can encrypt it for operational or procedural reasons. So that basically sums up the entire thing of what I wanted to talk about. And basically say that Cinder and Swift both have very important use cases with an open stack, work well together as far as the volume snapshotting, the backups, the loading from images through glance and things like that. And I hope that that helps you better understand where the two projects fit and why you would use one over the other. And to add to that, one of the things that hopefully makes sense now is you actually want both Swift and Cinder for the different use cases. And one of the things that I saved to the end for the better together part is the fact that one of the great things about Cinder and Swift and using the two of them is you can actually do backups of your volumes and Cinder to a Swift object store, which is an extremely great target for that. So, does anybody have any questions? Can you hear over the air conditioner? To get over the air. Although I'm glad it came on. Yes, I probably couldn't even hear you in the front row. Can you go to the microphone please? With Cinder, can you over provision or are the volumes out fully allocated when they're created? Yeah, so that's a really good question. And it depends on what backend driver you use. So the reference implementation for Cinder right now uses LVM. It has a built-in LVM driver. With the base default LVM driver right now today, you cannot over provision. However, you can actually configure the thin provision to LVM driver. And then of course, as the name would imply, there you go. Question over here? So my question was about Swift. I saw that you tried to geographically disperse files. So let's say you're starting small and you have one geographical location, say West. And then you've got a healthy Swift installation. Can you bring up another zone or geographical location and then basically bring everything that's over here in the background? Oh, this is a new thing, okay. Yes, absolutely. That is one of the design characteristics of Swift that we've been very keen on making sure it stays in the forefront with every piece of code that has contributed is that you've got to be able to manage capacity changes on an existing cluster. Also that includes, you know, we've got to be able to reboot with no client downtime or upgrade and things like that. So yes, in that sense, it is possible to wait each particular region or zone and then change that wait gradually and it will automatically rebalance things in a smooth way that won't overwhelm your network. This is a Cinder question. Can you take recurring incremental snapshots in Cinder? So you're going to have to be more specific with your definition. I have a feeling I know where you're going, but... Well, I mean, can you make the snapshot just take incremental changes since the last time you took a snapshot? Yeah, so with the reference driver LVM, it's just using LVM snapshots and so they are. So you're basically just creating a cal file and just doing that. So the thing about Cinder that's kind of interesting and that's significantly different about Swift, the focus on Cinder is abstracting out block storage devices on the back end, right? So depending on which abstraction you choose to use and what device you implement on the back end, that's why the question like, does it do over provisioning? Does it do... The question is always maybe and it depends, but the reference implementation in both of these cases, you can do that, yes. Thank you. I don't see anybody else at the microphone, but I think John and I will probably be up at the front just for a couple of minutes. Thank you very much for coming and have a great week. Thank you everyone.


The letter from yesterday I beg pardon miss but do you happen to have any material at all dealing with it if you please what's that will you please lower your voice but I and then you might read the sign over there or shall I read it for you absolute quiet required in this library my but you read beautifully but I wonder if you please lower your voice oh oh sure I mean oh sure I'll be more than happy to help you but you simply can't disturb the others here in the library I see well I'm terribly sorry excuse me everyone I didn't mean to disturb you please please be quiet good heavens ma'am I just wanted to apologize quite unnecessary now may I help you I hope you can I'm looking for some literature on hydrokinetics and don't suppose a Hick library like this would have anything like that though you're a stranger in Jackson City aren't you that's right how did you know I know most of the people in town and besides folks who live here never refer to the town is having a Hick library now look no offense intended but after all I don't expect too much from a two before place that probably doesn't have much more to offer than the encyclopedia and a couple of copies they're over boys you said you wish to see something on hydrokinetics that's right hydrokinetics is a branch of kinetics which relates to liquids you see kinetics is the branch of dynamics do you wish to read Kendall Johnson Abernathy or Sandin on the subject what what's that I said which author do you wish to consult those four seem to be the authorities but some engineers like Alexander and Bowen well look here are you serious serious about having books by Johnson and Kendall and Sandin and Abernathy on the theory of hydrokinetics will you follow me please yes certainly but turn on that light if you wish it's a little dark in here to do yes all right I think you'll find these quite up to date I'm sorry that one of the Alexander volumes is out but it should be back tomorrow quite all right it's Kendall I'm really after here we are this one that was printed sometime last year I believe yes yes it was a Kendall is propounding a new theory on hydraulics I read it when I was in New York I'm glad you didn't have to go back into the city to find what you want it no I hold look here I owe you another apology don't I know please don't bother oh but it's no bother you may use any of the tables over there yes but I'd like you'll find the one by the window quite good hmm sensitive cute too yeah darn cute yeah well yeah let's see Kendall says when an ounce of plain lubricating oil is introduced into hmm wonder what her name is first one I mean name played on the death says miss Marshall that's interesting miss Marshall oh well now as I remember reading about it three months ago Kendall says that if you introduce one ounce of common lubricating oil into a cylinder two inches in diameter and four inches in height pretty girl wonder why I can't get her off my mind wonder where she lives oh can't find it well then according to Kendall if an ultraviolet ray is permitted to cross the cylinder at the time pressure is applied to the top the result were one of what a good looking girl I curse doing in Jackson City she's smart too I just mentioned hydrokinetics she reeled off the four top authorities like she was a student on the subject I wonder what she's doing tonight well hang it all up I say miss Marshall oh I say miss Marshall yes would it be possible for me to check this book out I'm very sorry but I'm afraid not well it's really quite important I'm an inventor and I I'm just on the verge of a very important discovery I simply must have this book to you I'm sorry perhaps you should buy a copy I've tried that everywhere in town there's none I can get a hold of you could have one sent out from New York I can't wait that long I have to work on this thing while it's running through my head it's very important I might lose the whole idea by the time a copy came out of New York I'm sorry it's quite against the rules to permit anyone to take out a book without a library card well suppose I take a card how much oh there's no charge but you must have a property owner sign your application property owner application yes someone who can pay for the book in the event that it's lost and who's willing to personally guarantee your honesty must sign your application then your car will be ready within 48 hours all now look that's worse yet I'm sorry this isn't any way to treat a Jackson City guest you know I'd like to help you really I would would you really yes I would but I can't break the rule now wait a minute I've got it yes your place what your place your home or wherever you live you mean I mean you can take the book out yourself you take it home and I'll come by tonight and use it there that's not very clever mr. Mr. whoever you are Chase Adam Chase and not very original either well there aren't any new ideas at least give me credit for picking one that's not too bad are you serious about the book word of honor ma'am I need that book right now like anything seriously seriously then I I just might be able to help you would you really I might tell me can you take dictation a little good you can't help me that is if you'd like to I might I'll be glad to pay you well we'll see you'll do it you'll take the book home and let me study it there yes I'll take it home good what do you live you won't have any trouble finding me just ask anyone for Sicily Marshall did you say a Sicily Marshall yes what about it well nothing I just like it it it happens to be one of my favorite names what time tonight oh any time after 730 good how 732 you better go now we're beginning to stir up the folks who are trying to study yeah all right see you right now just a minute yes I've got to consult Kendall again hold on there a second do you really think this invention will prove itself well I'm not exactly an expert but the idea seemed sound wait a minute now let's see oh yes here find it how would you take this down mm-hmm Kendall volume one page 74 it has been my observation that hydraulic reaction often can be obtained through the use of a common water tumbler immersed in H2O that's water well confounded there I go again treating you like a child you probably know more about this entire subject than I do without my explaining chemical symbols don't you think we'd better call it a night oh it's early it's 1 a.m. no it couldn't be well it is though see no brother but I'm popular around this place from now on it's all right I've really enjoyed it mister you were serious there in the library yes rather I don't mind saying my complete future is probably tied up in this thing right now if it's what I think it's going to be I'm due to make a fortune out of it I hope you do well thanks and why oh I like to know people who are successful besides my father was an inventor was he really yes he was a brilliant man he had an invention I I never did quite understand what it was it was before he was married someone filed for the patents just a few hours before he did and he lost out someone stole his invention no no it was just a coincidence but my father was never the same after that something happened I don't know what I I remember hearing my family talk about it in whispers when I was just an infant is he still alive no no he's been gone three years oh I'm sorry he was a fine man grand but he never got over that whatever it was that happened to him long before I was born you you mean there was something more than just the loss of the invention patents yes something that was I think even more tragic I've never even been able to guess what it was maybe it's better than you don't know yes maybe so well really I should go it's late is there much more to do well yes I have to finish these papers before I can have the model of the invention built could I help you more would you I'd love to really tomorrow night can you wait that long well no I can't but I will there we are all finished good well now the models next how long do you think it'll take to build it well at least two weeks we've been on these papers longer than I thought we'd be almost 30 days I really don't know what I've done without you how I've enjoyed it oh we can relax now to the models bill then I'll have to go to Washington what time is it it's early nine o'clock good time enough to catch the last show that that is if you'd like to go out with me like to I can't think of anything I'd like better your train's leaving Adam I'll be back with those patents you will come back you'll try to stop me goodbye darling yes Adam will you marry me when I come back I said will you marry me when I come back to my diary January the 17th it has been five days since Adam went to Washington I'll never forget the unromantic but lovable way he asked me to marry him standing on the steps of the moving train shouting the question at me above the noise of the engine how I loved him at that moment I love him now but why why oh why hasn't he written five days and not a word from Adam yet I've been received ladies and gentlemen that the crack limited from Washington nearing Jackson City less than an hour ago was held up and robbed by unidentified gangsters the train was flagged down by two men who pretended their car had stalled on the track the engineer and fireman were shot and killed all passengers were held at gunpoint and the mail car was entered and robbed this train robbery will remind old timers of the historic and dramatic train robbery on almost the same spot some 50 years ago it'll be exact 53 years ago January the 17th there is no indication as to the identification of today's bandits I want to send this wire to Mr. Adam Chase Esther arms hotel Washington yes darling have not heard from you worried I love you this early hello yes operator this is the party calling Washington yes I'm calling Mr. Adam Chase that's right at the Esther arms hotel oh you have a hotel hello what's that checked out two weeks ago oh no thank you just cancel the call to my diary April the 17th it has been three months and five days since I last saw Adam Chase he promised to ride immediately from Washington three months ago seems to have dropped out of the world I can't locate him any place I've just returned from ten days in Washington searching yes come in Adam I had to come back oh darling darling what's wrong tell me what's wrong you look so ill so thin I guess I shouldn't be here since you didn't want me didn't want you didn't want you oh my darling what makes you say anything like that I wrote you up about the invention I didn't get your letter I haven't heard a word from you I told you what happened that I was ruined darling that if you loved me you'd come to Washington and we'd make it some way I didn't get it Adam I tell you I didn't get that letter I waited you didn't answer you didn't come you didn't want to come darling will you listen to me I didn't get that letter what what's actually I didn't get that letter you didn't get it no no I waited and waited I wired you phoned well I just got back from looking from one end of Washington to another for you oh my darling my darling I was too late just 24 hours too late Adam someone else someone from California had just filed for the patents to the same invention oh sweetheart I was just a few hours too late oh but the invention isn't everything I wrote to you I told you what happened I asked you to come to Washington to marry me I'd have come in a minute and I thought now the thousands of things I thought don't think of them anymore I had to come back I couldn't live without you I had to come back to see you just once more I couldn't live without you Adam we'll be married promise me we'll be married right away right away darling yes right away June 20th Adam and I've been married two months today we're very happy somehow there's something more than just our love for one another that makes us so close to each other I can't explain what it is we've rented a large house an old one but it's adorable and we're planning to yes dear all right Adam back among the rafters well what in the world is it well it's an old male sack full of mail what yeah look look here these letters none of them have ever been opened by Adam dozens of letters all sealed all stamped and dated look looks actually postmarks they're all the same January 17 1889 but how in the world did they get here in this attic I don't know I wanted to run a radio aerial out on the roof and I had to crawl way back in the rafters it was hidden back there up near the roof evidently been there for years but how did it get there 53 years ago 1889 look at these letters addressed to people all over the country Everett Holton Detroit Jessica Young New York Paul Reimer Chicago Mr. Mrs. FC a holiday Grady Pennsylvania and look here's one address to President Benjamin Harrison from someone in Maine wait a minute Adam look this letter addressed to Miss Cecily drew of Youngstown what the return address Mr. Aaron Marshall my father he wrote this I know the handwriting Cecily drew was my mother's maiden name Adam yes Cecily drew and she lived in Youngstown my father your mother open it open it I said open it oh how right what is it it was my father listen my darling Cecily I have bad news I have just learned that someone else has filed for the patent rights to my invention by some queer trick of fate another inventor had the same idea as I only he has been fortunate enough to get his application for patents into the Bureau ahead of me I fear all my work has been in vain all my sacrifice useless I have nothing to offer you now my dear but my love if you still love me hurry here to marry me I shall surely never exist if you don't all my undying love he wrote that your father to my mother Adam the train robbery what I remember hearing about it on the radio the train your letter to me was on was robbed the mail was stolen and the same thing happened 53 years ago to your mother and my father only she believed he failed to come back to her and he died never knowing she hadn't read his letter and his letter has been here hidden all these long years your mother my father you have heard the letter from yesterday tonight's original tale of dark fantasy by Scott Bishop originating in the studios of WKY this is Tom Paxton reminding you to buy United States war bonds and stamps dark fantasy comes to you each Friday night from Oklahoma City this is the national broadcasting company


Hey everybody, welcome back to Magic Orthodoxy. My name is David and this is a deck review. Hey, today we're going to look at the inversion deck from Paul Harris. What is the inversion deck? Basically, it's an inside out deck. It is a box that looks like a deck and a deck that looks like a box. Huh? Exactly. That's what this is. It's an inversion deck. The deck, I got mine from PigletMagic.com. I've never seen anything on the box. It actually says that it is from Paul Harris. I heard that he designed it. So kind of like other Paul Harris things, it's just kind of like another addition of weirdness or astonishment that you could add to something. I don't know that it's meant specifically for a trick. I did some research out there, tried to find if anybody was using this in a magic trick or knew of something that maybe it was tied to, didn't see anything out there. So it is what it is. The tuck box looks like a deck of cards. The front of the tuck case looks like the back of a deck of Riderback 808s. The sides actually have a great outline so that it looks like a stack of cards as does the top, as does the bottom, but it's kind of given away by the folds there. The back of the tuck case is the standard King of Hearts and you have a regular tuck flap with nothing on it and no tuck seal. And that is pretty much it for the tuck case. Let's take a look at these cards. So if the box looks like the cards, then the cards look like the box. So this is what the deck looks like and as you can see, it kind of resembles a card box if I hold it completely right, although there's no writing on the sides. So what you're getting with this is you're getting an entire deck of cards that are the face of a standard deck of Riderback 808s.  That's what you're getting. Now the faces, they're all just going to be standard US PCC playing cards, standard pips, standard courts, standard layout. Everything is going to be standard, standard, standard. With this deck, you're going to get a couple of extras.  So standard jokers. You're going to get a blank card that has a deck face on the other side and you're going to get a deck face card that has a standard US PCC back. Everything else, like I said, is the back design of the front design of the tuck case and the faces are completely standard. So that looks like something that you'd be interested in. If that looks like something fun, probably I would recommend this to people that just collect playing cards that like something interesting or video magic that has a lot of humor to it. I think that would be a neat shocker for your spectators to see this, you know, deck go in. Maybe you could do it in a change bag.   I know that I have many gaff decks that come with these cards that is to resemble the face of a deck of cards. And so this would, if you use this gaff, then getting the inversion deck would give you 52 of those gaffs depending on what you use it for. So that's always an option as well. Like I said, I got mine at penguinmagic.com. All right, so that is it for this deck review of the inversion deck from Paul Harris. As always, we recommend that you like this video just so other people can find it faster. We also recommend that you subscribe to this channel just to stay up to date on the latest in cards and card magic. Now, if you want to follow me on social media, you can. I'm at facebook.com, slash magicorthodoxy, twitter.com, slash magic orthodoxy and instagram.com slash magic orthodoxy. Thanks. Bye.


We popped the door, but we're good. Oh, that's not good. Oh, we've lost all our stuff. It's okay. I think it hurt the car. Hello, everybody. I'm the Revit. It's been a minute since we've been on BMNG and they got some new challenges. Of course, they're probably going to frustrate me. The Gambler 500. So let's get to it. Make sure you guys follow me on all social media. I'll just find the description box below. Let's go. Now, when I say it's going to frustrate me, these challenges always tend to frustrate me because I tend to not easily complete that. But we're going to try. I can already tell you that this is going to be a headache. This car does not want to turn. Oh, we got a handbrake though. That's a wall. Oh, no. No. Get the checkpoint. Okay, we're not doing too, too bad yet. But I'm feeling this is going to be very dangerous at some point in this course. Oh, boy. Like right here. I don't know why I'm pushing the clutch when I pull the handbrake because this is an automatic car. Oh, we're getting it now. Oh, I feel like we were. Oh, I see that. We had ourselves off-road. We got this. Oh, boy. Don't blow a tire, wreck the car. Anything like that. Nice PVC snorkel on this car though. Some really crazy rally, but you know where? Well, we popped the door, but we're good. Oh, that's not good. Oh, we've lost all our stuff. It's okay. It hurt the car. We should be able to complete this. I hope. We got to do two laps. We have 18 jerk points on each lap. Oh, yeah, this is not going to work out too well. Oh, just we're good. Oh, my. This is definitely not easy. It kind of hurts my wrist, but we got this. Picking up some speed, brake. Oh, B-Men G is definitely so much fun. Definitely need to get more drift mods and stuff. But these challenges are fun. Don't break the car. We've damaged it like the body and stuff, but we haven't really hurt anything detrimental to the car. Okay. So we got to remember that checkpoint right before the end is a 90 degree turn. I feel like that's where a lot of people end up getting screwed up. We got to complete one lap. Now that we kind of know where we're going, got a little bit of speed built up. We might be able to beat the five minute or the six minute challenge. Need a less nutty break though. I've never tried this challenge. And this is the first time I'm trying this. And I'm quite shocked that we're doing as well as we are. And it said this was difficult, very hard. Probably to complete it within the time frame, maybe. I'm just worried about not dying and picking up some time. Looks like we're picking up some seconds. Nine seconds faster than our previous. As long as we can pick up some time. It's on the wrist on the snap. We should possibly be able to complete this challenge with a metal or a wood token or whatever it is they want to give us. So we went flying last time. Lost all our stuff. Hopefully we don't need that gas. Because if we do, we're screwed. Oh man. We're hauling now. Got 11 seconds up. Got to remember going into the little shortcut. That was risky. Remember going into checkpoint 17. That's a really hard. Oh no, don't blow a tire. Oh, I don't like those sounds. Those are very bad sounds. Oh, we got this. We're golden, maybe. Oh, as I say that, stay on the road. I'm terrifying myself right now. We almost biffed it last time. It picked up some time there. We didn't have to come to a dead stop. We're 17 seconds ahead. A lot out to the finish. Let's go. So we completed it in not fast enough. We were 7 seconds too slow. Oh man, that was rough. That was a bit of a rough one. But let's see what other we have a Z. It put us in our Z. Well, which means there's no feedback. So let's try one more challenge. Another one of these gambler challenges. Liter Liberation. Liter Liberator. We're going to load into that one. And we're going to try this one. We're going to be doing a lot more on beam. Like I said, another episode prior. We got the PC fully running. We're going to be doing a lot of fun stuff. More exciting things to come. Big things to come with Moza and everything as well. Because we're loading it. So we're going to see if we can't complete this challenge. Oh my. So what do we have to do? Destroy all this, clean up. Required amount within 4 minutes. I'm not entirely sure. We just have to hit it. Oh, I mean, does that count if we just run into it? I don't know the actual challenge. Does it count if we get rid of it? Oh, I don't think it does. What do we have to do? I'm a little confused. We're just reversing this thing. There it is. Oh! I don't recommend doing this. With a DD wheel. What do you have to do? Stop on it? I'm not entirely sure. If you guys know how to do this, let me know. Because I'm kind of confused on what you have to do. I don't think that's right. I think that's what I'm doing here for this episode. Here on B-Men G. Take a look at some of the new challenges. We're going to be doing a lot more of these. We're just going to go full set. So make sure you follow me on all social media. All that's found in the description box below. This is going to hurt. As always, thank you guys for coming back and watching. I'm EvilRabbit. See you guys on the track.


An L-shaped recovery is not an anomaly, it is the norm. By Daniel Lacalle, an audio-mesis wire narrated by Million Quinteros. Many analysts and economists are trying to predict the shape of the economic recovery post-COVID-19. To understand how the recovery may look, we need to look at past recoveries and at the history of pandemics. Starting with the pandemic, we know a few things. First, there has never been a vaccine for any of the previous 18 COVID types. Second, there has never been a pandemic without a second wave before a treatment existed. Taking both things into account, many investors' idea that the worst is discounted may be over-optimistic. If we look at the past three decades of recoveries after a crisis, we can see that the last three recoveries have been weaker, with less productivity, a lower rise in real wages, and poorer investment growth than the previous three. We may even say that the recovery from the 2008 crisis was already clear evidence of an L-shaped bounce, where some economic areas such as the Eurozone did not see something resembling a full recovery until 2016. In the case of the United States, the weak labor force participation rate and stale real wage growth with poor investment growth were a constant problem until 2017. The signs of an L-shaped return to normal post-COVID-19 are starting to appear. In China, most sections are posting disappointing levels of return to normality, and if we exclude those sectors, like cement, that are driven by government building and state-owned enterprises producing to build inventories, the recovery is clearly very far away from V-shaped. It is true that this crisis is different from the previous ones. This is a supply shock followed by the forced shutdown of an economy by government decree. However, this is precisely what makes the recovery more challenging. In previous crises, even in the downturn, there were sectors that were doing well and growing at double-digit rates. The crisis has hit almost every sector and generated a level of unemployment that is unprecedented in recent history. Such a massive increase in unemployment in so little time makes the recovery more difficult because the shock to consumers has been enormous and most may not decide to return to the previous levels of spending even if their jobs come back. If this crisis has told us anything, it's that even the most bearish have been too optimistic. Shutting down an economy even for an apparently short period of time has massive long-term implications in solvency ratios that will not be addressed with liquidity. Businesses are collapsing at record pace and even the largest and safest multinationals will see their debt levels soar only due to the fallen profits. JP Morgan estimates that 2021 will still show a level of corporate profits that will likely be 20% below the 2019 level. This challenges the V-shaped recovery and bullish arguments about most stocks but also proves that even investment banks who always provide reasonably optimistic estimates are pushing back the recovery to 2022 looking at a benign scenario. Jerome Powell has also signaled that the U.S. recovery will not start until the end of 2021 and if we have learned anything from the Federal Reserve it's that their estimates like those of investment banks tend to be diplomatic and generally optimistic. Investors cannot assume that Fed and investment bank predictions are too negative because history proves the opposite is true. In a recent email to clients Deutsche Bank mentioned that it takes around 22 days to shut down an economy almost entirely and between 4 and 10 times that time to get it back on track. Considering that 75% of job losses have come from the service sector being travel and leisure, education, health and professional services it is also safe to assume that the job recovery will be very slow because of the number of businesses lost and consumers weak response in returning to activity as wages are unlikely to rise and households will likely try to save as much as they can to prepare themselves for another shock. Central banks cannot print jobs the biggest problem in this crisis is that the massive stimuli are driven to incentivize a demand that may not come back and as such generate further overcapacity in indebted and over invested sectors. Central banks and governments are bailing out the past and letting the future die. The massive bailout of indebted sectors that already had overcapacity and were in process of obsolete may also drive the largest wave of malinvestment in decades. If the previous recoveries came with poor wage and capital expenditure growth and high debt the next one will likely be even worse. Recent history tells us that L shaped recoveries are not an anomaly but the norm. This one may not be different. For more content like this visit Mises.org


and the Whistler and I know many things for I walk by night I know many strange tales hidden in the hearts of men and women who have stepped into the shadow yes I know the nameless terrors of which they dare not speak tonight transcribe that's the whistler's strange story whirlpool he wasn't sure when it began it was too much like walking in the middle of a nightmare and then remaining in living in the shipwreck the confusion was all there again coming back to us but slowly hazy and there was a strange buzzing in his ears pressure the sound of the scene world then gradually out of the world voice and then thankfully at first the poison growing coming closer and closer it'll be all right captain it's the shot was exhausted easy son easy we got his name doc it's Hastings Stephen Hastings oh good mr. Hastings you're all right it's over we pulled you out pretty bad shape isn't it worst of any we picked up do anything about the others the Khalifa just radioed she took on most of them come on I thought he was going through it all over is better though he's coming around Hastings mr.  Hastings just come in oh no I haven't any darling darling you're so tight for yourself so terrible water won't cruise being my idea hasn't been much of a pleasure to have a day huh doc yes mr. and you could you leave us alone a minute surely I want to want to be with my wife I certainly captain will wait on tell me what it's all about darling you shouldn't try to talk about I can talk to you they fished me out I'm okay you see I'm okay of course no and the name of South like this or in full dress so it's south Marty South that's fine and you are mrs.  Hastings to pick it up any mr. Hastings will do crazy begin with how can you pass me off as your husband here on board there are quite a few survivors I've heard nobody knew him he stayed in his cabin half the voyage the others were picked up by the Khalifa we'll see him in Singapore now the Khalifa is heading the other way for the United States and we didn't know a soul in Singapore where does this money come from from an old friend in Shanghai EJ Galloway a former business partner my husband you see EJ made a mistake once a business deal in Singapore and I found out about it I told Stephen what to ask for he did he got the results shake down a nice guy your husband was a matter of fact weak at all terribly weak you know he almost got sick to his stomach sometimes just thinking about it about blackmailing his old friends and why to go ahead with it you like me why now you don't mean I can be quite appealing maybe the guys like Stephen Hastings but not the guys like Marty South get out of here that's all for any time we'll see if you get lonesome for me darling even just that's all Marty and then she's gone leaving you to rest and think and think some more for reasons you can't explain to yourself you don't say anything about not being your husband Stephen Hastings do you and then half a day out of Singapore you can't stand it anymore you call the doctor then for here you're sitting up how wonderful but you want to know what I've decided and now you like money Marty you know I think you like me look I know what I'm going into it includes you only because you are necessary part of the deal I'm very necessary darling so is having a husband Stephen okay I'll keep him alive for a while I knew you would but get this straight baby your husband made a big mistake when he fell in love with you I'm not gonna make that mistake I think we'll get along fine together just fine in just a minute the whistler will continue tonight's story all of us are proud of our hometowns and rightly so in this brief moment before we continue with our program we'd like to offer a salute to one of our hometowns in America New York City hometown to more people than any other in the world its history is pretty well known how it was supposedly bought for $24 worth of trinkets from the Indians how it started under the Dutch went to the British and passed to the young United States after the Revolutionary War it was our national capital for five years and George Washington was inaugurated there today it's not only the biggest but probably the busiest and noisiest place in the world much of its growth and prosperity is due to New York Harbor the port clears more than 5,000 vessels a year and ships almost half of the entire trade of the United States but New York City is many things to many people it's not just San Francisco multiplied by 10 or Chicago multiplied by three it's Wall Street and Harlem the Statue of Liberty and Greenwich Village it's Broadway otherwise known as the main stem or the Great White Way more theaters are crowded in that area than any place in the world it's the Empire State Building the world's tallest structure it's a parade up Fifth Avenue and a baseball game between the New York Yankees and the Brooklyn Dodgers it's the Metropolitan Opera and Madison Square Garden it's Rockefeller Center occupying 12 acres and 15 buildings and it's the headquarters of the United Nations it's the native New Yorker who never moves off his block and the immigrant who came from halfway around the world it's the George Washington Bridge and the Holland Tunnel and Grant's tomb and when you've said all this you've still only scraped the surface of what New York is like what it's all about but one thing is for sure the people of New York are proud of their hometown and proud of the part it has played in the building of America and now back to the whistler you made a decision didn't you money about to steal and the money waiting for Steven Hastings in Singapore perhaps it was the suddenness with which Lucille Hastings thrust opportunity into your hands by asking you to pose as her dead husband but there's another thing you've decided on you're not going to fall in love with Lucille because that doesn't fit in with your plan at all the next night in Singapore the two of you move easily around the dance floor of the Fort Plaza Hotel seemingly just to devote a married couple Mr. and Mrs. Steven. You dance well there. Steven's improved very much and the poor guy was tired he had a right to me. I think we should stop talking about that. So it's me let's talk about when we go to work. I think the best way to go to go there when. The first thing where I go I have to look at each letter again. I think it's a little Taylor shop in Ponderosa State. Why wait to learn. I just think it's. What do I do that. Just have your coat. You can wait for it if you want to tell me Mr. Hastings what if they want proof then they can call the hotel and ask me to have. All right not until I have my coat pressed. Good morning sir I want to get this coat pressed I'll wait. Names Hastings. Oh yes and you're staying Fort Plaza why nothing Mr. Hastings just curious if you're going to call or anything my wife isn't there she stepped out no no Mr. Hastings as the coat please I'll have it for you right away. You watch the proprietor of the little Taylor shop as he takes your coat and moves off toward the back of the establishment you look around nervously ready to run for it if anything goes wrong but nothing does mark he's back in a matter of minutes handing the newly pressed code across the counter you pay him and slip it on feel the bulge of a heavy envelope in the inside pocket.  You don't have to knock my own husband the neighbors like inside.  Are you going to tell me what's going on when you calm down you might tell me I went to the Taylor shop like you said they give you the money that's not the beef Lucille I'm talking about the guy who picked me up on the way out one of your pals high powered insurance policy not making sense darling if somebody followed you it's because you went Singapore they out of alley darling rough neighborhood this is a big city. I wish I could buy that you can buy anything Mr Hastings how much did you get twenty thousand here it's in the end. I thought we agreed on Wednesday. I'll forgive you. No you won't I'll try. What are you thinking something pretty foolish but sometimes you would really like to level.  Here I go. My back's against the door anyway. You do that it's not the key to not talk about. About now. Right now. Only admit it tomorrow it could be a knife in my back all right that's what you want me to say right now. Your mind is spinning as you leave her money you're afraid aren't you because the one thing you've tried to guard against is happening slowly and surely you're falling in love with it and you know what it can mean walk alone through the streets of Singapore you catch sight of him again the man she's had following you you hurry forward turn into an alley and stop wait what are you what I'll take it easy Mr Hastings I guess just one of the talk of the walk what over for our deal I thought maybe you'd change your mind the way you've been acting before in me of course this is sort of a crazy setup I thought you're going to meet me when you got in last week introduce yourself set it all up after all I've been getting things second hand I think you better keep talking Mr Gray's good enough and Mr Gray it might be I don't blame you for being careful Mr Hastings screwy deal like this but how's this sound here you take your wife to the Red Angel Cafe tomorrow night just cash like see you have dinner with her the last one then stroll out on the terrace terrace yeah nobody out there much just give me a chance to get lined up and then light her cigarette the match will give me a target an easy one it hit you suddenly Stephen Hastings the weakling the coward who loved Lucille so much that he'd blackmail a lifelong friend he really didn't want to leave that cabin didn't know Marty because he'd set up a plan to kill her at the end of the voyage a plan that he was too weak to go through with perfect isn't it you can get rid of Lucille tomorrow night and the following morning drop around to the tailor shop pick up the rest of the money and leave town but you're not sure are you Marty not sure that this is the way you want it to be what's the matter Mr Hastings you haven't changed your mind change my mind like a little more time to think it over I've been doing some traveling I want my five thousand bucks for days five thousand okay you'll get it you want to leave it in your hotel box small new bills cash Mr Grave the money's there tomorrow night you'll see us my wife and me at the Red Angel Cafe on the terrace yeah I'm too light her cigarette I know about this place right angel could somebody mention it like very much and I like you for bringing me Lucille hi you want to talk come on where we're going on the terrace but okay you can see the lights from the harbor beautiful yeah Marty you're going to tell me something inside yeah I was I think I know what it is you know Marty you're not like Steven at all you're anything but weak except when it comes to putting this sort of thing in the woods give me a cigarette I said give me a cigarette anything wrong with that I know nothing wrong thank you darling you know just the way you're looking now tells me something you do love me don't you yeah I guess I do give me a life like okay you're beautiful something I'll never forget thank you how the term midshipman originated in the early days of the Navy crews included nine and ten year old boys whose primary duty was to carry orders from the officers to the crewmen but since the crew was ported in the folksel and the officers aft the answers were forced across a midship several times a day thus the term midshipman today midshipman is the name given to the officer candidates attending the Naval Academy at Annapolis this is but one of many interesting facts which can be found in the history of your United States Navy in the police station in Singapore the arresting officers huddle around a man sitting under the glaring white light come on great we know you did it you've been followed since you asked for that money in Hastings Hotel Mr. Hastings gave me the money left that for me what was it for the killing great you were seen firing the gun all right I did it but it was a plan Hastings he was tired of his wife he must have been tired of everything but he was a weakling suicides been on his mind for months only he didn't have the nerve suicide but why kill her I think maybe it was because of some deal she talked him into he didn't want to leave her around so that she could follow through with it that's why Stephen Hastings set this thing up so they'd die together don't be half right use you suffer for example how many years ago would you say the first helicopter was invented 227 no that's only half right brush up on your aviation tell your eye and e-officer you want to study with the United States Armed Forces Institute you suffer it's easy it's simple if you don't want to be half right you use you suffer featured in tonight's transcribed story were Bill Foreman as the whistler Whitfield Connor Georgia Ellis Marvin Miller Lawrence Dobkin and her Butterfield the whistler directed by Gordon T Hughes with music by Wilbur Hatch is written and produced by Joel Malone and transmitted overseas by the Armed Forces radio service the whistler was entirely fictional and all characters portrayed on the whistler are also fictional any similarities of names or resemblances to persons living or dead is purely coincidental this is George Walsh speaking and reminding you to listen again next week for another strange tale by the whistler