Hello, my name is Todd Montgomery some of you know me So I won't go into you know who I am, but I will talk to you about what Aaron is so Aaron is a open-source project started around 2014 And sponsored by the CME to design and build a high-performance low latency Messaging transport in other words communication you and with the intention to be used within trading organizations In the front office. So exchanges Bicyde traders anything you can think of with that low latency requirement Aaron archive came along also sponsored by the CME and it is to Record and replay streams of Aaron data and In Aaron cluster, which was sponsored by our friends at adaptive, which I happen to be a part of it and And that is to build a raft cluster Framework on top of Aaron archive and Aaron as well with the same goals of low latency you know high availability and You know and high throughput So we have a lot of customers who depend on us We're now able to actually show some of them now a little bit more publicly just flash the logos up a little bit This is really neat Especially, you know, if you have an open-source project that started, you know And people didn't want to admit they use you now some of them start to actually acknowledge that we exist and they use us Which is nice But really what we wanted to talk about here is some of the challenges of moving front office systems so that they're 24-7 availability and One of the questions you may have and a lot of people do have is what's so hard about 24-7 if you're talking to like consumer You know websites and things like that. What's so hard about 24-7? They have to be available 24-7 in any way. It's a little bit different when you start to think about it In the in the instance of low latency high throughput very demanding systems So there's nothing really hard about it except when you start to look at the SLAs that are very aggressive That must be met not only contractually, but sometimes regulatory, right? So you have to be available You have components that need to be upgraded. You can't just take the system down to upgrade it It's one of the advantages of running, you know When you have dedicated downtime you can upgrade the system, you know, and that's going to happen when you don't How do you know when to upgrade? Well, the answer is you should be able to upgrade at any time you need to right? but you can't do that and You know continue to meet your SLAs, can you? Actually you can if you think about it and Transaction to be processed in real time. It's a little different when you don't have transactions that have to be processed in real time So the not all systems that run 24-7 are exactly the same so It isn't hard, but it is hard in certain situations So the things that really matter to this are the fault tolerance model that's in use The how disaster recovery is handled and how you can sort of lean on it as well as how you do things like upgrading your production So first fault tolerance, I'll take you on a little journey about how Fault tolerance kind of evolves and has evolved so let's say you have a service you have a client connecting to that service that's running on some machine and You want to make this fault tolerant your service can be restarted I mean it means someone going in and actually restarting it by hand It could mean someone goes and pushes the power button, you know because they get it got turned off Right there are all kinds of things the idea being the first thing you may do to make this highly available is to put it on the cloud Now how does this make it highly available? Well now when you have cloud infrastructure you do have the ability to do all kinds of different things like move it Right, it's a little different than moving it when it's on-prem This is a form of fault tolerance But it gets more complicated as you start to think about your service and start to add different types of Fault tolerance to it you may have multiple services and you can go to any of them You may have more clients and how do they know which ones to go to these are all solved problems We have many different ways to solve them But essentially the problem that we're really trying to fix is the state Problem it's the fault tolerance of state. It's that state in the services that Starts to become the thing that we want to make highly available Most of the time a lot of systems just kick the can down the road What they do is they basically have a state storage somewhere else. They have a database or something else Again, it's a way of doing fault tolerance, right? It's not my problem now It's now a vendor's problem because I'm going to Oracle. I'm relying on Oracle now to set to have this problem But you notice that the same problem exists. It's just now moved, right? That might be good enough So it really is this state in the fault tolerance of state that really kind of matters and when you start to look at this there is a Continuum between partitioning that state and replicating that state if you have the state in one place No, what's the old adage on if you have it in one place you have it in none, right? The idea being if you lose one It's not good enough Regulatory wise you may have requirements that indicate that require that you have this state in multiple places As well as just wanting to have it in multiple places so We do have methods of doing this, but I'm going to talk about one specific method of Visualizing this for for development and for the way that Eric cluster works And that's the idea of a continuous log with snapshot and replay The the thing that is actually being replicated is a log of events those events then are processed in order and They then generate states and So and you can at some point snapshot that state and replay that state To sort of give an example. Here's just a sequence of messages It could be anything could be new order ad It could be cancel modify something like that. It's very easy to think of it from the trading side And that has an associated set of state along with it that gets incrementally kind of Continues on right it kind of gets added to as it goes along If you were to look at any of these events you could take a snapshot of that state at that at that time That snapshot is just a roll up of those the the effects of all the state changes you could then Kind of look at it as if I were to take that snapshot Be able to rehydrate it and then replay the log five and six after it Those two sides should actually be the same right? I should have the exact same state You can do that with many systems that do this basic idea What this allows you then is a way to think about this instead of it being your snapshot of a state within a Within a database it's just a log with snapshots and replay in fact most databases work this way They have you know this that they have a log they do this Essentially this with some additional things attached to it as well But if you take this step further so we've really just talked about how the application might look at a Stream of these events and actually state change and looking at holding that state But there's a reason why we're talking about this. We want to actually have multiple clusters of These services with local log archives Okay, so those look the log is replicated across them and those services are running and they're consuming that same log Now each of those should have the exact same state in fact They should and they do that's deterministic execution that log will always generate the same state When you have that deterministic execution now all those replicas should be in in the same state This idea of replicated state machines has been around for quite some time It is a simplification that allows you to build systems that are very highly available So there's a couple things here each replicated service needs to be reading from the same event log obviously and They have to have the same input ordering if the input ordering varies between them That's not going to work right you have to have the same input ordering That's the set the same log and you're locally replicating the log Okay, so there is no central place where the log is stored this the log is replicated at all the different nodes of the cluster Snapshots and are really checkpoints their events in the log and they roll up previous log events or the state changes for those events so One question that you kind of come up to first is okay I'm reading from this log, but there might be different spots that each service is reading from this log How do I know when I can process a message? What happens if only one processes a message and then it's the only one to have it? Well, we don't want that There's a couple different types of consensus algorithms Paxos was one of the first but They even go back further than that into the late 80s early 90s work was on even that being done in the 70s on Kind of they didn't call a consensus at the time, but they had the same building blocks RAF consensus is an idea that is very simple to distill it basically means that The event must be recorded at a majority of replicas before being consumed by any replica This is the consensus part so you can't just get a message and process it immediately You have to wait until that message is Locally replicated to at least in a node of three one other so you have it and another has it So that's the basic idea of something like you know Aaron cluster It's also the the you know other wrap differentations that are sort of taking the same technique They're looking at that log. They have the concept of snapshots. All those snapshots are an optimization And it is the idea that you use this so that each of these are in you know Without being intentionally making them in lockstep. They are in lockstep because they're actually replicate, you know reading from the same replicated law But it has some things that make it nice for 24-7 and they may have some things that make it bad for 24-7 The first thing we'll talk about is disaster recovery so when you're talking about recovering from a disaster and When I I'm using this term really kind of pretty loosely the idea for disaster recovery is not that you lost like a whole data Center, it's like maybe you lost, you know one member of that of a three node cluster Let's let's even consider that to be a mini disaster The metric that we really are concerned with in most of you know When you have tight SLAs is going to be a recovery time objective in other words How long does it take before you can get back into operation and continue operating and you want that to be low? And you want that to be low in all cases of disaster recovery that would be the ideal, right? Lose a whole data center lose all three members of the cluster You still like to be able to in disaster recovery bring that up within seconds ideally, right? So how does this look when you start taking into account the idea of disaster recovery? Well, the first thing is remember that snapshots, you know could be lazily disseminated the idea being that when a snapshot is taken It's really an optimization. You could still just use the log, right? And it's because it's an event log you could lazily disseminate these to the other members Or to dr, and you could strain the log as it reaches consensus to dr So, you know as you take snapshots you would a new snapshot comes along It could be lazily disseminated if you had a failure before that you could use the previous snapshot until you know You get the the the snapshot disseminated But this brings up an interesting point you could run this in a cold scenario where the What the where this data is being stored in disaster recovery is simply just You know cold there's no, you know, it's not running hot. It's just storing the snapshots. It's just storing the log Or you could even be really cold and put it in like s3 or something, right? So it could be you know, even even in that kind of scenario. It's very cold or it could be kind of warm In other words, you have service logic that's running on that log and it's setting there ready to take over in case it needs to So let's let's break this down for a cold Replicated state machine recovery. It's a little different than warm. The first thing is with a cold Recovery you first have to load a snapshot then you have to replay the log If we break that down sort of in the end of you of we have loading the snapshot We have a couple messages here in the state that gets generated You break it down into two steps the time to load a snapshot and then the time to replay the log So What does this matter? Well, let's say that you snap shotting once a day every 24 hours What's the worst scenario you've got a snapshot that is 23 hours and 59 minutes and 59 seconds point 99 seconds old, right? How long does it take to replay that when you're sending millions of messages a second a Long time. It's not IO bound It's compute bound because it's replaying and doing all the different things that needs to get this state so It's realistic to think that you could have a situation where you're replaying that much data and have to Reconstruct it and that's time where you're not participating in you know and actually being a node in the cluster Can't till you catch up So that means that the looting a snapshot is small Typically ish And it's large, you know the time to actually replay the log. It can be large So How do you fix this well a couple different options? The first is you can actually snapshot more often Suppose you snapshot every hour and you know that you can run through an hour's worth of data in Say a minute and that might be good enough right your SLA may be that you know in a certain types of situations like this You're able to come back within a minute replay and be caught up to speed. That's great And that means really what you're doing is you're just making it smaller log to replay But you then have more snapshots. Well, so what happens about the impact of taking a snapshot? You know anything we do on a machine perturbs it In fact, if you work in low latency, you're very aware of this trying to quiet a machine is a very intense process I'm trying to find out what is going on in the machine that is changing and making something else slow So taking a snapshot is going to perturb the machine in some way In fact, it does more than that in rafts taking a snapshot is an event in a log You then have to have all the members take that snapshot at the same time in the log Guess what nothing else is being done while they're taking that snapshot, right? So that's a disruption But if you were to instead think of it as Having something else that asynchronously takes that snapshot and disseminates those those snapshots back into the cluster nodes That is one way to think about you know reducing the impact of snapshots That doesn't just solve that you know snapshotting more often it helps But you still have the problem of if you're going to load For you know a snapshot and then load a log and you're not willing to go for a couple minutes while you're doing that How do you go faster? You have to have something which is at least warm and Then the idea is having a service replica running your logic in DR ready to be hot In a moment's notice You don't have to be an active node in the cluster You're the one the standby or that other node is just pulling across the SNAP the snapshot that's pulling across the log It's processing it just like a normal node was it's just not a active member of the cluster If a active member of the cluster goes down and you want to replace it with that you just have to tell it join cluster And that idea of being able to just swap in you know a crash node with a node That's warm and letting it go hot What kind of delay is that? We're seeing it's only about a second or two Most of that can even be reduced as well. So you're thinking of something like in DR. It is possible to run in DR Something where you have a full copy of your of a cluster running. You lose the data center You can start up in DR in You know seconds That's kind of powerful right because that means that it's like oh we lost the data center We had another heat event like we had in this summer right in AWS And then be able to be right back in it within seconds. That's pretty nice, right? That's the kind of idea that that we we kind of think about you know what has to happen for a lot of systems 247 upgrades so that's kind of one cut one There's a couple different things there that we talked about in terms of what it actually means to look at How you can you know get basically things from a disaster and recovery in a recovery time But let's look at another cause of you know when you're running 247 and how you want to do upgrades So you're going to do upgrades probably by stopping everything, right?  There are there are businesses that do this but That's not going to work right there. There is a significant amount of downtime. That's going to happen no matter how you do that So how do you? How do you do this? No, let's say that we run two systems one hot Okay, one that is let's say it's warm and we upgrade that one and then we switch over How long does that switch overtake? couple seconds That too long it might be If you're doing it if you're doing a couple second outage, you know four or five times a day People don't want to upgrade right? So that's a barrier you want to make us so that upgrades can be done quickly So the first thing is you have to really kind of absorb the fact that components will be on very varying versions No matter how you're doing an upgrade you can't just do it all at once if you're going to be live while you do it And that means including the infrastructure things like Aaron Aaron archive Aaron cluster These have to work in situations where they're running multiple versions in production now That's that's something we take on right but we don't think that it's any different if or if we say that you know You should do it. We have to also do it too, right and we do and I mean all components That you have the cluster is only one piece of usually larger systems So all of them might be on different versions. The best thing here is protocol design And lessons that have come from that so about how to make protocols so that you can have multiple versions running and how you do things like You know backwards compatibility obviously, but for was compatibility So what does for compatibility mean? It means that you put forethought into how might things change and how can I catch that there is a new version? that is safe to not Interoperate with and things that are safe to interoperate with by putting several little Bits in messages. That's one way of making them for compatible because you think up front. How do I handle this when I don't know what to do? You can give a little bit of additional information There's specifically things like IPv4 TCP Options and other things have this in mind because they they know they're going to be operating in situations where there's never going to be the same version So they have like ignore bits in options where you can ignore this option and keep processing but if you don't understand it and it doesn't have the Ignorance that you have to throw the whole message away that type of simple thing can then be leveraged when you're actually doing things like that Other thing is version everything and I mean everything messages data data and rest data in database Everything should have versions attached to it. Your future self will appreciate this To know sort of a lot more things later on the concept of semantic versioning is Is a powerful one? It is a versioning scheme that has very strict rules about what is compatible and what's not and how you version based on it When you have this you can leverage that idea to figure out if that's a message or a piece of data that you know How to handle and ones that you may not know how to handle so upgrading during production rolling rolling upgrades What we have seen is This sort of scenario, you know, you have a service. It's running various versions In this case, they're running the same version because we're gonna upgrade all of them And so you basically do the the simple thing you're leveraging raft You're leveraging the idea of your high availability. You're taking one down and upgrading it. You're continuing to operate because you have to The obvious problem here. I will address in a minute But you do this Now that is upgraded now you start upgrading the second at that point notice you have two versions in production You have two different versions that are live and active in production You have to have that so the idea that you're going to have this and just accepting it is fundamental to being able to do that and We do the last one and then we're done and everything everybody's upgraded and happy a Couple things to realize about this the obvious problem here is that when you take one down You're operating at risk and the idea of operating at risk is you have one node failure and it will stop and stall Processing because you cannot reach consensus so during that process when you're doing the upgrade of one you better hope that they don't fail How do you address that? You use a larger cluster So five nodes you can upgrade one at a time and not be running at risk now You can only you know will stay on one failure, but that's fine if you're Thinking about it if that is your bar Then doing it does that mean that you should grow the cluster to five and from three and then go back to the You know back to three when you're done actually know if you're upgrading all the time. Why would you want to do that? Why don't you just run five right? What some of our customers do better use Aaron they've run five. This is how they do rolling upgrades. Just simply Take one down. They not running at risk They then upgrade that one and just continue to do that. But if here's an interesting part of mouth math The majority of seven is four right so you can actually upgrade You know you you will can actually upgrade two at a time when you run a seven node cluster It's actually faster to do it that way than to run five Right with five you have to do one right after the other. That's five times So the time commitment is you know five times whatever though it is for one when you do it with seven it's four The interesting interesting thing to consider so There's lots of other implications of when you start to version everything your log now Has all kinds of version history in it That's kind of interesting isn't it so you have all these versions you can see when they change You know exactly what you know when they change the message event that when they changed That's an interesting thing to think about So this this has some interesting side effects when you start to start to put versions all over the place and start Thinking about running with the different versions in production Here's some hard lessons though that we've seen Retaining old broken behavior forever You almost have to so here's an here's an example, let's say you're in exchange. Let's say that you have some broken logic Let's say that you executed that broken logic at some point now It probably had no effect on the customer, but it has an effect on you for a regulatory reason If someone let's say you're operating in you seven years that you have to be able to retain that data You also have to go back seven years to look and see the logic that you execute on that data The interesting thing to think about right you may have to not hold on to that That broken data or that broken logic in your actual app and running But you may have to be able to go back to it and say here's how this happened So that's an interesting thought is how you have that because that log stays around for a long time The cluster services are often easy part Kind of if you look at this a lot of Design goes into how you're going to actually handle different versions when you're going to upgrade how you're going to upgrade Doing rolling upgrades like this and being able to continue to work while you're doing that and In how you coordinate this as a system with the external things like gateways attached to it stuff That's downstream that you know is processing data even databases that are attached in other places So it's usually the cluster itself in the cluster nodes Those are the easy things to upgrade the hard things are the things like everything else that's attached And that's where when you started to think about the fact that you may have multiple versions that are running in production and how they Interoperate you you actually actually make yours make the whole system cleaner because you can now use some of those techniques that you probably learned downstream as well Future flags or feature flags are not version They're not versions Seen this many times where people look at feature flags and they put them in a version and then they want to upgrade the version But that means that they're they just want to add a feature flag that which means they have to update the version Why not have the feature flags totally separate from versioning? That's a that's something that's usually a lot better the couple feature flags and versioning And the last thing is leverage the determinism you have determinism Realize that now reading that log. There's a lot of stuff that you can do with that that logic So leverage that for testing leverage it for the fact that you can run that same test over and over and over And it will give you the exact same state That's a powerful thing Just don't put like you know things that are non deterministic in there because then you'll have to be chasing them for a long time Anyway These are just some of the things that we've seen as we've seen a lot of users of air move from going from a lot of times Where they had some dedicated downtime maybe once a week not a whole lot But I'm talking about something where they had a window to no window at all that where they have to operate 24-7 and maintain Pretty aggressive SLAs they normally have Thank you any any questions Yeah, the the the back up and and this works also with standby as well So the backup of the standby the the the entity that is in disaster recovery or somewhere else It's the one who's going to the archive of the node and it's going to a follower It had been going to a leader. We've changed that recently So it goes to the followers instead and it load balances between the followers And it pulls across those things as they are you know being in the case of the log as it's being generated In the case of snapshots as they are current. Oh So we're we're in the process of doing asynchronous snapshot support as well And in fact, it'll be one of the jobs of the standby is that can be done like that What we've seen is that people have tried various things to do asynchronous snapshots the the most common thing I think is is Not thinking of it asynchronously enough There's a natural tendency that when you want to take a snapshot you want to get it back into the cluster as media quickly as possible and get disseminated and It's actually better to let that be a lazy So one of the things we added a while ago was when doing you know various things is to actually put IO length on the work that's being done in the archive and the intention there is to do it so that we go slower intentionally till it be less perturbation on the system, you know in that case so the It's sometimes patience pays off so in that case it's take the Take these snapshot asynchronously and if it takes 10 minutes to disseminate it, you know as long as you and you're doing it slowly You're being less perturbing to the system. It's better to do that than to do it too aggressive Now if you want to make sure that you get that snapshot, you know Disseminated because of other reasons you may have other reasons that you want to make sure that you may have other work You want to do it that snapshot? You might want to you know you have full control over how you want to do that But yeah, that's the common thing of just not being patient enough thinking that it has to be there now. I have no idea I Kafka traditionally does things in a kind of a little bit different manner and thinks about things a little bit differently it's not so much a You know unless they've added it recently there's not really a whole raft implementation in Kafka You can build systems that kind of look like this with Kafka You can if you wanted to write something yourself that you know does consensus has its own voting and underneath the covers uses Kafka It's going to be slow So how when I say slow, you know, what is that right? So the fastest way that we have run, you know a cluster is 1.8 million messages a second coming in and at the same time being able to round-trip a message from a gateway Through the cluster and a response coming back out and having the p99 of that response that whole round trip being less than 20 microseconds so On-prem solar flare cards EFI, you know, but you can get these systems to run very fast I think to run something like 1.8 million messages a second with Kafka and that's three machines I don't think you run the Kafka cluster 1.8 million messages a second, you know with three machines. I don't think so This was 32 byte messages We're just looking at you know, and that was maxing out to 25 gig nicks You know one for consensus and one for the log that lots of detail on that But essentially what that is is what kind of how far can you push cluster and you can push it very very far But that's as fast as we've been able to push it. I'm not sure I think what I mean from the Normal way that I believe that kind of architecture works You're really what you're doing is you're extending the club the Kafka club, you know the Kafka nodes the Kafka services into DR in some way Kind of it could look somewhat how we do warm, you know warm standby or cold backup That kind of thing where you're extending it into but I don't know the details of what they do I mean traditionally if you look at most brokered architectures they do that by bridging, you know into DR and That means they get very slow because they're round-tripping everything through DR We're fundamentally not we're asynchronously streaming into DR. All right. Thank you


