Welcome to the Outreachy Kernel Internship Report. I am Alison Schofield, the current Linux Kernel Community Coordinator, and I will be introducing you to our most recent cohort, Beatriz, Deborah, Metali, Samera, and Janzea, who've all recently completed Outreachy Internships. Outreachy, this goal is to increase diversity in open source. Anyone who's facing under-representation, systemic bias, discrimination in the industry is invited to apply. These interns get to work with experienced mentors in many free and open-source software communities. I believe at last I peaked over 100 different FOSS communities have participated in Outreachy. These internships are paid. The interns receive a $6,000 stipend. These internships are remote. Both the interns and mentors work remotely. They've always been remote, just like for the Linux Kernel World. Much of our work is done with people across the globe that we only see on mailing lists and now in a lot of Zoom meetings. These internships last for three months and do require a full-time commitment. They're offered twice per year, May to August, December to March. For FOSS communities, like the Linux Kernel Community, coordinators sign up their communities in each round. Mentors submit projects under our community and community coordinators approve the projects. That's the state we're in today. As I record this video, we are seeking out mentors for Linux Kernel projects. For the interns, they fill out an initial application where they check to make sure that they meet the eligibility criteria. Then they go ahead and make contributions to FOSS communities according to that community's guidelines and they submit a final application to a community and project. Here's a little more on the timeline. This is the round that we're in right now. The initial application deadline has passed. The project list is not yet finalized. Once that is finalized, the contribution period will begin. Aside from the internship itself, it's like the most busiest and the most exciting time of the whole process. After that contribution period, interns submit a final application to the project they want. Interns are announced and their internship period begins. This timeline repeats. So we do this whole thing twice a year. So that kernel contribution period, for 30 days, the applicants, the mentors, and all group of additional patch reviewers are in close collaboration, supporting these interns and helping them through the application process. They join a special mailing list. They complete a first patch tutorial and they submit their first patch to the Linux kernel. This is a thing to be celebrated. If you go no further, they get in your first submit accepted. Did I say submitted? Accepted in the Linux kernel. That's something to celebrate. You will see the interns all in their blogs and their social media celebrating the day they got their first patch accepted. Once they get past that, they start working with mentors to do some small project-specific tasks to see if they can find a project that would be suitable for them. Finally, they'll record their contributions and submit a final application. So the Linux kernel has a long history in outreach. We've been in it since 2013. More than 55 interns and mentors have been in this program. There have been six community coordinators so far. I'm number sixth. I'd like to mention the prior five, Sage Sharp, who started this whole thing, Julia LeWall, who continues to be super active on the mailing list and a mentor in the program, Vashali Thacker, Shadra Bark, Helen Coyke. Vashali and Helen were just doing it this past round and have decided to pass the torch on to me. Now Vashali, Shadra, Helen and I are in a special club. We are also outreach alumni. All of us were originally outreach interns and some of us then were outreach mentors and then outreach coordinators. So as you can see, once you get hooked in this program, you keep participating. And it's not just us organizers. There's a whole additional group of volunteers that make outreach happen. Former mentors, other Linux kernel maintainers and developers all pitch in during that contribution period to make the program a success. So what do the interns do? Well, they contribute across the board in the Linux kernel. Famenta can define a project with a scope that is good for an intern. It can come into Outreachy and he has a laundry list of all the things that the interns have done. And additionally, it's interesting to note that the Outreachy group has been a top contributor to the Linux kernel for pretty much every kernel release when the numbers are published, the volunteers of Outreachy. A lot of it is due to what happens in that contribution period. They do so many cleanup patches across throughout the stage and drive is that they end up being a top contributor to the Linux kernel. So this cohort today and they are they've done an amazing job. Here is their list of projects. Again, there's drivers and there's the course scheduler. These are not simple projects. Excited for you to listen to their presentations. And this presentation has been given once or twice a year. We bring out the interns and they present their projects. And every time there's somebody in the audience who says, wow, I didn't know that they did that much. They're always super impressed. So I'm looking forward to you being impressed right now. Let's get it started and we'll have Beatrice tell you about her internship first. Hello, my name is Beatrice Carvalho and I'm here on the Outreach kernel internship report to show you about my internship on the project, improvement on the kernel GPU subsystem. My mentors was Melissa Wendt and Daniel Vether. I'm from Brazil, but I've been living in Portugal for almost two years. I'm a computer engineer with emphasis on the embedded systems. Of course, my interest are is the Linux kernel. When I start my internship, my object was create new future and better understand how the DRM car works. To achieve this objective, I choose two tasks. Clean up the debug.fs support and remove custom dump map of set implementations. After deciding the two tasks, the internship goals was use the coccinelli to filter functions, refactor the code, run the new code with vkms and learn how to work with the Linux community. Very ambitious, right? But the plans changed sometimes. So what I did? During the event of the first task, we found that it couldn't be carried out as intended. So it needed to be restructured and change what I would do. Results in created the function vkms config show to which I meant to print the data in DRM, the debug.fs create files. And during the development of these functions, I came across an improvement in the code where I replace a macro in a vkms release. Both activities had arrived being reviewed and I proved to be part of the DRM MISC tree. In the middle checkpoint was realized that I was not going to be able to do the second task, because it is in another context and could take a long time to me understand how it works and how to solve it. So we drop off. I continue working in the vkms config debug, try converted into a struct proposed by Ambui Quaruga. It was a privilege in turn in the project. But when I realized the internship they derived and they could finish this activity, I learned a lot of things during my internship. How to use the git, how to build the kernel, how development kernel cycle works. But I think the most important where Linux kernel development is not linear. Several things can happen. We can have setup problems a lot of times. Sometimes we're broken the kernel and sometimes not knowing what to do. So when this happens, it's very very important you take a deep breath and step back to solve what happened and what I need to do to fix it. Other things that I learned is the outreach goal is learning how to contribute in the open source and how I can work with the project chose. The experience that I will have with my internship on the Linux kernel was amazing beyond that I imagined. Because I feel support and encouraged to explore the Linux kernel, how the development cycle works and I was encouraged to ask help both with my mentors and the community and how it works with the community. Because of this I learned a lot of things like the importance of communication. That it's very important to be clear about what I work, explain why I do the modification or what I would improve with this modification for example. And during this time I learned to have more self-confidence in what I do and what I was working. And I started back to enjoy programming. I know it's crazy but it's true. And because this I think the most important is I want to continue working and contributing to the Linux kernel. So in I would like to say thank you to thanks to Outreach Program to this opportunity for working with Linux kernel and thanks to my mentors Melissa and Daniel for taking your time teaching. Please feel free follow me in my blog OpenSorceries where I post about my outreach internship and I will continue post about my discovery about Linux kernel work and other things. So thank you very much for your attention. Have a good day. My name is Deborah Brower. I was an Outreachy intern from May to August of 2021. The name of my project was improving the HDMI CEC compliance test and the CEC emulation of the Vivid Driver. My mentors were Hans Verkau and Johan Fieldsvecht. About me I live in Victoria British Columbia Canada and I study computer science at Thompson Rivers University. So to understand my project you need to understand what is CEC. It stands for Consumer Electronics Control and it allows devices that are connected by HDMI to communicate with each other. It's mainly used in home theater systems. So on my slide there is an example. We have a TV that's in standby mode. It's connected by an HDMI cable to a playback device. A playback device is just anything that plays content to the TV like a DVD player or a streaming device like a Chromecast. When you press play on the playback device it can send a CEC message through the cable to the TV to wake it up first before it starts playing. So CEC is a convenience. It saves you from having to separately wake up the TV when to press play on your playback device. It can be a lot more complicated than what I've shown on my slide. There can be up to 15 connected devices all talking to each other and they can include TV, multiple playback devices, audio systems, tuners and recording devices. So the first part of my internship was focused on CEC compliance tests. CEC is a protocol and it's part of the HDMI specifications. So devices that use CEC have to follow the protocol rules so that everyone is speaking the same language and their behavior is predictable. So compliance test would check that a device is following those rules. So here's an example on the slide. Say your TV is playing and you press pause on the TV remote control. The TV could send the pause message to the playback device. The playback device would pause the media and then the playback device is required to send a status update back to the TV to let it know that it successfully paused. If the playback device doesn't send that status message back then the playback device is not compliant with the CEC protocol and the compliance test would check that. The compliance tests are in the video for Linux utilities and I focused on three of them specifically. Deck control, one touch record and timer programming. The second part of my internship focused on the Vivid Driver. The Vivid Driver is a test driver. It emulates real hardware devices so that application developers can test their applications without having to own all the specialized hardware in which their application might run. Vivid emulates CEC devices and it had a bug in it where occasionally it would lose messages. So on my slide is an example of how this would happen. The TV is sending a get info message at the same time that the playback device is sending a play message. You can't have simultaneous messages transferring in both directions so the TV gets priority and the playback device has to back off. The playback device will try again but on my slide the TV continues to send get info messages and after four times the playback device will just give up and the message is lost. So that was the bug. Our first attempt to solve the problem used an existing internal kernel API called the CEC PIN framework. The PIN framework is used by really rudimentary CEC hardware that just controls the CEC PIN on the HDMI connector but we found that it required PIN level timings that were too sensitive to emulate. If we had timer overruns greater than 0.3 milliseconds messages would still be lost. The successful solution was a whole new algorithm that re-implemented the CEC bus. It used message level timings so the timer requirements were not as sensitive and it also used signal free time requirements which basically forced the devices to take turn sending messages and to share the line better. So what did I learn during my internship? I learned how to write code with the help of other people. So I learned what is a code review and what's it like to get feedback and to iteratively change and improve your code based on that feedback. I learned how to approach a really large code base, how to use tools like Git and the virtual machine and the GDB debugger, how to read and interpret HDMI specifications, how to write a compliance test, what a kernel driver looks like, how it's organized, and how to use kernel functions like locks and timers and threads and how to do kernel debugging. So that's it for me. I want to especially thank my mentors, Hans and Johan for so generously sharing their time and expertise with me. Thank you to the outreach organizers for this amazing program and thank you for watching my presentation. Hello everyone, I'm Natali Bulkar and I'm here to present my project of Outreach and Linux kernel internship. My project was to create a scheduler test suite to understand functionality and performance of core scheduling. My mentor was Vinith Pillai. About me, I'm an engineering student at IIT Roorkee, India. I'm also an outreach's summer return with Linux kernel. Talking about my project, let's first discuss about a core-scaled feature. Core scheduling aims at making hyperthreading safer from hardware vulnerabilities like speculative execution attacks. SMT, that is simultaneous multi-threading when enabled, helps running multiple tasks at same time while maintaining computer performance. It virtually doubles the core that are on CPU. It groups trusted tasks on a core. It treats the CPUs in SMT core as a unit, finding the highest priority task on all CPUs. That task will drive the scheduling decisions. If another task is found that is compatible with high-priority task, it will be able to run on a sibling CPU. Otherwise, that sibling will have to be forced idle. Coming onto my internship goals, my task was to write a comprehensive test suite to simulate scheduler workloads. Then to collect traces, compare the performance results, the baseline in SMT off, and to reiterate on the test suite to add more capabilities. The main point was to analyze the puff traces and detect if the feature is working as expected. That is, no trusted tasks get to share a core. As I move forward through my internship, goals were revised. It was to create a case self-test to check and compare the performance with SMT enabled, SMT enabled with core scheduling, and SMT disabled. What I did was, I created a self-test that ran two threads on a core. One thread is a CPU stressor, and another one is a memory stressor. This test has five variants. First, both threads run without cookie. The next was to run one thread with cookie, and other without cookie, and vice versa. Fourth one was to run both threads with separate cookie, and in the last variant, one sibling is turned off, and tests are run on just online sibling of core without cookie. Each mentioned variant runs for a few seconds. In my case, I ran for five seconds. I checked which test was performing worse than hyper thread off test case. Future work. Coming on to future work, in upcoming time, I am going to build on this small test case and come up with full-fledged test suite to generalize the current Python course kit script by Julian, which works best for virtual machines to be able to work on all operating system. Throughout this internship, I learned a lot of things. I learned about Linux kernel development. I learned how to write kernel code, what is API, and how to use it in the code. I learned about few tools and commands like gdb and perf. Talking about perf, it is very powerful. It can instrument CPU performance counters, trace points, k-probes, u-probes. It is also included in Linux kernel under tools slash perf. I learned how to work with other people on the same task, and to ask questions when you are stuck. Communicating with people and community really helps. At last, I am grateful to my mentor, Vinit Pillai, for being patient, teaching me and guiding me throughout the internship. And thanks to Outreachy for this amazing opportunity. It was overall a great experience. These are some resources which I use during this internship. Thank you so much everyone for your attention. Thank you. Without requiring hardware support, this is great for running tests or eggs on machines where we don't have hardware support, but we still want to check the robustness of our code, like within a CI. My project mainly comprised two code areas. One of them was the weakness driver, which is part of the GPU driver system. The other part was Intel GPU tools test suite, which is a collection of tools for development and testing of the DRM driver from user space. The initial goals for my internship were in two parts. One of them was to expose the VKMS driver through the configFS file system. The other was to introduce V-Planckless or virtual hardware mode. Now configFS is a file system that enables creating, managing and destroying kernel objects from user space. And it is very useful when you want to say test or run multiple instances of a single driver. About the VKMS, about virtual hardware mode. Now VKMS tries to mimic actual hardware by mimicking the interrupts that are found in graphics hardware, which are called vertical blanking interrupt. We wanted to introduce a feature where it can also emulate virtual hardware, that is how we use virtual machines in KMU or by KVM. So this would mean a feature where we can have a KMS driver without vertical blanking interrupts or a V-Planckless mode. However, a month into the internship we realized that our initial goals are not very feasible. Given the amount of time we have, so we decided to only focus on implementing V-Planckless mode and preserving the tests except the tests which depend on V-Planckless interrupts directly. I initially thought that the implementation would be as simple as checking if virtual hardware mode is enabled and then disabling the V-Planckless interrupts and cleaning up the code a bit and that would be it. That was not to be. When we disabled the V-Planckless interrupts, all the tests failed. This obviously happened because the tests were not written in mind, written keeping in mind that we might have code where we need to skip V-Planckless interrupts. So we had to modify the tests a bit wherein the tests check if V-Planckless interrupts are enabled. If they are not, then all the tests that require V-Planckless interrupts or specifically check operations related to V-Planckless interrupts are skipped. Well, all the tests passed. I thought that would be it. But turns out, even for the tests that passed, there were some demessage of errors. I realized this is the cause. It is not necessary that before and after my patch, the tests are passing the same way. Definitely the code has changed and there might be some errors under the hood which are not affecting our tests, which our tests are not looking for, but there are errors that can cause crashes still. So there were two errors. One was memory allocation problem. We solved that by using virtual Manok, which allocates memory over a few pages. Instead of looking for a contiguous physical memory, the other error we were facing was a flaky V-map allocation error, which was already present in the VKMS driver. But it was interacting with my patch to produce a kernel panic. Thankfully, around this time, the part of the code that was where the error was happening, it was changed a bit in an unrelated patch by Thomas Zimmerman, which solved it. So good to go, right? No. There was tests that were still failing. So tests that were based on CRC, which checks for data loss in the frames that are being sent to the screen, were failing. This was because CRC is currently implemented around the vertical blanking interrupts. So we need to refactor a lot of code and refactor a lot of tests also and implement CRC as a one-shot operation. Since this would require a significant amount of testing and refactoring, we decided that at least for the first patch introducing virtual hardware mode, we can just skip all CRC tests and operations. And well, after this, my patch is something that we are mostly very happy with. So Avicii taught me a lot. During my code review and the process of iterating over patches, I learned a few things, which are checking the message logs, even if test results are preserved, because maybe under the hood, things are working differently. And it's important to keep an eye on them. Also that every time we change code, we should check for new race conditions. And maybe sometimes there are no more race conditions that might happen because of the changing code. So we also need to be careful to remove the logs around this part, where we are relatively sure the race conditions might not happen. I also learned how to use the atomic interface, which is used extensively in the DRM subsystem. And the patch review process also helped me write a cleaner code, which also becomes very easy to test later on. I also learned idiomatic C, island, tumors like f-trace can communicate. And a few general things about software, how it can be very tough and very rewarding. Also, planning ahead is very important. And having a great speed or where you can catch up in case something goes wrong is also necessary. Working as part of an inclusive community makes a lot of difference in terms of motivation and quality of work. And it also helped me overcome my imposter syndrome to ask questions in open forums. I'm very grateful to the DRM subsystem for being such a wonderful community to be part of. In the first part of my internship, I did, I saw some low-hanging issues, which really helped me get acquainted with the system. Here are the links to them. I plan to continue working on the weekend as a driver. And this is what I've thought for my future work. Lastly, I would like to say that I'm very, very thankful to my mentors, Daniel and Melissa, who were so patient and allowed me the time to make mistakes and grow and taught me so much about software. And a huge thanks to Sage and Veshawani and Helen. And all my fellow interns for making our produce such a wonderful experience and great community to be part of. Earlier, I used to think that I would use majorly about building software and best practices. I realized it's more about building a software community, which is a diverse, inclusive, welcoming and a wonderful safe space to be part of. That's all from me. And I would like to thank you. Hi, my name is Sia Bagdolet-Kaze. And today, I would like to talk about my internship at Outreachive. This summer, I was an intern for Linux Kernel under supervision of my mentors, Pival's Attachion and Tyler Hicks. The main objective of this internship was to introduce kernel self-test for kernel same-page merging feature or KSM. The kernel self-tests are a set of small tests that exercise individual code paths in the kernel. What is KSM? KSM is a memory-saving feature, which makes use of duplicated pages. It merges only private and anonymous pages and can be enabled by using M-Advice's code. Since virtual machines contain a lot of pages with the same data, KSM was initially intended for virtual machines. But now, any applications that generate many instances of the same data can use KSM. KSM performance can be tracked by using its C-spiles, where you can find information such as the number of shared pages or sharing pages. I started off by writing some unit tests. Unit tests are used to independently test the functionality of server modules. I implemented several unit tests for KSM during this internship. The first test validates that with different tunables, the right number of pages are merged. Along with that, we must also check that no longer duplicated pages must be automatically unmerced by KSM. Also, KSM treats differently zero pages. It depends on user pages' tunable, so it can either merge with the special kernel zero page or treat them as other usual duplicated pages. And finally, the last test validates that KSM is properly handling pages in different numeralodes. So, for instance, if there are two identical pages in two different numeralodes, they can be either isolated from each other or be merged. After unit tests, I implemented some performance tests. These tests are a little different than unit ones, since performance tests are mostly intended for developers when they are making some changes to MM subsystem to see if their changes are somehow affecting the performance of KSM. And there are two key points in performance tests. The first one is, of course, merging speeds. The first test provides merging speeds of duplicated pages in megabytes per second. And the second test evaluates latency of copian write breaks. When we want to modify already merged pages, these pages must be copied again so we can write on them. So this process of copying adds some overhead. As a result, this test provides two numbers, one for write access speed for unshared pages, and the second one is write access speed for KSM merged pages. During this internship, I learned certainly a lot about journal development overall structure and its cycle. For example, difference between RC trees and Linux Next Tree and how different subsystems are maintained. Also, since it is open source, it is not enough to write just a piece of code. You have to conform to the established style of communication. And I learned a lot about the structure of patches and how to properly send them. In addition, I gained very in-depth knowledge about the memory management subsystem, about its overall structure and code base, and etc. And finally, I had some experience with Git, but thanks to this internship I was able to practice it on a more complex and big project. And also, I used virtual machines for the first time. I mainly used them for testing my newly compiled journal. I would like to thank all the outreach organizers and especially my mentors for letting me gain a lot of knowledge throughout this summer. And that's it from me. Thank you for your attention and listening. Bye. Thank you interns. So I hope you were amazed, impressed, and if you want to find out more about these interns or find out how you can help out. I have some contact information here. Companies or individuals can donate. We always need Linux kernel developers to volunteer as mentors and help review patches. Let me pause and give one final thank you to the mentors behind all these interns. I believe each one mentioned their mentors. Pavel, Tyler, Melissa, Daniel, Vanith, Hans, and Johan, these were the key mentors that made the internships possible this round. Please outreach about the program in your professional circle, your local communities. And again, if you want to find out more about any of these interns, mentors, coordinators, look on the outreach.org website. Thank you.


