Hey everyone. Good afternoon. Welcome to join our session today. So we are going to share about the self-service stream processing platform on Kubernetes. I'm Chen Ya from Apple's AI ML data platform. This is our agenda today. So we'll talk about our journey moving to the cloud and Kubernetes and why we adopt Apache Flink for real-time data processing. Then our challenges while moving to production at a large scale and the solutions that we have figured out so far. So first about our journey moving to the cloud and Kubernetes. So our users expect very quickly scale up and down of the cluster resource to match their real-time traffic pattern and we cannot wait for long, right? And we also don't want to preempt user applications to honor some of them. So we can see this is like for the deployment itself. We have the auto scaling and how about the cluster. And from a platform's perspective sometimes it can be ideal that we decouple ourselves a little bit away from the infrastructure maintenance overhead. And when we move from virtualized deployment to containers, it actually help us abstract away the physical hardware complexities. So here we can see the containers can move freely around clouds and also the OS distributions. And in a multi-cloud environment, there are a lot of benefits for us to leverage the available support from different cloud providers, the hardware resource, and the cost efficiency. And Kubernetes can help us to organize these containers to workloads in a consistent approach to provide the compatibility. So there can always be limited admins who can help us address cluster issues at a very large scale. Luckily, we can leverage Kubernetes automatic recovery capability to solve some issues and to keep the cluster resilient and self-healing in case of failures. And we know many platforms have this need to add additional components on top of an orchestration layer. And here we can see Kubernetes has this modularized architecture that can allow us to integrate with multiple components and extensions. So that's about our journey moving to the cloud and Kubernetes and why we adopt Apache Flink for real-time data processing. So we know users have a very high expectation in terms of latency when they try to process data in real-time, right? They expect the data can be immediately processed upon arriving the system. And we can see Flink supports a pipeline in-memory execution model. So data can be accessed from local and one there is a slow operation. Flink is able to adjust its data processing speed. So we can see the busy operator can propagate the back pressure to upstream task and here it can avoid system crash overall, right? To slow down the throughput a little bit, but to avoid the system crash. And when there is a very large state, Flink is able to take checkpoints incrementally to capture the data and asynchronously in the background and to restore from the state, Flink can support this exactly once guarantee with replayable source like Kafka and the atomic state commit. So we know many users have this need to connect their streaming pipeline with upstream or downstream data source and things, right? And Flink has this very rich connector ecosystem, not the limited to Kafka, Iceberg, but also Cassandra, Elasticsearch, Pausa, right? And users don't need to write extra jobs to complete their entire workflow. We also know users have diverse background and needs when they're working with Flink, right? And luckily we have this multi-layered API on the very top. There is SQL table API that comes with optimization and built-in border plate codes, right? And in the middle we have this data stream API to unify stream and batch processing with some advanced windowing functions and at the very low level there is this process function that can provide fine granularity for users to manage their state and time in a very granular way. Okay, but still with Flink and Kubernetes, we have challenges when moving to production at a large scale. What can be some of them? The first is that we need an automated approach to deploy Flink on Kubernetes. And we also want a control plane that can scale beyond a single Kubernetes cluster. We would like to help our users self-onboard, observe and troubleshoot their applications without admins in the loop because there can be so many of them, right? Also, one support users and admins, they have this need to bulk operate a large number of deployments. How can we help them? And also to automatically scale not only stateless streaming applications, but also stateful applications. And how about managed resource availability? This can also be challenges, right? And also for streaming applications to have cluster upgrade in the cloud environment. So first, let's take a look at deploying Flink in Kubernetes, right? There are multiple options and the first option coming to our side is the Flink-Kubernetes native integration. It's first introduced in Flink 1.10 years ago, right? So how does it work? Let's take a look at this diagram. So we can see the Kubernetes client is actually embedded inside the Flink client to talk to the Kubernetes API server directly. And the Flink client can then create a job master deployment, including the job manager as well as the Kubernetes resource manager. And then we see the Kubernetes resource manager is actually responsible to dynamically allocate task manager parts through the Kubernetes API server. So for this Flink-Kubernetes native integration, we can understand in a way that Flink itself contained, right? It doesn't need to rely on any external tools from Kubernetes like the Kube CDL command. But it then also creates the challenge to automate the application upgrade in Kubernetes environment. So we must have already been familiar with these two concepts from Kubernetes, right? The custom resource and also the operator. Can we combine the custom resource and operator to capture the core responsibilities of a human operator to manage Flink deployments? So we know human operators, they have deep knowledge of how a Flink application ought to behave and what to do when there are problems. With a Flink Kubernetes operator, then it can help us to monitor, to upgrade, and to deploy the applications in an automatic way. And yes, we have this Flink Kubernetes operator introduced in Flip 212, with Apple being a major contribution to this as well. So the Flink Kubernetes operator, it actually leverages the Java operator SDK because it wants to directly talk to the Flink Java client library. And under the hood, it still uses the Flink Kubernetes native integration to launch the Flink deployment in a cluster. Both the native integration and the operator will use the Fabric8 Kubernetes client to talk to the Kubernetes API server. So here from this chart, we can see all possible current state and transitions of a Flink resource lifecycle. And let's take a deeper look on how the Flink Kubernetes operator works. From a high level, it follows this control loop principle from Kubernetes. So we can see the user creates a custom resource, and then the operator will try to check the status of this resource from the cluster. The observer will record a point in time status, but we need to be careful here. Before the control loop finish, anything can change, so the status recorded can also change. After the observation phase, the operator will have a validator to check the application resource back, if it is in good terms. And then are we ready to do the reconciliation and execute the upgrade? The answer is actually no. There are multiple things that we need to check. For example, we want to make sure there is no pending operation for this custom resource. It's very common that we trigger menu save points and it will take some time. So we want to wait any pending operation to finish. Another thing is that the status can change. What if in the middle something is wrong and the application is not stable anymore? Then the operator is responsible to bring this custom resource back to its last successful state. So something about the operator, and let's assume we now have the Flint Kubernetes operator in the production, right? There can still be challenges to run PAP-L enlarged. So the first one, what if the Kubernetes cluster where Flint Kubernetes operator fails and goes down? Can user group map beyond one Kubernetes namespace for modded tenancy, et cetera? Authentication and authorization might need to meet extra requirements and how can we support that and where should we support it? The deployment information need to be persisted for audit or recovery. What if the cluster is done and the operator is gone as well? And admins need to operate across multiple clouds, multiple accounts, and clusters. There can also be other service or platforms that want to integrate for real-time data processing. Lessons from BPG, right? What is BPG? This is the batch processing gateway service that Apple open sourced earlier last year. So essentially, it helps Spark users to launch Spark applications in a Kubernetes environment and manage there.  So how does it work? Let's take a look here. The batch processing gateway acts as an intermediary layer between the user request and the Kubernetes customer resource. And we can deploy Spark Kubernetes operator in each cluster. And it defines a Spark application customer resource. And now it's the Spark batch processing gateway's responsibility to transform the user request. Into a CRD format that can be recognized by the operator. Then these CRDs can be sent to the Spark Kubernetes cluster, have the operator to take over there. So essentially, the idea here is that the gateway service is trying to take over all the heavy lifting on behalf of the users. For users, they only need to worry about specifying a few configurations, maybe from a UI hitting several buttons, and that's it. They don't need to worry about the underlying infrastructure details, or even be familiar with Kubernetes. It also provides these flexibilities to support more frameworks in the future. It doesn't need to be Spark, it can be anything behind. And more lessons from this batch processing gateway that we can learn from. So we talk about this multi-tenancy challenge. Let's say users from different teams, right, they want to submit their Spark applications into a single cluster, or maybe multiple ones. How can we help them there? From this graph, we can see in the middle, the batch processing gateway tries to define a list of Spark logical clusters. And each logical cluster can support multiple queues. Very interestingly, right, this queue one can map to both the Kubernetes namespace one and two in the backend on the Spark physical cluster. Let's say one of the users submit a request asking for queue one. Then both C01 and C02 have queue one included in their mapping. And how can we decide? So we can have this routing algorithm to consider the weight of each cluster and our current status, right? Plus some randomness, anything if we want to increase the load of certain cluster or namespace, we can have all the flexibility there. And then we will help the users to launch their applications in the corresponding backend namespace or cluster. And they don't need to worry about it, right? They only need to know, okay, I want to submit this application to a queue one. Besides the multi-tenancy, we also know users deeply care about the observability of their application, right? They want to troubleshoot, they want to debug. So the batch processing gateway service can have this capability to support a log mover to move the log of a Kubernetes pod to persistent storage. Why do we want to move it? It's possible the pod can be gone, right? After the application is finished or completed. And sometimes we really want to recycle these pods, right? Because it will create a lot of pressure if there are so many terminated pods and the Kubernetes API server have to monitor it for the health check, right? So coming back here, when the user is hitting the log rest endpoint, then it can go to two routes. First, it will directly check from the executor pod if it's still available. If their log is still there, then it's great, right? We'll stream from there. If not, then we'll use a large log indexer to search for this executor pod or driver pod log and load from a remote storage. So there are a lot of functionalities that can be supported from this kind of gateway service. Okay, so with all these lessons learned, let's take a look at our Flink control plane. We want to support real-time data processing here, right? It's a busy diagram, but let's decipher it, right? In the middle, we have these control plane instances that can be deployed in multiple accounts or even cloud providers with its own persistent storage. And on the right-hand side, we have these Flink physical clusters running the queue, right? Similar to the batch processing gateway. And if a user issued a request to our control plane, it will first hit a proxy sidecar to get its identity authenticated, right? After that, if they have the identity, it will go to the gateway service to get further authorized. For example, whether this request indeed has the permission to use a queue to submit an application. So there can be a lot of distinctive features while managing a real-time application platform. For example, we need to consider how to help the applications to upgrade suspended triggering safe points, right? These are different from the batch processing gateway. But still from a high level, we share this similar architecture and it has this great benefit to reduce our maintenance overhead of multiple platforms and also unify the real-time and batch data processing experience in the long-term. Let's picture several scenarios on how we can leverage the Flink control plane to help our users. The first one is self-service user onboarding. So imagine that we have so many users and everyone wants to have a queue and increase their restores. We don't have that many admins to help them, right? Then what we can do. From the client side, they can issue a request, maybe just from a UI, letting us know if they need a queue where they want to increase the resource. The request will go to the Flink control plane. The control plane can automatically approve it or in some maybe rare cases, we'll ask the admin to do some manual approval. Maybe the resource is too much. And then the control plane can automatically update cluster resource back. For the provision, it will go to the Kubernetes cluster, update the clusters back. It's also possible that we need to create a new cluster and we can also do it automatically. And it's important that after all this provision, the control plane will trigger the smoke test to validate that this queue is successfully created and the smoke test could be running there. And then just let the users know, either your queue is provisioned successfully or not. Similarly for admins, right, if we want to help them to automatically migrate clusters, what we can do here. Admins can submit requests to the control plane. I want to migrate all the workloads from cluster A to B, maybe due to some maintenance or cluster upgrade. It's also possible that the cluster is failing for some reason and we want to notify the admin to keep them in the loop. Then the Flink control plane is able to trigger save points for all Flink applications on this cluster A. Suspend them before moving them, right? And then on the other cluster that we want to migrate to, the control plane can help to automatically redeploy all these applications. Using the previously triggered save points and our persisted spec, maybe in a remote storage or RDBMS. And then the control plane, again, is responsible to verify the Flink application health. Before letting the admins know, okay, the migration is successful or not. So there can be so many features and functionalities are able to support from this Flink control plane. Now let's move one step further into our story of automation and cost efficiency. Flink application auto scaling is introduced in this Flip 271, also with major contribution from our group at Apple. The main problem we want to solve is actually one and how much to scale up or down. So we know when there's too much resource, right, it can be costly for users over time and too few can cost the job to be unstable. But it's hard to scale a Flink application in place because the application needs to take a save point, right? And then to stop and resume from the previously taken state with a new configuration. Then there will be this associated cost, especially when there's data backlog, the data is waiting, queued there to be processed. So in this case, it requires us when making every scaling decision to consider if the backlog can be fully absorbed per user's configuration or before the data retention time comes. And how does Flink application auto scaling work? Can we simply change, let's say, the job parallelism of the entire application? The answer is no. Why? Because there can be workload distribution very differently across all the Flink job operators. And our proposed solution is to change the parallelism of a job vertex. What is a job vertex? It's a group of chained operators that can be executed together without data shuffling. Then our goal becomes to find the minimum parallelism of each job vertex that can still ensure there is no back pressure of the Flink pipeline. So here in this diagram, we can see, previously, everything is running normally. So the data processing rate matches the input record rate. And then suddenly, our log ingestion rate increases. We can see in the middle, the map filter operators, they cannot catch up. They are almost 100% busy. And then we mentioned about the back pressure propagating. So they're propagating the back pressure to their upstream sources. And these sources tries to slow down, reduce their throughput to make sure the application can still run. And then auto scaling can come into the rescue to calculate the scaling factors. And the key here is that we want to make sure we predict the effect of the changing parallelism on the downstream job vertices. And then we get these scaling factors, 5x, 10x, or 4x. As we mentioned before, our goal is to achieve back pressure free. It's okay if the operators are still busy, but there's going to be no back pressure because the incoming record rates can now match the true data processing rate. Okay, so where do we implement this Flink autoscaler? The Kubernetes operator can be a natural place. Why? Because it has access to all the deployment metrics. The way we make the predictions heavily relies on the metrics. We cannot use magic to predict. Also, the Flink Kubernetes operator is highly available and able to reconfigure the deployment for its rescaling. And the autoscaler itself also needs to emit some metrics to review, to generate insights on why some scaling decisions are made. Besides autoscaling a Flink application, we also need to be resource aware of the cluster in general. So both cluster autoscaler and carpenter can automatically scale Kubernetes cluster resource. And for us, we choose carpenter and we move from cluster autoscaler to carpenter because it can provide us the flexibility to use a wide range of instance types available. So we are no longer bounded to just one instance type for a queue. We can specify five or six of them. It also has less limitations of the orchestration node group. Now it can directly communicate to a Kubernetes node so that interval to retry can be greatly reduced to milliseconds instead of minutes now. This is extremely handy for our users to have the resource they need in the cloud environment. In order to help carpenter to get our cost bringing down, right, then it need to recycle the nodes. And to recycle the node, there's a prerequisite. There's no running pod on that node that we don't want to get rid of. Especially challenging for streaming application because if we move those running pods around, it can cause potential disruptions to a streaming pipeline. Then what can we do here? We want to solve the problem from the source. So when we first allocate those pods, those containers, we want to put them into those nodes that are already pretty busy. Instead of just finding a random node, maybe there are two pods running there. We want to find a node that maybe there are hundreds or thousands of pods already running there. So this is the bin packing. We try to add to a customized scheduler alongside the Kubernetes scheduler. And to move the pods on the same node and have more empty nodes for the carpenter to recycle and reduce our cost. So we are almost running out of time and we want to do a quick wrap up. So for our self-service platform, right, we put everything into this big diagram that we mentioned so far. So we have this user interface for the experience and also the admin experience. And they will interact with the flint control plane, maybe through multiple client toolings. And on this right-hand side, we have all these giant boxes with the goodies like the customer scheduler, the Kubernetes operator, with all the scaling implemented on it and the flint applications, et cetera. And we are happy to open for questions. Do you mean cluster upgrade? Yeah. So that's a great question. So we mentioned before, for example, we have this automatic cluster migration. So we don't want to interrupt the flint applications. Basically, we want to still keeping them healthy and redeploy them into another cluster. And after that, we'll do the upgrade on the original cluster. So basically, they still need to stop with the save point. But then with minimal time, we'll have the control plane to automatically do the redeployment. If you are worried about a massive, for example, disruption to a lot of applications, you can do it batch in batch. Or even one application at the beginning and then increase it by some index numbers. Yeah. That's a good question. So we don't use service mesh. So for that one, it's only a simple authentication. So we use like a gateway service embedded there and to cause some identity checker. Yeah. That's definitely a great question. So at this moment, we are running GPU machines as well for both our streaming applications and also the offline applications. And they also fit into this multi-tenancy story that we just shared. So ideally, you can have a different mix of resources. It can be a dedicated GPU queue, if you want. It can also mix with CPU resource. And it's actually more ideal because sometimes certain data workloads, they are more suitable for CPU processing. And for some, maybe for ML workloads, you can leverage the GPU queue. Yeah. Great question. So as mentioned, so Coventry and Cluster Autoscaler, they, well, first both have open source versions. So we are just free to use them. And especially asking, since we're already leveraging the hardware resource from the cloud providers, why don't we just use maybe the AWS Kinesis? The managed service. For in our case, because we're moving to a very large scale. And a lot of users have these customized needs. It can be hard to handle by like the managed service. So we want to have the kind of the control to help our users to build some customized solutions. And for some of them, they want the service, for example, the entire service to deploy to their own AWS account. And for some, they want it to be shared. And also the cost can be a concern as well. If you have so many workloads, then the way that we calculate the cost, et cetera, for managed service, it can be very expensive. Okay. So for a flint cluster, it doesn't span to multiple Kubernetes cluster. It will just sit into one cluster. And with one cluster goes down, right? So we mentioned there can be a persistent layer for our control plan to manage. So basically we want to save all the back of the flint deployments. And also their save point information it can be saved into, for example, S3, et cetera. So it's okay if the cluster goes down. We have a way to bring up all the flint deployments back as soon as possible or migrate them to another cluster. Okay. So we are running out of time. Yeah. Thank you.