Elante Tambo, within Peru, is undoubtedly one of the most incredible ruins to be found anywhere on Earth. Although many people have been mystified by the site's characteristics, some even suggesting that its shelf-like construction was once created as steps for giants, its real original use however, being no less remarkable. The so-called pre-incas, responsible for its original build, did so with the intention of utilizing these layers of soil to slowly acclimatize plants that were once not used to a certain altitude through a process of selective breeding, eventually taking them far higher than they were ever found before, making it possible to cultivate said herbs, fruits, or vegetables within their high-altitude sanctuaries once virtually impenetrable fortresses so that with these newly adjusted phenotypes of plants, and with the aid of what is the subject of this video, could stay high in the mountains virtually indefinitely, self-sustained thanks to the incredible achievements of Elante Tambo. The Incomisana Water Temple, being the final piece of this now lost people's armory, for although the horticultural knowledge displayed by this lost civilization is evidence of advanced culture, their abilities to control the path of water is another of the pieces of evidence which not only proves that this people were highly capable, but were also unquestionably advanced in their execution of said feats. For although these irrigation systems, or drinking water inflows, are many thousands of years old, most still work to this day. Some of these water features were so well made that even modern re-inhabitors still use several of these systems as they even rival that of the modern system which would replace it, bringing water to the locations. Dr. Richard McSod, who studied the water sources of Incomisana in Ole Tentabo, led a team of researchers from the University of Virginia, known as the Right Water Engineers, from the Right Paleo-Hydrological Institute, and archaeologists Armenda Gabaja Oviedo, and Dr. Gordon McCowan, all of whom conducted reverse engineering in an attempt to back-engineer the remarkable achievements seen at the water temple. Located north of the Manuraki Canal, in the sacred valley of the Incas, at an altitude of 3,000 meters, this sophisticated water complex consists of rooms, open spaces, beautiful complex pools, ornamental fountains, waterfalls, and buried channels. These pre-Incan accomplishments display an intimate knowledge of so-called modern hydraulic principles, even building their channels in such a way as to avoid hydraulic jumps. The water temple's architecture and hydraulic works define Incomisana as a high-status sanctuary for worship of water. Intricate and carefully executed cliff carvings parallel to the water temple add a mystical dimension to the temple's original purpose, which is currently claimed to have been the worship of water. Ancient roads also left by this same elusive group unquestionably tie Olentetabo and the water temple to this once great now lost civilization's empire. Who built the Incomisana water temple? How did they build it? Why is the polygonal masonry, something which ancient Peru is synonymous with, found at many of the world's ancient relics? Who were these ancient people? Where did they go? It is undoubtedly an incredible place, one which we find highly compelling. There are many astonishing ancient ruins which can be found throughout India. Ancient temples or caverns often carved into giant boulders or directly out of the bedrock of earth itself. Many of these ruins drenched in exquisite artwork, carvings created with such vision and accuracy that they boggle the minds of all who attempt to explain the methodology of their creator. We have covered a number of sites within India in the past, many of them so precise in their finish that they could have seemingly only been created using precision stone cutting technology, and our next side of interest is of no exception. And in the northern part of the state of Karnataka in South India, the village of Hampi has some extremely captivating ruins. Dotted with large boulders, the site is also home to some extremely puzzling relics, one of which is the ancient chariot, clearly a depiction of a once astonishing creation. The cart itself was not only clearly massive, but was pulled with elephants rather than horses. By indicative of a highly capable group, this incredible chariot is one amongst an array of marvelously preserved architectural artifacts, most of which display a level of refinement created with such precision that modern man could only replicate such feats using machines, something modern academia claims has only ever been utilized by our own modern civilization. Thus, an explanation as to how the site, or indeed its smorgasbord of ancient precision made stoneworks were made, eludes us to this day. And we hypothesize that the reason for this is due to mainstream historians' reluctance to consider what these ruins clearly indicate. That they were once the work of a civilization that was not only highly advanced, but utilized stone-cutting technologies, methods of transportation, lifting and placement that rival even that of today's architectural capabilities. How can one peer upon such sites as that of Hampi, or indeed others, Pumapanku, Giza, Petra, etc. Sites created with such accuracy, that to suggest they were created with soft metal tools or with the use of primitive measuring equipment is simply absurd. Furthermore, none of these ruins would be possible simply with the use of the human eye. The only logical explanation is that just like that of modern-day stonework, the stones were indeed machined, cut to such a high quality using precision tools, only then were they placed where they lay today. Hampi was predictably re-inhabited by ancestors based within permitted timelines, once being the capital of a previous Indian Empire. What's intriguing about the site, however, is the mysterious, seemingly untouched boulders which dot its grounds. The question is, although they now appear to be geological, were they in fact once relics themselves, left by an even earlier civilization? If not, then why were these stones left where they are found today? Why were they built around rather than utilized, carved, or shifted? They were clearly ones of significance, and due to the fact ancient sanctuaries and fortresses are often re-inhabited. The possibility that they were indeed once carvings would logically make sense. The questions would be, just how old is this civilization? Who built the ancient site of Hampi? How did they build it? Were ancient high technologies utilized in its creation? If not, then how was it constructed? It is a place which we find highly compelling. Ancient uparts are undoubtedly one of the most interesting subjects in regard to lost antiquities. Many of these artifacts, due to the locations in which they are found within, or the immense age displayed within the erosion seen upon the object, makes them one of the most controversial areas of study. How can one answer the question of how an iron pod is found within a solid lump of coal within a seam over 300 million years in age? Or how the clear imprint of a chariot wheel is found fossilized deep within a mine in Russia? These artifacts, found at hundreds of feet deep in sediment, or displaying a wooden handle petrified into coal, display an undeniably immense age, and as such, are solid pieces of evidence to support our posit of there having been a series of now lost civilizations stretching far into the past. Nature is infamous in being cyclical. Why then would we not be permitted by mainstream academia to presume this be the case for the climates of the Earth as well? Regardless of this digression, however, the subject of tonight's video is an incredible artifact which we believe to be that of an ancient upart. However, due to its incredible characteristic, is being masqueraded as that of a much later creation by a far more recent ancestor. Known as the Sword of Gougeon, this intriguing artifact has somehow resisted the effects of time, and although it is enormously old, is seemingly as sharp and as shiny today as the day it was made. This remarkable characteristic, although unexplained, is not the only interesting thing about the sword. It also features an incredibly old form of writing. Many characters are written in an ancient script, now known as Bird Worm Seal Script, literally Birds and Worms characters, owing to the intricate decorations of the defining strobes, it is very old and is attested to be a variant of seal script. In 1965, while an archaeological survey was being performed along the second main aqueduct of the Zhang River Reservoir in Jingxiao, Ubei, the series of ancient tombs were discovered. A dig started in the middle of October 1965, ending in January 1966, eventually revealing more than 50 ancient tombs. More than 2,000 artifacts were recovered from the sites, including the sword, having been found inside a casket together with a human skeleton. The casket was discovered in the December of 1965 at the Wangshan Site No. 1, seven kilometers from the ruins of Ying, currently called Jinashang, once the ancient capital of Qiu. The sword was found sheathed in a wooden scabbard, finished in black lacquer. The scabbard had an almost airtight fit with the sword body. Unsheathing the sword revealed an untarnished blade, despite the tomb being soaked in underground water for over 2,000 years. How did this sword retain its incredible condition? Why does it seem as if it is resistant to aging? What sort of metallurgy did the swordsmith once use to create such an amazing object? It is clearly an ancient upart, and one we postulate has an origin now hidden within the bowels of history. It is a remarkable thing, and as such, is highly compelling. In Austrian explorer Arthur Puznanski performed a study on Puma Panku in 1926. He later hypothesized that it was, in fact, one of the oldest archaeological sites on the face of the Earth. An ancient ruin dating back at least 15,000 years ago. Puznanski was one of the first explorers of the modern age to have ever investigated Puma Panku's incredible existence. And as our regular viewers would have predicted, his hypothesis is staunchly denied by academics worldwide. Yet, regardless of this, his sound reasoning, and indeed that of many other critically-minded individuals, means that his theory is one many others have arrived at, thus it continues to have many supporters to this day. And although mainstream academia persists in their attempts to place this amazing and largely inexplicable site's date of construction within permitted timelines, claiming to have carbon dating done at the site which places its origins at around 500 BC, supporters of a greater age dismiss this dating as unreliable. And due to our own in-depth and many years of investigative experience regarding these ruins, tend to agree that the site is indeed far older, and due to their having been in ice age around 10,000 years ago, this dating made by Puznanski would put it right where one would expect to have found it if it was indeed the work of a pre-catechalismic civilization, with Puma Panku being a surviving relic of their incredible legacy. Additionally, archaeologist and researcher Neil Steed has also investigated a relationship with astronomical alignments. He discovered intriguing supporting evidence for this controversial opinion, finding that it was built to coincide with winter and summer solstice, and a precise alignment with the spring equinox as well. However, these events would have only been perfectly aligned with the temples over 17,000 years ago. We have long argued against a field of study that is not only assumptive in method, but is also conspiratorial in nature. Any dating of any relic, which cannot be explained, is merely an attempt to muddy the waters of understanding. Often obscured with an in-depth volley of detailed and competent investigations into civilizations, we posit merely re-inhabited said sites with a known recent well-studied history. This convincing tale of events, however, is short-lived if one explores any of the said sites with a logical eye. One soon finds that many characteristics on display are not only found globally, which on its own is compelling proof of a past global superpower. But the countless trilathons, enormous megaliths, some reaching into the thousands of tons, along with highly advanced, incredibly accurate, yet unknown masonry techniques, all tell a story which academics who never seem to mention said features cannot explain. And to mention melting pots of ancient academic anomalies such as that of Puma Punku. How can anyone logically claim that the astonishing precision on show at the site, along with the many basalt megalithic platforms weighing many hundreds of tons, all indicative of a past highly capable technologically advanced civilization once having been responsible and once one grasps just how many holes can be found within mainstream opinion? They can be forgiven for doubting said tale of events, especially when those who tell such tales actively attempt to conceal such unexplainable features. Who built Puma Punku? Is it really over 15,000 years old? How would one cut such precision stonework without precision machinery? It is a place which we find highly compelling.


