This idea of failure games is pretty much the singular way that I improved my life over the last six or seven years.  Just like everyone else I wanted to get fit, didn't want to go to the gym. I wanted to have a relationship, never wanted to work up the guts to talk to that pretty girl in the smoothie shop. And so I realized if I just do what's comfortable, nothing will change. And that became this challenge that I want to share with you today. What's up you guys, Alex Hine. Now before we jump into this video, I actually have a link down below for a program of mine called Reinvent Your Life. Basically what we do is over the course of a year, every month we have a 30 day challenge where we work on one quadrant of your life that you want to improve. And so we go through health, finances, fitness, relationships, meaning everything. And each month you get a weekly video and a weekly affirmation. It's gonna be opening up soon. So if you want to join the wait list, the wait list link is right below this video. So this idea that if you just do one small thing that makes you a little sweaty every day, your life will get better, is really not that appealing to most people. I get it, right? Why would you want to do that? It's hard, it's a lot easier to sit and watch Netflix and watch Lost reruns or The Office. But that's kind of the whole point here. Point of these failure rejection games is that you're doing something that you ordinarily would use to keep yourself small, right? Now, two examples of my life of how I use this. One of them was that I've always been someone, even though I grew up on the ocean in New England, I never really liked the water, especially the open ocean. I mean, I've been swimming many times in the ocean and lakes and ponds, et cetera. And there wasn't like a particularly traumatic experience, but it's a big, huge dark abyss and you can't see anything beneath you. And I would rather be someone who's in the jungle with tigers and hang out there than be in the ocean, even with fish. So playing this rejection and failure game, I had to do an internship during my undergrad, studying biology and environmental science. And so I chose to go to Fiji to do a marine biology internship where I was in the water 10 hours a day. And this is, Fiji has man-eating sharks, you know? We're talking tiger sharks, bull sharks. Reef sharks are like, that's like old news. You see them all day long while you're diving around the reefs. So I decided that I was gonna get this internship in Fiji for six weeks where literally all damn day, I had to sit with an underwater clipboard and snorkel to count certain kinds of fish and sharks that I saw and clams and coral. So for me, understanding that I could have this kind of irrational fear forever or I could do something that was gonna really be exposure therapy and get in it. And as part of that, the crescendo was that I got scuba certified and I went on an open, i.e. no cage shark dive where they literally just brought a garbage can, filled it with dead fish and we brought it to the bottom of that area of the ocean and then let these massive man-eating bull sharks and tiger sharks just come swim around us at 80 feet. My point is not that, you know, I don't think everyone's gonna do that or be gutsy enough to do that, right? But the point of this failure game is pick one of those little baby fears that you have and find a little bit of a way to expose yourself to it daily. Now another example for me was when it came to weddings, I was always so embarrassed that I was the introverted dude that would need like five glasses of wine before he even did a single move on the dance floor. So realizing I didn't wanna be that dude who was 45 and still doing that and there are a lot of those people, those guys at every wedding, I decided that, well, how do I, you know, apply exposure therapy to this? What do I do? So I started just going to one salsa class, right? It was a small class. It was a beginner class, you're allowed to fail, you're allowed to make mistakes, you're allowed to mess up, like that's literally what it's there for. But just by going to this class, I realized that at the very least, you learn two basic moves and then the next time you're at a wedding, you have two basic moves you can use and it's not gonna be a big deal if you do it on the dance floor and no one knows what it is. So I wanna pose a little bit of a challenge here that I can guarantee will make your life better as fast as possible. Your challenge is to try and get rejected once a day. Now, that could be, you're gonna go to the smoothie shop you normally do and you're gonna ask out the cute girl or cute guy behind the counter there, right? And if they say no or it's weird, no big deal.  But try to pick one thing that you can get actually rejected at. One thing where you're actually a little nervous or a little sweaty. So two things you could do. One, if you're single, you have to talk to a random, attractive stranger and literally try to get their number every single day.  So anytime you meet a stranger that it's in line for the burrito shop, you're waiting in Whole Foods to get whatever. Talk to the person next to you even though you'd probably normally just be on Instagram and talk to them and if the conversation's going well, you'd be like, hey, I'd love to continue this conversation. What's your number? They don't have to respond. They can say no, they can deny you, they can give you the number and never answer it. But the point is to make yourself sweaty and to ask. All right, second thing, challenge. Force yourself to take a class in something that you don't wanna do, but not because you're not interested, but because it makes you nervous. So if you are not that physically coordinated, do a physical class. Take a dance class. If you are not that intellectual, go do something intellectual where you feel like you're out of your element. If it's something outdoorsy, go do like a wilderness survival class. Do wilderness first aid, do survival skills.  It's that your entire self identity changes from someone who cannot do that thing to someone who can learn anything if they put an effort in time. And that when you unlock that, that's like the ultimate cheat code because then almost any goal you realize is just something you can learn and it's something that you can probably reach with time. So in my opinion, the fastest way to upgrade your life is through fear. The fastest path to the mediocre life or to an incredible life is directly reflected in your relationship with your own fear. And it's easy to see what most humans choose. Most people definitely build their lives based on what is safe, which is a synonym for fear. This is doing not what you really want, but doing what is something that is secure and you know you can get. That's playing it safe, which is all fear. And like Carl Jung said, where your fear is, there is your task.  And again, before you guys go, don't forget, if you want more of these 30 day challenges below this video, my course, Reinvent Your Life is a whole year of 30 day challenges. Where each week we get a new video and a new affirmation and some live hangouts. And we go through every quadrant of life to make at least a 50 to 200% improvement and change. And it's the awesome Ultimate Reinvent Your Life program. So you can check it out. The wait list, it's not open, but it's opening soon. The wait list is right below this video. And I'll see you guys in these two other related videos.