Hello, everybody. Welcome back to Esoteric Atlanta. This is part two of our look at the Octurian anthology, which I'm so, so, so super, super excited about. I'm trying to light my stage right now. You're going to hear some banging and some yelling possibly in the background. That is the construction workers. And if you've been here for a while, you know that for a while now, I have had literally 10 feet outside of my window. They are building a high-rise. There used to be a restaurant there and now they've torn down the restaurant and they're building a high-rise.  I've lived in London, England. I've lived in Los Angeles, California. And of course, I'm from Atlanta. I've never in my life. I've dealt with construction in cities before, but I've never in my life dealt with a construction company quite like this before. And before we get into it, just going to call on Magdalen, Yeshua, Michael, Gabriel, Raphael, Hathor, who I now know I have a sole imprint from Hathor calling her in. All of my beings that are around me of the highest good, the highest light that are here to protect and guide. I ask that you come into this recording now. Help me say the words that I need to say. Please keep the equipment protected. Please keep the internet stable. I ask that if there are any nefarious beings that are not here for my highest good or wish to interfere with the knowledge being spread on this channel, that you will escort them out. I do not consent and I revoke any permission that the darkness thinks it has to use my wounds as an entry point into this. You've got to go. You can't be here. So thank you so much.   That's against the law. Twice now I've had to threaten to call the cops because they wouldn't let me into my house and I have a dog here. What if I had a kid here? And so twice I've had to tell them that I will call the Atlanta police department if they do not allow me into my house that they are breaking the law. One of my neighbors had to do the same thing because they tried to block her from coming in and she actually did call the cops. Two of my neighbors have gone to the city commission, two file complaints because on Saturdays they're not supposed to start working until like nine o'clock in the morning and they've been starting at seven. During the weekdays they're supposed to be finished up by like eight, I believe, but they've been going till 10. Multiple times now people have had their paintings, their computers, their TVs fall off the wall because of the aggressiveness of what's happening. And we know they're doing it intentionally and this is why we know they're doing it intentionally. The property that I'm on, I live in a very expensive, very nice part of Atlanta. Like I am right in the city center, I'm in the heart of Atlanta. But this building that I live in, this property is very, very old, like my apartment is very old. And because of that it's affordable, right? And a lot of people that live here are the same way, like we like being in this area, but this is a very affordable property. And the guy who owns the property has never, he's been, you know, construction companies have tried to buy the property he won't sell. He just likes having us here. But the people who bought the restaurant, the construction company are trying to get us the tenants to leave this property so that our landlord has no choice but to sell.    And I know that a lot of my neighbors are filing complaints left, right and center because that's not fair to us.  And you're getting your employees to intentionally bully us. God, I would hate to be in your shoes when the reckoning is upon us.  I know some of my neighbors are contemplating filing lawsuits against this company because of jobs lost. And I'm telling you guys, I've lived in Los Angeles, I've lived in London, I've lived in Atlanta, I'm used to construction workers being next door. And yes, it's annoying. But usually when they're doing construction next door, it's livable. They don't do things intentionally to bother you. They don't try to stop you from coming into your house.  They don't do those types of things. And if they do do something, where a TV falls off the wall or something breaks, they usually will reimburse the person. I'm telling you, I'm really considering outing this company's name because you don't want to go into business with these people. And that's one thing I think the owners of this company forget. They don't know who we are. They don't know who the tenants are that live here. They don't know that I'm a public figure that has a big platform. It just, it goes without saying, just always do the right thing. Just always be kind and do the right thing.  To the employees, it doesn't matter to you whether this property is bought or not. You just get paid by the hour. Why are you going along with this? Anyway, so to make a long story short, if you hear banging and shouting, it's the construction workers. So this is part two of our Arcturian anthology. And I am so, so, so, so excited to go deeper into this. We're starting with the section in the beginning. And if you missed part one, I will put that in the description box below. Ektara says, when you move with power, you affect reality in the beginning in the beginning by Judy Sion who is Tom Kenyon's girlfriend. My own mind is my own church. All national institutions of churches, whether Jewish, Christian or Turkish, appear to be no other than human inventions set up to terrify and enslave mankind and monopolize power and profits. Touche, I agree, Thomas Paine the age of reason. I grew up questioning religion. It seemed patently absurd to me, even as a very young child. The whole notion actually wasn't just absurd. It wasn't salty to intelligence, logic, reason and freedom of thought. I grew up reading and rereading Thomas Paine's an age of reason. As due to some odd blessing of fate, it was one of only two books left in the bathroom by some great guiding hand, certainly not my mother's. His logic seemed irrefutable to me, though I have come to differ with him on one key point, upon which I will not elaborate here, because each of us must make that final determination in the quiet of our own mind and heart. By the time I was old enough to comprehend Thomas Paine, I had already observed experience and comment to despise the system used to control our faking interactions. In the South, where I grew up, same, behavior was enforced by the application of shame and guilt. These remarkable control agents are a system of torture of the mind and heart devised by parents and other authority figures who themselves were likely raised the same way or who could not believe humankind capable of being good for goodness sake, so the fear of God was invoked and instilled. How do you end a cycle so firmly and insidiously set? Ultimately, most of us are broken, and eventually we accept the bit in the mouth and the blinders over our face. We don't see beyond what we have been told exist. We become pack horses for other people's beliefs, and most of us carry that load someone else put on us for the rest of our lives. If I had experienced the people who so firmly believed in religion as peons of virtue, perhaps I might have lingered longer at the fountain of dogma. But my experience was that those who preached to others did not live what they preach, and that includes some of the most famous television evangelists I have had the displeasure of knowing. They preach a doctrine they do not live, and I cannot tolerate that. Hello, Hillsong, y'all.  If you don't know the church's satanic, dig into Hillsong. I have never tolerated fools or hypocrites very well. Besides, I had other experiences as a child growing up as I did in the middle of nowhere. I cannot claim even a small town, not a hamlet, not even a village. I grew up in the middle of nothing, and the tobacco planes of Virginia. There was no other child for over 10 miles in any direction. I had friends in the wind, and the forest spoke to me until I was told that it couldn't. And I will say if you missed Judy's full story, she does write about it in Magdalen manuscript. That is in this playlist, which I will include in the description box below so you can hear Judy's full story of her childhood. One night as I lay down in the bed, three glowing orbs appeared at the foot of my bed. I told that story in the Magdalen manuscript, as I just said, so I will only mention the significance here because it's hard to believe the party line when you've had other personal experiences. I was always interested in the paranormal, so it wasn't the possibility of things beyond our understanding that confused me. It was the subject of God that always made me squirm. Who's God? What would God have to be jealous of? Why would there be knowledge that this God did not want his children to possess? And why on earth would a woman be blamed for wanting wisdom and eating an apple? If there is a metaphor in this, it's lost on me. And there is the issue of fairness and excess.  Because he or she does not have access to the teachings of Jesus Christ. It's the same thing I asked when I was a kid. That is the message of evangelical Christianity and the excuse for missionaries to intrude their belief systems onto others. Yeah, Christianity is super violent. Like it is textbook, one of the most violent religions. It is not the religion of peace. It's got more blood on his hands than Satanism does. That speaks volumes. I'd say it's actually embarrassing. Like the more that I learn about Christianity, the more I'm mortified that that was the religion my parents raised me in. Like I am mortified by that. And I look at people who still cling to the Bible. I'm like, does this not embarrass you? Does it not embarrass you that you are worshiping a God that demands burnt, virginal offerings that it says in your Bible? What is that? That's a child sacrifice.  And are you that deep in a cognitive dissonance that you don't understand that you are worshiping Lucifer in your churches? Lucifer is the God of the Bible. Make no mistake about that. The evidence is everywhere. If you are going to church, I don't care how nice your pastor is, you're worshiping Lucifer and you're putting money into the cabal. Wake up. Wake up. And I agree with her. It's awful. It's horrible what this religion has done. What about the actual things that these Protestant way showers said about women that we looked at at the return of the divine Sophia? I mean, for all this time I've been thinking, yeah, the Methodists are pretty cool. The Methodists are pretty laid back. Nope. The guy who started the Methodist church didn't think women had souls. He believed that when we were past our birthing years, when we went into menopause, that we needed to be taken out back and put down. I don't even think you should do that to an animal. So you're just blindly following because that's what your parents did. That's what your grandparents did. Well, as they said when we were kids, if your friends all jumped off a cliff, would you do it too? Wake up. Christianity is Satanism.  No different than the controllers. Why can't any child live an exemplary life of honor by choice, not fear, and retire to a dimension of plenty rather than burning in the damnation because they'd never heard about Jesus and the name Jesus, as we know, means hell. Satan, the J-cell, did not exist back then. The real name was Yeshua, which does not translate to Jesus. People are like, oh, it translates. No, it doesn't. If you replace the J with the Y in the name Yeshua, that does not equal Jesus. Replace the J with the Y. Let's sound it out together. Yeshua. Now let's put a J in there. Joshua. Josh. Joshua is Yeshua.  Satan. The story of Jesus was created by the controllers. Yeshua or Joshua, Ben Yoseph, was never crucified because the real God, source creator, does not demand human sacrifice. The real God does not demand blood rituals. The real God does not condone cannibalism and the drinking of blood, which is what communion is.  Let's really think about this, you guys. It's common sense. I know common sense ain't that common. I can't. I mean, this is tough love. What you are doing at your church on Sunday is no different than what they were doing on those islands. Judge not, at least be judged. That's in the Bible. Why do you think it's in the Bible? Because you are no different from them. You are doing the exact same religious practices that they were doing on those islands. Wake up. Wake up. Okay.  Exactly. I am reminded of the French Catholic bishop who, when he was asked why he was setting fire to a church full of both good Catholics and what he was considered a cathar heretics said, let them all burn. God will know his own. Let them all burn. What kind of God needs his creation to be willing to take the life of their own offspring to prove their love for him? That's what I just said. Let me read that in the back for those who didn't hear. What kind of a God needs his own creations to be willing to take the life of their own offspring to prove their love for him? That's a birth, virginal offering. That's a child's sacrifice. Wake up. Wake up. That Bible that you venerate as holy is the words of Lucifer.  The real God, the real God does not require this. Sorry.  I cannot believe how duped my own ancestors were. How is this acceptable? It's not acceptable. It's not.  We don't do sacrifices. That's not what we do on the side of good.  My life is a biological fact, not a theological fact. Don't get me wrong. I tried to believe in God. Then after many years of struggling with the notion I managed to accept that metaphysical option for all God. But still I searched. I read and I disassociated myself from the small town and the small minds that tried so hard to tell me what to believe. I have never stopped hunting for answers, searching for the puzzle pieces that would answer fundamental questions that haunted me. Why do we need to worship? Why do we bow down to misguided authority? Why do we call some beings masters? What does that make us? What in us makes us so quick to fall into line and allow slavery of the soul and the body? Why when someone says God, do we think male and see an old, bearded man and automatically go into prayer position, which it evidently means we bow down and think less of ourselves? There was a missing piece of the puzzle of information just like the missing link of our understanding of the biology of mankind, the missing link. I left a successful consulting business in 1986 to come to a small island in the northwest because I wanted to create a book about soulmates. Instead I wound up editing two channeled books I called Last Waltz of the Tyrants and UFOs in the nature of reality. It was my first incursion into alien territory and an alternative creation story. It took me two years walking in the wind at the edge of the ocean to pull it all in place in my own sphere of logic and believability and come to terms with what the possibility of such a creation story might mean. After two years it was if someone had taken a bolt cutter to my mind. Finally after two years the potential of humanity began to result began the result of genetic manipulation by an intergalactic civilization made a lot more sense the story of some old bearded man in a missing rib. If you could read this acturian information with an open mind it could free you. As long as we give our power away to some higher authority we lower ourselves. Let me share with you the creation story as it was given to us by the acturians and the number of other beings as well. They are not the first to tell the story but there are new gifts in the octurian version which we are delighted to share with you and hope that it loosens the binders and that may bridle you and cripple your sight. Eons ago a race of intergalactic technologically advanced beings called the Anunnaki realized their atmosphere was disintegrating and their scientists determined that gold would stabilize it and a scan of our planet showed immense deposits of gold I've heard this this actually is the story I've heard too. They came to earth to mine the golden Africa hence a science was determined. Africa is the cradle of the current civilization because it was in Africa that the Anunnaki genetic scientists mixed the brew of which we were made. Earth's rotation made it difficult for the Anunnaki to stay here for so for many long periods and their people did not didn't want to do the hard work of mining so they looked for a solution for how to mine the gold for their atmosphere without using their own people and their solution was the creation of the homeosapiens. Now I am going to say this because I've said this before with Tom Canyon as far as other channeled books. We know a lot more now factually now than they did when they were channeling this book okay. So when somebody is channeling the channeler is always receiving the message through the perception of what the channeler knows. So we now know if we're looking at Tartaria that human beings did not civilization did not start in Africa. We now know that the fertile crescent is here in the Americas. We also know that race does not come from evolution of geography but more intergalactic DNA okay. So I didn't my skin didn't turn white because my ancestors moved to Europe. My skin is white because I carry mostly Palladian Lyran and Octurian DNA right. Same black people are more serious that they were the serious constellation yeah. So I want as far as the rotation of the axis like we don't really know for sure what's true anymore when it comes to that. So I just want to make that very clear that there can be a level of grace given with error and channeling because when Tom Canyon was channeling this I'm sure like all of us he believed what we had been told in school all right. So he's claiming the information through the filter of what he knows so I hope that makes sense. That's why if anybody knows Tom Canyon I'd love to bring him on the show and ask him about Tartaria right. The clay tablets of early Sumeria tell the story as it was experienced then. Many people have pointed to these early primates as the origin of the human line but the Acturians added a twist I had never heard before. They talked about higher vibrational beings which are electromagnetic in nature called ephemals. Ephemals have always been here and we used to be able to see them though they vibrated a much higher level than we do. They are the fairies.  You guys know I see I see spirits and yesterday I was filming this. These videos that you're watching I've filmed way in advance because as you're watching currently watching this video I'm actually traveling right now so I had to film a lot of these in advance. So yesterday I was filming the April read with Nicole and Sarah and an orb kept going by my face all day this little I could see it. It was like this little lightning bug but it was an orb kept going. I could actually see it not just in the camera but with my eyes. Turns out it was one of my fairies. So I'm taking that as definitely a sign. So hey fairy I see you boo. They were fairies and elves and nose and mythology. They still exist. We have been trained not to see them quite like the supposed story told about the natives who could see Captain Hook's tail ship because they had no frame of reference for them. Some of these you fear experimented with entering the bodies of early primates but there was a window of time during which they couldn't body an animal. If they stayed beyond that window these ferales became trapped in a primate body. That kind of though does match the law of one with the organic portals right like the organic portals and if you missed those videos I'll put all three parts down in the description box below. The organic portals were the bodies created when our planet was moving from second density to third density and so the beings on the planet needed their density bodies so they created these organic portals these bodies that attracted higher density souls to come into the body right so that kind of makes sense what they're saying and now we've gotten stuck in this like samskar loop loop of karma in these bodies so that that makes sense. Though many intergalactic groups tell the story of the anunnaki taking their DNA and slicing it with the early primates to create a slave race to mine gold and serve their anunnaki masters I have never heard the piece about them choosing specific primates for this experiment only the primates that were trapped if termals and I do believe they have messed with our DNA like I do believe I'm RH negative I do believe that everybody should actually be RH negative I think because I don't believe in evolution I used to and then the Great Awakening happened and I realized we did not come from monkeys so the rhesus factor comes they name it after the rhesus monkey so people who are RH positive have what they call the rhesus factor in their blood that's 85% of the human population. I am RH negative I don't have the rhesus factor in my blood a lot of the controllers a lot of the powerful families are all RH negative right because RH negatives do tend to be more sensitive to the spiritual side it is very common for RH negatives to experience a lot of psychedelic stuff seeing spirits I've seen spirits a lot of my boyfriends also RH negative he's a negative and he has a lot of abduction stories so RH negatives also the back of our eyes are shaped differently so you see my eye my blue eye through the the black center bit go all the way if you were to like look all the way in the back my the in the back it's shaped like a diamond whereas someone who's RH positive it's a circle so that means that I am able to see things other people can't all RH negatives that have that particular trait where the back of their eyes shaped in a diamond they call it a stigmatism because you see like differently it's not a stigmatism you're just able to see beyond the dimensions whereas someone who's RH positive can't and so I do think that they added the recess factor to splice spliced it in with our DNA to try to take away spiritual gifts it doesn't matter at the end of the day it didn't really work because a lot of people who are RH positive do also have spiritual gifts it's just there's certain there's certain side effects they're definitely RH negative we like the eye and stuff so I do think that potentially in the future they might be able to remove the recess factor I don't know um I don't want you to freak out if you are RH positive it's fine uh but I do think that that was one of the times that they messed with our DNA for sure for sure according to the Octurians the Anunnaki specifically chose the primates that were trapped ephorals because they had the physical spark about them that set them apart from those primates so again the organic portals the bodies that were inhabited by sold people yeah the higher beings don't mess with organic portals they just use them to do their dirty work but they don't abduct organic portals they don't attack physically attack organic portals they want the the people that have the spark all right in other words they were not just your average monkey we are not the ecclesiastical creation of some god taking a rib away from Adam to create a woman we are a scientific experiment it was genetic tampering not unlike what we do with horses and breeding now so alien intervention in the creation of early mankind is the biological missing link but here's the most important and most dangerous part of the story I realized it was 20 years ago when I did UFOs in the nature of reality but I never heard anyone else support my theory until the Octurians think about it what is one of the bedrock understandings of metaphysics thought creates if we were created with the intention of making us a slave race no wonder re-revert to that position when confronted with what might appear to be anything greater than us god aliens with advanced technology the Anunnaki were a very advanced intergalactic race of beings very unevolved but very advanced that by the way was another major issue of my childhood mind if earlier gods were so great why were they so ignorant and jealous and dangerous you can have great power but not be very evolved evolution is a matter of consciousness power can be achieved with technology but because a race of beings has great power that does not make them great or deserving of servitude because of the concept of the early god specifically Jehovah to name one beastial represent representation of someone's notion of god and we know Jehovah is a demon could blow up a whole city does not make him sacred or great it just means he was powerful I think of Jehovah as an unevolved two-year-old with tremendous power what yeah if you read the missing books the bible Jehovah is the name of a demon sorry Jehovah's Witnesses is okay Jehovah's Witnesses all Christians are worshiping demons so frankly I'd rather have consciousness than that kind of power and I don't choose to fear god if he or she exists I would rather respect and love him or her than fear him or her any god I honor must deserve respect not require fear or groveling so let's go back to the creation story as per the actorians so you have early human beings who were the result of genetic and breeding of the feral's trapped in the primate bodies and Anunnaki DNA hold that thought of creating a slave race remember those two years I said I walked at the edge of the ocean in the wind trying to piece together the reasons for our tendency to bow down to even false authorities I was working on a book about aliens that contained the same information about the Anunnaki but until I reasoned out thank you Thomas Paine that the thought being held when they played with our DNA was that of creating a slave race it hadn't made sense I deduced that over 20 years ago but I had never heard it said by any group or anyone else until now and I only told a few people my theory I suspect we're only given information when we're ready to reason it out and accept it it took me years to make sense of what I was editing then and that was almost 20 years ago thought creates and the human race was created with the thought of creating a slave race so for us to take our full power back and realize the potential greatness of who we are requires understanding of how we got here service to our masters this is in our myocondrial DNA and according to the octurions before our dye was cast there were there have been over 20 additional genetic tamperings from different civilizations and races of beings they say this makes us intergalactic royalty to have such a melodge of genetic information I suspect that the saying when the student is ready the teacher will appear also applies to information when the mind is open the knowledge will avail itself I cannot tell you how privileged I feel to introduce you to our octurion friends and family in this text it is my most fervent hope that you could reason your way to at least considering the information contained herein the truth is when we were invited to participate in the sharing Tom didn't want to participate he has no problem with the concept of Buddha or Saraswati or Master Wu and the various pantheons of many spiritual traditions at all but the notion of aliens has always left him cold the spiritual teacher in him could accept the great teachers of many world traditions but not accept the concept of aliens he called those sacred beings gods and considered them divine I have vanished the word god from my vocabulary and now call them all aliens to me every single being believed to be a god was a visitor from another world possibly another dimension in a galaxy far far away Tom has worked with the Hathors for over 20 years now and I've worked with him through here through him for over 15 years they are truly old friends but he was very hesitant to step any further out onto the alien limb but when the subject of this book came up the one being we respected more than any other asked him to channel to bring through the bacteria material with this being request something we both pay attention this being was known in her only human life as Mary Magdalene and now we know so Judy and Tom if you hear me if you watch my video please stop calling her Mary Magdalene Mary was a very disrespectful name her name was just Magdalene just Magdalene and she is the one who stepped forward and asked Tom to please bring through this material because I know the quality of the channeled information is relative to the evolutionary state of the channel I couldn't imagine any well anyone else bringing through actuarian information at this time because I know the level of integrity in which Tom lives his life I know his keen intelligence I respect the scientists in him and I know he can tune his brain to any frequency and bring in the highest quality information and I know he hates to do it but he never turned down a request from the being known as Magdalene and as it turns out Magdalene is an actuarian as in the magnificent being known as Yishua Ben-Yosef along with the many beings referred to as Ascended Masters Sinat Kumar they were not just actuarian they were primarily Lyra Tom and Judy they were also shapeshifters Magdalene could shape into a lion which is Lyra but you can be a galactic mixture I'm also Lyra and an actuarian and Palladian but let's just we're gonna be honest here we're gonna tell the truth we need to tell the full truth okay they aren't just actuarian all right my alien strands my first conscious experience with the actuarian was in Zemarts with Sirlan at the at the gracious and dear friends apartment Magdalene suggested we use the time in Zermatt to bring through my lineage it was my birthday present as it turns out I'm not from here you may not be either additionally many of us carry emanations energy strands of other beings in other worlds many of us are not from these parts it seems my strands come from the far-flung reaches of space I was once told you are a crossed bread and lined bread to be here now I guess that means I'm not really from Virginia Tom lovingly allowed his consciousness to channel my menagerie several times a week during our visit it was one of the most delicious and greatly appreciated gifts I've ever received I barely remember most of the beings who came through to claim some aspect of my personality but I will never forget the actuarian he was bold and deeply intelligent he was no nonsense one of my favorite traits he shot straight there was a family in the apartment above us and as Tom altered his brain state to bring through this being the people upstairs began to drag furniture around the apartment making the most horrific noise on the tile floor a few feet above us the acturian beamed in to hear those horrible scrape scraping sounds and his first words were something to the fact what are those idiots doing up there I almost expected him to go and knock on their door and demand them to be more respectful I have loved the acturians ever since I experienced many other beings in that amazing time in Zermatt but the acturians struck a hardcore that hadn't been played for me before each of us is a combination of a physical body and a consciousness the physical body may be created by a mix of dna from our physical ancestors from a variety of lands on earth but the spark that inhabits the body and determines the consciousness may be a mix from many other dimensions and many galaxies and you may even have an animation of a being who is held as a goddess or an exalted spiritual teacher but according to Magdalen and the Hathars the deity himself or herself almost never fully incarnates almost never you may carry a strand of a deity an emanation which is why you relate to a particular being or the religion of that deity but it is highly unlikely that any of us is an incarnation of a deity I suspect our confusion about emanations is the reason why Magdalen discussed the subject in her section yeah I have been told that I have the imprint of Hathor I've been told that now by two different spiritualists that don't know each other that never communicated so I get that so I have an imprint from Hathor which makes sense to me even though in the Sophia code the Hathor section I was like this is too mathy I'm not I'm not a math person I don't really like numbers like math is too I'm very listen listen y'all when I was in the fourth grade my fourth grade teacher told my mama that generally speaking there are two types of people in this world there are people who think black and white and there are people who think gray people who think black and white are really good at math and science they want an exact solid answer they want an equation people who are gray thinkers don't need an exact answer they are good at philosophy they are good at the arts they're very artistic they are good at debating they're good at speaking and my fourth grade teacher told my mom that my sister and I or two different thinkers my sister was black and white thinker I was a gray thinker and that because I was a gray thinker I should not really be pushed to try to excel in things like math because that's just not how my brain worked and we needed to honor that my brain worked in a more gray way and boy was she right because let's be honest that's what I excel in I you know studied English in school at literature and I went to Indian study philosophy basically like that is not and it's and I can I can entertain very out there ideas and I don't need a reason why right so so I get that like math so the fact that Hathor is one of my big soul imprints she's all about the math like literally cracks me up because that is not maybe my twin flame is good at math I don't know maybe maybe my half of the soul is the the artsy fartsy like philosophy based side of the soul and his side of the soul is like math I don't know I don't know but I just find that funny God does have a sense of humor though so the actorians clearly wanted to use his opportunity to address issues their civilization was facing as a backdrop to issues we must also face the dilemma of the heart versus the mind they voiced grave concern over our lack of respect for our environment and suggested meditation techniques they also seem to be using this opportunity to explain their defense of earth and to announce that they would be contacting many more people on earth they tackled one of my favorite subjects the dangers of religion and mind control which is rampant today in my opinion power does not equal consciousness it has been my pleasure and my delight to transcribe what these magnificent beings had to say I get to hear it firsthand directly from the horse's mouth so to speak we never change of word of what's given and Tom and I purposely do not read whatever anyone else has written about the beings we work with to be sure that we deliver is what we deliver is original to us I'd like to leave you with one last thought as you enter these pages we are all divine beings with the capacity of greatness that knows no bounds we have purposely been lied to by the religious and governments and buried in a swamp of shame and servitude giving up ignorance does not mean you give up your commitment to evolution and the ascension of your spirit you do not need to grovel before anyone to ascend and evolve looking back I'd say the issue I have with the UFO community is that they've left out spirits and the issue I have with the new age community is that they tend to give their power away you can be powerful and fully conscious and free and I agree I think that's interesting that she talked about I I know that we were created to be a slat of something I agree with who were created to be a slave planet right by the bat and onaki by the Draco and so that's interesting though that that is in our DNA to be have a propensity for mind control right and I'm not just talking about the people in this world who are getting the zappardey doodaw and still believe in the event of 2020 I'm not talking about that I there are people in this this truther community the seeker community that are also being mind controlled by witches and warlocks in the truther community that have got their mind enslaved to bondage so that's they know that so the so that's an element that we now learn the controllers do know that our DNA is programmed for mind control so now we have to understand that because knowledge is power knowledge protects when we have to move forward and try to understand that we are programmed to buy splicing of our DNA to be a slave planet and so that's what we are fighting against our own our own propensities to fall into mind control right so anyway all right you guys I hope you're having a wonderful day and I'll talk to you soon


