All right. Well, I'll go ahead and get started. My name's Adam Hevner. I work for Pivotal. And I'm the product manager for LoggerGator. We have some pretty dense content coming up. So I did upload these slides to the CF Summit site. There's a bunch of links that you can get from the slides. I'm also on Twitter at Ahev. And I've put together a couple of medium posts to distill some of these thoughts in the written form as well. So feel free to reach out to me on either of those social networks and appreciate your interactions there. Let's use the fancy clicker, maybe. Before we get started, I just want to express my gratitude to the foundation and to Pivotal. LoggerGator has a lot of very interesting problems and Pivotal pays me to work on them. So it's a really fortunate and virtuous cycle that I find myself working in. And I'm really thankful to be a part of such a great community. It's really fun to be here and meet a lot of different folks. So for today's agenda, we're going to start by talking a little bit about what service level indicators we like to look at for LoggerGator. I'm going to talk, in particular, about working with Pivotal's SRE and the Pivotal web services environment, as well as the Pivotal Tracker environment. The SRE team for Pivotal manages two major environments. And we're looking at service level indicators on both of those. And we'll see how we're meeting service level objectives. We're sort of exceeding service level objectives in one of our environments. And we're struggling a little bit more to keep up with the goals that we've set for ourselves and the other. I'm also going to spend some time to talk about the future of LoggerGator and the V2 API. I was just prompted some questions about how you can learn about what LoggerGator is working on. And I'm going to share some of the resources that we're using for sharing our feature proposals and tracking our work. If you didn't attend the CF Summit in Santa Clara, I gave a talk there called Improving Message Reliability in LoggerGator. We've really made pretty dramatic improvements in our message reliability over the last year. And some of the content's repeated in that talk, but it's available on YouTube and is a great primer for the improvements we've made over the last year. So before defining a service level objective for LoggerGator on your platform, there's a few things that we think that operators should consider before trying to set some specific goals. The first thing is how many developers that your platform is supporting and what their expectations are for the CF Logstream? Are they writing tests against that Logstream? Are they expecting a certain amount of reliability when testing against that Logstream? Those are important questions to ask yourself. Additionally, are you using syslog drains on your platform? Many operators, and especially if you're using a multi-tenant environment, are going to be using syslog drains. And they're an important tool for long-term storage of your logs. And they're really the preferred way for storing app logs for long term.    And then last but not least is considering what compliance or auditing needs that your business may have. With any service level objective, 100% is not a realistic target. So be prepared to have that tough conversation with your business stakeholders. But also know that whatever objective you set for a loggergator is only as good as your network and your infrastructure. So being able to measure that over the course of the year and provide reporting on how good you're doing is really the foundation that's kind of the experience in the roadmap that we'll walk through that Pivotal Web Services has been on. So for each of these, we have a little bit of tooling that we'll walk through. Sort of, if you think about monitoring and defining service level indicators, much like a pyramid of testing, sort of the base of the pyramid for monitoring needs for a loggergator is to monitor your log stream. And I'm going to share a tool that really makes that easy and simple and something that really any operator or anyone can get set up doing quickly on the platform. Monitoring syslog drains is a little bit more challenging. But again, if you're using syslog drains, especially for an important business function, then it's something that you should also invest in tooling for around monitoring. And again, I'll share a repo where we have some syslog servers and other things that you can easily deploy and use to create some black box monitoring tools. And then last but not least, if you are monitoring the fire hose, there's a Bosch add-on called the Bosch HM forwarder that will monitor the Bosch health metrics of each of the Bosch deploy components on your IaaS. So this is an important tool. It does emit them into the fire hose by default. So it typically is also looked at through the fire hose. But you can look at it independently. So it's a good way to make sure outside of the fire hose that your actual Bosch deployment is up and running. So if loggergator has a problem but the rest of the platform is still functioning, you can actually account for what's going on there. So like I said, at the base of the monitoring period is monitoring your log stream. And a really simple approach to this is to use a black box approach where an application is producing logs and consuming those logs. We created a really simple application called CF logbond. And kudos to the Pivotal Labs team. They helped us put a very simple interface on this so that you can actually deploy this app with CF push. It doesn't require any operator scope or fire hose access. And you can get a very simple numerical value of how accurate or how reliable the log stream is. Now, you can do a couple of things with this. You can set it for different rates of emission. And you can also use a new service that's in the process of being open sourced by Pivotal, which allows you to take metrics produced by the application and emit them back through the fire hose. If you're interested in monitoring using the fire hose and some of your existing tooling, CF logbond is a tool that will allow you to do that. You'll just need that metrics forwarder service to put it into the fire hose. One of the things that we found working with the Pivotal SRE team is that they have needs that exceed the capabilities of a logbond as a prepackaged application. So we implement our black box monitoring tooling using a pipeline. We use concourse. It allows us to provide a consistent set of monitors across a number of foundations. So we currently monitor five foundations. And this is kind of the first look at our view into some of the service level indicators that we've been using for each of our environments. With service level indicators, it's really helpful to work with your operators to set a simple indicator that can represent the overall health of the system. And like I said, we're kind of working our way up the pyramid. And relying on Logstream as a way to assess if your logger gator deployment is accurately scaled is a really good first step. And we've really started to target a high level of reliability for Pivotal Web Services. You'll see over the past two days, when I grabbed this screenshot of our monitor, we had a perfect score. We didn't drop any logs in that time period. It's pretty unrealistic. We haven't seen that for, I think, longer than a few days. I'd expanded this out to a week. And we were, I think, hit the target that we see below, which is three nines and an eight. What we have been landing on and what we're shooting for for the first year of consistent monitoring is two nines. So 99% reliability over the course of a year is what we're targeting for the Pivotal Web Services environment. I mentioned Pivotal Tracker. That's the third one on the list. And as you'll see, we're actually not meeting our reliability target right now on Pivotal Tracker. And we're working with the Pivotal SRE team to understand why that's occurring. We try to take a bit of a hands-off approach so that they can consume our documentation, our scaling recommendations, and see if they're actually being effective. So we're working with them to see, why is it that that deployment is not seeing the same reliability as Pivotal Web Services? Rolling your own black box monitors is something that is really not too difficult. There are a couple of different repos to access. The Logurgator Tools repo is really where you can find all of these things. Logmon is included there. There's an application called LogSpinner, which allows you to produce logs at known rates. And it also has a link to RCI, which has some pipelines that will start to execute these things on regular intervals for you. So as you move up the pyramid, you'll want to look at white box monitoring solutions as well. So this allows you to peer into the Logurgator system. And we found a couple of different ways that this is especially useful. One of those ways is monitoring infrastructure metrics you're probably already familiar with. So CPU and network I.O. are especially important for the Logurgator system. So looking at each of the components and checking for CPU and network I.O. is often something that we're looking at if we're trying to investigate why something's not meeting the service level objectives we set. The other thing that we are often looking for is what is the ingress into the system and what's creating any high volume ingress into the Logurgator system. So we do that by looking at Metron ingress per Bosch job name. And typically what we see on a normal platform is that the Go Router and the Diego cells are producing most of the traffic into Logurgator. But that is often how we will identify a noisy application is by looking for a particular cell that has changed in the last 24 hours or whenever an incident occurred or a particular service that seems to be sending more into Logurgator than as usual. As a rule of thumb, if there's a service that's exceeding Diego or Go Router, it's probably doing something it shouldn't be because that's pretty uncommon in the deployments that we've had experience with. I mentioned syslog drains. And the syslog drain functionality has been separated out into a separate release. There's a little bit of an asterisk here in that we have not been able to include that packaging in the CF release. There are some challenges with Bosch links and how we have done service discovery. We've moved away from EtsyD in this release. It's not coming to the open source distribution until CF deployment goes GA. But this was a ground up release for us. And so the white box monitoring is a little bit fresher and has a mind towards scaling and indicators that are appropriate for that. You'll see on this monitor, I have a specific number display for the max number of drains over a time period. And the syslog drain release is a really simple scaling mechanism where each syslog adapter can handle 500 drains. So we haven't done it, but it's certainly possible that you could autoscale the syslog drain release off of that indicator. We're not really sure that's a good idea. Autoscaling is a little bit of a slippery slope. But we use a monitor to tell us when that deployment needs more headroom and we need to scale it. So what we found working with Pivotal Web Services is that the way to, from the benefit of hindsight, the way to set a reasonable service level objective is kind of the following steps. First, ensure that you have a monitoring solution that can give you precision down to the level of precision that you need. So you really need to be able to look past the decimal point and say that you're hitting a number of nines for your reliability. And when we started this process, most of our monitoring was based on white box monitoring solutions. And because of distributed math and challenges around that, we might see 98% reliability for a minute period. And then the next minute, we might see 101%. So you can average that out to 99, but that doesn't actually give us the precision we need to start setting service level objectives. So we came up with that block box solution. And hopefully, if you download the CF logmon application, within the first 24 hours, you can achieve that 2 nines reliability for a 24-hour period. From there, it's really about repeating and expanding the time period. So first, we achieved a one week of 99% reliability. And as we spent time on the platform, we started to see 24-hour periods where we were able to add nines to that 24-hour target. As I showed, we have now exceeded our monitor's precision in that we regularly have 24-hour periods where we are perfect and we don't drop any logs. But it may take some scaling and some adjustments to your deployment to actually achieve another nine on that 24-hour period. As you expand your time period to something like a 30-day period, you likely will have a deployment or other updates on your platform that have potential to eat into your error budget. So really, the first 30 days, if you can get that 99%, you're doing well. I think it's taken us quite a while to be able to add nines over a 30-day period. I don't think, actually, we have achieved higher than 99% over a 30-day period. As I mentioned, we have added nines to our one week target. So we're kind of reaching where loggergator team and the Pivotal SRE team is with our service level objectives in that because of moving tooling around in a couple of adjustments to our monitors, we're just at that six-month period. So we're achieving 99% reliability over a six-month period. And our goal is to achieve that over a year and to be able to confidently say that that's a scaling approach that operators can achieve. You may have targets that you're trying to hit that are above 99%. If you're considering that, you really need to consider your deployment considerations. It will limit your ability to regularly update CF. And that may be contrary to the goals you have for your platform. Another important consideration for your reliability targets is the capacity planning and what capacity your deployment can handle for a certain amount of log volume. Over the summer, I conducted a series of experiments to attempt to determine exactly how much load a single Doppler can handle. And through these experiments, which I was able to repeat consistently using some pipelines, we found that a single Doppler can handle just about 30,000 envelopes per second before it starts to exceed that 1% target that I mentioned. Based on that 30,000 per second, we actually recommend 10,000 envelopes per second as the recommended scaling indicator for the number of Dopplers. I know this image will be hard to see, but we ended up building a monitoring tool for us that tracks the max envelopes per second into a Doppler and then uses that 10,000 envelopes per second as a way to understand the capacity of each Doppler. So most of the monitoring tools will allow you to pull that max figure. And it's pretty simple math to use that 10,000 envelopes per second. And one of the reasons we are able to achieve such high reliability on Pivotal Web Services, we have plenty of headroom on Dopplers. We have quite a few Dopplers. And typically, they are not spiking even to 40%. So it's been an action item to actually start scaling down our number of Dopplers since we have been exceeding our targets. I've collected these thoughts and put together a white paper, which is called the LoggerGator operator guide. It's available in the LoggerGator repo. And it's linked on the readme. So if you want more details about this, you'd like to dig into the math. And you'd like to have access to all the tools I just mentioned. This is a great paper to check out. So I'm going to switch gears and spend the rest of the talk to talk a little bit about what we're planning for the future. I've had a number of questions about new ideas for LoggerGator and how we communicate what we're working on. So this is a good forum for me to do that. And I'm going to take the chance to do so. Before I jump into the specifics, strategically, the approach that we've been trying to hold ourselves to is really that agile approach. And we've had a couple of big ideas. I've posted a couple of ideas to CFDev around giving developers access to metrics and a couple of other custom app metric ideas that we think are really exciting. But when we've gotten together with other teams, it's been challenging to figure out where do we start? What experiments can we do to understand how we could take some of the risk out of this larger initiative for us? So I'm going to come back to the slide and talk about a few of the small things that we've been doing recently that have helped us inform what that big vision looks like. So over the summer, I spent quite a bit of time putting together lots of different ideas and feature narratives and trying to prioritize where those were at with the different users and where they were going to land for different releases. What we saw was there were a couple of key themes that were emerging. One is that with improved reliability, nozzle developers were having trouble handling the spikes that were produced by LoggerGator. So previously, we had a UDP protocol. We now had GRPC. And those spikes were making it through the nozzle. And sometimes they're disconnecting from the traffic controller. As I mentioned before, additionally, app developers don't have access to the firehose. And they can't get metrics around dedicated service instances they're creating. So this creates a monitoring gap for app developers on a multi-tenant system. There's also some missing configurations and things that we hear operators would like to do. They want to put more in the firehose. They want to put less in the firehose. So there's some additional tooling and ingress points that we've been looking at. And last but not least, I mentioned noisy neighbors. These are really hard to determine what's happening. We've developed some techniques on figuring it out. But they're pretty nuanced. They're hard to explain. And they're still lacking. We oftentimes have to actually SSH onto the virtual machine, look around at what processes are consuming resources to actually conclusively determine what's going on. We can't do it purely through a monitoring tool. So as I mentioned, I put together a handful of feature proposals. I haven't spammed all of these to the CF dev list, but I've sent out a fair number of them. And I'll show off another slide where we're starting to organize these on the LoggerGator repo itself. So another thing that we found helpful in charting a path forward is to just review briefly where we've been. And part of the transition from UDP to GRPC meant creating a new V2 API. So if you're familiar with Dropson, this is a replacement for Dropson. And it's something that Diego is using to send logs into LoggerGator, as of just a few releases ago in CF release. So this is a new way to emit metrics into LoggerGator and logs, of course. And there's some key features that I wanted to highlight. First off, as I mentioned, it's built on GRPC. So this gives us a more reliable transport. Underneath the covers, GRPC is a TCP-based protocol, so it has acknowledgments in it. It also requires mutual TLS. So it's a little bit more set up for a nozzle developer or a service developer to be able to communicate with, but it does provide secure transport. We also have gotten feedback that there's a need to be able to emit events into the LoggerGator system. If you think about metrics as something that is emitted consistently over an interval, and that's a synchronous process, logs provide an asynchronous way to conduct events, but services don't emit logs into LoggerGator. Only applications do. So events bridge that gap. They allow services to emit a specific asynchronous event into the LoggerGator system. When we were designing the API, I knew that Kubo was a new reality. I didn't have time to change the name in time for this presentation, but we've tried to take out any of the Cloud Foundry opinionated portions of the API and make it more generic for Kubo. We'll take a look at how powerful that can be. And this is now in GA. I mentioned GA ago as using it. For Ingress, any component can now use this using the Go LoggerGator client. So we're trying to also envision an egress that would be more flexible. So kind of familiar with the current egress model. Of course, we have CF logs. So you can create streams that are specific to an origin GUID, and that gives you a really small, reasonable meta log. So that's something like a syslog drain or a log stream. Or you have this other just everything, all you can eat option. We had a feature request come in on our GitHub repo to provide a little bit of filtering there. So we do have a filter that allows you to do logs or metrics. But it's still an overwhelming amount of data. In fact, this is how we see nozzle development currently with the V1 API. So we wanted to think of a way that could really improve this experience. So what we talked about was thinking about selectors. And we chose this word because of its use in CSS. So this is not syntax. But if you are interested, for example, in the event concept that I mentioned, you could write a nozzle that specified, just send me the events. And just subscribe to events for that. Additionally, you might be interested in a specific metric. So you could specify a type. Give me all the gauges. And then within that type, specify a specific metric. So again, this really reduces the burden that a nozzle would have to handle the amount of volume that it can take in. I mentioned that app developers do not yet have access to metrics. But again, this model allows us to specify a scope. And we're working to have all the metrics emitted by components tagged with an Oregon space detail so that those can be mapped to a specific scope for a space developer. And then I mentioned Kubo. If you're spinning up a Kubo cluster, you could specify the scope of that cluster. Again, a way to specify only logs and metrics from that cluster would be sent through that subscription. And the way that it's handled internally by loggerators, those subscriptions are actually passed through to Doppler. And it creates the subscription stream. So this is allowing us to really think about a new simplified world. This is what we see happening over the next year. There may be a scary moment for some nozzle developers here on the slide. But trust me, it's not going to happen too fast. The first step that we see in this process is what I mentioned about V2 ingress. So first thing we want to do is get everyone onto the V2 API and start that ingress from a consistent V2 standpoint. This is the scary moment. And trust me, we're not about to deprecate the firehose anytime soon. But looking at only supporting V2 egress eventually will be the vision of what we have for supporting a simpler loggerator. Recent logs and container metrics is another area that Dopplers currently handle that is a little out of place from a microservices standpoint. So we see that that could go away as well. And in its place, we're bringing in a V2 Doppler that will be a simplified version and only speak V2. Right now, Doppler is sort of operating in a mixed mode where it provides both V1 and V2 streams. You may ask yourself, who is consuming V2 now? The V2 subscriptions are currently handled by the CF Syslog drain release. So that's how we're dogfooding this new API standard. So eventually, that will allow us to simplify Doppler in such a way that it will really be a sort of 2.0 version of the Doppler functionality and only speak V2. So kind of back to our approach, our big vision, one that really encapsulates everything, is the ability to allow developers to consume metrics through a developer segmented fire hose. And some of the steps that we're taking is, first, actually, a suggestion that came in through the community about adding container metrics to Syslog drains. This has allowed us to start working on some of the selector specifications that I mentioned and uses some of the existing tooling so that developers don't have to worry about creating nozzles or a service or any of those challenges that we have with a full fire hose implementation. The next concept that we're working on is an event envelope type. And I mentioned that that's sort of a new concept. But again, it's allowing us to sort of de-risk the overall goal and start working on some of the selector and V2 concepts that we're working to build out. So all of those are really kind of in the theme of this selector subscription model. And that's work that we're in flight on now, and we're just starting to put into an experimental mode. The next thing that we have come up with as a good way to improve the nozzle development experience is to provide a better canonical reference nozzle. Because nozzles have to consume from the fire hose and be multi-threaded, oftentimes the implementation of them is challenging for developers. But providing a reference nozzle that is not tied to a specific metrics platform and simply post-generic bodies is something that we'll see as a powerful tool for nozzle developers to fork and create their own nozzles from. And last but not least, thinking about the developer segment and fire hose as a nozzle as a service has really helped us to think of a better UX for the developer and a cleaner implementation. And this is a feature narrative that I have written and posted to the CF Dev. I think a better implementation than how I originally described it in the developer segment and fire hose. All right, I know that's a lot. And there's probably those that want to learn more about this, read the feature narrative. So one of the things that we've been experimenting with is the GitHub Projects view. So I've taken all of the features that I just described and put them into issues that are pinned to our GitHub's Project View. So this allows us to show what we're working on at a macro level. Of course, if you want to know more specifically what things are in flight, what stories are, we use Pivotal Tracker. And if you have specific questions, we are always available in Slack. So that's it. Love to answer any questions. I'll be hanging out as well if we don't have much time for them. But hope everyone enjoyed it.


