Podcasts about Maintaining

Grandpa Bill's Grunts & Groans@billholt8792 Magoo's Redemption: A 2025 Christmas Carol" "Scrooge 2.0: Heart-Brain Coherence & Modern-Day Miracles" "From Grinch to Giver: The Power of Mnemonic Memory in 2025" "The Ghosts of Christmases Past, Present, and Future: A 2025 Perspective" "Unlocking Magoo's Potential: A Christmas Carol & the Magic of Memory" #ACarolForThe21stCentury, #MagooReborn, #HeartBrainCoherence, #MnemonicMemory, #PodcastLife, #ChristmasSpirit #2025Vision #BenevolentBusiness Grandpa Bill's Grunts & Groans @billholt8792 #GrandpaBill, #BHSalesKennelKelpHolisticHealingHour, BH Sales Kennel Kelp Holistic Healing Hour Podcast : Instilling and PRACTICING Calm -Peace-and Repose Weekly Guided Meditation: "A Christmas Carol" Revisited:https://www.buzzsprout.com/2222759/episodes/16319651 Summarizing the key plot points of "A Christmas Carol." Highlighting the significance of the three ghost visitations. Discussing how these visitations impacted Scrooge's character. Magoo's Transformation: Describing Magoo's initial personality and behavior. Explaining how the "A Christmas Carol" framework inspired his transformation. Detailing the role of Heart-Brain Coherence in this process. Modern-Day Scrooge: Illustrating how Magoo's transformation manifests in his 2025 life. Describing his new business practices and philanthropic endeavors. Emphasizing the positive impact of his transformation on himself and others. Mnemonic Magnetic Memory Methods & Podcasting: Explaining how GB utilizes Mnemonic Magnetic Memory Methods in my podcasting routine. Describing specific techniques GB employs e.g., visualization, keyword associations, storytelling. Discussing how these methods enhance your creativity, memory, and overall life experience. Grandpa Bill suggest revisiting the previous podcast episode relating to this topic: Encouraging listeners to explore Heart-Brain Coherence techniques. Suggesting you ALL revisit "A Christmas Carol" with a new perspective. Inviting listeners to share their own stories of transformation and personal growth. Mnemonic Magnetic Memory Techniques to Enhance Delivery: Visualization: Imagine yourself as Magoo, experiencing the ghost visitations and the subsequent transformation. Linking key concepts e.g., "Scrooge," "Heart-Brain Coherence," "2025 to vivid images & memorable stories. Storytelling: Weave your own personal story ,making it more relatable and engaging. Repetition: Repeat key phrases and concepts throughout the day to reinforce their importance. Mind Mapping: Creating a visual representation of the episode's structure and key ideas to aid in recall and delivery. By incorporating these techniques and focusing on the core message of "A Christmas Carol," you can create a compelling and insightful podcast episode that resonates with your audience. *COMMUNITY ADVOCACY-Speaking with passion and authenticity. Maintaining a HEALTHY conversational tone. Using clear and Concise language. Engaging with our audience through questioning and promoting interactive elements.

Listen to today's podcast... 1-519-527……. I use to be able to remember my friends birthdays, their phone numbers and the good times that we had together. Now, I find myself forgetting even my family's birth dates, their phone numbers and who I met yesterday. I blame it on aging, but in reality, it is not really so much about aging, as it is about being so busy that I don't take the time to file the information away. Take One Action Today To Build Your #Resiliency!      So here are Today's Tips For Building Resiliency Celebrating Good Memory Day: A good memory is nurtured by a healthy, common sense lifestyle. This requires a healthy body, mind and spirit. Participate in activities that stimulate your brain, such as reading, crossword puzzles, playing cards, and other mental exercises. Be social. Maintaining a network of friends will increase your overall level of brain stimulation. Exercise daily. Physical activity significantly lessens the chance of cardiovascular complications that could cause dementia. Manage stress through techniques such as relaxation, meditation and yoga. Finally, Find a healthy work-life balance. Learn to slow down and be in the moment. One of our biggest fears as we age is losing our memory. By taking care of ourselves and by learning to slow the chaos down, we allow our brains to access our memories more effectively and efficiently. By The Way…Good Memory Day was two days ago! If you like today's wellness tips, let me know. You can leave me a review on amazon or through your #alexa app. Looking for more tips to build your resiliency? Look for my book on Amazon called Stress Out. 52 Weeks To Letting More Life In #mentalhealth #hr

Journalist Johnny Vedmore joins the program to discuss the likely plans being laid by the globalists technocrats. He describes a future that is both hopeful and daunting. We discuss what humanity can do to plan and create a beneficial environment for all mankind as technology changes every aspect of our lives.You can follow Johnny Vedmore at https://Newspaste.com

Thanks to our Partners, NAPA TRACS, and Today's Class Join Carm Capriotto and a panel of experts—Joe Marconi, Dan Buss, and Nick Salas—as they delve into the intricacies of selling your automotive repair business. This insightful episode covers everything from preparing your business for sale and understanding valuations to structuring deals and ensuring clean financials. Learn from seasoned shop owners about succession planning, transparent communication with employees, and navigating the emotional and professional challenges of ownership transitions. Whether it's asset vs. stock sales, working with valuation experts, or addressing staff concerns, this discussion equips you with the knowledge to maximize your business's value and ensure a smooth sale. Joe Marconi, Executive Council Member, Elite Worldwide. Auto Shop Owner. Joe's Episodes HERE. Dan Buss, Elite Worldwide. Nick Sallas, Sallas Auto Repair, Kansas City Show Notes Watch Full Video Episode Importance of Transparency (00:02:18) Joe Marconi on Readiness (00:03:13) Succession Planning (00:05:16) Successor Challenges (00:06:40) Selling Experience (00:08:11) Valuation Discussion (00:09:51) Multiple Valuation Explanation (00:10:37) Advice on Business Preparation (00:12:18) Challenges of Selling a Business (00:13:23) Cultural Implications of Cash Transactions (00:14:43) Building Generational Wealth (00:16:25) Understanding Succession Planning (00:17:03) Emergency Plans in Business (00:20:37) Importance of Professional Advisors (00:22:34) Emotional Impact of Selling a Business (00:28:43) Contracts for Key Employees (00:32:05) Transparency in Hiring (00:33:07) Interview Questions for Potential Hires (00:34:15) Structuring Business Sales (00:35:38) Maintaining a Business Plan (00:37:12) Dealing with Tire Kickers (00:38:04) Evaluating Business Offers (00:39:19) Importance of Clean Financials (00:40:22) Value of Independence in Business (00:41:21) Goals for Business Sellability (00:42:32) Preparation for Selling (00:43:08) Maximizing Business Value (00:43:54) Purpose and Succession Planning (00:45:26) Thanks to our Partner, NAPA TRACS NAPA TRACS will move your shop into the SMS fast lane with onsite training and six days a week of support and local representation. Find NAPA TRACS on the Web at http://napatracs.com/ Thanks to our Partner, Today's Class Optimize training with Today's Class: In just 5 minutes daily, boost knowledge retention and improve team performance. Find Today's Class on the web at

This Podcast Is Episode 611, And It's About The High Cost Of Not Keeping Up With Your Bookkeeping If you ask 100 business owners what they like least about running a business, bookkeeping will likely rank high. It's an annoying and frustrating chore that takes up much time and is easy to put off until tomorrow.   Avoiding your bookkeeping is dangerous, however. Not knowing your construction company's financial situation can result in missteps that could ultimately cost you your business.   When starting bookkeeping as a construction business owner is challenging, a good first step is to break the process down into manageable tasks.   Here are a few tips to help get you started: 1. Set up a simple system Choose an accounting method and set up a basic system, whether a spreadsheet or accounting software tailored for construction businesses. 2. Gather your documents Collect all necessary financial documents such as invoices, receipts, bank statements, and payroll records. Organizing these into folders can make the process less overwhelming. 3. Focus on one area at a time Instead of tackling everything at once, concentrate on one aspect, like tracking expenses or invoicing, until you feel comfortable before moving to the next. 4. Schedule regular time for bookkeeping Setting aside a specific time each week for bookkeeping tasks can help make it a routine and prevent it from piling up. 5. Seek help when needed If you're feeling stuck, consider hiring a bookkeeper or accountant with experience in the construction industry. They can help you set up your system and teach the essentials, providing much-needed support in this challenging task. Take small, consistent steps to gradually build your bookkeeping skills and confidence. By taking control of your bookkeeping, you're empowering yourself to make informed decisions about your business. What happens then if you fail to do so? Here are three costly consequences of not keeping up with your bookkeeping: 1. You'll make poor decisions You can only make informed decisions about your business when you have a complete picture of your current financial situation, including how much money is in your accounts, what your cash flow forecast predicts, and how much money you owe. Knowing when you can afford to spend money or need to hold back is much more challenging without that information. Without proper bookkeeping, your decisions will be based on how you think things are going, which isn't always accurate. You may have just finished a good month and decide it's time to hire new employees, only to find out you don't have enough money in the bank to pay them. In the long run, waiting three months to hire employees might be more profitable, but you won't know that because your books aren't up-to-date. Maintaining your books ensures that you have your company's full financial picture available so you can make smart decisions. 2. You'll make financial mistakes Your employees, contractors, and lenders all rely on you to make your payments on time, every time. Payroll itself requires considerable attention to ensure your employees receive their benefits adequately. Not keeping track of your financial books can result in expensive errors, including missed benefits, bills not being paid on time, or over- or under-payments. This could cost you extra in fees for late payments or rushed payments, which also affects your books. In addition to all this, financial mistakes can lead to a lack of trust. You need a trusting relationship with your employees, contractors, and lenders, and payment errors can quickly erode that relationship. 3. You'll lose money In addition to losing money in unnecessary late fees and payment charges, not keeping track of your books can result in lost money that your business desperately needs. You won't know which of your clients or customers aren't paying you on time, which means you can't follow up with them or add interest charges for their late payments. You could be paying too much in expenses, and if you don't reconcile your books, you'll have no idea that money is being wasted. You may have purchased a software program to enhance productivity in the early days of your business. You may have stopped using it but forgot to cancel it, so each month for the past few years, you've been paying for a service you don't use. Those payments add up and affect your overall financial position. Why outsource your construction bookkeeping to us - we might be the help you need Flat Fee No Hourly Rate Surprises You don't have to pay for payroll taxes, workers' compensation insurance, health and other benefits, or office expenses. We will work within your budget, so there are no surprises. Our services are usually cheaper than hiring a qualified employee, and you can choose an hourly or flat fee. Our contract has no time minimum time commitment clause. You have our service for as long as you need it. There is nothing to lose. Quality & Experience We pride ourselves on employing the highest quality bookkeeping professionals and ProAdvisors. Our employees have passed our extensive test, a thorough background check, and a personality screening process. Most of our employees have over 10,000 hours of bookkeeping experience. This experience level is difficult to find when seeking a part-time employee. Professionalism As non-employees, we can give helpful, honest advice on improving your procedures and overall efficiency. Most employees want to fill their time simply and are resistant to change.  Final thoughts Bookkeeping might be many entrepreneurs' least enjoyable task, but it's essential. If you find yourself putting off or dreading it, it's a good idea to look into hiring someone to do it for you. Construction Bookkeepers are trained and knowledgeable in the process, and they can save you valuable time and money in the long run. Otherwise, be prepared to set aside time regularly to do your books yourself, and don't let yourself put the task off. It's too critical to the future of your business. Want to get your books in order without adding more work to your plate? Contact us today. About The Author: Sharie DeHart, QPA, is the co-founder of Business Consulting And Accounting in Lynnwood, Washington. She is the leading expert in managing outsourced construction bookkeeping and accounting services companies and cash management accounting for small construction companies across the USA. She encourages Contractors and Construction Company Owners to stay current on their tax obligations and offers insights on managing the remaining cash flow to operate and grow their construction company sales and profits so they can put more money in the bank. Call 1-800-361-1770 or sharie@fasteasyaccounting.com

