Upgrade your smartphone with Appalachian Wireless. Get $300 off selected models, capture memories, stream and stay connected with the latest technology. Visit one of our stores or AppalachianWireless.com right now. Appalachian Abundance will be hosting their first clothing swap Saturday, July 22nd at AppCycled in downtown Pikeville. The clothing swap is going to be set up in a way where you come in with your clothing that is washed, no stains, no rips, clothing that's in good condition that you would give to someone else and you're going to bring those items in pre-sorted, pre-folded and we're going to have clothing laid out that other people have already donated for the cause and you're going to get one ticket per one item and then you can go through all the clothing that we already have set up so it's not going to be anything from AppCycled directly but it is going to be clothing that is in good condition so you don't have to worry about getting something old and gross. It's going to be something fun and fresh. Appalachian Abundance hopes the swap will help reduce clothing waste, support slow fashion and build a community. The clothing swap is kind of going to enhance the community around reduced reuse recycle. We sort of have there's a stigma around old dirty clothing that we want to reduce. We want to show people that not everything old is bad. Things that are old can be great and you still have life and things that are usable. The swap will be held from 12 to 5 p.m. For more information go to Appalachian Abundance on Facebook. Reporting for Mountain Top News, I'm Brianna Robinson.


Ukrainian forces could retake Bakhmut. As Wagner Group troops evacuate Bakhmut, Ukrainian forces may have a chance to retake the war-torn city but it's unclear if that will be Kiev's priority as a long-awaited counter-offensive looms. Business Insider wrote it. Russia claimed victory over Bakhmut earlier this month after a long and costly battle for both sides of the war. Shortly after, Wagner Group boss Yevgeny Prigozin announced he would be withdrawing his mercenaries from the city on June the 1st after Russia claimed full control of the city. Regular Russian troops will replace Wagner's forces Prigozin said. That transition, coupled with notably low tempo and movement from Russian forces in the area, leaves an opening for Ukraine to potentially retake Bakhmut according to an assessment from the Institute for the Study of War. While Bakhmut may have been a symbolic win for Moscow, Ukrainian officials such as President Volodymyr Zelensky still assert that Kiev's forces are active in the city limits. Now they're saying those Ukrainian troops can continue to make gains around the city and stage a semi-encirclement to drive Russia out according to the Washington Post. Nonetheless, the attrition-style fighting of Bakhmut has left Russian forces exhausted ahead of Ukraine's long-anticipated counter-offensive.


Hello, everyone. Thank you for joining this talk. Today, I'm going to talk about how we can combine infrastructure as a code with GitOps and how we can manage your multi-cloud infrastructure. And I will introduce a new concept, and on that way, I will introduce two new tools. Short about myself, my name is Fasen Salahi. I work as Cloud Engineer, Cloud Consultant at Liquid Reply. Short about my company. We are a company based in Germany, and we are highly focused on cloud native development. We help our customer to build, design, build container orchestration platforms, and also to help them under way to the cloud native journey in topics like cloud native development, and especially FinOps. What are my focuses? Like my company, I like to design and build cloud and cloud native infrastructures. I'm highly focused on automation. I like to automate boring stuff that I'm daily dealing with them. And I also like to make myself busy with cloud platforms. I have OpenStack background, and now I'm highly focused on container orchestration platforms. What I do beside my job, I've been part of Combined Release Team since release 122, and I really love it. I do it beside my job. As next, let's take a look where we are standing when we are talking about multicloud infrastructure management. How does it look like these days? I think let's talk about infrastructure as a code. It's one of DevOps best practices. It's focusing on avoiding environmental drifts. It means every time I'm going to deploy the same infrastructure, I'm going to not to face runtime issues, missing dependencies. So infrastructure as a code is lying on the pillars of DevOps. It means it's using Git as a single source of truths, where our code is lying. And we are using GitLab CI-CD pipelines to automate the deployment and provisioning this infrastructure, and also maintaining the lifecycle of these cloud resources. I'm sure most of you are more or less familiar with this picture. We are starting to manage multicloud infrastructure, or even against one of these providers. Some of these tools, now we have in our landscape, they are neutral, like Terraform, Plumi, and some of them are highly opinionated, because they are developed for a specific cloud provider. I'm sure you have come to this point, you are using Terraform to provision an infrastructure, and you are getting this point that Terraform cannot handle all the requirements, cannot tackle all the dependencies I want. So in my case, I'm ending up writing really long, terrible, dirty shell script inside Terraform, and using AWS CLI to achieve what I want. But this is like really painful. This is this heterogeneous setup that I think most of you know from your own companies. I have seen by lots of customers. At some point, it's really painful. Let's look what challenge this brings to us. First, as I said, one tool is not a silver bullet to tackle all the requirements. It cannot be, because some of these APIs of the cloud providers, they are highly opinionated. They are developed for their own toolings. And our infrastructure as a core tools are not talking to the same API all the time, because these APIs are changing all the time. The other challenge I've personally been dealing with lots of customers, someone is going and deleting in a VM in AWS stack. And my tool is not reconciling. There is no reconciling working. So if someone deletes one VM or a three bucket, the next time I'm going to run Terraform plan apply, it's going to break, because it says, I'm sorry, a VM is missing. I don't know what happened. Someone deleted my mistake. So this is a pain. And such a setup, as we saw, brings complexity for the platform or SRE team. And it puts them on the back foot, because they are limited. They are limited in terms of resources to deal with such a complex setup. And if one developer comes with a specific request like I want this and that specific cloud resource, please do it for me. They cannot handle it. And the other last but not least, I know from my career, developers are not interested into managing cloud infrastructure, because they are, from my point of view, they are our customer. They don't want to deal with any tooling. They just want to get the resource and get the benefit of it. They don't want to be involved at any part of creation or managing the life cycle. I would like to take you first to a definition of GitOps. Let's take a look at what is GitOps about. Let's make a recap. GitOps is born in cloud native. It's the declarative way to get to continuous delivery, continuous deployment. Basically, it's born in Kubernetes. So at the end, it means nothing than Kubernetes manifests. The core part of this concept is Git as a single source of truth. All our manifests, all our configurations are lying there. And the other integral part is the GitOps operator, which is based on Kubernetes operator concept, is a tool that's running on a target cluster and is reconciling all the time with the Git. It's the way how you describe your system. And as soon as there is a push into the Git repo or there is a pull request accepted, the tool gonna detect it and will update all the resources in the target Kubernetes cluster. Let's take a look at the tools that we have in the landscape. So Flux and I will go see they are most well-known tools in a CNCF project, widely used by everyone. But today I'm going to talk about Fleet. Why Fleet? Why I've chosen Fleet? Fleet is a GitOps engine from Suzeraincher. They have this mentality in their mind that Suzeraincher is the central platform for managing not only the workload on top of Kubernetes cluster, but also managing many clusters at a scale. So this makes it like really nice tool to give it to SRE team to manage huge multi-cloud setup. Short about Fleet, like the other GitOps operators, it has a controller which is running in a Kubernetes cluster and this controller is all the time, reconciling with the Git and checking the state of the Git. And as our classical CI part, as soon as a developer makes changes in a Helm chart or container image, it will be built by our CI CD pipeline. It will be pushed to the Artifactory. And one of the features that just came out in Fleet is that Fleet is also able to check the state of the Artifactory to see which images are lying there. If there's an update, it can detect it, but it won't be applied till the user, like more specifically allows it. And at the left side, we have our Donacrim clusters. So in terms of Fleet, Donacrim clusters are our target clusters. They can be bundled into different type of groups, stage-based, provider-based, and that's how you can deploy Kubernetes application scale. So at the end of the day, there is one agent from Fleet which should be run at the target cluster and that's how the agent is always in contact with Fleet controller and asking, give me a job to do, give me a job to do. And Fleet says, okay, there are changes in the Git repo, so yeah, update the target cluster. So short about Fleet Bundle, Fleet Bundle is nothing than a Kubernetes manifest or Helm chart or customized configuration. I'd just like to point to this tweet from Casey Hartover from 2019, where he envisioned not only deploying Kubernetes workload using GitOps on Kubernetes, but also managing infrastructure using the same concept. How we can achieve this? How we can achieve managing infrastructure using GitOps? So we have to take a look at the principles of GitOps, which is declarative semantic. So we have to be able to define cloud resources with the same semantic. And that's where we are going to benefit the Kubernetes operator, which is the approach to implement this concept. So based on nothing than extending Kubernetes API using CRDs. One of the tools to achieve this goal is a crossplane, is based on the same concept, and uses the same extension of the API and it enables us to define managed resources with CRDs and create highly opinionated controllers for different cloud providers. With crossplane. So having such a tool, which enables us to also define our infrastructure using custom resources, it's creating opportunity. We are not always interested into creating Kubernetes cluster. We are, sometimes, our applications, they need to talk to other services. And why not taking the benefit of managed services from cloud providers? Like S3 bucket, message queue, message pop, or a database like Aurora or Postgres. So this tool enables us to create a self-managed layer. So it enables the developers just to use the same API to talk to cloud providers and define the dependencies. And recently they introduced a new project called TerraJet. TerraJet enables us to use the existing Terraform providers to build crossplane providers. So we're using the underlying existing providers to benefit the existing ones, not to write the new ones. Let's take a look at the crossplane building block. At the heart of this concept is Composite Resource. It's nothing than the way how it enables us to create the schema of our cloud resources. This is exactly how when we want to create the managed resources, it defines how this managed resource looks like. The other important component is Composite Resource definition, similar to CRD, but a bit different. It's how we define the type and the schema of this Composite Resource. Actually, it enforces all the time when we are creating a claim. So I will talk later about it. Every time we want to create the managed resource, this is the Composite Resource definition to enforcing the semantic and type of the resource. Composition is nothing than one-to-one mapping between the managed resources in terms of crossplane and the real cloud resources. It's the component that knows, okay, when I want to create RDS instance, I need to talk to exactly the real cloud resource. And the provider is similar to Terraform provider, so it's how you are talking to any specific cloud provider. There's a controller running, and your Kubernetes cluster is able to talk to your target provider. So imagine such a concept enables us to create the self-managed service platform. At one side, we have the dev team. They don't really care about what's happening at the background. It's like, let me give you an example of persistent volume claim and persistent volume. Persistent volume in terms of storage class, back-end storage are mostly managed by SRE or platform team. And mostly developer team, they have no idea or they don't want to be involved at all about what's happening in the background. So they just want to create a claim, like persistent volume claim, and crossplane will take care of creating the real cloud resources. This is a great opportunity just to put both of this team under the same concept and the same platform, and this enables the platform SRE team just focus on the background and taking care of the definition of resources or creating configuration or a specific bundling of cloud resources. And at the end of your site, dev people can easily use and create resources. How does it look like one of these custom resources? This is example of a cloud SQL instance from GCP, it's nothing than a Postgres. So this is like the claim and at the end, it's gonna be a cloud SQL database in GCP. So Navina, Felit and crossplane, let's put them together. Imagine the first photo I showed you, we had a heterogeneous infrastructure management platform with different tools for different cloud providers, as I said, some of them are highly opinionated. We have one central comitis cluster, Felit is running and at the same time, crossplane is deployed. Felit is taking care of deploying crossplane, so if you want to change something in terms of crossplane version configuration, it will use the same concept, the configuration of relying in the git, and as soon as you change something in the configuration of crossplane, Felit's gonna detect it and it will update the crossplane. So this enables us to talk to one single API at Universal API, which is Kubernetes, in a declarative way, we know YAML manifests. In the same way, we can create cloud resources. So this saves us from the hustle of using different languages, different tools, and just to talk one API and get the benefit of the declarative manner. I will show a short demo, but before jumping to the demo, I will just talk about what I will show in this demo to you. So my central cluster is running in the AKS cluster and Felit and crossplane are deployed and I will show how we can create a JKE cluster, and then gonna be a fleet agent running there and at the same time, gonna be a Cloud SQL Postgres created. Shortly, I will show how the git repository looks like. So as I said, I'm using the fleet to deploy crossplane, so this is how it's defined. So using the custom resource definition concept of fleet. So I'm just pointing this to the Helm repository and saying, okay, I want this chart with this version, and please deploy specific cloud provider packages when you're deploying crossplane. Also, I would show how these claims or custom resources they look like in terms of GCP. So this is a really simple hello world example how you can create a JKE cluster using crossplane. So yeah, it's simple, straightforward. And I will also just go and show the Cloud SQL. Yeah, we saw it in the slides. I will just zoom a bit. Can everyone see it? Okay. Let's take a look at crossplane. So the crossplane is running. So as I said, I've deployed two providers, AWS and GCP. Yeah, as you can see, they're running and we can check the state of the providers. Just short K standing for QCTL just alias. So as you can see, both are the providers are deployed. They're healthy. And as next, I would just like to create a secret to be able to talk to the GCP. It's standard JSON secret, just like formulated inside the Kubernetes secret. So I'll just have a, just let's take a look. Setup provider. I just have a shared script. It deploys the secret, nothing fancy. So it's already there, nothing changed. And I will just show you another Git repo, which will be just for the sake of this demo. So one of the custom resources from Fleet, so I'm just defining another Git repo. With Fleet, you can always specify specific passes and I'm just pointing this to JKA cluster and Cloud SQL. Just I have another shared script, which actually registers this repo. I'm just going to use it. So it has been created. So let's take a look at what's happening there when I, okay, short about what's happening right now. This bootstrap, yeah, we can ignore it because it's for the initial setup. But the second one, you can see this new Git repo, I just deployed, yeah. So the hash, it's standing for the hash commit. So that's coming directly from the Git repo. And what's happening, you see, it's saying it's not ready because it's now talking to the Cloud provider. It's trying to create two resources. So as you can see, now it's trying to create. Most probably I will just jump into the real manager but now it's trying to create a node pool for the Kubernetes cluster and also trying to create the Cloud SQL. So it won't satisfy till it manages both the resources and then you will see it will just be idle. So in the meantime, we can take a look at the real clusters. What's happening there? So it's in the provisioning state, so it's synced but it's not ready. We can also take a look at the Cloud SQL. Same, it's synced but still trying to create. I can jump into the GCP console, just need to refresh. Yeah, it's spinning up the cluster. Most probably, yeah, it's deploying. And if you take a look at the nodes, yeah, it's starting to provision the nodes. It will take a while and let's take a look at the SQL part. Yeah, it's already there, it's already there and running. So this is state of reconciling gonna continue till both of the resources are healthy and running and then it will just, as I said, it will be satisfied till you make the next change in the Git repo. We'll just jump back to the slides. So I would like to summarize my call. So as we saw, this creates a great opportunity to have a common API, a common language and the same workflow for both of the DEF and SRE or platform teams, they can use the same Git repo and everything gonna be gatewayed using the pull request and it's gonna be really transparent for both sides, which resources have we deployed, what is the state, because everything is declarative relying in the Git repo. And the principle of least privilege, so it's my own experience from my customers, don't give Kube CTL or any kind of CLI to the DEF team because this kind of enter cares. So Git is the best place to direct them. So please use the Git, create your resources, we're gonna see, we're gonna gateway it, we're gonna look through the pull request and keep their fingers away from any kind of command line. So as we saw, this one I help us to avoid having different setups with different configurations because everything is declarative, everything is managed with the Git so we can always see the state and always the Git operator is reconciling with the Git and the state of the system is up to date. And this also good opportunity for managed data operations like enforcing policies like LPA or Kaikai Werner or network policies or any monitoring observability, tools can be deployed with the same concept. At the end of the talk, I would just like to say we have two more talks in the KubeCon from three of my great colleagues. Please join our other talks and come to our booth, let's connect and great to see you there. Thank you. Are you willing to take questions? We have a few minutes. Any questions, anybody? Hey, hi, this is Anil. How cluster APA versus fleet in the even like, I know cross plane, I got it, but cluster APA versus fleet, any insights you can give? To be honest, I took a look, but I think there's not that much movement in regarding of cluster API, but I can see a good opportunity there that it can be integrated. Anybody else? Any questions about the TeraJet? TeraJet? Did you have a try with Opus Tech because it actually is one of the provider that is missing for the cross plane? To that end, yep, I was just checking a couple of days ago for this. I think I saw example for the main cloud providers. I was looking for KVM or Libvert or Opus Tech. Unfortunately, they are still in the beginning, so I hope there are going to be more movements there. But yeah, that's, I think it would be great, but I think it's coming. I sense a theme. There's, it's almost like GitOps is new or something. Anybody else? All right, awesome. Thank you so much for your talk. Thank you.


