Podcasts about Oops

For a 3rd straight year, Joe's Royal Rumble picks come true, but at what cost? There goes the Money with Shane O'Mac, Ruby is an unhappy gem in AEW and more!

Content warning: The episode of The Nanny we discuss includes some transphobic humor, which we begin to discuss about 34 minutes into the show We manage to discuss Corbin Bernsen's guest appearance in this second-season episode of The Nanny without once mentioning that he was in, like, almost all of Psych. Oops. Oh well. At […]

Oops! Someone spilled something on the machine that makes sketches down at Sickos HQ and now it won't turn off!! Enjoy 50 minutes of extremely stupid sketches from your favorite boys of online!

2 - 1-22 OOPS WHAT WAS IN THE PIC I SENT MY BOSS by Maine's Coast 93.1

Going Broke Land Investing or Not (LA1688) RERUN Transcript: Steven Butala: Steve and Jill here. Jill DeWit: Howdy. Steven Butala: Welcome to the Land Academy Show, entertaining land investment talk. I'm Steven Jack Butala. Jill DeWit: And I'm Jill DeWit, broadcasting from sunny Southern California. Steven Butala: Today, Jill and I talk about going broke land investing or not, hopefully not. This came up because somebody directly emailed me and asked me, "Am I going to go broke doing this?" And I said, "I don't know. Are you?" I mean, I can tell you... That's what this episode is about. I can tell you exactly how to go broke or how not to go broke, hopefully. And what it takes like in your soul, and in your skillset, and in your attitude, and everything. Jill has got a lot of notes too, because I think a lot of it... Jill talks to a lot more, "I'm thinking about joining, but I'm not sure yet," people. Jill DeWit: And this is one of their big concerns. Steven Butala: Yeah. Jill DeWit: And I tell them, here's exactly what you do then, and you won't go broke. Steven Butala: Excellent. I'm going to enjoy the show, just like you are, listener. Before we get into it, let's take a question posted by one of our members on the landinvestors.com online community. It's free. Jill DeWit: Mike wrote, "I've seen a lot of talk and varying opinions on this. When would you remail the same acreage," and he put in bold, "Same acreage in a county you've mailed before. Would it depend on days on market and activity in the county, since some places will have a quicker turnover and change of ownership. Remailing after two months, I guess you'd piss off a lot of people, and it would be too soon to get a significantly different response or change of ownership. There must be a sweet spot. Any thoughts?" Steven Butala: So this question is not addressed in our formal education program, so it comes up. In fact, it comes up every single live event. It just comes up a lot. And it's a great question. And God, I hate when people answer questions like this, but I'm going to answer it like this. It's up to you. But I can tell you what we do, and I can tell you what other people do, and both are successful. We never ever remail the same acreage county, maybe in our lifetime. Steven Butala: What we do is, if we mail a county in, let's say, it doesn't matter, Minnesota, some specific county in Minnesota, I usually mail between five and 10 acres to begin with, or some number like that, depending on how the number check comes out. There's 5,000 properties in one county in Minnesota that are between one and five acres that don't have any improvements on them. Okay, bang. I'm going to mail it. If we have success, then we'd mail five to 10 acres. If we have success with that, then we mail 10 to 20 acres or whatever. Steven Butala: I cannot think of a single time in my entire career where I went back two months later because I had a bunch of success and remailed the same thing. So every time I get questions like this, this is what I ask myself. Why would you do that? And I bet you a dollar the answer is this. Because I don't want to buy any more data. I don't want to spend any more money. Jill DeWit: That's what you think is going on? Oh, that's interesting. Got it. Steven Butala: I already scrubbed all this data. It's already all in place. I'm happy with it. I got a good response on it. I'm just going to do it again. I want to skip that whole part of my life and just send it back to O2O, or maybe just call O2O and say, "Hey, can you just mail the same thing again?" Jill DeWit: I've heard people doing this when they thought they priced it so wrong, and they want to come back with a new price, and they want to hit the same area. I can kind of wrap my head around that one. Maybe you came in and you offered too little, you offered $100 an acre, and you realize, "Oops, I should have been offering $500 an acre." Something like that. And you're like,

On this week's episode of the Just Grizzlies podcast with Kelcey Wright Johnson, Brandon Clarke hops on the mic to talk about the perfect alley-oop; who throws it, how he initiates it, how he keeps his body ready and more. He also opens up about keeping his mental heath strong during tough periods, his incredible PER rating this season, his relationship with Jaren Jackson Jr. and a special shoutout to his two pet kittens.

Peter gets a lot of bad news right away: Alycia's dead, Kimberly's in the wind, and all evidence points to him as Bobby's murderer. At least he convinces Amanda that he didn't kill her ex, even though she, you know, obviously knows he definitely DID try to kill AMANDA HERSELF. But never mind! He's very pleased when Kimberly appears at his house out of the blue, but despite criticizing MICHAEL earlier for not noticing wild swings in Kimberly's personality, Peter does not interpret the headband and sister-wife dress as representing one of Kimberly's alters. Betsy pretends to agree to corroborate Peter's alibi to the cops, but then enacts her own scheme to get him out of her way. Will amateur sleuths Michael and Amanda crack the case in time? After Alison gets between Richard and Jake (or rather Jake's murderous rage), she manages to talk Jane into meeting with a friend of Alison's at the DA's office (?) about pressing charges against Richard -- and Jane does seem optimistic and energized in Alison's pal's office...until she warns Jane about how weak her case is, and how humiliating it will be for Jane to go through with it. Alison and Jake try to hector Jane into following all the "correct" steps for a sexual assault survivor, but Jane has other ideas. And when Dr. O'Malley isn't treating an obstreperous unhoused teen with a mysterious illness (though Matt is taking the brunt of the kid's sarcastic abuse), he's making things awkward with Jo by spouting off about irresponsible parents who give birth to children they then don't raise themselves. Oops! Won't you join us in our podcast on "Peter's Excellent Adventure"?Visual AidsVisual Aids S04.E30Show NotesShow notes for this episode can be viewed on this episode's page on AgainWithThisPodcast.com.Will & Grace S07.E07: "Will & Grace & Vince & Nadine" on HuluFollow Us@awt90210 on TwitterAgainWithThisPodcast.comSupport AWT On PatreonThank you to all our supporters! You can support the podcast directly on Patreon and get access to bonus episodes of “Again With Again With This” as a thank you from us! Check out AWT's Patreon page today.Support AWT With A Personal MessageWish your friend a happy birthday or just call them a squeef with a AWT Personal Message. It's $50 and helps keep us going. Start on our ad page now!Buy our book"A Very Special 90210 Book" (Abrams, $24.99) can be yours RIGHT NOW! Here's ordering info via our publisher, Abrams or find it anywhere else books are sold! See acast.com/privacy for privacy and opt-out information.

Hey everybody, it's Nick here. Unfortunately due to an unfortunate situation, my beautiful baby girl Simona caused an unfortunate setting on our recording board to happen which unfortunately means this week's audio didn't record.We'll be back next week with a super great episode, featuring some of the things we talked about this week, including an awesome segment talking about plot holes in Disney movies. If you have a plot hole that really drives you nuts, we'd love to hear it. Send us an email at hello@dinnerplusdrinks.com and we'll add it to the list!Have a great week, sorry for the oops, we'll be back next week!Nick

This video will be about 30 mins with Poody the morning motivation. The episode consist of Values, Chess and Stars. --- Send in a voice message: https://anchor.fm/30minswithpoody/message Support this podcast: https://anchor.fm/30minswithpoody/support

Avantgardistische Elektronika und frickelige Klangexperimente. ## NOKO 131 - Rich On Old AFX Tapes warp≈end rephlex≈es! Oops! he did it again.. Richard D. James give us the hook back! Under the well known alias Aphex Twin arised the Syro album on Warp Records, 13 years after the larger than average Drukqs box and more than 20 years after the larger than life Selected Ambient Works era. In the last months, after the Syrobonkers! interview with Dave Noyze, he shared well over 280 dat/tape recordings thru the web most from the early 90s. now the account as user48736353001 switched to user18081971, not without a little message: what an opportunity to promote my shit knock-offs! . AFX - Intro. phone pranks (as Caustic Window w/ Scanner & Mixmaster Morris) (CAT 023, 1994) 1. AFX - asthma1 2. AFX - pcp 2 [unreleased version] 3. AFX - moodular acid [pissflaps mix] (1993) 4. AFX - fresher + cleaner (1990) 5. AFX - ach (1993) 6. AFX - t08+4 7. AFX - t13 quadraverb 8. AFX - random fx (1990) 9. AFX - mtg edit eq-powerpill (1994) 10. AFX - window peeper (as Phonic Boy on Dope) (1987/88) 11. AFX - pump the shit (1991) 12. AFX - thnxu4letinmestywitu (1990) 13. AFX - with my family 14. AFX - lmt 15. AFX - cutting 16. AFX - cmarth [longer] 17. AFX - 5 [demo] 18. AFX - brk2 19. AFX - barbarella on microdots 20. AFX - make a baby 21. AFX - square dance 22. AFX - winding road (1995) 23. AFX - (taut) 24. AFX - chink 101 25. AFX - japan (remix as Polygon Window of Soft Ballet - sand löwe) 26. AFX - ssba (1994-ish) 27. AFX - dondo (1994) 28. AFX - diskhat all prepared1mixed 13 (WAP 375, 2015) 29. AFX - minipops 67 [source field mix] (WAP LP247, 2014) 30. AFX - untitled 97 (as Steinvord w/ Squarepusher) 31. AFX - hypersquij 32. AFX - nova robotiks 33. AFX - nocares 34. AFX - fogbeak 35. AFX - ibiza spliff 36. AFX - Outage. shit smothered (same on CAT 00897, 1997) 37. AFX - glock+onion 38. AFX - Outtake. (throatie) # Nokogiribiki Weird broadcast radio since 2005. Eine Sendeübernahme von Radio Blau aus Leipzig. * https://nokogiribiki.tumblr.com

Unsubscribe Ep38 - Shot Show Hangover Ft. @Brandon Herrera and @Garand Thumb Play Button THIS IS ALL THAT WE MANAGED TO FILM AT SHOT SHOW, WE PLANNED FILMING LIKE 8 PODCASTS BUT WE GOT TOO DRUNK. OOPS. SO YOU JUST GET @Brandon Herrera AGAIN ALSO WE STOLE @Garand Thumb PLAY BUTTON BECAUSE HE IS TOO FANCY FOR OUR PODCAST. aka we got drunk and didnt ask him. ------------------------------ WHERE TO LISTENSpotifyhttps://spoti.fi/2Ye8YOUApple Podcastshttps://apple.co/3cbqY4kAmazonhttps://amzn.to/2YbzQiaGoogle Playhttps://bit.ly/2YcWmaDStitcherhttps://bit.ly/3cbnY8o ------------------------------ Follow the Cast of Unsubscribe -Baddie- @Baddie Streams https://www.twitch.tv/baddiehttps://twitter.com/BaddieStreamshttps://www.instagram.com/baddiestreams/https://www.youtube.com/baddiestreams -DonutOperator- @Donut Operator @Donut Vlogerator https://www.youtube.com/channel/UCwkm_Wcyh0pc7UUmZZfL-6whttps://www.instagram.com/donutoperator/https://www.twitch.tv/DonutOperatorhttps://twitter.com/DonutOperator -Eli_Doubletap- @Eli Doubletap https://www.instagram.com/eli_doubletap/https://www.twitch.tv/Eli_Doubletaphttps://twitter.com/Eli_Doubletaphttps://www.youtube.com/c/EliDoubletap ------------------------------ Edited by Fluckhttps://www.twitch.tv/fluck

Dear Listener, Welcome to our first solo episode of 2022! We're diving in with a conversation about fullness cues. More specifically, how to handle those times when you're feeling uncomfortably full after an eating experience. I think we can all agree that speaking harshly to yourself in those moments doesn't help, but turning down the volume on that inner negative voice is much easier said than it is done. So tune in to hear the five biggest reminders I have for you to navigate the feeling of unpleasant fullness with more self-compassion. Can't wait for you to hear these! Yours Chewly, Claire Join our free, private FB community: https://clairechewning.com/community Work with Claire 1:1: https://clairechewning.com/work-with-me The self-paced, online Intuitive Eating Discovery Course: https://clairechewning.com/intuitive-eating-course (Use code “PODCAST” at checkout for 10% off of your enrollment investment

Resident Joe is caught on a hot mic calling FOX reporter Peter Doocy "a stupid son of a bitch." Oops, so much for respect and unity Pop Pop.

The last five years highlighted the racism, xenophobia, and islamophobia which exists in American society—but it didn't start then. In his new book Go Back to Where You Came From And Other Helpful Recommendations on How to Become American, my guest Wajahat Ali takes a clear-eyed and very funny look at this dark part of our American identity. "Wajahat Ali's deeply personal and keenly perceptive memoir is a clear-eyed account of his American immigrant experience.… We are all fortunate to be on the receiving end of not only his intellect, but his humanity and heart." ― Katie Couric, Emmy Award-winning journalist "This is the book I've been hoping Wajahat Ali would write for ten years―hilarious, stylistically fearless, deeply humane." ― Dave Eggers, author of The Every "Wajahat Ali has already proven that he is the fastest mind on TV. Now his fans can sample his brilliance on the page." ― Ishmael Reed, author of The Terrible Fours "This book is a tour de force―equal parts tragedy and laugh-out-loud comedy. With brazen wit, rigorous analysis, and searing insight, Wajahat Ali speaks to the first-generation American's dilemma of being both ‘us' and ‘them.'" ― Suleika Jaouad, author of Between Two Kingdoms "A hilarious and heartwarming treatise on what it truly means to be American in the twenty-first century. You'll be laughing so hard you won't even notice the inevitable Islamic takeover of America! Oops, I've said too much." ― Reza Aslan, author of God: A Human History "Wajahat Ali brilliantly and lovingly unpacks the complicated history and urgent lived experience of being otherized in America.… [A] rich feast for all the senses―a must-read." ― S. E. Cupp, author of Losing Our Religion "This powerful and moving book is, at its heart, a love story. The beloved, flawed and tragic -- so flawed, so tragic -- is America. The lover's hope is always undermined. And yet his hope somehow endures." ― Mohsin Hamid, author of Exit West "Find a place on your bookshelf between Mark Twain and James Baldwin. Read this book before putting it there." ― Timothy Snyder, author of On Tyranny "With wit and charm, Ali has delivered a masterful meditation on growing up brown in America...An intoxicating rejection of cynicism in the face of existential threats to multiracial democracy, and a clear-eyed call to arms against the forces seeking to stop the expansion of American democracy. An affirmation of the country America could be." ― Mara Gay, editorial board, New York Times "In prose at times hilarious and at other times deeply moving, Wajahat Ali chronicles a uniquely American experience. All will benefit from reading his story." ― Representative Ilhan Omar "Full of wisdom and compassion, not to mention Ali's signature humor. As educational as it is entertaining. I wish my nine-year-old immigrant self had this book when the playground kids were telling me to go back where I came from.”" ― Gary Shteyngart, author of Our Country Friends "A tender knife-sharp analysis of racism . . . personal, painful, familial, and global" ― Juan Felipe Herrera, United States Poet Laureate Emeritus --This text refers to the hardcover edition. --- Send in a voice message: https://anchor.fm/alyssa-milano-sorry-not-sorry/message