Gut, Food, & Health series   Episode Description: “Your taste buds have a different agenda than your mind and your gut. They're not connected in congruence all the time. So what tastes good in your mouth, is not necessarily what your gut or your brain needs.” —Dr. Edison de Mello    Your gut is the gateway to your overall health and well-being. Did you know that the gut-brain connection can significantly influence your mood, cognitive function, and immune system? Maintaining a balanced gut microbiome is crucial for optimizing both physical and mental wellness. Dr. Edison de Mello MD, PhD, is a renowned expert in the field of integrative medicine. As the Founder and Chief Medical Officer of the Akasha Center for Integrative Medicine, he seamlessly blends cutting-edge Western medical practices with the wisdom of Eastern holistic approaches to provide personalized, comprehensive care to his patients. Discover the profound impact of food on gut health, the challenges of implementing dietary changes, and the importance of tailored solutions as Dr. de Mello and Justine Reichman dive deep into the gut health revolution. Meet Dr. de Mello: Dr. Edison de Mello, MD, PhD is the founder and Chief Medical Officer of the Akasha Center for Integrative Medicine. He is a board-certified integrative physician and a licensed psychotherapist. Dr. de Mello completed his residency at the Albert Einstein College of Medicine at Beth Israel Medical Center in New York City, where he trained in a biopsychosocial model and integrated complementary medicine into Family Medicine. Inspired by his grandmother, Nana, who practiced natural healing, Dr. de Mello's approach combines Western and Eastern medicine, focusing on treating the mind, body, and spirit. He has written several articles and contributed to Dr. Andrew Weil's upcoming book on the microbiome and food addiction. Dr. de Mello is also on the advisory board of several organizations and a member of various professional associations. Website  Instagram Facebook YouTube X   Connect with NextGen Purpose: Website Facebook Instagram LinkedIn YouTube Episode Highlights: 01:13 Food and Gut Health 04:46 Mindfulness and Food Insensitivity   07:33 Allergy and Intolerance Test 13:59 Tailoring Dietary Advice and Personal Needs 16:45 The Role of Medical Education in Nutrition 20:50 Navigating Global Health    

SUMMARY In this episode, the hosts discuss the challenges of injury recovery for aging martial artists, sharing personal experiences and insights on how the body changes with age. They emphasize the importance of taking injuries seriously and exploring various recovery methods. In this conversation, the hosts discuss the challenges and strategies of training in martial arts while dealing with injuries. They share personal experiences and emphasize the importance of adapting training methods, maintaining communication with instructors, and learning from others who have faced similar challenges. The discussion highlights the mental resilience required to continue training despite physical limitations and the supportive role of the martial arts community in recovery. TAKEAWAYS Injury recovery is a significant concern for aging martial artists. The body heals differently as we age, often taking longer to recover. It's essential to take all injuries seriously, regardless of age. Personal experiences with injuries can provide valuable insights for others. Exploring various recovery methods can aid in healing. Maintaining a proactive approach to health can prevent future injuries. Understanding the physical changes that come with age is important for martial artists. It's important to adapt training methods during recovery. Communication with instructors about injuries is crucial. Mental resilience is key when facing physical limitations. Upper body training can still be effective during lower body injuries. Learning from others' experiences can provide valuable insights. Honesty in training helps instructors accommodate students' needs. Injured students can still contribute to the dojo environment. Practicing forms verbally can aid in maintaining skills during recovery. Injuries can be an opportunity for personal growth and learning.

How can triathletes make the most of the off-season without falling into the trap of excessive volume training? Coach Patrick is here to flip the script on traditional winter workouts and set you on a smarter path for the upcoming season. Discover why avoiding peer pressure and making informed training choices can make you the sharpest and fastest athlete come race day. Maintaining the same workout routine year-round might be a recipe for stagnation, but winter offers a golden opportunity for strategic changes. We unpack the importance of varying workout routines and highlight the need for safe indoor alternatives during harsh conditions. Plus, we explain why sleep should become your new best friend during these colder months, helping you recharge and optimize your performance. Fuel your body right and break free from monotony with diverse training activities this winter. From workout nutrition tips to the benefits of strength training, we've got the insights you need to boost your endurance. Explore how incorporating activities like hiking or rowing can freshen up your routine, and learn why winter is the perfect time to focus on body composition and gear upgrades. Coach Patrick also shares resources from Endurance Station US, ensuring you have everything you need to train smartly and safely.

In this episode, Tiffany Grant and Rick Yvanovich discuss the concept of kaizen, which translates to "change for good. " Kaizen emphasizes continuous improvement in processes and personal growth. Rick explains how this Japanese philosophy, popularized by Toyota, can significantly enhance business operations and personal development. Tune in to learn how incorporating Kaizen can lead to lifelong learning, adaptability, and resilience.Check out the full show notes: https://moneytalkwitht.com/podcast-show-notes/kaizen-for-business/Takeaways Kaizen, which means constant improvement, emphasizes the importance of lifelong learning for personal and professional growth. Businesses should focus on empowering employees to embrace continuous skills acquisition and personal development every day. Utilizing technology effectively helps streamline processes, making it essential for modern businesses to adapt and improve. An infinite mindset encourages ongoing self-improvement and a commitment to learning new skills throughout life. Reflecting on our actions and knowledge allows us to adapt and enhance our understanding over time. Maintaining an open mind is crucial; we must be willing to let go of old beliefs when new information arises. Resources Mentioned (Affiliate Links)Rick Yvanovich's book, Business as UnusualSimon Sinek's book, The Infinite GameCarol Dweck's book, Mindset: The New Psychology of SuccessConnect with Rick YvanovichWebsite: rickyvanovich.comTwitter: @RickYvanovichConnect with Tiffany GrantWebsite: Money Talk with TiffTwitter: @MoneyTalkWithTInstagram: @MoneyTalkWithTFacebook: Money Talk with TiffThank you for tuning into this episode of Money Talk With Tiff. Join us every Thursday for new insights and expert advice on financial and business growth. For more episodes, visit moneytalkwitht.com. Remember, spend wise by spending less than you make.Be sure to subscribe, rate, and leave a review if you enjoyed this episode!Support this PodcastCopyright 2025 Tiffany Grant

In this episode, Steve Fretzin and Justin Weinstein discuss:Importance of cultivating strong client relationships in the legal fieldEffective strategies for scaling and growing a law practiceCreating a positive and sustainable workplace cultureProactive client engagement and community involvement in legal services Key Takeaways:Assigning a designated client relationship manager ensures continued connection and personalized care for clients even years after a case is resolved.Proactively educating and engaging with the community helps individuals prepare for potential legal situations, rather than reacting to crises.Treating the workplace as a second home and focusing on employees' personal and professional growth reduces turnover and fosters long-term commitment.Maintaining a strong cash flow and hiring with a focus on ROI, alongside leveraging relationships, are critical to doubling or expanding the size of a law firm. "Failures are learning opportunities, and really, there is no such thing as failure if you view it that way. You're still here, still alive, and still able to make better and better decisions while improving. That's what truly successful people do." —  Justin Weinstein Got a challenge growing your law practice? Email me at steve@fretzin.com with your toughest question, and I'll answer it live on the show—anonymously, just using your first name! Thank you to our Sponsors!Rankings.io: https://rankings.io/Rainmakers Roundtable: https://www.fretzin.com/lawyer-coaching-and-training/peer-advisory-groups/ Episode References: Never Eat Alone by Keith Ferrazzi and Tahl Raz: https://www.amazon.com/Never-Eat-Alone-Expanded-Updated/dp/0385346654 About Justin Weinstein: Justin Weinstein, Founding Partner of the Weinstein Legal Team, earned his Juris Doctor from Nova Southeastern University, joined the Florida Bar in 2012, and since establishing his Fort Lauderdale practice in 2016, has expanded to West Palm Beach, Orlando, and Naples, representing medical professionals treating car accident victims while fostering connections across South Florida and the Treasure Coast, with a focus on personal injury litigation, community involvement, client relationships, and accessible advocacy. Connect with Justin Weinstein:  Website: https://www.thelawofwe.com/Email: justin@weinstein-legal.comLinkedIn: https://www.linkedin.com/in/justinpweinstein/ & https://www.linkedin.com/company/weinsteinlegalteam/Instagram: https://www.instagram.com/jpweinstein & https://www.instagram.com/weinsteinlegalteam/ Connect with Steve Fretzin:LinkedIn: Steve FretzinTwitter: @stevefretzinInstagram: @fretzinsteveFacebook: Fretzin, Inc.Website: Fretzin.comEmail: Steve@Fretzin.comBook: Legal Business Development Isn't Rocket Science and more!YouTube: Steve FretzinCall Steve directly at 847-602-6911  Audio production by Turnkey Podcast Productions. You're the expert. Your podcast will prove it. 