This is stock number 10541. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used. Light duty truck headquarters. Today we are checking out this super clean 2014 Ford F-150 Raptor. This vehicle has the 6.2 liter V8 motor. It has been fully safe to be inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off. The truck has been gone through mechanically 100% and is 100% ready to go. Tuxedo black is the color we shoot all of our videos in 1080p 60 frames per second. So if you have HD capabilities on your computer tablet or smartphone device I recommend turning them on right now because it is like you're right here looking at the truck with me and definitely your best way to check out and verify the quality and condition of the vehicle before seeing it in person. It has the factory putter coated step bars and if you want to check out all the photos on this truck in the upper right hand part of your screen as they link right to our website to do that. Painted and polished aluminum 17 inch SVT Raptor rims. It has the Ironman all country mud terrain tires. These are LT 315 70R 17s and they look like they have probably about I'd say 80% of the tread left frame and underbody on this truck is in excellent shape. Didn't see any corrosion on there. Front fenders in really nice condition. I didn't see any dents or dings on that. It does have the HID headlamps.  You also have the front camera forward facing camera on there. Front bumper is in pretty nice condition. I didn't see any major dents or dings on there. Passengers side fender is in nice shape as well. And the passenger side rim, no scuffs or scrapes on that and that tire is just as much tread as the rest. Down this side of the truck you can see just how reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the vehicle, hear the vehicle and have confidence in what you're looking at before you even get here. So then when you do get here there's absolutely no surprises. Cab looks great. That's why we offer the Summit Auto Fastpass option in the upper right hand part of your screen. They link right to our website where you can apply for financing, get pre-approved, see a payment quote, even appraise a trade-off from the comfort of your own home. So that when you get here all you have to do is drive the truck, love it and you'll be all set to go. Frame and underbody looks really good. Lower rockers look great. Has all the remaining factory exhaust hasn't been altered in any way. Back tires have about just a little bit under what the front ones have but still probably about 60-70%. Fox shocks back here, standard on the Raptor and you can see those box rails all look really good. Almost no corrosion on this truck whatsoever. The back rim is in excellent shape and as we come around to the back of the vehicle rear bumper looks really good. Didn't see any dents or dings on that and it does have the backup parking sensors. You get the full towing package with the receiver hitch four pin and seven pin wiring and the tailgate is in excellent condition as well. Locking tailgate, it does have the tailgate step assist. You get the bed extender slash cargo organizer system back here as well and a drop-in factory bed liner. Got that step assist right there. Tailgate lifts up real easy. It is a locking tailgate and there is a backup camera and as you go down this side of the truck just as clean as that passenger side didn't see any dents or dings on the box and for full disclosure this back rim is in excellent shape as well. Does have the capitalist fuel fill which is a really nice feature and down the rest of the side of the truck looks really good. Has the driver's side door code entry which we do have the code for. LED lights, power folding mirrors and they are heated and also get the driver's side blind spot mirror. Inside the Raptor luxury package gives you the black leather and cloth mesh seating. You get the Raptor stitched into the backrest, no rips, no tears on those seats, memory driver seat, factory SVT floor mats throughout. You get the sony sound system power windows power locks. The mirrors do power fold in as well and out. I always like showing both sides are working on used vehicles. You get auto headlamps, power pedals and power tilt and power telescopic steering wheel. As you hop inside the truck here you can see that this one has 50,937 miles digital speedometer or the instrument cluster is very nice and clean it's an SVT Raptor speedometer or instrument cluster. You get the leather wrap steering wheel with the thumb pads and the center orange stripe on it part of the Raptor package. Cruise controls and information center controls on left, Bluetooth and audio controls on the right. Turned out four-wheel drive factory brake controller. This one has the My Ford Touch radio, AM FM and Sirius XM radio capabilities on here and you can see that it did have the factory navigation system as well. You can do your climate controls here. It does have heated and cooled seats. I'm going to turn that seat on because it's only 24 degrees out right now. Stability control. Down here you have your climate controls that you can do here if you don't like using the touchscreen and you can also do your audio controls there as well. It does have a CD player, the sync system to connect to your Bluetooth cell phone. Down here is your Raptor special options, your downhill assist control in the off-road mode. You get four up-fitter switches and your automatic transmission with the optional tap shift. Passengers side all-weather floor mat, passenger seat is in excellent shape as well. This truck's never been smoked in. Power sunroof, home link buttons for your garage door security systems and lighting systems. Headliner is in excellent shape and you get your power sliding rear window and sunroof controls right there as well as some map lights. We'll take a quick look at the back seats and then we will check out under the hood. The back seats are just as nice as the front seats in this truck. No rips or tears back here.  Power sliding rear window with the built-in rear defrost. These seats do fold up for extra storage. It has the Sony 700 watt subwoofer back here, 110 volt, 150 watt plug-in and another 12 volt plug-in back here as well as the all-weather floor mat. Very very clean in this truck and it does have the latch child or I'm sorry the child safety locks on the back doors as well. We'll take a quick look under the hood and I would personally like to thank you for checking out the video today and hopefully from this HD video you'll have been able to tell just how clean this truck is all the way around inside and out. Under the hood we have the 6.2 liter v8 motor engine base. Very clean, runs very smooth. This truck has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. The truck has been gone through mechanically 100% and is 100% ready to go. I'd highly recommend it from a quality and condition standpoint and to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, half-tons, three-quarter-tons, one-tons. You name it we got it go to our website www.summitauto.com full pictures and descriptions from two locations all at summitauto.com. If you want to check out more HD videos you can go to youtube.com slash summit auto. Remember to like subscribe and share on this video and all the videos that you see there in fact in a second you'll see a link to subscribe to our YouTube channel on your left. A link to more F-150 videos like this one on your right if you've not been to our website on the bottom link to this vehicle on our website click those check us out and we really look forward to help you with this extremely clean 2014 Ford F-150 Raptor Luxury Edition. Thanks again.