Okay, I was super excited when I actually got this package from Jingos and also thank you to Massimo and in general the Italian Jingos community that actually managed to make this reach to me and now that I have it you can see me actually feeling to properly unbox it but then you can actually see that inside of it there's the keyboard and underneath the Jingpad A1 and I gotta say the boxes are very nice now now they're wrapped in plastic but soon they're going to be you know unwrapped and the material feel like the materials they choose for the box it really makes it feel like very high quality so I was actually rather impressed with also you know the logo with this white transparent translucent thingy I like it and then we can see that inside of it there's a wait for it wait for it yes yes a cover with which is the leather cover without the keyboard and again I had to hold it into my hands because it really felt so nice and then of course inside of it there is the tablet with the pen I tried to take off the plastic but it took me a couple of tries here it's connected to the cover by a pretty strong magnets now you can see that I'm trying to take off the plastic and when I finally managed to take off all of it I take the tablet into my hands and my first thought was like wow look at this glass back it was really impressive like I've heard positive comments about the tablet but actually holding it into my hands for the first time it was really nice I think the back with the logo is super cool you can see all the reflections and I really like it then what else is in the box then also sorry I forgot about that the leather cover has the jingle pad logo very faint inside of it there is the pen you can see that well I'm trying to show you how you would use the pen but more seriously you do have a USB type c charger let me focus this and on the other side you also have a button for the eraser which actually works I've tried it and then you also get the brick to actually charge it it comes in the china version you can use any adapter and on the other side you have well first of all the sim thingy to get out your sim and sd guard and even though wifi sorry cellular phone is not yet supported you can actually insert your sim and it will recognize it there is some candies for some reason but also the cable which actually connects the tablet and the brick and again let me show you that it is indeed a china version of it then let me actually take this off and switch to the keyboard which I was very curious in taking in opening up sorry because it's really I think a very important accessory I was always been a fan of the surface like laptops with the detachable keyboards so I was really wondering how could this perform for these tasks so you can see me here again not very doing a good job of unboxing you can actually see that I'm not a professional yet but as soon as I actually managed to take this into my hands my first impressions of it were that it actually pretty heavy and thick but because of that it really gives you a nice feeling of being solid and you can open it up take this off inside of it there's a cardboard to make like the width of the thickness sorry of the tablet the materials here are very metal and I think it's a good choice when you actually put inside the tablet it's all metal and it feels really sturdy when it's open you can see that the place where the tablet lies has this texture that's very alcantara like and when you close it up there's the nice logo and on the back you can actually open up I had to do a couple of gases to actually find the right spot the thing is that actually holds holds hit up to be more like a computer now that we've done that we can actually try to insert the tablet inside of it I did show you like how open it can get this is as much as it can go it can close up and at this point when it's actually all close together it's quite thick and heavy and this is true the tablet itself is much lighter but it really feels so nice and also the leather cover I wouldn't probably use it much but that one also feels nice in the hand so materials are big thumbs up for me now I'm setting up the account I did not notice that I had to put six numbers inside of it done that again you can see how you can actually choose even in the leather cover how much to rotate it you can choose between those two you know selection brackets and then I choose the time zone for some reason Italy searching from for Italy didn't bring up anything but searching from Rome did bring up Rome Europe Italy but okay select that and the way if I skip that you have to agree with the terms which is we're all hello that's me which is weird because usually you don't do that for open source projects but okay and then it actually boots up you can insert the password you just did you will discover that 123456 is not actually the password that I usually use on my devices so don't try it with my accounts and it actually works now here I just tried to see if there was any issue like with the monitor or opening up a couple of experiment apps but to actually know how it performs them give a look to hit as a whole you need to wait until I do a full review still I was also wondering how this worked when docked to the keyboard and how was the truck pad because that's a really important point like I do have like the pine book which is super nice but the fact that the truck pad isn't that good really makes it meh overall and this time the truck pad is really good and I was happy to try it out the mouse is nice and you can use all of the gestures as well so I like that here you can see that there is the files application you cannot right click which is weird but on such a tablet oriented device it kind of makes sense I hope there's some way to still do a right click in apps like chromium and that was it so again I will do a couple I think even more videos about this trying it out reviewing it and setting up stuff so if you're interested in seeing how it performs to daily tasks well just stick to the channel and you'll discover it