Paul Frazee is the CTO of Bluesky. He previously worked on the Beaker browser and the peer-to-peer social media protocol Secure Scuttlebutt. Paul discusses how Bluesky and ATProto got started, scaling up a social media site, what makes ATProto decentralized, lessons ATProto learned from previous peer-to-peer projects, and the challenges of content moderation. Episode transcript available here. My Bluesky profile. -- Related Links Bluesky ATProtocol ATProto for distributed systems engineers Bluesky and the AT Protocol: Usable Decentralized Social Media Decentralized Identifiers (DIDs) ActivityPub Webfinger Beaker web browser Secure Scuttlebutt -- Transcript You can help correct transcripts on GitHub. [00:00:00] Jeremy: Today I am talking to Paul Frazee. He's the current CTO of bluesky, and he previously worked on other decentralized applications like Beaker and Secure Scuttlebutt. [00:00:15] Paul: Thanks for having me. What's bluesky [00:00:16] Jeremy: For people who aren't familiar with bluesky, what is it? [00:00:20] Paul: So bluesky is an open social network, simplest way to put it, designed in particular for high scale. That's kind of one of the big requirements that we had when we were moving into it. and it is really geared towards making sure that the operation of the social network is open amongst multiple different organizations. [00:00:44] So we're one of the operators, but other folks can come in, spin up the software, all the open source software, and essentially have a full node with a full copy of the network active users and have their users join into our network. And they all work functionally as one shared application. [00:01:03] Jeremy: So it, it sounds like it's similar to Twitter but instead of there being one Twitter, there could be any number and there is part of the underlying protocol that allows them to all connect to one another and act as one system. [00:01:21] Paul: That's exactly right. And there's a metaphor we use a lot, which is comparing to the web and search engines, which actually kind of matches really well. Like when you use Bing or Google, you're searching the same web. So on the AT protocol on bluesky, you use bluesky, you use some alternative client or application, all the same, what we're we call it, the atmosphere, all one shared network, [00:01:41] Jeremy: And more than just the, the client. 'cause I think sometimes when people think of a client, they'll think of, I use a web browser. I could use Chrome or Firefox, but ultimately I'm connecting to the same thing. But it's not just people running alternate clients, right? [00:01:57] Paul: Their own full backend to it. That's right. Yeah. Yeah. The anchoring point on that being the fire hose of data that runs the entire thing is open as well. And so you start up your own application, you spin up a service that just pipes into that fire hose and taps into all the activity. History of AT Protocol [00:02:18] Jeremy: Talking about this underlying protocol maybe we could start where this all began so people get some context for where this all came from. [00:02:28] Paul: For sure. All right, so let's wind the clock back here in my brain. We started out 2022, right at the beginning of the year. We were formed as a, essentially a consulting company outside of Twitter with a contract with Twitter. And, uh, our goal was to build a protocol that could run, uh, Twitter, much like the way that we just described, which set us up with a couple of pretty specific requirements. [00:02:55] For one, we had to make sure that it could scale. And so that ended up being a really important first requirement. and we wanted to make sure that there was a strong kind of guarantees that the network doesn't ever get captured by any one operator. The idea was that Twitter would become the first, uh, adopter of the technology. [00:03:19] Other applications, other services would begin to take advantage of it and users would be able to smoothly migrate their accounts in between one or the other at any time. Um, and it's really, really anchored in a particular goal of just deconstructing monopolies. Getting rid of those moats that make it so that there's a kind of a lack of competition, uh, between these things. [00:03:44] And making sure that, if there was some kind of reason that you decided you're just not happy with what direction this service has been going, you move over to another one. You're still in touch with all the folks you were in touch with before. You don't lose your data. You don't lose your, your your follows. Those were the kind of initial requirements that we set out with. The team by and large came from, the decentralized web, movement, which is actually a pretty, large community that's been around since, I wanna say around 2012 is when we first kind of started to form. It got really made more specifically into a community somewhere around 2015 or 16, I wanna say. [00:04:23] When the internet archives started to host conferences for us. And so that gave us kind of a meeting point where all started to meet up there's kind of three schools of thought within that movement. There was the blockchain community, the, federation community, and the peer-to-peer community. [00:04:43] And so blockchain, you don't need to explain that one. You got Federation, which was largely ActivityPub Mastodon. And then peer-to-peer was IPFS, DAT protocol, um, secure scuttlebutt. But, those kinds of BitTorrent style of technologies really they were all kind of inspired by that. [00:05:02] So these three different kind of sub communities we're all working, independently on different ways to attack how to make these open applications. How do you get something that's a high scale web application without one corporation being the only operator? When this team came together in 2022, we largely sourced from the peer-to-peer group of the decentralized community. Scaling limitations of peer-to-peer [00:05:30] Paul: Personally, I've been working in the space and on those kinds of technologies for about 10 years at that stage. And, the other folks that were in there, you know, 5-10 each respectively. So we all had a fair amount of time working on that. And we had really kind of hit some of the limitations of doing things entirely using client devices. We were running into challenges about reliability of connections. Punching holes to the individual device is very hard. Synchronizing keys between the devices is very hard. Maintaining strong availability of the data because people's devices are going off and on, things like that. Even when you're using the kind of BitTorrent style of shared distribution, that becomes a challenge. [00:06:15] But probably the worst challenge was quite simply scale. You need to be able to create aggregations of a lot of behavior even when you're trying to model your application as largely peer wise interactions like messaging. You might need an aggregation of accounts that even exist, how do you do notifications reliably? [00:06:37] Things like that. Really challenging. And what I was starting to say to myself by the end of that kind of pure peer-to-peer stent was that it can't be rocket science to do a comment section. You know, like at some point you just ask yourself like, how, how hard are we willing to work to, to make these ideas work? [00:06:56] But, there were some pretty good pieces of tech that did come out of the peer-to-peer world. A lot of it had to do with what I might call a cryptographic structure. things like Merkel trees and advances within Merkel Trees. Ways to take data sets and reduce them down to hashes so that you can then create nice signatures and have signed data sets at rest at larger scales. [00:07:22] And so our basic thought was, well, all right, we got some pretty good tech out of this, but let's drop that requirement that it all run off of devices. And let's get some servers in there. And instead think of the entire network as a peer-to-peer mesh of servers. That's gonna solve your scale problem. [00:07:38] 'cause you can throw big databases at it. It's gonna solve your availability problems, it's gonna solve your device sync problems. But you get a lot of the same properties of being able to move data sets between services. Much like you could move them between devices in the peer-to-peer network without losing their identifiers because you're doing this in direction of, cryptographic identifiers to the current host. [00:08:02] That's what peer-to-peer is always doing. You're taking like a public key or hash and then you're asking the network, Hey, who has this? Well, if you just move that into the server, you get the same thing, that dynamic resolution of who's your active host. So you're getting that portability that we wanted real bad. [00:08:17] And then you're also getting that kind of in meshing of the different services where each of them is producing these data sets that they can sink from each other. So take peer-to-peer and apply it to the server stack. And that was our kind of initial thought of like, Hey, you know what? This might work. [00:08:31] This might solve the problems that we have. And a lot of the design fell out from that basic mentality. Crytographic identifiers and domain names [00:08:37] Jeremy: When you talk about these cryptographic identifiers, is the idea that anybody could have data about a person, like a message or a comment, and that could be hosted different places, but you would still know which person that originally came from. Is that, is that the goal there? [00:08:57] Paul: That's exactly it. Yeah. Yeah. You wanna create identification that supersedes servers, right? So when you think about like, if I'm using Twitter and I wanna know what your posts are, I go to twitter.com/jeremy, right? I'm asking Twitter and your ID is consequently always bound to Twitter. You're always kind of a second class identifier. [00:09:21] We wanted to boost up the user identifier to be kind of a thing freestanding on its own. I wanna just know what Jeremy's posts are. And then once you get into the technical system it'll be designed to figure out, okay, who knows that, who can answer that for you? And we use cryptographic identifiers internally. [00:09:41] So like all the data sets use these kind of long URLs to identify things. But in the application, the user facing part, we used domain names for people. Which I think gives the picture of how this all operates. It really moves the user accounts up into a free standing first class identifier within the system. [00:10:04] And then consequently, any application, whatever application you're using, it's really about whatever data is getting put into your account. And then that just exchanges between any application that anybody else is using. [00:10:14] Jeremy: So in this case, it sounds like the identifier is some long string that, I'm not sure if it's necessarily human readable or not. You're shaking your head no. [00:10:25] Paul: No. [00:10:26] Jeremy: But if you have that string, you know it's for a specific person. And since it's not really human readable, what you do is you put a layer on top of it which in this case is a domain that somebody can use to look up and find the identifier. [00:10:45] Paul: Yeah, yeah, yeah. So we just use DNS. Put a TXT record in there, map into that long string, or you could do a .well-known file on a web server if that's more convenient for you. And then the ID that's behind that, the non-human readable one, those are called DIDs which is actually a W3C spec. Those then map to a kind of a certificate. What you call a DID document that kind of confirms the binding by declaring what that domain name should be. So you get this bi-directional binding. And then that certificate also includes signing keys and active servers. So you pull down that certificate and that's how the discovery of the active server happens is through the DID system. What's stored on a PDS [00:11:29] Jeremy: So when you refer to an active server what is that server and what is that server storing? [00:11:35] Paul: It's kinda like a web server, but instead of hosting HTML, it's hosting a bunch of JSON records. Every user has their own document store of JSON documents. It's bucketed into collections. Whenever you're looking up somebody on the network you're gonna get access to that repository of data, jump into a collection. [00:11:58] This collection is their post collection. Get the rkey (Record Key), and then you're pulling out JSON at the end of it, which is just a structured piece of stuff saying here's the CreatedAt, here's the text, here's the type, things like that. One way you could look at the whole system is it's a giant, giant database network. Servers can change, signing keys change, but not DID [00:12:18] Jeremy: So if someone's going to look up someone's identifier, let's say they have the user's domain they have to go to some source, right? To find the user's data. You've mentioned, I think before, the idea that this is decentralized and by default I would, I would picture some kind of centralized resource where I send somebody a domain and then they give me back the identifier and the links to the servers. [00:12:46] So, so how does that work in practice where it actually can be decentralized? [00:12:51] Paul: I mentioned that your DID that non-human readable identifier, and that has that certificate attached to it that lists servers and signing keys and things like that. [00:13:00] So you're just gonna look up inside that DID document what that server is your data repository host. And then you contact that guy and say, all right, I'm told you're hosting this thing. Here's the person I'm looking for, hand over the hand over the data. It's really, you know, pretty straightforward. [00:13:18] The way that gets decentralized is by then to the fact that I could swap out that active server that's in my certificate and probably wanna rotate the signing keys 'cause I've just changed the, you know. I don't want to keep using the same signing keys as I was using previously because I just changed the authority. [00:13:36] So that's the migration change, change the hosting server, change out the signing keys. Somebody that's looking for me now, they're gonna load up my document, my DID document. They're gonna say, okay, new server, new keys. Pull down the data. Looks good, right? Matches up with the DID doc. [00:13:50] So that's how you get that level of portability. But when those changes happen, the DID doesn't change, right? The DID document changes. So there's the level of indirection there and that's pretty important because if you don't have a persistent identifier whenever you're trying to change out servers, all those backlinks are gonna break. [00:14:09] That's the kind of stuff that stops you from being able to do clean migrations on things like web-based services. the only real option is to go out and ask everybody to update their data. And when you're talking about like interactions on the social network, like people replying to each other, there's no chance, right? [00:14:25] Every time somebody moves you're gonna go back and modify all those records. You don't even control all the records from the top down 'cause they're hosted all over the web. So it's just, you can't do it. Generally we call this account portability, that you're kinda like phone number portability that you can change your host, but, so that part's portable, but the ID stays the same. [00:14:45] And keeping that ID the same is the real key to making sure that this can happen without breaking the whole system. [00:14:52] Jeremy: And so it, it sounds like there's the decentralized id, then there's the decentralized ID document that's associated with that points you to where the actual location of your, your data, your posts, your pictures and whatnot. but then you also mentioned that they could change servers. [00:15:13] So let's say somebody changes where their data is, is stored, that would change the servers, I guess, in their document. But [00:15:23] then how do all of these systems. Know okay. I need to change all these references to your old server, to these new servers, [00:15:32] Paul: Yeah. Well, the good news is that you only have to, you, you got the public data set of all the user's activity, and then you have like internal caches of where the current server is. You just gotta update those internal caches when you're trying to contact their server. Um, so it's actually a pretty minimal thing to just like update like, oh, they moved, just start talking to update my, my table, my Redis, that's holding onto that kind of temporary information, put it on ttl, that sort of thing. Most communication won't be between servers, it will be from event streams [00:16:01] Paul: And, honestly, in practice, a fair amount of the system for scalability reasons doesn't necessarily work by servers directly contacting each other. It's actually a little bit more like how, I told you before, I'm gonna use this metaphor a lot, the search engines with the web, right? What we do is we actually end up crawling the repositories that are out in the world and funneling them into event streams like a Kafka. And that allows the entire system to act like a data processing pipeline where you're just tapping into these event streams and then pushing those logs into databases that produce these large scale aggregations. [00:16:47] So a lot of the application behavior ends up working off of these event logs. If I reply to somebody, for instance, I don't necessarily, it's not, my server has to like talk to your server and say, Hey, I'm replying to you. What I do is I just publish a reply in my repository that gets shot out into the event logs, and then these aggregators pick up that the reply got created and just update their database with it. [00:17:11] So it's not that our hosting servers are constantly having to send messages with each other, you actually use these aggregators to pull together the picture of what's happening on the network. [00:17:22] Jeremy: Okay, so like you were saying, it's an event stream model where everybody publishes the events the things that they're doing, whether that's making a new post, making a reply, that's all being posted to this event stream. And then everybody who provides, I'm not sure if instances is the right term, but an implementation of the atmosphere protocol (Authenticated Transfer protocol). [00:17:53] They are listening for all those changes and they don't necessarily have to know that you moved servers because they're just listening for the events and you still have the same identifier. [00:18:10] Paul: Generally speaking. Yeah. 'cause like if you're listening to one of these event streams what you end up looking for is just the signature on it and making sure that the signature matches up. Because you're not actually having to talk to their live server. You're just listening to this relay that's doing this aggregation for you. [00:18:27] But I think actually to kind of give a little more clarity to what you're talking about, it might be a good idea to refocus how we're talking about the system here. I mentioned before that our goal was to make a high scale system, right? We need to handle a lot of data. If you're thinking about this in the way that Mastodon does it, the ActivityPub model, that's actually gonna give you the wrong intuition. Designing the protocol to match distributed systems practices (Event sourcing / Stream processing) [00:18:45] Paul: 'cause we chose a dramatically different system. What we did instead was we picked up, essentially the same practices you're gonna use for a data center, a high scale application data center, and said, all right, how do you tend to build these sorts of things? Well, what you're gonna do is you're gonna have, multiple different services running different purposes. [00:19:04] It gets pretty close to a microservices approach. You're gonna have a set of databases, and then you're going to, generally speaking for high scale, you're gonna have some kind of a kafka, some kind of a event log that you are tossing changes about the state of these databases into. And then you have a bunch of secondary systems that are tapping into the event log and processing that into, the large scale, databases like your search index, your, nice postgres of user profiles. [00:19:35] And that makes sure that you can get each of these different systems to perform really well at their particular task, and then you can detach them in their design. for instance, your primary storage can be just a key value store that scales horizontally. And then on the event log, you, you're using a Kafka that's designed to handle. [00:19:58] Particular semantics of making sure that the messages don't get dropped, that they come through at a particular throughput. And then you're using, for us, we're using like ScyllaDB for the big scale indexes that scales horizontally really well. So it's just different kind of profiles for different pieces. [00:20:13] If you read Martin Kleppman's book, data Intensive applications I think it's called or yeah. A lot of it gets captured there. He talks a lot about this kind of thing and it's sometimes called a kappa architecture is one way this is described, event sourcing is a similar term for it as well. [00:20:30] Stream processing. That's pretty standard practices for how you would build a traditional high scale service. so if you take, take this, this kind of microservice architecture and essentially say, okay, now imagine that each of the services that are a part of your data center could be hosted by anybody, not just within our data center, but outside of our data center as well and should be able to all work together. [00:20:57] Basically how the AT Proto is designed. We were talking about the data repository hosts. Those are just the primary data stores that they hold onto the user keys and they hold onto those JSON records. And then we have another service category we call Relay that just crawls those data repositories and sucks that in that fire hose of data we were talking about that event log. App views pull data from relay and produces indexes and threads [00:21:21] Paul: And then we have what we call app views that sit there and tail the index and tail the log, excuse me, and produce indexes off of it, they're listening to those events and then like, making threads like okay, that guy posted, that guy replied, that guy replied. [00:21:37] That's a thread. They assemble it into that form. So when you're running an application, you're talking to the AppView to read the network, and you're talking to the hosts to write to the network, and each of these different pieces sync up together in this open mesh. So we really took a traditional sort of data center model and just turned it inside out where each piece is a part of the protocol and communicate it with each other and therefore anybody can join into that mesh. [00:22:07] Jeremy: And to just make sure I am tracking the data repository is the data about the user. So it has your decentralized identifier, it has your replies, your posts, And then you have a relay, which is, its responsibility, is to somehow find all of those data repositories and collect them as they happen so that it can publish them to some kind of event stream. [00:22:41] And then you have the AppView which it's receiving messages from the relay as they happen, and then it can have its own store and index that for search. It can collect them in a way so that it can present them onto a UI. That's sort of thing that's the user facing part I suppose. [00:23:00] Paul: Yeah, that's exactly it. And again, it's, it's actually quite similar to how the web works. If you combine together the relay and the app view, you got all these different, you know, the web works where you got all these different websites, they're hosting their stuff, and then the search engine is going around, aggregating all that data and turning it into a search experience. [00:23:19] Totally the same model. It's just being applied to, more varieties of data, like structured data, like posts and, and replies, follows, likes, all that kinda stuff. And then instead of producing a search application at the end. I mean, it does that too, but it also produces a, uh, you know, timelines and threads and, um, people's profiles and stuff like that. [00:23:41] So it's actually a pretty bog standard way of doing, that's one of the models that we've seen work for large scale decentralized systems. And so we're just transposing it onto something that kind of is more focused towards social applications [00:23:58] Jeremy: So I think I'm tracking that the data repository itself, since it has your decentralized identifier and because the data is cryptographically signed, you know, it's from a specific user. I think the part that I am still not quite sure about is the relays. I, I understand if you run all the data repositories, you know where they are, so you know how to collect the data from them. [00:24:22] But if someone's running another system outside of your organization, how do they find, your data repositories? Or do they have to connect to your relay? What's the intention for that? Data hosts request relays to pull their data [00:24:35] Paul: That logic runs, again, really similar to how search engines find out about websites. So there is actually a way for, one of these, data hosts to contact Relay and say, Hey, I exist. You know, go ahead and get my stuff. And then it'll be up to the relay to decide like if they want it or not. [00:24:52] Right now, generally we're just like, yeah, you know, we, we want it. But as you can imagine, as the thing matures and gets to higher scale, there might be some trust kind of things to worry about, you know? So that's kind of the naive operation that currently exists. But over time as the network gets bigger and bigger, it'll probably involve some more traditional kind of spiraling behaviors because as more relays come into the system, each of these hosts, they're not gonna know who to talk to. Relays can bootstrap who they know about by talking to other relays [00:25:22] Paul: You're trying to start a new relay. What they're gonna do is they're going to discover all of the different users that exist in the system by looking at what data they have to start with. Probably involve a little bit of a manual feeding in at first, whenever I'm starting up a relay, like, okay, there's bluesky's relay. [00:25:39] Lemme just pull what they know. And then I go from there. And then anytime you discover a new user you don't have, you're like, oh, I wanna look them up. Pull them into the relay too. Right. So there's a, pretty straightforward, discovery process that you'll just have to bake into a relay to, to make sure you're calling as much the network as possible. ActivityPub federation vs AT Proto [00:25:57] Jeremy: And so I don't think we've defined the term federation, but maybe you could explain what that is and if that is what this is. [00:26:07] Paul: We are so unsure. [00:26:10] Jeremy: Okay. [00:26:11] Paul: Yeah. This has jammed is up pretty bad. Um, because I think everybody can, everybody pretty strongly agrees that ActivityPub is federation, right? and ActivityPub kind of models itself pretty similarly to email in a way, like the metaphors they use is that there's inboxes and outboxes and, and every ActivityPub server they're standing up the full vertical stack. [00:26:37] They set up, the primary hosting, the views of the data that's happening there. the interface for the application, all of it, pretty traditional, like close service, but then they're kind of using the perimeter. they're making that permeable by sending, exchanging, essentially mailing records to each other, right? [00:26:54] That's their kind of logic of how that works. And that's pretty much in line with, I think, what most people think of with Federation. Whereas what we're doing isn't like that we've cut, instead of having a bunch of vertical stacks communicating horizontally with each other, we kind of sliced in the other direction. [00:27:09] We sliced horizontally into, this microservices mesh and have all the different, like a total mix and match of different microservices between different operators. Is that federation? I don't know. Right. we tried to invent a term, didn't really work, you know, At the moment, we just kind of don't worry about it that much, see what happens, see what the world sort of has to say to us about it. [00:27:36] and beyond that, I don't know. [00:27:42] Jeremy: I think people probably are thinking of something like, say, a Mastodon instance when you're, when you're talking about everything being included, The webpage where you view the posts, the Postgres database that's keeping the messages. [00:28:00] And that same instance it's responsible for basically everything. [00:28:06] Paul: mm-Hmm [00:28:06] Jeremy: And I believe what you're saying is that the difference with, the authenticated transfer protocol, is that the [00:28:15] Paul: AT Protocol, Yep. [00:28:17] Jeremy: And the difference there is that you've, at the protocol level, you've split it up into the data itself, which can be validated completely separately from other parts of the system. [00:28:31] You could have the JSON files on your hard drive and somebody else can have that same JSON file and they would know that who the user is and that these are real things that user posted. That's like a separate part. And then the relay component that looks for all these different repositories that has people's data, that can also be its own independent thing where its job is just to output events. [00:29:04] And that can exist just by itself. It doesn't need the application part, the, the user facing part, it can just be this event stream on itself. and that's the part where it sounds like you can make decisions on who to, um, collect data from. I guess you have to agree that somebody can connect to you and get the users from your data repositories. [00:29:32] And likewise, other people that run relays, they also have to agree to let you pull the users from theirs. [00:29:38] Paul: Yeah, that's right. Yeah. [00:29:41] Jeremy: And so I think the Mastodon example makes sense. And, but I wonder if the underlying ActivityPub protocol forces you to use it in that way, in like a whole full application that talks to another full application. [00:29:55] Or is it more like that's just how people tend to use it and it's not necessarily a characteristic of the protocol. [00:30:02] Paul: Yeah, that's a good question actually. so, you know, generally what I would say is pretty core to the protocol is the expectations about how the services interact with each other. So the mailbox metaphor that's used in ActivityPub, that design, if I reply to you, I'll update my, local database with what I did, and then I'll send a message over to your server saying, Hey, by the way, add this reply. [00:30:34] I did this. And that's how they find out about things. That's how they find out about activity outside of their network. that's the part that as long as you're doing ActivityPub, I suspect you're gonna see reliably happening. That's that, I can say for sure that's a pretty tight requirement. [00:30:50] That's ActivityPub. If you wanted to split it up the way we're talking about, you could, I don't know, I don't know if you necessarily would want to. Because I don't know. That's actually, I think I'd have to dig into their stack a little bit more to see how meaningful that would be. I do know that there's some talk of introducing a similar kind of an aggregation method into the ActivityPub world which I believe they're also calling a relay and to make things even more complicated. [00:31:23] And NOSTR has a concept of a relay. So these are three different protocols that are using this term. I think you could do essentially what a search engine does on any of these things. You could go crawling around for the data, pull them into a fire hose, and then, tap into that aggregation to produce, bigger views of the network. [00:31:41] So that principle can certainly apply anywhere. AT Protocol, I think it's a little bit, we, we focused in so hard from that on that from the get go, we focus really hard on making sure that this, the data is, signed at rest. That's why it's called the authenticated transfer protocol. And that's a nice advantage to have when you're running a relay like this because it means that you don't have to trust the relay. [00:32:08] Like generally speaking, when I look at results from Google, you know, I'm trusting pretty well that they're accurately reflecting what's on the website, which is fine. You know, there's, that's not actually a huge risk or anything. But whenever you're trying to build entire applications and you're using somebody else's relay, you could really run into things where they say like, oh, you know what Paul tweeted the other day, you know, I hate dogs. [00:32:28] They're like, no, I didn't. That's a lie, right? You just sneak in Little lies like that over a while, it becomes a problem. So having the signatures on the data is pretty important. You know, if you're gonna be trying to get people to cooperate, uh, you gotta manage the trust model. I know that ActivityPub does have mechanisms for signed records. Issuers with ActivityPub identifiers [00:32:44] Paul: I don't know how deep they go if they could fully replace that, that utility. and then Mastodon ActivityPub, they also use a different identifier system that they're actually taking a look at DIDs um, right now, I don't know what's gonna happen there. We're, we're totally on board to, you know, give any kind of insight that we got working on 'em. [00:33:06] But at, at the moment, they use I think it's WebFinger based identifiers they look like emails. So you got host names in there and those identifiers are being used in the data records. So you don't get that continuous identifier. They actually do have to do that hey, I moved update your records sort of thing. [00:33:28] And that causes it to, I mean, it works like decently well, but not as well as it could. They got us to the point where it moves your profile over and you update all the folks that were following you so they can update their follow records, but your posts, they're not coming right, because that's too far into that mesh of interlinking records. [00:33:48] There's just no chance. So that's kind of the upper limit on that, it's a different set of choices and trade-offs. You're always kind of asking like, how important is the migration? Does that work out? Anyway, now I'm just kind of digging into differences between the two here. Issues with an identifier that changes and updating old records [00:34:07] Jeremy: So you were saying that with ActivityPub, all of the instances need to be notified that you've changed your identifier but then all of the messages that they had already received. They don't point to the new identifier somehow. [00:34:24] Paul: Yeah. You run into basically just the practicalities of actual engineering with that is what happens, right? Because if you imagine you got a multimillion user social network. They got all their posts. Maybe the user has like, let's say a thousand posts and 10,000 likes. And that, activity can range back three years. [00:34:48] Let's say they changed their identifier, and now you need to change the identifier of all those records. If you're in a traditional system that's already a tall order, you're going back and rewriting a ton of indexes, Anytime somebody replied to you, they have these links to your posts, they're now, you've gotta update the identifiers on all of those things. [00:35:11] You could end up with a pretty significant explosion of rewrites that would have to occur. Now that's, that's tough. If you're in a centralized model. If you're in a decentralized one, it's pretty much impossible because you're now, when you notify all the other servers like, Hey, this, this changed. How successful are all of them at actually updating that, that those, those pointers, it's a good chance that there's things are gonna fall out of correctness. that's just a reality of it. And if, so, if you've got a, if you've got a mutable identifier, you're in trouble for migrations. So the DID is meant to keep it permanent and that ends up being the anchoring point. If you lose control of your DID well, that's it. Managing signing keys by server, paper key reset [00:35:52] Paul: Your, your account's done. We took some pretty traditional approaches to that, uh, where the signing keys get managed by your hosting server instead of like trying to, this may seem like really obvious, but if you're from the decentralization community, we spend a lot of time with blockchains, like, Hey, how do we have the users hold onto their keys? [00:36:15] You know, and the tooling on that is getting better for what it's worth. We're starting to see a lot better key pair management in like Apple's ecosystem and Google's ecosystem, but it's still in the range of like, nah, people lose their keys, you know? So having the servers manage those is important. [00:36:33] Then we have ways of exporting paper keys so that you could kind of adversarially migrate if you wanted to. That was in the early spec we wanted to make sure that this portability idea works, that you can always migrate your accounts so you can export a paper key that can override. [00:36:48] And that was how we figured that out. Like, okay, yeah, we don't have to have everything getting signed by keys that are on the user's devices. We just need these master backup keys that can say, you know what? I'm done with that host. No matter what they say, I'm overriding what they, what they think. and that's how we squared that one. [00:37:06] Jeremy: So it seems like one of the big differences with account migration is that with ActivityPub, when you move to another instance, you have to actually change your identifier. [00:37:20] And with the AT protocol you're actually not allowed to ever change that identifier. And maybe what you're changing is just you have say, some kind of a lookup, like you were saying, you could use a domain name to look that up, get a reference to your decentralized identifier, but your decentralized identifier it can never change. [00:37:47] Paul: It, it, it can't change. Yeah. And it shouldn't need to, you know what I mean? It's really a total disaster kind of situation if that happens. So, you know that it's designed to make sure that doesn't happen in the applications. We use these domain name handles to, to identify folks. And you can change those anytime you want because that's really just a user facing thing. [00:38:09] You know, then in practice what you see pretty often is that you may, if you change hosts, if you're using, we, we give some domains to folks, you know, 'cause like not everybody has their own domain. A lot of people do actually, to our surprise, people actually kind of enjoy doing that. But, a lot of folks are just using like paul.bsky.social as their handle. [00:38:29] And so if you migrated off of that, you probably lose that. Like your, so your handle's gonna change, but you're not losing the followers and stuff. 'cause the internal system isn't using paul.bsky.social, it's using that DID and that DID stays the same. Benefits of domain names, trust signal [00:38:42] Jeremy: Yeah. I thought that was interesting about using the domain names, because when you like you have a lot of users, everybody's got their own sub-domain. You could have however many millions of users. Does that become, does that become an issue at some point? [00:39:00] Paul: Well, it's a funny thing. I mean like the number of users, like that's not really a problem 'cause you run into the same kind of namespace crowding problem that any service is gonna have, right? Like if you just take the subdomain part of it, like the name Paul, like yeah, only, you only get to have one paul.bsky.social. [00:39:15] so that part of like, in terms of the number of users, that part's fine I guess. Uh, as fine as ever. where gets more interesting, of course is like, really kind of around the usability questions. For one, it's, it's not exactly the prettiest to always have that B sky.social in there. If we, if we thought we, if we had some kind of solution to that, we would use it. [00:39:35] But like the reality is that, you know, now we're, we've committed to the domain name approach and some folks, you know, they kind of like, ah, that's a little bit ugly. And we're like, yeah that's life. I guess the plus side though is that you can actually use like TLD the domain. It's like on pfrazee.com. [00:39:53] that starts to get more fun. it can actually act as a pretty good trust signal in certain scenarios. for instance, well-known domain names like nytimes.com, strong authentication right there, we don't even need a blue check for it. Uh, similarly the .gov, domain name space is tightly regulated. [00:40:14] So you actually get a really strong signal out of that. Senator Wyden is one of our users and so he's, I think it's wyden.senate.gov and same thing, strong, you know, strong identity signal right there. So that's actually a really nice upside. So that's like positives, negatives. [00:40:32] That trust signal only works so far. If somebody were to make pfrazee.net, then that can be a bit confusing. People may not be paying attention to .com vs .net, so it's not, I don't wanna give the impression that, ah, we've solved blue checks. It's a complicated and multifaceted situation, but, it's got some juice. [00:40:54] It's also kinda nice too, 'cause a lot of folks that are doing social, they're, they've got other stuff that they're trying to promote, you know? I'm pretty sure that, uh, nytimes would love it if you went to their website. And so tying it to their online presence so directly like that is a really nice kind of feature of it. [00:41:15] And tells a I think a good story about what we're trying to do with an open internet where, yeah, everybody has their space on the internet where they can do whatever they want on that. And that's, and then thethese social profiles, it's that presence showing up in a shared space. It's all kind of part of the same thing. [00:41:34] And that that feels like a nice kind of thing to be chasing, you know? And it also kind of speaks well to the naming worked out for us. We chose AT Protocol as a name. You know, we back acronymed our way into that one. 'cause it was a @ simple sort of thing. But like, it actually ended up really reflecting the biggest part of it, which is that it's about putting people's identities at the front, you know, and make kind of promoting everybody from a second class identity that's underneath Twitter or Facebook or something like that. [00:42:03] Up into. Nope, you're freestanding. You exist as a person independently. Which is what a lot of it's about. [00:42:12] Jeremy: Yeah, I think just in general, not necessarily just for bluesky, if people had more of an interest in getting their own domain, that would be pretty cool if people could tie more of that to something you basically own, right? [00:42:29] I mean, I guess you're leasing it from ICANN or whatever, but, [00:42:33] yeah, rather than everybody having an @Gmail, Outlook or whatever they could actually have something unique that they control more or less. [00:42:43] Paul: Yeah. And we, we actually have a little experimental service for registering domain names that we haven't integrated into the app yet because we just kind of wanted to test it out and, and kind of see what that appetite is for folks to register domain names way higher than you'd think we did that early on. [00:43:01] You know, it's funny when you're coming from decentralization is like an activist space, right? Like it's a group of people trying to change how this tech works. And sometimes you're trying to parse between what might come off as a fascination of technologists compared to what people actually care about. [00:43:20] And it varies, you know, the domain name thing to a surprising degree, folks really got into that. We saw people picking that up almost straight away. More so than certainly we ever predicted. And I think that's just 'cause I guess it speaks to something that people really get about the internet at this point. [00:43:39] Which is great. We did a couple of other things that are similar and we saw varied levels of adoption on them. We had similar kinds of user facing, opening up of the system with algorithms and with moderation. And those have both been pretty interesting in and of themselves. Custom feed algorithms [00:43:58] Paul: So with algorithms, what we did was we set that up so that anybody can create a new feed algorithm. And this was kind of one of the big things that you run into whenever you use the app. If you wanted to create a new kind of for you feed you can set up a service somewhere that's gonna tap into that fire hose, right? [00:44:18] And then all it needs to do is serve a JSON endpoint. That's just a list of URLs, but like, here's what should be in that feed. And then the bluesky app will pick that up and, and send that, hydrate in the content of the posts and show that to folks. I wanna say this is a bit of a misleading number and I'll explain why but I think there's about 35,000 of these feeds that have been created. [00:44:42] Now, the reason it's little misleading is that, I mean, not significantly, but it's not everybody went, sat down in their IDE and wrote these things. Essentially one of our users created, actually multiple of our users made little platforms for building these feeds, which is awesome. That's the kinda thing you wanna see because we haven't gotten around to it. [00:44:57] Our app still doesn't give you a way to make these things. But they did. And so lots of, you know, there it is. Cool. Like, one, one person made a kind of a combinatorial logic thing that's like visual almost like scratch, it's like, so if it has this hashtag and includes these users, but not those users, and you're kind of arranging these blocks and that constructs the feed and then probably publish it on your profile and then folks can use it, you know? [00:45:18] And um, so that has been I would say fairly successful. Except, we had one group of hackers do put in a real effort to make a replacement for you feed, like magic algorithmic feed kind of thing. And then they kind of kept up going for a while and then ended up giving up on it. Most of what we see are actually kind of weird niche use cases for feeds. [00:45:44] You get straightforward ones, like content oriented ones like a cat feed, politics feed, things like that. It's great, some of those are using ML detection, so like the cat feed is ML detection, so sometimes you get like a beaver in there, but most of the time it's a cat. And then we got some ones that are kind of a funny, like change in the dynamic of freshness. [00:46:05] So, uh, or or selection criteria, things that you wouldn't normally see. Um, but because they can do whatever they want, you know, they try it out. So like the quiet posters ended up being a pretty successful one. And that one just shows people you're following that don't post that often when they do just those folks. [00:46:21] It ended up being, I use that one all the time because yeah, like they get lost in the noise. So it's like a way to keep up with them. Custom moderation and labeling [00:46:29] Paul: The moderation one, that one's a a real interesting situation. What we did there essentially we wanted to make sure that the moderation system was capable of operating across different apps so that they can share their work, so to speak. [00:46:43] And so we created what we call labeling. And labeling is a metadata layer that exists over the network. Doesn't actually live in the normal data repositories. It uses a completely different synchronization because a lot of these labels are getting produced. It's just one of those things where the engineering characteristics of the labels is just too different from the rest of the system. [00:47:02] So we created a separate synchronization for this, and it's really kind of straightforward. It's, here's a URL and here's a string saying something like NSFW or Gore, or you know, whatever. then those get merged onto the records brought down by the client and then the client, you know, based on the user's preferences. [00:47:21] We'll put like warning screens up, hide it, stuff like that. So yeah, these label streams can then, you know, anybody that's running a moderation service can, you know, are publishing these things and so anybody can subscribe to 'em. And you get that kind of collaborative thing we're always trying to do with this. [00:47:34] And we had some users set up moderation services and so then as an end user you find it, it looks like a profile in the app and you subscribe to it and you configure it and off you go. That one has had probably the least amount of adoption throughout all of 'em. It's you know, moderation. [00:47:53] It's a sticky topic as you can imagine, challenging for folks. These moderation services, they do receive reports, you know, like whenever I'm reporting a post, I choose from all my moderation services who I wanna report this to. what has ended up happening more than being used to actually filter out like subjective stuff is more kind of like either algorithmic systems or what you might call informational. [00:48:21] So the algorithmic ones are like, one of the more popular ones is a thing that's looking for, posts from other social networks. Like this screenshot of a Reddit post or a Twitter post or a Facebook post. Because, which you're kinda like, why, you know, but the thing is some folks just get really tired of seeing screenshots from the other networks. [00:48:40] 'cause often it's like, look what this person said. Can you believe it? You know, it's like, ah. Okay, I've had enough. So one of our users aendra made a moderate service that just runs an ML that detects it, labels it, and then folks that are tired of it, they subscribe to it and they're just hide it, you know? [00:48:57] And so it's like a smart filter kind of thing that they're doing. you know, hypothetically you could do that for things like spiders, you know, like you've got arachniphobia, things like that. that's like a pretty straightforward, kind of automated way of doing it. Which takes a lot of the spice, you know, outta out of running moderation. [00:49:15] So that users have been like, yeah, yeah, okay, we can do that. [00:49:20] Those are user facing ways that we tried to surface the. Decentralized principle, right? And make take advantage of how this whole architecture can have this kind of a pluggability into it. Users can self host now [00:49:33] Paul: But then really at the end of the day, kind of the important core part of it is those pieces we were talking about before, the hosting, the relay and the, the applications themselves, having those be swappable in completely. so we tend to think of those as kind of ranges of infrastructure into application and then into particular client side stuff. [00:49:56] So a lot of folks right now, for instance, they're making their own clients to the application and those clients are able to do customizations, add features, things like that, as you might expect, [00:50:05] but most of them are not running their own backend. They're just using our backend. But at any point, it's right there for you. You know, you can go ahead and, and clone that software and start running the backend. If you wanted to run your own relay, you could go ahead and go all the way to that point. [00:50:19] You know, if you wanna do your own hosting, you can go ahead and do that. Um, it's all there. It's really just kind of a how much effort your project really wants to take. That's the kind of systemically important part. That's the part that makes sure that the overall mission of de monopolizing, social media online, that's where that really gets enforced. [00:50:40] Jeremy: And so someone has their own data repository with their own users and their own relay. they can request that your relay collect the information from their own data repositories. And that's, that's how these connections get made. [00:50:58] Paul: Yeah. And, and we have a fair number of those already. Fair number of, we call those the self hosters right? And we got I wanna say 75 self hoster going right now, which is, you know, love to see that be more, but it's, really the folks that if you're running a service, you probably would end up doing that. [00:51:20] But the folks that are just doing it for themselves, it's kind of the, the nerdiest of the nerds over there doing that. 'cause it doesn't end up showing itself in the, in the application at all. Right? It's totally abstracted away. So it, that, that one's really about like, uh, measure your paranoia kind of thing. [00:51:36] Or if you're just proud of the self-hosting or, or curious, you know, that that's kind of where that sits at the moment. AT Protocol beyond bluesky [00:51:42] Jeremy: We haven't really touched on the fact that there's this underlying protocol and everything we've been discussing has been centered around the bluesky social network where you run your own, instance of the relay and the data repositories with the purpose of talking to bluesky, but the protocol itself is also intended to be used for other uses, right? [00:52:06] Paul: Yeah. It's generic. The data types are set up in a way that anybody can build new data types in the system. there's a couple that have already begun, uh, front page, which is kind of a hacker news clone. There's Smoke Signals, which is a events app. There's Blue Cast, which is like a Twitter spaces, clubhouse kind of thing. [00:52:29] Those are the folks that are kind of willing to trudge into the bleeding edge and deal with some of the rough edges there for pretty I think, obvious reasons. A lot of our work gets focused in on making sure that the bluesky app and that use case is working correctly. [00:52:43] But we are starting to round the corner on getting to a full kind of how to make alternative applications state. If you go to the atproto.com, there's a kind of a introductory tutorial where that actually shows that whole stack and how it's done. So it's getting pretty close. There's a couple of still things that we wanna finish up. [00:53:04] jeremy so in a way you can almost think of it as having an eventually consistent data store on the network, You can make a traditional web application with a relational database, and the source of truth can actually be wherever that data repository is stored on the network. [00:53:24] paul Yeah, that's exactly, it is an eventually consistent system. That's exactly right. The source of truth is there, is their data repo. And that relational database that you might be using, I think the best way to think about it is like secondary indexes or computed indexes, right? They, reflect the source of truth. [00:53:43] Paul: This is getting kind of grandiose. I don't tend to poses in these terms, but it is almost like we're trying to have an OS layer at a protocol level. It's like having your own [00:53:54] Network wide database or network-wide file system, you know, these are the kind of facilities you expect out of a platform like an os And so the hope would be that this ends up getting that usage outside of just the initial social, uh, app, like what we're doing here. [00:54:12] If it doesn't end up working out that way, if this ends up, you know, good for the Twitter style use case, the other one's not so much, and that's fine too. You know, that's, that's our initial goal, but we, we wanted to make sure to build it in a way that like, yeah, there's evolve ability to, it keeps, it, keeps it, make sure that you're getting kinda the most utility you can out of it. Peer-to-peer and the difficulty of federated queries [00:54:30] Jeremy: Yeah, I can see some of the parallels to some of the decentralized stuff that I, I suppose people are still working on, but more on the peer-to-peer side, where the idea was that I can have a network host this data. but, and in this case it's a network of maybe larger providers where they could host a bunch of people's data versus just straight peer to peer where everybody has to have a piece of it. [00:54:57] And it seems like your angle there was really the scalability part. [00:55:02] Paul: It was the scalability part. And there's great work happening in peer-to-peer. There's a lot of advances on it that are still happening. I think really the limiter that you run into is running queries against aggregations of data. Because you can get the network, you know, BitTorrent sort of proved that you can do distributed open horizontal scaling of hosting. [00:55:29] You know, that basic idea of, hey, everybody's got a piece and you sync it from all these different places. We know you can do things like that. What nobody's been able to really get into a good place is running, queries across large data sets. In the model like that, there's been some research in what is, what's called federated queries, which is where you're sending a query to multiple different nodes and asking them to fulfill as much of it as they can and then collating the results back. But it didn't work that well. That's still kind of an open question and until that is in a place where it can like reliably work and at very large scales, you're just gonna need a big database somewhere that does give the properties that you need. You need these big indexes. And once we were pretty sure of that requirement, then from there you start asking, all right, what else about the system [00:56:29] Could we make easier if we just apply some more traditional techniques and merge that in with the peer-to-peer ideas? And so key hosting, that's an obvious one. You know, availability, let's just have a server. It's no big deal. But you're trying to, you're trying to make as much of them dumb as possible. [00:56:47] So that they have that easy replaceability. Moderation challenges [00:56:51] Jeremy: Earlier you were talking a a little bit about the moderation tools that people could build themselves. There was some process where people could label posts and then build their own software to determine what a feed should show per a person. [00:57:07] Paul: Mm-Hmm [00:57:07] Jeremy: But, but I think before that layer for the platform itself, there's a base level of moderation that has to happen. [00:57:19] Paul: yeah. [00:57:20] Jeremy: And I wonder if you could speak to, as the app has grown, how that's handled. [00:57:26] Paul: Yeah. the, you gotta take some requirements in moderation pretty seriously to start. And with decentralization. It sometimes that gets a little bit dropped. You need to have systems that can deal with questions about CSAM. So you got those big questions you gotta answer and then you got stuff that's more in the line of like, alright, what makes a good platform? [00:57:54] What kind of guarantees are we trying to give there? So just not legal concerns, but you know, good product experience concerns. That's something we're in the realm of like spam and and abusive behavior and things like that. And then you get into even more fine grain of like what is a person's subjective preference and how can they kind of make their thing better? [00:58:15] And so you get a kind of a telescoping level of concerns from the really big, the legal sort of concerns. And then the really small subjective preference kind of concerns. And that actually that telescoping maps really closely to the design of the system as well. Where the further you get up in the kind of the, in that legal concern territory, you're now in core infrastructure. [00:58:39] And then you go from infrastructure, which is the relay down into the application, which is kind of a platform and then down into the client. And that's where we're having those labelers apply. And each of them, as you kind of move closer to infrastructure, the importance of the decision gets bigger too. [00:58:56] So you're trying to do just legal concerns with the relay right? Stuff that you objectively can, everybody's in agreement like Yeah, yeah, yeah. You know, no bigs don't include that. The reason is that at the relay level, you're anybody that's using your relay, they depend on the decisions you're making, that sort of selection you're doing, any filtering you're doing, they don't get a choice after that. [00:59:19] So you wanna try to keep that focus really on legal concerns and doing that well. so that applications that are downstream of it can, can make their choices. The applications themselves, you know, somebody can run a parallel I guess you could call it like a parallel platform, so we got bluesky doing the microblogging use case, other people can make an application doing the microblogging use case. So there's, there's choice that users can easily switch, easily enough switch between, it's still a big choice. [00:59:50] So we're operating that in many ways. Like any other app nowadays might do it. You've got policies, you know, for what's acceptable on the network. you're still trying to keep that to be as, you know, objective as possible, make it fair, things like that. You want folks to trust your T&S team. Uh, but from the kind of systemic decentralization question, you get to be a little bit more opinionated. [01:00:13] Down all the way into the client with that labeling system where you can, you know, this is individuals turning on and off preferences. You can be as opinionated as you want on that letter. And that's how we have basically approached this. And in a lot of ways, it really just comes down to, in the day to day, you're the moderation, the volume of moderation tasks is huge. [01:00:40] You don't actually have high stakes moderation decisions most of the time. Most of 'em are you know pretty straightforward. Shouldn't have done that. That's gotta go. You get a couple every once in a while that are a little spicier or a policy that's a little spicier. And it probably feels pretty common to end users, but that just speaks to how much moderation challenges how the volume of reports and problems that come through. [01:01:12] And we don't wanna make it so that the system is seized up, trying to decentralize itself. You know, it needs to be able to operate day to day. What you wanna make is, you know, back pressure, you know, uh, checks on that power so that if an application or a platform does really start to go down the wrong direction on moderation, then people can have this credible exit. [01:01:36] This way of saying, you know what, that's a problem. We're moving from here. And somebody else can come in with different policies that better fit people's people's expectations about what should be done at, at these levels. So yeah, it's not about taking away authority, it's about checking authority, you know, kind of a checks and balances mentality. [01:01:56] Jeremy: And high level, 'cause you saying how there's such a high volume of, of things that you know what it is, you'd know you wanna remove it, but there's just so much of it. So is there, do you have automated tools to label these things? Do you have a team of moderators? Do they have to understand all the different languages that are coming through your network? [01:02:20] Yes, yes, yes and yes. Yeah. You use every tool at your disposal to, to stay on top of it. cause you're trying to move as fast as you can, folks. The problems showing up, you know, the slower you are to respond to it, the, the more irritating it is to folks. Likewise, if you make a, a missed call, if somebody misunderstands what's happening, which believe me, is sometimes just figuring out what the heck is going on is hard. [01:02:52] Paul: People's beefs definitely surface up to the moderation misunderstanding or wrong application. Moderators make mistakes so you're trying to maintain a pretty quick turnaround on this stuff. That's tough. And you, especially when to move fast on some really upsetting content that can make its way through, again, illegal stuff, for instance, but more videos, stuff like that, you know, it's a real problem. [01:03:20] So yeah, you're gotta be using some automated systems as well. Clamping down on bot rings and spam. You know, you can imagine that's gotten a lot harder thanks to LLMs just doing text analysis by dumb statistics of what they're talking about that doesn't even work anymore. [01:03:41] 'cause the, the LLMs are capable of producing consistently varied responses while still achieving the same goal of plugging a online betting site of some kind, you know? So we do use kind of dumb heuristic systems for when it works, but boy, that won't work for much longer. [01:04:03] And we've already got cases where it's, oh boy, so the moderation's in a dynamic place to say the least right now with, with LLMs coming in, it was tough before and