SCP-618 is a perceptual anomaly causing human beings to have an aversion to green vegetables, commonly cultivars of the wild cabbage, and other food items. SCP-618 appears in 0.5% of the human population. SCP-618 manifests upon the birth of a human subject, though it does not display its effects until the subject grows to eat solid foods. This perceptual anomaly peaks between ages 3-5, then slowly decreases until total dormancy between the ages of 6 and 8. In some cases, approximately 2% of those affected, SCP-618 remains active to varying degrees into subjects adulthood. The effects of SCP-618's perceptual anomaly are less influential, however, and only leave an aversion to the food items, normally culminating in the triggering of the gag reflex upon an attempt to consume the item. SCP-4019 is a substantial disagreement within the field of anatomy over the amount of orifices present on the human body. The majority of anatomical scientists have concluded that humans possess seven openings. However, studies which involve the examination of a cadaver for the purposes of disproving this conclusion universally result in the discovery of two additional orifices. These instances are located on the upper chest and forehead, and allow direct access to the right ventricle and cerebral cortex, respectively. It's noted that effective studies often state that a thin flap of fat and skin covers these openings, preventing blood loss. SCP-4019 was first noted by Dr. Masoud Konstantini. Konstantini states that the walls of the openings possess markings which are similar to those present in the scars of patients which have undergone surgery. In an unearthed entry of their personal journal, Konstantini elaborated on this observation. It was as if these individuals possess two small, foreign objects within their bodies and, sometime before, during, or after their deaths, they had been forcefully removed. SCP-5652 is a microscopic entity resembling an adult female hammerhead shark with an approximate four micrometer body length. SCP-5652 was discovered in Budapest within the bloodstream of Joseph Hemaer, a local architect. Hemaer recently arrived in Budapest from a Caribbean business trip when he reportedly started to feel mild pain and discomfort in his cardiovascular system. Later during a medical examination, SCP-5652 was discovered and retrieved by the embedded foundation agents, but the pain was still present. Two days after SCP-5652's discovery, the source of the pain was found. Ten heavily damaged humanoid automatons of similar sizes to SCP-5652 were discovered embedded in the walls of Hemaer's blood vessels. The automatons were noted to have disproportionately large hands. Further research revealed that the automatons were remote controlled, and a small symbol depicting a modified version of the foundation's sigil was found printed on the chest of each automaton. Weird. SCP-3482 refers to 216 promotional posters produced by Person of Interest, Dato, for Archibald Garner, a right-wing politician running for mayor of Fellowship, Wyoming. All instances appeared overnight on September 3, 2019, in various locations around the town of Fellowship. SCP-3482 instances possessing memetic properties such that anyone who views an SCP-3482 instance will immediately forget the concept of left. The full ramifications of these effects have yet to be explored, although affected individuals will not suffer panic or confusion due to these effects. While the exact numbers are unknown, almost all of the 1,984 residents of Fellowship seem to be under the effects of SCP-3482. SCP-5097 was previously Senior Researcher Cassidy Cara, a member of the Site-17 Extra-Realistics Department. On April 8, 2020, Dr. Cara spontaneously ceased existing. SCP-5097 was discovered after Foundation Artificial Intelligence units detected a sudden loss of data associated with Dr. Cara at 9.58pm on April 9, 2020. At the same time, several personnel acquainted with Dr. Cara had noticed her lack of activity around the site and the inability to access her skip-net email. An investigation was launched revealing her private quarters were completely empty, with the exception of a note, who it was addressed to is unknown. The note left by SCP-5097. I'm sorry, but today I cannot seem to find the will to even begin to can. Therefore, under these circumstances, I will not. SCP-2600-EX is an anomalous species of trout located in- The trout are cytologically identical to speckled trout, but have shaggy white fur covering 90% of their bodies. It is not known what purpose this fur serves, but it is hypothesized that the trout have much lower body temperature than normal speckled trout. All specimens of SCP-2600-EX currently in the Foundation's position were deceased upon discovery. SCP-2600-EX is believed to have the ability to transfer its fur to normal speckled trout via unknown means. Notice to all personnel, Director Dobson has been relieved of his position. Our investigation found a ring of researchers working with the director, falsifying research documents and manipulating data in order to justify further research. As of now, our data shows SCP-2600 is nothing more than a fungal infection. It has been designated explained. You will all be receiving relocation notices to projects more worthy of your time.  SCP-1367, if left to float freely, will begin to maneuver towards the largest gathering of at least six individuals within 480 meters, whose aggregate mood is at least mildly positive. Tests conducted in an airtight room have proved no air current is necessary for the object's locomotion. When SCP-1367 comes within 4.5 meters of a targeted gathering, auditory abnormalities are heard by all within listening range. The amount of distinct speakers seems to be doubled, as additional voices are heard amongst the group. In cases where SCP-1367's effects go unnoticed or are disregarded, the targeted group will find themselves experiencing a slowly elevating positive mood and increasingly fewer inhibitions when it comes to social interaction. At approximately two hours of exposure, there seems to be no further effect. SCP-5812 is the group designation for a series of spectral anomalies confined to the Glasgow Necropolis. Each SCP-5812 instance is visually humanoid, albeit non-corporeal, and is present for approximately 280 days before it disappears. Addendum, investigation into the cause of SCP-5812 appearances. We got a table here listing hypothesized cause and correlation coefficient. For those of you who flunked that class, a value of 1 implies that the two events are positively correlated, meaning one increases, the other increases. A value of negative 1 implies that the events are negatively correlated, meaning one increases, the other goes down. And a value of 0 implies no correlation. The exact cause of the correlation between birds in the Glasgow Royal Infirmary and the de-manifestation of SCP-5812 instances is currently being researched. SCP-014 takes the form of an antique dinner fork, well-worn, and, as nearest can be estimated, not cleaned since the 1890s. The object is fashioned from the electroplated nickel silver typical of the suspected period of its manufacture, and the rightmost time is bent degrees outward. Ground stains and mold adorn the prongs and the pits of the decorated parts of the handle. Analysis of this material seems to indicate that SCP-014 was last used on some form of beef. SCP-014 was moved to this facility in the early 1970s and seems, for all intents and purposes, to be an entirely mundane dinner fork. If it is possessed of any extraordinary qualities, these are known only to those in the very highest echelon of this project's coordinators, whose representatives assure us that SCP-014 is, quote, very important, end quote. Officers who have spent time alone with SCP-014 are unanimous in their appreciation that the object is of great significance, hence its continued presence at this site, though none can quite say why. SCP-6150 is a Vosgod 3KV spacecraft re-entry module bearing heavy exterior damage. Metal implements have welded all apertures on the module shut. An opaque substance covers all viewports on the inside. Occasional noises originate from the object, including metallic pounding, scraping, and muffled vocalizations seeking help in distress to Russian or screaming. Foundation personnel discovered SCP-6150 in an abandoned facility near the Baikonur Cosmodrome. Facility interior displayed immense fire damage. No surviving documentation from the facility or otherwise exists in Foundation custody, though a discovered spray-painted message on the entrance wall reads, translated from Russian. Vosgod 3, which pertains to a thought-unflown space mission, and codenamed Threshold, the context of which is unknown. SCP-5334 is a gaseous planet orbiting the star HD44219, approximately 164 light-years from Earth. SCP-5334's ring system is composed of approximately 2.7 billion glass bottles, each containing various alcoholic beverages. Analysis of recovered bottles during a faster-than-light anomalous exoplanet survey suggests they are at least 800 years old, and each bottle's alcohol content is exceptionally high, ranging from 40 to 70%. The bottles have no discernible markings or identifying characteristics besides damage caused by micro-impacts. Approximately once every 200 days, roughly 20,000 to 150,000 glass bottles will spontaneously disappear from the ring system. Following this, SCP-5334 will undergo multiple erratic alterations to its orbit, deviating as wildly as 20 degrees from its stable configuration. These erratic alterations will slowly become less prominent, and will eventually result in SCP-5334 returning to its original orbital path. Moved to Site-19, 1993, Origin is as of yet unknown. It is constructed from concrete and rebar with traces of Krylon brand spray paint. SCP-173 is animate, an extremely hostile. The object cannot move while within a direct line of sight. Line of sight must not be broken at any time with SCP-173. Personnel assigned to enter the container are instructed to alert one another before blinking. Object is reported to attack by snapping the neck at the base of the skull, or by strangulation. In the event of an attack, personnel are to observe Class 4 hazardous object containment procedures. Personnel report sounds of scraping stone originating from within the container when no one is present inside. This is considered normal, and any change in this behavior should be reported to the acting HMCL supervisor on duty. The reddish brown substance on the floor is a combination of feces and blood. Origin of these materials is unknown. The enclosure must be cleaned on a bi-weekly basis. SCP-5991 is an anomalous phenomenon that triggers whenever a human successfully consumes an entire Christian Bible. When a subject consumes the Bible, an entity will manifest in front of them, referred to as SCP-5991-1. SCP-5991-1 is a pale, emaciated entity with no orifices besides its mouth. SCP-5991-1 has no teeth, does not possess eye sockets nor eyes, and is wearing a crown of thorns. SCP-5991-1 will approach the subject and unhinge its own jaw. SCP-5991-1 will then violently shove the subject down its throat and into its stomach, which is noted to be much larger than SCP-5991-1 on the inside. Once the subject is consumed by SCP-5991-1, they will land on a wooden boardwalk, which is built on a floor comprised of biological tissue of unknown composition. Subjects are able to freely exit the stomach by pressing a large, pulsating orange sack located behind where the subject lands. SCP-4574 are two animate conglomerations of primitive spears, hand axes, clubs, and javelins, each in the shape of a smiley-dawn. The weapons compromising SCP-4574 are of similar craftsmanship, and many are decorated with feathers, leather strips, carvings, or dyes. The majority, approximately 80% of these weapons, share similar compositions, and collectively date to approximately 13,000 BC. SCP-4574 inhabit a large, partially submerged cave system in the state of Quintana Roo, Mexico. Cave paintings line the portions of the cave above water, dating to the same time period as the spears. SCP-4574 guard the caves as a pair. They will not attack those who enter unless the intruder attacks them, or attempts to touch the cave paintings. Otherwise, SCP-4574 are relatively docile. They communicate with each other verbally in an indistinct language, and show signs of intelligence well beyond that of ordinary felines. SCP-1057 is an animate, empty space, 5 meters long, in the shape of an adult tiger shark. It does not appear to have any mass, however, it displaces water by an unknown mechanism. SCP-1057's refractive index is approximately that of air, which makes it partially visible when immersed in salt water. As well, its anti-shadow is discernible under bright light. Experiments involving the insertion of inanimate objects into SCP-1057's quote, body, have revealed that there is nothing there. However, further experiments along these lines are contraindicated, as this triggers extremely aggressive behavior on the part of SCP-1057. SCP-1057's behavior has been assessed by Foundation ectiologists as being within normal parameters for an adult tiger shark. Many food consumed by SCP-1057 disappears, with the exception of the non-digestible fluorescent dyes, which are regularly added to SCP-1057's food to facilitate monitoring its behavior.  While SCP-1268 is capable of basic motor functions and self-maintenance, it does not appear to be capable of communication, nor does it show signs of emotion or higher intelligence. SCP-1268 will wander aimlessly, until it is in proximity to a large group of people. In these situations, SCP-1268 will go into the crowd and slowly move through it. During this process, the behavior of those in the group will be altered in a predictable manner. 0 to 2 minutes, no effects are visible. 2 to 7 minutes, persons in the crowd are visibly nervous, turning their heads frequently and moving more quickly than before SCP-1268 entered the crowd. 7 to 14 minutes, persons other than SCP-1268 begin to experience disorientation and confusion. 14 minutes forward, almost all persons in the crowd panic and attempt to leave the area by any means necessary. Subjects affected this way show a distinct lack of concern for the safety of themselves and others. Anomalous effects will cease after SCP-1268 is no longer in the crowd. SCP-6555 refers to the remains of an unidentified structure on the rogue celestial body of XCO-8537-A. Discovered in 26576HE, after deep space satellites detected faint electromagnetic situations, SCP-6555 emits a constant broadcast of archaic emergency radio frequencies from its epicenter. Research probes dispatched to the surface of XCO-8537-A for observation of SCP-6555 have, thus far, been inconclusive. The configuration and layout of SCP-6555 suggests that the structure was at one point semi-modular, ventilation, air conditioning, and other primitive systems present within SCP-6555 show that the interior of the building was once adequately maintained and supplied with oxygen. Miscellaneous calcium fragments and ligaments, almost identical in DNA composition as that of ancient mammalian organisms, were discovered nearby SCP-6555's central transmitter. Fragments have been dated to be at least several thousand years old, indicating unnaturally quick and potentially anomalous decomposition. SCP-590 appears to be a young male, approximately 16 years of age. The only benefit he receives from his powers is apparent longevity, as he is not age since his arrival at the Foundation. Although in all aspects a normal teenager, when SCP-590 touches any other human, he heals all injuries and ailments physical and mental they may have. As an odd side effect, SCP-590 receives the injuries upon himself, being subjected to all the pain and the aftermath. To elucidate, when healing a physical wound, SCP-590 not only feels the pain of receiving the wound, but gains scars relevant to where the wound was on the subject. Any mental healing performed is transferred directly, resulting in SCP-590 gaining whatever mental aberration he was healing. Those wounds he receives from using his powers accumulate. SCP-4564-A is the collective designation for all first run copies of the video game Fishing Derby. The initiation of SCP-4564's anomaly occurs when any instance is played upon an Atari VCS Games console. Anytime a player successfully catches a fish with the value of 6 pounds, a random eel matching the above criteria, henceforth known as SCP-4564-A, will proceed to exit the water in search of the nearest human being. Hereafter referred to as SCP-4564-B, the SCP-4564-A instance will attempt to insert itself into the human's gastrointestinal tract via the anus or mouth. The SCP-4564-A instance will release a neurotoxic slime, which induces a powerful urge for SCP-4564-B to travel to the sea. Upon reaching the sea, an SCP-4564-A instance will exit the victim's body via the first submerged orifice. Both will proceed to lose all anomalous effects, although often distressed. SCP-4564-B have never been harmed and can be hosted between one and ****ing instances of SCP-4564-A at a time. Thank you for listening.  Please become a patron or visit our merch store at the link in our bio to support our work. Secure. Contain. Protect.


