Warning, this SCP reading contains descriptions of sexual content and other not-safe-for-work material. Viewer discretion is advised. Item number SCP-835 Object Class Keter Special Containment Procedures SCP-835 is to be monitored and checked daily for new growth. In the event SCP-835 becomes hostile, suppression tactic AA-6 is to be immediately implemented until aggressive action ceases. That area must be maintained in open ocean, due to the highly aggressive response of SCP-835 to confinement for any length of time. Waste issued by SCP-835 must be immediately collected and contained. Feeding of SCP-835 is to take place twice daily to consist ██████ SCP-835 may be moved to a new location twice yearly, provided that the current location is no longer capable of supporting SCP-835 and the move had been approved by Site Command. Staff are to remain at least 5 meters away from SCP-835. Anyone working near SCP-835 must have safety lines attached to recall winches. Contact with SCP-835 will result in the immediate recall of all staff, and implementation of suppression tactic AA-6. Should contact result in full capture of a staff member, SCP-835 is to be monitored constantly until the release of the subject. Description SCP-835 appears to be a large mass of coral-like polyps weighing 8 tons. The individual polyps are larger than any known coral species, growing to more than 1 meter in diameter in some cases. The central mass is roughly oval shaped, with a very large, 3 meter diameter polyp at each end. SCP-835 is incapable of locomotion and appears to anchor itself with the large tentacles projected from the SCP-835 polyps. These are also used in feeding and are coated with a sticky adhesive substance. The tentacles are also quite strong and have been shown to be capable of damaging plate steel. The coral of SCP-835 is extremely hard, requiring high-powered diamond drills to collect even small samples. SCP-835 also grows at a very accelerated rate, capable of adding 22.68 kilograms or 50 pounds of mass every day. SCP-835 is susceptible to many chemicals, which cause SCP-835 to seal up and halt all growth for 24 hours, prompting the development and use of suppression tactic AA-6. Testing has shown ██████ SCP-835 emits a large mass of semi-liquid material several times a day from the large pods at each end. This appears to be made of semi-digested solids, fecal matter, and semen. This mass also has several forms of virus, bacteria, and parasites, many of which have been found only within SCP-835. The bacterium 835-I-5 forms the major concern for containment due to ██████. This coupled with the extremely hard shell of SCP-835 form a major obstacle to neutralization. Any force capable of cracking open SCP-835 would also cause the slurry inside to spread and cause additional infection from 835-I-5. Addendum 835-01, first draft of after-action report by Mobile Task Force Zeta-9er, Circumstances of Retrieval, on ██████ at ████ hours, Mobile Task Force Zeta-9er, Mole Rats, conducted an investigation of SCP-835. At this time, SCP-835 had a mass of only 4 tons and only one large polyp at the north end of the structure, designated Polyp Alpha. Polyp Bravo not yet being in existence. As per standard procedure, four team members were chosen for the initial investigation. Standard isolation suits, underwater variant were worn by all four team members. Lieutenant ██████ took point as team leader while sergeants ██████ and ██████ served as support. Corporal ██████, a rookie team member, accompanied the team as an observer. A standard underwater remote vehicle, or URV, was used for initial investigation. SCP-835 did not at first act in a hostile manner towards the team, allowing team members to approach and make contact without incident. URV-01 was sent to investigate the exterior of the object, while team members C, L, and M proceeded towards what they believed to be the entrance of the site. Corporal ████ was ordered to remain outside and to monitor URV-01 in order to ensure the device's tether did not become tangled on the exterior protrusions. The first sign of trouble occurred when Corporal ████, while attempting to clear a jam in URV-01's sampling claw, reported in with the words, ██████, Oh God, help me, help me.    Christ, alright, here goes, guess I'll just let Sarge edit this for me, again. So the thing grabbed the kid, it had me full to rights, the entrance wasn't an entrance, it was just some cave. The real entrance was the big polyp thing on the north end. It grabbed the kid and started dragging him towards the mouth, top side started to drag him up, but all they got was a snapped cable, and the kid, he got pulled inside and eaten. God, I still remember him screaming.  I'm shouting at him to calm down, we're gonna get him out of there, and then top side tells us to abort, and they start to winches. I'm screaming at them to wait, I had his hand, I had him. I had the caribiter on, we're hooked together, and top side starts winching us up, and we're not getting anywhere.    I saw that on TV once, it was like that except I was going down to throw to some horrible underwater hell monster, not up some poor bastard's rear. There were these muscular contractions, I guess, and they were slowly sliding us down the length of the tube. If we weren't wearing the hard suit, we'd have been crushed, but as it was, we were held so tight we could barely move, even with power assist.   I started yelling for him, trying to get him to say something. He managed to tell me he was alright, he was sobbing like a baby. I started doing some calculations. Based on my dead reckoning tracker and initial sonar scans, we were moving about a meter every minute. That meant 72 hours until we came out the other side, assuming we did. We had the air, our re-breeders could keep going for days, what we didn't have was the power to keep the suits warm for that long. But the heat went out, hypothermia would kill us. I don't know, look it up, in any case we'd be dead. We needed to conserve power. I told the kid to turn off his helmet lights, lock his joints, and turn down his heater to minimal. He started crying, he didn't want to do it. I didn't blame him, but I told him we had no choice. We finally agreed to shut down everything but our internal helmet lights, at least. We seemed to calm him down, and honestly, that extra 0.1% power wouldn't make a difference. I think that was the worst part. We spent at least a day like that, locked in our suits, couldn't move our arms and legs, no sound but the things gurgling in your own breathing, and the sound of your re-breeder. The puke on the kid's faceplate started to dry up and flake off about an hour or so in, so I could see his face. He looked tired and scared. I think… check the log, Sarge. I think it was about 13 hours in when the kid started talking again. Kid started babbling, apologised for… Anyway, after that. He calmed down a lot, even managed to crack a couple of jokes. Then I told him to take a nap. He slept a bit. Thank God. About 24 hours in, we reached, I guess they're calling it the stomach now. First warning sound with a gurgling kind of noise, louder with a crunching noise over it. I told the kid to bring his suit up to full power and get ready. A little while after, we fell out into this big chamber, big as in, big enough for the two of us to fit in it comfortably, which was huge compared to a tight squeeze of the tube. Kid's suit started hissing and the outer shell started to turn all pitted and stuff, and I know that my gloves were starting to degrade too, so I yelled at him to move. And we started heading towards this sphincter, I guess. I remember… God, why can't I remember this? The insides of the stomach were lined with… I almost lost it there. I'd stayed, my suit would have melted and I'd be dead, but the kid grabbed me and shoved me head first through the sphincter and we fell into the other place. It was even worse in the stomach. This place was, well, you know what we're full of. I'm not squeamish, Bill.  But this place squicked me out so bad I almost passed out. The kid helped me back up to my feet, though, told me we were almost out. Come on, Lieutenant. We're almost out of here. Let's go. He said. We moved over to the other sphincter, but the thing was, well, it was puckered up tighter than my drill sergeant's asshole back in basic, so no way we were getting out of there. We decided to wait for a bend until the thing shot its load, so to speak.  Anyway, that's when things started to go bad. I managed to wrestle the thing. Through the sphincter and to the stomach, its tentacles right at me as it started to melt.  You know the rest of the story, Bill, except one thing. As for the rest, filled in from the reports and the logs for me, will ya? Oh, and be sure to edit it so the motherfuckers in command don't yell at me for being unprofessional in me AARs again. I'm gonna finish off my drink and take a couple of valium and go to bed. ██████████. Thanks. Warning. This SCP reading contains descriptions of sexual content and other not-safer work material. Viewer discretion is advised. Notice from the Foundation records and Information Security Administration. This document requires level 4 clearance and authorization for need to know under Code Trident Victor Blue. If you do not possess the necessary security clearances, please close this document immediately and report to Security Breach to the Records and Information Security Administration. Thank you. Maria Jones, Director, R-A-I-S-A. SCP-835 Object Class Keter Special Containment Procedures SCP-835 is to be monitored and checked daily for new growth. In the event SCP-835 becomes hostile, suppression tactic AA-6 is to be immediately implemented until aggressive action ceases. Containment area must be maintained in open ocean due to the highly aggressive response of SCP-835 to confinement of any length of time. Waste issued by SCP-835 must be immediately collected and contained. Feeding of SCP-835 is to take place twice daily to consist of any form of local aquatic species. Feeding should be supervised at all times, and no unscheduled feedings of SCP-835 that were to take place for any reason. Should SCP-835 enter a rage state, higher level mammals may be issued as a food supply, up to and including Homo sapiens. SCP-835 is shown high levels of docileity when digesting higher level mammalian life and recommendation for the issuing of the form of food have been approved for use during testing phases. SCP-835 may be moved to a new location twice yearly, provided the current location is no longer capable of supporting SCP-835, and the move has been approved by Site Command. Staff are to remain at least 5 yards away from SCP-835. Anyone working near SCP-835 must have safety lines attached to recall winches. Contact with SCP-835 will result in the immediate recall of all staff and implementation of suppression tactic AA-6. Should contact result in full capture of a staff member, SCP-835 is to be monitored constantly until the release of the subject. Description SCP-835 appears to be a large mass of coral-like polyps weighing 8 tons. The individual polyps are larger than any known coral species, growing to more than 1 meter in diameter in some cases. The central mass is roughly oval-shaped, with a very large, 3 meter diameter polyp at each end. SCP-835 is incapable of locomotion, and appears to anchor itself with the large tentacles projected from the SCP-835 polyps. These are also used in feeding, and are coated with a sticky adhesive substance. The tentacles are also quite strong, and have been shown to be capable of damaging plate steel. The coral of SCP-835 is extremely hard, requiring high-powered diamond drills to collect even small samples. SCP-835 also grows at a very accelerated rate, capable of adding 50 pounds of mass each day. SCP-835 is susceptible to many chemicals, which cause SCP-835 to seal up and halt all growth for 24 hours, prompting the development and use of suppression tactic AA-6. Testing is shown that SCP-835 appears to be made from basic human biological components, with the shell being formed from super-dense calcium, the caps that cover the polyps coated with tooth enamel, and the tentacles appearing to be formed from mutated tongue cells. Most human biological systems are present, however many, neurological, lymphatic, circulatory, etc., show extreme mutation and atrophy. The digestive and reproductive systems appear both highly developed and linked, with both feces and semen being collected and ejected from the same chamber. SCP-835 emits a large mass of semi-liquid material several times a day from the large polyps on each end. This appears to be made of semi-digested solids, fecal material, and semen. This mass also has several forms of virus, bacteria, and parasites, many of which have been found only within SCP-835. The bacterium 835-I-5 forms the major concern for containment due to 835-I-5 and its role in the reproductive cycle of SCP-835. Vertebrate animals infected with SCP-835 will undergo the following symptoms. Increased weight gain, 10-20 lbs. a day on average, constant hunger, urge to consume normally unpleasant, unpalatable items, raw meat, organs, grass, wood, hardening, calcification of the skin, formation of polyps on the skin, rapid reduction in intelligence and mobility, increased aggression, urge to enter seawater, atrophy of many major biological systems. End stage infection appears to convert the subject into an additional instance of SCP-835. Just to determine what, if any, intelligence remains have been inconclusive. However, SCP-835 appears to have a limited amount of awareness. 835-I-5 has shown a very high infectivity rate, with 68% of all infected subjects progression to end stage. There is no form of treatment or antibiotic that has been shown to halt or reverse the effects of 835-I-5. This, coupled with the extremely hard shell of SCP-835, form a major obstacle to neutralization. Any force capable of cracking open SCP-835 would also cause the slurry inside to spread and cause additional infection from 835-I-5. 835 After Action Report Uncensored Notice from the Foundation Records and Information Security Administration. This document requires level 4 clearance and authorization for need to know under Code Triton Victor Blue. If you do not possess the necessary security clearances, please close this document immediately and report to Security Breach of the Records and Information Security Administration. Thank you. Maria Jones, Director, RAISA Addendum 835-01, first draft of After Action Report by Mobile Task Force Zeta-9er, Circumstances of Retrieval. On ████ at ████ hours, Mobile Task Force Zeta-9er, Mole Rats, conducted an investigation of SCP-835. At this time, SCP-835 had a mass of only 4 tons and only one large polyp at the north end of the structure, designated Polyp Alpha. Polyp Bravo not yet being in existence. As per standard procedure, four team members were chosen for the initial investigation. In isolation suits, underwater variant were worn by all four team members. Lieutenant ████ took point as team leader, while Sergeant ████ and █████ served as support. Corporal ████, a rookie team member, accompanied a team as an observer. A standard underwater remote vehicle, or URV, was used for initial investigation. SCP-835 did not at first act in a hostile manner towards the team, allowing team members to approach and make contact without incident. URV-01 was sent to investigate the exterior of the object, while team members C, L, and M proceeded towards what they believed to be the entrance of the site. Corporal ████ was ordered to remain outside and to monitor URV-01 in order to ensure that the device's tether did not become tangled on the exterior protrusions.  Jesus Christ, I can't do this.   I should have kept my eye on him. Footnote ████, at this point, Lieutenant ████ logged off their personal computer for ten minutes. Internal sensors indicated the mini-fridge in the quarters was opened, and a fifth of Jameson Whiskey removed. Christ. Alright, here goes. Guess I'll just let Sarge edit this for me, again. So the thing grabbed the kid. It had me full to rights. The entrance wasn't an entrance, it was just some cave. The real entrance was the big polyp thing on the north end. It grabbed the kid and started dragging him towards the mouth. Topside started to drag him up, but all they got was a snapped cable, and the kid? He got pulled inside and eaten. God, I still remember him screaming. He was screaming at us. He was crying. Oh god, Lieutenant, it's eating me.  I'm shouting at him to calm down. We're gonna get him out of there, and then Topside tells us to abort, and they start the winches. I'm screaming at them to wait. I had his hand. I had him. I had the caribiter on, and we were hooked together. The Topside starts winching his up, and we're not getting anywhere.  Footnote 2. Post-incident analysis indicates that this was the point where the support vehicle's crane suffered a critical structural failure. It was like, Jesus, I need another drink. Fuck.  I saw that on TV once.  There were these muscular contractions, I guess, and they were slowly sliding us down the length of the tube. If we weren't wearing a hard suit, we'd have been crushed, but as it was, we were held so tight we could barely move, even with power assist.   Footnote 3. In early missions, 25% of all Zeta-9er casualties were caused by aspiration of vomit caused by backflow against the suit's faceplate. Second-generation isolation suits were redesigned with catchpockets, piezoelectric face shield wipers, and self-clearing air intakes to prevent further incidents. I started yelling for him, trying to get him to say something. He managed to tell me he was alright. He was sobbing like a baby. I started doing some calculations, based on my dead reckoning tracker initial sonar scans. We were moving about a meter every minute. That meant 72 hours until we came out the other side, assuming we did. We had the air, our rebreaters could keep going for days, what we didn't have was the power to keep the suits warm for that long. If the heat went out, hypothermia would kill us. I don't know, look it up, in any case we'd be dead. We needed to conserve power. I told the kid to turn off his helmet lights, lock his joints and turn down his heater to minimum. He started crying, he didn't want to do it. I didn't blame him, but I told him we had no choice. We finally agreed to shut down everything but our internal helmet lights, at least. It seemed to calm him down and honestly, that extra 0.1% power wouldn't make a difference. I think that was the worst part. We spent at least a day like that, locked in our suits, couldn't move our arms and legs, no sound but the things gurgling and your own breathing and the sound of your rebreather. The puke on the kid's faceplate started to dry up and flake off about an hour or so in, so I could see his face. He looked tired and scared. I think, check the log, Sarge. I think it was about 13 hours in when the kid started talking again. Step note 4 Mission Time, 1613 from start, 1217 since capture. Kid started babbling, apologized for stealing my shorts, said you guys made him sneak into my quarters and take it from me as a dare. Why the hell did you guys make him do that? I mean, I don't mind if you haze the new guys, Bill, but did you always have to do it in a way that reminded him I'm a chick? It was hard enough trying to get them to listen to me as it was. Anyway, Bill, it's all there in the log. You know what I told him. They were lies, of course. Jokes. He laughed, too. Joked back. I hope he was joking. I don't know what I would have done if we survived. Maybe I would have gone ahead and did it. I don't know.  Anyway, after that he calmed down a lot. Even managed to crack a couple of jokes, and then I told him to take a nap. He slept a bit, thank God. About 24 hours in, we reached. I guess they're calling it the stomach now. First warning sign was a gurgling kind of noise, louder with a crunching noise over it. I told the kid to bring his suit up to full power and get ready. A little while after, we fell out into the big chamber, big as in big enough for the two of us to fit in uncomfortably, which was huge compared to the tight squeeze of the tube. Kid's suit started hissing, and the outer shell started to turn all pitted and stuff, and I know as my gloves were starting to degrade, too, so I yelled at him to move, and we started heading towards this sphincter, I guess. I remember. God, why can't I remember this? The insides of the stomach were lined with teeth and faces, human faces, and they were all wailing at us and screaming.  I almost lost it there. I started opening up with my gun, started shooting them in the heads, and if I'd stayed, my suit would have melted and I'd be dead, but the kid grabbed me and shoved me head first through the sphincter and we fell into the other place. It was even worse in the stomach. That one was lined with faces and filled with acid. This place was, well, you know it was full of. I'm not squeamish, Bill. You can't be if you're a mole rat, but this place squeaked me out so bad I almost passed out. The kid helped me back up to my feet, though, told me we were almost out. Come on, Lieutenant, we're almost out of here. Let's go, he said. We moved over to the other sphincter, but the thing was, well, it was puckered up tighter than my drill sergeant's asshole back in basic, so no way we're getting out of there. We decided to wait for a bit until the thing shot its load, so to speak.  Anyway, that's when things started to go bad. The kid started complaining about this awful smell. I tried to stay calm, told him it was probably his suit's waste recyclers, told him to let me take a look at it. Yeah, there was a hole in the back of his leg, probably from the acid. I put a patch on it, and told him to not worry about it. And that's when I noticed that there were these red things growing all over his face. He started screaming when the first of them burst in splattered blood all over the inside of his faceplate. He begged me to die. I put my gun to his faceplate and pulled the trigger. Click.  The tentacles burst out of his face a moment after. It grabbed me, and it started licking me, Bill. The thing was running its tongues all over my face and body, over the suit. It grabbed me and pushed me down and tried to hunt in my suit like a dog, but it couldn't get through. I managed to wrestle a thing that had once been the kid back through the sphincter into the stomach. Its tentacles ride at me as it started to melt. He smiled, told me he loved me before he died. I screamed.  You know the rest of the story, Bill, except one thing. When I got back to the ship, there was a breach in my suit. I haven't told anyone yet, Bill. No one noticed. Not even me. A little crack on the wrist of my left club. And I guess someone missed a spot on decontamination, and well, I figured I was okay, right? It just hit the skin, nothing internal, and I didn't start getting symptoms right away. But I've read the reports about the latency times, and I'm gonna start coming down. Now it's about the tail end of the incubation period, so I locked myself in and waited. I just looked in the mirror and noticed that my face is starting to grow some red blotches, so yeah, I guess I'm fucked. As for the rest, filled in from the reports and the logs for me, will ya, I will be sure to edit it so the motherfuckers in command don't yell at me for being unprofessional and me AARs again.  Tell the cleaner teams not to enter my quarters. Abandon the entire ship and scuttle it on top of the original site. It should be easier to contain two of us than just one. Besides, I think the kid would like it that way. Now we can be together, just like he wants. Thanks.