A new MP3 sermon from Bloomington Reformed Presbyterian Church is now available on SermonAudio with the following details: Title: 12 - Maintaining the Right Perspective Subtitle: 2 Corinthians Speaker: Richard Holdeman Broadcaster: Bloomington Reformed Presbyterian Church Event: Sunday - AM Date: 1/12/2025 Bible: 2 Corinthians 4:13-18 Length: 35 min.

In this episode of the Modern Man Podcast, host Ted Phaeton welcomes renowned matchmaker Gina Hendrix to discuss the complexities of modern dating, particularly for high-profile men. They explore the challenges men face in finding genuine love, the misconceptions surrounding matchmaking, and the importance of self-awareness and communication in relationships. Gina shares her journey into matchmaking, the significance of profile optimization for dating apps, and how emotional intelligence plays a crucial role in personal connections. The conversation emphasizes the need for men to be open to help and to trust the process of finding love. In this conversation, Gina Hendrix, an ethical concierge matchmaker, discusses the intricacies of modern dating, the impact of dating apps, and the importance of ethical matchmaking. She shares insights on streamlining the dating process, the challenges men and women face in finding meaningful relationships, and the significance of being open and vulnerable in love. Through success stories and personal anecdotes, Gina emphasizes the need for genuine connections and the value of being hopeful in the dating landscape.   Takeaways Access is everything in love and dating. Dating apps complicate the dating landscape. Men often overlook their need for help in dating. Self-reflection is crucial for personal growth. Feedback from dates is essential for improvement. Professional success does not guarantee personal success. Vulnerability is key in personal relationships. Communication is vital in maintaining relationships. Matchmaking is not just for the wealthy; it's for those seeking genuine connection. Trust the process when seeking help in dating. Streamlining the dating process saves time and effort. Honorable intentions are crucial in matchmaking. The cost of hiring a matchmaker can be less than divorce. Ethics play a significant role in matchmaking. Dating apps have changed the perception of dating options. Women often seek men at their level of success. Men need to be aware of their dating approach. Being open and vulnerable is key to finding love. Success stories often come from being open to the process. Maintaining hope and positivity is essential in dating. Chapters 00:00 - Introduction and Teasing the Episode 01:14 - Meet Gina Hendrix: The Matchmaker 02:45 - Challenges in Modern Dating 03:50 - The Journey to Matchmaking 07:22 - Understanding the Need for Help 09:51 - Profile Optimization for Success 12:44 - Misconceptions About Matchmaking 15:40 - The Search for Genuine Connection 19:05 - Bridging Professional Success and Personal Life 21:44 - Making the Most of Matchmaking Services 24:22- Streamlining the Dating Process 30:48 - Navigating Modern Dating Challenges 35:01 - The Impact of Dating Apps 41:11 - Success Stories in Matchmaking 46:20 - Lessons Learned and Final Thoughts   Gina's Links:  Website: ginahendrix.com Facebook: ginamatchmaker  TikTok: matchmakerginahendrix  Youtube: ginahendrix5879  Instagram: matchmakerginahendrix  LinkedIn: ginahendrix  Free eBook Here: Mastering Self-Development: Strategies of the New Masculine: https://rebrand.ly/m2ebook   ⚔️JOIN THE NOBLE KNIGHTS MASTERMIND⚔️ https://themodernmanpodcast.com/thenobleknights   