Ep 174FUp: The most powerful iMac G4 ever made. Modification and Hackintosh (hvala, Jovan LukićFUp: Apple loses second key chip engineer, this time to MicrosoftMicrosoft Releases Office for Mac Update With Full Apple Silicon Support in ExceliOS 15.2.1 and iPadOS 15.2.1 Fix Messages Bug and HomeKit VulnerabilityApple Floated as Potential Buyer of PelotonGruber: Leaker Sinks Peloton Stock With Confidential InformationApple CEO Tim Cook personally lobbying against the American Innovation and Choice Online ActApple submits plan to allow alternative App Store payment systems in South KoreaPUBG developer sues Apple over alleged rip-offs being sold in the App StoreApple Music is second worldwide with 15% market shareGoogle requiring all ‘G Suite legacy free edition' users to start paying for Workspace this yeariCloud+ with custom email domain.TidBITS o prednostima i manamaDruge opcije:ProtonMailFastMailTutanota (hvala, Ivan Jelić)Mark Flider: 15 years ago, Steve Jobs introduced the iPhone. It was probably the best presentation ever made, by anyone.It used custom animations that I wrote just for him.And Keynote (the presentation software he used, and I worked on) hard crashed both the main and backup machine. Oops!ZahvalniceSnimljeno 22.1.2022.Uvodna muzika by Vladimir Tošić, stari sajt je ovde.Logotip by Aleksandra Ilić.Artwork epizode by Saša Montiljo, njegov kutak na Devianartu.Skrivenost/Latency2010.ulje na platnu/oil on canvas80 x 60 cmprivatno vlasništvo/private collection

The vibes are exquisite in what Cody calls “the best episode ever” as our hosts play a drinking game throughout the conversation. Amid a volcano-induced tsunami, Stephanie finds herself smack dab in the middle of a surf competition begging the question, what is more intimidating? Natural disaster or not placing 1st?With representation more important now than ever, we wonder who will be repping go-go boot clad women as the Green M&M loses her famous kicks in this episode that can't be missed.

Homer - The Odyssey - Episode 3 - Odysseus And The Cyclops Don't See Eye To Eye!   I'm Christy Shriver, and we're here to discuss books that have changed the world and have changed us.      And I'm Garry Shriver and this is the How to Love Lit Podcast.  This is our third episode covering Homer's Odyssey, and Christy, are we finally getting to Odysseus this week?     Yes- We finally meet our title character- it was an odyssey. Pun pun-     Oh my- here we go….    I know, and we get to see wordplay this week as well- although word play through translation is not exactly the same but the Greeks did a lot of it, and not just in the Odyssey, so it's nice to get just a little taste.    How interesting.    I know, it really is.  Homer, even though writing in verse that has meter, does not rhyme, but he does use word play- which may or may not be called a pun- but it does play around with the meaning and sounds of different words.      In episode 1 we discussed a lot of the historical context both of the period in which the story is set, but also of the mysterious writer, the supposed blind bard, we have always called Homer.   I did notice we do finally get to mee the blind bard of the Odyssey, the one the ancients think might be based on our poet, but I'm not sure I would have even paid much attention to that character if we hadn't talked about Demodocus being the model for Homer, previously.      No, I agree.  I wouldn't have either.  It's kind of an interesting literary concept, at one point there is a bard telling a story about a bard telling a story and then there's the story- so a story within a story within a story- talk about complicated.      Yeah- let's just move on.  In episode 2, we discussed Telemachus and his coming of age story that we call the Telemachy- or books 1-4.  In that portion of the story, we learned that swarms of suitors have overrun the family home back in Ithaca while Odysseus is away.  Telemachus' mother, Odysseus's wife, Penelope is being pressured to pick one of these suitors to be her husband, an act which would give the selected suitor a claim to be king or chieftain of Ithaca, perhaps even a contested heir to her fortune, leaving Telemachus' life in extreme danger.  We saw that Penelope tricked the suitors by claiming she would marry one of them after she weaved a funeral shroud for her father-in-law, Laertes.  During the day she would weave, but at night she would unravel her work.  For three years this worked until one of her ladies' maids gave her up.  It is at this point that we enter the story of Telemachus.  Athena visits him, first in the shape of an old friend of Odyssseus', Mentes,  but then into another man named Mentor.  She encourages Telemachus to take charge of his own future- to go out in the world and try to find out what has happened to his father by visiting his father's old war buddies.  Telemachus listens to Athena and visits two places: Pylos and Sparta.  Here he learns very little, honestly, about what happened to his father, but what we do see is Telemachus coming into his own.  We see his confidence and sense of self develop to the point that he seems quite a different person as he journeys back home ready to confront the very dangerous challenge of taking control over his own home or really retaking a kingdom that has been taken away from him.    Yes- and today we will see where Odysseus has been this whole time.  The goal today is to get through book 9, maybe start book ten, which is kind of a chronological boomerang really.  We start book 5 twenty years after Odysseus has left home.  Calypso is forced to release him which she does.   Poseidon is outraged and reacts.  Garry let's read Poseidon's response.    “I'll give that man his swamping fill of trouble!” With that he rammed the clouds together- both hands clutching his trident- churned the waves into chaos, whipping all the gales from every quarter, shrouding over in thunderheads the earth and sea at once- and night swept down from the sky- East and South Winds clashed and the raging West and North, spring from the heavens, roiled heaving breakers up- and Odysseus' knees quaked, his spirit too; numb with fear he spoke to his own great heart: “Wretched man- what becomes of me now, at last?     And of course the answer is- you're not to die yet.  The gods will see to it.   He is shipwrecked and then found naked on the beach by Nausicaa, the daughter of King Alcinous ruler of the incredibly gracious and skilled Phaeacian's.    And of course, it is through these people, we see an incredible example of what the Greeks call Xenia and basically how Homer defines what it means in this world to be a good person. In the Homeric world, or perhaps the ancient Greek world, if we can generalize, what makes a person good or bad is not the same as we think of today. So, Garry, just to get us started, as a concept, what is Xenia.    Well, it's a concept of hospitality that is an extremely complex and developed social  institution in the ancient Greek world.  If we break the word down- the word xenos- that word means both guest-friend or guest-stranger.  If you think of the word xenophobia- it means you have fear or hatred of strangers.  So xenia is how you receive or treat strangers in your community, your oikos, your household.   Well executed xenia solidified relationships between peoples; it created alliances, and could often be the difference between life and death.  It was also religious- one of Zeus' names is Zeus Xenios because he was the god that embodied a moral obligation to be hospitable to foreigners or strangers.       And it's that moral element that is so central to so much of what we should understand about why things happen the way they do in the Homeric world.  In Homer's world, hospitality drives morality.  It is in the hosting, receiving, gift-giving and relationship building that is pushing forward the movement in the world.  It's what gets you in favor or in trouble with the gods.  If you are a good host and/or good guest, you are a good person.  If you are a bad host/ bad guest, you are a bad person.  To me it really seems to be that simple.  The moral code that determines your place is life is not based on the ten commandments or something like that- it is not based on lying, or stealing or even murdering- things that we use to define morality. If you think about it, all three of those things Odysseus does all the time and is even admired for how well he does them.  The gods are proud that he is cunning.  He brags about sacking villages.  The climax of the book involves broadscale murder (there's a slight spoiler, if you are 3000 years behind the times and don't know the ending).  There is definitely no morality around sex at all.  The definition of who you are as a person is very dependent on something else and that something else is what the ancient's called xenia- this concept of being a good host and being a good guest.  Garry, from our standpoint today, that seems weird.  We don't value hospitality in this way at all, and on the other side, we look poorly on people who are pirates, liars, thieves, or adulterers.     True- and it is a very interesting way of thinking about things- and something we should think about.  Of course, obviously and I know you weren't being exclusionary, but there are other values emphasized in Homer's epics- respect for the gods, being a wise and moderate person, not to mention, you are supposed to avenge the death of family members, that is also part of the moral code, but your point cannot be overstated more- the importance of hospitality is essential to success in life, and there are very good and obviously practical reasons for this.      Just to clarify what we're talking about- even before we get to book five, we've seen examples of this in every chapter of the epic already.  Telemachus was a good host to Mentes. Nestor and Menelaus were amazing hosts to Telemachus ,and now Alcinious is even more gracious then the other two and in fact brings Odysseus home, even though it will cost him dearly, as we'll see at the end.      True, but the concept of Xenia is not just inherent in Greek culture.  It was important in other cultures in other parts of the ancient world as well.  If you want an example that you might be familiar with from this time period and if you familiar with Biblical text we see similar things in the book of Genesis in the Bible. Abraham is very concerned about being a good host as well as a good guest and we see various interactions of him being a guest when he wanders around Canaan.  And just as the gods in the Odyssey punish and murder those who do not respect the rules of hospitality, there is a perspective to suggest that the Hebrew God of the Bible also punishes those who do not respect the rules of hospitality- just look at Sodom and Gomorrah and how the destruction of that town is set up by the abuse of guests in the community.  How you receive strangers very much defines your humanity in many cultures and has for a long time.  This idea of morality being connected to hospitality is very ancient and deeply embedded in various ancient cultures.      Well, in the Odyssey there are at least 12 hospitality scenes of all kinds. We see examples of bad hospitality as well as examples of good hospitality- In book five, we see both juxtaposed against each other almost back to back.  In Polyphemus the Cyclopes- we see almost a perfect example of a bad host.   But he isn't the first character in the book to violate the rules of Xenia- for that we don't need to look further than book one and the suitors.  Those guys are clearly terrible guests, terrible humans and we don't feel a bit sorry for them when they get what's coming in the end.  But before we get t here, let's start with the concept of xenia itself.  What is this idea of being a host which is so central to the story?  How should we understand it in terms of culture so we can then extrapolate cross-culturally?  Why is hospitality important to the degree that it is a motif in almost every book of this epic.  In fact, it's a type scene.     A type-scene.  That's a new term.  Christy, what's a type scene?    A type scene is a scene that you see over and over again.  It's kind of like a pattern.  But you become familiar with it to the point that you can recognize differences in how different people practice the same pattern or the same type, so to speak. For example, in the Iliad, how a person puts on his armour is a type scene- it happens over and over and you can see the pattern with the differences.  Holding sacrifices is another type-scene- it happens all the time.  There are many kinds of type-scenes at the disposal of the bard, he uses them to set up the story. We don't have time to feature all of them, obviously, but I want to talk about hospitality because it's so relevant to what the Odyssey is all about, in my view.   Like I said before, in the Odyssey there are at least 12 hospitality scenes.  So, that's a lot of emphasis- it sets off the plot in chapter 1, it creates complications throughout, and in some ways how we can watch Odysseus evolve as a character.  We watch him develop as we watch him reveal who his is in these various interactions with his different hosts.  So back to this idea of gift-giving and hospitality.  What are your thoughts- just in general?    Well, first of all, let's recognize that we are in an ancient world consisting of mostly isolated islands.  There are no hotels, no restaurants, and not even any money.  The Chinese are given credit in being the first to come up with money, but that wasn't until around 770 BCE.  So, just in that regard, you can see how important relationships would be just on a survival level.  Bartering, obviously did exist. But, in general, if a person is going to travel, he will have to rely on mercy from other people to survive, and of course that's how ancient societies worked.  Again, a parallel example of ancient text would be the stories of the Old Testament in the Bible, if you recall.  People went into the lands of others and threw themselves at the mercies of those rulers.  So in some sense, the idea of emphasizing hospitality on a macro-scale makes sense- I'll host you if you'll host me.  But that doesn't answer the second question, why all these gifts?  You would think that the one giving the gift would be the one being hosted.  He/or she after all is the one being fed, being clothed.  You would also think that if you were a rat of a human, and so many of us are rats, you could just go around and exploit person after person.  And notice, and you can see this through the many scenes of hospitality, you are supposed to feed and bathe a guest BEFORE you even ask their name or their business.  THAT was the ethics of the tradition.  So, the question, is why give gifts?      Well, of course, I don't know, but the obvious first pass guess, again, maybe is the idea of reciprocity.  I am going to host you today knowing that one day that balance of power may shift and I may need your hospitality.  I'll give you a good gift, so that one day you will give me a good gift- that sort of thing.  Except, as I say that out loud, it does fail the say out loud test.  After going through the Christmas season, if you are a person who practices gift-giving, you know there are always those people that shaft you.  How many of us have been in situations where we drew names, and you're supposed to buy a gift for the person that you get their name and spend a certain dollar amount.  Well, we all know that person or persons who will shaft whoever they draw.  They will justify it by saying to themselves, “Well, the original price was the money limit, I just got it on sale and they'll never know.”- which of course is bogus because we always know.   But sometimes people don't bother even doing that.  They may just shaft you because there is nothing anyone is going to do about it at a holiday party.  That sort of thing.  I can't imagine the Greeks not having those schumcks- well, we know they have those schmucks- they've moved into Penelope's house in book one.  So, I guess I'll ask you- why give gifts?  I can see how it would make a society a better and kinder place, but I can't see how and why it works.  It seems to go against human nature.    True- Of course the first reason is it makes you a good person and it pleases the gods- and we want to be good people and we all want to please the gods.  We just do.  Even those of us who unfortunately find ourselves incarcerated for terrible things we've done to other people, will likely NOT EVER want to give up the idea that we are good people.  We want others to see that in us, and we want the gods to see that in us.  And of course, we see that idea here- the gods will reward generosity and hospitality.      Which brings us to Alcinous' daughter- she truly is depicted at being a wonderful human being.  She's brave and she's generous.  Let's read where Odysseus approaches her and begs for mercy.    Page 174    But of course, as we can clearly see here.  Naussicaa, the princess, is an exceptional person.  Not very many of us are as wonderful as this girl, so I don't think reciprocity fully explains the concept of gift giving.  Of course, I don't know for sure, but one perspective  to consider here is in watching the balance of power.  Remember, primitive societies didn't have InterPol, or the United Nations, or anything like that, but that doesn't mean they didn't still have complex systems of interacting. When you show up on someone's shore, the smart thing for the person on the shore to do is to kill you at the get go- and in fact, that's what happened a lot.   Man, after all is a warring being, and societies historically war. And that is where I see the value of gifts.  The currency of today and the currency of the ancient world in one sense is the same- fame, reputation, power, glory, status- isn't that what people buy with their money- a higher place on the hierarchy?   Today, we literally BUY it with money.  We can and do buy VIP seating, VIP lounges, private planes, exclusive clubs, name brands and for what?  These things showcase that we are more important than other people- our social rank- no matter how egalitarian we claim to be.  In the ancient world just as today, greatness is defined by reputation, fame, glory- and how that happens is by giving and getting.  It's builds reputation.  If we look at what actually happens in this particular story what I notice is that for one- These tokens matter economically.  And this particular family, which is described as being a cunning family, are good at amassing wealthy by being recipients of great gifts.  We certainly see it in Odysseus.  But we also see it in Telemachus who actually negotiates his gifts, but and even Penelope is very smart in collecting gifts and building her own wealth.   But let's look at it from the other side of things.  What the giver gets in exchange is also of great value.  The giver of each gift is sending with the recipient a signal to everyone who sees the gift a message of his great reputation.  Everyone is reminded that King Menelaus is great every time he sees an artifact that came from his kingdom.  Everyone is reminded not to mess with a man as grand as can afford to give away something as great as this gifr or that gift.  But the giver is also building personal indebtedness that can extend multi-generationally.  We saw that when Telemachus visited his fathers' friends.  This networking extends reputation and gift exchange is also a tool with  which hierarchy is established.      Well, in the case of King Alcinous, he had a tremendous reputation for greatness and was, and I quote, “obeyed like a god”.   We could talk quite a bit about this banquet  King Alcinous and Queen Arete threw in honor of their guest:  the recognition scene, the games, etc.  but I want to jump ahead to the cyclopes- which is just fun to read.  And of course, it brings up one of the reasons why this book is so popular.  It's readable at every level.  We can read it for some psychological or anthropological understanding of humanity, but it's also just as fun and worthy to read the gory description of a dude poking out another dude's only eye.  So, jumping straight to book 9, the bard, in book eight, has been telling Odysseus' story but now Alcinous is making Odysseus tell his own story and finally Odysseus confesses his identity.      I am Odysseus, son of Laertes, known to the world for every kind of craft- my fame has reached the skies.  Sunny Ithaca is my home.  Atop her stands our seamark, Mount Neriton's leafy ridges shimmering in the wind.      And on he goes describing his homeland.  The first story he tells is about him sacking and plundering Cicones- sacking the city, killing the men.  By our standards, its sheer pirating, but it's not a shameful story in this context.  The shame came at the end when his stupid men got drunk and allowed the Cicones to get them back.  He says “out of each ship, six men-at-arms were killed.”  So, there's the example of how a lot of these interactions between peoples go- people warring against invaders.  But after the Cicones, he gets to the Lotus eaters.    The Lotus eaters' story is famous too, and I love how the Percy Jackson movie portrayed the Lotus eaters as being a casino in Las Vegas, and the men just kind of losing track of time as so many have in those corridors that connect the Pallazzo to the Venetian or Bally's to Paris.      I agree- Las Vegas is perfect.  The passage about the lotus eaters is a short passage especially for how well known it is, let's remember those famous Lotus Eaters.    Page 214    You know, I've heard this passage described as people high on drugs, but we may be too quick to go the route of mental incapacity.  When the men go back to their boat, they are aware that they are being forced to leave, and they even cry about it.  It's not their perceptions that are impaired; it's their will that's impaired.  The bedazzling experience of the present has totally obliterated any sense of time as well as any concern about other experiences in the future.  It's a metaphor for a lot of things beyond drugs that have this effect- although drugs definitely unfortunately do this in the extreme.      Ha!  I would say so- can we say tik tok!!  You know, our good friend, Cristiana, the other day got on tiktok, and let me say she's my age, so we're not talking about a child.  Anyway, her complaint about it was that she spent an hour drifting through video after video.  She was entertained for sure, but after an hour she looked up and realized could not tell you one thing that she had seen.  The videos were too short to even stick in her short term memory.  She was annoyed because she couldn't account for the time- she remarked that she literally had nothing to show for it- it went the way of the lotus eaters.    Ha!  So true- I guess Instagram and Facebook aren't much better,  but let me ask you this- is that an example of good xenia or bad xenia?     HA!  Well, I think of it as just a little sidebar until we get to the big xenia story-  the story of the Cyclopes-     A couple of things to notice as we compare the story of Polyphemus as host to the story about King Alcinous and Queen Arete and their reception of Odysseus.  With the Phaeacians, we see a positive example of what it means to be a good person.  We see a great and confident leader who has built a good community.  Homer is going to juxtapose that with this community that does not work well.  We are going to see what it means to be bad- a bad person, a bad leader and live in a bad society.  Remember when I said that a type-scene is a scene where you recognize a pattern.  Well, the pattern to receive a guest has been established a bunch of times already starting in book one now through book 8.  And Polyphemus does everything absolutely wrong.  He's the very opposite of a good person, and the Cyclopes society is the opposite of a good society.  Besides the hospitality type-scene- we also have an assembly which is another type-scene.  We've had a bunch of assemblies already as well- remember when Telemachus called an assembly, they met and passed around the scepter and all that, well Polyphemus is going to try to call an assembly, but it doesn't go well either because nothing these barbaric people do is worth anything.  They are awful in all ways.    So, in a traditional hospitality scene- you're supposed approach the visitor, welcome the visitor, seat and feed the visitor, offer the visitor a drink, then ask the visitor's name, exchange information, entertain the visitor, allow the visitor to bath, then sleep, try to detain the visitor give the visitor a gift, make a sacrifice  to the gods and finally escort him to the next destination.  That's exactly what we've already seen over and over again up to this point.  With that in mind, let's look at how Polyphemus treats civilized life.  First of all, Polyphemus isn't there at first, but when he gets there, before anything else, he asks them who they are.      Let's read it.     Page 219    Stop after other men then read his response    And of course they answer him, not by stating who they are but by saying who've they've been with and asking for a guest-guest.      Which  didn't go well.    No- let's read how it goes.     P 220      Instead of feeding the guests, he eats them.  It can't get worse than that, but there are more oppositions, instead of the host offering the guests wine, Odysseus offers Polyphemus wine.  And instead of Odysseus revealing his identity, he conceals it- He tells Polyphemus his name is Nobody or No man depending how your book translate it- And of course Polyphemus  likes the wine so much he decides to give Odysseus or Nobody a guest gift, but the gift is terrible.    Page 222    The scholars tell us that this scene actually has four examples of word play in the Greek, but the translation only comes across as one.  It's kind of fun that it works.  But it is this word play that has interested so many and sets the primary complication for the ten years of Odysseus' life.    Odysseus manages to get Polyphemus drunk and he and his crew stab him in the eye, very infeasibly with a piece of wood they made out of embers (don't try to explain that scientifically).  Let's read it.    Page 223    And of course, Odysseus gets away by being smart, patient, more cunning- the things that the gods reward.  Polyphemus is left to cry out to his father Poseidon- which of course in some ways is the correct idea, you are supposed to pray to the gods before your guests leave, but not like this.  And of course, finally Odyssey leaves not being escorted but by fleeing with his life as Polyphemus throws boulders at him.  Ironically, however,  Odysseus would have gotten away, and we wouldn't have had a story except for the lines that Odysseus blurts out once he's safely far enough away where he thinks he's escaped.    Page 227  .  He just can't be a nobody.  He had to tell him who he was.  He wanted him to know.  And isn't that what takes all of us on so many personal Odysseys.  We just can't be a nobody.  We would lose something in our humanity like that.  It's about identity.  That's what we're looking for in some sense.  It's what the whole of life experience is about in many ways.  Who are we?  We are NOT a nobody- at least we hope we're not- we hope to be a somebody to somebody.  How well Homer knows us.     Indeed.  It's an idea that we see Homer taking with us for the rest of the books.  Odysseus will reclaim his name.  He will define it. It's what defines your home- the place where you are somebody.  But another point to make, and I don't want to leave this discussion of uncivilized people without making mention of one other thing.  There is something very interesting to notice in Poseidon's prayer.  You know, if I had been blinded, and I had a magical father with powers, I might pray for my eyesight back.  That would be the most helpful thing moving forward, at least you'd think.  But that's not what Polyphemus does.  Let's read it.    Page 228    He'd rather have revenge than his own eyesight.      Indeed- it's fascinating to me- that when Homer wants to finish his description of what a pitiful example of a living breathing low-life is, what a totally uncivilized society looks like- he starts by saying it's a group of people who do no work, produce nothing, have no assemblies, do not live well in community, but he ends it with a prayer to seek vengeance in a final breath.      Ha!  I guess so. The worst of in us all played out- a bad person would rather hurt another person that move forward.   Well, off Odysseus goes.  He thinks he's caught a break at the beginning of book 10.  He reaches the home of the god Aeolus- a giant floating island.  And this god receives him well- another hospitality scene.  They go through all the things, and he gets a great parting gift.  He gives him a sack of wind.  Aeolus binds the winds from all the corners of the earth except the West Wind that blows Odysseus all the way to Ithaca.  For Nine days he sails non stop.  He can see men tending fires on the beaches of his hometown.  He's made it.  He can rest, but his men are greedy.  Right before they get there, while Odysseus is asleep, the shipmates open the bag wanting to sneak out treasure while Odysseus isn't watching.  When they open the bag all the winds come out at once, and they get blown all the way back to King Aeolus.  Oops.  Odysseus asks him to put the winds back in the bag.  This time, Aeolus says, sorry but no.  Instead this is what he said- let's read King Aeolus lines.    , “Away from my island- fast- most cursed man alive! It's a crime to host a man or speed him on his when the blessed deathless gods despise him so.  Crawling back like this-it proves the immortals hate you! Out- get out!'    And so off he goes- and I guess it's time for us to head out as well.  Next episode we'll pick up with Circe, and go through the rest of Odysseus' wanderings.  I also want to talk a little bit about the role of women in the books, as we'll meet a couple more.      Sounds good.  So, we'll call it a wrap for today.  Thanks for listening.  WE hope you're enjoying our discussions as we work our way through this influential classic.  As always, we hope you will honor us by sharing an episode with a friend either by text email or word of mouth.  Please leave us a five star rating on your podcast app and of course visit us at howtolovelitpodcast.com, where we have plenty of instructional materials if you are a teacher or student.  Also, follow us on any or all of our social media: Instagram, facebook, linked in, and if you'd like to receive our monthly newsletter, please email Christy at christy@howtolovelitpodcast.com.                       

***** Reviews and subscriptions help us out so much. If you enjoyed the show, make sure to subscribe and leave us a review on iTunes. ***** The HP Podcast is brought to you by HandsomePhantom.com where you can find all sorts of video game related content. Follow us on Twitter! Twitter.com/HandsomePhantom Twitter.com/BenSmith2588 Twitter.com/csfdave Twitter.com/_gloriousginger Learn more about your ad choices. Visit podcastchoices.com/adchoices

Episode #519 features the return of accomplished writer and creator Gregg Hurwitz from Knighted, which is being released by AWA Studios! Hurwitz is a terrific novelist, and his newest book, Dark Horse, is coming soon! We touch on that, but then we go in depth into Knighted, which is described this way: “In this action-packed adventure set in the universe of The Resistance, Gregg Hurwitz (The Dark Knight, Vengeance of Moon Knight), Mark Texeira (Ghost Rider, Wolverine), and Brain Reber (X-Men: Legacy, Spider-Man/Deadpool) introduce a masked vigilante for the 21st Century. Bob Ryder is a hapless bureaucrat whose bad luck streak comes to a crescendo when he accidentally kills the city's masked vigilante, The Knight. Oops. Now, Bob is forced to take on the mantle of the legendary hero before the city descends into chaos. Good thing he's got The Knight's former butler/assistant to show him the ropes.” The third issue just was released, and it's a great adventure series, so I highly recommend you pick it up… after you listen to my fun interview with Gregg! Don't miss it! Show your thanks to Major Spoilers for this episode by becoming a Major Spoilers Patreon member. It will help ensure Wayne's Comics Podcast continues far into the future!

About MaciejMaciej Winnicki is a serverless enthusiast with over 6 years of experience in writing software with no servers whatsoever. Serverless Engineer at Stedi, Cloudash Founder, ex-Engineering Manager, and one of the early employees at Serverless Inc.Links: Cloudash: https://cloudash.dev Maciej Winnicki Twitter: https://twitter.com/mthenw Tomasz Łakomy Twitter: https://twitter.com/tlakomy Cloudash email: hello@cloudash.dev TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part byLaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visitlaunchdarkly.com and tell them Corey sent you, and watch for the wince.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Cloud Economist Corey Quinn. And my guest today is Maciej Winnicki, who is the founder of Cloudash. Now, before I dive into the intricacies of what that is, I'm going to just stake out a position that one of the biggest painful parts of working with AWS in any meaningful sense, particularly in a serverless microservices way, is figuring out what the hell's going on in the environment. There's a bunch of tools offered to do this and they're all—yeee, they aspire to mediocrity. Maciej, thank you for joining me today.Corey: Welcome to Screaming in the Cloud. I'm Cloud Economist Corey Quinn. And my guest today is Maciej Winnicki, who is the founder of Cloudash. Now, before I dive into the intricacies of what that is, I'm going to just stake out a position that one of the biggest painful parts of working with AWS in any meaningful sense, particularly in a serverless microservices way, is figuring out what the hell's going on in the environment. There's a bunch of tools offered to do this and they're all—yeee, they aspire to mediocrity. Maciej, thank you for joining me today.Maciej: Thank you for having me.Corey: So, I turned out to have accidentally blown up Cloudash, sort of before you were really ready for the attention. You, I think, tweeted about it or put it on Hacker News or something; I stumbled over it because it turns out that anything that vaguely touches cloud winds up in my filters because of awesome technology, and personality defects on my part. And I tweeted about it as I set it up and got the thing running, and apparently this led to a surge of attention on this thing that you've built. So, let me start off with an apology. Oops, I didn't realize it was supposed to be a quiet launch.Maciej: I actually thank you for that. Like, that was great. And we get a lot of attention from your tweet thread, actually because at the end, that was the most critical part. At the end of the twitter, you wrote that you're staying as a customer, so we have it on our website and this is perfect. But actually, as you said, that's correct.Our marketing strategy for releasing Cloudash was to post it on LinkedIn. I know this is not, kind of, the best strategy, but that was our plan. Like, it was like, hey, like, me and my friend, Tomasz, who's also working on Cloudash, we thought like, let's just post it on LinkedIn and we'll see how it goes. And accidentally, I'm receiving a notification from Twitter, “Hey, Corey started tweeting about it.” And I was like, “Oh, my God, I'm having a heart attack.” But then I read the, you know—Corey: Oops.Maciej: [laugh]. Yeah. I read the, kind of, conclusion, and I was super happy. And again, thank you for that because this is actually when Cloudash kind of started rolling as a product and as a, kind of, business. So yeah, that was great.Corey: To give a little backstory and context here is, I write a whole bunch of serverless nonsense. I build API's Gateway, I hook them up to Lambda's Function, and then it sort of kind of works. Ish. From there, okay, I would try and track down what was going on because in a microservices land, everything becomes a murder mystery; you're trying to figure out what's broken, and things have exploded. And I became a paying customer of IOpipe. And then New Relic bought them. Well, crap.Then I became a paying customer of Epsagon. And they got acquired by Cisco, at which point I immediately congratulated the founders, who I know on a social basis, and then closed my account because I wanted to get out before Cisco ruins it because, Cisco. Then it was, what am I going to use next? And right around that time is when I stumbled across Cloudash. And it takes a different approach than any other entity in the space that I've seen because you are a native Mac desktop app. I believe your Mac only, but you seem to be Electron, so I could be way off base on that.Maciej: So, we're Linux as well right now and soon we'll be Windows as well. But yeah, so, right now is Mac OS and Linux. Yeah, that's correct. So, our approach is a little bit different.So, let me start by saying what's Cloudash? Like, Cloudash is a desktop app for, kind of, monitoring and troubleshooting serverless architectures services, like, serverless stuff in general. And the approach that we took is a little bit different because we are not web-based, we're desktop-based. And there's a couple of advantages of that approach. The first one is that, like, you don't need to share your data with us because we're not, kind of, downloading your metrics and logs to our back end and to process them, et cetera, et cetera. We are just using the credentials, the AWS profiles that you have defined on your computer, so nothing goes out of your AWS account.And I think this is, like, considering, like, from the security perspective, this is very crucial. You don't need to create a role that you give us access to or anything like that. You just use the stuff that you have on your desktop, and everything stays on your AWS account. So, nothing—we don't download it, we don't process it, we don't do anything from that. And that's one approach—well, that's the one advantage. The other advantage is, like, kind of, onboarding, as I kind of mentioned because we're using the AWS profiles that you have defined in your computer.Corey: Well, you're doing significantly more than that because I have a lot of different accounts configured different ways, and when I go to one of them that uses SSO, it automatically fires me off to the SSO login page if I haven't logged in that day for a 12 hour session—Maciej: Yes.Corey: —for things that have credentials stored locally, it uses those; and for things that are using role-chaining to use assuming roles from the things I have credentials for, and the things that I just do role assumption in, and it works flawlessly. It just works the way that most of my command-line tools do. I've never seen a desktop app that does this.Maciej: Yeah. So, we put a lot of effort into making sure that this works great because we know that, like, no one will use Cloudash if there's—like, not no one, but like, we're targeting, like, serverless teams, maybe, in enterprise companies, or serverless teams working on some startups. And in most cases, those teams or those engineers, they use SSO, or at least MFA, right? So, we have it covered. And as you said, like, it should be the onboarding part is really easy because you just pick your AWS profile, you just pick region, and just pick, right now, a CloudFormation stack because we get the information about your service based on CloudFormation stack. So yeah, we put a lot of effort in making sure that this works without any issues.Corey: There are some challenges to it that I saw while setting it up, and that's also sort of the nature of the fact you are, in fact, integrating with CloudWatch. For example, it's region specific. Well, what if I want to have an app that's multi-region? Well, you're going to have a bad time because doing [laugh] anything multi-region in AWS means you're going to have a bad time that gets particularly obnoxious and EC2 get to when you're doing something like Lambda@Edge, where, oh, where are the logs live; that's going to be in a CloudFront distribution in whatever region it winds up being accessed from. So, it comes down to what distribution endpoint or point of presence did that particular request go through, and it becomes this giant game of whack-a-mole. It's frustrating, and it's obnoxious, and it's also in no way your fault.Maciej: Yeah, I mean, we are at the beginning. Right now, it's the most straightforward, kind of pe—how people think about stacks of serverless. They're think in terms of regions because I think for us, regions, or replicated stacks, or things like that are not really popular yet. Maybe they will become—like, this is how AWS works as a whole, so it's not surprising that we're kind of following this path. I think my point is that our main goal, the ultimate goal, is to make monitoring, as I said, the troubleshooting serverless app as simple as possible.So, once we will hear from our customers, from our users that, “Hey, we would like to get a little bit better experience around regions,” we will definitely implement that because why not, right? And I think the whole point of Cloudash—and maybe we can go more deep into that later—is that we want to bring context into your metrics and logs. If you're seeing a, for example, X-Ray trace ID in your logs, you should be able with one click just see that the trace. It's not yet implemented in Cloudash, but we are having it in the backlog. But my point is that, like, there should be some journey when you're debugging stuff, and you shouldn't be just, like, left alone having, like, 20 tabs, Cloudash tabs open and trying to figure out where I was—like, where's the Lambda? Where's the API Gateway logs? Where are the CloudFront logs? And how I can kind of connect all of that? Because that's—it's an issue right now.Corey: Even what you've done so far is incredibly helpful compared to the baseline experience that folks will often have, where I can define a service that is comprised of a number of different functions—I have one set up right now that has seven functions in it—I grab any one of those things, and I can set how far the lookback is, when I look at that function, ranging from 5 minutes to 30 days. And it shows me at the top the metrics of invocations, the duration that the function runs for, and the number of errors. And then, in the same pane down below it, it shows the CloudWatch logs. So, “Oh, okay, great. I can drag and zoom into a specific timeframe, and I see just the things inside of that.”And I know this sounds like well, what's the hard part here? Yeah, except nothing else does it in an easy-to-use, discoverable way that just sort of hangs out here. Honestly, the biggest win for me is that I don't have to log in to the browser, navigate through some ridiculous other thing to track down what I'm talking about. It hangs out on my desktop all the time, and whether it's open or not, whenever I fire it up, it just works, basically, and I don't have to think about it. It reduces the friction from, “This thing is broken,” to, “Let me see what the logs say.”Very often I can go from not having it open at all to staring at the logs and having to wait a minute because there's some latency before the event happens and it hits CloudWatch logs itself. I'm pretty impressed with it, and I've been keeping an eye on what this thing is costing me. It is effectively nothing in terms of CloudWatch retrieval charges. Because it's not sitting there sucking all this data up all the time, for everything that's running. Like, we've all seen the monitoring system that winds up costing you more than it costs more than they charge you ancillary fees. This doesn't do that.I also—while we're talking about money, I want to make very clear—because disclaiming the direction the money flows in is always important—you haven't paid me a dime, ever, to my understanding. I am a paying customer at full price for this service, and I have been since I discovered it. And that is very much an intentional choice. You did not sponsor this podcast, you are not paying me to say nice things. We're talking because I legitimately adore this thing that you've built, and I want it to exist.Maciej: That's correct. And again, thank you for that. [laugh].Corey: It's true. You can buy my attention, but not my opinion. Now, to be clear, when I did that tweet thread, I did get the sense that this was something that you had built as sort of a side project, as a labor of love. It does not have VC behind it, of which I'm aware, and that's always going to, on some level, shade how I approach a service and how critical I'm going to be on it. Just because it's, yeah, if you've raised a couple 100 million dollars and your user experience is trash, I'm going to call that out.But if this is something where you just soft launched, yeah, I'm not going to be a jerk about weird usability bugs here. I might call it out as “Ooh, this is an area for improvement,” but not, “What jackwagon thought of this?” I am trying to be a kinder, gentler Corey in the new year. But at the same time, I also want to be very clear that there's room for improvement on everything. What surprised me the most about this is how well you nailed the user experience despite not having a full team of people doing UX research.Maciej: That was definitely a priority. So, maybe a little bit of history. So, I started working on Cloudash, I think it was April… 2019. I think? Yeah. It's 2021 right now. Or we're 2022. [unintelligible 00:11:33].Corey: Yeah. 2022, now. I—Maciej: I'm sorry. [laugh].Corey: —I've been screwing that up every time I write the dates myself, I'm with you.Maciej: [laugh]. Okay, so I started working on Cloudash, in 2020, April 2020.Corey: There we go.Maciej: So, after eight months, I released some beta, like, free; you could download it from GitHub. Like, you can still download on GitHub, but at that time, there was no license, you didn't have to buy a license to run it. So, it was, like, very early, like, 0.3 version that was working, but sort of, like, [unintelligible 00:12:00] working. There were some bugs.And that was the first time that I tweeted about it on Twitter. It gets some attention, but, like, some people started using it. I get some feedback, very initial feedback. And I was like, every time I open Cloudash, I get the sense that, like, this is useful. I'm talking about my own tool, but like, [laugh] that's the thing.So, further in the history. So, I'm kind of service engineer by my own. I am a software engineer, I started focusing on serverless, in, like, 2015, 2016. I was working for Serverless Inc. as an early employee.I was then working as an engineering manager for a couple of companies. I work as an engineering manager right now at Stedi; we're also, like, fully serverless. So I, kind of, trying to fix my own issues with serverless, or trying to improve the whole experience around serverless in AWS. So, that's the main purpose why we're building Cloudash: Because we want to improve the experience. And one use case I'm often mentioning is that, let's say that you're kind of on duty. Like, so in the middle of night PagerDuty is calling you, so you need to figure out what's going on with your Lambda or API Gateway.Corey: Yes. PagerDuty, the original [Call of Duty: Nagios 00:13:04]. “It's two in the morning; who is it?” “It's PagerDuty. Wake up, jackass.” Yeah. We all had those moments.Maciej: Exactly. So, the PagerDuty is calling you and you're, kind of, in the middle of night, you're not sure what's going on. So, the kind of thing that we want to optimize is from waking up into understanding what's going on with your serverless stuff should be minimized. And that's the purpose of Cloudash as well. So, you should just run one tool, and you should immediately see what's going on. And that's the purpose.And probably with one or two clicks, you should see the logs responsible, for example, in your Lambda. Again, like that's exactly what we want to cover, that was the initial thing that we want to cover, to kind of minimize the time you spent on troubleshooting serverless apps. Because as we all know, kind of, the longer it's down, the less money you make, et cetera, et cetera, et cetera.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And—let me be clear here—it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small scale applications or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: One of the things that I appreciate about this is that I have something like five different microservices now that power my newsletter production pipeline every week. And periodically, I'll make a change and something breaks because testing is something that I should really get around to one of these days, but when I'm the only customer, cool. Doesn't really matter until suddenly I'm trying to write something and it doesn't work. Great. Time to go diving in, and always I'm never in my best frame of mind for that because I'm thinking about writing for humans not writing for computers. And that becomes a challenge.And okay, how do I get to the figuring out exactly what is broken this time? Regression testing: It really should be a thing more than it has been for me.Maciej: You should write those tests. [laugh].Corey: Yeah. And then I fire this up, and okay, great. Which sub-service is it? Great. Okay, what happened in the last five minutes on that service? Oh, okay, it says it failed successfully in the logs. Okay, that's on me. I can't really blame you for that. But all right.And then it's a matter of adding more [print or 00:14:54] debug statements, and understanding what the hell is going on, mostly that I'm bad at programming. And then it just sort of works from there. It's a lot easier to, I guess, to reason about this from my perspective than it is to go through the CloudWatch dashboards, where it's okay, here's a whole bunch of metrics on different graphs, most of which you don't actually care about—as opposed to unified view that you offer—and then “Oh, you want to look at logs, that's a whole separate sub-service. That's a different service team, obviously, so go open that up in another browser.” And I'm sitting here going, “I don't know who designed this, but are there any windows in their house? My God.”It's just the saddest thing I can possibly experience when I'm in the middle of trying to troubleshoot. Let's be clear, when I'm troubleshooting, I am in no mood to be charitable to anyone or anything, so that's probably unfair to those teams. But by the same token, it's intensely frustrating when I keep smacking into limitations that get in my way while I'm just trying to get the thing up and running again.Maciej: As you mentioned about UX that, like, we've spent a lot of time thinking about the UX, trying different approaches, trying to understand which metrics are the most important. And as we all know, kind of, serverless simplifies a lot of stuff, and there's, like, way less metrics that you need to look into when something is happening, but we want to make sure that the stuff that we show—which is duration errors, and p95—are probably the most important in most cases, so like, covering most of this stuff. So sorry, I didn't mention that before; it was very important from the very beginning. And also, like, literally, I spent a lot of time, like, working on the colors, which sounds funny, [laugh] but I wanted to get them right. We're not yet working on dark mode, but maybe soon.Anyways, the visual part, it's always close to my heart, so we spent a lot of time going back to what just said. So, definitely the experience around using CloudWatch right now, and CloudWatch logs, CloudWatch metrics, is not really tailored for any specific use case because they have to be generic, right? Because AWS has, like, I don't know, like, 300, or whatever number of services, probably half of them producing logs—maybe not half, maybe—Corey: We shouldn't name a number because they'll release five more between now and when this publishes in 20 minutes.Maciej: [laugh]. So, CloudWatch has to be generic. What we want to do with Cloudash is to take those generic tools—because we use, of course, CloudWatch logs, CloudWatch metrics, we fetch data from them—but make the visual part more tailored for specific use case—in our case, it's the serverless use case—and make sure that it's really, kind of—it shows only the stuff that you need to see, not everything else. So again, like that's the main purpose. And then one more thing, we—like this is also some kind of measurement of success, we want to reduce number of tabs that you need to have open in your browser when you're dealing with CloudWatch. So, we tried to put most important stuff in one view so you don't need to flip between tabs, as you usually do when try to under some kind of broader scope, or broader context of your, you know, error in Lambda.Corey: What inspired you to do this as a desktop application? Because a lot of companies are doing similar things, as SaaS, as webapps. And I have to—as someone who yourself—you're a self-described serverless engineer—it seems to me that building a webapp is sort of like the common description use case of a lot of serverless stuff. And you're sitting here saying, “Nope, it's desktop app time.” Which again, I'm super glad you did. It's exactly what I was looking for. How do you get here?Maciej: I'd been thinking about both kinds of types of apps. So like, definitely webapp was the initial idea how to build something, it was the webapp. Because as you said, like, that's the default mode. Like, we are thinking webapp; like, let's build a webapp because I'm an engineer, right? There is some inspiration coming from Dynobase, which was made by a friend [unintelligible 00:18:55] who also lives in Poland—I didn't mention that; we're based in [Poznań 00:18:58], Poland.And when I started thinking about it, there's a lot of benefits of using this approach. The biggest benefit, as I mentioned, is security; and the second benefit is just most, like, cost-effective because we don't need to run in the backend, right? We don't need to download all your metrics, all your logs. We I think, like, let's think about it, like, from the perspective. Listen, so everyone in the company to start working, they have to download all of your stuff from your AWS account. Like, that sounds insane because you don't need all of that stuff elsewhere.Corey: Store multiple copies of it. Yeah I, generally when I'm looking at this, I care about the last five to ten minutes.Maciej: Exactly.Corey: I don't—Maciej: Exactly.Corey: —really care what happened three-and-a-half years ago on this function. Almost always. But occasionally I want to look back at, “Oh, this has been breaking. How long has it been that way?” But I already have that in the AWS environment unless I've done the right thing and turned on, you know, log expiry.Maciej: Exactly. So, this is a lot of, like, I don't want to be, like, you know, mean to anyone but like, that's a lot of waste. Like, that's a lot of waste of compute power because you need to download it; of cost because you need to get this data out of AWS, which you need to pay for, you know, get metric data and stuff like this. So, you need to—Corey: And almost all of its—what is it? Write once, read never. Because it's, you don't generally look at these things.Maciej: Yeah, yeah. Exactly.Corey: And so much of this, too, for every invocation I have, even though it's low traffic stuff, it's the start with a request ID and what version is running, it tells me ‘latest.' Helpful. A single line of comment in this case says ‘200.' Why it says that, I couldn't tell you. And then it says ‘End request ID.' The end.Now, there's no way to turn that off unless you disabled the ability to write to CloudWatch logs in the function, but ingest on that cost 50 cents a gigabyte, so okay, I guess that's AWS's money-making scam of the year. Good for them. But there's so much of that, it's like looking at—like, when things are working, it's like looking at a low traffic site that's behind a load balancer, where there's a whole—you have gigabytes, in some cases, of load balancer—of web server logs on the thing that's sitting in your auto-scaling group. And those logs are just load balancer health checks. 98% of it is just that.Same type of problem here, I don't care about that, I don't want to pay to store it, I certainly don't want to pay to store it twice. I get it, that makes an awful lot of sense. It also makes your security job a hell of a lot easier because you're not sitting on a whole bunch of confidential data from other people. Because, “Well, it's just logs. What could possibly be confidential in there?” “Oh, my sweet summer child, have you seen some of the crap people put in logs?”Maciej: I've seen many things in logs. I don't want to mention them. But anyways—and also, you know, like, usually when you gave access to your AWS account, it can ruin you. You know, like, there might be a lot of—like, you need to really trust the company to give access to your AWS account. Of course, in most cases, the roles are scoped to, you know, only CloudWatch stuff, actions, et cetera, et cetera, but you know, like, there are some situations in which something may not be properly provisioned. And then you give access to everything.Corey: And you can get an awful lot of data you wouldn't necessarily want out of that stuff. Give me just the PDF printout of last month's bill for a lot of environments, and I can tell you disturbing levels of detail about what your architecture is, just because when you—you can infer an awful lot.Maciej: Yeah.Corey: Yeah, I hear you. It makes your security story super straightforward.Maciej: Yeah, exactly. So, I think just repeat my, like, the some inspiration. And then when I started thinking about Cloudash, like, definitely one of the inspiration was Dynobase, from the, kind of, GUI for, like, more powerful UI for DynamoDB. So, if you're interested in that stuff, you can also check this out.Corey: Oh, yeah, I've been a big fan of that, too. That'll be a separate discussion on a different episode, for sure.Maciej: [laugh]. Yeah.Corey: But looking at all of this, looking at the approach of, the only real concern—well, not even a concern. The only real challenge I have with it for my use case is that when I'm on the road, the only thing that I bring with me for a computer is my iPad Pro. I'm not suggesting by any means that you should build this as a new an iPad app; that strikes me as, like, 15 levels of obnoxious. But it does mean that sometimes I still have to go diving into the CloudWatch console when I'm not home. Which, you know, without this, without Cloudash, that's what I was doing originally anyway.Maciej: You're the only person that requested that. And we will put that into backlog, and we will get to that at some point. [laugh].Corey: No, no, no. Smart question is to offer me a specific enterprise tier pricing—.Maciej: Oh, okay. [laugh].Corey: —that is eye-poppingly high. It's like, “Hey, if you want a subsidize feature development, we're thrilled to empower that.” But—Maciej: [laugh]. Yeah, yeah. To be honest, I like that would be hard to write [unintelligible 00:23:33] implement as iPad app, or iPhone app, or whatever because then, like, what's the story behind? Like, how can I get the credentials, right? It's not possible.Corey: Yeah, you'd have to have some fun with that. There are a couple of ways I can think of offhand, but then that turns into a sandboxing issue, and it becomes something where you have to store credentials locally, regardless, even if they're ephemeral. And that's not great. Maybe turn it into a webapp someday or something. Who knows.What I also appreciate is that we had a conversation when you first launched, and I wound up basically going on a Zoom call with you and more or less tearing apart everything you've built—and ideally constructive way—but looking at a lot of the things you've changed in your website, you listened to an awful lot of feedback. You doubled your pricing, for example. Used to be ten bucks a month; now you're twenty. Great. I'm a big believer in charging more.You absolutely add that kind of value because it's, “Well, twenty bucks a month for a desktop app. That sounds crappy.” It's, “Yeah, jackwagon, what's your time worth?” I was spending seven bucks a month in serverless charges, and 120 or 130 a month for Epsagon, and I was thrilled to pieces to be doing it because the value I got from being able to quickly diagnose what the hell was going on far outstripped what the actual cost of doing these things. Don't fall into the trap of assuming that well, I shouldn't pay for software. I can just do it myself. Your time is never free. People think it is, but it's not.Maciej: That's true. The original price of $9.99, I think that was the price was the launch promo. After some time, we've decided—and after adding more features: API Gateway support—we've decided that this is, like, solving way more problems, so like, you should probably pay a little bit more for that. But you're kind of lucky because you subscribed to it when it was 9.99, and this will be your kind of prize for the end of, you know—Corey: Well, I'm going to argue with you after the show to raise the price on mine, just because it's true. It's the—you want to support the things that you want to exist in the world. I also like the fact that you offered an annual plan because I will go weeks without ever opening the app. And that doesn't mean it isn't adding value. It's that oh, yeah, I will need that now that I'm hitting these issues again.And if I'm paying on a monthly basis, and it shows up with a, “Oh, you got charged again.” “Well, I didn't use it this month; I should cancel.” And [unintelligible 00:25:44] to an awful lot of subscriber churn. But in the course of a year, if I don't have at least one instance in which case, wow, that ten minute span justified the entire $200 annual price tag, then, yeah, you built the wrong thing or it's not for me, but I can think of three incidents so far since I started using it in the past four months that have led to that being worth everything you will charge me a year, and then some, just because it made it so clear what was breaking.Maciej: So, in that regard, we are also thinking about the team licenses, that's definitely on the roadmap. There will be some changes to that. And we definitely working on more and more features. And if we're—like, the roadmap is mostly about supporting more and more AWS services, so right now it's Lambda, API Gateway, we're definitely thinking about SQS, SNS, to get some sense how your messages are going through, probably something, like, DynamoDB metrics. And this is all kind of serverless, but why not going wider? Like, why not going to Fargate? Like, Fargate is theoretically serverless, but you know, like, it's serverless on—Corey: It's serverless with a giant asterisk next to it.Maciej: Yeah, [laugh] exactly. So, but why not? Like, it's exactly the same thing in terms of, there is some user flow, there is some user journey, when you want to debug something. You want to go from API Gateway, maybe to the container to see, I don't know, like, DynamoDB metric or something like that, so it should be all easy. And this is definitely something.Later, why not EC2 metrics? Like, it would be a little bit harder. But I'm just saying, like, first thing here is that you are not, like, at this point, we are serverless, but once we cover serverless, why not going wider? Why not supporting more and more services and just making sure that all those use cases are correctly modeled with the UI and UX, et cetera?Corey: That's going to be an interesting challenge, just because that feels like what a lot of the SaaS monitoring and observability tooling is done. And then you fire this thing up, and it looks an awful lot like the AWS console. And it's, “Yeah, I just want to look at this one application that doesn't use any of the rest of those things.” Again, I have full faith and confidence in your ability to pull this off. You clearly have done that well based upon what we've seen so far. I just wonder how you're going to wind up tackling that challenge when you get there.Maciej: And maybe not EC2. Maybe I went too far. [laugh].Corey: Yeah, honestly, even EC2-land, it feels like that is more or less a solved problem. If you want to treat it as a bunch of EC2, you can use Nagios. It's fine.Maciej: Yeah, totally.Corey: There are tools that have solved that problem. But not much that I've seen has solved the serverless piece the way that I want it solved. You have.Maciej: So, it's definitely a long road to make sure that the serverless—and by serverless, I mean serverless how AWS understands serverless, so including Fargate, for example. So, there's a lot of stuff that we can improve. It's a lot of stuff that can make easier with Cloudash than it is with CloudWatch, just staying inside serverless, it will take us a lot of time to make sure that is all correct. And correctly modeled, correctly designed, et cetera. So yeah, I went too far with EC2 sorry.Corey: Exactly. That's okay. We all go too far with EC2, I assure you.Maciej: Sorry everyone using EC2 instances. [laugh].Corey: If people want to kick the tires on it, where can they find it?Maciej: They can find it on cloudash.dev.Corey: One D in the middle. That one throws me sometimes.Maciej: One D. Actually, after talking to you, we have a double-D domain as well, so we can also try ‘Clouddash' with double-D. [laugh].Corey: Excellent, excellent. Okay, that is fantastic. Because I keep trying to put the double-D in when I'm typing it in my search tool on my desktop, and it doesn't show up. And it's like, “What the—oh, right.” But yeah, we'll get there one of these days.Maciej: Only the domain. It's only the domain. You will be redirected to single-D.Corey: Exactly.Maciej: [laugh].Corey: We'll have to expand later; I'll finance the feature request there. It'll go well. If people want to learn more about what you have to think about these things, where else can they find you?Maciej: On Twitter, and my Twitter handle is @mthenw. M-then-W, which is M-T-H—mthenw. And my co-founder @tlakomy. You can probably add that to [show notes 00:29:35]. [laugh].Corey: Oh, I certainly will. It's fine, yeah. Here's a whole bunch of letters. I hear you. My Twitter handle used to be my amateur radio callsign. It turns out most people don't think like that. And yeah, it's become an iterative learning process. Thank you so much for taking the time to speak with me today and for building this thing. I really appreciate both of them.Maciej: Thank you for having me here. I encourage everyone to visit cloudash.dev, if you have any feature requests, any questions just send us an email at hello@cloudash.dev, or just go to GitHub repository in the issues; just create an issue, describe what you want and we can talk about it.We are always happy to help. The main purpose, the ultimate goal of Cloudash is to make the serverless engineer's life easier, on very high level. And on a little bit lower level, just to make, you know, troubleshooting and debugging serverless apps easier.Corey: Well, from my perspective, you've succeeded.Maciej: Thank you.Corey: Thank you. Maciej Winnicki, founder of Cloudash. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment telling me exactly why I'm wrong for using an iPad do these things, but not being able to send it because you didn't find a good way to store the credentials.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Oops, we did it again! When we put in the Song of the Week we didn't check our past shows so we accidentally reused one from before.If you can figure out which show had the song the first time, you might win coffee. Text your answers to 760.608.1942. This week Big Squatch is on talking to the Bow Tie Guy about the concept that if you want to improve, you've got to get better. To give to the ministry and support the show financially text the word "MuM" to 760-WALLS-CA.

Giulio Gallarotti stops by Chanel in the City to chat with host, Chanel Omari on how & why he started stand up comedy, how he transitioned from tennis to comedy, how to cope with your friends receiving a certain success that you might want to achieve and how to handle it, how OOPS the podcast came about and how different live podcasting is from stand up comedy!  Giulio also shares how and why he started to create his own content and how that's the way of our future to be heard. He opens up about creating content in Iraq and his new series that will air on his own instagram content.  Giulio chats opening up for Pete Davidson and Ricky Valez and how it feels to be close with inspiring comics as themselves.  Make sure to follow Giulio @notjulio on all social media platforms         

Coruscant is in retrograde and we're feeling retrospective! We delved deep into the FOD archives to choose our favorite ads and sketches, talk about how they were developed, and even try to rank them! No roleplay in this one, so kick back with your loved ones around a fire, crack a cold one or two, and let the commentary flow through you.Support us on Patreon!Merch and more: FistfulOfDestiny.comRate us on Apple PodcastsFind us on RedditInstagram: @FistfulOfDestinyTwitter: @FistfulDestinyTodd Aden is our Galaxy MasterChase Robinson is CannonNick Fox is ErebosMadison Gallagher is GritAndrew Schaffer is KieraEdited/Produced by Andrew Schaffer and Chase RobinsonDistributed by Firwood Studios See acast.com/privacy for privacy and opt-out information.

Hello! If you're listening to this Phantom Thread it's because Thread is away unexpectedly. Oops, someone was caught with their pants in the cookie jar! But don't worry, we know you still need your TC fix…so while you wait, please, sit back, relax and enjoy a Thread fact! And while we're outie, remember, leave a Hotmail on our voice line to be auto-uploaded onto an upcoming Thread Corner episode! Hotmail line: 818-276-6922 (T1T-AS-NOW-AA) ElectronicHat.eu/ThreadSnCothatsabigolSattheendofThread R.I.P. Walt Weathers 1983-2018 Pinky Toe Poddicle - Across loads of platforms! https://podcasts.apple.com/us/podcast/pinky-toe-poddicle/id1475409174 Catering provided by Nathan Ballard, Macklen Makhloghi and Megan Reisberg threadweathers@gmail.com Twitter: @thread_corner, @threadweathers, @drkevinchadwick Insta: @joecooltampon, @d.o.c_2, @threadweathers, @thread_corner

This is the final part of thsi special 3-part series where you are going to learn HOW to accelerate your English learning to reach your English goals faster in 2022. Get the ALL the worksheets, audio lessons, and transcription for this special training podcast series here: https://realenglishconversations.com/email/deliberate-practice/ About this episode... So what was the BIGGEST mistake I made that kept me stuck as a beginner for so long? It wasn't only because I was doing Naive Practice... But it was also because I was following the 'common' suggestions and ideas about HOW to learn a language, such as: "Just listen to lots of audio" "Watch movies with subtitles" "Take a language course" "Go to a Spanish speaking country. You'll learn fast!" Trust me, I tried ALL of them.... Multiple times. It seemed like these ideas worked for everyone else, but they weren't working for me. I thought, “Maybe I'm just bad at learning languages”. And at one point, I almost gave up. It wasn't until I started think about how I usually learn new skills that I realized, it's a simple 2-step method: Step 1: Think about the skill I want to be able to do. Step 2: Think of ways to learn and practice it. For Spanish, I wanted to be able to: > Speak with real people and understand them But when I looked at what I was actually doing > Memorizing random words and doing grammar drills Wait a minute… How are grammar drills helping my speaking? Or listening? Oops. They don't. And what type of words am I learning? …Words from grammar lessons. Are those the words used in everyday communication? Nope. Definitely not. This helped me realize, I was doing the wrong activities for the skills I needed. My next mission: Find a better way to practice speaking and listening. And this brought me to the ‘trial and error' part of my learning where I spent the next two years experimenting with different ideas. Although most of my ideas were complete failures… … Eventually I found the key methods that UNLOCKED my language skills and allowed me to make rapid progress. Like really rapid. I got up to an advanced level within 1 year. Although my story is ‘interesting' because it explains HOW I figured out how to reach fluency. My story is also the LONG and SLOW WAY. … And I don't recommend it. Because there is a MUCH faster way. In today's podcast, I want to share the concept of DELIBERATE PRACTICE which builds on the concept of Purposeful Practice. Without doubt, Deliberate Practice is the fast-track to fluency. And it's a method that can easily increase the speed you learn by 3x. >> Get the worksheets, audio downloads, and transcription for this ALL the lessons from this special training podcast series here: https://realenglishconversations.com/email/deliberate-practice/ Get on the Fast-Track to Fluency with our Special Offer HERE: https://realenglishconversations.com/memberships/member-plans/fluency-programs/ny-special-offer/

Hello! If you're listening to this Phantom Thread it's because Thread is away unexpectedly. Oops, someone was caught with their pants in the cookie jar! But don't worry, we know you still need your TC fix…so while you wait, please, sit back, relax and enjoy a Thread fact! And while we're outie, remember, leave a Hotmail on our voice line to be auto-uploaded onto an upcoming Thread Corner episode! Hotmail line: 818-276-6922 (T1T-AS-NOW-AA) R.I.P. Walt Weathers 1983-2018 Pinky Toe Poddicle - Across loads of platforms! https://podcasts.apple.com/us/podcast/pinky-toe-poddicle/id1475409174 Catering provided by Nathan Ballard, Macklen Makhloghi and Megan Reisberg threadweathers@gmail.com Twitter: @thread_corner, @threadweathers, @drkevinchadwick Insta: @joecooltampon, @d.o.c_2, @threadweathers, @thread_corner

Join Cronus, Daralis, Rylie and their Kingdom Hearts obsessed friend Austin as he explains the games to them. Goofs and Goofs abound as they reminisce about all the laughs they've had in 2021. Join our Discord https://discord.gg/t9WX76d4qG Intro and Outro Song: Dearly Reminded by Ayano Ultra https://ayanoultra.bandcamp.com

Oops, he did it again. Antonio Brown has quit the Bucs and the guys are confused on how to feel. Also, the debut of 2 new segments. Merch: https://www.facebook.com/109437791217379/posts/286828156811674/?d=n

Hello! If you're listening to this Phantom Thread it's because Thread is away unexpectedly. Oops, someone was caught with their pants in the cookie jar! But don't worry, we know you still need your TC fix…so while you wait, please, sit back, relax and enjoy a Thread fact! And while we're outie, remember, leave a Hotmail on our voice line to be auto-uploaded onto an upcoming Thread Corner episode! Hotmail line: 818-276-6922 (T1T-AS-NOW-AA) R.I.P. Walt Weathers 1983-2018 Pinky Toe Poddicle - Across loads of platforms! https://podcasts.apple.com/us/podcast/pinky-toe-poddicle/id1475409174 Catering provided by Nathan Ballard, Macklen Makhloghi and Megan Reisberg threadweathers@gmail.com Twitter: @thread_corner, @threadweathers, @drkevinchadwick Insta: @joecooltampon, @d.o.c_2, @threadweathers, @thread_corner

Overcome thoughts by overcoming anger…; Schools are failing…; — Fauci on overcounting cases… B from Florida is a nurse and knew about overcounting cases early on.

Oops! Here's another long-lost review that's been NETFLIX AND CHILLED! Our recording equipment has changed over these last few years, and these are the reviews that were lost in the shuffle and never posted! This is the first of many, and perhaps it will become a new trend of looking up forgotten Netflix films, but for now enjoy: The Film School Janitors' review of I AM MOTHER, a film about (checks notes) the post-apocalypse, human survival, and a robot. Did you see it? Do you remember any of it? Perhaps this review will jog those memories for you!

About EllEll, former SysAdmin, cloud builder, podcaster, and container advocate, has always been a security enthusiast. This enthusiasm and driven curiosity have helped her become an active member of the InfoSec community, leading her to explore the exciting world of Genetic Software Mapping at Intezer.Links: Intezer: https://www.intezer.com Twitter: https://twitter.com/Ell_o_Punk TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers—and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And—let me be clear here—it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small scale applications or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. If there's one thing we love doing in the world of cloud, it's forgetting security until the very end, going back and bolting it on as if we intended to do it that way all along. That's why AWS says security is job zero because they didn't want to remember all of their slides once they realized they forgot security. Here to talk with me about that today is Ell Marquez, security research advocate at Intezer. Ell, thank you for joining me.Ell: Of course.Corey: So, what does a security research advocate do, for lack of a better question, I suppose? Because honestly, you look at that, it's like, security research advocate, it seems, would advocate for doing security research. That seems like a good thing to do. I agree, but there's probably a bit more nuance to it, then I can pick up just by the [unintelligible 00:01:17] reading of the title.Ell: You know, we have all of these white papers that you end up getting, the pen test reports that are dropped on your desk that nobody ever gets to, they become low priority, my job is to actually advocate that you do something with the information that you get. And part of that just involves translating that into plain English, so anyone can go with it.Corey: I've got to say, if you want to give the secrets of the universe and make sure that no one ever reads them, make sure that it has a whole bunch of academic-style citations at the beginning, and ideally put it behind some academic paywall, and it feels like people will claim to have read it but never actually read the thing.Ell: Don't forget charts.Corey: Oh yes, with the charts. In varying shades of blue. Apparently that's the only color you're allowed to do some of these charts in; despite having a full universe of color palettes out there, we're just going to put it in varying shades of corporate blue and hope that people read it.Ell: Yep, that sounds about security there. [laugh].Corey: So, how much of, I guess, modern security research these days is coming out of academia versus coming out of industry?Ell: In my experience in, you know, research I've done in researching researchers, it all really revolves around actual practitioners these days, people who are on the front lines, you know, monitoring their honey pots, and actually reporting back on what they're seeing, not just theoretical.Corey: Which I guess brings us to the question of, I wind up watching all of the keynotes that all the big cloud providers put on and they simultaneously pat me on the head and tell me that their side of security is just fine with their shared responsibility model and the rest, whereas all of the breaches I'm ever going to deal with and the only way anyone can ever see my data is if I make a mistake in configuring something. And honestly, does that really sound like something I would do? Probably not, but let's face it, they claim that they are more or less infallible. How accurate is that?Ell: I wish that I could find the original person that said this, but I've heard it so many times. And it's actually the ‘cloud irresponsibility model.' We have this blind faith that if we're paying somebody for it, it's going to be done correctly. I think you may have seen this with billing. How many people are paying for redundant security services with a cloud provider?Corey: I've once—well, more than once have noticed that if you were to configure every AWS security service that they have and enable it in your account, that the resulting bill would be larger than the cost of the data breach it was preventing. So, on some level, there is a point at which it just becomes ridiculous and it's not necessarily worth pursuing further. I honestly used to think that the shared responsibility model story was a sales pitch, and then I grew ever more cynical. And now my position on it is that it's because if you get breached, it's your fault is what they're trying to say. But if you say it outright to someone who just got breached, they're probably not going to give you money anymore. So, you need to wrap that in this whole involved 45-minute presentation with slides, and charts, and images and the rest because people can't refute one of those quite the way that they can a—it's in a tweet sentence of, “It's your fault.”Ell: I kind of have to agree with them in the end that it is your fault. Like, the buck stops with you, regardless. You are the one that chose to trust that cloud provider was going to do everything because your security team might make a mistake, but the cloud provider is made up of humans as well who can make just as many mistakes. At the end of the day, I don't care what cloud provider you used; I care that my data was compromised.Corey: One of the things that irks me the most is when I read about a data breach from a vendor that I had either trusted knowingly with my data or worse, never trusted but they somehow scraped it somewhere and then lost it, and they said, “Oh, a third-party contractor that we hired.” It's, “Yeah, look, I'm doing business with you, ideally, not the people that you choose to do business with in turn. I didn't select that contractor. You did, you can pass out the work and delegate that. You cannot delegate the responsibility.” So no, Verizon, when you talk about having a third-party contractor have a data breach of customer data, you lost the data by not vetting your contractors appropriately.Ell: Let's go back in time to hopefully something everybody remembers: Target. Target being compromised because of their HVAC provider. Yet how many people—you know this is being recorded in the holiday season—are still shopping at Target right now? I don't know if people forget or they just don't care.Corey: A year later, their stock price was higher than it was before the breach. Sure they had a complete turnover of their C-suite at that point; their CSO and CEO were forced out as a result, but life went on. And they continue to remain a going concern despite quite literally having a bull's eye painted on the building. You'd think that would be a metaphor for security issues. But no, no, that is something they actually do.Ell: You know, when you talk about, you know, the CEO being let go or, you know, being run out, but what part did he honestly have to do with it? They're talking about, oh, well, they made the decisions and they were responsible. What because they got that, you know, list of just 8000 papers with the charts on it?Corey: As I take a look at a lot of the previous issues that we've seen with I've been doing my whole S3 Bucket Negligence Awards for a while, but once I actually had a bucket engraved and sent to a company years ago, the Pokémon Company, based upon a story that I read in the Wall Street Journal, how they declined to do business with a prospective vendor because going through their onboarding process, they noticed among other things, insufficient security controls around a whole bunch of things including S3 buckets, and it's holy crap, a company actually making a meaningful decision based upon security. And say what you will about the Pokémon Company, their audience is—at least theoretically—children and occasionally adults who believe they're children—great, not here to shame—but they understand that this is not something you can afford to be lax in and they kiboshed the entire deal. They didn't name the vendor, obviously, but that really took me aback. It was such a rarity to see that, and it's why I unfortunately haven't had to make a bucket like that since. I wish I did. I wish more companies did things like this. But no it's just a matter of, well, we claim to do the right thing, and we checked all the boxes and called it good, and oops, these things happen.Ell: Yes, but even when it goes that way, who actually remembers what happened, and did you ever follow up if there were any consequences to not going, “Okay, third-party. You screwed up, we're out. We're not using you.” I can't name a single time that happened.Corey: Over at The Duckbill Group, we have large enterprise customers. We have to be respectful and careful with their data, let's be very clear here. We have all of their AWS billing data going back for some fixed period of time. And it worries me what happens if that data gets breached. Now, sure, I've done the standard PR crisis comms thing, I have statements and actions prepared to go in the event that it happens, but I'm also taking great pains to make sure it doesn't.It's the idea of okay, let's make sure that we wind up keeping these things not just distinct from the outside world, but distinct from individual clients so we're not mixing and matching any of this stuff. It's one of those areas where if we wind up having a breach, it's not because we didn't follow the baseline building blocks of doing this right. It's something that goes far beyond what we would typically expect to see in an environment like this. This, of course, sets aside the fact that while a breach like that would be embarrassing, it isn't actually material to anyone's business. This is not to say that I'm not taking it seriously because we have contractual provisions that we will not disclose a lot of this stuff, but it does not mean the end of someone's business if this stuff were to go public in the same way that, for example, back when I worked at Grindr many years ago, in the event that someone's data had been leaked there, people could theoretically been killed. There's a spectrum of consequences here, but it still seems like you just do the basic block-and-tackling to make sure that this stuff isn't publicly exposed, then you start worrying about the more advanced stuff. But with all these breaches, it seems like people don't even do that.Ell: You have Tesla, right, who's working on going to Mars, sending people there who had their S3 buckets compromised. At that point, if we've got this technology, just giant there, I think we're safe to do that whole, “Hey, assume breach, assume compromise.” But when I say that, it drives me up the wall how many people just go, “Okay, well, there's nothing we can do. We should just assume that there's going to be an issue,” and just have this mentality where they give up. No, that gives you a starting point to work from, but that's not the way it's being seen.Corey: One of the things that I've started doing as I built up my new laptop recently has been all right, how do I work with this in such a way that I don't have credentials that are going to grant access to things in any long-lived way ever residing on disk? And so that meant with AWS, I started using SSO to log into a bunch of things. It goes through a website, and then it gives a token and the rest that lasts for 12 hours. Great.Okay, SSH keys, how do I handle that? Historically, I would have them encrypted with a passphrase, but then I found for Mac OS an app called Secretive that stores it in the Secure Enclave. I have to either type in a password or prove it with a biometric Touch ID nonsense every time something tries to access the key. It's slightly annoying when I'm checking out five or six Git repos at once, but it also means that nothing that I happen to have compromised in a browser or whatnot is going to be able to just grab the keys, send it off somewhere, and then I'll never realize that I've been compromised throughout. It's the idea of at least theoretically defense in depth because it's me, it's my personal electronics, in all likelihood, that are going to be compromised, more so than it is configured, locked-down S3 buckets, managed properly. And if not me, someone else in my company who has access to these things.Ell: I'm going to give you the best advice you're ever going to get, and people are going to go, “Duh,” but it's happening right now: Don't get complacent, don't get lazy, how many of us are, “Okay, we're just going to put the key over here for a second.” Or, “We're just going to do this for a minute,” and then we forget. I recently, you know, did some research into Emotet and—you know, the new virus and the group behind it—you know how they got caught? When they were raided, everything was in plain text. They forgot to use their VPN for a while, all the files that they'd gotten no encryption. These were the people that that's what they were looking for, but you get lazy.Corey: I've started treating at least the security credential side of doing weird things, even one off bash scripts, as if they were in production. I stuff the credentials into something like AWS's parameter store, and then just have a one line snippet of code that retrieves them at runtime to wind up retrieving those. Would it be easier to just slap it in there in the code? Absolutely, of course it would. But I also look at my newsletter production pipeline, and I count the number of DynamoDB tables that are in active use that are labeled Test or Dev, and I realized, huh, I'm actually kind of bad at taking something that was in Dev and getting it ready for production. Very often, I just throw a load at it and call it good. So, if I never get complacent around things like that, it's a lot harder for me to get yelled at for checking secrets into Git, for example.Ell: Probably not the first time that you've heard this but, Corey, I'm going to have to go with you're abnormal because that is not what we're seeing in a day-to-day production environment.Corey: Oh, of course not. And the reason I do this is because I was a grumpy old sysadmin for so long, and have gotten burned in so many weird ways of messing things up. And once it's in Git, it's eternal—we all know that—and I don't ever want to be in a scenario where I open-source something and surprise, surprise, come to find out in the first two days of doing something, I had something on disk. It's just better not to go down that path if at all possible.Ell: Being a former sysad as well, I must say, what you're able to do within your environment, your computer is almost impossible within a corporate environment. Because as a sysad, I'm looking at, “What did the devs do again? Oh, man, what's the security team going to do?” And you're stuck in the middle trying to figure out how to solve a problem and then manage it through that entire environment.Corey: I never really understood intrinsically the value of things like single-sign-on, until I wound up starting this company. Because first, it was just me for a few years. And yeah, I can manage my developer environments and my AWS environments in such a way that if they get compromised, it's not going to be through basic, “Oops, I forgot that's how computers work,” type of moment. It's going to be at least something a little bit more difficult, I would imagine. Because if you—all right, if you managed to wind up getting my keys and the passphrase, and in some cases, the MFA device, great, good, congratulations, you've done something novel and probably deserve the data.Whereas as soon as I started bringing other people in who themselves were engineers, I sort of still felt the same way. Okay, we're all responsible adults here, and by and large, since I wasn't working with junior people, that held true. And then I started bringing in people who did not come from a deeply computer-y technical background, doing things like finance, and doing things like sales, and doing things like marketing, all of which are themselves deeply technical in their own way, but data privacy and data security are not really something that aligns with that. So, it got into the weeds of, “How do I make sure that people are doing responsible things on their work computers like turning on disk encryption, and forcing a screensaver, and a password and the rest.” And forcing them to at least do some responsible things like having 1Password for everyone was great until I realized a couple people weren't even using it for something, and oh dear. It becomes a much more difficult problem at scale when you have to deal with people who, you know, have actual work to do rather than sitting around trying to defend the technology against any threat they can imagine.Ell: In what you just said though, there is one flaw is we tend to focus on, like you said, marketing and finance and all these organizations who—don't get phished, don't click on this link. But we kind of give the just the openness that your security team, your sysads, your developers, they're going to know best practices. And then we focus on Windows because that's what the researchers are doing. And then we focus on Windows because that's what marketing is using, that's what finance is using. So, what there's no way to compromise a Mac or Linux box? That's a huge, huge open area that you're allowing for attackers.Corey: Let's be very clear here. We don't have any Windows boxes—of which I'm aware—in the company. And yeah, the technical folk we have brought in, most of them I'd worked—or at least the early folks—I'd worked with previously. And we had a shared understanding of security. At least we all said the right things.But yeah, as you—right, as you grow, as you scale, this becomes a big deal. And it's, I also think there's something intrinsically flawed about a model where the entire instruction set is, it all falls on you to not click the link or you're going to doom us all. Maybe if someone can click a link and doom us all, the problem is not with them; it's the fact that we suck at building secure systems that respect defense in depth.Ell: Something that we do wrong, though, is we split it up. We have endpoint protection when we're talking about, you know, our Windows boxes, our Linux boxes, our Mac boxes. And then we have server-side and cloud security. Those connect. Think about, there's a piece of malware called EvilGNOME. You go in on a Linux box, you have access to my camera, keylogging, and watching exactly what I'm doing. I'm your sysad. I then cat out your SSH keys, I go into your box, they now have the password, but we don't look for that. We just assume that those two aren't really that connected, and if we monitor our network and we monitor these devices, we'll be fine. But we don't connect the two pieces.Corey: One thing that I did at a consulting client back in 2012, or so that really raised eyebrows whenever I told people about it was that we wound up going to some considerable trouble building a allow list within Squid—a proxy server that those of us in Linux-land are all too familiar with in some cases—so everything in production could only talk to the outside world via that proxy; it was not allowed to establish any outbound connections other than through that proxy. So, it was at that point only allowed to talk to specify update servers, specified third-party APIs and the rest, so at least in theory, I haven't checked back on them since, I don't imagine that the log4yay nonsense that we've seen recently would necessarily work there. I mean, sure, you have the arbitrary execution of code—that's bad—but reaching out to random endpoints on the internet would not have worked from within that environment. And I liked that model, but oh my God, was it a pain in the butt to set up properly because it turns out, even in 2012, just to update a Linux system reasonably, there's a fair number of things it needs to connect to, from time-to-time, once you have all the things like New Relic instrumentation in, and the app repository you're talking to, and whatever container source you're using, and, and, and. Then you wind up looking at challenges like, oh, I don't know, if you're looking at an AWS-style environment, like most modern things are, okay, we're only going to allow it to talk to AWS endpoints. Well, that's kind of the entire internet now. The goalposts move, the rules change, the game marches on.Ell: On an even simpler point, with that you're assuming only outbound traffic through those devices. Are they not connected to anything within the internal network? Is there no way for an attacker to pivot between systems? I pivot over to that, I get the information, and I make an outbound connection on something that's not configured that way.Corey: We had—you're allowed to talk outbound to the management subnet, which was on its own VLAN, and that could make established connections into other things, but nothing else was allowed to connect into that. There was some defense in depth and some thought put into this. I didn't come up with most of this to be clear, it was—this was smart people sitting around. And yeah, if I sit here and think about this for a while, of course there's going to be ways to do it. This was also back in the days of doing it in physical data centers, so you could have a pretty good idea of what was connect to the outside world just by looking at where the cables went. But there was also always the question of how does this–does this do what I think it's doing or what have I overlooked? Security's job is never done.Ell: Or what was misconfigured in the last update. It's an assumption that everything goes correctly.Corey: Oh, there is that. I want to talk though, about the things I had to worry about back then, it seems like in many cases get kicked upstairs to the cloud providers that we're using these days. But then we see things like Azurescape where security researchers were able to gain access to the Azure control plane where customers using Cosmos DB—Azure's managed database service, one of them—could suddenly have their data accessed by another customer. And Azure is doing its clam up thing and not talking about this publicly other than a brief disclosure, but how is this even possible from security architecture point of view? It makes me wonder if it hadn't been disclosed publicly by the researcher, would they have ever said something? Most assuredly not.Ell: I've worked with several researchers, in Intezer and outside of Intezer, and the amount of frustration that I see within reasonable disclosure, it just blows my mind. You have somebody threatening to sue the researcher if they bring it out. You have a company going, “Okay, well, we've only had six weeks. Give us three more weeks.” And next thing we know, it's six months.There is just this pushback about what we can actually bring out to the public on why they're vulnerable in organizations. So, we're put in this catch-22 as researchers. At what point is my responsibility to the public, and at what point is my responsibility to protect myself, to keep myself from getting sued personally, to keep my company from going down? How can we win when we have small research groups and these massive cloud providers?Corey: This episode is sponsored in part by something new. Cloud Academy is a training platform built on two primary goals. Having the highest quality content in tech and cloud skills, and building a good community the is rich and full of IT and engineering professionals. You wouldn't think those things go together, but sometimes they do. Its both useful for individuals and large enterprises, but here's what makes it new. I don't use that term lightly. Cloud Academy invites you to showcase just how good your AWS skills are. For the next four weeks you'll have a chance to prove yourself. Compete in four unique lab challenges, where they'll be awarding more than $2000 in cash and prizes. I'm not kidding, first place is a thousand bucks. Pre-register for the first challenge now, one that I picked out myself on Amazon SNS image resizing, by visiting cloudacademy.com/corey. C-O-R-E-Y. That's cloudacademy.com/corey. We're gonna have some fun with this one!Corey: For a while, I was relatively confident that we had things like Google's Project Zero, but then they started softening their disclosure timelines and the rest, and it was, we had the full disclosure security distribution list that has been shuttered to my understanding. Increasingly, it's become risky to—yourself—to wind up publishing something that has not been patched and blessed by the providers and the rest. For better or worse, I don't have those problems, just because I'm posting about funny implications of the bill. Yeah, worst case, AWS is temporarily embarrassed, and they can wind up giving credits to people who were affected and be mad at me for a while, but there's no lasting harm in the way that there is with well, people were just able to look at your data for six months, and that's our bad oops-a-doozy. Especially given the assertions that all of these providers have made to governments, to banks, to tax authorities, to all kinds of environments where security really, really matters.Ell: The last statistic that I heard, and it was earlier this year, that it takes over 200 days for compromise even to be detected. How long is it going to take for them to backtrack, figure out how it got in, have they already patched those systems and that vulnerability is gone, but they managed to establish persistence somehow, the layers that go into actually doing your digital forensics only delay the amount of time that any of that is going to come out where that they have some information to present to you. We keep going, “Oh, we found this vulnerability. We're working on patches. We have it fixed.” But does every single vendor already have it pitched? Do they know how it actually interacted within one customer's environment that allowed that breach to happen? It's just ridiculous to think that's actually occurring, and every company is now protected because that patch came out.Corey: As I take a look at how companies respond to these things, you're right, the number one concern most of them have is image control, if I'm being honest with you. It's the reputational management of we are still good at security, even though we've had a lapse here. Like, every breach notification starts out with, “Your security is important to us.” Well, clearly not that important because look at the email you had to send. And it's almost taken on aspects of a comedy piece where it [grips 00:23:10] with corporate insincerity. On some level, when you tell a company that they have a massive security vulnerability, their first questions are not about the data privacy; it's about how do we spend this to make ourselves come out of this with the least damage possible. And I understand it, but it's still crappy.Ell: Us tech folk talk to each other. When we have security and developers speaking to each other, we're a lot more honest than when we're talking to the public, right? We don't try to hold that PR umbrella over ourselves. I was recently on a panel speaking with developers, head SRE folk—what was there? I think there was a CISO on there—and one of the developers just honestly came out and said, “At the end, my job is to say, ‘How much is that breach going to cost, versus how much money will the company lose if I don't make that deployment?'” The first thing that you notice there is that whole how much money you'll lose? The second part is why is the developer the one looking at the breach?Corey: Yeah. The work flows downward. One of the most depressing aspects to me of the CISO role is that it seems like the job is to delegate everything, sign binding contracts in your name, and eventually get fired when there's a breach and your replacement comes in to sign different papers. All the work gets delegated, none of the responsibility does, ideally—unless you're SolarWinds and try and blame it on an intern; I mean, I wish I had an ablative intern or two around here to wind up a casting blame they don't deserve on them. But that's a separate argument—there is no responsibility-taking as I look at this. And that's really a depressing commentary on the state of the world.Ell: You say there's no responsibility taken, but there is a lot of blame assigned. I love the concept of post-mortems to why that breach happened, but the only people in the room are the security team because they had that much control over anything. Companies as a whole need a scapegoat, and more and more, security teams are being blamed for every single compromised as more and more responsibility, more and more privileges, and visibility into what's going on is being taken away from them. Those two just don't balance. And I think it's causing a lot of just complacency and almost giving up from our security teams.Corey: To be clear, when we talk about blameless post-mortems for things like this, I agree with it wholeheartedly within the walls of a company. However, externally as someone whose data has been taken in some of these breaches, oh, I absolutely blame the company. As I should, especially when it's something like well, we have inadvertently leaked your browsing history. Why were you collecting that in the first place? Is sort of the next logical question.I don't believe that my ISP needs that to serve me better. But now you have Verizon sending out emails recently—as of this recording—saying that unless anyone opts out, all the lines in our cell account are going to wind up being data mined effectively, so they can better target advertisements and understand us better. It's no, I absolutely do not want you to be doing that on my phone. Are you out of your mind? There are a few things in this world that we consider more private than our browsing histories. We ask the internet things we wouldn't ask our doctors in many cases, and that is no small thing as far as the level of trust that we place in our ISPs that they are now apparently playing fast and loose with.Ell: I'm going to take this step back because you do a lot of work with cloud providers. Do you think that we actually know what information is being collected about our companies and what we have configured internally and externally by the cloud provider?Corey: That's a good question. I've seen this before, where people will give me the PDF exploded view of last month's AWS bill, and they'll laugh because what information can I possibly get out of that. It just shows spend on services. But I could do that to start sketching out a pretty good idea of what their architecture looks like from that alone. There's an awful lot of value in the metadata.Now, I want to be clear, I do not believe on any provider—except possibly Azure because who knows at this point—that if you encrypt the data, using their encryption facilities—with AWS, I know it's KMS, for example—I do not believe that they can arbitrarily decrypt it and then scan for whatever it is they're looking for. I do not believe that they are doing that because as soon as something like that comes out, it puts the lie to a whole bunch of different audit attestations that they've made and brings the entire empire crumbling down. I don't think they're going to get any useful data from that. However, if I'm trying to build something like Amazon Prime Video, and I can just look at the bill from the Netflix account. Well, that tells me an awful lot about things that they might be doing internally; it's highly suggestive. Could that be used to give them an unfair advantage? Absolutely.I had a tweet a while back that I don't believe that Google's Gmail division is scanning inboxes for things that look like AWS invoices to target their sales teams, but I sure would feel better if they would assure me that was the case. No one was able to ever assure me of that. It's I don't mean to be sitting here slinging mud, but at the same time, it's given that when you don't explicitly say you're not doing something as a company, there's a great chance you might be doing it, that's the sort of stuff that worries me, it's a bunch of unfair dirty trick style stuff.Ell: Maybe I'm just cynical, or maybe I just focus on these topics too much, but after giving a presentation on cloud security, I had two groups, both, you know, from three letter government agencies, come up to me and say, “How do I have these conversations with the cloud provider?” In the conversation, they say, “We've contacted them several times; we want to look at this data; we want to see what they've collected, and we get ghosted, or we end up talking to attorneys. And despite over a year of communication, we've yet to be able to sit down with them.”Corey: Now, that's an interesting story. I would love to have someone come to me with that problem. I don't know how I would solve that yet. But I have a couple ideas.Ell: Hey, maybe they're listening, and they'll reach out to you. But—Corey: You know, if you're having that problem of trying to understand what your cloud provider is doing, please talk to me. I would love to go a little more in depth on that conversation, under an NDA or six.Ell: I was at a loss because the presentation that I was giving was literally about the compromise of managed service providers, whether that be an outsourced security group, whether that be your cloud provider, we're seeing attack groups going after these tar—think about how juicy they are. Why do I need to compromise your account or your company if I can compromise that managed service provider and have access to 15 companies?Corey: Oh, yeah. It's why would someone spend time trying to break into my NetApp when they could break into S3 and get access to everyone's data, theoretically? It's a centralization of security model risk.Ell: Yeah, it seems to so many people as just this crazy idea. It's so far out there. We don't need to worry about it. I mean, we've talked about how Azure Functions has been compromised. We talked about all of these cloud services that people are specifically going after and being able to make traction in these attacks.It's not just this crazy idea. It's something that's happening now, and with the progress that attackers are making, criminal groups are making, this is going to happen pretty soon.Corey: Sometimes when I'm out for a meal with someone who works with AWS in the security org, there'll be an appetizer where, “Oh, there's two of you. I'm going to bring three of them,” because I guess waitstaff love to watch people fight like that. And whenever I want the third one, all I have to do is say, “Can you imagine a day in which, just imagine hypothetically, IAM failed open and allowed every request to go through regardless of everything else?” Suddenly, they look sick, lose their appetite, and I get the third one. But it's at least reassuring to know that even the idea of that is that disgusting to them, and it's not the, “Oh, that happened three weeks ago, but don't tell anyone.” Like, there's none of that going on.I do believe that the people working on these systems at the cloud providers are doing amazingly good work. I believe they are doing far better than I would be able to do in trying to manage all those things myself, by a landslide. But nothing is ever perfect. And it makes me wonder that if and when there are vulnerabilities, as we've already seen—clearly—with Azure, how forthcoming and transparent would they really be? And that's the thing that keeps me up at night.Ell: I keep going back during this talk, but just the interaction with the people there and the crowd was just so eye-opening. And I don't want to be that person, but I keep getting to these moments of, “I told you so.” And I'm not going to go into SolarWinds. Lord, that has been covered, but shortly after that, we saw the same group going through and trying to—I'm not sure if they successfully did it, but they were targeting networks for cloud computing providers. How many companies focused outside of that compromise at that moment to see what it was going to build out to?Corey: That's the terrifying thing is if you can compromise a cloud service provider at this point, it's well, you could sell that exploit on the dark web to someone. Yeah, that is a—if you can get a remote code execution be able to look into any random Cloud account, there's almost no amount of money that is enough for something like that. You could think of the insider trading potential of just compromising Slack. A single company, but everyone talks about everything there, and Slack retains data in perpetuity. Think at the sheer M&A discussions you could come up with? Think of what you could figure out with a sort of a God's eye view of something like that, and then realize that they run on AWS, as do an awful lot of other companies. The damage would be incalculable.Ell: I am not an attacker, nor do I play one on TV, but let's just, kind of, build this out. If I was to compromise a cloud provider, the first thing I would do is lay low. I don't want them to know that I'm there. The next thing I would do is start getting into company environments and scanning them. That way I can see where the vulnerabilities are, I can compromise them that way, and not give out the fact that I came in through that cloud provider. Look, I'm just me sitting here. I'm not a nation state. I'm not somebody who is paid to do this from nine to five, I can only imagine what they would come up with.Corey: It really feels like this is no longer a concern just for those folks who manage have gotten on the bad side of some country's secret service. It seems like APTs, Advanced Persistent Threats, are now theoretically something almost anyone has to worry about.Ell: Let me just set the record straight right now on what I think we need to move away from: The whole APTs are nation states. Not anymore. And APT is anyone who has advanced tactics, anyone who's going to be persistent—because you know what, it's not that they're targeting you, it's that they know that they eventually can get in. And of course, they're a threat to you. When I was researching my work into Advanced Persistent Threats, we had a group named TNT that said, “Okay, you know what? We're done.”So, I contacted them and I said, “Here's what I'm presenting on you. Would you mind reviewing it and tell me if I'm right?” They came back and said, “You know what? We're not in APT because we target open Docker API ports. That's how easy it is.” So, these big attack groups are not even having to rely on advanced methods anymore. The line onto what that is just completely blurring.Corey: That's the scariest part to me is we take a look at this across the board. And the things I have to worry about are no longer things that are solely within my arena of control. They used to be, back when it was in my data center, but now increasingly, I have to extend trust to a whole bunch of different places. Because we're not building anything ourselves. We have all kinds of third-party dependencies, and we have to trust that they're doing the right things as they go, too, and making sure that they're bound so that the monitoring agent that I'm using can't compromise my entire environment. It's really a good time to be professionally paranoid.Ell: And who is actually responsible for all this? Did you know that 70% of the vulnerabilities on our systems right now are on the application level? Yet security teams have to protect it? That doesn't make sense to me at all. And yet, developers can pull in any third-party repository that they need in order to make that application work because hey, we're on a deadline. That function needs to come out.Corey: Ell, I want to thank you for taking the time to speak with me. If people want to learn more about how you see the world and what kind of security research you're advocating for, where can they find you?Ell: I live on Twitter to the point where I'm almost embarrassed to say, but you can find me at @Ell_o_Punk.Corey: Excellent. And we will wind up putting a link to that in the [show notes 00:35:37], as we always do. Thanks so much again for your time. I appreciate it.Ell: Always. I'd be happy to come again. [laugh].Corey: Ell Marquez, security research advocate at Intezer. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment that ends in a link that begs me to click it that somehow it looks simultaneously suspicious and frightening.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Hello! If you're listening to this Phantom Thread it's because Thread is away unexpectedly. Oops, someone was caught with their pants in the cookie jar! But don't worry, we know you still need your TC fix…so while you wait, please, sit back, relax and enjoy a Thread fact! And while we're outie, remember, leave a Hotmail on our voice line to be auto-uploaded onto an upcoming Thread Corner episode! Hotmail line: 818-276-6922 (T1T-AS-NOW-AA) R.I.P. Walt Weathers 1983-2018 Pinky Toe Poddicle - Across loads of platforms! https://podcasts.apple.com/us/podcast/pinky-toe-poddicle/id1475409174 Catering provided by Nathan Ballard, Macklen Makhloghi and Megan Reisberg threadweathers@gmail.com Twitter: @thread_corner, @threadweathers, @drkevinchadwick Insta: @joecooltampon, @d.o.c_2, @threadweathers, @thread_corner

CLICK TO SUBSCRIBE ON YOUR FAVORITE PODCATCHER So…we were so invested in musicals the past few weeks, we forgot to mention that we've watched sixteen (SIXTEEN?!??!) movies and we wanted to share our reviews with you! So strap in for a whirlwind review of our past month and a half in movies to ring in 2022 this week on Macintosh & Maud Haven't Seen What?! You can email us with feedback at macintoshandmaud@gmail.com, or you can connect with us on Instagram, Twitter and Facebook. Also please subscribe, rate and review the show on your favorite podcatcher, and tell your friends. Intro and outro music taken from the Second Movement of Ludwig von Beethoven's 9th Symphony. Licensed under an Attribution-NonCommercial-NoDerivs 3.0 Hong Kong (CC BY-NC-ND 3.0 HK) license. To hear the full performance or get more information, visit the song page at the Internet Archive.

TW: Language Catch up with the resurrected Two Witches Podcast 2.0 - Electric Boogaloo! It's a Holiday Miracle - praise the Almighty Holy Donut! We're back for Season 2, and we brought Magical Jobcat! We'll tell you what we've been up to since our chat with Mortellus, the Bagans Slayer on Episode 21, and introduce you to Vintage Magic and what the hell that has to do with haunted bricks. Surprising no one, a certain bossy nun and her Hell's Angels reinforcements are involved, but SJ's maternal grandfather recently showed up to join the party too to try to make them cry on the podcast. AGAIN. Also, a status report on the cover up, OOPS - we meant construction, at the Providence Academy, and an exciting update on the St. Ignatius Hospital in Colfax, WA. Andrea also has great news for all of you plant nerds too that our Patrons will enjoy the spoils of! SHOW NOTES HERE! Sincere gratitude to our new Holy Donut Cult Members: Jennifer C., Theresa Z., Danny, Megan C., Garrett K., and last but not least, Aidan K.! JOIN THE CULT. We have donuts - and lots of bonus content!

This week in the last video store near you, GLaDos and Patron take over the show and force but maestro and The Admirable Admiral to relive this past year through questions. Two podcasters/videostore workers enter the breakroom and one will be crowned victorious in Part 2 "OOPS"

Oops, Dave's recount confirms this is the final episode for 2021. Just kidding last week.Dave talks about his son's recent interview on NPR as part of their coverage on the recent tornadoes in Kentucky. Here's a link to the radio story; his interview begins at 12 minutes in.Del describes BC, a favorite comic of his and how the turtle and bird are like the two bucks. It's a stretch.A teacher tried to give away $50 but his students didn't read far enough to discover this. Dave can relate.Dave is working part-time at ANOTHER bike shop and loving it. Some guys never learn.We touch upon some of our highlights of 2021 and give a few predictions for 2022. As a test to see if anybody read this, send us a note to buckstwoold@gmail.com with the words 'Free NFT' as the subject and we'll send you a free copy of Del's stovetop art, which will likely be worth millions someday.  

Oops, Dr. Rubin and Dr. Pete forgot to say good-bye and all of a sudden, they found themselves in a short hiatus. In this season 2 closer, the co-hosts discuss the need for a break, setting boundaries, all within the context of a new year and the resolutions that people make as the world enters a new year. Learn about intention versus resolution, and both Dr. Rubin and Dr. Pete share some of their committed intentions for the new year. You will not want to miss this episode, especially if you are seeking peace in the new year.

A composite episode devoted to tips in reducing stress and anxiety levels. And of course, when you actively reduce your stress, mindfulness is in the mix! Welcome to Episode 79 of Roll With Peace, In Mind. Today's riff is A Wisdom Replay--Reducing Stress For Your Health and Well-Being is a wondrous mix of two past episodes: The 6 Best Gifts To Give Yourself Before Stress Has Gotchu In A Mess episode 43, and Reducing Stress: Be An Advocate For Your WellBeing episode 36. All to make one episode full of Mindful Thinking, examination and reflection. The titles give you an indication of the subject matter. Enjoy! **and OOPS! Said the wrong episode numbers in the episode audio but hey, it's all good!!** And I've got a group class & a workshop to tell you about-- 1) Don't Deny YOU: Virtual Guided Meditation & Journaling Workshop Wednesday, December 29th at 6:30PM EST I will be offering this 60 minute workshop. The end of the year, a new year is coming. What are your Intentions to treat yourself better and to enjoy your Life more? Join me for an inspiring, relaxing and invigorating workshop of relaxation and self-discovery. Also January 8th and 9th 2022. Click title for more information. A virtual workshop so you can join me from anywhere in the world!  2) End of The Month ChillOut: StressBusters Guided Meditation January 30th at 1:00PM EST. This is my End of The Month virtual guided meditation group class geared to help you Cleanse, Refuel, Balance and Restore. Click title for more information. I hope you will join us, bring a friend and/or family member or a group of folk to the Wellness Party! Check out my website for testimonials! *** And I keep forgetting to mention my handmade artisan works! MODAL VISIONS, Where Art, Spirit & WellBeing Come Together. It is the handmade branch of Jacquie Bird, Spiritual Wellness featuring wellness creations from jewelry to my Mandala WallArt home decor! Click MODAL VISIONS for unique, one of a kind Wellness Art! * * * Please tell your friends and family about this podcast, word of mouth is da the bomb-diggedy! **Producing a podcast takes a great deal of time, effort, and patience--especially when you are the Creator, Host, Producer, Writer, Editor, Artwork Creator/Designer and also the person to find, book, and interview the guests--it's a pretty massive job. And all of that with no monetary compensation. That's why I can use your help, please consider becoming a Podcast Patron for my Roll With Peace, In Mind podcast. Your contribution would assist me in continuing to create this valuable free product of service that promotes empowerment, peace of mind, shares stress and anxiety relief tips, inspires mindfulness and positivity. Join my mailing list to keep up with new events, products and workshops Click here *** And lastly, who am I? I am Jacquie Bird of Jacquie Bird, Spiritual Wellness. I have lived as a performing artist, Creative, and teacher since the age of 18. Bumps in the road? Um yeah...a LOT! They hurt? Uh huh, made a grown girl cry. But everything is a step in The Journey, to be Experienced and to be Learned from. Today I navigate with much more Grace, Wisdom, Joy, Intention, Mindfulness, Humor and GRATITUDE. In these podcast episodes, I share what I have learned and am still learning, with YOU. For more on my products and services, hit me up on my site Jacquie Bird, Spiritual Wellness  Thank you for listening!

r/Maliciouscompliance In today's episode OP works for a company that provides online sales services for another business. That other business hires on a big boss is going to take over the online sales technology. The big boss immediately gets into a huge dispute with OP's company. So when the big boss demands that OP's company hands over the code without making any changes, they happily comply! The code transfer was a massive train wreck, which resulted in the big boss getting canned. Oops! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

Like Clark Griswold's jelly of the month club, my red carpet interviews prove to be the gift that keeps on giving. In the Cancel Me, Baby! 2021 finale, I'm looking back on hot-button topics I discussed with celebs before they became more explosive than your local Karen. In Part 2, we hit: masculinity (where'd it go doe), physical interaction (metaverse sex, amiright), AND the young star I talked to about labels and boxes who ultimately came out as trans in TIME this year(!!!) Time to rock out with your crystal balls out. --- Support this podcast: https://anchor.fm/taylor-ferber/support

What would make your podcast better next year? Here are my top 4 tips on how to reflect to get better results from your podcast.  You want results, right?  Okay, then let's get into it.  I released this episode right before the end of 2021… but don't lump me in with all of those ‘new year's resolutions' types. That ain't me.  But, I will admit. This time of year does serve as a good reminder to reflect on what you've done so that you can revamp and get the results you're looking for.  In this episode of Just One Tip, I'm sharing my top 3 (okay 4, since you're counting) tools for reflecting on how your show is doing. And, by ‘how your show is doing' I mean, how well your show is delivering on your specific KPIs. If you're going after audience growth, how are your downloads? If you want to develop loyal fans, how's your engagement? What about leads? Traffic to your website? Invites to speak? Sales? Offers of unconditional love… look, I don't know what you're going for here… so judge for yourself. Look at yourself. That's why it's called reflecting! Here's how I CAN help. Here are my top 3 key things you should be reflecting on about your podcast so you can get results.  1. Check Your Stats for Traction. There are four places I like to look to determine which shows had the best traction:  Titles (which titles generated the highest plays) Topics (what were listeners loving) Time (what length of show generated the most plays) Talked About (which episodes were the most shared). These four things will help you determine what you should be doing more of in the new year.  BONUS: There are a lot of SEO tools you can use to help you determine which shows drive the biggest results but one simple option we like to use is Google Search Console. This helps us understand the keywords that are working in delivering new listeners to the website (and podcast).  2. Customers and Clients. If you're podcasting for your business, then reviewing your clients for the past 12 months can really help you align your podcast… or re-align it as the case may be. Do you know who you want to be talking to (and is it who's showing up)? Take a look at your client list.  If they're just the kind of clients you want to attract? Keep doing what you're doing.  If they're not the kind of clients you want, adjust your content accordingly. If they're finding you through your podcast, hiring you because of the podcast, or see your podcast as proof that you know what the hell you're talking about, HUZZAH, your podcast is working. If your podcast is not attracting clients, building authority or serving as social proof… you need to revisit what you're doing! 3. You. Yes, it's time to check in on you. Ask yourself, ‘how you doin?' This is especially true if you've been podcasting for a while. Are you showing up 100% for every episode? Is the passion still there? Are you doing everything you can to serve your listener? Are you letting little things slip (Oops, I was talking into the wrong mic, oh well… good enough)? You might want to actually listen to a few episodes for this reflective exercise.    Now, here's the hard part. It can be hard to objectively reflect on your own podcast. I mean, you're in it. It's your blood, sweat, and tears. It's your baby. That's why I offer my free 15-minute coaching calls. I can be the truth-teller you need to hear. I can hold up that mirror. I can help you see what's right in front of you so you can get out of that rut and get the results your looking for (and your business needs) from your podcast.  Yep, that's reflecting tip #4. ME. All you have to do is click here to access my calendar and book your free 15 minute coaching call. More clarity is just a click away, book your free 15-minute coaching call in the show notes of this episode or by going to podcastperformancecoach.com. Let's get you set up for success with your podcast.    Book your FREE 15-minute coaching call here: https://calendly.com/timwohlberg   Don't need my help but LOVE all of the fresh and tasty tips I deliver? Subscribe already! Why would you ever want to miss an episode. I mean, each episode literally makes your show better!    Subscribe now. (in this player) Listen to more 5-minute episodes, explore my resources and check out my coaching packages at https://podcastperformancecoach.com/

Its the last episode of season 8 and boy is it wonderful!  Not the episode itself.  Its awful.  way to many long pauses and disjointed conversations.  What’s wonderful is that it means this year is over.  Wait what’s that? You’re saying we still have a week left oft his shit?  *sighs* Plugs and Amazing Folks […]

The Least Haunted Digital Theater proudly presents, Oops! All Christmas! When Cody and Garth mess with The Backwards Carousel of Time in ways never intended, they are thrown into a dystopian nightmare. Now to find their way home they will need to team up with a not so jolly old elf to wage a war on Christmas itself! Featuring The Least Haunted Digital Theater Players: Cody Franks, Garth von Ahnen, Nate Nauseda, Alison Franks, Travis Alexander, and Gunner Franks. featuring Elmo! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

Happy Holidays from Animorphs Anonymous! Welcome to the special bonus episode where we talk about Six of Crows by Leigh Bardugo with special guest Marisa of Alternamorphs fame! In this episode Kaycie huffs a candle, Alex spoiling Orange is the New Black apparently brought about the apocalypse, and Marisa has a smear campaign against a certain eReader but we can all agree Inej is the best!   Join us on the first and fifteenth for new episodes of Animorphs Anonymous and find Marisa @marisamidori

The end of 2021 is upon us, which means it's time for our annual year in review episode! And this time, we've brought a friend, our reliable unofficial fourth co-host, Aspiringspike. We first talk about the biggest releases, bannings, and changes in 2021 for Modern and Historic, then head into the awards show to hand out this year's Diveys. We talk about our favorite cards, decks, and events of the year, then discuss our goals for 2022. Thanks to all of you for another great year of The Dive Down! The Break Down: A Whole Year (in Order!) The Dive Down: Taking and Taking and Taking Become a citizen of The Dive Down Nation!: http://www.patreon.com/thedivedown Get 15% off your first 2 months of ManaTraders! https://www.manatraders.com/?medium=thedivedown and use code "thedivedown2021" Timestamps: 5:43 - Housekeeping 6:57 - The Break Down - 2021 begins! 13:38 - Kaldheim, Oops, all Valkis, and some bans 22:52 - Historic Anthology 4 and Time Spiral Remastered 24:30 - April update, Strixhaven, and the Mystical Archives 33:51 - Modern before and after Modern Horizons 2 43:48 - July and Adventures in the Forgotten Realms 49:20 - Jumpstart: Historic Horizons 52:24 - Modern in October and Innistrad: Midnight Hunt 1:00:21 - December begins and the year ends 1:04:55 - The Dive Down begings - The 2021 Awards Show! 1:05:32 - The Best Card of the Year 1:10:53 - The Non-2021 Card of the Year 1:12:21 - Supporting Card of the Year 1:15:11 - Overhyped Card of the Year 1:20:05 - Overperformer of the Year 1:21:57 - The Deck of the Year 1:25:53 - Most Hated Deck of the Year 1:27:52 - In Memoriam 1:32:36 - Magic Experience of the Year 1:37:13 - The Best WOTC Decision of the Year 1:40:01 - #mtgfinance of the Year 1:40:47 - Our 2022 Goals 1:46:13 - The Best Guest(s) of the Year and Thanks 1:48:40 - Closing out Links from this week's episode: Watch Aspiringspike on twitch: https://www.twitch.tv/aspiringspike Find Spike on twitter: https://twitter.com/Aspiringspike Our opening music is Nowhere - You Never Knew, and our closing music is Space Blood - Goro? Is That Your Christian Name? Watch us stream our episodes every Sunday night at 8pm Central: https://www.twitch.tv/thedivedown_shane email us: thedivedown@gmail.com (mailto:thedivedown@gmail.com) twitter: https://twitter.com/thedivedown

MONSTER PARTY WANTS YOU TO BREAK THE ICE! JAMES GONIS, SHAWN SHERIDAN, LARRY STROTHE, and MATT WEINHOLD, bundle up in their winter shrouds, and brace themselves for this frigid festival of fright  If you basked in the heat from MONSTER PARTY'S SUMMER SLAY-CATION, you'll get a case of the chills when you experience... MONSTER PARTY'S WINTER SLEIGH-CATION!!! As you've probably already deduced, this episode revolves around any horror movie or TV show that involves winter, ice, or cold related themes. We've got alarming lodges, repellant research stations, naughty Nazicles, seasonal slashers, abominable abominations, and an avalanche of more icy awesomeness! Oops, better wrap this up! We're running out of cold synoymns. Joining us for this temperature-challenged tirade, is a long-time friend of the show, and our resident Winter Warlock. He's an acclaimed journalist, magazine editor, blogger, and filmmaker, who's like a hot cup of cocoa for your frozen heart. Please welcome back... DAVID WEINER! (IN SEARCH OF DARKNESS, IN SEARCH OF DARKNESS II, IN SEARCH OF TOMORROW, FAMOUS MONSTERS OF FILMLAND, IT CAME FROM..., ENTERTAINMENT TONIGHT) HAPPY NEW YEAR EVERYBODY! FINGERS CROSSED! NOTE: IF WHEN YOU FIRST DOWNLOADED THIS EPISODE, YOU EXPERIENCED SOME OVERLAPPING AUDIO DURING THE FIRST FEW MINUTES, THAT PROBLEM HAS NOW BEEN FIXED. SORRY FOR THIS INCONVENIENCE. LOVE, THE MANAGEMENT.

SHOW NOTES:  - All the info you need to START is on our website! - Join our PATREON family for bonus perks! - Get your TBR merch - Show credits   FROM TODAY'S PODCAST:  - Find a D-Group Near You! - D-Group Schedule - D-Group FAQ   SOCIALS: The Bible Recap: Instagram | Facebook | Twitter D-Group: Instagram | Facebook | Twitter TLC: Instagram | Facebook | Twitter   D-GROUP: The Bible Recap is brought to you by D-Group - an international network of discipleship and accountability groups that meet weekly in homes and churches: Find or start one near you today!

The Toy Drive is over and we want to start by thanking the Packers community in supporting this year's mission. Just as that was a success, so was the Packers Sunday Night Football matchup against the Bears - that shaw Aaron Rodgers throw for 4 touchdowns and put up 45 touchdowns. Oh yeah, did we mention Rasul Douglas did it again? Thank you for joining Packers fans, welcome back to the IKE Packers Podcast. Number 1 way to help the show is by telling another Packers fan. Other ways to contribute are by leaving a 5-star review on Apple Podcasts and subscribing wherever you get your podcasts. Follow us on Instagram: @WelcomeToIKE Follow us on Twitter: @IKE_Packers Like the music? Listen on Spotify: IKE Music Like hanging out with us here? Check out some of our other podcasts. ikepodcastnetwork.com is your one stop shop for the top rated shows.

Subscribe to RED Podcast – The Marketing Podcast for Experts on Soundwise Click the icon below to listen.