A few months ago on this channel, I reviewed a little-known fantasy series called The Dinosaur Lords. It's a good series. Solid characters, a fun setting, epic battles, a core mystery that the audience can theorize about, all the sorts of stuff you'd hope to find in an epic fantasy. It has one problem though. A problem that many people just cannot see past and would ruin the entire thing for them if they read it. You see, it doesn't have an ending. The author planned for six books, released three, and then he died. And that's it. None of us will ever know what happens to these characters, nor will we get answers to the nature of their world. It's heavily implied that the story takes place on the planet Venus after it's been terraformed and all the magic we see is just advanced technology. We'll just never know how or why this situation came about. We'll never learn what the goal of the Grey Angels is or what happens to our favorite characters. I know that sounds like a spoiler, but it isn't. It's implied very early in the first book and no one in universe ever confirms it. We've all been in a situation like this before. I'd be amazed if even one viewer hasn't. Some piece of media, particularly long ones that are released in parts, never finish. For one reason or another, things just never come together and we're all left hanging at the end. There's no climax and no resolution. Things just abruptly stop before they were supposed to. I'm not talking about rushed endings or endings that are bad for one reason or another. I'm talking about things that don't have an ending at all. Things that are left unfinished. What happens next feels like a lost memory. A hole in your knowledge that seems like it could be filled, but when you reach out to grab it, it vanishes. It isn't surprising this happens. When you think about it, it's more surprising that some of the things we love get made at all. A large number of factors need to come together in order for these to exist in the first place. For a book, you need the writer to get the inspiration they need to start, the motivation they need to continue, the time needed to write it, and the technology to get it out there. And that's not even starting on the nightmare that is publishing. Keep in mind that in a lot of cases, all of this has to happen while they have another job to support themselves or while they're taking care of kids or while some other obstacles get in their way. All of this makes it so easy for them to give up and never produce the story we love. For something the size of a television production, the complexity is orders of magnitude greater. They require money, actors, directors, writers, and a sufficient audience to avoid being prematurely sent to a farm-up state. After all, it is a profit-driven enterprise. It only takes a single wrench in one of the many gears to grind the whole thing to a permanent halt. We can all imagine something great. The real test is manifesting it into the real world. When the harsh light of reality strikes your creativity, that's when things start to go wrong and something unforeseen prevents you from completing your work. Until recently, it seems that this would be the fate of manga series Berserk. Creator Kintaro Murad died and it seemed no one would be able to complete the series until the reigns were handed to someone else. Will they do a good job finishing off the series? I don't know. I certainly hope so. The future is a fickle mistress, though. The new guy is the only one who heard the ending, allegedly, so he's in the best position to finish things off. That still leaves things like the art, scene composition, dialogue, fight choreography, and pacing that could go wrong. Only time will tell if things work out here.  A similar situation worked out alright for Wheel of Time, at least. Robert Jordan died before completing his magnum opus, but he had extensive notes detailing how he wanted things to go, and more importantly, he was close to the end when he died. Brandon Sanderson only had to write the last book, or rather, he was supposed to write one and had to split it in three. The last three books, which in total make up maybe a quarter of the total series word count, because Robert Jordan wasted about three million words describing skirt smoothing. That was an unusual case, not the norm by any means, but most fans were grateful to have it. There are people who complain about the Sanderson books, and that's fine, there are criticisms to be made. His style is different from Jordan's, even when he tries to emulate it. A few characters get pushed to the side, and by his own admission, Jordan would have written a better ending. What confuses me are the people who insist we would have been better off if the series never finished. There aren't a lot of them, but they exist. Would they truly be happier if they spent their entire lives never knowing how things wrap up? I seriously doubt it. Sure, they could guess that the good guys win and the bad guys lose, and they might even be correct. All the small details would be lost, though. Even if the same thing happens in Epic Fantasy over and over again, it happens differently every time. And it's the details, the character interactions, the jokes, the small moments that make it worth experiencing. That's the whole message of the series.  Some would argue that no ending would be superior since you could just imagine your own ending with blackjack and hookers. Thing is, you can do that with a bad ending too if it really bothers you. There's no stopping the power of imagination. There are some cases where we don't get a full ending, however we do get a basic outline of what was supposed to happen. My name is Earl is a great example of this. For those who never saw it, it was one of the best sitcoms of the aughts. It followed a character named Earl who had previously been a dirtbag criminal and decided to turn his life around by making a list of everything bad he'd ever done and making it up to people one item at a time. It was funny, heartwarming, and had a storyline that wasn't just zany episodic antics. Unfortunately, we never get to see Earl complete his list. Luckily, the creator, Greg Garcia, did a Reddit AMA where he gave the outline for how things would have ended. Basically, Earl was going to get stuck on a difficult list item and run into a stranger with his own list. He would then learn that his crusade had started a chain reaction of people making up for the wrongs they committed and that he'd finally put more good into the world than bad. Then he'd tear up his list and walk off into the sunset as a free man. Sounds great to me. It would wrap up the story in a satisfying way and let us know that the character's struggles were all worth it. I hope we can get something similar for the dinosaur lords, though I'm not holding my breath. This is better than nothing, at least in my opinion, but still unsatisfying. It's like reading a Wikipedia synopsis of the story. We know what happened in a dry, clinical way and we miss out on all the minute details that make a story a story. It's like an action scene. I could tell you that Jackie Chan fights a room of bad guys and wins, which would be unsatisfying, or I could show you the entire fight complete with the stunts and silly antics that make it worth watching. All of this is, of course, assuming the ending will be good or at least passable. It's easy to imagine a vague finale that checks every box you want it to and doesn't screw it up unlike those professional writers and directors who are clearly less talented than you, person on the internet who can barely type up a comment that makes sense.  As long as it only exists in your mind, it's perfect and untouchable. No one can criticize it because it hasn't had to deal with the deadly weapon known as other people's opinions yet. When the rubber hits the road, people find things to complain about. Dialogue, prose, acting, special effects, and a hundred other things that aren't covered in a basic outline can all go horribly wrong. And the way people use, quote, the writing as a way to describe everything they dislike about visual media, like movies and video games, is meaningless. They use it to criticize directing decisions all the time, which means many of them don't know what words mean and their opinions are worthless. Even in books, quote, the writing is too broad to say anything useful. Do you mean the dialogue is bad, the characters are inconsistent, the descriptions are confusing? Criticism requires clarity to be useful, otherwise it's just people complaining about something they don't understand for reasons they don't understand. I almost never use the cliched phrase, good idea with bad execution, because it's pointless. It's always about the execution. Literally always. On the plus side, the internet has allowed us all to discuss things we love with like-minded people. On the minus side, making the media you consume a large part of your identity seems to make you view any deviation from what you consider proper as a personal attack. The fact that some people genuinely want entire book series or seasons of television to be remade just because they didn't like them is the highest peak of narcissism that humanity can achieve. Refusing to touch grass has convinced you that your opinions are super important and that the arcs of fictional characters is super serious business. You think that everything has to be catered to you and if it isn't you need to throw a fit until someone changes it.  Being upset or annoyed is fine. Expecting the world to cater to you at all times is not.  No discussion on stories that end prematurely would be complete without mentioning fanfiction and other internet fiction. Oh yeah, we're going there. They're notorious for this sort of thing specifically due to their unusual serialized nature. Most fanfiction comes out one chapter at a time. A single piece being released every week or every month or just whenever the author feels like putting one out. In order to keep the audience's interest, things have to happen in every update. This leads to wonderful things like plot points being hinted at and unceremoniously dropped later or characters angsting for far longer than they should be because the author doesn't know what to do next but they're on a schedule. It also means that a serialized fanfiction or TV show has different pacing needs than a book series or a binge model streaming show but no one seems to want to acknowledge that. After all, why would you want to trim out the boring or unneeded parts to strengthen the whole when you could just produce a flood of mediocre content with little thought and pray that some people like sifting through it all? I see you there, Ubisoft, go away. There's a specific fiction press story I always think back to when this subject comes up. It's called Rose by Y.S. Wong. The story is complicated but suffice to say it involves a magical revolution against an evil government in order to make a Japanese teenager the Queen of England. You're just going to have to read and find out how that happens yourself. The good news is that the Polish are oppressed in this world. The bad news is that everyone else is too and so the heroes have to fight against that. It's a great read, one that was updated like clockwork for a long time. Then there was an author's note about going on hiatus for exams and... nothing for a whole year. Then we got four chapters which were actually a flashback sequence for one of the main character's backstories that didn't advance the plot. It gave me hope that we might get back into the swing of things. That was over six years ago now and Wong's profile hasn't been touched since. Rose is actually the sequel to another story called Orchid. So the author clearly has the determination to write an entire book. It was relatively popular too so it's not like there was no interest. Whatever the reason, he just stopped updating. Hope he's doing okay, wherever he is. Did I make this entire video just to complain about never getting to read the end of a completely unknown internet story that no one else has thought about since 2016? Maybe. If this were a regular book series, we just would have gotten the first one and never gotten more. Which means we would have had a semi-decent ending where things wrap up, kind of. Instead we get a much bigger cliffhanger. This likely wouldn't have happened if it were a professional project, even if it did release serially. There's too much money at stake for an author to just give up, especially if this is their job. People always bemoan how things get cancelled when they don't make enough money and how things would be better if media was just made for the sake of art. No one ever mentions how relying on board creatives to get their asses in gear with no promise of reward is a recipe for disappointment. TV shows have been cancelled prematurely for decades and it's basically a meme that good ones always get cancelled prematurely. Netflix has been notorious for this for years. However, they don't release serially. Entire seasons drop at once so it's more like a traditionally published book series than a serialized fanfic where things are given to you in big semi-self-contained chunks rather than small pieces. The problem is that a season of TV takes a lot more money, expertise, and labor to make than a book. This means there is less room for error and if it doesn't make enough money it goes down the tubes and because they're released in big chunks that need to be completed before they drop there's no time to make any last minute changes if it doesn't have an ending. With traditional TV, where the last few episodes of the season are usually being filmed while the early episodes are still premiering, they sometimes have time to slap together some rewrites and bring things to a conclusion. Not a satisfying conclusion necessarily, just a conclusion. Arrested development is a good example of this as long as you forget about the revival, which you should. The American version of Life on Mars is another one. The show got cancelled before the end of season one so the crew got together and rushed out a resolution. Is the ending good? Not particularly, but at least we get an answer to the show's central mystery. We aren't left hanging for an eternity. Netflix can't do this so when one of their offerings is cancelled it's gone forever and you'll never know what happens next. The Chilling Adventures of Sabrina is a deeply flawed show. It has something going for it that many Netflix originals don't though. It gets an ending. The series finale is... not great, but it wraps things up. Character arcs are completed, the final villains are taken care of, the day is mostly saved, the heroes get to live happily ever after, sort of. There's a sense of closure, if nothing else. I could talk all day about the problems that show has, but they are tempered by that feeling of closure. I would recommend this over something like Daybreak, even though I like to daybreak a lot more. Because that only got a handful of episodes before leaving us unsatisfied. Blueballs are painful. Metaphorically, of course. When something is put out one small piece at a time it takes less to interrupt it than if it has to be put together all at once. Even something with a low cost of entry like fanfiction. Since it's all being written for fun, usually, and there's no payment beyond attention from your own small corner of weirdos on the internet, it's easier to lose motivation.  Next thing you know you haven't updated in six months and your audience never finds out if your high school AU version of Severus Snape will live happily ever after with Dobby the Janitor. If there's no ending, it's hard, if not impossible, to recommend it to someone else. It's a frustrating way to make you feel like your time has been wasted. Without closure, we tend to forget about everything that came before. Even when we don't forget, we don't know what happens next, that knowledge is closed off to us forever. We can theorize and discuss it and fantasize, but we'll never know. It's like asking where Jimmy Hoffa is buried. Fun to talk about, depressing when the truth sinks in. And that's the tragedy here. The tragedy of knowing that we're all ignorant and we always will be. Is there a lesson to be learned from this? Be careful with cliffhangers, I suppose. Don't start something you don't think you can finish, might be another one. Sometimes ending out of nowhere is better than the alternative, where it just goes on forever with no end in sight until it becomes terrible and everyone loses interest, save a small cadre of hardcore fans who get upset by the bumbled ending. Better to fade away than make a fool of yourself in a bid for attention, I suppose. Maybe some story concepts are best when confined and don't get turned into long series, whether we're talking about books, TV shows, or anything else. Not everything needs to be a long series. Sometimes things are better when they're released in one piece. If that means making it shorter, so be it. Entertainment of all sorts has been getting longer for years anyways. The average length of Hollywood movies is 17% longer than it was in 1990, and books have been stretching to a ludicrous degree.  Those are supposed to be shorter and easier to consume. Maybe there isn't a lesson at all and I'm just complaining for... I dunno, this many minutes. I started this channel specifically because I wanted people to complain about slash laugh at terrible books with and none of my friends were available. Having deeper discussions and trying to discern deeper truths is great. It's just not needed all the time.  Let's all bond over that. I didn't have a place to insert this in the script, but did you know that Daenerys has been stuck in Nereen since Bill Clinton was president?  Huge thank you to everyone who watched this far. I'm sure everyone who's leaving a comment telling me to kill myself definitely made sure to watch the whole video. So thanks to them as well, and all the names you see on screen right now, these are my patrons. So thanks especially to my super ultra great patrons who are Oppo Savilainen, Olivia Rayan, Brother Santotes, Buffy Valentine, Carolina Clay, Dan Anceliovic, Dark King, Dio, Echo, Eevee, Flax, Great Griebo, Carcat Kitsune, Liza Rudikova, Lord Tiebreaker, Madison Lewis Bennett, Matthew Bodro, Microphone, Peep the Toad, Return of Cardamom, Robbie Reviews, Sad Martigan, Celia the Vixen, Tesla Shark, VaVixus, VaVictus, and Wesley. I'm not redoing that, I don't even care. If you want to get your name on here, be sure to join my patron page. If you can't do that, then please just write this video and comment on it. Subscribe, all the things I'm supposed to say here. Thank you, goodbye.