Emotion has a tremendous impact on communication in general, but more specifically, it's very much related to our ability to listen effectively, both in terms of understanding our own emotion and how that impacts our listening skills, but also just our ability to interpret and identify emotion in others and understand how that might impact the message that they are trying to send as well.  So let's take a few minutes to understand emotion and how it might impact listening specifically. To define emotion very quickly here, emotion is the body's multi-dimensional response to any event that either enhances or inhibits your goals. So keeping in mind that emotion is multi-dimensional, that it's not just any one thing, that it's both physical and it's psychological and it's all kinds of things. It's multi-dimensional, but it's a response to a specific event and it either enhances or inhibits our goals. So when we determine whether an emotion is what kind of valence it has, is it going to be what we would call positive or negative? It really depends on whether or not it's helping us achieve our goal or inhibiting us from achieving a goal. So emotion is a little more complicated than we may initially expect. It's not just the fuzzies that come on us when something specific happens. There's a little more to it than that, but let's dig a little deeper then into emotion. So first of all, as I mentioned before, emotions are multi-dimensional. They affect us in more than one way. So they are multi-dimensional. First of all, there are physiological changes that come along with emotion. Oftentimes strong emotions will come with, you know, the increased body temperature will see more sweating or hands will get clammy. Our heart rate will increase. Those types of things, our stomach may tighten up a little bit. Those are physiological changes, changes that happen within our body when we experience a strong emotion. We also have nonverbal reactions when we experience a strong emotion, whether it's fright or surprise or joy or whatever it is, we're going to respond in a nonverbal way. So that's another dimension of emotion is how it impacts us in our nonverbal communication. But we also have cognitive interpretations that are related to emotion. In other words, how we think about those emotions and how we interpret them in our own mind and how we assign value to those and assign meaning to those things. Those cognitive interpretations are an important dimension of emotion as well. And then finally, our verbal expression. We express ourselves verbally when we experience an emotion. And so how do we do that? Are we doing it in an as effective way as possible? That's what we mean when we say emotions are multi-dimensional. They affect us physically. They affect us psychologically. They affect us in an unverbal sense. They affect us in a verbal sense. So there's a lot of dimension to emotion and a lot of things that happen and can happen as a result of those emotions. I briefly mentioned before as well that emotions will vary in what we call valence. Valence is basically the appropriateness. So we identify valence in two different categories. First of all, intensity. Intensity. How intense is that emotion? Meaning, are we experiencing that emotion to the right level of intensity and not letting it get either too out of proportion or not giving it enough intensity? Either way, we want to be in the appropriate range of intensity and then duration as well. So duration meaning, is that emotion affecting us in the appropriate length of time or for the appropriate length of time for the appropriate span of time? Or are we letting it linger? Are we letting it go too quickly? Are we letting it linger too long? Either one of those would not be great. So really when we talk about valence, we're talking about appropriateness. So we look at this in terms of the level of intensity and duration and is it still in that appropriate range? When we stay angry for too long or we get way too angry over something small, that means our emotion is taking on a negative valence. Meaning it is not in the appropriate proportion for either of those factors, intensity or duration. Meaning it is keeping us from achieving a goal. It is inhibiting us from achieving a goal. So we would then assign that what we call negative valence. But if we are experiencing it in the appropriate range of intensity and duration, then we would say that's having a positive valence. If it's helping us achieve a goal in that sense. So emotions are going to vary though in valence. And every emotion can have either a positive or negative valence. It just depends on the situation. It depends on the context. So we need to keep that in mind as well. But that's how we look at emotion and kind of weigh and measure emotion is through valence. So there are a variety of things that influence emotion and factors that come into play.  Are you just a generally happy person? Are you generally kind of sour person? Are you right in the middle?  A great deal on how we experience and how we express those emotions. Our culture will as well. You know, in Westernized cultures, we tend to be more expressive with our emotion. We value that personal freedom of expression. Whereas in more collectivistic cultures and other cultures, they tend to be more reserved in their expression of emotion. And because they don't want to, it's a collectivistic culture. They don't want to upset the fruit basket, so to speak. So they tend to hold things in a little more and don't feel the need to express every emotion in the moment that they have it. As we do in some, you know, individualistic kind of culture. So our culture certainly will play a role in how we experience and how we express these emotions as well. Our gender and member gender is really a sociologically defined. It's a social construct in a sense, right? So masculine, feminine. We're not talking about male-female here. We're talking about masculine and feminine. And we've been conditioned as, you know, if you are primarily masculine or predominantly masculine, then you experience emotions. Or you would express emotion differently than if you were predominantly feminine in your gender. So gender will have a significant impact on how we express emotion in particular. Social roles and conventions kind of come back to culture in a sense. But really what's expected of you as a parent or as a doctor or as a teacher or whatever, you know, what are some of the social roles and conventions that apply to how we are expected to experience and express those emotions. Social media certainly has had a major impact on emotion as well. We see what we call the disinhibition effect, meaning people are more likely to express emotion more quickly and in a stronger fashion over social media because they are less inhibited in that context. So we say and do things we wouldn't necessarily normally say or do in real life. We do that over the internet because we're removed. That removal of being, you know, on the other side of a screen from somebody sort of gives us the feeling of permission to express ourselves in a stronger way or experience and express those emotions more strongly. Which, you know, has positive and negative attributes, I guess, to it. And then emotional contagions as well play a role here. The fact that emotion can absolutely be passed from one person to another. If somebody walks in with a really strong emotion and they walk into a room with a really strong emotion, that emotion is going to rub off on everybody else, whether it's a, you know, happiness or anger or whatever. That's going to have a tendency to rub off on those around them when they may not be experiencing such a strong emotion. So emotional contagions, what are we passing along to other people? That will influence our emotion as well. And then finally our emotional intelligence impacts how we experience and how we express emotions to a great degree. So let's spend a moment just talking about emotional intelligence and what that is. So emotional intelligence is the ability to recognize, understand and manage your emotions as well as understand and influence the emotions of others. So emotional intelligence essentially is our ability to first of all recognize, which is not as easy as it sounds, but when we're experiencing an emotion, being able to say, okay, I'm experiencing this emotion. Put our finger on exactly what it is we're feeling rather than just letting that emotion take us over and without really understanding what it is. We need to recognize our emotion and recognize when we're experiencing an emotion, a strong emotion. Understanding what that is and what that means, what that implications that may have for us and those around us. And then being able to manage our emotions. Now that does not mean totally tamp down our emotions and never experience or express an emotion. That's not what this is getting at. What we're getting at here is our ability to effectively express and looking at it in terms of positive valence. Are we allowing that emotion to manage us? Or are we managing that emotion in a way that helps us achieve our goals in that situation? And then doing that for others as well, being able to recognize emotion and others, understand what that means for them, influence it if possible. Influence is not the same as manipulate. We're not trying to manipulate the emotions of others, but we're just saying, you know, are there ways we can help somebody in a bad mood be in a better mood or that we can, you know, for bosses in a mood, what can we do to influence that? It's in a way that affects us positively, hopefully. So the ways that we can influence those things without manipulating people and without minimizing their emotions, we can understand those and influence them as well. So emotional intelligence basically says, how good are we at doing this? People with high emotional intelligence have loads of this ability and people with a lower sense of emotional intelligence don't have the ability to do these as well. Now this is something we can develop within a certain degree. So something we ought to work at. Aristotle once said that anybody can become angry. That is easy, but to become angry with the right person and to the right degree and at the right time and for the right purpose and in the right way, that is not within everybody's power and is not easy. And really what Aristotle was getting at there is that not everybody has the same degree of emotional intelligence. Emotional intelligence is what gives us the ability to be angry with the right person to the right degree at the right time and for the right purpose and in the right way. We have high degree of emotional intelligence. We have the ability to do those things more effectively. And somebody with lower emotional intelligence, that's just not as good for them and not as one of their strengths. So we ought to develop as listeners, we want to develop high emotional intelligence so that we can really relate to others, understand their emotions, understand how that would impact what they're saying and why they're saying it and what that means for us. So we ought to be able to look at those things really as a communicator. That's the idea and be able to factor that into our listening and have emotion be one of the ways that we listen. We don't just listen with our ears. We listen with our eyes. We listen with every sense that we have in terms of identifying that other person's emotion and how that might impact what they're saying and how we might interpret it. So if you have questions about emotion and how it impacts listening, please feel free to email me. I'd love to hear from you there. In the meantime, I hope that you will have a renewed understanding of the impact that emotion does play in interpreting the communication of others in particular in the way that we might listen to others using our emotional intelligence.