First question is from de de seg mowin. How would you tweak anabolic and aesthetic to be an hour format? So maps anabolic and maps aesthetic. So, you know, here's one's just what's interesting about this. I Obviously created maps anabolic. I still follow the program here and there it doesn't take an hour over an hour to do maps anabolic foundational workouts No, it just does but anabolic does not aesthetic does but maps anabolic doesn't so if you're taking Over an hour either your rest periods are too long or I don't know what you're doing It should not take over an hour. Now maps aesthetic. I Typically would do the workout in an hour and 15 minutes hour and 20 minutes at most. I know Doug same experience It's just more volume. Now if you don't have over an hour to do maps aesthetic workouts You could just cut the sets out of the exercises for the areas of your body that you think need less work There's other ways you could do this Or at least how I do it because this happens to me sometimes sometimes I only have 40 minutes or 30 minutes and so and I'm running through one of these programs So what ends up happening? So if I have if I'm short on time and I'm running maps anabolic and I talked about this the other day I think on the show like because this this kind of how I'm training right now is I'll cut it in half, right? So it's only a three-day a week program. So what I'll end up doing is You know, I'll do upper body one day lower body the next day upper body But I'm following all the exercises in anabolic I'm just turning it from a three-day week to a six-day a week program and splitting it in half So that's how I would mess with anabolic now a static. You mean it's okay, right? Yeah now That's how I would do anabolic now a static because we there's more days in the gym It's a little bit longer and then you have focus sessions I would just add some if I couldn't get to I'd pick a muscle group or two And I'd pull it out of the foundational day and I would just add it to a focus day. Oh, that's a great point Yeah, so you have a full it's because the way aesthetic is designed It's a full-body routine and then you have focus days every other day So what I would just do is just say, okay I'm gonna take the my shoulder exercises and might maybe my pushing exercises shoulder Chest and tries I'm gonna put on my focus day with my my two or three focus exercises that I was gonna do Yeah, I think that's that's great advice and those are two easily two of the most popular programs. Yeah that we currently that's I mean one of the things we always try and communicate on the show is that you know, we design these things as As a foundation or as a kind of a generic blueprint for people to follow But you this is how you can modify this stuff I mean, yeah, you're you're always best that is to learn how to modify workouts for you And this includes your body your goals your fitness specific areas you want to focus on and your schedule And that's that was the idea the idea was to give you the the blueprint and then you kind of move away or Change it according to your individual needs and that's always gonna give you the best results Anyway, individualization of workouts is one of the best things