لنرى لك بعض الذين سنعطيك ونعطينا مرحباً لنا مجموعة of the greatness of this day of celebration and why we celebrate it حديث is from Amir al-Mu'mineen صلى الله عليه وسلم وعلي speaking with Odaifa part of the حديث which is مشهور from the names that is given to عيد الزحراء or فتح فرحة الزحراء Amir al-Mu'mineen says يوم الغدير الثاني the ninth of ربي العول is the second ايد الغدير so from here straight away we understand that ايد الغدير or the event of غدير in itself is made up of two parts one part is the eighteenth of ذلهجة and the second part is the ninth of ربي العول and within this there is كلم كبير there is great words and there is great interpretation in regards to the similarities and the conjunction between the ninth of ربي العول and the eighteenth of ذلهجة such that the eighteenth of ذلهجة is completed with the aid of ninth of ربي العول and the ninth of ربي العول is completed with eighteenth ذلهجة the one who celebrates the ninth of ربي العول is because he has understood and accepted eighteenth ذلهجة and vice versa for you find Amir al-Mu'mineen states ninth of ربي العول يعني يوم الغدير الثاني in another description يوم الرفع القلم the day the pen is raised and there is تفسير about this يوم البركة the day of blessings يوم الثارات this is the day of vengeance يوم يستهب فيه الدعوة or يستجاب فيه الدعوة the day where دعوات are accepted ويوم نزع السواد نزع السواد what you are elaborating towards it is the day of removing the black clothes يوم ندامة ظالم the day of regret for the oppressor يوم فرح الشيئة the day of happiness ويوم قتل المنافق the day where the the منافق was killed sent towards جهنم وبأس المسير يوم حدم الضلالة this is the day of the destruction of misguidance and you find that so on so forth يوم نصر المذلوم كل one of these names upbeat a certain particular dimension of this great ويد فلAct العراحة الزحراء that occurs on the ninth of rabeel