Hi, I'm Mitch Loculain, and welcome to Riedel's podcast series. Today we'll be bringing you this episode from the heart of Sydney, where we'd like to shine a light on the arts and theatre industry. We will be taking a look at the role of stage manager and what exactly these highly skilled individuals bring to the arts. It's about highlighting the challenges and the most interesting aspects of this role. We are particularly honoured to have stage manager, Mary Ann Carter, an incredible industry expert joining us for this session. Hi, guys. Thanks for joining us here today at Riedel. We'd really like to just talk to you about, really, today, what you think about the theatre industry in general, about your role. But first, I was wondering if you could just give us a little bit of background into yourself and what you've done and talk us through it. Yeah, sure. So thank you. It's a pleasure to be here. My name is Mary Ann Carter, but everyone calls me Maz. I've been stage managing for just over 20 years. I work freelance. There's a lot of companies that I work with regularly, but I do a bit of everything.  I've done a little bit of everything. I like that. Magic's good. Is there any fun magic that you've seen that's kind of blind your mind? Magic is always fun because we don't get to tell you how, but we're quite often involved very closely in the magic backstage. So it's always it's good fun to be in on the trick. Yeah, excellent. Excellent. So let's kind of get into this. And can you describe for us what the role of the stage manager actually is? Yeah, absolutely. And it's quite a hard role to describe because it is very varied. So basically stage managers coordinate and facilitate the artistic, technical and safety elements of putting on a show. But because theatre and events vary widely, the job itself varies depending on what the production itself actually needs. So I often say, I don't know what my job is until I know what the show is. But some of the core skills that you need for the job are technical knowledge and ability to facilitate technical artistic needs as well. And you need to read music, but mostly what you need is good communication. That's probably the key quality. Stage managers definitely need the right temperament and the instinct for the work. I would say the most fun part of our job, though, and the one we tend to focus on is calling a show. And by that, I mean we create a prompt copy from either a score, a script or a running order, and we queue all of the technical elements that happen in a show. So this ranges from really simple shows where you just queue the lights on and send one person on stage to really complicated shows where you might have potentially hundreds of queues to call and you could be talking to dozens of people at the same time. So for example, I've done shows where I've had to be communicating with 20 people or more at the same time whilst watching a dozen screens. And then you've also got to be aware of and dealing with what's happening live around you as well. So it's certainly a kind of, what would we say, it's a multi-skilled juggling approach. It definitely is a bit of a juggling act, going back to your bit of magic and pulling a rabbit out of a hat when it comes to definitely communicating to a lot of people. And it does seem that that is quite a critical part of your role as well in terms of being able to make sure that you are heard and everyone can hear what's going on so that you can coordinate those people. And I guess you have to deal with a lot of talent as well. Did is that something that, you know, is quite critical in your role? Absolutely. And dealing with all different types of talent who have different temperaments, different ways of speaking to each other and different needs and sensing what that talent needs just before they walk on stage is a big part of the job because I'm there to create a world that they can perform well in. So you have to kind of sense what they need artistically and technically and give it to them in the moment so that the show is as good as the show can be. So what would you say that your most challenging part of stage management is? I would say probably the most challenging is staying calm while dealing with different personalities. So art requires people to push themselves, which means tensions can raise when people are really working hard to try and make something special. But you need to stay calm and provide an environment where everybody feels like they can do their own part of the puzzle. Yeah, excellent. And I'm sure it does get quite hectic at times when you're when you're trying to coordinate all those people. 100%. Yeah. And how do you generally overcome some of those challenges? So to, you know, to keep yourself calm and to try and project that level of calm onto everyone else that's around you when everything may not be going the way that you want it to go. For me, it's preparation. That's like my biggest tool in overcoming any challenges. The more prepared I am, the calmer I feel. And if you're prepared and calm, then you can better deal with changes on the day because there is always changes on the day. So I like to say be super prepared and then just enjoy the ride when the wheels come off. Yeah, sure. And do you think from your perspective when you're trying to, you know, understand and get across those changes as well as keeping calm and trying to find those wheels as they're bouncing down the road, do you think that having the ability to be able to make sure that everyone is aware and has that awareness of what's going on? Do you think that that makes your role a lot easier? Absolutely. And it makes everybody else's role easier too. I think lots of crew will say to you that a calm voice on comms, making everybody feel like everything is in control is what gives them the strength to do their jobs well. So... Yeah, definitely. It's almost like you need voice coaching to make sure.  But the calmer they sense your voice is, the more that they will trust that the show is going to work. Yeah, definitely. And I know from being out on some of those shows that they don't always go to plan. And there is a lot that you have to be able to, you know, work on your feet to get happening and trying to keep a lot of those people calm who just may not know that what's going on and certainly being able to have one of those nice calm voices is nice to hear at the end of the day over the end of the comms. So as a freelance stage manager, how has the development of communication technology improved your workflow and the workflow within the theatres for where you work? Well, being able to communicate well is an absolute must for a smooth running of a show. When crews can work as a team and communicate well without hindrance or frustration from the column system, you've already won half the battle of putting on a really smooth show. Theatre comms, when I started out, used to be very, very simple, but as theatres evolved and become more technical, the comms have had to evolve to meet that demand. So I would say the biggest change in all of that was latency. When that came in, that was a really big change for everybody. So it's certainly an excellent thing that companies like Redell are leading the way in kind of producing that latency over digital comms because it's a big thing for our industry and for my job particularly. So you have to understand the core part of my job is precision in timing. So there's nothing more important to me than the timing on the comms. So that's why that change was such a big thing for our industry. There's several layers of complexity when you're calling a show. So I have to hear what's going on on stage. I take a millisecond of response to that and then I say the word go. Somebody else has got to take a millisecond to hear that and then they've got to spend another millisecond reacting and pressing the go button. So calling a show, it's more of an art than a science and the better the comms system is, the better the art that we do with that comms system is. So when I hear about comms systems that have super low latency, I'm like a kid in a candy shop. I think, great, that means we can do our job really well. Great.  So whether it's lighting, it's audio, mechs and so forth. So who do you consider from a stage management perspective as your team? Everybody's my team and I'm part of everybody's team and we're all a team working for the show. And it really is one of those things when we're your stage managing, sometimes one department will feel like their need is a little more important than somebody else's need but essentially we're all just working on the show and I feel like sometimes I'm the captain of going, no, here's what the show needs right now. Yeah, that's right. So it's never kind of about who gets to win an argument. It's really about what is the show need in this moment. And that's correct. That's definitely right. And you want to get it done and you want to get it done right. And as you said, that comes down to not only the fact that sometimes, yeah, the theater comp show that need to be complex but from a user perspective, they need to be simple as well, right? Which is really what you've stated. And what do you think makes them simple? Like for you as a user, what do you think that in theater communications, I should say in general, but what do you think makes it simple for you? I really like when you meet a new system when you can very quickly simplify the system to what you need. So if you don't want to be hearing a lot of things and you can quickly turn them off, that's always great. But if it's a complex show, of course, you need the opposite of that. So a flexible system is really important because like my job, I don't know what it is till I know what the show is. You don't know how complicated you need the system to be until you see what the show is. So... Yeah, definitely. Are there any disadvantages to a, you know, maybe a more complex system that might not be as easy to handle? Look, if it's complex, the only disadvantage is usually the squiggy organic thing at the end of the system.  You know, for example, I was watched stage managing for a major orchestra and I had completely and utterly forgotten that they had routed the comms down to recording studio in a completely different set of the building. So I got on comms and started saying to the lighting operator, God, I'm so bored right now, I could absolutely. And then I put in a lot of colourful language and forgot the artistic director for the orchestra was downstairs listening in. So, you know, that's not the fault of the comm system, but you do sometimes when they're complex comm systems, forget about these things. And it's, you know, if it's a complex comm system, you can make it do whatever you want. It's just sometimes we forget what it's capable of doing, I think. Yeah, definitely. And I've certainly had those experiences relate to me previously when, you know, and coming from a bit of a broadcast background as well, whenever you see a comms panel and a microphone, you just assume that it's on and you don't say anything, you don't want anyone else to hear. So that's, it's certainly always interesting to be at the end of a comms panel and, you know, a communications belt pack. And certainly performing your job, it does make it very, very simple for you and for everyone else when you're able to be able to talk to anybody that you need to talk to. All right, man, thanks very much for joining us here today. It's been a pleasure to have you on. We hope to see you out in theaters soon and have a fantastic day. Awesome, thanks very much.