Hi and welcome to the session. I am Shashi. Let us do one question. Question is, find the 20th term from the last term of the AP, 3A, 13 till 253. First upon, let us understand the key idea to solve the given question. If L is the last term of the AP, then the N-th term from the end is the N-th term of an AP whose first term is L and the common difference is minus 10. Generally, we know the general formula of N-th term is equal to A plus N minus 1 multiplied by D. So, L-th term from the end is equal to last term as last term will become the first term. So, we will write last term plus N minus 1 multiplied by minus E. D will get replaced by minus D. So, we get the formula for L-th term from the end is equal to L minus N minus 1 multiplied by D. Let us now start with the solution. We know given AP in the question is 3A, 13 till 253. Now, clearly last term of the AP that is L is equal to 253, right? Now, common difference that is D is equal to 5. Now, we know the formula for N-th term from the end is equal to L minus N minus 1 multiplied by D as we have already understood in the P-idea. Now, L is equal to 253 and D is equal to 5. So, we get N-th term from the end is equal to 253 minus N minus 1 multiplied by 5. Now, we have to find that 20th term from the end. So, we can write 20th term the end is equal to 253 minus 20 minus 1 multiplied by 5. Now, this is equal to 253 minus 19 multiplied by 5 which is equal to 253 minus 95 which is further equal to 158. So, we can write 20th term from the end is equal to 158. So, 20th term from the last term is 150 H. This is our final answer. This completes the session. Hope you understood the session. Take care and goodbye.