Logging trees is a real chore in New World. I won't lie, probably the most bored I've been playing the game.  But the good news is, it doesn't all have to be slow and boring. It can get much easier and faster to level up, and that's what I bring you today, the fastest way to reach a level 200 from a 100. How's it going guys? My name's DPJ and if you enjoyed the video leave a like who really helps out and if you like what you see and want to see more, be sure to subscribe. So yeah, logging trees does indeed suck, and in reality unless you buy or craft better tools and just seek out heavy trees, it's even slower. But even with decent tools and a bunch of heavy trees, with a bonus to resource gatherings within your choice of farm spots, logging trees up to that 100 level is kind of, well, just, shite. But this video isn't about leveling up to that 100 mark. This is leveling from a 100 to a 200, but while we are here the fastest way and the best advice I can give you in getting to a level 100 is obviously seek out heavy trees and use better than those basic tools. Do what you can to either buy better or craft better tools.  Also farm trees within the area you have the best territory standing and resource gathering bonuses. Then farm away and once you reach a level 100, it actually gets much easier because from here guys, it means you now don't have to farm trees anymore. Yes, you heard that right. Because the best, Login XP, doesn't actually come from farming trees, weirdly enough. Now we all know that once you hit that level 100, you can farm those pretty blue trees known as widewood trees I believe that's pronounced, not even sure. These give you around that 550 Login XP mark, which isn't too bad considering. But there's actually a better and much faster way in earning that Login XP once you reach that level 100 and it's to kill and log enemies. So once you've reached that 100 level mark, you want to go here within the south east area of Brightwood. There's a fast travel point here called the Alchemist Shrine.  And you will be met by a level 32-ish enemies, but they are pretty easy to kill. The enemies within here are a specific type you are looking for. They are called the Bronze Grove Terror Wolves. These wolf-like creatures are seriously easy to take out. But the crazy part is, once you do take them out, you can farm and lug them for that Login XP, which gives you close to 830 per Terror Wolf. So over 300 more than those pretty green trees. And while they spawn in their drawers over here too, over and over constantly. So do this guys and I hope it helps you out. They can also drop some decent loot too. Now I do believe there are higher level Terror Wolves on the map somewhere. But this is for the average player like me who isn't already close to that max level and ain't had time to smash out the basket. So yes, I hope this helps you people out in earning that Login XP and reaching that level of what you want. I'm not sure what it goes up to, but I know it's crazy slow if you don't use methods like this. So yes guys, I hope you enjoyed the video. If you do leave a like, really helps out. If you're new around here and want to see more new world, be sure to subscribe. And if you never want to miss a video I upload, you can turn notifications on by hitting that bell button. But guys, thanks as always for stopping by and hopefully I will see you on that next one.