too much, so just get started. We've been here since our service. That's what's going on. That was a hard day to go on so far. It was really great. It was a good work here. I want to know I'm really grateful for the lease by working with the people


Ads heard during the podcast that are not in my voice are placed by third-party agencies outside of my control and should not imply an endorsement by Weird Darkness or myself. Stories and content in Weird Darkness can be disturbing for some listeners and is intended for mature audiences only. Parental discretion is strongly advised. Welcome Weirdos, I'm Darren Marlar and this is Weird Darkness. Here you'll find stories of the paranormal, supernatural, legends, lore, the strange and bizarre, crime, conspiracy, mysterious, macabre, unsolved and unexplained. Coming up in this episode it's Thriller Thursday. The landlady is a short horror story by rolled doll. It initially appeared in The New Yorker on November 28, 1959. Doll once said that he'd always wanted to write a ghost story but never quite been able to. The closest he came and his opinion was the story that I'm about to share with you, the landlady. But after reading through his own story afterward he doesn't think he really succeeded with his effort. Nonetheless, the tale won Best Short Story Mystery at the 1960 Edgar Awards, so for this Thriller Thursday episode I bring you the landlady by rolled doll. If you're new here, welcome to the show. While you're listening, be sure to check out WeirdDarkness.com for merchandise, my newsletter, to enter contests, to connect with me on social media. Plus, you can visit the Hope in the Darkness page if you're struggling with depression or dark thoughts. You can find all of that and more at WeirdDarkness.com.  Billy Weaver had traveled down from London on a slow afternoon train with a change at reading on the way, and by the time he got to Bath it was about nine o'clock in the evening and the moon was coming up out of a clear, starry sky over the houses opposite the station entrance. But the air was deadly cold and the wind was like a flat blade of ice on his cheeks. Excuse me, he said, but is there a fairly cheap hotel not too far away from here? Try the Bell and Dragon, the porter answered, pointing down the road, they might take you in, it's about a quarter of a mile along on the other side. Billy thanked him and picked up the suitcase and set out to walk the quarter mile to the Bell and Dragon. He had never been to Bath before, he didn't know anyone who lived there, but Mr. Greenslaid at the head office in London had told him it was a splendid town. Find your own lodgings, he had said, and then go along and report to the branch manager as soon as you've got yourself settled. Billy was 17 years old. He was wearing a new navy blue overcoat, a new brown trilby hat, and a new brown suit, and he was feeling fine. He walked briskly down the street. He was trying to do everything briskly these days. Briskness, he had decided, was the one common characteristic of all successful businessmen. The big shots at the head office were absolutely fantastically brisk all the time. They were amazing. There were no shops on this wide street that he was walking along, only a line of tall houses on each side, all of them identical. They had porches and pillars and four or five steps going up to their front doors, and it was obvious that once upon a time they had been very swanky residences. But now, even in the darkness, he should see that the paint was peeling from the woodwork on their doors and windows and that the handsome white facades were cracked and blotchy from neglect. Suddenly, in a downstairs window that was brightly illuminated by a street lamp not six yards away, Billy caught the sight of a printed notice propped up against the glass in one of the upper panes. It said, bed and breakfast. There was a vase of yellow chrysanthemums, tall and beautiful, standing just underneath the notice. He stopped walking. He moved a bit closer. Green curtains, some sort of velvet material, were hanging down on either side of the window. The chrysanthemums looked wonderful beside them. He went right up and peered through the glass into the room, and the first thing he saw was a bright fire burning in the hearth. On the carpet in front of the fire, a pretty little dash unto was curled up asleep with its nose tucked into its belly. The room itself, so far as he could see in the half-darkness, was filled with pleasant furniture. There was a baby grand piano and a big sofa and several plump armchairs, and in one corner he spotted a large parrot in a cage. Animals were usually a good sign in a place like this, Billy told himself, and all in all it looked to him as though it would be a pretty decent house to stay in. Certainly, it would be more comfortable than the Bell and Dragon. On the other hand, a pub would be more congenial than a boarding house. There would be beer and darts in the evenings and lots of people to talk to, and it would probably be a good bit cheaper too. He'd stayed a couple of nights in a pub once before, and he'd liked it. He'd never stayed in any boarding houses, and to be perfectly honest, he was a tiny bit frightened of them. The name itself conjured up images of watery cabbage, rapacious landlady, and a powerful smell of kippers in a living room. After dithering about like this in the cold for two or three minutes, Billy decided that he'd walk on and take a look at the Bell and Dragon before making up his mind. He turned to go. And now a queer thing happened to him. He was in the act of stepping back and turning away from the window when, all at once, his eye was caught and held in the most peculiar manner by the small notice that was there. Bed and breakfast, it said. Bed and breakfast. Bed and breakfast. Bed and breakfast.  And the next thing he knew, he was actually moving across from the window to the front door of the house, climbing the steps that led up to it and reaching for the bell. He pressed the bell. Far away in a back room, he heard it ringing. And then, at once, it must have been at once because he hadn't even had time to take his finger from the bell button, the door swung open and a woman was standing there. Normally, you ring the bell and you have at least a half minutes wait before the door opens. But this day was like a jack in the box. He pressed the bell and out she popped and made him jump. She was about 45 or 50 years old and the moment she saw him, she gave him a warm, welcoming smile. Please come in, she said pleasantly. She stepped aside, holding the door wide open and Billy found himself automatically starting forward. The compulsion, or more accurately, the desire to follow after her into that house was extraordinarily strong. I saw the notice in the window, he said, holding himself back. Yes, I know. I was wondering about a room. It's all ready for you, my dear, she said.  I was on my way to the bell and dragon, Billy told her, but the notice in your window just happened to catch my eye. My dear boy, she said, why don't you come in out of the cold? How much do you charge? Five and six pence a night, including breakfast. It was fantastically cheap. It was less than half of what he was willing to pay. If that is too much, she added, then perhaps I can reduce it just a tiny bit. Do you desire an egg for breakfast? Eggs are expensive at the moment. It would be six pence less without the egg. Five and six pence is fine. He answered, I should like very much to stay here. I knew you would. Do come in. She seemed terribly nice. She looked exactly like the mother of one's best school friend, welcoming one into the house to stay for the Christmas holidays. Billy took off his hat and stepped over the threshold. Just hang it there, she said, and let me help you with your coat. There were no other hats or coats in the hall. There were no umbrellas, no walking sticks, nothing. We have it all to ourselves, she said, smiling at him over her shoulder as she led the way upstairs. You see, it isn't very often I have the pleasure of taking a visitor into my little nest. The old girl is slightly dotty, Billy told himself. But at five and six pence a night, who cares about that? I should have thought you'd be simply swamped with applicants, he said politely. Oh, I am, my dear. I am, of course I am. But the trouble is that I'm inclined to be just a teeny weeny bit choosy and particular, if you see what I mean. Oh, yes. But I'm always ready. Everything is always ready day and night in this house, just on the off chance that an acceptable young gentleman will come along. And it is such a pleasure, my dear, such a very great pleasure when now and again I open the door and I see someone standing there who was just exactly right. He was halfway up the stairs and she paused with one hand on the stair rail, turning her head and smiling down at him with pale lips. Like you, she added, and her blue eyes traveled slowly, all the way down the length of Billy's body to his feet, and then up again. On the second floor landing, she said to him, this floor is mine. They climbed up another flight. And this one is all yours, she said. Here's your room. I do hope you'll like it. She took him into a small but charming front bedroom, switching on the light as she went in. The morning sun comes right in the window, Mr. Perkins. It is Mr. Perkins, isn't it? No, he said. It's Weaver. Mr. Weaver. How nice. I've put a water bottle between the sheets to air them out, Mr. Weaver. It's such a comfort to have a hot water bottle in a strange bed with clean sheets. Don't you agree? And you may light the gas fire at any time if you feel chilly. Thank you, Billy said. Thank you ever so much. He noticed that the bedspread had been taken off the bed and that the bedclothes had been neatly turned back on one side, all ready for someone to get in.  Looking earnestly into his face, I was beginning to get worried. That's all right, Billy answered brightly. You mustn't worry about me. He put a suitcase on the chair and started to open it. And what about supper, my dear? Did you manage to get anything to eat before you came here? I'm not a bit hungry, thank you, he said. I think I'll just go to bed as soon as possible, because tomorrow I've got to get up rather early and report to the office. Very well, then. I'll leave you now so that you can unpack. But before you go to bed, would you be kind enough to pop into the sitting room on the ground floor and sign the book? Everyone has to do that because it's the law of the land and we don't want to go breaking any laws at this stage in the proceedings, do we? She gave him a little wave of the hand and went quickly out of the room and closed the door. Now the fact that this landlady appeared to be slightly off her rocker didn't worry Billy in the least. After all, she not only was harmless, there was no question about that, but she was also quite obviously a kind and generous soul. He guessed that she'd probably lost a son in the war or something like that and had never gotten over it. So a few minutes later, after unpacking his suitcase and washing his hands, he trotted downstairs to the ground floor and entered the living room. His landlady wasn't there, but the fire was glowing in the hearth and the little dash hunt was still sleeping soundly in front of it. The room was wonderfully warm and cozy. I'm a lucky fellow, he thought, rubbing his hands. This is a bit of all right. He found the guestbook lying open on the piano, so he took out his pen and wrote down his name and address. There were only two other entries above his on the page, as one always does with guestbooks. He started to read them. One was Christopher Mulholland from Cardiff. The other was Gregory W. Temple from Bristol. That's funny, he started suddenly. Christopher Mulholland. It rings a bell. Now where on earth have I heard that rather unusual name before? Was it Du Boit's school? No. Was it one of his sister's numerous young men, perhaps, or a friend of my father? No. None of those. He glanced down again at the book. Christopher Mulholland. 231 Cathedral Road, Cardiff. Gregory W. Temple. 27 Sycamore Drive, Bristol. As a matter of fact, now that he came to think of it, he wasn't at all sure the second name didn't have almost as much of a familiar ring about it as the first. Gregory Temple, he said aloud, searching his memory. Christopher Mulholland.  She was holding it well out in front of her, and rather high up, as though the tray were a pair of reins on a frisky horse. They sound somehow familiar, he said. They do. How interesting. I'm the most positive I've heard those names before somewhere. Isn't that odd? Maybe it was the newspapers. They weren't famous in any way, were they? I mean, famous cricketers, seven, or football players or something like that? Temus, she said, setting the tea tray down on the low table in front of the sofa. I don't think they were famous, but they were incredibly handsome. Both of them. I can promise you that. They were tall and young and handsome, my dear, just exactly like you. Once more Billy glanced down at the book. Look here, he said, noticing the dates.  It is? Yes, indeed, and Christopher Mulholland's is nearly a year before that, more than three years ago.  I would never have thought it. How time does fly from all of us, doesn't it, Mr. Wilkins? It's Weaver, Billy said, W-E-A-V-E-R. Of course it is, she cried, sitting down on the sofa. How silly of me. I do apologize. In one ear and out the other. That's me, Mr. Weaver. You know something, Billy said, something that's really quite extraordinary about all of this? No, dear, I don't. Well, you see, both of these names, Mulholland and Temple, are not only seen to remember each one of them separately, so to speak, but, somehow or other, in some peculiar way, they both appear to be sort of connected together, as well, as though they were famous for the same sort of thing, if you know what I mean, like, well, like Dempsey and Tony, for example, or Churchill and Roosevelt.  You really shouldn't bother, Billy said. I didn't mean you to do anything like that. He stood by the piano, watching her as she fussed about with the cups and saucers. He noticed that she had small, white, quickly moving hands and red fingernails. I'm almost positive it was the newspapers in which I saw them, Billy said. I'll think of it in a second. I'm sure I will. There's nothing more tantalizing than a thing like this that lingers just outside the borders of one's memory. He hated to give up. Wait a minute, he said. Wait just one minute. Mulholland, Christopher Mulholland, wasn't that the name of the eaten schoolboy who was on a walking tour through the West Country, and then all of a sudden, milk, she said, and sugar? Yes, please. And then all of a sudden, eaten schoolboy? She said, Oh no, my dear, that can't possibly be right, because my Mr. Mulholland was certainly not an eaten schoolboy when he came to me. He was a Cambridge undergraduate.  Come on, your tea's already for you. She patted the empty place beside her on the sofa, and she sat there smiling at Billy and waiting for him to come over. He crossed the room slowly and sat down on the edge of the sofa. She placed his tea cup on the table in front of him. There we are, she said. How nice and cozy this is, isn't it? Billy started sipping his tea. She did the same. For half a minute or so, neither of them spoke, but Billy knew that she was looking at him. Her body was half turned toward him, and he could feel her eyes resting on his face, watching him over the rim of her tea cup.  It was not in the least unpleasant, and it reminded him, well, he wasn't quite sure what it reminded him of. Pickled walnuts, new leather, or was it the corridors of a hospital? At length, she said, Mr. Mulholland was a great one for his tea. Never in my life have I seen anyone drink as much tea as dear, sweet Mr. Mulholland. I suppose he left very recently, Billy said. He was still puzzling his head about the two names. He was positive now that he had seen them in the newspapers, in the headlines. Left, she said, arching her brows. But, my dear boy, he never left. He's still here. Mr. Temple is also here. They're on the fourth floor, both of them together. Billy said his cup down slowly on the table and stared at his landlady.  How old are you, my dear? She asked. Seventeen. Seventeen, she cried. Oh, it's the perfect age. Mr. Holland was also Seventeen, but I think he was a trifle shorter than you are. In fact, I'm sure he was, and his teeth weren't quite so white. You have the most beautiful teeth, Mr. Weaver. Did you know that? They're not as good as they look, Billy said. They've got simply masses of fillings in them at the back. Mr. Temple, of course, was a little older. She said, ignoring his remark, he was actually twenty-eight, and yet I never would have guessed it if he hadn't told me never in my whole life. There wasn't a blemish on his body. A what? Billy said. His skin was just like a baby's. There was a pause. Billy picked up his teacup and took another sip of his tea, then he set it down again gently in its saucer. He waited for her to say something else, but she seemed to have lapsed into another of her silences. He sat there staring straight ahead of him into the far corner of the room, biting his lower lip. That parrot, he said at last, you know something. It had me completely fooled when I first saw it through the window. I could have sworn it was alive. Alas, no longer. It's most terribly clever the way it's been done, he said. It doesn't look into least bit dead. Who did it? I did. You did. Of course, she said. And have you met my little basil as well? She nodded toward the dash-und curled up so comfortably in front of the fire. Billy looked at it and suddenly he realized that this animal had all the time been just as silent and motionless as the parrot. He put out a hand and touched it gently on the top of its back. The back was hard and cold, and when he pushed the hair to one side with his fingers, he could see the skin underneath, grayish-black and dry and perfectly preserved. Good gracious me, he said, how absolutely fascinating. He turned away from the dog and stared with deep admiration at the little woman beside him on the sofa. It must be most awfully difficult to do a thing like that. Not in the least, she said. I stuff all my little pets myself when they pass away. Will you have another cup of tea? No, thank you, Billy said. The tea tasted faintly of bitter almonds, and he didn't much care for it. You did sign the book, didn't you? Oh, yes. That's good, because later on, if I happen to forget what you were called, then I can always come down here and look it up. I still do that almost every day with Mr. Mulholland and Mr. Temple, Billy said, Gregory Temple. Excuse my asking, but haven't there been any other guests here except them in the last two or three years?  No, my dear, she said, only you. Thanks for listening. If you liked the show, please share it with someone you know who loves the paranormal or strange stories, true crime, monsters or unsolved mysteries like you do. And please, leave a rating and review of the show in the podcast app you listen from. You can email me anytime with your questions or comments at Darren at WeirdDarkness.com. Darren is D-A-R-R-E-N. WeirdDarkness.com is also where you can find all of my social media, listen to audiobooks that I've narrated, shop the Weird Darkness store, sign up for monthly contests, find other podcasts that I host, and find the Hope in the Darkness page if you or someone you know is struggling with depression or dark thoughts. Also on WeirdDarkness.com, if you have a true paranormal or creepy tale to tell, you can click on Tell Your Story. You can find all of that and more at WeirdDarkness.com. Stories on Thriller Thursday episodes are works of fiction. The landlady was written by Rold Dahl. Weird Darkness is a production and trademark of Marlar House Productions, and now that we're coming out of the dark, I'll leave you with a little light. Proverbs 16, verse 3. Commit to the Lord whatever you do, and your plans will succeed. And a final thought. As you get older, you really just want to be surrounded by good people. People that are good for you, good to you, and good for your soul. I'm Darren Marlar. Thanks for joining me in the Weird Darkness.