Hi, I'm Dr. Sean N. Teary, I'm an assistant professor in the Department of Family and Community Medicine and I am one of the providers that sees patients here on campus at University Family Medicine. As a family doc, we see a little bit of everything. We do well-childs, we do physicals, we take care of things like diabetes and hypertension, take care of acute concerns like I bump my knee and it's hurting. So family docs, we say we do it all, we see a little bit of everything. I am naturally a family doc. I like to talk, I like conversations, I love long relationships with patients and there's no age group or demographic that I don't like working with. I really love that in a day I can see a four-day old and see a 92-year-old all in one. So I really love what family medicine is, kind of the holistic philosophy and approach to patient care. I think the best part of what I do is getting to know patients.  It's neat to grow alongside with your patients, it's a privilege to be able to take care of people and to see them through the good times and the bad.


provide both confidentiality, integrity and authenticity. So this means that nobody can see what you're looking at, nobody can change what you're looking at, and you know that the person who is sending you this is a specific person. They use signed digital certificates. Each one of these certificates must be signed by another certificate.  So why do we have to launch another one? Well, the internet is a bad place. It's extremely easy to modify or to observe HTTP communication. There have been a number of attacks that have demonstrated this over the years, including cookie session reuse and others. Based on telemetry from the Firefox browser, we know that only 40% of initial HTTP requests go over HTTPS. This is probably because both getting and installing a certificate, as well as setting up all the correct TLS parameters, is extremely confusing. And in part, this is because every CA decides how it will issue a certificate on its own. So our solution is to create another certificate authority.  So because we are EFF and Mozilla, we've decided that it should be completely free. Cryptography shouldn't be something that you have to pay for on the internet. And unfortunately, right now, there are only two certificate authorities that are willing to issue free certificates except for let's encrypt. And unfortunately, both of them make it a quite complicated process and will exclude you from getting a certificate if you fall into certain groups. So we decided to make it free, and we also decided to make it open source. We did this because it's extremely hard to tell what certificate authorities are actually doing and how they decide whether or not to issue a certificate. So we decided it would be best to come up with a standardized protocol, which we've called ACME, so that we can get everybody's input on what is the most secure way that we can do this. So let's encrypt has already launched, and you can right now go and get a publicly trusted free certificate from us. Unfortunately, this isn't a cheap thing to do.  So the CA and TLS ecosystem is a pretty strange place. Before we got there, this is a map of every single trusted certificate authority that currently exists. Every single one of these nodes can issue a certificate that your browser will completely trust. And this is ridiculous, the fact that there are over 1,600 certificate authorities is very silly. You can actually see let's encrypt is one of the small magenta nodes in the bottom left-hand corner. Unfortunately, we haven't surpassed some of the other certificate authorities yet, but that's soon to happen. So there's a group called the CA Browser Forum, and these are the people who decide how the CA and TLS ecosystem works. Because CA's have a slightly vested interest in making money over protecting users, there's often a rift between them and the browsers and how rules should be made that affect publicly trusted certificates and certificate authorities. Because of this, they decided to come together and self-govern themselves in order to bring order about. The browsers generally yield slightly more power than the certificate authorities. They require a larger majority in order to pass a rule. And this is because, like I said previously, certificate authorities are generally guided by making money, whereas the browsers are generally guided by trying to keep users safe. Unfortunately, let's encrypt is not yet a member of this group, because they have very stringent requirements for membership, which include a number of audits we haven't yet completed, although we are very close to doing so. Like I said, the CAB Forum creates rules called the baseline requirements, which every certificate authority must comply with if they wish to be trusted by browsers. This includes basically documenting every process that is involved with issuance of a certificate and takes a very long time. So the CAB also chooses the different security levels of a certificate. These are called validation levels. There are currently three. And it should be noted that cryptographically, there is no difference between each of these levels of validation. What they mean is how thoroughly a CA has validated the person who is requesting a certificate. Domain validation is what we're interested in. And it basically just means that, as a CA, we can verify that you control a certain DNS name. Now, there are a few extra steps for organizational validation. This means that a CA would have to validate that you are an owner of a certain business in a certain country. And extended validation goes even further and checks other governmental records. Both OV and EV certificates don't provide any more security. All they provide is UI hints in the browser. So with an EV certificate, you will see a green box in your URL bar that says the name of a company. But the cryptographically, these certificates are exactly the same. So what does let's encrypt fit into this? Like I said, we're doing everything completely for free. This includes issuance, renewal, and revocation. And any other action you would do with us is entirely free. We're not charging anyone anything. We're also only going to be issuing domain validated certificates.  Our system is entirely automated. The only people that we hire are operations, maintenance people. We're also only issuing certificates that are valid for a maximum of 90 days. This is a we originally decided on doing this because in the previous world where certificates were valid for anywhere from one to up to three years, it made it really hard to figure out how to automate renewal of a certificate. Every once a year, you would go to your certificate authority and ask for a new certificate, and then spend the next few hours trying to figure out what you had to tell them and how you'd install it in your server. By limiting the validity period to 90 days, we're ensuring that people are forced to renew often. This also comes with a good side effect that if a certificate becomes compromised, it is only compromised for a maximum of 90 days, which makes it slightly safer. So we're also issuing multiple domain certificates instead of wildcard certificates. These use subject alternative names, which are multiple DNS names inside of a certificate, meaning that a single certificate can be used to validate up to 100 domains. In order to make our certificates actually publicly trusted, we've applied to the Mozilla, Apple, Google, and Microsoft root programs, but we've also had one of our intermediate certificates cross-signed by IDENTRUST, which is another certificate authority, and this means that every certificate we issue is already trusted, so we don't have to worry about old devices not trusting our certificates. So we started our closed beta in about early September, and this went from all the way up to December 3rd, and during that period, we only issued about 20,000 certificates. You can see the first period in September was just staff issuing certificates to themselves, and I think we only issued around 100 or 200 certificates. And then we opened a closed beta, and we issued around 20,000 more. And then on December 3rd, we opened up to everyone. You didn't have to apply to join, and we would issue a certificate as long as you could prove that you controlled the domain. In the first day, we doubled the number of certificates we issued, and in the week, I think we could droop all that. I mean, in the first 12 hours, we were issuing a certificate almost every two seconds. And since then, we've issued over 200,000 certificates across 440,000 domain names. We are still in beta, though, that should be noted. We don't expect to do a Google-style beta. It will probably take a while. So using certificate transparency logs, which are a collection that Google has created of almost all currently valid certificates, we can see that Let's Encrypt is already the fifth largest certificate authority, and we have already lodged them both WOSign and Stardust to sell the two currently free public certificate authorities. So our goal is to raise... It isn't to be the largest certificate authority, but it is to raise the total percentage of connections on the Internet that go over HTTPS. So this is a very hard thing to measure. Unless you're sitting on a backbone, it's almost impossible to tell what percentage is going over HTTP and what percentage is going over HTTPS. Luckily, Firefox can provide us with certain TLS telemetry about what certificate authorities issue certificates that they are seeing, and we can also use certificate transparency to try and figure out how people are actually using our certificates.  There are currently over 120,000 individual registrations. So we count... A single registration can issue multiple certificates, and we see that currently only there are about two certificates per registration with two DNS names per certificate. Now, this is most likely because people are just testing the service, so they will go out and try and find a certificate for their blog or personal website, and not very many people are using very large certificates with multiple subject alternate names yet. We see that around 33% of the names that we issued for have multiple certificates with that name in them. Now, this is actually a very common thing we were expecting to see because we issue a very large number of certificates to content distribution networks, and these networks will have tons of endpoints that will work for a whole bunch of different websites. So they will maybe have 15 certificates that will have a set of 50 domain names spread out across them. We also see that 20% of certificates have the exact same duplicate namesets. This is probably more to do with people trying to get used to our official client and us having to fix a few bugs in it that meant that people would reissue the same certificate over and over without noticing that they already had a valid one. But we're seeing that slowly decrease. We've also seen that 80% of the domain names that we've issued for have never had a certificate before according to the certificate transparency logs. So we're actually providing people who usually wouldn't have got a TLS certificate with certificates. And we've had about 1% of our total issuance have been revoked so far, which is a good sign that our revocation system is actually working. So in order to see how people are actually deploying our certificates, we've written a very small TLS scanner that will go through the DNS names and certificates we've issued and try to see if they actually use them. And we see that about 75% of the people that we've issued a certificate for have actually deployed it on the domain name that we issued it for. And only 8% of those names have a broken TLS configuration. This means if you tried to connect to them, your browser would reject the certificate. And this is because they're using a self-signed certificate or because they aren't presenting the correct chain of certificates among other things. And 3% of the names we've issued for don't serve HTTPS at all. Now, this actually is probably quite smaller. Because we only scan for HTTPS, people could be using these certificates for mail servers or IRC servers or XMPP servers, we wouldn't know. And we can see that 45% of the certificates are used by every single DNS name that they contain, which is actually quite good number. So, looking at the Firefox telemetry, we see that only 0.1% currently of successful TLS handshakes use a let's encrypt certificate. Now, this sounds very low, but it actually makes a lot of sense. We don't plan... Our goal is not to make the largest websites on the internet use our certificates. If that happened, the percentage of successful TLS handshakes that we were involved in would be much higher. But our goal is to make... issue certificates to the long tail of people. People who may not have hundreds of thousands of visitors to their website, but should still be able to use cryptographic protocols. So, we have an official client, which is called let's encrypt. Which currently is used by about 65% of our users. This is a very complicated client, and it will do a lot of things for you. It will manage renewal. It will manage installing the certificate into either Apache or Engine server, among other things. But there have also been, since we entered public beta, around 30 unique third-party clients that have popped up. For pretty much any scenario, you might want to use a certificate for. So, including a web server called Caddy that has a built-in ACME client, which means that as soon as you can turn on your web server, if you don't have an Excel certificate, it will automatically go out and fetch one for you. Another one is a web-based client, so that you can go in your browser and generate a certificate without installing anything on your system at all. So, our main goal is actually to get hosting providers and content distribution networks to use our certificates. While most people here might want to just go out and install a certificate on the server they run themselves, the majority of people who are running smaller websites are using a hosting provider who will run all of this for them. And generally, these people will charge for certificates. And our goal is to try and get them to A, make it free, and B make it painless for the users. So, so far, we have ACME, QCDN, Dreamhost, Scion, Prestige2. These are both hosting providers and content distribution networks who have already integrated with Let's Encrypt and will allow you to get a certificate completely for free. And we assume that in the long term this will make up the majority of our usage. Most likely, people issuing hundreds of thousands of certificates won't be individuals, they will be hosting providers. So, we still have a lot of work to do on our certificate authority. Currently, you can only do validation based on either HTTP or HTTPS. This has made it quite complicated for some people who have very complex setups, either using load balances or other systems to validate their websites. One of our solutions to this is the DNS challenge, which will allow anyone to just add a DNS record and automatically validate the domain name they want. We also want to implement a proof-of-possession challenge. This means that if you ask for a certificate for a domain name that we know is already using a SSL certificate, we will ask you to prove that you control the private key of that certificate. And this is an extra way to verify that a single person won't control or can't mis-issue a certificate for a domain they can't control. We also want to add multi-path validation. Currently, we validate from a single point. This means that we are susceptible to network local attacks. But this will change very soon. All right, thank you. The first two questions are for the Internet. Okay, the first question from the Internet is that given the critics on the official client, wouldn't it have been better to split the server and service and the client? I think the client is a very hard thing to implement. And because we are the people who created the protocol, I think it makes sense for us to also work on trying to create a client for it. If we had just waited for somebody else to do it, I don't think we would have been able to get as far as we have so far. The second question is that, well, a lot of people are apparently interested in your T-shirt and want to know first what's on it, and second, where can they get one? Unfortunately, these aren't for sale yet, but they should be very soon. And you may notice that this is supposed to be the contents of a certificate. You can try and decode it, but I don't think you'll get very far. Okay. Okay, next question from Mark for number one. I have tried your service and it works very well. I was wondering what keeps you from going into public.  What is beta in your service currently? Well, our service hasn't been completely tested. We wouldn't suggest that a website like Facebook that gets millions of requests a day would deploy one of our certificates just yet. Yeah. It is currently we have a hard limit on how many certificates we are able to issue due to our hardware security modules. And because of that, we're kind of trying to take it slowly for now. Yeah. As far as we know. Okay, next question from Mark for number two. Hi. What are you using for revocation? Are you using the standard defined relocation list or do you have your own solution? We're using OCSP. Our plan is to promote OCSP stapling. Yeah. I think the CRL model is too broken. And we're kind of trying to push both Apache and Engines to get the act together with OCSP stapling so that it will actually be a useful revocation method. Okay, next question is for the internet and after that microphone number one again. Okay, the question is why is there a limit on certificate issues per domain because that is especially annoying for like dynamic DNS users? Yes, we agree. Currently, we use the public suffix list to decide how many certificates a domain should get. So if you have, say, Roland.com, you'll only be able to get five certificates for that domain. Currently, this is because we have a hard limit on how many certificates we're able to issue so we don't want a single user to be able to go out and take up a significant percentage of that. We're trying to figure out a better rate limiting solution. You should notice in the future that you will be able to issue a lot more certificates, but we're just not there yet. Hi, first thanks for the talk and for the great aim, I think we all support. I have a question regarding the audit that has to be done by Let's Encrypt because for new kids on the block usually there's this kind of certain audit where the Mozilla Foundation also was part of creating this and as I know there's a three month grace period of like handing in all the papers and whatever afterwards and if you started in September, that means now we are in December, so what's the status of this whole audit thing? And as I know maybe you can comment on this as well, the cross validation does not count for this, so I'd be very interested. So we are not yet in the root programs of any of the major browsers. We've, I think, just finished our audits. Unfortunately a cross signature doesn't require any audits. If you can pay a certificate authority enough money, they will cross sign one of your certificates and allow you to issue. It's a very silly system. So we, yeah, we, it means that we can currently issue completely valid trusted certificates, but we are not a member of the organization that decides, you know, how that works. It's strange. Next question for microphone number five. Hi, first of all, I would like to thank everyone working on this project. You guys are awesome. So I've got a question regarding engine eggs. Do you know when you might have it completely supported? I'm not 100% sure. We are working on, this is kind of our main focus in the client right now is increasing the, how well the Apache and engines plugins work. Engine has kind of got the shot under the stick currently because the majority of people we are working with are using Apache. The next few months though, that should improve significantly. Okay, thank you. Next question is for microphone number four and then we go back to the internet. So I have two. So one is let's say that tomorrow, shot two suddenly there's a big new attack. Everyone should move to shot three. But unfortunately, as we all know, many clients will lag. How would you plan to solve this situation? Will you push everyone to migrate instantly to shot three? Will you cater to those of your users that would like to remain as compatible as possible? And kind of related to that, can you give us, I'm sure you've been asked this question a lot, but why 90 days? Why not a lot less and maybe even get rid of the entire revocation system why not more? Can you give us a little glimpse of how you want to handle these decisions? So the first question, that decision isn't 100% up to us. It would be more up to the CAB forum and how they choose to sunset the algorithm. Most likely we would continue issuing until the deadline so that people can switch over as seamlessly as possible. But again, that's kind of a policy question for the governing body. And then the 90 days, we have been considering allowing less than 90 days. So if you would like to issue a one-day certificate or a two-day certificate, that should be possible. We decided that there should be a hard limit, though, on how long a certificate we're willing to issue. And 90 days is in part due to how long we would think a certificate that was compromised is safe to be around. And that should be as small as possible. Unfortunately, renewal is still a hard problem, so we can't just say a week or two weeks. And 90 days was kind of what we came down to as the safest. Okay, last questions for the internet. Okay, then the last question will be what is the stack that you use to generate the certificates? Do you have any special optimization like code or hardware to keep up with the increased demand? So we sign our certificates using hardware security modules and a library produced by Cloudflare, which they use for their universal SSL program, which is called CFSSL. But there's no special process involved. It's just a typical X509 generation. Thank you very much.