S7. Episode 1 - Maintaining Your Competive Edge by Millennial Mayhem

Are your docs part of your DevOps cycle? Richard chats with Mattias Karlsson about automating documentation for APIs, cloud resources, and more! Mattias talks about using tools to build text files that contain every Azure resource being utilized, hopefully per application, along with API info, NuGet packages, and more. He also digs into the different audiences for that documentation - business wants to know what website exist, both interior and publically facing. Operations need to know what resources are consumed on-premises and in the cloud. Development is always looking for versions of APIs, calling approaches, etc. Maintaining documentation by hand is tedious and perpetually out-of-date. But if you can get up to speed with the tooling, you can make your documentation generate at the speed of deployment!LinksBicepAzure Resource InventoryAzure CLIPulumiRecorded October 29, 2024

Northwest Arkansas continues to grow, and cities are trying to ensure the water supply keeps pace. On today's show, we talk about water leaks and growth. Also, Governor Sarah Huckabee Sanders lines out her priorities for the 95th General Assembly in her State of the State address. Plus, the Northwest Arkansas Martin Luther King, Jr. Council will host the 29th annual Recommitment Celebration.

Sarah is passionate about harmonious relationships between dogs in homes. Maintaining and fostering peace between highly driven individuals is not simple and something she takes very seriously. One thing that is missing in the thoughts of many professionals and guardians alike is the level of responsibility we should be placing on ourselves as the person who decided to integrate the dogs we acquired. Learn specifics about what this looks like and then some. Sign up for courses and join the membership here: sarahstremming.com Join us on Patreon: https://www.patreon.com/cogdogradio Music by AlexGrohl from Pixabay