Welcome back everyone. I wanted to talk some more about calculating area under the curve. I actually want to continue the example we finished in the the last video, right? So if you haven't seen that yet, go go back and look at it. What we were trying to do is we were trying to find the area under the curve f of x equals x cubed minus six x as we range from a equals zero to b equals three. We were using six rectangles and we were trying to determine the height of the rectangle using the right points. So what you see in the screen right here is actually the graph of the function y equals x cube minus six x. And you can see here in green and red the associated rectangles to that area under the curve. And so like we saw last time, some of the areas, some of the rectangles lived above the x-axis. Those are going to have positive areas because the y-coordination is positive there. And those are illustrated on this Desmos website in green. And then there are some rectangles have negative area that will be found on those are below the x-axis. And on this Desmos app, they are illustrated here in red. And if you want to play around with this calculator yourself, there's a link below in this video. So feel free to use that. And so this this is actually a nice calculator that can help us do calculate these areas of the curves because as you saw in the last video, we had six rectangles and there was a lot of a tedious arithmetic we had to go through. I didn't even show you all of them because we had to calculate f of 0.5, f of 1, f of 1.5, f of 2, etc. And there was some arithmetic going on there that I had done prior to the video so you didn't even see it. These things can get very tedious very quick and man was not meant to do these type of calculations. That's why man invented calculator. So I wanted to show you some online calculators that you can use to help you out as you try to approximate these areas under the curve here. And so this Desmos one I show you first because I like it because it actually can show you not just the answer but it shows you geometrically what's going on right here. So I'd notice this thing is manipulative, right? So you can type in the function so you have you can type this then you can change that if you want to. You can change the left end point and that affects things. I'm going to put it back to zero right. We'll just leave it there. You can switch the right end point as well and it changes in real time. Of course, you can also change the number of rectangles here. Let's say we want to go up to doesn't want me to change this. Well, I'll just kind of see what it looks like there. You can change the number of rectangles. Something like that. You can also change this value right here. This C value changes the sampling points the Xi star and there's some instructions right here what's going on here. Negative three doesn't even make any sense for rectangles. What are you doing computer? This needs to go from zero to 100 yet. So that's a good number of rectangles. We'll do five at the moment. So going back to the C here just understand what's going on here. C is represented the method of choice. How are you going to choose the Xi star? If you choose C to equal one it computes using the right end point rule. If you choose C to be zero try that again. If you choose C to be zero it'll choose the left end points and if you choose C to be one half it chooses the midpoints of the interval and so this number right here this I right here whichever you're looking at that'll tell you the area under the curve its estimate inside number changes. This is the answer you're looking for. If you're looking for the right end point rule the left end point or the midpoint rule or the left end point rule like this and then I also added the trapezoid rule here where it averages together the left and right end point rules. We talked about each of these in lecture 43. So if we put this back to six and we put this to three and we put this to zero and right end point rule come on you can do it. Oh this web app doesn't really like to work with my recorder very well. It's come alive again. So this right here was the exercise we had done in the previous video and you'll see that the answer we got was the same negative 3.9 375. So this Desmos website does pretty nice for computing these the the so-called Riemann sums. We'll talk about those more in a future video here. It helps this character this area to the curve. Another one I'm going to advertise to you is through emathhelp.net. It has a pretty nice calculator as well. They have a lot of calculators.  Fortunately my recording app is kind of having some issues with some of them which is good news for us. When I personally go to this website I have a pretty nice ad blocker maybe you know I know ads are how they make their money but at the same time I don't want what they're selling so feel free to block them to their doom if you have to. But what you can see here it's it's similar to what you saw in Desmos you can enter your function x cubed minus 6x set your a value set your b value set the number of rectangles and you can choose how you're going to choose the sample points and so then there's going to be a step click button down here that says calculate and so it takes a second to calculate it'll reload the page and now you get some new advertisements seriously go to the you no no go to suu come on what are you thinking there internet why does it think I want to go to the you right now anyways and you might not be able to see this super well on this video but if you if you go to the website yourself the link is below you can this will look at a lot this will look a lot better to your screen you can manipulate the sizes and things so it'll repeat itself and tell you that you're trying to find the area under the curve x cubed minus six as you go from zero to three this integral notation will make more sense in a future lecture so just just postpone a little bit there and so you have your function you go from a equals zero to b equals three six subdivisions it then calculates the delta x which you got one half and then calculates each of the x i's so we have the interval zero to one half one half to one one half to three halves three halves to two two two to five halves and five halves to three just like we did before it calculates each of those values f of x one which was negative two point eight seven five f of x two which was negative five you go through all of those so it gives you all of those details and then in the end it'll give you the value one half times the sum of all those things you get the negative three the negative three point nine three seven five so if you're only interested in the final answer you'll calculate that for you but also it shows you each and every step along the way so you can kind of understand where the calculation is coming from if you don't want to see the steps you can actually click where it says show steps and if you turn that off it'll do the calculation again with just the just the final answer there so you know hidden amongst many ads here but negative three point nine three seven five here so what i want to do is just do another example of this uh so let's time let's take the function x squared and we're going to go on the interval zero to four let us do four subdivisions why is this thing stubborn there we go we're going to do four subdivisions so four rectangles and this time i want to use midpoints so for the decimals want to have to choose this c to be point five and so you can see right here if you go from zero i'm sorry not zero to four i want to go from zero to one that's the example i prepared so i'm going to zoom in a little bit so you have your standard parabola y equals x squared and so if you look at the area under the curve using these rectangles you get the four rectangles you see right there their height is determined by the midpoint so we're getting these values right here and then if you scroll down you can see the estimate uh the area is going to be approximately point three two eight one two five that's approximately how good the area is under the curve and like we saw on previous videos the midpoint rule does pretty good because although the midpoint rule at some points might overestimate at other points it underestimates and it kind of averages out to be a pretty good estimate um if we were to do that with the emath emath help calculator we type it in x squared use a carrot there for exponents we want to go from zero to one four rectangles and then we can choose our scheme here there's the left rule the right rule the midpoint rule the trapezoid rule so we'll pick the midpoint rule and i do want to show the the steps here so let's calculate so this gives us all the explanation of what was going on in that calculation right so we're trying to approximate the area of under the curve zero to one x squared we had four rectangles we're using the the midpoint rule here so we're going to calculate each of these midpoints x zero plus x one over two x one plus x two over two x three plus x x two plus x three over two keep on going in this situation your delta x will be one minus zero over four which is one fourth um you're you're getting a four sub intervals and it'll look like zero to a fourth a fourth to one half a half to three fourths and three fourths to one then if you find the midpoint of each of these intervals you're going to get one eighth three eighth five eighths and seven eighths calculate the function at those values since we're just squaring function we have one sixty fourth nine sixty fourth twenty five sixty fourths and forty nine sixty fourths there's the decimal expansions there as well so we have to add together those four values times it by delta x which is one fourth and then you get the the value point three two eight one two five so that's pretty cool uh because these calculators can give you all the details you need um as you're working through these things and again i do want i want people to use calculators these type of numerical approximations should be done with a calculator it's very important that everyone understands exactly what the calculation is what's going on we should know what's going under the hood so to speak but please use technology to help you so you don't spend years upon years trying to calculate these things and i'll talk some more about those in the next video uh look at the link below to find it and please subscribe bye