Hi, this is George Cao, and today I want to offer you a free tool to help you track your clients, particularly how many calls your client, a certain client has left with you, therefore how many calls you have left with all of your current clients, and also how much room do you have for accepting new clients. This tool will help you track all of that. So first thing is that this tool is in Google Drive, and Google Drive is free. So if you don't have an account, you have the Google Drive, get a free account. It's awesome. I use it every day. It's drive.google.com. Once you sign in to Google Drive, then come back to this video and find the link to this template. The link to this template will be given in the notes area of this video. Once you come in here to this template, what you do is you click File, and you click Make a Copy, and this will then copy all the formulas so that this template can work for you as well to make the right calculations. So let me kind of walk you through the template what we're looking at here. First of all, this first column is a client name. I've used fake names and fake email addresses here. And then this one is the start date. So this is basically helpful for you to know when you started working with a client, how long they've been with you. This is just for your information. By the way, if you want to hide any of the columns, you can click on the column itself by clicking on the letter at the very top of the column, and then you can click on the drop-down menu, and then you can click Hide Column. So I'm going to do that right now just to show you what happens. Hide Column. And you can hide multiple columns if you want. If you want to expand a hidden column, you just notice these arrows here. If you click on the middle of the arrows, it'll expand the column again.  So for example, as you can see here, Morgan just had a call with me, and these are fake names, right? Morgan just had a call with me on July 13th.  So she paid me for a package. We've already completed all the calls, so I put complete here. Chuck just had a call on July 10th. So the great thing about this is that this top cell here will automatically track what is the most recent call you've had with any of your clients. And so what I recommend that you do is at the end of each day where you've had a client call, come into your template and put in which client was it and what was today's date. So if you do that, for example, it will automatically update this. It will automatically update what is the most recent. So I always look at the spreadsheet and I go, okay, did I track my client calls today already, or yesterday, and I'll be able to see what date it was. That's the most recent date listed there, okay? So let's see what else. Okay. Oh, the other thing about the spreadsheet that you can track, I'm just going to do some fake numbers here. You can also sort by the most recent calls. So let's say you want to know which client it's been the longest since you've talked with them. Then you click on the top of the column here. You click on the arrow here and then you click sort sheet by A to Z. Click on that and it automatically sort. Oh, okay, Chuck, it's the, I haven't had a talk with him in a while, let's say. And so I need to then schedule the next appointment. What I've done here in this next column is when is the next appointment scheduled, okay? I've automatically programmed it such that it'll be yellow if you haven't filled in anything. So, okay, I need to follow up with Chuck about scheduling the next appointment because there's nothing scheduled. Let's say I already followed up and the next appointment is scheduled for, you know, September 20th. Then I'll just put that there and you can see the color automatically changes. And I'll know that, all right, great, I've already completed with that. Fully scheduled means that Morgan and I already worked out our calendars and he's already scheduled all of his appointments going forward. So it makes it nice and easy there. And again, she's already completed all her calls, so there's no need to schedule an appointment. And sometimes what I'll do is if I've reminded a client to schedule an appointment and they haven't responded yet, I'll just put a 1X mean I've sent them one email. If I sent them two emails and I put a 2X. If it gets to something like 3X or 4X, I may need to call the client or contact her another way like through Facebook or something to say, hey, we need to schedule our next appointment, et cetera, okay? Number of client hours remaining, this is really cool because this is basically how many paid client hours the client has left with you if they've already, if they're in, this is regarding if you've sold them a package of sessions. So that's the way I work in my program. People either buy a package of, usually they buy a package of 10 sessions with me, for example, or 20 sessions with me. So then, for example, Chuck here has just three client hours left. So what that means is every day when I come in and update this, update the most recent call, whether I have a next call scheduled, I also say, oh, I already had a call with Chuck today, let's say. That means Chuck has two client hours left. Now, why is this 10.375? I calculate if a client does a half hour call with me, that's considered 0.625 of a client hour. So in other words, a half hour isn't just 0.5. It's 0.625 because there's additional time for decompression. It's more logistics to schedule. It's basically not as easy for clients to have half hours with me than it is to have a one hour. It's just easier on my business. It's easier on their schedule as well. So I try to incentivize people towards doing an hour long sessions instead of half hour sessions, which is why this calculation is here. So for example, let's say Morgan had 11 hours with me left, but then he opted to do a half hour session with me. So 11 minus 0.625 means that he has now 10.375 hours left. Does that make sense? So you just keep going on that calculation. And this top number will automatically calculate for you the total number of client hours remaining that you owe your clients total for this period, or basically for whenever you're tracking this for. This column is for your own tracking of how much clients have paid. So you can say, oh, wow, my clients thus far have paid. If you highlight, by the way, I should show you this. If you highlight numbers, like click and drag and highlight numbers, you'll see the sum is automatically calculated over here. So like that. And even click on the sum, you can even see what the average is. The average client's paid $2,000, let's say. So it's pretty cool. All right, let's go to, let's see, number of calls total. This is for your own tracking just for your own information. They've bought 20 call package or 10 call package. And this over here, let's move over here, is to help you track whether you have scheduled your first call with them or whether you still have to schedule your first call with them, whether you've added them to your current client email list, your current client's Facebook group, your LinkedIn and Google Plus if you use that stuff, or if you have their birthday on your calendar, if you want to track that. And finally, let's go to the next tab, Availability. And this will help you track how many client spots you can still take remaining. You start using this tool by using the start of the week. Okay, so this week is July 13, 2015. So that's the date there. Oh, by the way, I'm sorry. I should mention that. Give me a second here. Okay. You only touch, you only mess with the yellow cells here. And don't leave the white ones untouched because they will automatically calculate. So this week is week number 29 in the course of the year. This is week 29. So the weeks remaining, this automatically calculates 52 minus 29, it automatically does that. How many vacation weeks are you taking left? I'm just gonna put five for how many weeks of vacation I have left. Enrollment weeks is where you focus on marketing and don't take any client calls. If you do that, then put a number here, I put two here. How many realistic paid client hours do you have per week? Just based on your history and what you're able to schedule every week and your own energy level, I put 12 here that I'm able to do per week. Therefore, this automatically calculates how many realistic paid hours for the rest of the year that you have. It calculates based on these other numbers. If you're teaching a course and that eats into your paid hours per week, you might wanna put that here. For example, I'm teaching a course later this year. There will be four weeks and it'll take four paid hours per week from me just in terms of what I'm able to in my own schedule have as working sort of focus client or teaching hours, right? So this is basically what automatically calculate how many hours left you have to take client calls for the rest of the year. This is how many session hours per client package. So let's say your average sessions package is 10. That means you can now take 16 clients more, okay? So I hope that this tool is helpful. I'm always open to your questions and comments and until the next video, I wish you well. Thank you.