నార్లులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులులుల it also teaches us life lessons so horse riding is not just a sport it can be it is also a disciplinary disciplinary method and here we can learn not just the sport but also about life so how long have you been here for 13 years how long have you been here how did you start I started horse riding after lockdown at first I was scared I was very scared but then after a period of time I realised horse riding is not just a fear factor every child has that fear factor but then whoever can conquer the horse can excel in horse riding at first when I started I did not know anything I started horse riding what was your coach what inspired you to follow me in this sport it has always been my parents my dad and my mother they have always encouraged me they have always encouraged me they have always encouraged me to try but just try it once my dad is actually into horse riding he is a polo player my mom also has some experience in jumping so these are my coaches and they inspire me they encourage me to encourage me you can pursue this sport so I started because of them and I am still going because of them so thank you for telling us so many things so let's say hi to the audience hi so let's say hi to the audience hi how old are you five that's it how many horse riding have you done I have done a lot not a lot are you scared at first not at all I am scared I am scared I am scared of my mom and dad at first I have told them I have told them so many times I have tried I have tried I don't want to go horse riding I am scared because of my mom and dad ok I am afraid I don't want to go I am scared enschaft à ṭhārī Ṭhādhaṁ ṣikāṃ ṣiushaṁ ṣoṣā ṭhādiṣṁ ṣalā-eeṣāṁ  Dieu Jī spoke in the lady's back-seal థరారికలవా థాన అచగ౨నertonమం పచొ了. అదబిమం నౌవా అద౪లనదలి.  ఠ్ఎలుషరె. న于 1950ocide 0$ నji alcanz loss of ads. బena ధరనీ పతిలు చారకీ. బicamenteబ్లు చాలంение Wrestle�ైబది. మర వ commer� వ్తిషమరోనీ. మరపరదిక Futi drawings, . కింపులా, ఇacon inclus క Audience that ಕಾಳಿರು ಕಲ್ತಿ,್ ಇಣಿಂದಯಂило криಽಕ tankh ಪೃಜಎ಺ಕಾಡುತ ಬೇರೂತಿಕೋದಗದ್raw ಇಗಾಡಟೂವೈಲಂಗಕ್ನರಂನದರೂಣ delivery ಮೀಗಳರಲಾಲ್ ಎಸಾಡಡಗಿ ನಾಗರೇಷಾಧರಮ್ ರಶುಳು ಜಾಯ dévelop�ಕ ಆಲ್ರಿ This one. Let's eat... But what are we eating? Why won't you eat? If mom and dad want, we won't be eating. We won't be eating, we won't be un- Club Q Richita, is there a limitation when it comes to eating? Actually in Organisation part 1 when horse riding is crossed over the horse or competing So, one sense of relief for horse riding I think it should be as a moral etiquette ధర్ా chunky మార్ిలేమి రాతిరిే. అలిনి చైమతాస్ఇ .లానఫం sûr జినిఇపె బికేక్క్దాసు కాన So that pleasure factor, I've never wanted to go to a vacations elsewhere because Khusita mauro ghoda pakhre yachi, toh aav koti kain ke jubi. Acha. Jyot duyta hi vacation, amma odisar to duyta vacation chale gote crop cutting holidays and summer vacation. Si duyta kore apana bahar gu jaanti. Acha. Ke besimti ghoda chole labile, ki ita vara e-sports activity re kebe kiche hindi chottomot accident hi chi? Ki podi jayi chanti, ki kim hindi kiche? Hors riding as a sport, risk factor to achi. Mauro gute incident hi thi la, mu nasi kre thi li, sethi training no thi li, gute fall hi thi la mauro, mu stretcher through hospital ku jayi thi li, 7 days bed rest, hollipar na thi li training kore pa. But then mauro regret, main regret ta seita thi la, it was not a falling, pain ro kiche regret no thi la mauro. Regret kali seit insha rathi la ki mu aau riding 8 time period re kore parni. Toh incidents, accidents hot hai hos riding re, but then I am never scared of falls. I am just scared ki, I am scared of giving up after a fall. Acha, jayite ebe jitiki aparangora achhanti pila maani ki sanga maani jo achhanti, keba jo classmates maani achhanti, e-sports re ki achhanti? Odisha re, as I said, infrastructure nahi toh, I couldn't find people of my age at least, jo maane hos riding re tha hanti. But then if odisha infrastructure tha, infrastructure tha assi jibar, then I am pretty sure, mawais ro bohut pila maani, encourage hebe e-sports re ase apai, aau maathe bhi training pa yawari time ta mili ho. Toh that ebe jayi toh I couldn't find people of my age in this. Apana koni chahun chahani, apana ebe covid summeru, e-summer pachon toh hos riding re, time dei chanti, kheli chanti, medal bhi jitiki chanti, apana unku koni dharkar, ke odisha re kono heba dharkar, kon chahun chahani apana. Odisha re, I would like to request the government ki just some basic infrastructure if we could open, odisha re, jadi like some horses in some land for this stable for training, toh I am pretty sure odisha would do way better in equation field. Neishin hapare, tebe amathe thinka saito auri anne kathaba samayo aave ka brek rao. Saskutika Rajadhani Rukh. Rajadhani Rajadhani. Got up? Bhubneswar. Crime? Politics? Entitonment? Sports? Business? Jibhan Jibika o Sanghar Saraw. Aakhe dekha kahan. Twin City bada khabar. Prathe dina sandhya panchata thiris ke bada aar gasne ujre. Jai Jagannath. Chaka ki sabude kuji. Thadhanan auri anka naya ra ladhi. Khiye bhi amara guadhiya bandhu nufanti. Khiye bhi pati re tundi dehi basu. Kintu aame kahibu roko. Havise pa gadi baapain. Rajanetan ko aakhada. Samarthana maagi baara aadha ra. Odisha ra apara sambha bana. Samay bo dha jojana re sambha bo gadi baapain. Hav Rajanati kaprati jogita. Chapisra maha ladhiye. Nua Bharatra ek a sambhru dhaudi saapain. Aame hai bu. Jati aapana ko ama video ki bhalla gila. Te bhi ama channel ko like, share and subscribe karipa ku jamabhi bulantu nahi. Brake pari kajukram ko saagat. Riddhi, jitvale samaya mele pathha pada, pathha skool ro asla pre karn karo. Munda chakos khaata fritik tiri dekhe. Kato. Acha. Tapare? Tapare. Khe li ba ku jae. Ii horse riding kitha pala kora? Dilli re, nasik re, bombe re, kar kata re. Acha, athana karo jimti, apana karo horse re na ho chu rudraksh. Umar ho horse re na ho. Gul. Gul? Acha, na gul ko kimti dakko? Gul ko reins khi chiki. Acha, kari kari ki. Kimti kimti aothare? Sa suni? Acha, tami taro kair niyo? Haa. Tamu kumti dakkili? Sa suni ki asse pakko ku? Haa. Acha, aur riddhi, aus kaun tamu karibapai? Khua hai pitha ko. Khua hai bhi diyo? Kaun khua? Ghoda. Acha. Sakha hai? Haa. Acha, tamu koi mitha, tamu ghoda ko bhi mitha pasan. Acha, riddhi. Acha, riddhi. Amu koi ghoda slokko, ghoda sundar slokko, kai ki suna illa, e bhi aoguchi amu kai ki suna au. Grimes, kai ki suna au. Grimes. Twinkle, twinkle, traffic light On the corner shining light Red means top Green means go Yellow means Drive very slow Twinkle, twinkle, traffic light Bhoho sundar. Red sita, jodhi horse riding ko tha koi ba seita olympic re bhi aogchi se game. Jodhi amu future plan dikhibapai karo ki chaddi ki santhi ki chi e im aogchi ti kama se tha share karandu aogu jengi ke mithi ee sports ku aogu bada hi bhe. Kan e bhi apana audisar rau chande apana kora pattha bhi aogchi. Pattha puni olga aogute apana jimdi ko chandhi space scientist abhi taba hi ologa pattha nis chindabhapare tha hi aogu kemti mantain koi bhe. Horse riding aogu studies I mean sports and studies these are two very different fields but then mati dihta ja koi re equal interest aogchi to ja chaha hai ba raha hai always I managed to divide both of them mu dihta ja koi equal importance re and olympics as far olympics yes it's my aim mu horse riding aoguri koi aogu chauchi practice audisar India pay aoguri medal study aogu chauchi ee bhe recently Asian games re bhi India has bagged the first prize gold medal after 41 years so that has been a very big inspiration for me as well to yes that accha hai recently apana kote bohi bhi lekhichande se ko bhi sir se bhoogta thila so bhoogra title comic reciders se ita kote story for matri aogchi but it's mostly about Indian history and not only Indian world history like the disaster strategies jota poora world re hi thila prevention like all of that se ita and actually se bhoogre bhi moogote equation jumpari aogchi ridhi oppa jem di koi leki se ita hore podi jai thila tapre admit he thila kiche samaya chale par na thila horse riding kori par na thila simdi tome ke bhi podi chho ke bhi ke bhi ke mdi chotomoto kondya hi chi ke accident simdi ke bhi ke bhi hi chi accident he ni chotomoto kondya bhi se hi chi koti kumar ke miti hi chi ke mdi podi galo bhaiya doos pakri thila guterin amu empty empty se iti bhai se guter par bhakmata da kandila moogote goda moogote bhaiya oppa le podi le acha kandila tapare moog kandili ni acha humda strong gal na hum thale tme bhi jimdi koi lao odisi dancer haba naale dokter aho horse rider bhi aho odisi tamis tamis ikhucho dance bhi korucho aho dokter haba beli kahila bada heki ebetan mo bada heki aha dokter kond bhaiya oppa hi chahun cho mooha bhakku chahun chi samasthanku thikkari bhakku samasthanku dabaibide bhakku samasthanku ejection dabaiku acha tbh ridhya aur asita amatarafru apan konekonek dujana konekonek dhonne baat aho amatarafru bhi bho chara good wishes aho re aago ku jao ita kote different sports takku neki amaro odisar aur naa bhi aago ku nio tbhe ama kajokromu kaasila dujana jaka amasatha jogo dalas tbh anek anek dhonne baat thank you thank you tbh amasatha thile amar aate thi amasatha katha utile tbh aajata same hoichi kajokromu ku ita dokhi ba namaskar samasthgadi bhaap bhai