I hope it's not on the screen but I'm not re-recording it because brilliant story. Keep watching to find out what book we're talking about today. It's Kylo Denigno and welcome to Kylo's reading day. So today we're talking about the book Queenie. The author of the book is Candice Cardi Williams. The genre of the book is fiction. The theme of the book is literature. We're gonna jump right into it because I will tell you the entire plot of this book. I absolutely adored it. My favorite quote in the book is from Cheska. I'm gonna put the spelling here. I will I'll be honest to say I had to listen to the audio book just to learn how to pronounce this word. I would not look at this in here Cheska but it is pronounced Cheska. So one of the most important quotes in the book comes from Cheska where she says you can be any kind of black girl you want to be. Okay so now that quote is so important to the story because this book is all about judgments. Judging yourself, judging other people, judging relationships, judging things you don't know. So you have Queenie who's going through a break and she doesn't know how to cope with the fact that her feelings are hurt from her breakup. She starts to date, she starts to hook up with men, she starts to do all these things which then causes her friend Cassandra to judge her. Ends up calling her all kinds of names, all kinds of things and Cassandra's even judging Queenie. Cassandra makes a statement in the book where she says sure I'll loan you some money but where's your other money? Savings? All of that? That is uncommon for younger black people. Okay Queenie made that be known. Girl it's not a given that I have savings and then you find out later that Cassandra comes from this great Jewish home and her dad helps her with most of her bills. She lives with her dad and you're just like well yeah you do have a lot of disposable income. Queenie does not. But then Queenie is judging her mom. Her mom absolutely broke her heart. There were a number of things that happened where Queenie's mom just did not live up to what Queenie thought the mother should do and Queenie's never raised a child so Queenie you don't know. So she was judging her mom without knowing, without walking through the mama's shoes and then lastly this cannot be understated. Queenie loves but she judges her grandparents hard core.  Like the story about the grandparents was so reminiscent for me. I was like man I missed my grandma because it's things that grandparents do that they can get away with just because they've lived so long because they are the parents of your parents. They can get away with so much but let me tell you the grandpa and the reason why he doesn't want to drink but then he ends up being one of Queenie's biggest allies but Queenie had to get over the judgment she had from them.  Oh you don't understand. Oh back when things cost three pounds and so when Cheska says you can be any kind of black girl you want that was one of the starting points for Queenie to say you're right is what I'm going right now what I want and how would I change it okay so a brilliant brilliant story brilliant brilliant brilliant brilliant story it's really really important that you can be any kind of a girl that you want right don't judge yourself don't judge what you think you should do don't judge what you think you shouldn't do be the person that you want to be okay bonus because sometimes I'm gonna give you a bonus there's a word that I've been using for at least the last six years and the word is Mazungo okay my husband is Ghanian and his best friend best man really close friends to the family is Rwandan and they always say Mazungo and they'll say oh is it a Mazungo meaning white person or white girl in this book in this case I've never seen it in print and I felt I felt really proud I was like wow when they say representation matters I'm for it because the word Mazungo is in a book so would I reread this book yes in fact when I started Kyla's reading day I immediately started thinking about books that I've absolutely loved that I've already read and I had actually read this 121 weeks ago so thank you for hanging out with me today as we review the book Queenie please let me know if you enjoyed this video give it a like that really does help you to share the book reviews with other people it helps them get it out there to other people who enjoy books other people that enjoy book reviews so thanks for hanging out with me today on Kyla's reading day I'll see you next week bye