I'm a year ago, we were kind of huddled up in a small conference room across the street. It's been awesome to be in here in our new draft room, having meetings, talking through things, and prospects as we prepare for next week. I'd like to thank a lot of people that have really helped in the team building process. This spring, Coach Ray will, obviously, discussions we've had back and forth about prospects and fits for our football team. Todd Torcelli, our trainers, all the assistant coaches, Chick and Mitch, the personnel department, Ryan Calden, Monty Austin Ford, John Salgi, as we prepare for the draft, and then going back to free agency, Brian Gardner, and the pro department, certainly Ben Moreno with the contract negotiation. So with that, excited about next week and another step and another part of the process as we try to put the 2022 Tennessee Titans team together for questions. I mean, how much movement is there still to do? What's the last week likely enough to the draft? Just going back through, we watched through a couple guys last night as a group. You start the comparisons. This player versus that player, it may be vertically in a position stack. It may be horizontally in a one position versus another position. I mean, you're trying to predict guys that are going to go ahead of where you're picking. Sometimes that's a bit of a crapshoot. But just still some dialogue as we try to fine tune here, heading into next week. John, I just talked to AJ about the supermortem. Where do you stay? Yeah, we've had some discussions with his reps. When he was here a couple of weeks ago, I talked to him. And you're working through that, not going to get into any details with contract negotiations. Never have really done that. But we've made it public about how we feel about AJ and how we wanted to be a part of this football team. What are your thoughts on how the receiver market has exploded so much when you look at these recent contracts? Yeah, I don't know what the trends are with that, T. But it's interesting to look at and where that has shifted. Every year, it seems like certain positions, there's ebbs and flows with where those markets goes. A couple of years ago, the safety market was down. That's when I think we got Kenny Vaccaro. He was out there for a while. We were fortunate enough that he was there in August. So just kind of year to year how those market trends are. I think we're trying to get the best football player that's available for our football team. You're going to need every position at some point. I mean, we saw that last year with 91 different guys that lined up for us. So you're going to need good football players at a lot of different positions over the course of a season. So just try to put ourself in the best position to take the best player that we think helps our football team. John, you had a situation, I guess, AJ is talking with Devo Samuel on an Instagram video, talking about the terms of the negotiations. You got him repressing it, right? Does any of this make you feel more urgency when it comes to the AJ situation? Yeah, I mean, I've talked about where we're at. I've talked to AJ's reps. AJ knows how we feel about him, how much he means to this football team. And I haven't seen any Instagram videos or Snapchats or Vimeos or any of that kind of stuff. When you've got the same agent representing three of the former receivers who are in this situation, does that complicate things in terms of who is the first and then all wanting most money? Yeah, I don't really have any control over who reps who. That's up to the individual player and who they select and who they feel most comfortable with handling their situation. Does it complicate things? I don't know. Our focus right now is with our football team. Is there any chance that AJ could be treated between now and then? I think I've spoke on that several times now. So do not foresee that happening. Have you cut down to any more talent if you like in terms of that line and prospects you seem to see a lot of the work you've been out? Tracking the plane, John. Specifically with the O-line down here? Yeah, there was O-line minute, certainly at stops that I saw. And there were players at other positions at some of those stops that I went to. That's one of the things that Mike and I were excited about was being able to get back out this spring, be around these prospects on their pro days, watch them work on the field, spend some time with them after their pro days, visiting with them, getting to know them. Maybe you get a little bit more time at the school than you do certainly in that Combine interview where it's 15 or 18 minutes, whatever that is. So you get a little bit more normalcy. The players in his environment, he's in a meeting room that he's used to on his campus, get a better feel for the real guy as opposed to maybe what the rat race of the Combine is as those guys are being shuffled from one room to the next room to the next room and it's a bit of a whirlwind for them. Pick up on there. Can you talk through Zion, Johnson, and Kenyans beneath this prospect? Yeah, both of those guys, I mean, the big, strong players. Both guys have played a couple different positions. Really, Zion has played three positions. Kenyans played both guard and tackle. They're strong, they're good movers. Both of those guys were good when we met with those guys and they're good prospects. Mike, can you chime in there especially on Zion with the water from that room? No, I don't think I have anything to add on Zion. I mean, obviously, he played next to Tyler and he's an excellent player, an excellent person. Really, really good person. I'm sorry? Did he live with yourself? Yeah, he lived with Tyler, yeah. They probably didn't say much. Tyler doesn't say a whole lot and Zion doesn't say a whole lot. In terms of positions of need for your roster, just in terms of shooting up, receiver, tie-in, up into the line, it's a lot of positions, Terry, we need a lot. But how does this draft stack up depth-wise in some of those spots? Yeah, I think as we've gone through the process, there's been some position groups that have shown a little more volume maybe than other positions, but we feel like that the positions that can help our football team, again, as I stated earlier, you're never gonna know what position you're gonna need throughout the course of an NFL season. And there's players that really at every position that we feel good about. Now, whether they're there when you're able to pick, that's another thing. If I had that crystal ball, the draft would be a lot easier. But no, I think that where our football team is currently and what's available is a good thing. And not having a second round. Potentially, there's creative ways that you can strategize and try to gain draft capital. Whether it's sliding back from where we're at, whether it's involving future picks in next year or the following year, there's ways to kind of put things together to try to put yourself in position to get the player you want. It's a much interesting effect. Yeah, I think it's probably where we're at, John, in the draft where we're picking, that's a little bit more as you get closer to your pick. It was a different situation back when we had the first pick. I mean, you're trying to strategize to get what you can get from that. Obviously, both of you guys are hardcore football guys. Mike, is there anything that you look forward to players as a head coach that maybe, or something that gets you excited or something that's a red flag that's different compared to maybe a personnel guy with the coaching background? Matt, I think we want to have guys that we trust. I think that's important. We want to evaluate the trust and the ability and hopefully find those where they match up with high level of trust and high level of ability. You try to, I think, where we're at now is trying to get to, is this somebody that you want to see every day and coach every day and have in your meetings? And that's what we try to ask the position coaches, obviously, try to hide a vision for them and a role in what they're going to do and what they eventually may do for us. I think, for me, there is a lot of maybe just traits, character traits, that I'm looking for. And then we'll go and watch the tape. And I trust everybody's opinion, but I really want to bring great people onto this team. John talked about how nice it was to get back out on the road this spring. How much did it help you to familiarize with some of these guys and maybe learn a little bit more of what you were just talking about? It's very unfair, the picture that sometimes gets painted from the combine. And I'm probably at fault more than anybody. The 18 minutes, and these kids are just coming in from the airport and they're dropping their bags off and they're getting rushed over to some suite in the dome. And we've had numerous instances where maybe didn't feel great after that short exposure and then followed up with them either here or on their campus and then really come out of it with a different opinion. So that is a critical element. And some of these players, they try to think that we want something other than who they really are. Because I think that's the best thing. It's just for us to try to identify who they really are, what they're going to be in September and October and November, and not maybe what they think we want them to be in April. When you look at these receivers, big guys, they're small, how do you weigh that?  A lot of them are primarily big guys. How do you weigh, how do you buy them? I think you look at opportunities and production, how they catch the ball, how they protect the ball, their willingness to block. Some schools don't ask them to go in there and block. Some of them are running routes, are running RPOs or relief routes and trying to pull out defenders that way. What routes have they asked them to run? Some guys, it's like, well, he doesn't run it. They probably only have 12 or 14 plays and they're not running that much of a route tree. How much can he understand and explain about coverage? I think those are all ways that we identify how they play without the ball, how they play with the ball. Are they tough to tackle? Is this a, so players got really good play strength? Can they play inside? Can they return punt? So there's a lot of things that we look at. What do you guys see in this, Ty Vanier? Yeah, I mean, I think there's a, it's a pretty good mix. You've got some guys that are dual players. They can play kind of on the line of scrimmage as well as have the athleticism to detach and play away from the line of scrimmage. There's some guys that can make those move blocks, some of the things that we asked to do, maybe from the backfield. And then you've got guys who really, they're more detached players. They play predominantly in the slot or on a wing position in their pass catchers. But even those guys, the guys that we've watched, there's at least a competitiveness as blockers to at least try to get their nose dirty a little bit in the run game. You guys talked in the past about the lack of blocking to try that in college. Can you still define guys there that can do what you need? Yeah, I think we've identified a few guys that we would, you know, maybe consider in that category. And then also, you know, some of those guys, their skill set can't be overlooked because they are match-up issues against guys that we try to face and we try to decide who's gonna cover them on third down. So there's some guys that we've identified, I think at different levels of the draft. And we're still going through that process now. John, would you say the strengths of this draft class and maybe whether it's the most depth? Yeah, I mean, I think you can look at every position, Jim, I think it's, you know, the offensive line's pretty deep. There's some pretty, there's some good edge rushers. There's some good receivers. There's a group of backs that are pretty good.  I think there's positions, employers at every position that have really good depth, you know, across the board.  But, you know, I think we've been able to identify guys that are about every position. You can open as strong as this. Yeah, I think it's according to what quarterback class you're comparing it to. And I think if you compare it to certain ones, it certainly is not as strong. But there's other classes where I'd say it's at least comparable and maybe even a 10's better. You know, it's been good to spend a little bit of time with some of those guys, get to know those guys. You know, that's a hard position. Quarterback position is a hard position to play in a national football league. There's a lot that goes into that position. You know, I think all the guys that are in this draft that we've talked to, you know, certainly seen capable and willing to learn and put the time in to make that transition. You know, that conversation with the quarterbacks, I would imagine that's different. How is that conversation different for you guys that you're talking to them? Yeah, I mean, I think you're trying to identify leadership. You know, how's that guy gonna lead a football team? You know, what's his level of confidence? He's certainly probably gonna be more well-versed in his specific offense, terminology-wise. And you can't expect them to just be able to spit back like whatever we call a certain player, certain defense, but can they associate, you know, the concept that we're trying to talk about? But it's really the leadership and the willingness to learn the coachability and how are they gonna step into a situation and with guys much older than them that they might line up with and be able to lead those guys and push those guys to score points. For both of you guys, in terms of Dylan Rayden. Terry, one. Does he project more as a left guard or as a right tackle? Say that, ask that question again, Terry. Yeah, in terms of Dylan Rayden, do you guys think he's more of a left guard or a right tackle, and how does that affect where you might feel the other spot in the ground? I think with the offensive line, we're trying to get the best five guys up there that can block their guy. You know, I think Dylan has shown he can play tackle. I think he's worked at guard. He's played guard. I think there's some versatility with him as a football player, but at the end of the day with the offensive line is trying to get the right five guys up there that can block their guy on a consistent basis. Yeah, I mean, but I think that the versatility is something that we preach, especially with the offensive line. Guys that can play a couple of different spots. If he's at this position and your next guy, maybe he's best as Dylan's backup, let's just say, for example, and he's better than the next guy that's gonna go in at the other position that you may need if somebody goes down, again, you're trying to get your best five guys out there. When you have a draft and there's a specific position or two you're looking at, how do you balance making sure the value aligns with the pick, but at the same time, not letting too much time pass to where you lose a quality enough player at that position that you play? Yeah, I think when we talk about all the time it's need versus best player and when those things line up, it's a really cool thing. But at the end of the day, you're trying to identify who helps the team the most. There's short term and there's long term. Sometimes it takes players a little longer to maybe blossom into being productive players for us. I think we've got some guys on our team that are examples of that. And it's being able to balance the immediacy. Again, we want them all to come in and contribute right away. That would be in a perfect world. But you're looking at trying to balance what is the long term, what's the long game with that player as well? John, how would you think about not having a second round in a competition, if you took a quarterback and saved your first round? Yeah, I mean, I think those are hypotheticals and those are scenarios that we talk about. It's like, if this, then what's the overall plan and how is that going to impact the football team? We work through those scenarios. At the end of the day, we try to do what's best for the football team. And to Luke's question, you're looking certainly at the short term in the window, but you're also looking at the long game as well when you're adding players to your team. Michael, you've got it, Charlie. Well, I think when you look at positionally, in this case, offensive line, whether it's a 6-4 safety or a 6-4 corner or a 6-7 400 pound offensive line, and those are, you know, we just haven't seen a whole lot of those players that have been in this league. So, you know, there's questions that you have to ask. Where are you going to play them? You know, what skills are they going to need to be required in those offensive line? You know, we certainly have a scheme that we're comfortable with, that we have really tried to embed and make our own. And so for us, there's going to be an element of movement and speed off the football in different angles.  So, you know, those are things that we look at talking about offensive linemen in the run game. You both have got to be better around what sort of the status update on that, what you've added already this offseason and how to be further than this run? Yeah, I mean, we're excited to work with Robert and with Austin, you know, and seeing what those guys can bring. They've been productive players in this league. You know, we'll continue to work and build. Again, we don't play until September. So, you know, it's a long process with putting the team together so that it's ready for opening week.  But again, like I said earlier, we're trying to get as many good football players really at every position that we can as possible. John, what are some of the results? Out the results, you guys have gone from the last two drafts. Maybe, you know, kind of more slow developing or kind of near to impact. How has all that maybe impacted the draft evaluation process? Has anything changed based on the way the last two collapses? No, I mean, I think there's different circumstances, you know, with every draft class. You know, I think that we have, we've seen returns on some of those players. You would obviously like to, you know, see more from, you'd like for all of them to come in and be impact players, you know, the reality for 32 teams in the National Football League is that's not high that that happens.  It's a different game, you know, the pro game is a different game from the college game. And trying to identify the right types of guys who can help our football team. Certainly, have you heard yourself with the Taylor Hill field and having the eyes to count the first week? Well, I think that when you look at cap, it's, you have to be so much strategic with how you attack it, Paul. You know, it went up this year, you know, we took that dip a year ago.  I mean, certainly you'd like everybody to have as low a cap number as possible. But when you're trying to fit everything in, sometimes you have to make decisions that you think are best for the team. You know, sometimes it works out, sometimes it doesn't. But we're glad Ryan's here, decided, you know, to work with him. And we'll deal with, you know, where there's, I feel pretty confident with Ben and his ability to work the pencil on the cap numbers. John, obviously you're looking at some of those offensive guys in the draft right now. Defensively, anything you'd be looking for to add in maybe some of those later rounds. And then can you give an update on Taylor Barley to have these coming along? Yeah, he's, to answer your first question, I mean, guys that can impact defenses, guys that can stop offenses from scoring points, whether that's upfront on the line of scrimmage, whether that's covering guys, guys that make tackles. I mean, you know, we've been able to find defensive help really at all levels of the draft. You know, whether it was Hooker on a Saturday pick, David Long on a Saturday pick, Jeffrey Simmons in the first round. I mean, we've been able to find guys that can come in here and play stylistically the way that Mike and his staff want to.  He's continuing to learn and work and how to be a pro and make that transition to try to help our football team. He knows how important it is to us that he puts in the time and he's dedicated. And, you know, he's certainly on the right track, it looks like. I had a good first week, I'll tell you that.  So not only just rehab, but just from a mental perspective and just being in those meetings and, you know, having him answer questions and I'm not gonna say who he beat, but he won the quiz competition today.  It's the same every year, you know. I'm gonna say that every head coach in the National Football League would like to have every single player there just because that's what we like to do. We like coaching players and enjoy doing that. Also very respectful of what they've done, where they're doing it, and hopefully, as we work our way, you know, into these different phases that we'll get, you know, as many guys that want to come back that want to be here. More of Mike or Ryan Daniel will be here, does he miss anything at Real Valley? I've had communications with Ryan. Again, as the head coach, I want every single player here. I would love to see that happen. Had communications with Ryan and I'm comfortable where those are at and, you know, expect him back here pretty short or shortly. Mike, how much of advisory role have you played in Tyler's going through the Grand Park? Oh, I am, I'm just excited for Tyler and his, you know, next opportunity. That's really what I'm trying to do. It's taken me a lot of years to be more dad than coach and I'm trying to do a much better job at that and I feel like I have. So, I'm excited for him to see where his next opportunity will be and try to support him any way I can. Is there a chance to reach that allows? No, John and I haven't even said it, but I think that there's 31 teams that are evaluating Tyler. I don't think that's good for anybody, Corey. What do you think of the long-term investment? Yeah, I mean, I think you have that conversation with the player. We've done that before. We've taken a player at a position that, you know, we had and was a veteran player and at the end of the day, I had a conversation with, you know, the player that was on the team. He understood, like, that's what it is. Again, we tell the players, like we're trying to create as much competition as possible at every position and trying to put the team in the best position to go in football games. But it's just transparency and conversation, up-frontness, you know, with the player, you know, as we have done in the past at other positions. Do you think I would be okay with that? I haven't had that conversation with it. I don't know who we're gonna pick yet, Jared, so. So, did the top tackles, I was married over to maybe, you know, if they're playing for that, it's gonna start right here, and who do I have to tell you about it? You just gotta go out there and see what you look at. Yeah, I mean, I think we've done that before. I mean, Jack Conklin was a left tackle and we drafted him and we moved him over to right tackle. And yeah, I think that there's guys in this draft who, you know, play one side, but we feel like that they're capable of playing another side, or maybe playing both sides. Essentially, not a coping draft. Your last not coping draft was 2019, which was probably your best draft was 2019. Is there a sense? Thanks, Jared. Is there a sense that going back to a normal structure will go back to the results of this not coping draft? If you're telling me that, absolutely, it's going to. I mean, you don't know. Like, you don't know who the players are gonna be there. You try to strategize and get yourself in position to get the guys that you want.  I mean, if you can tell me right now that we're gonna have another one like that, you're, sign me up for it. I would imagine, same as the B-Vap on a second contract, but if you look at, you know, the last five first round picks, there's a good amount of guys that haven't come back for a second contract. Is there a frustration level, just as far as like the return that you got on your first round picks over the last four to five? No, I think that there's different situations for every player. Like, when you're working through that and you're making those decisions, you know, Mike and I have those conversations about, you know, what's the impact of that player being here or not being here?   It's a pretty in-depth thought process and dialogue that Mike and I have when we make those decisions. Is there something about the 2019 class that was special or was it love?  I love it. Keep going. Is there something that we did this and are trying to find that in this class? Took the right guys. Like, we took the right guys. The process is pretty similar with how, or I would say it's very similar with how we did it. We took the right guys. That's good? Guys, have a great weekend.