In this episode of Working Class Audio, Matt welcomes mastering engineer Adam Haggar who has worked with Migos, Belinda Carlisle, and The Antlers. In This Episode, We Discuss: Adam's Journey In The Audio Industry Different Cities, Studios, And Roles Within The Music Industry His Approach To Mastering And Building His Business The Importance Of Networking Challenges Of Maintaining High Standards In A Competitive Industry Value Of Staying Connected To One's Passion For Music Links and Show Notes: Adam s Site Matt's Rant: Los Angeles Credits: Guest: Adam Haggar Host/Engineer/Producer/Editor: Matt Boudreau WCA Theme Music: Cliff Truesdell The Voice: Chuck Smith

Send us a textCommunication is key to a thriving relationship, and asking for what you want instead of complaining is a game-changer. This episode offers practical tools to help you identify your unexpressed needs and transition from a blame-focused mindset to positive, actionable requests. • Emphasizing the importance of vulnerability in relationships • Identifying the root of complaints and transforming them into requests • Maintaining love and empathy while making requests • Discussing personal responsibility in fulfilling partner needs • Recognizing and managing micro disappointments • Encouraging feedback from listeners about their experiences with requests

Today, I'm giving you a comprehensive January checklist to help organize your taxes if you're self-employed so that you can have a headstart on your taxes for 2025.     Tune in to this episode to get a strong start to the tax year and put systems in place to simplify your tax preparation process.   Also mentioned in today's episode:    Why you should check your odometer now 2:11 Issuing 1099's and estimated tax payments 6:48 Maintaining business bank accounts and receipts 10:45   If you enjoyed this episode, please rate, review and share it!  Links: Check out my program, Money Bootcamp.  