Welcome to Digital Asset News, the top stories in cryptocurrency and digital assets and bring them down to bite-sized pieces today. That's pretty interesting stuff. First up, Bitcoin will break out this year, says DeVair, CEO. And this is yet another example of a large institution stating the obvious that Bitcoin is going to be huge. Now, having said it this year makes it very interesting. We're going to take a look at all the different institutions that have said what they have said and where this all might potentially lead sooner rather than later. Also, Ripple partner Flare says 295 million XRP sent to claim the Spark token in massive response from crypto investors. We're going to take a look at this and I'm going to show you with a tutorial, a step-by-step process, how to use the Nano Ledger S to claim your Spark tokens. And we'll round up the day with Q of the day and we'll do that at the very end. But first, let's jump into the market. So today, September 1st is about 9am, Texas time, getting things done early. Thank God. So I gotta tell you, it is way easier to make these videos when the market is up because everybody's usually, they have a natural exuberance, they're really happy in there. You just want to see what's going on and there's not too many negative comments. It's amazing. So these are the days I live for. So Bitcoin is up 1%. Almost touching that 12,000 spot. I think it can do it this week, but time will tell. Ethereum up big time. Bigly, 469, I think it's going to touch 500 by the end of the week. We're up 8% and 15% for the 7-day average. And then Tether and XRP are two stable coins. What are you going to do? XRP watch out. Chainlink, about the same, $16. Up for the weeks, 5.2% looking pretty good. And Polkadot, I gotta tell you, I think it can reach $7, but we will see. It's up 44% massively for a 7-day average, not too shabby. Cash, Litecoin, Litecoin up 1.7%. Great. 5.4% for Cardano, SV up 1.1%. Crypto.com, 0.6%. Nothing really big. Tron up big time. And I know they just did a partnership with Band, so we'll see how that all works out, but looking pretty good. Stellar 2.2 Monero, which Monero don't really have too much faith in. Looks like they're trying to get rid of all the privacy coins. We'll see how that works out. NEM up 21%. Congratulations to all you NEM holders. And UMA, the one that I totally got wrong on Alex Mascioli's video. I gotta tell you, UMA is doing massive, but I think it all has to do with DeFi and Sushi Swap, which I definitely need to do a video on sooner rather than later. And that's really the big stuff moving forward. 26% for Ampliforth. Again, DeFi looking good. All right, well, let's jump into today's top story. So first up, Bitcoin will break out this year, says DeVair, a CEO. And I'm always looking for big institutions that are talking positively about Bitcoin. And I know it's not the most exciting technology. It is 10 plus years old now. But from what I've been talking to, from what I've heard about, Bitcoin will still pop because it is on the minds of every big institutional investor. Now, all the different things that are going on with DeFi, that is the new generation, I think. Now, can that actually sustain? I personally don't think so. But only time will tell. Anyhow, what's going on here? So DeVair Group CEO Nigel Green, but did the last week of the US presidential election and a weak dollar will drive the price of Bitcoin for the rest of 2020. I think it's that, those two factors, plus quantitative easing, which is going to lead to Bitcoin being massively pumped. Finally, Federal Reserve's policy shift on inflation, in case you don't know, the Fed wants to massively, not massively, but it wants to let it run hot as far as inflation above 2%. And of course, when we see inflation, that means a opportunity for Bitcoin to start to rise up. And of course, where Bitcoin goes, so does the rest of cryptocurrency market. He also warned about investing in the stock market, which I think is interesting because that is what DeVair is all about. Stock markets and pensions and things like that. DeVair Group established by Green in 2002, described itself as one of the world's leading independent financial advisory organizations, more than 10 billion assets under management or under advice from 80,000 clients in 100 countries. And I had to take a look at the website to see what this place is all about. And it's just the basics, the basic website. But when I found interesting under products and services, it talks about here, international pension planning. If you know anything about pensions, there is a real problem with them across the United States, actually cross globally. And I've always said, if pensions get in the game, watch out, because that is a huge amount of capital to come into the cryptocurrency asset market. So I'm hoping these guys will be on the forefront of going, Hey, you know what, let's try to push, you know, one to 5% into this asset class, which is the best performing asset class of the decade, just saying. All right, so scrolling down, they talk again about US presidential election, always there's uncertainty. But I got to tell you, this one is going to be the most uncertain, I believe personally, if Joe Biden gets elected and becomes the president, you will see the stock market drop because Donald Trump has done great things for the stock market and all his of his friends, let's be honest, he's got a lot of, he knows a lot of rich people. And with the tax cuts, he's done big things. And that has pushed up the market.  All I care about is where is the price going to go. And if you see Trump get reelected, who knows, then I think that the stock market will push a little bit. I don't know, it can continue this nonsense, especially with the Fed going, Hey, I'm going to let inflation run a little bit hot. But if you see Biden come in there, it's going to tank a little bit. Is that a bad thing? Not so much for us. It doesn't really matter for us because it's all good. All this uncertainty is good for us. Cryptocurrency is assets because it allows people to go, you know what, that economic policy that we have here in the United States, which is actually causing problems throughout the globe is screwing things up. So where can we go to a safe haven asset that has no boundaries, is not influenced by any government and has an economic hardening of its financial backing? Well, guess what? You can't print Bitcoin. So let's go with that. And then, of course, they get in, then the floodgates open and cryptocurrencies. That's just my thesis. Anyhow, so you have the presidential election, you have the coronavirus and quantitative easing. And of course, he says here, as uncertainty heightens, investors will pile into safe haven assets, in particular those not tied to any specific country, such as Bitcoin and Gold. And I have to agree. I think the new savings account is Gold, Silver, Bitcoin, but just an opinion. Decentralized, I've never heard this before, non-sovereign. I mean, I've heard the phrase, but I've never heard non-sovereign with cryptocurrency assets. I'm going to start using that. Decentralized non-sovereign, meaning not having to do with any type of country. Secure digital currencies, including Bitcoin, will become more attractive to investors as they will offer a hedge against turbulence in traditional markets. And this is the same thing that Shamath, Peli Hepatia, was talking about. He calls it schmuck insurance. And that's why we should get Bitcoin, because it could pay off massively when all the economic policies start to fall around us. And I think that's exactly what's going to happen, even if it doesn't collapse. I don't think that the dollar's going to totally wipe out for the reserve currency of the world. But I do see a lot of turbulent times ahead. And when there's turbulence and uncertainty, where can you go? Safe haven assets. Anyhow, the Devere Group CEO added printing of historic sums of helicopter money that's pushed in the financial system has devalued the dollar and prompted it inflation fears emphasizing you can't print Bitcoin. And of course, I just kind of stole that from him. But it totally makes sense. So I'm going to add these guys Devere to my institutional investors when I talk about everything else. So some of the people who are in the space, Fidelity, with their eight trillion assets under management, they also got a merit rate with one trillion assets under management. And you got the Goldbugs, Van Eck, with 49 billion AUM. And these guys were heavy into gold. And they say, you know what, as good as gold is, Bitcoin's even better. And they lay out the whole case. Paul Tudor Jones, 21 billion assets under management. And he put 2% of total investments into Bitcoin futures. This was on May 8th. And he is apparently a legend on the stock market. So when people take a look at, well, Paul Tudor Jones is doing it, I'm going to do it. And then off they go. And of course, Grayscale, who are massively buying up Bitcoin in droves, I think they purchased like 75% of all Bitcoin in the last couple of months. And then lastly, MicroStrategy just came out and said, hey, we're buying 21,000 Bitcoin. And this was this month, or actually, I guess last, last month, because it was September 1st. So they own 0.1% of all Bitcoin. And the CEO state, hey, Bitcoin's digital gold, harder, stronger, faster, and smarter than any money that has preceded it. And these guys, if you don't know, they just deal with computer analytics and data processing. So my theory is that they probably took a look at all the different analytics that they have and data and said, you know what, it was really going to be good and probably going to happen pretty fast. Bitcoin, let's get into that. And they bought a ton of it. All right, so that's it for that section. Let's move on. Next up, this is all about XRP. So if you are an XRP holder or thinking about it, stick around. If you're not, go ahead and fast forward to the next section, talks about the queue of the day. So what's happening here? Well, Flare Network is a new Turing Complete smart contract platform. All we're doing here is we're going to try to get the spark token, which is the Flare native token. And it's like an airdrop, which you're going to get a utility fork of XRP. So we're going to set this up so you can get your spark tokens easily and simply by using a Ledger, Nano, S, or X. That's all we're going to do right now. So this all comes from White's Wind. I think I said his name right. But White's Wind, he's one of those lead programmers for XRP Labs. And he put out a tool to help you get your spark tokens. So pretty simple. To make it super simple, actually, there is a nice little graphic that was made by Stethus Crypto. And let's just blow it up real quick. So here's what you need. So you need a Ledger, Nano, S, or X. You can also use Zoom or XUMM if you want to, but Ledger, Nano, S, and X is pretty simple. You don't have that, you can use the XUMM. So you need a non-custodial Ethereum address, meaning you can't use Coinbase or any type of exchange. It must be like MyEtherWallet, Mu, MetaMask, Nano, S, something like that. We're going to get the XRP Toolkit, which is xrptoolkit.com to connect your Ledger wallet and the full guide for XRP holders, which is the one we just took a look at. So very first thing, I'm going to go do an overview here of this nice little graphic. Then we'll go over to whites.com to take a look at what we got to do. So we're going to go to the Warnings and Slamers. I'm going to click Continue. Here's the options. We're going to choose 2B. Don't use XUMM. I think it's Zoom, X, ZUM, I don't know. And we're going to use an NL address. If you don't have one of those, then you're going to use the XUMM. You're going to generate an ETH-compatible account, which is pretty simple. If you don't have it, you're going to provide an ETH-compatible account address, which is right here. We're going to stick it in. Then you're going to connect your ledger nano to the XRP toolkit, and we'll go over all that in a second, and paste the message field and so on and so forth. So let's do the very first thing it says, visit flair.whites.com. Okay, before we get started, there's something very important you need to know, and that is that if you need a firmware update, which looks like this in your, for your nano ledger, under Ledger Live, then you must update your firmware first. If you want a step-by-step tutorial about how to do that, there's going to be a little card that's going to swipe right about now, and you can click on that and watch it. It's about seven or eight minutes, then it'll help you walk you through. But you must do this first if you have this little option where it says update firmware. So do that first before you move on. So again, one disclaimer is warning and acknowledgments. I am responsible. Tool is right on a voluntary basis. Tool is right on a voluntary, sure. I agree. Yes, I do all that stuff. Read it all. Fantastic. I'm going to click continue. So we can click on 2A or 2B. Again, if you don't have a ledger nano, you're going to click on 2A and continue, but we have one. So we're not going to use XUMM. I'm going to click continue. So number three, generate ETH compatible account. So if you have a nano ledger, you should have an ETH compatible account. It's going to look something like this, 0x415, blah, blah, blah, blah. So just to make sure, if you want to go to your nano ledger, you can go to portfolio or you can go to accounts, doesn't really matter. But so here's Ethereum. And you can tell here's my legacy account. I'm going to click on that. And up here, let me move this down, send receive by Ethereum. If you just want to find the actual address, just click on receive. And it's Ethereum on legacy. Yeah. It's going to have you take a look at your actual nano ledger. And that's the address, 0x. That's mine.  Anyhow, we're going to click on copy this address copied just to make sure that we have it. So we do have it. We're going to skip this step. I own an ETH compatible account. And I own the secret because it's in a nano ledger. And it's going to say, okay, now provide it. Now prove it. All right. Command V. And it says right here, please never use a ETH compatible address generated for you by an exchange. Got it. Next. Number five, confirm account ownership on the XRP ledger. Your ETH compatible address will now have to be stored in the message key field on the XRP ledger on your account. This way flair networks can determine the account on a flair ledger is owned by you. This way, the token distribution contract knows which XRP ledger accounts contain the balance to read for spark token distribution. And it says here, you didn't use XUMM. So please follow the instruction below to use XRP tool kit.com for legion of devices to store your ETH compatible address in the required field on the XRP ledger, blah, blah, blah. Great. So it's going to say open XRP toolkit, nice, fantastic little link and connect your wallet. So we're going to open link in a new tab. And here it is. And it says connect your connect to a ledger. Sure, we'll click on that. And it says plug in device and open the XRP app, which it is plugged in, but now I need to go to XRP. So I'll go back to my Anna ledger, scrolling over to XRP, hit the buttons, and it says retrieving account information. That's me XRP 6,169. So just so you know, like I have multiple nano ledgers, I have a couple Ss, a couple Xs. And I'm going to have to do this for each single one, because in this one, it has 6,000 XRP. So that's just one of them. So we'll do that, we'll confirm. So here we are on the XRP toolkit.com. There is our address. It says we have 6,169, which is the exact amount that I have on my, on this ledger. And are we done? No, there's a couple more steps to do. So we're going to go back here, it says in the main, so open XRP tool toolkit and connect your wallet. Done. In the menu bar, go to account and select the properties menu item. So here's account, properties. Look at the account properties page for the message key section, which here is a message key section. And it states, paste the value displayed below in the message key field and click the update button. So I'm going to copy this, come over here, stick that in the message key, I'm going to click the update. And then we're going to actually take a look at our nano ledger. It's going to say transaction type account setting. I'm going to scroll over account one of three, RHZ, blah, blah, blah, blah, scroll, that says account one of three, scroll over account two of three, count three of three. Here's the fee XRP point zero zero zero one two, I'm okay with that message key one of five, two of five, three of five, four of five, and it's going to scroll through. And then the last thing you're going to see is going to say sign transaction with a checkmark. We're going to click both buttons. If you got a S or X, whichever one they are, or if you keep going, I'll say reject. So we're going to accept it. We're signing it. Submitting the transaction. Please wait. And we're all set. And that is all there is to it, my friends. Now we're going to go back here. We're going to click on next. And that's pretty much it. So you just got to wait until probably December when it starts to do that drop. And what I have to do is I have to go back and do this for all my other nano ledgers because I have them on different ones. All right, so I hope that helps you out. Let's jump into Q of the day. Okay, everybody, welcome back to the office. So for our Q and A, we've got Brad Cam, and he is the co-founder of Unstoppable Domain. So the question always is for differences of subscribers are two questions. One is, Rob, what should I invest in? And for that, I have no idea because I'm not a financial advisor. And the second thing is, as far as like crypto domains for unstoppable domains, what type of industries or what type of domains should I get into? Again, I don't have that type of information, but my man here does, because he sees all the data and all the information that we are not privy to. So Brad, thanks for coming in and doing this quick Q and A of the day. Thanks a bunch for having me. And yeah, I mean, I think we get this question a lot, and I don't know that we're experts either. I think this is a new industry. So I think that the thing that everyone's trying to figure out right now is what are going to be the similarities between the traditional domain industry and the blockchain domain industry, and then what are going to be the differences. And I think I was maybe started buying domains in like 1998 myself.com domains. I kind of went through this cycle. I bought a couple of good ones, but not too many. I don't think I was amazing at it or anything. But the things that I think everybody was really into at the time were like, so there was gambling related stuff. There was sports related stuff. I think my only successful sale ever was fantasy football at futbol.com. And then I think that, so those were the things that I think, oh, and also marijuana related terms and stuff like that that wound up being pretty important. And I think the reason why they wound up being important was for sort of a strange reason, because a lot of the ad platforms wouldn't let you buy ads around weed terms. And so if you had this domain, it was like the only way for people to find it. So people were actually typing it into the web address bar as that of just into the search bar. So that was kind of a quirk of history that made marijuana related terms pretty interesting. I remember back in those days, I do remember. Yeah. So just from what we're seeing with folks on the blockchain domain side, people are interested in a lot of crypto related terms. I think that's anything that is in any way associated with crypto or crypto meme is probably where a lot of the focus is going. I think people are also going after traditional industries like travel and healthcare and finance and other stuff like that. So we're seeing that stuff. We're seeing crypto stuff. I think the one other area that maybe is like a little unique about blockchain domains that doesn't probably happen quite as much in the traditional world is that these can also be domains for your personal website or for people to pay you personally.  So that's another thing that we're seeing is people trying to get their names. Whereas like in traditional world, having your name is your domain name. Maybe that matters, but maybe you care a little bit more about your email address. Maybe you care a little bit more about something else. Yeah, makes sense. I think for us, when I tried to describe it like why people would do it, there's always a couple reasons. First of all, your name because you can get paid in cryptocurrency. So Bitcoin Ethereum, every other type of cryptocurrency that you want to, wouldn't that be great if you just have your name joeblow.crypto and just goes right there. So it's like super simple instead of those long hash graphs. Fantastic. And then of course, I saw that sex.crypto just sold a couple of days ago for I think it was $90,000. So not that that is like the typical type of what's going to actually happen, but I can see as as you were saying it names, I can understand the industries, you know, crypto and things like that. But if we look like I was thinking like five, 10 years down the road, what are these these regular industries that we see right now, especially like with with finance and banks, and then branching off into like pharmaceuticals and healthcare and just the regular actual business names where they could put crypto or Zill, how much would that be worth, you know, going further? Like these are the types of I think plays that are like way down the line, but I think they could be huge, just like with your fantasy football and marijuana. Imagine if you get like a marijuana type of website back in the 90s and what it's actually is for today, as far as like the states that can actually actually legalize it, it'd be huge. It'd be, you know, a watershed moment. But who knows? I don't know. Yeah, I think the one thing I would keep in mind is that that, you know, for your listeners out there is that, you know, one of the things the thing that's super important for domain names is making them useful. Like so, you know, you have a way to get traffic. And once you figure out a way to get traffic, that's really what, you know, that's really what's going to make your your domain name important. And I think one of the reasons why people are thinking about industries like porn industry, like marijuana industry and others is because those are, you know, legal activities, at least the illegal activities in the US that have issues with the current tools. So, you know, those types of places when the current internet really isn't quite working for you, even though you're not doing anything wrong, that's a great place for, I think, crypto in general, to step in crypto payments to step in blockchain domain to step in. Those of course aren't the only industries that are that are that are relevant.  And again, this is not our prediction. We do not make predictions about what's going to be the best domain name. I don't think that we're the experts at that. We're technology builders. So we're trying to build a revolutionary new domain registry, how the ecosystem rolls out over the course of the next 20 years, I think there's probably there might be better people to predict exactly how that's going to go. We're just watching and observing and seeing these kind of early trends, but it's really it's really early.  And so that's another category. So I know I already talked about finance, but just just to kind of make it real for everybody, the stuff that people are actually doing today, which I think should be, you know, kind of if you're trying to think about how to, you know, how to focus the stuff that's actually happening today should give you a hint of, you know, maybe what's going to be there tomorrow. So I kind of see it like what you said in the beginning, get your name, because it's going to be easy to accept payments, right? And then maybe like to get traffic to your website, maybe something like for like blog or something like that, then look towards DeFi, perhaps maybe something around there, and then cryptocurrency, and then way far away what I was talking about. Okay, got it. All right, Brad, thanks so much. I appreciate it. I know you're a busy guy. So that's it for today. All right. So I hope that helped a little bit for Q of the day. Now, if you want to sign up and take a look at different domains for unstoppable domains, there is a link in the description of my video is going to look like this. This will take you directly to the unstoppable domain site. A lot of good things out there. I've already bought two. I think I have three now, and we'll see what all works out. Maybe in a couple of years, I could be a millionaire, but I don't think anybody's going to want to buy Dan likes crypto or Dan likes crypto or Dan teaches crypto. Maybe not, but who knows? All right. So I want to say thanks again for watching all the way through. Really appreciate it. If you like those types of videos, there's going to be too much going to pop up in your left and right. Not for sure, because YouTube handles all of that, just like the ads you may have seen on this video. So if you saw a scam ad in the beginning, middle, or even after this, go and talk to YouTube. They'd love to hear from you. So that's it for today. Really appreciate it, and I'll see you on the next one.