All right. Well, welcome everybody. Welcome to Brain Club. Nice to see so many returning folks and new folks today. I'm Mel Hauser. I use she, they pronouns on the executive director here at All Brains Belong. So they will be having a book chat about the book together by Dr. Vivek Murthy. Brain Club, of course, is our weekly community education space where we provide education about neurodiversity and related topics of inclusion. It's a way that we bring people together based on a shared vision of what's possible as we define and reimagine health and community for people with all types of brains. In so doing, to contribute to systems change by shifting social norms. This is a place where people can collectively learn and unlearn together and promote new ways of thinking and being in order to collectively change the world. And although All Brains Belong has a lot of different types of programs, this one is not for medical or mental health advice. It's not a support group. It's not a place to discuss or solve individual specific problems or process individual trauma. This is an education space tonight. That being said, all forms of participation are okay here. You can have your video on or off. And even if it's on, we don't expect anything of you. We certainly do not need you to sit still or look at the camera or, you know, any of those neuronormative constructs. So please feel free to walk, move, fidget, stim, snack, take breaks, whatever needs doing. And you're welcome to communicate in any way you are most comfortable. You can unmute and use mouth words you can type in the chat. Sarah, would you be able to take over letting folks in from the waiting room? Yes, I've been doing it. Yep. Okay, great. Awesome. So, in addition to affirming all aspects of identity, we feel that safety comes first for everyone. And so sometimes the topics that we talk about sometimes they connect to, you know, really, really distressing memories really distressing experiences. We just ask that you discuss the impact of those experiences, not the events themselves. And this is going to be a lots of lots of space and time for discussion today and so just balancing individual needs and the collective needs of the group. Close captioning is enabled. You just have to toggle it on if you'd like to use it. And depending on your version of zoom, you might see the live transcript close captioning icon but if not look for the more dot dot dot and choose show subtitles and you can do the same and choose hide subtitles if you want to turn them off. And that's my visual support to open the chat box so I'll actually see it if anybody's using it. All right, cool. And just to preview before we get into tonight. Thanks Lizzie Lizzie made a slide to preview. Next month's brain club our theme is systems change from the ground up. And we have a variety of community panels I think it's going to be a really really good series of brain clubs. We'll be discussing the book together by Dr. Vivek Murthy who was the surgeon general of the United States from 2014 to 2017. And the themes of this book are around the importance of human connection and the hidden impact of loneliness on health. Usually a book chat there's a mixture of books you read the book or not read the book and everyone's welcome, everything in between. But the idea being that, you know, after understanding the hidden impact of loneliness the book also then gets into the social power of community and different ways of building community. First, I'd love to introduce our guest facilitator tonight. Suzanne Richmond is an educator former faculty at Goddard College, and a spiritual care provider. She's also the founder of the hummingbird center which is a retreat center in central Vermont, built to help people come together and cultivate a sacred and a full path forward. So thank you Suzanne for for being with us today. I'm happy to be with you. Suzanne, I wonder, because before I like I before I get into like some some slides and quotes I put together. You're the person who brought this book to my attention. What led to you doing that? Wonderful question. You brought the possibility of a healing community to my attention. First, you did that under a tree at the state house you and Sarah and many members of all brains belong. And I was lucky enough to show up one summer sultry summer night and notice what kind of deep interconnected my cereal webs you and all brains belong and everyone who's part of all brains belong had woven together. When I stepped under that tree with you all, the healing power of community was already intact. You had a task before you though that was not as much exploration with patients, but exploration with funders to support all brains belong.  The way we do medicine and healing with all brains belong so that we can generate the funds we need to create a well supported enterprise. And so I kind of thought, I bet you there's some great research on that and indeed there is a lot of research about the way we connect with each other. Fully influences the way our body senses the environment which fully impacts our immune system and all the wonderful things Sarah taught about last week. We need each other to be healthy, but you needed data, you needed data driven materials. So I went to the book and I combed through it with a fine tooth comb and I was thinking about all brains belong. And I underlined a bunch of sections in there which spoke to me as the medical scientific evidence for what you're already doing to build community healing and health. That's what led me to read the book to underline the lines in the book to give you the book. And here we are. And maybe that helped you talk the medical scientific talk to your funders. I don't know, but here we are the book was worth the read anyway. Look is amazing. Thank you. Thank you for all all of this. And because of my own executive functioning. I read the, I think it took me like a year to read read the book. I'm so glad that I did and I'm going to share share some passages that stood out. Nice. All right, here we go. So, as, as Suzanne said, we know that loneliness and social isolation are bad for health. Dr. Murphy distinguishes between isolation and loneliness where loneliness. It can't be is distinct so you can be isolated but not necessarily lonely loneliness. He defines as the subjective emotional state of being alone resulting in internal discomfort. And we know that so many people feel alone in so many different settings. And despite this. Dr. Murphy writes social connection stands out as a largely unrecognized and underappreciated force for addressing many of the critical problems we're dealing with, both as individuals and as a society. He discusses driving factors for loneliness being shame and fear shame and fear conspire to turn loneliness into a self perpetuating condition, triggering self doubt, which in turn lower self esteem and discourages us from reaching out for help. Over time, this vicious cycle may convince us that we don't matter to anyone and that we're unworthy of love that should say, driving us ever inward and away from the very relationships we need most. Further, he says that the combination of loneliness and stigma create a cascade of consequences that affect not only personal health, but also the health of society. I wonder how that's landing on on folks. I could say that people in the United States, no matter what type of brain and neuro identities we have and functions we have is said that people in our country are the loneliest people of all countries. So, all of us to some degree are impacted by that social field. All of us feel some isolation, some shame, some fear. All of us feel the awkwardness around connectivity. And this, this slide is, is not pointing to the finger at one. But I think as a culture and as a society, we're all in this bath of sorts. We're less at different times in our lives. Sarah says in the chat I think it's difficult in this culture of rugged individualism to reach out for help when you need it. Right I mean we talk about it brain club, often about unlearning the myth of independence and normalizing interdependence and the book talks quite a bit about interdependence the idea of being connected to and relying on other people. That is what we need. Dr. Murphy further describes the paradox of loneliness, when we become chronically lonely. Most of us are inclined to withdraw. And there's research that shows that loneliness changes threat perception this reminds me very much of what Sarah presented a few weeks ago. We push people away and see risk and threat in social opportunities. And the hyper vigilance that comes also creates intense preoccupation with our own needs and security, which can appear to others as self involvement. And there's a quote for researcher Steve Cole, human beings are great assets to other human beings, but they can also be great threats. Dan, I think you had some questions you wanted to pose. I love this, this sad, sad image. I've been that person. I've been that one holding my knees to my chest. And my imagination creates another image next to it. If I were able to draw on the screen, and it would be of this same woman sitting on a park bench on one side of the park bench opened and leaning back. And she would put her arm out and wait for someone to come by so she could listen to them. Because on one hand, we close ourselves up like this figure in the image. And on the other hand, sometimes we can open ourselves wide to let others in. And so I want to explore that the movement between when we feel shut down, closed down, unconnected and not belonging. And when we can begin to create spaces of membership and belonging rather than othering. So, one of the questions I have for all of us. For the moment, my, my visual prompts are not so high tech, let's see if that shows. I don't know if you can see it, let's see. There we go. My question, one of my questions of the many that I carry in my life is, how do we build a social architecture of belonging? Knowing that there is a pandemic of loneliness. And another way to say that statement is how do we build connectivity and conviviality, rather than alienation and competition. And one of the things I wanted to offer is a quick glimpse of how another culture builds connectivity other than this one we're part of. And then I want to move into deep dialogue with all of you. So, I think I was in my 30s when I was invited to go on a health project in West, in East Africa. And we were living in the territory of the Maasai, which is Southern Kenya and Northern Tanzania. And I was staying with a man who would fly Cessnas into the remote Maasai villages to bring healthcare and bring immunizations and help stitch up kids if they got snagged by a lion or a thorn bush. He was an amazing man and a deep healer. And he told the story, and I'm getting really distracted seeing my face there, but I will look at you all. Thank you, darling. He told the story of when the village comes together to gather to have community meetings. The men, the women, the children, they all come from multiple directions of the compound. And they all bring with them a blade of grass or a reed. And an elder is sitting in the middle of the compound under the tree with a cow horn. And everybody one at a time puts the blade of grass in the cow horn. And if somebody does not put the blade of grass in the cow horn or the reed, that means that person is hurting. That person needs to be seen, heard and recognized and held by the community. And so all attention is given to the one who is the most alienated or the most unpeaceful or maybe feeling the most vulnerable. And Pat, who was my friend who I was visiting who flies the Cessnas into these villages to do the medical care. He said it was quite amazing that everybody in the village would check in with the person who withheld their reed or their grass. And I ask myself, when do we do that in our culture? How do we come together so that we can all put our grass or our reed in the cow horn and know that we're all ready to be together? How do we dissolve the alienation and the hurt? How do we dissolve the other ring? So I wanted to ask if anybody else wanted to tell a story of when you saw others being welcomed in or when you especially yourself felt welcomed in. And it can be any kind of story. You can put a few sentences on the chat or maybe one of you feels like saying something about a special time when you didn't feel lonely or you didn't feel alienated. You can take a few more deep breaths with this question because it might be bringing up the sense that it's rare in your life. Or like myself, I don't talk a lot in public but I am very curious if anyone has even a smidge of a story when you noticed somebody creating an environment where it felt like there was more belonging than less. Either for you or for somebody else. Yeah. So thank you. This is really amazing. I was just at a workshop and I am often uncomfortable in social situations and it was one of these places where there were lots of tables and everybody had lunch together. And there was one day where I just didn't have the courage to go up to a table and say, can I join you? So I sat alone hoping someone would join me and nobody did. And, you know, maybe I was putting out a vibe that I wanted, I don't know, but it was really hard. And so the next meal I just walked up to a table and of course no one ever says no, right? But it was this hurdle of getting through it. And then the next day someone came up and said, can I join you? I was this back and forth and I was watching it the whole time and it was really like this pain and joy and pain and joy, but a very great learning experience of just, you know, most people are compassionate and don't want you to feel alone. And that's kind of what came out of it. So anyway, the PS is that one of the roomies that I had was sort of staying in her room and I invited her to come on a walk with us. And it kind of changed her experience because I think she was also feeling the same thing. So thank you for bringing this up. It's really gorgeous. What a really gorgeous to use your word story. It's quite visual. I could I could be there with you as you told it. And like the social architecture of places where we eat can be really difficult at times. I walk into the wayside, for example, and I see a lot of single people sitting by themselves eating their whatever they've ordered, you know, and fish and chips. And there's a part of me that just wants to sit down next to them and create conversation. I also don't want to invade their space. So it's not simple to navigate what you just described you navigated. And it sounds like you were experimenting a great deal in that process of, hmm, what will happen if I sit here?  And then, hmm, what will happen if I reach out to my roomie to say, would you like to? You know, again, experimenting and what I'm hearing is a lot of self awareness and a lot of dignity and a lot of sensitivity and empathy and grace that you practiced because you're listening to yourself and listening to the others around you. And you're you're working with shaping a space and there's a lot of improv that goes with shaping a space like that and experimental process. And now that you've described that, how in your life might you continue to experiment with that kind of social architecture of building connectivity, connection, relationship? Do you see yourself having more courage or curiosity? Okay, there. I think I'm just going to, I live, you know, I'm pretty solitary anyway, but when I go out in the world, I think my attunement will be heightened to what other peoples are experiencing. And, you know, particularly just really looking at inclusiveness more these days and understanding how painful it can be to not be included, you know, for some people. So, yeah. And I really want to also read Sierra's comment in the chat that I think connects to what Gail just said that support and belonging looks so different for different people. And I think there's a lot of assuming on how others, especially marginalized groups want to be included, instead of finding out what does belonging really feel like for each individual person. Thank you, Sierra. That's really important. And I think what we try to do here and in Brain Club is like this, this social experiment in a way. It's the idea of the social architecture Brain Club, I think, is the idea of creating multiple ways of participating with the idea that, you know, if, if observation is a completely valid form of participation.  Yeah, I, I just wanted to elaborate on that I think you know I, I grew up in a family that really love throwing lots of parties and my way I like to interact at parties now that I'm, you know, old enough and realize this is to sit and watch and listen and be quiet and kind of passive and that was always really thought of as oh you're not having fun you're not enjoying yourself.  And it made me assume that I didn't like parties and I didn't like hanging out with people and that's not the case it's just I never, you know what when you don't have that. When you don't have the experience of what does belonging look like in a way that feels good for me it's really hard to imagine that when all you've experienced is, you know, the scary cafeteria lunchroom in middle school or whatever that looks like. So true. So true. And it is so much about like who is the architect. And in what is the, you know, the dominant culture the dominant neuro brain culture, forgive me I don't have all the wonderful language you all have at the ready for myself. But each of us have the power to be part of the design team of those spaces, including as I was so grateful to hear a few weeks ago with Sarah Sarah's presentation. For some of us going out into those spaces is especially difficult. Those of us who were much more introverted. Those of us who get along just fine with companionship with ourselves. It is very much what kind of structural spaces do we want to create to sense belonging with ourselves and with each other, because belonging is also an inside job. As we were, as Mel was mentioning earlier, the subjectivity of one can be alone and not be so lonely, one can be alone and be very lonely. But when you're designing the kind of space you need, what does that look like? What are the, maybe another person wants to say something about a unique environment that did fit you, or that you helped shape to fit yourself, or that you might have even helped shape to welcome another into it. Is there anybody else who has an experience they want to share?  I always do the thing where I mute myself and speak in the wrong order, so Monique, go for it. I saw your lips. And I wasn't watching a busy meeting. Hi, this is Monique here. Oh, I'm muted. I'm muted, right? Oh, you're good. No, you were great. Beautiful, I hear you. Okay. Well, I just, this February marked six years of me being housebound, so I do not spend time with people. It's very fleeting when I do spend time in person with people. And that's okay. I'm 85% of the time because I am by nature a solitary person. And I enjoy solitude and I enjoy silence. But sometimes it gets a bit hairy. So about maybe two years ago, I started just reaching out to people in my life and saying, Hey, can we just, can we spend an hour, sometimes we spend three hours, can we spend an hour, I need to do something. And I just, I don't want to do it alone. Can we just spend an hour in Zoom? And our cameras don't even, we do leave our cameras on, but I'm like, I give the option. We don't even need to have our cameras on. We'll be muted, listen to your own music or be silent or whatever and let's just do our own things. But let's know that somewhere someone's hanging out with me and I'm hanging out with you. And so I have a group of people that I can do that with, I can. And then we now actually gather on Sunday afternoons and spend time together online, just doing our own thing. Whatever that is, sometimes people take a nap.  So that's how I, that's one of the ways that I cultivate community. And this brain club here is a place where I have felt welcome, like from the moment I landed in this space, I have felt welcome and understood, which is just such a unique experience to be understood. Yeah. Thank you. I could cry. I was wondering how long it would take until somebody could, until somebody mentioned all brains belong as as a space where they felt so welcomed, you know, a very healthy, open, welcoming environment. And I love your language around cultivating community, the use of that phrase cultivating community. And you're doing that together. And that's the name of the book. And you created and cultivated community when you asked a friend to hang out with you using the technology of co zooming while you were doing your own thing. And that's very insightful request. And now look at what, what's that, what that can turn into the Sunday gathering space. And there's a neuroscientist whose name escapes me for the moment Dan Siegel, that's who he is. And he talks about the social field. And the social field is so much bigger than being in the same embodied room together. And the social field is current and present and vibrating when you intend it, when you bring it upon yourselves with your friends when you co zoom and hang out and do your own thing. Like, I fully believe we're creating that social field, whether we're in the same room or not, or whether we're just in the same alignment as you talked about. So there's other deep research around guarding each other's solitude. And I feel honored to witness your solitude in your home. And I feel like you're my guardian and I'm your guardian anytime you're alone and I might think of you or anytime I'm alone and you might think of me. And we're guarding each other's solitude as well. And that's a place of being with each other without needing to be in a complex social web that might be overwhelming to our sensory systems. So, cool. I'm glad that all brains belong feels like immediately a welcoming place where you felt understood course it does. I'd like to connect this discussion to the research on what's known about why this matters. So, Dr Helen Stokes Lamper wrote social isolation and loneliness are akin to a chronic long term condition in terms of the impact they have on patients health and well being. And yet of course, this is often ignored and perpetuated by the healthcare system. Often at least the folks a lot of the folks that we know have had the experience of feeling invalidated dismissed like the opposite of feeling understood by their healthcare through their health care experiences and the impact the impact of that can be can be so profound. And that's why you know it all brains belong. We say that healthcare is more than medical care. People come here because they're looking for social connection. Many of the people, if not most of the people feel like I don't have it I don't know how to have it I, I'm not the kind of person who can go to a group and like be comfortable there. But it turns out when, and I think Suzanne to your point about like the architecture the intentional design of a space, even a virtual space, like that's really what, what we have been, I think, co creating and so many of you that they've been part of this journey all throughout you know and so invaluable to that co creation process, because it's like what what would it look like if we know that we all have different brains and different brains of different needs. What would it look like to design social connection that really could work for everybody. In a way that acknowledges that everyone has different access needs and that conflicting access needs are inevitable, because we know we know the power of that connection. And I think as it relates to brain club I think what we hear often is that when, when, when folks hear their own experiences reflected back to them like through the stories of other people that experience of feeling understood less alone. But that is social connection. It just doesn't look the same for everyone. I wonder if anybody has thoughts, thoughts about that like the idea of even like asynchronous social connection, you know, through storytelling or even like, if I read a book and someone described something I'm like oh me too. There's there's something that can be can be really powerful about that but but coming together and you know hearing hearing from other people who are saying things at brain club or you know, other places that that resonate with you what's what's the impact on on belonging. There's comments in the chat around connecting about, you know areas of passion special interests monotropic foci. You know, really when you bring people together based on shared interests and normalize that there's multiple ways of interacting about those interests. That's really important. The richness of all brains belong as an as an innovation towards learning about what belonging looks like for brains neurodiverse brains neurodiverse people diverse people. I love that question. And I, I feel like you're so open to feedback from everybody just asking the question you just asked Mel. Is I can't see the chat maybe there's a whole waterfall or cascade of people responding or not but there it is. I'm also curious I hold that same question like, how do we stretch. How would, how could all brains belong stretch to create even greater belonging, because we're the experiment is opening and it's not done. I think one thing I talked about a lot and Suzanne what you were saying about you know finding, finding belonging and community that meets your like sensory needs and that type of stuff. How, what it looks like to try to find belonging and community when you're in burnout and when you're starting from a place of, you know, if I'm starting from a place of I have a deficit in my dopamine or energy or spoons or whatever we're using if I'm starting at a place where I'm at a deficit of that. How to create belonging and community when everything feels like it takes energy to put in to really get energy out. I think that is like, you know the idea of like with chronic pain a lot tends to talk about you know exercise is going to be helpful for pain but you can't exercise if you're in pain you need to, you know it's, it's really hard to do one without doing the other. That's not a, not an answer but there's more questions. Beautiful. Just naming that is really important right because I think, you know, there's so many people in that situation but think about like Sierra we, we are having those conversations all day long.  That's just part of the equation, and that you know fluctuating capacity for anything and tolerance of stimuli and stimuli that you like. It can be difficult. Monique. I'm going back to know what you open with about being alone together. And that is kind of my that is like the sweetest of sweetness for me. When I can be with somebody and we're quiet and we're parallel play body doubling. Those are my golden moments in life and the word belonging together community. It could be my own bias but I feel like they are inherently extroverted and exuberant and exclamation mark and annoying. So, I just want to my own perspective of community belonging together is quiet is still soft subtle. I don't think that that's valued in our society. I'm thinking of that book quiet right now that book is coming to mind and how quiet people are not valued in our society. That aspect of a personality, everybody gets quiet aspects, of course, but that aspect of the personality is not honored or practiced very often. Yeah, just making a point. Yeah. Check.  Reading in the chat. Paul says it wasn't until brain club that I learned about access needs and began understanding my own. I guess I realized now I'm seeking more parallel play and relationships. It seems like a lot of work to retrofit this new aspect of me into established relationships. This place however is awesome. It resonates with me a lot, Paul, and you know some it depends on the relationship sometimes relationships can be retrofit and sometimes they can't. But you can't go backwards you can't unlearn what you discover about yourself it's your access feeds. And they're valid every single one of them. The critique of the book is really important. You know I think this was like a neurotypical surgeon general. And so you're raising really important points. And I think he would appreciate a letter. I mean there's just ways to stretch the research canon that's out there so it's not going to feel like an insult to feel like you're left out your experiences omitted. It doesn't matter to the author and it's really important all these comments that are just coming up right now. And ways we gather ourselves are every bit as important as ways we gather together, the ways we find in center and show up in our own self, where we do feel like we're recharged. And Sarah your question is kind of stunning I'm going to be sitting with that for a long time that when we you know when we run out how do we recharge if we're burnt out and how do we create what feels nourishing. And it's not always for sure I think in the all brains belong population and I'm I consider myself among y'all you know. I need enormous amounts of time to gather myself every day I live up in the hills and I hardly ever come down. So it is it's a really important question. And in my life one of the things I've learned and this is just my brain in terms of that question is one of my superpowers that I'm still honing is listening. And I like to listen to other people to learn. And I learn a lot about myself that way. And that somehow doesn't take a lot of energy, but I've noticed when I listen to other people who feel really burnt out. And they have an opportunity to explore inside of themselves what's going on and speak to the the hurt or the pain or the discomfort or the sense of feeling dishonored or not seen. They become more and more present as they name what's hurting. And so I've worked with a lot of health care like I've worked with a lot of nurses, for example, who are just at the point of just crying. And to sit and listen to what what ails them where the grief is how the grief feels in their body and then to join them so they don't feel so alone in those feelings. My experience is that the health care workers who have self identified as burnt out really benefit by being given the space to express their inside feelings. Because the institutions don't give the space for that. Why did you walk away from dominant health care centers? What was missing there? Why did you create all brains belong? What are you learning through creating what you needed to be able to thrive more and less and burn out a little less? That's a great question. I mean, I think what we when we started when we started all brains belong. We didn't really actually imagine this community village of learning and healing together. That was not part of the original construct. It evolved because the community co created itself. The original construct was like, let's have a health care practice where yeah, yeah, I mean, definitely there was going to be a community programs and people were going to come and make friends because that was really important. But along the way, it was our community that said, you know, no, we need a forum that we can, you know, develop shared language and come to understand our experiences better.  But you know, then our community says you got to do something about employment. You know, work is crushing me.  And even the way we do medical care now is very different than, you know, two and a half years ago, in terms of now we do a lot of group based medical care. And what we have found is that, you know, our community members who participate in group medical visits, they understand their health better they understand their access needs better they feel better they make more progress. And that that was truly a co created model for health care delivery. And, and so Sears charming and I think that's one of the reasons that mutual aid is accessible models that it's an intent inherently community co created. Yeah. I apologize to you Sierra, my brain turned to Sarah when I was speaking of you Sierra and some of what you had said, forgive me. I respond to that funny I was scrolling in the chat being like what's Sarah asked a question. I didn't see the question. What I was going to say is that one of the things I hear a lot. And I think I saw it in the chat earlier, it's the idea that when you grow up being taught that there's one right way to think to learn to communicate to play to socialize when you're taught that explicitly or implicitly. When you're being an adult and you're still asking questions like what is the one correct way to make friends, because you were taught that there was a correct way to make friends. And I'm nice I see it with my seven year old I see like I've like seen other adults give, give, you know, neuro normative advice or I'm like, go ask them to play. Oh my god, don't do that. Anyway, so I think it the idea of when you have not had either a lot of or any positive social connection experiences, you show up. And it's kind of like what Gail described like going to the conference room lunch table and you're like, I just don't want to do this I'm gonna stay over here I'm gonna do my thing over here. And then you're like I really recognize and there's this gap between like I wish I didn't feel this way about being here at this table or so so but but but it's it's it's the idea that like I think people don't know that there's so many people for whom that's true. I don't know why I don't like what I don't know how to make a friend I know I'm lonely I know I'm isolated but like what do I do. I think it's about like showing up just showing up, taking a chance and showing up. And when you have that experience of showing up and if it goes well, then you have something to compare to and then you know that I think I think a lot of people you know you can say it's the environment it's not you it's the environment So until someone has the experience of having a positive social interaction.  I guess you're right I guess different types of social groups feel different. It's not just me. It depends on the group. What Sarah said the more we can share our vulnerabilities the more we can break down the shame and realize that we're most definitely not alone. Yeah, but it takes trust to get there right and if you've been burned. It doesn't feel safe to take that leap is I think when people are burned. They internalize the story often that it's their fault. Sarah, I saw you just turn your camera on do you want to chime in. Oh, I just love in the conversation. I mean, one of the two most, I think the two most fun things that and probably the proudest things in my life are are like 10 or so years ago. I got to be the director of a community wellness and recovery center for mental health stuff and mental health peer support and. I mean, it was so fun to like, think of all the ways that like, like I was lonely on Friday night. I never had a date I never had anywhere to go on holidays I never had. And so, in some ways it really became about me and that was a problem but but it was but it was so fun to think of all the ways that I felt excluded and marginalized, and then start to try to and start to, and, and then, and then in a lot of ways, but it also wasn't just about because, because we had, we just saw these incredible holiday parties because, and we were made a point of being open on holidays because, and it was just and we had a budget to do it so it was just like a blast to like, you know, be open on Christmas and and all the days that all the providers were closed, and have these magnificent Thanksgiving, you know, and just get the whole and just get like everybody he was in half of our community was homeless and half of our community was, you know, in the in, it was like sort of in the mental health system, and, you know, public housing stuff and, and, and so it was just it was fun to sort of like, have a little have some resources and then, and then think of all the things that the culture wasn't providing for our people and then be able to start to start to try to provide them and so and then 10 years later, when I'm like have no power and I'm marginalized because I've melted down, then trying to think of like, I have no energy and that was before zoom was popular, but we, but the only thing I could think of was I loved creating having this peer support thing, but I don't have any energy I don't have any resources. So, but it turned out that you could do like this, there was these conference call stuff was even before zoom so but you could have these conference calls. And so it was like, Okay, I think I can put something on Facebook and say, I don't have anything to do on Friday night. And I'm crazy. Anybody else feel crazy and wanted to do something on Friday night I mean it was just those kinds of things.  And this is what I finding. And because it was about like what I had to find what I could do for me, which meant that I would find other people to whom that also those things also appealed to because and you know there are other people who are who who couldn't take advantage of what we were offering for a zillion reasons. And what was offered. It was just that there were some people who were enough like me that calling in on a conference call on a Friday night was a hell of a lot because I was sitting around doing nothing. And then, you know, and we developed from there. So that anyway, that was sort of, but it really started with what, what I could do. And the hope that if I tried to do something and put out a call that there would be other people like me who would do something who would, who would respond and I got lucky. And that was incredibly validated. Wow. Yeah, yeah, I loved it. You know, the, the idea that you're creating what was missing in your life. And you're creating it in, you did it professionally for a long time and now you're doing it personally and interpersonally. It's Friday night. I'm feeling vulnerable or isolated. I don't need to be there are other people I can create community with and we can lift each other up in whatever way community looks like to you. Without it being one of those alienated, you know, overused words. Like there's no force field around what is community except what you create your your create your you create a lot in your life through its absence, you create what you need through its absence. And I think that's like so important. Like, because some of the times I some things I learned were because in my life I've learned because of what people what people gave me that was there. But some of the most important things have been about going into my own heart and soul and like what wasn't there and what did I need to fix it and how, how do, how do I begin to create that how do I begin to offer that so that it's, it exists in my world, but it needs to and maybe other people need me to need it to exist too. So how do how how how do how do I begin to make that of see if we can make that make that possible and if it's like what's happening here all brains belong I mean that's the whole premise that's what's so exciting about this place. Resonance, you got it. So exciting. Thank you all for letting me hang out with you guys tonight. This was amazing. I really am grateful to everyone for being here for participating in your own way and for being part of our community. I'll give you a preview of next week. I think that I haven't made the video yet, but it's a community panel of health care providers from the traditional system, who have been introduced to all the things. They're sharing about their experiences and discussing their views on what's wrong with health care and how patients can get what they need. So I've done, I've done most of the interviews so far and they're, they're pretty rich. So I look forward to sharing this with you next week. All right, see ya. Bye.