Chapter No. 56 of Ancient Tales and Folklore of Japan. This is a LibriVox recording. All LibriVox recordings are in the public domain. For more information or to volunteer, please visit LibriVox.org. Recording by Linda Ray Nielsen, Vancouver, B.C. Ancient Tales and Folklore of Japan by Richard Gordon Smith The spirit of a willow tree saves family honour. Long ago there lived in Yamada Village, Serashina Gunn, Shin-Auto Province, one of the richest men in the northern part of Japan. For many generations the family had been rich, and at last the fortune descended in the 83rd generation to Gobi Yusa. The family had no title, but the people treated them almost with the respect due to a princely house. Even the boys in the street who are not given to bestowing either compliments or titles of respect bowed ceremoniously when they met Gobi Yusa. Gobi was the soul of good nature, sympathetic to all in trouble. The riches which Gobi had inherited were mainly money and land, about which he worried himself very little. It would have been difficult to find a man who knew less and cared less about his affairs than Gobi. He spent his money freely and when he came to think of accounts his easy nature let them all slide. His great pleasures were painting kakimono pictures, talking to his friends and eating good things. He ordered his steward not to worry him with unsatisfactory accounts of crops or any other disagreeable subjects. The destiny of man and his feet is arranged in heaven said he. Gobi was quite celebrated as a painter and could have made a considerable amount of money by selling his kakimonos, but no, that would not be doing credit to his ancestors and his name. One day while things were going from bad to worse and Gobi was seated in his room painting a friend came to gossip. He told Gobi that the village people were beginning to talk seriously about a spirit that had been seen by no fewer than three of them. At first they had laughed at the man who saw the ghost. The second man who saw it they were inclined not to take quite seriously, but now it had been seen by one of the village elders and so there could be no doubt about it. Where do they see it? asked Gobi. They say that it appears under your old willow tree between eleven and twelve o'clock at night, the tree that hangs some of its boughs out of your garden into the street. That is odd, remark Gobi. I can remember hearing of no murder under that tree, nor even spirit connection with any of my ancestors, but there must be something if three of our villagers have seen it. Yet again, where there is an old willow tree, someone is sure to say, sooner or later, that he has seen a ghost. If there is a spirit there, I wonder whose it is. I should like to paint the ghost if I could see it, so as to leave it to my descendants as the last ominous sign on the road which has led to the family's ruin. That I shall make an effort to do this very evening I will sit up to watch for the thing. Never had Gobi been seized with such energy before. He dismissed his friend and went to bed at four o'clock in the afternoon, so as to allow himself to be up at ten o'clock. At that hour his servant awoke him, but even then he could not be got up before eleven. By twelve o'clock midnight, Gobi was at last out in his garden, hidden in bushes facing the willow. It was a bright night, and there was no sign of any ghost until after one o'clock, when clouds passed over the moon. Just when Gobi was thinking of going back to bed, he beheld, arising from the ground under the willow, a thin column of white smoke which gradually assumed the form of a charming girl. Gobi stared in astonishment and admiration. He had never thought that a ghost could be such a vision of beauty. Rather he had expected to see a white, wild-eyed, disheveled old woman with protruding bones, the spectacle of whom would freeze his marrow and make his teeth clatter. Gradually the beautiful figure approached Gobi and hung its head as if it wished to address him. Who and what are you? cried Gobi.  If you are indeed spectral, do tell me, if you may, whose spirit are you, and why you appear under this willow tree? I am not the spirit or ghost of man, as you say, answered the spirit, but the spirit of this willow tree. Then why do you leave the tree now, as they tell me you have done several times within the last ten days? I am, as I say, the spirit of this willow, which was planted here in the 21st generation of your family. That is now about six centuries ago. I was planted to mark the place where your wise ancestor buried a treasure twenty feet below the ground, and fifteen from my stem facing east. There is a vast sum of gold in a strong iron chest hidden there.  Never hitherto has there been danger, but now in your time ruin has come, and it is for me to step forth and tell you how by the foresight of your ancestor you have been saved from disgracing the family name by bankruptcy. Pray dig the strong box up and save the name of your house. Begin as soon as you can and be careful in future. Then she vanished. Go be returned to the house, scarcely believing it possible that such good luck had come to him as the spirit of the willow tree planted by his wise ancestor had said. He did not go to bed, however. He summoned a few of his most faithful servants, and at daybreak began digging. What excitement there was when at nineteen feet they struck the top of an iron chest. Go be jumped with delight, and it may almost be said that his servants did the same. For to see their honored master's name fall into the disgrace of bankruptcy would have caused many of them to disembowel themselves. They tore and dug with all their might until they had the huge and weighty case out of the hole. They broke off the top with pit taxes, and then Go be saw a collection of old sacks. He seized one of these, but the age of it was too great. It burst and sent rolling out over a hundred immense old-fashioned oblong gold coins of ancient times, which must have been worth thirty pounds each.  He could hardly realize as true as good fortune, which had come to him. Bag after bag was pulled out, each containing a small fortune, until finally the bottom of the box was reached. Here was found a letter some six hundred years of age saying, He of my descendants who was obliged to make use of the treasure to save our family reputation will read aloud and make known that this treasure has been buried by me Fuji you saw in the twenty first generation of our family so that in time of need or danger a future generation will be able to fall back upon it and save the family name. He whose great misfortune necessitates the use of the treasure must say greatly do I repent the folly that has brought the affairs of our family so low and necessitated the assistance of an early ancestor. I can only repay such by diligent attention to my household affairs and also show high appreciation and give kindness to the willow tree which has so long been watching and guarding my ancestors treasure. These things I vowed to do I shall reform entirely. Go be you saw read this out to the servants and to his friends. He became a man of energy. His lands and farms were properly taken care of and the use of family regained its influential position.  It is the famous painting in the usa gardens today which is called the willow ghost and perhaps it is the model from which most of the willow tree ghost paintings have sprung. Go be fenced in the famous willow tree and attended to it himself as did those who followed him. End of Chapter 56 Recording by Linda Marie Nielsen, Vancouver, B.C. Chapter 57 of Ancient Tales and Folklore of Japan. This is a LibriVox recording. All LibriVox recordings are in the public domain. For more information or to volunteer please visit LibriVox.org. Recording by David McKay. Ancient Tales and Folklore of Japan by Richard Gordon Smith. The Camphor Tree Tomb. Fivri, 10 miles from Shirakawa in the province of Iwaki. There is a village called Yabuki-mura. Close by is a grove some 400 feet square. The trees used to include a monster camphor nearly 150 feet in height of untold age and venerated by villagers and strangers alike as one of the greatest trees in Japan. A shrine was erected to it in the grove, which was known as the Nekoma Miojin Forest, and a faithful old man, Hamadatsushima, lived there, caring for the tree, the shrine, and the whole grove. One day the tree was felled, but instead of withering or dying it continued to grow, and it is still flourishing, though lying on the ground. Poor Hamadatsushima disemboweled himself when the sacred tree had been cut down. Perhaps it is because his spirit entered the sacred tree that the tree will not die. Here is the story. On the 17th of January in the third and last year of the Meireki period, that is 1658, a great fire broke out in the Homiogi Temple in the Maruyama-Hongo District of Yedo, now Tokyo. The fire spread with such rapidity that not only was that particular district burned, but also a full 8th of Yedo itself was destroyed. Many of the Daimyo's houses and palaces were consumed. The Lord Date Tsunamune of Sendai, one of the three greatest Daimyo's, who were Satsuma, Kaga, Sendai, had the whole of his seven palaces and houses destroyed by the fire. The other Daimyo's, or feudal lords, lost only one or two. Lord Date Tsunamune resolved to build the finest palace that could be designed. It was to be at Shinzenza in Shiba. He ordered that no time should be lost, and directed one of his high officials, Harada Kaenaonori, to see to the matter. Harada, accordingly, sent for the greatest house-building contractor of the day, one Kinokunia Bunzaemon. And to him he said, You are aware that the fire has destroyed the whole of the town mansions of Lord Date Tsunamune. I am directed to see that the finest palace should be immediately built, second to none except the Shoguns. I have sent for you as the largest contractor in Yedo. What can you do? Just make some suggestions and give me your opinion. Certainly, my lord, I can make plenty of suggestions. But to build such a palace will cost an enormous amount of money, especially now after this fire, for as there is a great scarcity of large timber in the land. Never mind expenses, said Harada. Those I shall pay as you like and when you like. I will even advance money if you wanted. Oh, then, answered the delighted contractor. I will start immediately. What would you think of having a palace like that of Kinkakuji in Kyoto, which was built by the Shogun Ashikaga? What I should build would be a finer mansion than that of the present Shogun, let alone those of any Daimyo. The whole of the Hagi, shelves, to be made out of the rarest woods, the Tokubashira, kakumono cornerpost, to be of the Nonten, and ceilings of unjointed camper tree boards. Should we be able to find a tree of sufficient size? I can find nearly everything except the last in my own stocks. The camper trees are difficult. There are but few. They are mostly sacred and dangerous to interfere with or obtain. I know of one in the forest of Nekomami-Ojin in Iwaki Province. If I can get that tree, I should indeed be able to make an unjointed ceiling, and that would completely put other palaces and mansions in the second rank. Well, well, I must leave all this to you, Ser Harada. You know that no expense need be spared, as long as you produce speedily what is required by Lord Date Tsunamune. The contractor bowed low, saying that he should set to and do his best, and he left no doubt delighted at so open a contract which would enable him to fill his pockets. He set about making inquiries in every direction and became convinced that the only camper tree that would suit his purpose was the one before referred to, owing chiefly to its great breadth. Kino Kunia knew also that the part of the district wherein lay this tree belonged to or was under the management of Fujieda Geki, now in the Hanzhou District of Yedo, acting as a showgun's retainer, well off, receiving 1,200 koku of rice a year, but not overscrupulous about money of which he was always in need. Contractor Kino Kunia soon learned all about the man and then went to call. Your name is Kino Kunia Bunzaemon, I believe. What may I ask do you wish to see me about? said Fujieda. Sir, said the contractor, bowing low. It is as you say. My name is Kino Kunia Bunzaemon, and I am a wood contractor of whom perhaps your lordship has heard, for I have built and supplied the wood for many mansions and palaces. I come here, craving assistance in the way of permission to cut trees in a small forest called Nekomamirojin, near the village called Yabuki-mura in the Sendai District. The contractor did not tell Fujieda Geki, the showgun's retainer or agent, that he was to build a mansion for the Daimyo Date Tsunamune, and that the wood which he wanted to cut was within that Daimyo's domains. For he knew full well that the lord Date would never give him permission to cut a holy tree. It was an excellent idea to take the Daimyo's trees by the help of the showgun's agent, and charge for them fully afterwards.  If you will assist me to get what I want, I will build you a new house for nothing. And by way of showing my appreciation, I ask you to accept this small gift of Yen-200, which is only a little beginning. You need not trouble with these small details, said the delighted agent, pocketing the money. But do as you wish. I will send for the four local managers and head men of the district wherein you wish to cut the trees, and I will let you know when they arrive in Yedo. With them you will be able to settle the matter. The interview was over. The contractor was on the high road, he felt, to getting the trees he required, and the money-wanting agent was equally well pleased that so slight an effort on his part should have been the means of enriching him by Yen-200, with the promise of more and a new house. About ten days later, four men, the heads of villages, arrived in Yedo, and presented themselves to Fujieda, who sent for the timber contractor, telling the four whose names were Mosuke, Magozaemon, Yohei, and Jinyemon that he was pleased to see them, and to note how loyal they had been in their attendance on the Shogun, for that he, the Shogun, had had his palace burned down in the recent fire, and desired to have one immediately built, the great and only difficulty being the timber. I am told by our great contractor, to whom I shall introduce you presently, that the only timber fit for rebuilding the Shogun's palace lies in your district. I myself know nothing about these details, and I shall leave you gentlemen to settle these matters with Kinokunia, the contractor, so soon as he arrives. I have sent for him. In the meantime, consider yourselves welcome, and please accept of the meal I have arranged in the next room for you. Come along, and let us enjoy it. Fujieda led the four countrymen into the next room, and ate with him at the meal, during which time Kinokunia, the contractor, arrived, and was promptly ushered into their presence. The meal was nearly at an end. Fujieda introduced the contractor, who in his turn said, gentlemen, we cannot discuss these matters here in the house of Lord Fujieda, the Shogun's agent. Now that we know one another, let me invite you to supper. At that I can explain to you exactly what I want, in the way of trees out of your district. Of course, you know my family are subjects of your feudal lords, and that we are therefore all the same. The four countrymen were delighted at so much hospitality. Two meals in an evening was an extraordinary dissipation for them, and that in Yedo. My word, what would they not be able to tell their wives on their return to their villages? Kinokunia led the four countrymen off to a restaurant called Kampanaro in Ryogoku, where he treated them with the greatest hospitality. After the meal he said, gentlemen, I hope you will allow me to hew timber from the forest in your village, for it is impossible for me otherwise to attempt any further building on a large scale. Very well, you may hew, said Mosuke, who is the senior of the four, since the cutting of the trees in Nekomamiogen forest is, as it were, a necessity for our Lord, they must be cut. It is, in fact, I take it an order from our Lord that the trees shall be cut, but I must remind you that there is one tree in the grove which cannot be cut amid any circumstances, whatever, and that is an enormous and sacred camphor tree, which is very much revered in our district, and to which a shrine is erected. That tree we cannot consent to have cut. Very well, said the contractor, just write me a little permit, giving me permission to cut any trees except the big camphor, and our business will be finished. Kinokunia had, by this time in the evening, taken his measure of the countrymen so shrewdly as to know that they were probably unable to write. Certainly, said Mosuke, just you write out a little agreement, Jinyaman. No, I'd rather you wrote it, Mago, said Jinyaman, and I should like Yohei to write it, said Mago. But I can't write it all, said Yohei, turning to Jinyaman again. Well, never mind, never mind, said Kinokunia. Will you gentlemen sign the document, have I write it? Why, of course, they all assented. That was the best way of all. They would put their stamps to the document. This they did, and after a lively evening departed pleased with themselves generally. Kinokunia, on the other hand, went home fully contented with his evening's business. Had he not in his pocket the permit to cut the trees, and had he not written it himself so as to suit his own purpose, he chuckled at the thought of how neatly he had managed the business. Next morning, Kinokunia sent off his foreman, Chogoro, accompanied by ten or a dozen men. It took them three days to reach the village called Yabukimura, near the Nekomamiogen Grove. They arrived on the morning of the fourth day, and proceeded to erect a scaffold around the camphor tree, so that they might the better use their axes. As they began chopping off the lower branches, Hamaratsushima, the keeper of the shrine, came running to them. Here, here, what are you doing? Cutting down the sacred camphor.  Do you hear me? Stop at once! Chogoro answered, you need not stop my men in their work. They are doing what they've been ordered to do, and with a full right to do it. I am cutting down the tree at the order of my master, Kinokunia, the timber contractor, who has permission to cut the tree from the four headmen sent to Yedo from this district. I know all that, said the caretaker, but your permission is to cut down any tree except the sacred camphor. There you are wrong, as this letter will show you, said Chogoro. Read it yourself. And the caretaker, in great dismay, read as follows. To Kinokunia Bunzaemon, timber contractor Yedo, in hewing trees to build a new mansion for our Lord, all the camphor trees must be spared, except the large one, said to be sacred in the Nakomamiyo-jin Grove. In witnessware of, we set our names. Ginemon, Magozaemon, Mosuke, Yohai, representing the local county officials. The caretaker, beside himself with grief and astonishment, sent for the four men mentioned. On their arrival, each declared that he had given permission to cut anything except the big camphor. But Chogoro said that he could not believe them, and in any case he would go by the written document. Then he ordered his men to continue their work on the big camphor. Hamaratsushima, the caretaker, did harakiri, disemboweling himself there and then. But not before telling Chogoro that his spirit would go into the camphor tree, to take care of it, and to wreak vengeance on the wicked Kinokunia. At last the efforts of the men brought the stately tree down with a crash. But then they found themselves unable to move it. Pull as they might, it would not budge. Each time they tried the branches seemed to become alive. Faces and eyes became painful with the hits they got from them. Pluckily they continued their efforts, but it was no use. Things got worse. Several of the men were caught and nearly crushed to death between the branches. Four had broken limbs from blows given in the same way. At this moment a horseman rode up and shouted, My name is Matsumaya Tetsunosuke. I am one of the Lord of Sendai's retainers. The Board of Counselors in Sendai have refused to allow this camphor tree to be touched. You have cut it, unfortunately. It must now remain where it is. Our feudal Lord of Sendai, Lord Date Tsunamune, will be furious. Kinokunia, the contractor, planned an evil scheme and will be duly punished. While as for the Shogun's agent, Fujieda Geki, he also must be reported. You yourselves return to Yedo. We cannot blame you for obeying orders. But first give me that forged permit signed by the four local fools, who, it is trusted, will destroy themselves. Chogoro and his men returned to Yedo. A few days later the contractor was taken ill and a shampooer was sent to his room. A little later Kinokunia was found dead. The shampooer had disappeared, though it was impossible for him to have got away without being seen. It is said that the spirit of Hamaratsushima, the caretaker, had taken the form of the shampooer in order to kill the contractor. Chogoro became so uneasy in his mind that he returned to the camphor tree, where he spent all his savings in erecting a new shrine and putting in a caretaker. This is known as the Kusunoki-Zuka, the camphor tree tomb. The tree lies there, my storyteller tells me, at the present day. The end. End of chapter 57. Recording by David McKay. End of Ancient Tales and Folklore of Japan by Richard Gordon Smith.