Vance Morris is a former Disney Leader turned entrepreneur, coach, speaker and author. He helps businesses deliver extraordinary customer experiences through workshops, boot camps, and training at Disney. In this episode, Vance shares practical strategies for implementing premium pricing by presenting options and building value through transparency and trust. He emphasizes the importance of creating emotional connections with customers to enhance loyalty and retention, even in B2B environments. Additionally, he advocates for confident implementation of price increases, highlighting that many pricing challenges stem from business owners' mindset rather than market resistance.   Why you have to check out today's podcast: Learn how to confidently set premium prices and create packages that differentiate your business from competitors. Discover how emotional connections, rather than just logic, can drive customer loyalty and enhance sales, even in B2B settings. Get tips on overcoming common pricing hurdles and improving customer retention through simple yet effective strategies.   “People have enough information, they don't have enough implementation; just go do it. You could go out right now, raise your prices 10% and nobody's going to bat an eyelash.” - Vance Morris   Topics Covered: 01:45 - How he found himself in pricing 02:31 - Sustaining a cycle of value and profitability as inspired by Disney's pricing strategies 05:20 - How he justifies premium pricing in his upholstery cleaning business 08:46 - Demonstrating expertise and showcasing value  11:32 - Emphasizing the value of positioning as a premium service rather than competing on being the second cheapest 13:00 - Maintaining pricing integrity 14:21 - Adapting Disney-inspired strategies to differentiate your business making it incomparable to competitors 16:37 - How to differentiate your products or services, even in competitive markets like B2B software 17:57 - How to foster loyalty, enhance customer retention, and make price increases more acceptable 21:09 - Highlighting the value of small, thoughtful gestures to build a positive reputation and stand out in competition 22:42 - Offering premium pricing tiers in clear, non-salesy manner 24:57 - Vance's best pricing advice   Key Takeaways: "Not so much to justify [premium pricing], as it is being able to offer a better experience, which then allows me to charge a higher price, which puts more money in my pocket." - Vance Morris "It's about creating a connection. It's people doing business with people. It's not people doing business with business and creating some kind of emotional connection with the purchasing manager, with whoever's doing the buying. And it just makes selling so much easier." - Vance Morris "When you have that connection, a price increase may not be overlooked, but is a lot more palatable than just hard excel spreadsheets flying around." - Vance Morris "There is no competitive advantage to being second cheapest; if you're not going to be the cheapest, you might as well go the other direction." - Vance Morris   People/Resources Mentioned: Disney: https://www.disney.com/ Ritz-Carlton: https://www.ritzcarlton.com/ Dunkin Donuts: https://www.dunkindonuts.com/en   Connect with Vance Morris: LinkedIn: https://www.linkedin.com/in/vancemorris/ Website: https://deliverservicenow.com/   Connect with Mark Stiving: LinkedIn: https://www.linkedin.com/in/stiving/ Email: mark@impactpricing.com  

How can combining professional coaching and emotional intelligence lead to long-term success in real estate? In this episode of the Real Estate Excellence Podcast, host Tracy Hayes interviews Wendy Griffis. Wendy is a Realtor®, Author and Group Leader in Jacksonville, Florida. Wendy has been serving the Jacksonville and surrounding areas since February 2000. Her experience and understanding of the area and market allows her to give accurate and thorough advice to her clients; providing successful, streamlined results, regardless of market conditions. Wendy acts in a consulting role – having an honest & direct approach with her clients. She knows how to help buyers and sellers follow her customized, but tried and true processes that gets results! Wendy has significantly outperformed the majority of the agents in our MLS in year over year sales numbers, property days on market, and list to sold price. Wendy is an advocate for her clients before, during and after the transaction. Wendy can be seen annually in the Jacksonville Journal Book of Lists. She was on the cover of Jacksonville Real Producers Magazine, and featured in articles in Florida Realtor and Buffini & Company magazines.  Wendy discusses the importance of emotional intelligence, crafting relationship-based business models, and navigating difficult market conditions with grit and grace. Listeners will hear about her approach to balancing professionalism and personal connection, the lessons she learned during the Great Recession, and how she uses insights from industry leaders like Brian Buffini to stay ahead in an ever-evolving field. Ready to transform your real estate career? Explore coaching opportunities and take time to develop your emotional intelligence.   Highlights 00:32 – 06:53 Wendy Griffis: Recognize the Difference ·       We welcome Wendy Griffis to the show! ·       How she transitioned from aspiring math teacher to successful realtor. ·       Rebounding from job loss due to Y2K and finding her path in real estate. ·       The growth and her philosophies for sustained success in the industry. 06:54 – 13:19 Emotional Intelligence in Real Estate ·       Wendy talks about her journey from selling six houses in the first year to over twenty annually by the second year. ·       Initially driven by the need for income and lacking a CRM. ·       The evolution of technology and its impact on customer service. ·       The transitioning phase of not wanting to be a sale-sy agent and choosing to build a relationship-based business.  ·       Maintaining professionalism and changing industry perceptions. 13:20 – 25:56 Coaching and Continuous Learning ·       How Wendy's journey went from hosting client events to enduring the economic turmoil of the late 2000s. ·       The emotional toll of difficult client conversations and personal financial struggles. ·       The underestimated daily tasks of a realtor. ·       Building long-term business relationships and setting personal boundaries. ·       The often-ignored emotional intelligence required in the industry. 25:57 – 36:49 Handling Tough Conversations ·       The crucial role of a seasoned real estate agent in guiding clients through complex home-buying processes. ·       The significance of soft skills like emotional intelligence. ·       The necessity of developmental learning and effective client interactions. ·       Competent service and the impact of personal growth through literature and networking. ·       Effective strategies for new which includes blending short-term client acquisition with long-term relationship management. 36:50 – 55:07 Developing Emotional Intelligence ·       Wendy's journey of personal and professional growth through reading and developing emotional intelligence. ·       How emotional intelligence helps in not taking rejection personally and swiftly moving towards solutions. ·       How handle setbacks promptly. ·       How personal notes fostered a genuine connection with clients. ·       The value of buyer consultations and the proper handling of buyer broker agreements are examined.   55:08 – 01:23:06 Strategic Selling and Pricing ·       Wendy discusses how effective pricing and negotiation tactics to the importance of deepening client relationships. ·       The challenges faced by agents dealing with new constructions and builder incentives. ·       The importance of consistent systems, client engagement through events. ·       Leveraging additional help such as transaction coordinators and operations managers. ·       Conclusion.   Quotes: “Real estate is not sales. I'm not selling anybody anything—I'm helping them achieve their goals.” – Wendy Griffis “ Emotional intelligence is about not taking things personally and focusing on solutions.” – Wendy Griffis “Price isn't always the problem, but it's often the solution” – Wendy Griffis   To contact Wendy Griffis, learn more about his business, and make her a part of your network, make sure to follow her on Instagram, Facebook, and Website. Instagram: https://www.instagram.com/wendygriffis/ Facebook: https://www.facebook.com/WendyGriffisGroup Website: https://www.wendygriffisgroup.com/   If you want to build your business and become more discoverable online, Streamlined Media has you covered. Check out how they can help you build an evergreen revenue generator all powered by content creation!   SUBSCRIBE & LEAVE A 5-STAR REVIEW as we discuss real estate excellence with the best of the best.

January 13, 2025: Jason Rose, CEO of Clearsense, explores the delicate balance between accessibility, accuracy, and security in data management. Jason delves into pressing questions: How do organizations tackle the dual challenge of maintaining data integrity while protecting against cyber threats? What cultural shifts are necessary to maximize the value of 20 years of digitized healthcare data? And as mergers and acquisitions reshape the landscape, how can systems ensure efficiency without compromising security?Key Points: 06:35 Data Accuracy and Validation11:51 Security Concerns in Healthcare19:23 Partnerships and Risk Management27:44 Mergers and Acquisitions in Healthcare37:45 Predictions for 2025News ArticlesCritical Condition: The Delicate State of Healthcare DataHHS Proposes New Cybersecurity Measures to Protect Healthcare DataTransform Resolutions into Revolutions for Lasting Personal ChangeSubscribe: This Week HealthTwitter: This Week HealthLinkedIn: Week HealthDonate: Alex's Lemonade Stand: Foundation for Childhood Cancer

In this episode of Weaver: Government Impact, host Todd Hoffman, along with Weaver IT experts Brett Nabors and Morgan Page, explores the critical challenge of preparing the future workforce in government sectors. The discussion revolves around adapting to rapid technological changes, addressing skill gaps, and evolving compensation models to stay competitive. This episode is a must-listen for those interested in workforce development and technology integration in the public sector.Key Points: • Bridging skill and competency gaps in government workforces is achieved through targeted cross-training and strategic external hiring.• Maintaining legacy systems while integrating new technologies balances traditional and modern IT needs in government.• Adapting compensation models helps governments remain competitive and attract skilled professionals in a rapidly evolving tech landscape.The podcast delves into the complexities of preparing a future-ready government workforce. It highlights the challenges of retiring employees, the lack of succession planning, and the rapid pace of technological advancement. The conversation with Nabors and Page provides insights into how governments can bridge skill gaps internally through cross-training and externally through strategic hiring while addressing pay pressures to compete with the commercial sector.“Your Gen AI is now your level one... Your level one with Gen AI is no longer necessary because you can take Joe Bob off the street, pair him with Gen AI, and say, how do I insert a question here,” Page said. “And it gives you a three, five, seven-step process to fix it.” This shift towards leveraging technology like Gen AI redefines the government workforce's skill levels and roles. Subscribe and listen to future episodes of Weaver: Government Impact on Apple Podcasts or Spotify.©2024

The Wellfit General Manager, Nikesh Naik, joins the Morning majlis team to encourage you to join the Wellfit gym membership and tackle 2025 properly. Nikesh also explains the modern facilities that Wellfit offers and how it caters to everyone with the diverse and exciting classes, allowing newcomers to enjoy an easy transition into the gym. Listen to #Pulse95Radio in the UAE by tuning in on your radio (95.00 FM) or online on our website: www.pulse95radio.com ************************ Follow us on Social. www.facebook.com/pulse95radio www.twitter.com/pulse95radio www.instagram.com/pulse95radio

Maintaining a healthy relationship with money requires ongoing self-reflection and 'adjustment'. Put another way, wealth isn't found in the accumulation of money, it's found in our growing influence. Money puts action into our intentions.Read moreBook in a free 15-min phone call with Darcy Ungaro (financial adviser).Sign up to the fortnightly newsletter!Brought to you in partnership with: Icehouse Ventures is a Kiwi Venture Capital firm investing in Kiwi startups since 2001. Affiliate Links*!The Bitcoin Adviser: Plan for intergenerational digital wealth. Hatch: For US markets.Sharesies: For local, and international markets.Easy Crypto: To buy and sell digital assets.Sharesight: For tracking and reporting on your portfolioExodus: Get rewards on your first $2,500 of swapsRevolut: For a new type of banking.*Some links create a financial benefit.Online courses:The Home Buyers Blueprint: Get a better home; Get a better mortgage.The KiwiSaver Millionaire Roadmap: Get a Rockstar Retirement!New Wealth Foundations: Personal finance from a wealth-builder's perspective.Take the free, 5-part online course Crypto 101: Crypto with Confidence Get Social:Check out the most watched/downloaded episodes hereFollow on YouTube , Instagram, TikTok: @theeverydayinvestor, X (@UngaroDarcy), LinkedIn.www.ungaro.co.nz________________________

In a world at odds with your faith, the only way to keep going in the right direction is to maintain an eternal perspective, so in Jesus, keep your focus on His unseen work.