Good morning. Pegasus is classified as a weapon. Pegasus is classified by the Israeli state as a weapon and that weapon is supposed to be used against terrorists. The prime minister and the home minister have used this weapon against the Indian state and against our institutions. They have used it politically. They have used it in Karnataka. They have used it to scuttle probes. They have used it against the Supreme Court. They have used it against all the institutions of this country. The only word for this is treason. There is no other word for this. Right? And this has to be investigated and the home minister has to resign. Look, these Pegasus people call this software, snooping software. This is a weapon. The Israeli state is classified as a weapon and this weapon is used against terrorists and criminals. Our prime minister and the home minister have used this weapon against the institutions of India and against the people of India. They have tapped my phone. Look, this is not a matter of my privacy. This is not a matter of Rahul Gandhi's privacy. I am a politician. I raise the voice of the people. This is a attack on him. This is a attack on the voice of the people. Pegasus has been used against the Supreme Court. The investigation of Rafael has been used against Pegasus to stop him. So Narendra Modi has used this weapon against our country. And there is only one word for this. Treason. The home minister has to resign and the judicial inquiry, the Supreme Court inquiry should be on Narendra Modi because no one else can authorize this Pegasus. This Pegasus's authorization, the Prime Minister and the Home Minister can do it. Can we take one by one, ma'am? The list which has come out today on the Pegasus state includes a business man, a leading businessman whose name was there in the object list. The inquiry is going on in France but here the government is numb. How do you take this? Look, I have said very clearly that there has been gross theft in Rafael.  This is a truth.  But the truth has a way of coming out. Right? There is an inquiry in France and you will see the Prime Minister himself is responsible for corruption in Rafael. You'll see it. Right? You can't buy everybody. You might think you can buy everybody. The Prime Minister might think he can suppress everybody. He might buy everybody with funds. And the reason all those people, you're seeing even your question, you're asking a very interesting question, you're asking it in a very particular way. Why are you not asking why the CBI director's phone was not tapped? Why are you asking me about Anil Ambani? No, no, no, no, you can't ask me because no, no, no, because this is a mischievous question. The real question is why on the last minute, when the CBI director was about to file an FIR, why was his phone trapped and why was he blackmailed? That's the real question. Who did it? That's the question. The question is not whether Anil Ambani's phone was tapped. See, even in your questions, it's all related. No, no, but you have to ask the correct question. You have to ask the precise question. So the answer is the entire Indian state is under attack. The amazing thing is you don't know. You don't seem to understand that you are being attacked. Maybe because you're paid, maybe because you have to live with these cameras, maybe. But this is not an attack on Rahul Gandhi. This is not an attack on individuals. This is an attack on the Indian state. Okay, so tell me one thing. If, if, if there is nothing to be taken, if the Indian government has not done this, then someone else must have done it. The Japanese government must have done it. Israel's government must have done it. Russia's government must have done it. Uganda's government must have done it. Because Pegasus can only send it to the government. So then it should be an inquiry. No? So why isn't the Prime Minister saying, yes, people's numbers are tapped in Pegasus. We'll get an inquiry. Why isn't the Prime Minister saying that we didn't do it? Sir, I have a question. No, and this and this is also a question. That is, did they buy it or not? Answer it. The government is saying it. Yes or no, the answer is not given. It is also classified that we have used it or not. And Amnesty has said that we have used it. Look, it was a matter of Rafael. It was a matter of the farmers. No, no, it is not a potential target. My phone is tapped. It is clearly tapped. Right. So it's not a potential target. Do you feel scared when you use your phone? No, look, it is clearly tapped. I don't care. Sir, on what? Look, it is a simple thing. You want to understand Indian politics.  If you are not a thief, if you are not a thief, you will not be scared at all. It is a simple thing. On what basis are you directly? Are you allowed to buy Pegasus? Can I buy Pegasus? Pegasus has to be authorized by the nation state. The file has to be signed at a minimum by the home minister, probably by the prime minister. Pegasus cannot be sold to the military of a country. It is sold to the government of a country. Please read the contract. It is sold from government to government. Much like Mr. Modi says the Rafale deal was a government to government deal. But then Mr. Anil Ambani is sitting in the meeting. Our stand is clear on that. These are the laws that have to be taken back. But the government is saying that it is ready for the debate. There is no discussion for the debate. There is no discussion for the debate. Sir, you said that your phone is tapped. Your phone is tapped. It is not only this phone. Every single phone of mine is tapped. And let me tell you another thing. I get a phone call from IB people who tap my phone. They call me up and say, please be aware that I am tapping your phone. I have no, also by the way, my security people tell me that they have to debrief what I say. They have to report to their seniors everything I say. So I am under no pretentions that I am not tapped. Sir, tell me one big thing. This has happened to me 3-4 times. My friends are called up. They are told to tell Rahul Gandhi that our phone is tapped. Sir, the government is saying that Rahul Gandhi is going to tell us something. Is there any intimidation? I don't get intimidated. Sir, have you said anything about the Supreme Court? Supreme Court? See, I don't get intimidated. I am... These things don't intimidate me. Sir, the government... Thank you very much.