Meantime, President Mohamed Buhari has mourned the victims of terror attacks in Borno and Kitsina State. In a statement by his spokesperson Garbashir who the president vowed that the perpetrators would be brought to justice and called on migrants to come together in the fire ends of those who would seek through terror and violence to divide them along religious, political or ethnic lines. He said the attacks on artisanal minors and farmers for survival were evident that a terrorist and bandit had been backed into a corner. The president told the victims in his thoughts and prayers.


Hi, this is Danielle Gardner. I discovered George Cowell a few years ago when I was at a point in my business journey when I was just reassessing everything that I'd ever been taught about marketing and business and I really felt that a lot of the things a lot of the practices that I was even doing they really lacked some integrity and they also encouraged a lot of fear and panic that just didn't feel good, you know, and so it was really refreshing to meet someone out there who thought the same way I did and I guess since having this change in myself quite honestly, I haven't been able to identify any other coach that I would work with so George has been my my chosen coach and mentor for the last couple of years I've been in his master heart program for what this is my second year and I've done some one-on-one coaching with him as well. So I love George's approach I love the way he thinks and the things that he brings up it's really encouraged me with my own marketing and he's also very much helped me with systems in my business to actually follow through and get things done things like writing content things like following up on previous clients and having that sort of after sales service so to speak so and you know George has a system for everything which is is so great so that's what I've really benefited from as well and I guess It was also very surprising to me that really George's pricing is very reasonable I mean he here is a person that is making a big impact in the online world and It's very reasonable to work with him as well price-wise. So all of those things Have been something that I really value. So if you're looking to work with George, I really hope this helps you and That you can do some great work together. This is Danielle Gardner. Thanks for listening. Bye for now