And on the Kyle Kuzma side of things, did you ever look up and say, what in the hell are you wearing, sir? Stop worrying about cool stuff once he did the pink sweater. I was like, yeah, I don't even wanna ask questions at this point. Oh, the giant pink sweater with the sleeves? Yeah, yeah, that one got me. And once I seen the pink sweater thing, I was like, yeah, it can't get no worse than this. It can't. And then I seen the big, yeah, I seen the big bubble jacket that he wore the day we went to play Brooklyn, if I'm not mistaken. And the collar of the jacket was like at the top of his head. I was like, bro, what are you doing? God, I love it. I love it so much. He gives us stuff. Is he getting those made?  Like, how does that work? I don't know. He's real big and passionate. And he tells his stories all the time with just like all the stuff that he wears and whatnot. You know, I was like, yeah, man, that's cool. And all, but some of the stuff, some of the stuff is getting outrageous. You know, it takes up a lot of space and you're locked.


Hi Frederick, how's it going? It's going well. How are you doing? Not too bad. We'll see how successful all the Americans are at switching time zones today So I just dropped the link to the meeting minutes in the chat for everybody that's ready Then we'll get started Probably about like five after so thanks for joining today Once again, thanks everyone that's joined so far I dropped the link to the meeting minutes in the chat if you just want to add your name there. That'd be great Okay, once again for people that are just joining. I just dropped the link to the meeting minutes in the chat And we'll get started in about a minute here So thanks for coming today Okay, it's five after I think we can probably get started last time meeting minutes are in the chat in case you Need a link to them Thanks everybody for joining. This is the weekly seen up working group Meeting we meet every week at 1600 UTC so for people in the US. Yes, that did just switch for people in Europe We'll switch and I think like two weeks. So time zones are fun Before we get started. Is there anything that anyone would like to add to the agenda? We can probably Jump right in then so the first one is the use case template That book put together so This one's been open for a little while now See Ian on the call But I went through mostly comments before this all the ones in the file Have been resolved The only one is Sorry, it wasn't Ian's comment. I think this is actually Victor's yours That Missing what Qnative is in the glossary documentation Yeah, well, basically he refers to cube Cube native term So basically the comment is like if we can add it in some place Maybe not in this argument, but probably in a glossary where we can use it as a reference I Mean I was arguing about Off-tangent I have to say I think I think Victor's exactly right if we're gonna use the term and it means something It would be good idea to write down what it means to us. Okay Yeah, I guess I Think this has been open for a while. Would you be okay if created a separate issue for that? Yeah, I think I mean, it's not related but as long as we address that concerns, it's fine Okay So So I'll add that after this meeting. I guess Beyond that, I know there's quite a few people on the call here who Haven't approved it yet, but they've made comments. I guess is there Does anybody else have any I guess like It's comments, do you think we can merge this like thoughts? You'll see the comment I've just literally added two minutes ago might not be on your screen yet at the very bottom I think that one does want addressing There's two parts to it one of them I care about one of them not so much the one about numbering Don't care one way or the other just make a choice The one about the sub directory. I think that one does want dealing with a sub directory be a much better idea Because you tend to want to include images and stuff in these documents. So having a sub directory means you've always got somewhere to put them Okay, and you're saying There'd be The sub directory under this use case for like images You're basically what happens it what we did for the other one is we made a sub directory Which should have the name of the file and then the file would become a read me in that sub directory Okay, I got you. So instead of this being Directly under it. It would be in a different folder. It would be that slash read me MD. Basically. That's all it would take That's the only thing Yeah Okay, um, I Guess I don't see look on the call I guess I get what you're saying there, too Yeah, okay, yeah, maybe and then yeah, actually the problem was like The scope of the SPR was increased. I mean initially was Yeah So I guess like the templates find it just we want to do the actual like use cases and dip slightly different format Yeah, so probably we can request to split it. I mean, I'm okay with the template, but now I have to review the use case Okay Maybe we can ask to like split out the Like the templates fine and then make the use cases as a separate pull request Yeah, and then I guess maybe we have the discussion on that On that PR then too And yeah, I think Ian. I think you make a good point where We potentially want to do as a as its own separate folder and then I guess maybe we Also create an issue that the BGP use case means to Numbered at some point too Yeah, the one thing I would say about numbering is again for now at least we can choose but I Can see that what we might run into is if we start getting a flood of use cases They're all going to take number five if it's the next number going and they'll conflict with each other So that one might be a minor irritation, but again, it's not the end of the world It's it's like ten minutes of anyone's time to deal with so either way will work Yeah Yeah, I think I think we can probably cross that bridge when we come for right now. It's It's a potential for problems, but Okay for now Cool anything anyone else wants to add on the use case template. Okay Cool next one is the defining the different actors and the roles This one's been Open for a little bit I guess does anyone of you want to raise their hand and volunteer to Define the actors and their roles. I know there's a lot of content around this I mean, we can also leave it open for right now, too. I can have a go. Where are we gonna put it? That's up to you Okay, fine Then we'll make a top-level file for it and another one for the glossary that we keep talking about and That and if we want a glossary then let's add that as an issue as well Okay Let me do that now Are you creating an issue for that? Yeah, okay, great. Thanks, then I'll just note that down in the meeting minutes, too Okay, great. Thanks, Ian Then I know this one sparked quite a bit of discussion at the last meeting about adding the maximum representation for Roles, I know you and you write out wrote up quite a All long note on this I guess the question being Do you want to add any of this to the pull request? Are you fine with the pull request as it is? if We are concerned about this. Well, I'm not terribly bothered if it's a second pull request to be honest But it wasn't me who had the concern it was Shane and towel particularly worrying about their their IBM compatriots, so their choice but I Think this is big enough and might lead to enough debate that a second pull request would actually make a little more sense now you say it Okay Tal do you have any thoughts on this? um It looks good to me, but Shane was the one with More concerns, so I see he's not on the call today. So If you'd rather wait for him before emerging or Well, if we make this a separate pull request, we won't be merging it with this We'll be merging it without and saying we haven't quite got there. We'll fix it up And then there will be a second pull request and that will make him easier Easier for him or you or anyone else to edit, you know a couple of words within it if if that's what you want to do Yeah Check the slack real quick because didn't he comment on his concerns in there and potentially them being addressed Yeah, I'm saying it was okay, but I guess he didn't actually put it on GitHub I've read your comment and I think it represents and resolves my concerns completely Yeah, Jeff had one that I think was more about Wording and you know a response I'm giving him in slack is not what's going into the pull request So what he put in there might be might be worth a little bit rewording as well But if we make a separate pull request, you can deal with it then and there and then it will be in the right place Okay, so I guess the consensus then is to merge this and then there'll be a separate pull request Kind of addressing the discussions from last time Is that correct? Yeah Okay, and then I guess in the question is do you want too many creating an issue for that or? Yeah, I wouldn't normally but if I don't create an issue I'll forget so that's a good idea actually Yeah, can you just copy paste this into? Like an issue that'd be great and then And then I'll merge this for now. Okay Um, so thanks for that And the next thing is around the PR approval process. I know this is like something that is that was brought up a little bit earlier around Like who should have the ability to like merge your process or like how should we do it? I guess is there any more like discussions or ideas on this on what we say is like What a PR has these approvals Then we can say it's ready. I guess the thinking one of the ideas last time was there's a minimum of three approvals and Someone should have a veto power. I guess maybe I can I'll take it on myself to Maybe put together a first PR for this out of the discussion so far and then maybe that'll Kind of spark some further discussion Yeah, they'll look to me if I remember correctly. It's like this was depending of the the roles or like another PR that we have So I think that you merge the other one so maybe that can clarify This discussion as well. I think so Oh, you're you're talking about what the The roles yeah, I think so now that we have that one probably That discussion can continue or yeah, but if you carry that the PR would be much further I think Are you talking about this one? Yeah, so you're saying I should add to this PR. Is that correct? Yeah, I guess is you Yeah, once that you create a PR maybe You can refer to these ones. Okay Yep Yes, is there anything anyone else wanted to add to the discussion overall on the call together? if not people can also Add it later to or message me or just add it to the discussion. Okay The other thing is I know Oliver made this I think about like two weeks ago of creating like a high level roadmap of ambition for 2021 I was wondering if people had a time to look at this had like any thoughts about this I mean, we could also say this is something for the co-chairs to figure out to once they're elected No thoughts discussions ideas. I guess we can also wait for the co-chairs to Provide more insight once they're elected to Before we get into the elections I saw there is also Ian you had a deployment use case. I guess did you Want to add anything about that? Yes, I'm a terrible person. I wrote this weeks ago Run it around a couple of people who are variously objected to it So I need to kind of back off on the opinion in it, which is completely fine It should be unopinionated that cell point But the idea here is And I would add there's a couple of other basic ones here I Should know how to deploy a bit of cnf right? I start with a network that has nothing running on it And I want one cnf to run in the network possibly in a variety of places I want to know how I get from a to b basically and I would add the next one that follows that is probably debugging use case Which is I have cnf's running on my network and the network isn't working the way I expect it to How do I find the component at fault and the reason I think these two are important is the first one deals with Elements of Orchestration that no one's really defined terribly well in this like you know, how do I get the software installed? How do I actually start a cnf because there's no such thing as a Kubernetes application in that regard the second one deals with Responsibility boundaries, so how do I know which cnf is broken or if the platform is broken? And that one I think is the one that we were talking about weeks ago that would say well privilege is important lack of Privilege is important because with privilege in place if you're allowed to have privileged containers You can break the platform and nobody can tell who's at fault So I think once we've got those two written down then we can start getting quite creative with the use cases At that point with the sorry with the best practices at that point because we'll have something to hang them off of And you know, we aren't doing much in the way of writing best practices at this point. So that would actually get us moving Cool Yeah, so it sounds like you have like quite some thoughts and probably even a document behind this stuff Other people are interested. It sounds like Ian's the person to talk to Yeah if you have Your own thought about what that deployment use case looks like or what that debugging use case looks like I would Greatly welcome your input to be perfectly honest.  I want this to be Well, we're all going to have to sign up to it at some point And there's no point in doing that, you know in a long rambling argument in the in the poll request So sooner you get the your thoughts across the better the result will be Okay, cool. Yeah, so the people have thoughts or experience on deploying stuff, uh, please message Ian cool um Is there anything anyone else wants to add to that or ideas to throw out right now? okay And that just brings us to the last point On the agenda Is the elections. Um, so currently for the co-chairs for the service provider chair We have self nominations from jeffrey and uh book From for the cnf developer chair. Uh, we have ian victor and gear gay For the kubernetes community chair. We currently have no nominations. Um, the nomination trade is also open until The end of the day So if you're considering run running for the kubernetes community chair Please feel free to throw your A name in the ring. Um, the only other thing is Um with shane, um, he nominated himself, but he didn't say which chair So I don't know. Tal. Have you spoken? Uh, with shame. Um, yeah, I Uh Can you remind me what kind of chairs we have should be obvious? Yeah, so it's the Service provider the cnf developer in the kubernetes community chair So we are we can only be I think a community chair Okay On one point there, I wonder if we can just save ourselves a little bit of trouble because I realized that I made a mistake In my nomination and I think it's fair to say the others did as well Where everybody who stood for a chair can we just basically make a blanket assumption? They're also standing for a tech lead Yeah most people nominated for both and Nomination period is open till next week I guess Is there is there something specific you wanted to address the man? Well, I've been to know if I need to send another email But I mean I think to be quite honest anyone who's stuck the name in for chair is probably well qualified to be a tech Lead as well. That was really the thought Yeah Yeah, I think you're I think you're you're right that the nominations can carry over So I'll follow up with Shane and In slack and ask him to clarify in the mailing list Which position which position he's going trying to run for Um The other thing I wanted to point out. Is there anyone on the call that hasn't added their company to the interested parties That would like to vote in the election If you're interested in voting, please feel free to add yourself to an interested party here and well Happening merge that too So how does that work if The company I'm not it's not really interested in this particular space But I personally am interested in possible votes um I guess would you feel comfortable adding your name? Yeah, I'm fine with that Okay, I mean I Think that is fine too if you don't want to put down your company's name but since we do have organizational voting obviously we can't just have everybody putting down their name but um Say for instance like I'm just picking an example like tal and shane can both put down their name because their employer is red hat and so That's what it goes back to so I guess technically you would Be listing yourself as the interested party, but you'd be representing your company Or you'd be voting through your company Yeah, that's the problem is that the company I'm at is a healthcare company and they're really not interested in this kind of stuff And they won't want to be represented in this kind of a thing. So that's where that comfort comes from Yeah, I mean, I think it's Like quite fine unless anybody else has any disagreement about that Um, if we go kind of barric room lawyering then basically that seems to make frederick an individual contributor and shut his company um You know show any more interest in the area in the future Then we can the rules that I'm supposed to be writing regarding Company representation would start to kick in somebody could say but frederick stands for his company. He isn't individual anymore Yeah, yeah Um, that makes sense to me and I'll I'll also add that I uh I'm surprised we don't have uh academics involved too. Uh, I know a lot of universities do research on these things and graduate students are writing dissertations Um, uh We we obviously want to allow participation from that part of the community as well So if we ever do get somebody I think they They would also count as an individual contributor rather than say representing a university which Just doesn't make sense really Is there any reason not to list individual contributors in the interested parties? I mean Well, I need to drop for another call, but uh, you know, thanks. Thanks for listening to me on this Yeah, thanks frederick I would add I would add arm in the list as well Okay, um Without us fill up, right If if unless anybody has major objections, I can also just add this on the call right now Just wanted to say hello. Uh, I joined in the meantime book is here Hey, look, how's it going? Bit busy What what's um Pretty probing Is it two L's it's one lwp Uh, sorry Is that correct? Yeah Okay, I'll merge that too. Does anyone else on the call want to be added? Also, feel free to add a pull request too and um Yeah, thanks for people that are adding the notes in the background for me too And all the miss camel. That's great Bill what's the timeline Yeah, what's the deadline for adding to interested parties? Um Right, I think we can be kind of friendly about this. I would say probably like to like today ish Like if unless you don't think you can make that deadline like I think we're trying to encourage participation not block people out um So we're happy to add more people like if you if you need more time, I think that's fine too. But um Yeah, I guess do you know when you'll be able to Have um yemwear well Uh, I'm not sure I need to uh get some uh confirmation. So uh, that's why I was asking because you know Today's a good deadline to put in an email and say hey, we need to close this So thanks Yeah, so if you can do that, that'd be great. Um, if not, I don't think people are going to be like Absolutely, we can't do this because you missed the deadline We're trying to encourage participation by everyone Hey, bill Yeah, should we come up with some type of like Quarterly by annually something like timeline to use like as cube cons roll through this and that um Obviously, we don't want like just kind of constant tsunamis, but you know The example just given like I know in the past um Typically like if you have a anal legal department like I do they want to go and review, you know repos things like that. So Um, you know, it's not always just like I unilaterally make a decision to be a quote on quote contributor. Um Do we want to set some type of um You know things for like, you know, maybe like after every cube con or something We do like an update to the contributors list. Um, or interested parties list Gives people on the chance, you know, they go to cube con they go back talk to their bosses, etc And we kind of make some type of formal thing. So Like we're encouraging participation, but we also kind of give people like Things that they can point their employers at like say like hey, you know the next round to like become an interested parting Start voting is that Specific timelines and deadlines for that. I would go more for a like a more agile approach Like if somebody's interested then they can just put themselves I'm okay with that as long as people aren't worried that like You know, some wedge issue shows up and then like a bunch of people suddenly add themselves Like I mean, I'm personally fine adding whenever as long as you know, people don't mind managing the list I would go with this like organic way I'm just from personal experience saying that if there's something on the repo that says, you know next round of whatever Is it's such in such time? It's easy to send that to a legal department. Say please don't procrastinate on this. That's all like It's not about like creating artificial barriers to people. It's just if you've dealt with like some of the kooky illegals you've maybe Looked for some of these types of verbiages to pop ups that you can kind of pressure them a little is all Yeah, definitely um I guess the question then is like, how do we balance it to not discouraging people from Participating but also like encouraging that I guess Maybe Jeffrey would you be interested in taking like a first stab at that language just because I'm not super familiar with what legal would need Because I haven't worked at a large company And then I think we can have a discussion About if we think that fits the needs of the community I let it go here. Just a quick question for this one. Um Could that work if we use like the election date the next one because I assume that's what we need the interested parties for as kind of the The date for legal that I want to participate in this and for that I need to be or I need the company to be listed here and that's your deadline Could that be a solution without creating extra deadlines and rounds on this? Yeah, I guess Yeah, I think that's that's a bit less confusing than Than having to connect to deadline And do we think that like I think the company name is the problem for legal or Contributing anything to repo is a problem for legal I think it's more just motivating legal departments that aren't like super Motivated to like go in and look at things to understand your motivation things of legal in this because like I think the company name Is more like trademark issue than legal Um, yeah, so I think that was a really good suggestion. What if we say Uh, we can add companies at any time, but the deadline to be in each election is Like two weeks before the voting starts or something like that Yeah, and then I was thinking the same thing bill Like when Ildico made that suggestion is just like you can add people anytime, but like I said, um So to your gaze exact question like I will submit something and like I mean I had to go through an approval process At the very beginning of this to like have chargers name at the bottom like You know, like do we put our name on something yada yada like let us review. Um, it's just a thing and I mean, I'm not saying that it won't always happen. It just sometimes it takes way longer than I would like it to Like our VMware friend, you know, it's like I I'm going to try like it's it's helpful to have the by the end of the day email, right? So like I said, I really like the more participation the better whenever we bring people in the better I just know that sometimes if I can point to a link and say look elections are coming up at this time Can you please, you know Get off your hindquarters and make this happen for me. It sometimes is advantageous for me I second that I also think that it's not entirely clear What what does that mean if you're interested party, uh, if you put your name out there What is the commitment and that's for sure the first question lego is going to ask well What are you committing to do if you put your name there? So I don't know if we want to complicate it that much Yeah, I'm insane here from the arms side. I've not run that past our legal. Yes. I'm principle We are interested but the legal implications of that I would I think if if we can clarify bill, what does that mean? um If you're if you're putting your name on the list and they would probably go a long way for those of us who has How should I say this a legal department that likes to weigh in on things Okay. Yeah, I think That definitely is not especially clear right now Um Because if it's an initiative with some bios and kind of membership agreements, it's much clearer and different in this case. It's not quite Yeah, let's make sure we it doesn't backfire because as someone who works on a relatively rigid corporate We managed to get our name there quite easily Because there were no definition of commitments and so on and so forth if there are I think our legal might weigh in so we need to balance this. Yeah That's a good point. So ronnie you're basically saying since it's not specified Don't throw a name in there and legal will be fine. Let's say I like that. It's a pragmatic approach No, I mean that's kind of the approach I took Full honesty and really all I told legal was that um, you know, our company name was like We're going to say that like, you know, we should be following best practices, right? I mean, we're not writing standards or anything here But like the thought would be is that if our name is on that list at the bottom and something's the best You know practice that you know charter agrees with that and that might change later once legal looks at this harder I don't know. Um, but that's kind of the pitch. I said was like a we're putting out general guidance and trying to Get some type of conformity around rfps and like vendor engagements, etc I think uh legal would Legal would always be concerned about whatever the liabilities are and I think it could be clarified that there is no liability Uh involved here Or maybe it's not so clear, you know, what what happens if we do Put some best practices and somebody is hurt And decides to sue cncf for whatever reason and I'm I'm being very wild here with my uh imagination. I know Um So I think the legal liability is Is under the license. Um, so it's apache 2.0. So I think I'm not a lawyer, but it's basically It's up to you All right, what you do with it is it is your responsibility in terms of What the interested party means, I think This is like a bigger discussion. So I'd like to like create an issue about this and like move the discussion there because I think there's been some great points on this call and I guess we don't really have the answers yet Right. This is like, I mean, this is the first time we're kind of doing this in this group um, and so maybe the Kind of like the loose definition is work so far. Um And it'll work kind of like through this initial phase, but as we kind of Build out and get a little bit more structure we can Yeah, I guess maybe define that a bit more too I guess to like legal departments aside too if we have people who You know, never attend a single call never read a single pull request this and that Do we just let anybody vote like I don't know if there's like a bar um I'm not saying that there needs to be but like the whole interested parties thing is really like literally just at its base definition I'm I'm just saying that I'm interested in this Yeah, I mean we we wanted at least at the beginning to keep it very loose to encourage participation and discussion from Anybody who wanted to be a part of it. I think as this becomes larger, you know, right like governance Scales as the organization or like as the community scales I think we've seen this a lot of different organizations or different projects across the CNCF and so I I would actually leave this up to kind of the Co-chairs that get elected to define If they want to change the governance process Like what like what's a better way to do it? Say I don't think we're going to solve it today I'd say and yeah, should we create a bar like potentially But yeah Well, if somebody creates a pull request to add themselves as an interested party That pull request isn't automatically merged. So yeah, I guess it's uh It's up to the co-chairs, right We're not the first one to do a project in this In this organization, right? So why don't we get bill? Why don't we figure out for CNCF who What are the bylaws or what's their guidelines and just add this and though It's like the millionth project, right? Yeah, there's a lot of stuff in CIG contributor experience Under CNCF and that's actually a report like the organizational voting from and so there's A lot of great information there. So it's a potential source to look at if people aren't familiar They're a contributor strategy. Sorry Um, and they you're right. They do have a lot of stuff on governance and so let's just say this follows the CNCF governance blah blah blah contribution strategy and We don't need to reinvent the wheel. We just we refer to what everything else is being Being done, right? Yeah, that's the funny thing about CNCF though is we require Open governance, but we don't say how you have to do it. So every project can do it differently So we just have to choose one of them. I'm not saying We can't point to one. That's I mean, we just pointed to fluent D for doing the voting Um, and so I just copy it's just like which one do we want to do, right? How did Because CNCF is all about choices Yeah, um, so I think this is a super good discussion. Um And I think it's definitely something that we should track for the future Um, I don't think it's going to affect this current election unless people See any really big issues um Yeah But I think it is important to discuss as we kind of get more and more formalized, right? This is the process of Building out the actual structure of what we're doing at the same time Okay, um Are there any additional questions comments concerns issues pull requests? Actually one thing Look, are you still on the call? I'm in here Yeah, I guess you were just so so the comment that you want You discussed before to split the use case example use case out of the template Yeah, exactly. So if you can Split the example use case good, um out we can merge the template and then I think people want a little bit of time to look at the use case specifically and Ian had something here where It might be helpful to have a structure Where you have a sub directory and the readme file is the actual use case Because then you can add images and other things like that okay, I Told adding an example according to the template Would be also helpful for understanding template And it's a real use case example at least I Try to to find out the one that is not that long, but that's still descriptive and illustrative so I Might either put it in a readme or or simply just for a time being leave it out Of this merge request and then create another merge request separately so that we can discuss that use case I don't think anyone's got any debate that you're making sensible choices in applying the template But yeah, you don't want your template to get hung up just because your use case You know wants discussion. So I would I think it makes sense to separate the two for all that You know logically what you're trying to do is demonstrate the use of the template Yeah, so I think everybody's agreed the template's great and we can merge it and then We can discuss your use case separate and then yeah Okay Do that Awesome. Thanks cool Anything else? Otherwise, I think Everybody can have back nine minutes Okay, thanks everybody for coming today. I really appreciate it Thank you. Have a nice day. Thanks bud