Thank you very much. Thank you for the opportunity to present this this paper. This is a great audience to get to get comments and discussion. And I'm really excited about it. This is a joint project with Yanis Bakos also at NYU. And, you know, for a while now Yanis and I have been investigating blockchain and blockchain related technologies. One of those technologies is smart contracts. And like with any blockchain technologies, we have heard a lot about how smart contracts are going to make the business landscape more decentralized and democratic and it's going to free us from the nomination of a large, large players. The smart contracts are themselves. I'm not going for this audience here. I'm not going to go into a lot of explanation of smart contracts just just a little bit. But let me point out that smart contracts themselves go back to the 1996 paper by Nick Szabo, where he describes the now iconic example of Carly's. And in that example, if a payment on a car is missed, the smart contract will automatically lock the car and return the control rights to the to the bank. After 2014, Ethereum made smart contracts much more popular and smart contracts entered mainstream discourse. And since that, it has been said and expected that smart contracts will make contracting complete. They will allow us to get rid of courts they will allow us to get rid of escrow holders and other trusted enforcers. And with that they will enable for complete decentralization so there were a lot of those there are those those are enabled by smart contracts and I'm not talking about the failed. In our case, but there are many other dollars. And in the result, that should allow for democratization of of the business landscape of industries that should allow us to have small entrance coming and competing and on the level field with with large large players. So those are big promises. What we set out to do is to build a model to figure out whether smart contracts really can deliver on those promises. And if so, what are the economic forces that are allow us that would allow them to do that. So to start with just to to ground them the terms smart contract is basically a computer program. And as a specific computer program that automatically executes an agreement between the parties upon a certain trigger. So, to be fully clear, smart contracts does not need multiple parties you can have a smart contract with yourself on a terium, but the ones that we think are going to be interesting are the ones that involve multiple parties. So, the key characteristic of a smart contract, the one that is going to bring the most benefit is that because of the automated execution does not allow on does not allow reneging on the on the terms of of the agreement. The key limitation is that the trigger and the agreement mass allow for allow for digital input and digital execution. And this is a limitation because not every agreement allows allows for such level of digital codifiability. And that means that such agreement is does not lent itself to smart contracting so not everything can be smart contracted out. The digital inputs that are necessary for smart contracts very often come from new connected sensors. So sometimes we already have the digital input that we need, but very often we were talking about smart contracts. We mean that we are going to also set out new sensors the sensors are connected in order to directly provide input to that to the smart contract. And this such connected sensors are now also known as Internet of Things. And because of that, because of this connection between the dependency between the smart contracts and and the sensors, the benefits of smart contracts are often confused with those of digital sensors. And this in fact goes back even to the new examples are Carly's example, because in that example the main benefit comes from the mechanism that allows the car to be locked remotely. And this benefit is ascribed to the smart contract. But the two technologies can be implemented separately can have sensors without smart contracts and we have, we have, we can have smart contracts with the existing digital inputs without without adding new technology. So we built a simple model in order to carefully separate the effect of the smart contract and sensors on the contracting situation. And what we find is that sensors expand the state space over which the parties can contract the smart contracts restrict the strategy space, and because of that they're going to have a different effect on the efficiency of the contract. So let me describe the very simple model example that we are we are working with, and it is motivated by the fact that a lot of smart contracts nowadays are actually implemented in shipping industries. So we have a fruit company and a transportation company FNT and fruit company contracts with the transportation company for shipping off perishable good fruit at the price of P. The shipment may be of high quality or low quality. If the shipping is of high quality which means that fruit is properly refrigerated. F obtains high value is the fruit is tasty and last longer and tea in course higher cost because refrigeration is costly. If the shipment is low quality fruit was not refrigerated the fruit company obtains low quality because the fruit is going to rot in quickly on the shelf and transportation company bears only lower cost. We are going to assume that shipment even of low quality is more of socially beneficial. And it would be even better to have high quality shipment even though it is of high cost. And if the fruit is not shipped at all both parties obtain zero. After the delivery the fruit company should pay to the transportation company. But if it doesn't transportation company can take a fruit company to court to expand the payment. If the dispute is brought to court, then both parties are going to bear some non reimbursable cost of legal action that could be effort and stress and and some other some other aspect that cannot be reimbursed in a way. And in the simple model we are assuming that the courts always fair and they are able to enforce the performance of the contracts in full that the model lends itself easily to relaxing this assumption to some extent and even actually do comparative statics on the furnace of course. So, in in this setup, we, what is crucial is on the upon delivery, when the fruit is delivered, the refrigeration is not observable. So, we cannot see at the moment or verifiable in court so the fruit can fruit company cannot see whether the fruit was refrigerated. Yes, they are going to get higher or lower value out of it later down the road but not at the moment of the delivery and payment. The fact of delivery and the payment itself is both observable and verifiable. So, so that that that can be easily contracted up. So that is the extended former presentation of this game where the transportation company can provide local to delivery high quality deliver no delivery at all. The fruit company pays or does not pay and then it doesn't pay the transportation company takes legal action or not. So, as very easily seen it in such a case in this environment that the trading is never efficient in equilibrium. First of all, if the cost of legal action is too high is high. Then the transportation company will not find it worthwhile to take the fruit company to court if the payment is not made knowing that the fruit company is not going to pay knowing that the transportation company is not going to deliver at all. There is no trading and zero social welfare, but even for low value of legal action, even if the threat of going to court is a credible threat. Then we are only going to get low quality delivery in this equilibrium because the contract cannot be specified for the for different quality of delivery. Okay, so markets current situation have a way to deal with that we are we have we can have relational contracts we can have reputation we can have our long term relationships. But in all those all those cases, the, the mechanism that are defending us against this, this failure are our favoring large companies, and they require trust. So the premise of smart contracts is that maybe with smart contracts we can have a relationship that that's not required trust, and will allow small companies to come enter the market and and play the level playing field with the large incumbents. So that should work out even in the one period game. So, we see that smart contracts can help a little bit, but we're going to qualify that. So, because the fruit delivery and the payment are verifiable we can assume that they're digitally, they're digitally codifiable we can have a smart contract that is going to make an automatic payment upon the delivery. Instead, it restricts the strategy space off of F because now F no longer has a choice between pay and not pay. That is going to improve the contracting situation because now even for high cost of legal action, the transportation company will deliver the food because we'll know that it will get paid. The smart contract is going to make contracting possible where it was not possible before, but it does not increase the efficiency of the trade because the only quality of the delivery that is going to happen is low quality. So, we can think and look into the effect of sensors. So, if the sensors are put into place and just sensors without smart contract, the sensors that would, for example, in the container of the of the shipment that would allow to distinguish between the non refrigerated shipment upon delivery sensors are provide the provide the variable on which the contract can be can be specified and also it would be an evidence verifiable in court. That, by naturally is going to allow us to to to distinguish between states and is going to allow for efficient high quality delivery when delivery happens. At the same time, however, if the cost of going to court is high. The same dynamics applies transportation company is not going to find it worthwhile to go to to to go to court and take legal action that knowing that after the company is not going to pay knowing that transportation company is not going to deliver. So, smart contracts are going to help in some situations and sensors are going to help distinguish between the states, but for those high high cost of transaction, the, the only way to get the efficient trade is to have both smart contracts and and sensors. So, so when we have both technologies together contracting in equilibrium is fully efficient. So, as our clear synergies but as we can see also the synergies may depend on the parameters. Now smart contracts and sensors have different effects differently the interactions sensors increase the state space over which the parties can contract and smart contracts reduce the strategy space. So, in effect, smart contracts can make contracting possible when it was not, but in themselves they are not improving efficiency, whereas sensors can increase efficiency when contracting already occurs. And those benefits will have different value depending on the parameters. If we also take into account that both of those technologies can be implemented together and they will have different costs of being implemented. We can ask, when is it optimal to implement one technology or the other technology or when do we need to implement both of them together. What we find is that sometimes when we implement one of the technology adding the other technology brings no benefit. And if we and in other times for the parameters, implementing only one technology brings absolutely no benefit it only makes it worthwhile if we can efficiently if we can, if we can afford to to implement both technologies together. So, if the cost of legal action is really low, then there is no argument and no, no benefit from, from implementing smart contracts, even when smart contracts are really cheap to implement. And there may be some regions where it is optimal to implement sensors. When we have inter, when we have intermediate value of legal action, we can see that the smart contracts may be worthwhile to implement. The area where it's worthwhile to implement smart contracts is increasing, but it is never good to implement never beneficial to implement both of them together. So in some regions when one of them can do the job, I think the other one is not going to improve. Whereas if this cost of legal action is really high, then it may be worthwhile to implement smart smart contracts. It may be worthwhile to implement sensors only when it is also worthwhile to implement smart contracts, sensors by themselves are not going to help help at all. And in fact, in some in this region implementing smart contracts at all alone is also not not good. So this, depending on the parameters, it tells us for which industries, which technologies may be optimal to be, to be implemented and in which industries they, each of the technologies or both of them together can, can effectively change the relationships between the, in the market. Now, another thing is that even though implementing a technology may be socially optimal, the individual incentives to adoption may differ. So what we find we find that if we look at the individual incentives under some parameters we get over provision of technology, and sometimes we get under provision of technology. So, for example, as we said earlier for really low costs of legal action, it is not socially optimal to implement smart contracts because they provide no benefit and they are costly to implement. And yet if the transportation company has lower gaining power, then the fruit company has incentive to impose this technology, even though it lowers social welfare because it allows a fruit company to capture more surplus from T. And the transportation company if it has lower gaining power it may also be worse off with sensors, because of with or without smart contracts, even though social surplus increases and this is also because a fruit company can extract more surplus with sensors. And this may give incentives to sabotage sensors if they are imposed. So let me finish here and rub it up. What we show is that carefully separating the effects of smart contracts and sensors on contracting situation. It shows that sensors increase the strategy space over which we can contract smart contracts reduce reduce the strategy space. And it has different effects on the different effects on the efficiency of contracting. We find conditions under which it is optimal to implement one of the technologies on where there are synergies to implement both or it doesn't make sense to implement only one. And we also look at the incentives to adopt that may be conflicting with the social optimal. And thank you very much and I'm looking for the Q&A.