Cadman Presents to Kill a Mockingbird by Harper Lee Read by Sissy Spasic Copyright 1960 Renewed 1988 by Harper Lee Production Copyright 2006 by Harper Collins Publishers Lawyers, I suppose, were children once Charles Lamb Part One One When he was nearly thirteen, my brother Jim got his arm badly broken at the elbow. When it healed, and Jim's fears of never being able to play football were assuaged, he was seldom self-conscious about his injury. His left arm was somewhat shorter than his right. When he stood or walked, the back of his hand was at right angles to his body. His thumb paralleled to his thigh. He couldn't have cared less, so long as he could pass and punt. When enough years had gone by to enable us to look back on them, we sometimes discussed the events leading to his accident. I maintained that the Ewells started it all, but Jim, who was four years my senior, said it started long before that. He said it began the summer Dill came to us when Dill first gave us the idea of making Boo Radley come out. I said if he wanted to take a broad view of the thing, it really began with Andrew Jackson. If General Jackson hadn't run the creeks up the creek, Simon Finch would never have paddled up to Alabama, and where would we be if he hadn't? We were far too old to settle an argument with the fist fight, so we consulted Atticus. Our father said we were both right. Being Southerners, it was a source of shame to some members of the family that we had no recorded ancestors on either side of the Battle of Hastings. All we had was Simon Finch, a fur-trapping apothecary from Cornwall, whose piety was exceeded only by his stinginess. In England, Simon was irritated by the persecution of those who call themselves Methodists at the hands of their more liberal brethren, Simon called himself a Methodist, he worked his way across the Atlantic to Philadelphia, thence to Jamaica, thence to Mobile, and up the St. Stephen's. Mindful of John Wesley's strictures on the use of many words in buying and selling, Simon made a pile practicing medicine, but in this pursuit he was unhappy lest he be tempted into doing what he knew was not for the glory of God, as the putting on of gold and costly apparel. So Simon, having forgotten his teacher's dictum on the possession of human chattels, bought three slaves and with their aid established a homestead on the banks of the Alabama River some forty miles above St. Stephen's. He returned to St. Stephen's only once to find a wife, and with her established a line that ran high to daughters. Simon lived to an impressive age and died rich. It was customary for the men in the family to remain on Simon's homestead, Finch's landing, and make their living from cotton. The place was self-sufficient, modest in comparison with the empires around it. The landing nevertheless produced everything required to sustain life, except ice, wheat flour, and articles of clothing supplied by riverboats from Mobile. Simon would have regarded with impotent fury the disturbance between the north and the south as it left his descendants stripped of everything but their land, yet the tradition of living on the land remained unbroken until well into the 20th century when my father, Atticus Finch, went to Montgomery to read law, and his younger brother went to Boston to study medicine. Their sister Alexandra was the Finch who remained at the landing.  Sample complete. Ready to continue?