everybody forced here ripping 2223 Chronicles basketball hobby six box half case number six pick your team style I've got Bradley are with the Mavericks Pacers and Spurs Brian M. Sons Chang Q with the Rockets Edward P. T. Wolves Ezekiel with the net sixers Warriors Francis H. Bucks Jared I. Magic Joseph R. Hornets Justin P. with the Cavs Lance H. Pelicans Long J. Raptors Luis M. Clippers Matthew X Thunder Michael S. Nix Patrick G. Nuggets Robert P. Blazers Rory Seahawks Stephen L. Pistons Tanavad Heats Tom G. Bulls and Lakers and Celtics Trevor W. Grizzly's Vaughn B. Kings and Jazz whaming with the Wizards good luck everybody I get these teams filled up there's only four breaks left for the daytime here with spots left I guys are no summer work that's kind of cool hey Gina Williams there we got Zion number to 75 for the Pelicans Westbrook they're red Zion hoops to 149 pelicans Stefan Laravia I don't know man there's some pelicans what is that it's like a blank but it's not thick all right Tatum Griffin Orange Mark Williams XR for the Hornets nice one there get Murray got a shade on sharp on the hoops update here Kevin Garnett Hall of Fame autographed to 75 Timberwolves sweet KG any more of these Hall of Fame autos KG got LeBron Atari Eason for and there is a Andrea Barniani Raptors auto Andrea Barniani Raptors Keegan Murray essentials Andrea Barniani the Raptor that Jay wants everybody Palo Bancaro nice Walker Kessler titanium 5 of 12 great card jazz that's pretty sweet that's pretty sweet congrats Utah got your bars for the junior silver Phoenix shade on sharp blazers red Agbaji to 149 jazz essentials so on yeah I thought I was going to let it color man oh man Mark Williams to 149 for the limited rookie they've got Johnny Davis Jalen Turin on the hoops LeBron and Palo all right teams are moving in number seven now Celtics Nets Bulls Cavs Nuggets Grizzlies Pelicans Nix and Sixers everybody so we got left nine to go right along box to seal wants it to be a Pelicans box Jabar Smith junior pinnacle rookie out of 75 Houston Jabar Smith Keegan Murray Dynagon got a red rookie Ben caro Dynagon to 149 magic stuff for the magic Dyson Daniels and Steph Curry got rookie to 99 as Andrew Nemmard for the Pacers on the luminance re Dyson Daniels purple LeBron marquee to 49 for the Lakers nice color match Lakers LeBron of the magic LeBron of the magic not for Palo though Chet Holmgren prestige Palo Ben caro rookie timeless treasures that's who 49 Orlando magic doing well pretty much throughout the day Kevin Durant Chet Holmgren hoops next is Diabate and Benedict Matherin Bava Jake L'Arabia 9 of 25 Chronicles base sweet L'Arabia that's awesome it's a Griffin Andrea Bargnani Raptors under the lights auto it's a lot of Bargnani so many bar and Bargnani for the Raptors Christian Brown Kevin Durant Jay Nivee Jay Nivee on the hometown heroes rookie auto to 99 for the Pistons awesome Ivy get that one back for you Pistons Mitchell and Matherin you guys here with you to say he said don't bombard me with a lot of Bargnani it's hard to run it's hard to draw bars over here or something about Andrea Bargnani Christian Coloco to 49 rookie limited for the Raptors that kid I could not have been good silver Levine for Chicago and nice during the 99 essentials blue rookie for the Pistons and Jankler Avia moving on here let's see so you guys got Chicago Cleveland Denver Memphis the Pelicans the Knicks the Sixers all left in the next one Celtics as well again all teams are on sale corners are gone now the next one I believe nine to go be much appreciated we get these breaks filled up everybody just four more Chronicles daytime of Chronicles draft over on channel two as well guys let's get that filled up 25 to go Chronicles draft football Keegan Murray rookie to 99 for the Kings plates and patches John Grant silver James Hardin the hoops there got red Keegan Murray rookie you go Kings XR to 1 49 excuse me shade-on-sharp Blazers essentials Dyson Daniels out of 75 for the Pelicans look at Donchich orange Jaden Hardy hoops orange Hardin 75 there you go Dallas Jalen Williams window more junior Paolo base shade-on-sharp prestige Dynagon Keegan Murray oh champ bucks rookie hometown heroes audit to 99 to 49 Patrick Baldwin junior Warriors on the absolute rookie there Dyson Daniels Jaden Ivy next is Kyrie and Walker Kessler Hawks AJ Griffin rookie limited number to 249 Chet Holmgren rookie hoops there now we've got Chet Holmgren Jabar so the junior marquee XR Jalen Brunson number do 149 for the Knicks nice we're pretty decent Vaughn Jabari Walker on the limited rookie Jersey auto Blazers out of 99 on for the Blazers which break did you have a jazz in one that's one of the last one to 75 we've got Giddy for OKC Hardin red Lebron number to 149 for the Lakers Jeremy Sohan on the Phoenix to 49 Paolo Ben Carol Phoenix rookie auto there we go Jared I yep 24 49 big congrats to the magic awesome Paolo Chet and Jabari then you hit a I don't know I'm gonna spoil it anyway you hit a titanium Walker Kessler to 12 rookie Bo champ to 99 for the Bucks but this breaker last one I know it was one of the other there's Kessler hoops shade on sharp now you've got to 99 Steph Curry essentials Johnny Davis timeless treasures rookie for the for the Wizards to 99 Matherin William Jaden Ivy we need a big gala now that Coloco earlier that's cool Giannis luminance the 25 bucks Jordan Hall spurs to 49 rookie Phoenix auto Jordan Hall spurs yeah Vanna's been great we pulled like four Andrea Barney on the autos we see the abate Clippers rookie to 249 limited Daniel silver Dynagon rookie Keegan Murray Kings marquee red to 149 Wendell more junior for the T Wolves there's Draymond and Anna and pool base or a pool beef is what I just read on the bleacher report that's interesting who could have seen that coming all right guys we got breaks the field coming up here Nets bulls calves nuggets Grizzlies pelicans nicks and sixers every single team is on sale to Buster tribute a one-gone Jesse Winker Oscar Gonzalez auto I mean it could happen you could also hit like a Corbyn Carroll look at Donchich you've got Nicola Jovic heat cornerstone rookie quadrize auto out of 99 nice one for the heat Matherin XR marquee Christie to 149 magic Franz Wagner read there now you've got the abate in Neymar not never that was Matherin wrong pacer mixed up Jabari Smith junior rookie to 249 for the Rockets plates and patches Matherin on the hoops shade on sharp blue rookie Phoenix 42 of 99 trailblazers of the sea of trailblazers very very nice got Ivy to 99 pinnacle rookie for the Pistons Matherin rookie there for the Pacers in the Phoenix Malik Monk number to 10 gold auto for the Kings Kings score auto to 10 Malik Monk Arabia Chet Holmgren essentials for Jalen Williams rookie gold standard in 99 awesome Jalen Williams for the best break over all today so far Jabari Smith junior silver Luca the hoops guy Yanis to 149 bucks essentials and Luca still spots available the next four breaks as well everybody last four PYT's for Chronicles daytime on release day chat to 10 4 of 10 ok see gold Chronicles base parallel oh my oh my Matthew X yep we'll get that mag of course big congrats Matthew 4 of 10 Chet gold here he is man what a break Jane Ivy Chet Holmgren red hoops to 149 got one card in between the number Chet's holy cow Steph Curry and Donovan Mitchell stuff space yeah that was an awesome one let's break this killer as Matt's got some Chronicles graphics football break he's trying to fill up over on channel 2 got Jane to 249 for thunder he can Murray Mack MacLung got Phoenix rookie Jabari Smith junior Rockets Nate Archibald Celtics on the Hall of Fame auto here to 149 great Nate the great God you're barricade junior and Chet Holmgren again this is our best half case of the day I'd say Thomas Treasurer's Brandon to 149 for the Spurs silver Paul George Clippers next up is an orange Jalen Williams ok see to 75 my smart key color match ok see Kodrush in its ok Nets Bulls Grizzlies Pelicans Nixon 6 or 6 to go a Muggsy Bogues took took the Hornets up to gets I can't even think of a I can't even think of like a funny Hornets player right now Matherin Jaden Ivy Phoenix blue that is sick to 99 that's getting mad for the Pistons congrats Pistons oh my goodness Ivy essentials who's Monjang with Ivy auto with Ivy auto as well the mellow hoops redemption who pain Watson Nuggets limited rookie Jersey autograph vice redemption for Denver there they've been on sale all day Hardy there you'll catch Dyson Daniels that is a oh look at that I'm Baji jazz the 25 marquee there you go jazz and Malik I brand them me dust this off do the recap okay four mags and a chronicles half case that's awesome all right we got Nuggets redemption Peyton Watson got Nate Archibald Jordan Hull March on Bochamp Andrea Bargnani twice Kevin Garnett's Yati Yovitch or Yovitch excuse me Yovitch Malik Monk gold to 10 on the auto of the Kings that is a Jabari Walker rookie Jersey auto Blazers Ivy on the Phoenix blue to 99 go to the Pistons and as a to 10 Chronicles Shet Holmgren base the Thunder Jaden Ivy rookie auto to 99 Pistons and Palo purple auto out of Phoenix sick Palo there to 49 congrats Orlando that's gonna do it we're moving on to half case number seven