Okay, so let's start with the session about the creation of tracker data. Okay, yesterday we saw in aggregated data, we saw how to create new data, how to handle data values, and that is a complete registration record. Today we are going to talk about the tracker data. The main thing that is important to notice is in the tracker data, we have two kinds of data. We have the data that is called identifiable. It means those elements that can be identified by a UID and the non not identifiable object, that is, those objects that cannot be identified by a UID. So this is very similar to what we saw yesterday with data values. Now instead of data values, data value model, we will have the event model, tracker entity model, enrollment model, all that. And within each model, we will have a repository to access the event or the tracker entity instances or the enrollment. So, when we are, I said, I said that we have two main kinds of elements, the identifiable objects are the not identifiable objects. The identifiable objects are the tracker entity instances, the enrollment, the event, the nodes, and the file resources. I mean, these elements can be identified by the 11 charter UID that you, I think you are familiar with. And you can use that UID to do an investigation also on those elements. And in the not identifiable objects, we have the tracker entity instance, tracker entity attribute values, and the tracker entity data values. It means that these objects are not identified by a UID, but by a combination of fields. For example, the tracker entity attribute values are identified by the combination of a tracker entity instance and an attribute. And the data values are identified by the combination of an event, another element. So how to deal with the identifiable objects. As I said, the identifiable objects are identified by a UID. This UID is unique. And this UID is generated by the SDK. So how is the flow here? The flow is, in first place, you have to create like the base object, a base object with a minimum information required to create an object. And this is what is called a projection in the SDK. So for example, here in this code snippet, we have the tracker entity instance projection that only needs to fill the organization unit and the tracker entity type. So this is the minimum information required to create a tracker entity instance in the system. So in the repository, we have an add method that accepts this projection and returns a UID. So once you create the object using this projection and you get the UID, now you can use that UID to access the tracker entity instance or enrollment or event or whatever. And modify and change a field or deleted or update anything like here, for example, the object repository. In this object repository, you will find method with the name set. For example, in the case of tracker entity instances, you will have set, I don't know, geometry, set, follow up, set, whatever, and a value. Okay. Also the delete, delete if exist, and then we have the create method to get the object, get the element, or check if the object exists or not. Okay, and this was for identifiable object. Okay, now for not identifiable object. If you remember from yesterday, for the aggregated data values, we have to specify the data element, the organization unit, the period, the attribute of the combo thing. So you need to specify all that information to identify the data value. In the case of a tracker data, we have track entity attribute values and track entity data values. Those values are can be uniquely identified by in the case of attribute values by the track entity attribute on the track entity instance. Because this combination of track entity instance and track entity attribute is unique. And in the case of track entity data values. And you can identify a data value by the event and the data element. In the same way that it's for. We have some right method methods methods to upload. And to update the data. The set to modify any value in the database delete on delete if exist. And also the, the same read method and before. Yeah. In the same way that with all the repositories and models in the decay. We always have two ways to access the repository, the reactive method and the blocking method. This is the same thing. Okay, any questions so far. This is about the issue of tracking data. Because now I'm going to change the subject a little, a little, we are still in creation of data. But more focus on the data entry form. And this is about the, the research values. Okay, and you know that. So the target entity attribute target entity attributes can have some properties like the value type for example if it's numeric or or a text or text or a date or whatever. And also there's a property called unique and automatically generated that it means that it is not the user who enters the that the value for that attribute. It's the system that generate the value for this. And this value is unique, usually. And also you can specify a pattern to generate the value to this value has to be unique in the whole system. But we know that in the device in the mobile device, you can be working offline. So the SDK and the web API, they have a mechanism to reserve some values. So the back end generate regenerate some values for the device. So, in this way we want to that those values are going to be unique. And this is required to operate offline and to be sure that they are going to be. Yeah, the. Okay, we have to download before we go offline. We have to download these values. And this is automatically done in the skeleton app and they're calling this method. The important thing is that we can get a new value using the reserve it value manager. It value and we have to specify the attribute you ID and the organization unit.  And it's important to do that to regenerate the attribute value. And it's important to know that the SDK regenerate download a certain number of activities values, usually 100, but this is, this can be parametric side. And once the SDK has run out of values, it automatically query request for more values to the server. This is automatic. And also the SDK handles all the logic about the expiration of research with values because they have an S pretty date. And also to, to be sure that we always have values in the device to use. Okay, any questions so far about the traditional tracker data or the reserve values. There are no questions. Okay, so let's start with the exercise. Yeah. So this is quite a long exercise. Yeah, we will have more than half an hour for this. This exercise. Okay, I'm going to the code. So in this exercise, I'm going to run the application. This exercise has three parts. It has three parts, the creation of the second entity in turn, the creation of the enrollment and the creation of the attribute value. It means all the steps involved in the creation of a new rocket entity in terms with enrollment in a, in a program. Okay, if you go to this, to this brand to the initial brand, the exercise eight, then you go to programs, programs. You can see a plus bottom that in the, yeah, in the use cases branch. And this button gives you access to the, to the flow to enroll a second entity in a program. So, here, I click the bottom, but it does nothing because it's not implemented. So what will you, what you will have to do is to implement the missing method in this flow. So in first place, you have to create a new TI, and you have to go to this class, the target entity instance, target entity instance activity class. And let's go here. Yeah, is this one, target entity instance activity class. And the first part of the exercise is that here you have to create the target entity instance. And in the description, the tips. And you can see that you have to set any organization unit in the capture scope so probably the first step here is to get an organization unit using the transition to new depository filtering back up to the scope and get the first one. And also we saw here that the target entity instance and projection. And it requires two fields, the organization unit and the target entity type here we have the program. So, and the program has a target entity type link. So this is the targeted type we have to. And this method returns. A string, a single of a string. This string is a UID of the object created. That has we, we know this method returns that string. And this is the first part of the exercise. And so I'm going to explain the three parts. And each part in will give you access to a next step in the flow. I mean, if you want to have the targeted instance, you can click the plus button. And it will do something. But it will not enroll the target entity yet. And now it's enrollment. In the enrollment form service. Let's go here. You can check the produce here and look for the enrollment form service. Okay, so here we have the exercise eight B. And it says, create a new enrollment and save the enrollment you ID in the variable room and you ID of the here. In this class we have this variable, and I mean you ID that is used by other methods within the service. It's important to save the field. This variable with the enrollment you ID.  And then the enrollment date and incident date to today. And we have a helper class hyper method for that. Okay, this is the second part. Once you are here, you can click this button. And probably that the eyes want to be enrolled. And the last part, the attribute values, probably that the eyes want to be enrolled, but with, without the values. So we have to go to the enrollment form activity class. We have enrollment form for activity class. Yeah, and we have this other method. Okay, this method is a listener of the former of the data entry for the enrollment form. This is the listener that is triggered every time that a value is modified. So here you have the parameters that attribute you ID and the value. And what you have to do is to save the value. Otherwise, delete it, because if you delete, you remove a value in the identity form, what you are going to have here probably is an empty thing. So you have to check if the value is empty or not. If it's empty, delete it. Otherwise, save it. Okay. And yes, and I think that's all so far. Then we have an optional exercise about precepted values, because in this way, I will recommend you to use the child program. Use please a child program. And in this enrollment in this program, we have an attribute that is unique and auto generated. So if you, if you do until the exercise. And you will be able to fill the form, the form and the track and the distance will be a role in the program. But the attribute that is generated will not be at the negative because it's not implemented. The exercise is the one that implement this behavior. So this is optional. Okay. Any question about the exercise.