operator, and other in the chairman on board, they wanted to try some other stuff on board. No children? No children? No, no farm labor. So I can go to the Womble? Yeah, you can go to the Womble. Alto. Alto.


I gave her the doll on her birthday. She loved it at first and told me it was so beautiful, that its hair was so soft and the dress was so pretty. She wouldn't let it out of her sight for days. Through the daylight hours she set it on the table so she could see it while cleaning the house. And at night time it sat next to her bed, watching us sleep with big blue, unmoving eyes. But my daughter's love for the doll soon changed, soon I noticed something was bothering her. I asked of course, but she wouldn't tell me. She said the doll was just being silly. I could notice that day after day she became more reserved towards me, until I couldn't take it anymore. I pressed her, told her she would tell me what was going on right now or I would take her to the doctor. She finally broke down crying, the words came spilling out. She told me the doll scared her. It was constantly watching her, sometimes it even seemed to move. This worried me, and I went to take a look for myself. The doll sat motionless on the little table in her bedroom. Its eyes were dull and unchanged, and I couldn't help but sigh in relief. Of course she's not moving. I went to look away, but then saw a tiny movement from the corner of my eye, holding my face close to the doll's eyes. I stared into them. Something was moving, trying to concentrate. I looked closer, yes there definitely was movement, but not from the eye itself. It was behind the eye. Suddenly I burst out and onto the floor spilled at least ten wriggling maggots. I dropped the doll in shock, backing away instinctively. My daughter yelled from the other room, asking me what was going on. I yelled back at her not to worry. Picking up the doll again, I used a tissue to wipe away the maggots. Suddenly I saw more, pressing against the skin and plastic outer layer. So soon, I had hoped she would last longer, I'll have to get her a new one. Maybe keep it alive at first, that way it'll last longer for sure. My daughter always said she loves the blonde hair of little Katie down the block.