Summary In this episode of the ESPC podcast, Josh Abner Vizcay discusses the intersection of sports betting, mental health, and financial literacy. He emphasizes the importance of collaboration and sharing information in making informed betting decisions. The conversation covers various NFL games, analyzing team dynamics, coaching strategies, and player performances, while also highlighting the significance of maintaining mental health and relationships in the gambling world. The episode concludes with predictions for upcoming games and a call to action for listeners to engage with the content. Takeaways The ESPC podcast aims to monetize time spent watching sports. Collaboration and sharing information are key to success in sports betting. Mental health is an important aspect of gambling and investing. Fundamental analysis is more effective than technical analysis in betting. Time management is crucial; time equals money. Understanding team dynamics and coaching strategies can lead to better betting decisions. Double-digit dogs in the division have a high cover rate. Situational intelligence is vital in making informed decisions. The air raid offense has its strengths and weaknesses in the NFL. Maintaining relationships is essential for mental health in the gambling community. Sound Bites "Time is money." "Sports is an investable asset class." "The air raid wins early, loses late." Chapters 00:00 Monetizing Time: The Purpose of the Podcast 03:51 Mental Health and Financial Literacy in Sports Betting 06:37 Analyzing the Chargers vs. Texans Game 09:52 Pittsburgh Steelers vs. Baltimore Ravens: A Tactical Breakdown 12:44 Buffalo Bills vs. Denver Broncos: Quarterback Dynamics 15:54 Coaching Mismatches: Packers vs. Eagles 29:33 Analyzing Jordan Love's Progression 30:54 Game Predictions and Coaching Mismatches 33:21 The Importance of Collaboration and Diversity in Analysis 34:50 Understanding Quarterback Challenges in Air Raid Offense 38:44 Defensive Strategies: Zone Blitz and Simulated Pressure 42:34 Evaluating the Tampa Bay Buccaneers' Game Plan 46:39 Quarterback Performance and Game Strategy 51:42 Final Thoughts on the Vikings vs. Rams Matchup 56:46 SlickRickClosing copy.mp3

How to maintain a polite society. It’s not about revenge, its about forcing evil people to adjust their behavior. BK and the fires ravaging the California coast. Looking back on the new years terror attacks, what do we know now that we didn’t a week ago.See omnystudio.com/listener for privacy information.

Kacper Kapuściak from Software Mansion joins Jamon and Mazen for a deep dive into the world of maintaining open source libraries for React Native—what it takes, why it matters, and how tools like Reanimated and Screens keep evolving. They also explore the impact of open source on the community and how developers can stay ahead. Show NotesMinute React Native Software Mansion Membrane  Connect With Us!React Native Radio: @ReactNativeRdioJamon Holmgren: @jamonholmgrenMazen Chami: @mazenchamiKacper Kapuściak: @kacperkapusciak This episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

Our guests in this episode have been described as the world's two oldest scientifically astute longevity activists. They are Kenneth Scott, aged 82, who is based in Florida, and Helga Sands, aged 86, who lives in London.David has met both of them several times at a number of longevity events, and they always impress him, not only with their vitality and good health, but also with the level of knowledge and intelligence they apply to the question of which treatments are the best, for them personally and for others, to help keep people young and vibrant.Selected follow-ups:Waiting For God - 1990s BBC ComedyAdelle Davis, NutritionistRoger J. Williams, BiochemistThe Importance of Maintaining a Low Omega-6/Omega-3 RatioLife Extension MagazineCalifornia Age Management InstituteFibrinogen and agingProfessor Angus Dalgleish, Nuffield HealthAbout Aubrey de Grey speaking at the Royal InstitutionGeorge Church, GeneticistJames Kirkland, Mayo ClinicDaniel Munoz-Espin, CambridgeNobel Prize for John Gurdon and Shinya YamanakaVSELs and S.O.N.G. laserXtend Optimal HealthFollistatin gene therapy, MinicircleExosomes vs Stem CellsPrevent and Reverse Heart Disease - book by Caldwell Esselstyn Jr Dasatinib and Quercetin (senolytics)We reverse atherosclerosis - Repair BiotechnologiesBioreactor-Grown Mitochondria - MitrixNobel Winner Shinya Yamanaka: Cell Therapy Is ‘Very Promising' For Cancer, Parkison's, MoreDeath of the world's oldest man, 25th Nov 2024Blueprint protocol - Bryan JohnsonMusic: Spike Protein, by Koi Discovery, available under CC0 1.0 Public Domain Declaration

Protecting the nation's energy grid is a top priority for America's electric companies, and the electric power industry leads several initiatives to safeguard the grid from any potential threats and hazards. This episode explores Edison Electric Institute's (EEI's) Culture of Security initiative, which is comprised of a few different programs to help electric companies collaborate and share best practices, including a peer review to assess security culture.  On this episode, EEI Managing Director of Cyber and Infrastructure Security David Batz and EEI Senior Director of Cyber and Infrastructure Security Kaitlin Brennan discuss the Culture of Security initiative and others led by our industry, as well as our partnerships with federal agencies to enhance sector-wide resilience to both cyber and physical security threats. 

Hailey joins us in today's episode to discuss how her personal identity has changed or evolved since becoming a mom! Keep the conversation going on our Instagram @accordingtwo. Follow us on Instagram: According Two: @accordingtwo Megan Stitz: @megan_marie32 Ciera Stitz: @ciera_jo

As we begin a new year, cartoonists Dave Kellett and Brad Guigar make their predictions for 2025 and share their goals for the next twelve months.PredictionsDAVE: Business planning anxietyBRAD: Because of Dave's prediction, the winners will be people who help address that anxiety. (That's us!) Be the distraction/escape people need; they won't forget you. DAVE: Bluesky at 50M by the end of the yearBRAD: Substack gains prominence — rises to Kickstarter/Patreon levelsDAVE: we'll all be playing reactionary, whack-a-mole life choices for the first two years of the trump admin. Until the midterm elections, when it might calm slightly. BRAD: AI will go mainstream and start to gain acceptance among artists and writersDAVE: Kickstarter and Patreon continue to be market leaders. No change on the horizon for thatBRAD: Printing is on the decline under tariffs. And we might be working with small US printers to do smaller books.DAVE: in publishing, YA & kids will continue to dominate the career path of published cartoonists. BRAD: Non-social media options will grow, hopefully including RSSDAVE: Webtoons might begin to fall apart in the US market. Their Hollywood goals are not working, and they were playing the long game toward THAT in terms of accumulating debt DAVE: I will have to raise prices on all my books. Or cut features in my books. No more metallic foils, spot gloss, or bookmarks…you're just getting a bare-bones book. GoalsBRAD: SurviveDAVE: SurviveBRAD: EiAD v3 or Webcomics HandbookDAVE: ANATOMY OF DOGS Kickstarter BRAD: Build Spice Rack Comics into an example of what you can do with the webring / collective concept. Suggest that this is the time to start building quasi-collectives.DAVE: Triple down on Bluesky in the 4-6 years before enshittification BRAD: Lean into KDP for After Dark booksDAVE: Triple down on BlueskyDAVE: Launch and start building THE WRONG WAY. I have been planning it for over a year. DAVE: Focus on one of the few things I can control: my family's happiness and health. Outlive the fuckers and try not to let them steal my joy. I find solace in friendships at Alaska Camp and SDCC. DAVE: if we can't do books, do we do more smaller Quickstarter?DAVE: Is this the time to start on Substack?SummaryIn this episode, the hosts discuss a range of topics, including a personal quest for a long-lost book, Wimpy the Wellington, predictions for the comic industry in 2025, the anxiety surrounding business planning for cartoonists, and the evolving role of cartoonists in providing relief during turbulent times. They also explore the rise of new platforms like Blue Sky and Substack and the potential mainstream acceptance of AI in the creative fields. In this conversation, Brad Guigar and his co-host discuss the evolving role of AI in creative processes, emphasizing its potential as an assistant rather than a replacement for artists and writers.They make predictions for 2025, including the impact of tariffs on print publishing, the continued dominance of YA and kids' books, and the uncertain future of Webtoons in the U.S. market. The discussion also touches on the concept of 'shrinkflation' in publishing, where features may be reduced due to economic pressures.Ultimately, both hosts express a shared goal of survival in a changing industry landscape. In this episode, the hosts discuss their goals and predictions for 2025, focusing on the importance of social media platforms like Blue Sky, the launch of a new project called The Wrong Way, and the innovative approach of Spice Rack Comics. They also touch on adapting to market changes, personal goals, and the significance of community support in the creative industry.TakeawaysCartoonists have a significant impact on their audience's mental health.Business planning in the comic industry is becoming increasingly complex.The rise of platforms like Blue Sky may change social media dynamics.Substack is poised to become a major player in content monetization.Anxiety will be a common theme in the coming years for creators.AI's acceptance in the creative industry is on the horizon.The importance of community and support among creators is paramount.Predictions for the future can help guide current decisions.The role of humor and distraction in art is vital during tough times. AI will be used as a writing assistant, not a replacement.Ethically sourced AI can enhance creative processes.Print publishing is expected to contract significantly due to tariffs.YA and kids' books will continue to dominate the market.Webtoons may struggle in the U.S. market moving forward.Shrinkflation will affect the features of published books.Survival is the primary goal for creators in 2025.Economic changes will force a reevaluation of publishing strategies.The creative industry must adapt to new market dynamics.The future of comics relies on navigating these challenges. Tripling down on Blue Sky is a strategic move for growth.The Wrong Way project is set to launch in 2025.Spice Rack Comics aims to innovate web rings and promote collaboration.Adapting to market changes is crucial for sustainability.Personal goals should focus on what can be controlled.Community support is essential for success in creative fields.Digital income sources are becoming increasingly important.Maintaining joy and personal happiness is a priority.Nostalgia can be a refuge during uncertain times.Building a supportive network can enhance creative endeavors. You get great rewards when you join the ComicLab Community on Patreon$2 — Early access to episodes$5 — Submit a question for possible use on the show AND get the exclusive ProTips podcast. Plus $2-tier rewards.Brad Guigar is the creator of Evil Inc and the author of The Webcomics Handbook. Dave Kellett is the creator of Sheldon and Drive.

In this episode of FYI, Brett Winton, ARK's Chief Futurist, hosts an enlightening discussion with Peter Diamandis, founder of the XPRIZE Foundation and author of the upcoming Longevity Guidebook, alongside ARK Invest CEO/CIO Cathie Wood. They explore the transformative role of artificial intelligence and biotechnology in extending human health span and lifespan. Peter delves into the revolutionary advancements in diagnostics, gene editing, and epigenetic reprogramming, while Cathie highlights the market implications of these breakthroughs. Tune in to understand how these technologies are reshaping the future of healthcare, the economy, and our approach to aging.Key Points From This Episode:The premise of Peter Diamandis' Longevity Guidebook and its focus on reversing aging.AI's pivotal role in drug discovery, healthcare diagnostics, and personalized medicine.How advancements like CRISPR and epigenetic reprogramming are redefining longevity science.The market's undervaluation of biotech innovations and their transformative potential.The concept of "longevity escape velocity" and its implications for human life expectancy.Maintaining a "longevity mindset" through sleep, exercise, and diet is important.Economic and societal shifts from extended lifespans and productivity.The future of brain mapping and AI-assisted preservation of consciousness.Innovations in healthcare delivery, from diagnostics to preventative therapies.

Maintaining a culture of respect is crucial, and without it you can shake the foundation of any profession. Yet, incivility remains a significant challenge in nurse anesthesia educational programs, affecting both students and faculty. Today we're discussing strategies or creating the right culture and professionalism with Nancy A. Moriber, PhD, APRN-CRNA, FAANA and Maribeth Massie, PhD, CRNA, FAANA, FAAN. Here's some of what we discuss in this episode: Incivility is a problem in our society and has infiltrated the healthcare setting and nursing academia, including nurse anesthesia. Incivility negatively impacts the teaching-learning environment, undermines professionalism, creates unnecessary stress and anxiety, and can lead to significant mental health issues. The different biases that can impact incivility. Strategies to combat these behaviors. Ways to create and sustain positive environments for teaching and learning. Get the Positive Psychology Coursera course mentioned in the show here: https://www.coursera.org/learn/positive-psychology-resilience Visit us online: https://beyondthemaskpodcast.com/ The 1099 CRNA Institute: https://aana.com/1099 Get the CE Certificate here: https://beyondthemaskpodcast.com/wp-content/uploads/2020/04/Beyond-the-Mask-CE-Cert-FILLABLE.pdf Help us grow by leaving a review: https://podcasts.apple.com/us/podcast/beyond-the-mask-innovation-opportunities-for-crnas/id1440309246 Donate to Our Heart Your Hands here: https://www.ourheartsyourhands.org/donate  Support Team Emma Kate: https://grouprev.com/haloswalk2024-shannon-shannon-brekken