Welcome to JSA TV and JSA podcast, the newsroom for tech, telecom, and data center professionals. I'm Buffy Harakitas, coming to you live from Channel Partners 2022 in fabulous Las Vegas. And joining me today is Mario DiRigi, Chief Revenue Officer for Fusion Connect. Mario, welcome to JSA TV. Great to see you again, Buffy. So great to see you. Thank you for having us. Yes, yes. Mario, recently Fusion Connect announced a $55 million round. Can you give us a little more information about that? Sure. So back in mid-January, we made an announcement that the company went through a restructure led by Morgan Stanley, private equity, and some of their affiliated funds. And really what this did to us, it was a recapitalization of our balance sheet. We had a reduction on our debt by around 80%, which allowed us to invest more in a business. And they also gave us a $55 million cash infusion to help us fully fund our entire five-year growth plan. But the most important part about that cash infusion was we had 17 senior officers of the company also invest their own personal funds as part of that investment. And why is that important is because there is a strong belief in what we're doing, what we're building, and more importantly, in the ability to go out and exceed our business plan for the next five years. So really, really exciting times. I mean, we have so many great things that we are going to be working on. A lot of it is going to be on product development, right? So we are really transforming the company to a managed security service provider. So a ton of product development. But the biggest thing, I am the recipient of most of that funding because we are doing a massive expansion of our sales, both direct channel, account management, our marketing, and also our support functions for our partners. So for me, this is us getting closer to our partners, closer to our customers, and really going out and building that exceptional. And I mean, we really want that exceptional experience for our partners who also want that for their customers as well. Thanks, Mario. And recently, you just announced the channel alliances. Can you give us a little more information about that? Sure. So we promoted Diane Frazetta to our vice president of channel alliances. So Diane has been with the company for a little over a year. She came in and she really ran the eastern part of the country. She did a phenomenal job of rebuilding and getting it really to the point where it is far exceeding objectives. She has been a long time in the industry, a lot of time on the actual suppliers, on the partner side. So she has a great mix of understanding what the partners want, as well as what we need to do to deliver to drive a better experience for them. So yeah, so she was promoted to our VP of channel and alliances, just really, really, really excited for her. She is just going to be a great asset not only for the company, but more importantly for the partner community. That's wonderful, Mario. And with so much going on in the digital workforce today, can you tell us a little bit more about how Fusion Connect is empowering the digital workforce? So if we speak about digital workforce, I really want to focus more on the hybrid workforce. So what this pandemic has told us is people want flexibility to work from anywhere on any device. So a hybrid workforce is here to stay. It is not going away. And those companies need to now adjust their policies for the ability to go out and give that flexibility to employees because they are competing against other organizations that are offering the flexible workplace. We did a workplace study. Over 30% of the companies out there said that they are going to stick with the hybrid workforce full-time. I think that number is going to continue to grow. But there are certain things, when you have that hybrid, that you need to make sure. Some of the risks there is how are you insuring the productivity of those employees when they're home? So security, access, collaboration, messaging, how are you giving them all the tools you need, they need, excuse me, to really be effective and optimize their work experience from any place, any time, any device. Any place, any time, any device. Got it. Well, Mario, it was such a pleasure to have you here at JSA TV today, live from Channel Partners 2022. Fusion Connect has been a leader in the channel for so many years.  Can you tell our viewers where they can go to find more? So we are in our booth. So we're right on the front row coming in. So please stop by there. We have a plexiglass room right in front there that we are doing some meetings. And we're also in the Versace 2403 meeting room. Stop by. Come see us. We'd love to get to know each other. How about for those viewers that are not here at Channel Partners? So if you go to our website, we have a channel coverage map with all the contact information for who covers your territory or your geographic region. You can click on it. Contact numbers will come up and do it. Or more importantly, Mario D'Riggi,<PHONE_NUMBER>, Mario.D'Riggi at FusionConnect.com. The hottest email in the channel. Mario, thank you so much for joining us today on JSA TV and JSA Podcast. And viewers, thank you for tuning in to another episode here at Channel Partners 2022. Be sure to follow JSA on LinkedIn and Twitter and at hashtag GreenerData for all you need to know about the launch of our book and our movement, GreenerData on Earth Day, April 22. Happy channel networking.


All right, how's everybody doing? Having a good time? All right, how many people here use TOR? All right, how many people trust TOR? No, there we go. How about that? That's good to see. Well, these two gentlemen have been working on a project that is going to help us maybe perhaps trust TOR a little bit more, or at least find those people that are out there messing around with TOR, making it untrustworthy. Let's give these two guys a big round of applause. Thank you for the introduction. It seems that we have a problem with the slides. I'm not sure enough. So, apparently, they're working on fixing it. In the meantime, we're gonna start. I'm Guevara Nubir, and this is a joint presentation and work with Amir Ali Sanatina. We are both from Northeastern University. We work on developing security privacy techniques, building systems to enhance security. We're also interested in investigating the potential of attacks on the real-world systems, and therefore this work. So, unfortunately, you cannot see the slides, but the talk is about something called honey audience that we develop, and it is about exposing snooping, TOR, HSDIR relays. So, this is in the context of TOR. A large number of people use it. It's quite popular. We're interested in understanding how many of the TOR relays are misbehaving. These are relays that the host was called the Hidden Services. And in fact, this issue that we're gonna be talking about is known to the TOR people, and they've been working on having long-term solution and also short-term solution. Our interest was in knowing how many today of these relays are misbehaving. The next slide that you can see, unfortunately, is about what is TOR. TOR is a very powerful and popular tool for enhancing privacy. I personally, yes, so, so, I personally regularly use TOR. Any time, for example, I want to check something that has to do with Heldt or any when I Google something, I don't want to have the whole world know about it, so I use it, and I feel that among the systems that exist today, it's really one of the best systems that one can use. So maybe one question to the audience. So the first question was how many of you know about it? So how many of you use it? Okay, fair number. So how many of you run a relay? So how many of you have a hidden service that's running? Okay, I see much less numbers, and it could mean that maybe some of you don't want to even disclose this information. So this work is about showing that, well, in fact, you can't, while you can't trust maybe TOR about various kinds of things, you cannot trust that your hidden service, the existence of it is not hidden, and this is the goal of this work. So TOR provides two types of services that are quite well known. One of them is that you can browse the internet anonymously, and it says that you can go to some website, and the goal is that your ISP, the website, would not know that you're doing so. The type of services called hidden services. It allows one to run a server, a website, for example, and no one would be able to know what's this IP address, and therefore it's a physical location. So TOR is used by a large number of people. I think they have over a million people every day that would use it. Most of these users are normal users. So most of them try to browse the internet, don't want to reveal things about themselves. Some people try to circumvent censorship.  You also have a fair number of journalists. Whenever they want to communicate with their sources or they want to access information, they don't want to reveal that. So that is another type of use of TOR. You have also activists, whistleblowers. They don't reveal information about themselves, who they're talking to, what information is being shared. You also have law enforcement and military use. They don't reveal information about what they're doing. They also sometimes they also want to hide among the group of larger people who are much more normal. And obviously you have also criminals who use TOR for their activities. In fact, I don't see, you don't see the slides, but so the next one is about hidden services. A hidden service is basically this capability of being able to run this website or server and hide its physical location. It has other side effects that are quite interesting. One of them is by reading your website as a hidden service, you can hide, you'll have this self-authentication. You don't need certificates because the onion address itself includes information by the public key and allows you to self-authenticate. It allows you also to have end-to-end encryption. And there are many systems besides websites that use TOR hidden services. SecureDrop, for example, used by the New Yorker or the Guardian, allows one to communicate with journalists and provide information to journalists. But even mainstream systems like Facebook, they have a hidden service. You have also applications like Ricochet that allows secure messaging and every client runs as a hidden service so you can hide the identity, the clients who's talking to him and you also get rid of central entities. You also have other types of people who use it, like the Silk Road, for example, run as a hidden service. You have ransomware like CryptoLocker used hidden services so that they could hide the location of the server that collects the bitcoins that people would have to pay. So there's a variety of people who would use it. So maybe to also clarify, you know, for this talk, so TOR claims to have a set of properties, but it does not really claim, for example, that it will give you, if you go use a TOR browser, you don't have any guarantee that you have end-to-end encryption because if you just browse a website that does not have HTTPS, any traffic going from the exit node would be in the clear. For hidden services, when you create a hidden service, there's no guarantee for you that that hidden service, its existence is protected. TOR aims at, at least in what they have as a system today is that you can't really tell where the location, but not the fact that it exists. And this work was about finding out how many relays misbehave, trying to get this information as an indicator of other malicious activities. Within the space of, in general, looking at privacy infrastructure and attacks on it. So whenever you have a privacy infrastructure, various kinds of entities try to attack it maybe to reduce its popularity or to misuse it. I mean, cryptography in general, used for good things, a lot of people try also to misuse it. And there has been work related to this, trying to find out how many of the exit relays would be snooping into the traffic of users. Which is different from what we are doing. Other work looked into all these hidden services, what kind of information, what kind of content do they have? So here, what we want to know is out of the TOR relays, the subset of them that can serve as, have this hsdir flag, therefore they host descriptors about the hidden services, how many of them are misbehaving and misbehaving, meaning that they log information that they're not supposed to do. So whoever is running, they modify the code to be able to log this information. And later on, they might visit these websites. And as I mentioned, this is a problem that is known to the TOR people and they've been working on resolving it. And they have other techniques that they use to identify these misbehaving relays. Our techniques have the advantage that we can cover a larger scale of misbehaving devices. So this is not really about breaking the privacy of TOR in terms of you browse someplace, but more about the hidden service existence. The questions we try to address, there are four of them. The first one is how many of the TOR relays are misbehaving in the sense that I defined? Oh. Yeah. This makes my life easier. So there are four questions we're trying to address. One of them is how many of them are misbehaving? And if you could have a small number, lower bound to that number, we have an idea about how much misbehavior is happening in TOR. The next thing is that which one of them are snooping in terms of trying to find out information that they're not supposed to collect? The third one, what do they really do? How much are they just collecting information? Do they try to attack, are they aggressive or not? And the last one is who they are really, besides what relay and what's IP addresses. So we have addressed mostly the first two questions and a little bit of the third one, the last one, but really who they are that we didn't really solve. And this might be, you know, nice community for looking into that and pushing this work to the next stage. So first maybe I'll explain a little bit how hidden services work. This diagram somehow summarizes that. So to run a hidden service, what you do, you pick a random public key. And some people will go and select one that will end up in an onion address that they prefer, like Facebook has a nice one. But typically you pick a random public private key, you hash the public key in a specific way that gives you the dot onion address. Then what you do, you pick a subset of the relays, it's called introduction points, a few of them, and you set up a TOR circuit to them. These introduction points will help people come back to you later on. Then you hash your dot onion address with time information and other things, and that gives you a descriptor, a descriptor ID. And it also tells you which relays with this HSDIR flag you should put this descriptor information with. And you're going to find the two and then you end up with a set of six relays with the HSDIR flag where you'll put the information.  And that's in, and then in step three, this client, he'll take the dot onion address and he will hash it the same way you did. And every day is going to give him the descriptor IDs that will tell him which HSDIR relays he should come to. So in step three, he will go to these relays and ask them what are the introduction points to be able to talk to this hidden service. In step four, the client will also select something called the rendezvous point. Some other relay, he sets up a circuit to him, relays with the HSDIR flag, which one of them are misbehaving in the sense that I defined earlier. So now going back to just a little bit more specific about the HSDIR. So you have the, these relays, they have identifiers and that will show up in something called the ring of HSDIR identifiers. And your onion address, once you hash it, gives you this descriptor ID and you find the first HSDIR after your descriptor ID. And you pick the first three, I mean the first one, second and third. And then you hash it again in a different way and gives you another descriptor ID. And then you find the other two after, or the other three after that. And you have now three and three relays that will host information how you would be reached. The reason why it changes every day and you take more than one is to have reliability and protect against denial of service. Such that if you're always hosting information in the same location, someone who wants to block you, he might have that information and won't serve it to anyone. The side effect is that whenever they host that information, they can log it and they can go visit your system that you don't want to leak. So our system, how to detect who's misbehaving, the idea is quite simple. We can create a large number of these things, we call honey onions like honey pot. We set them up in a secure way in the sense that we follow all the instructions that they're not going to leak. We don't tell anyone about them. We know that if someone comes to visit our service, then whoever had the information leaked it, logged it and maybe gave it to someone and leaked it. So that is the fundamental idea. But it is not that trivial because information every day, you're going to give it to six people or six relays. So it could be any of the six. We'll have to find out who out of the six. Since we want to look at the global scale, we generate several batches. Every day, we generate some number. Every week, another number and every month, another batch. The reason for this is that some of them will collect these onion addresses, but they won't visit them immediately. They will wait for a few days to confuse us that it might be someone else. So we could compute that we need 1,500 onions to be able to cover more 95% of these relays. So every day, we generate 1,500. Every week, 1,500. And every month, 1,500. And then we see who's visiting. Some of you remember there was a peak in the tour number of hidden services. So I don't have time to comment on that, but it is not us for various reasons. I mean, that number was much larger than what we generated. We generated, at any moment, we had 4,500 onions in the system. So before I bore you a little bit with some math, I'll just show you the reason. So we choose this name, honey onion, because it made sense. Then we go a little bit and we found that, oh, it has a meaning. And it was, in fact, quite interesting that the meaning really matched what we were doing. So we couldn't resist using it. So how do you find that who's misbehaving? The idea is quite, again, so we create the onion, we put it on six places. If one of those is misbehaving, we know that one of the six is bad. But then, as we create more, they might end up in different locations. And now we have that, for these two onions, the visits, there are two people who could explain it. And then later on, we put more and you can tell what these are maybe not the guy, depending on the assumption and so on. You can see that there is some maybe possible way how one could find out about who is misbehaving. So the architectural system that we built, in step one, you generate all these onions that you're going to place on these servers. Then some of them get visited. Whenever there's a visit, it gives us information that all who knew about it should become suspicious. We put them in some graph that we built. It's called a bipartisan graph that has nodes that correspond to onions and nodes that correspond to relays. And whenever there's a visit for the onion, we put all the edges to all the relays that had this information. So since I'm running a little bit out of time, so maybe get to what we exactly did. So I'm not going to maybe talk about details of the math. The first thing is that we wanted to know what is the smallest set of suspicious of relays that could explain the visits that we see. That will tell us the lower bound on how many of these relays are misbehaving. If you find the smallest set that explains the visits, we know that there should be more than that that are misbehaving. And there's a way to formulate it, but I'm going to skip maybe that math. This is not necessarily a trivial problem. There's some heuristics that could give some approximation. And we could formulate this as something called integer linear program. Basically, to each relay, we're going to give some variable, either zero or one. One meaning that it is malicious. And we want to minimize the sum of these XIs such that you find the smallest set. But we need to explain every visit. And this can be solved with something called ILP solver. And before we tell you what we found, why we trusted this technique works reasonably well. Well, we also did some simulations selecting some of these to be malicious and so on. And you can see that we can get between 97% accuracy to 81, assuming 81 means that there was a significant number of malicious ones. So now I'm going to pass the talking to Amir Ali, who's going to tell you the results of the experiment. Good thing the slides are back because otherwise I didn't have much to talk about. Here we can see from left to right on the bottom, you can see our schedule for daily, weekly and monthly visits. And the reason behind having three schedules is if adversary visits a honey and immediately we can catch them in our daily. But if they would wait for a why, then they won't show up in the daily. But we can still spot them in the weekly and monthly. The other thing, as was mentioned by Gohara, the rise in the number of honey, onion services, we only, at each point in time, we only had 4500. But the number of increasing onion addresses was at least more than the magnitude, much more than what we had. So we are sure it's not us. And we started our experiments on February 12th. And most of the results that we explained are based on the 72 days that we are running this experiment, although we have them for further and we discuss them later. We are sure that the visits are not a result of the rise in the number of onion addresses because the increase was happening on 18th of February. And we can still see visits even happening on 12th and 13th of February. So it happened before the increase. The other thing to mention in the daily graph, you can see there are not many visits during the peak. One of the reason is that to get the HSTR flag, it would take 96 hours or four days. So after people saw there are a lot of new onion addresses, they probably set up new relays and it took them four days to get the HSTR flag. And after that, they started probing. The other things that you see more visits on weekly and monthly because they are running for longer time. So these adversaries or the malicious HSTRs had more time to visit them. This is an example of a typical connectivity graph that we had. For example, the gray circles in the middle are the onions, the visited onions. And the black ones above them are the HSTRs that are picked by ILP and that explain the visits. All the other colorful nodes are the other HSTRs who have been hosting these onions. As you can see, for example, for the orange one top right, that one is more trivial to pick because you only have one HSTR who visits both of two onions. But the power of ILP really comes in the cases with the purple one, the top left. When you have many HSTRs who have been hosting many of the visited onions, but you want to know what is the lower bound or who are the most likely HSTRs. And that's where really our technique and ILP comes to power. And we can pick these four and identify these are the most likely suspicious HSTRs. And apparently we are running out of time. So the snooping behavior, we saw some of them visiting everything. And we are hosting Alibaba. They were visiting most of the onions. And they tore people. We identified them. We talked to tore people. And after a while, they become more advanced and they delay their visit. The bottom left graph. And the geographical location, we mostly see them in Europe and Northern America. It's because tour is more, and it's also representative to use the shop tour. You don't have it much in Middle East and China because mostly blocked. And this location doesn't necessarily mean that these are the countries who are snooping. These are the relays that are located in these countries, not the country themselves. And to give you more statistic, more than half of them are hosting on cloud infrastructure. And they also had the exit flag, about 25%, which is much more than what you would have. And some of them are doing some attacks. And some of them are less aggressive. So maybe just one final comment. So since we've done this work, in fact, whoever was snooping changed their behavior. And now, in fact, you can see that most of them delay. They don't really visit quite immediately. They wait for days and sometimes a week before they do the visits. So this is still an interesting problem. They could stop here. Sorry that we couldn't really talk about the last part in detail.