This 2019 Ford F350 SuperCab Long Box Dual Rear Wheel is stock number 12160Z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy duty truck headquarters. This 2019 Ford F350 has the 6.7 liter power stroke diesel. This truck has been fully safe and inspected by our service shop.  And this truck is 100% ready to go. Black agate metallic 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, smartphone, or television, turn them on right now. Because it is definitely your best way to check out the quality, condition, and options of the truck before seeing it in person. And if you like the video and want to subscribe to our YouTube channel, the lower right hand part of the screen is a subscribe button. You can click that and then click the bell notifications. You'll get updates on the videos we do each and every day here at Summit Auto. This one also has the FX4 Off-Road Suspension Package.  Polished aluminum rims on here. It has Michelin LTX LT24575R17 tires. They have a little bit under half the tread left, right around half right there. Frame and under body is in excellent shape. Front fender is in nice shape as well. No dents or dings on there. Headlight lenses are nice and clean. Front bumper is in excellent shape. You can see any dents or dings on there and it does come with the factory fog lights. The hood is in very nice shape as well. You can see any dents or dings on there. Passengers side front fender is in nice shape too. And the passengers side rim, no scuffs or scrapes on there. Looks really good. As you go down this side of the truck, take note of how clean the body is, 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 truck here, the truck, and have confidence in what you're looking at before you even get here. So when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from wherever you're at. And if this video helps you buy this truck, let your salesman know and tell him Brett sent you. Back rim is in excellent shape as well. No scuffs or scrapes. Back tires have just about as much tread as the front tires. Maybe just a little bit less. Frame and underbody is an exceptionally clean condition. This is a one owner out of California. It does have the camper package with the anti-sway bars. Frame and underbody is exceptionally clean. And the lower cab corners all look really good. Factory chrome step bars. The dually tubs are in nice shape as well. I didn't see any dents or cracks on there or major scuffs. Rear bumper is in great shape. No dents or dings and it does have the backup parking sensors full towing package which includes the receiver hitch four pin and seven pin wiring. The tailgate is in excellent shape as well and it does come with a soft tonneau cover. This is a shock down assist tailgate. Spraying bed liner, fifth wheel and gooseneck prep package. Turn the LED lights on in here so you can see a little bit better. It also has the seven pin wiring and side box tie downs. Once again and that's a factory Ford Toughliner or Toughbed as Ford calls it. Spraying bed liner. Very nice back there. And as you come around to the driver's side just as nice as that passenger's side. No dents or cracks on the tub. Didn't see any major rock chips or anything. And this back rim is in excellent shape as well. Down the rest of the side of the truck looks really good. It does come with the door code entry which we have the code for. If you ever wanted to find out what your door code is for your 17 to 21 super duty in the upper right hand part of the screen is a video on how to find that. Heated mirrors, directional signals. These are power scopes so they power fold in, power telescope out. And we'll show you how that works in just a minute. This one has the Lariat package which gives you the black leather interior. There are no rips, there are no tears on this seat. It is in excellent shape. Factory all weather floor mats, auto headlamps, power pedals, telescope exterior wheel. Power windows, power locks, power mirrors, memory driver's seat. And these mirrors do power fold in like so. I always like showing both sides so that you know that both sides are working properly. And then it does have the power telescope out feature and in. Once again, both sides working good. We'll hop inside and check out the miles and ignition and radio and everything that this truck has to offer. Get the nice built forward tough animation there. We'll dim it down for you. 18,209 miles, you get a digital speedometer, big information center, compass display as well. And that instrument cluster is very nice and clean. This steering wheel is in excellent shape as well. It is leather wrapped, Bluetooth and audio controls on the right. Cruise controls and information center controls on the left. This one does have the six speed automatic transmission with the optional tap shift. You do get the sync eight inch radio AM FM. And I believe it's got serious satellite radio, but I just want to verify. Yes, it does have serious satellite radio capabilities on here right there. This is also where your backup camera shows up. You do have a factory exhaust breaks, stability control, downhill assist control. You can connect it to your Bluetooth phone. You can do your climate controls on here. And you can also do all your different apps including Android Auto, Apple CarPlay. So you can project your cell phone to the screen. So while this one doesn't have a navigation system on the radio, you can project it from your phone such as Waze or Google Maps to the screen. And then you have a nav right on the screen. So that's pretty cool too. Turned out four wheel drive factory brake controller down here. You're heated in cooled seat buttons, your dual climate controls, two USBs, couple cup holders, nice storage area, 12 volt power point, 110 volt 400 watt plug-in. Passenger side, floor mat and seat are in excellent condition as well. Smells very clean inside this truck. The headliner is in really nice shape. And you do get six auxiliary outfit switches. So if you want to add extra lights or anything to this truck, use those just as power switches. We'll take a quick look at the back seats and then we'll start it up and take a look under the hood. So these super cabs, these doors open up all the way like so. That's really convenient when you're getting into the back of the vehicle or loading it up with stuff. Back seats are in excellent shape as well.  These seats do fold up for extra storage. Then they kind of lock into place. They lock into place like so. All weather floor mat back here is in nice shape. You get 110 volt 400 watt plug-in, two USBs, power points, and then a 12 volt power point right there. And that's just a normal plug-in. Very nice and clean. And these doors kind of just swing closed like that. We'll start it up and then we'll check out under the hood. It starts right up and other than telling me my hood and doors are ajar, no check engine lights or anything like that. I would personally like to thank you for checking out the video today and hopefully from this HD video you will have been able to verify the quality and condition of this truck inside and out. Under the hood we have the 6.7 liter power stroke diesel engine. Engine bay is very clean, runs very smooth. And once again, this truck has been fully safety and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. And this truck is 100% ready to go. There's your emissions sticker. And to see more pictures of this truck or one of our other 450 new and used cars, trucks, SCVs, minivans, Wranglers, half tons, three quarter tons, one tons, you name it, we got to go to that website right there. www.summitauto.com Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos you can go to youtube.com slash summitauto.com. Remember to like, subscribe, and share on this video and all the videos that you see there. Click the bell notifications. You'll get updates on the videos we do each and every day here at Summit Auto. In fact, in a second you will see a link to subscribe to our YouTube channel and the upper left link to more F-350 videos like this one. The upper right link to this vehicle on our website and the lower left and link to one of our latest YouTube videos in the lower right. Click those, check us out. And we're super excited to help you with this Ultra Clean 2019 Ford F-350 SuperCab Long Box Dually Lariat FX4 in black agate metallic. Thanks again for checking out the video. Remember to like, subscribe, and share.


Yeah, from a very high level, net ops, especially in the back end side, we have a three different area by force file, info, and Sentinel from the high level, the picture is like, at least I will have a mirror doc can share every inches. The team will go through and into into dust or what they are doing and the team member and what we are today. So for here, I just become the one to star is this conversation, but all the how well does it happen is missing the team? What is by first? What does the by first team do? It does a few things, mainly runs IPFS infrastructure at scale. Our biggest project is the IPFS gateway hosted at IPFS.io and the web.link, which allows browsers that speak well and tools that speak HTTP to access content from the IPFS network without having to run their own nodes. It basically provides a canonical way to address IPFS content via HTTP. We also provide the default bootstrap nodes, which are baked into go IPFS and JS IPFS as a public service so that other nodes can find each other in the network. And we also run preload nodes, which augment JS IPFS and expose IPFS end points that are not available in the browser. In practice, that means that JS IPFS clients can add content locally in the browser, then use a preload node to request that CAD, effectively caching the data and allowing the browser to have to be closed and be loaded without losing the data. So why are we doing it? Our motivation is to provide the best performance infrastructure for others to use, and most importantly, for the IPFS gateway, which seems to be the most widely used infrastructure, provide best practices and standards and tools for others who want to run IPFS and IPFS cluster at scale. How are we doing it? The high level of how the gateways run is we have bare metal nodes. They're run on Equinix. We run in seven data centers, and we have between four to 16 nodes. The reason we run on bare metal and net VMs is because this IO is very important, and access times are very important if we want to provide very fast service. So that's why we haven't moved on to VMs yet, where most storage is via network, basically. We're working towards that, too. There is a load balancing layer that's running NGINX, and does all of the HTTP layer balancing and filtering and such, and also a separate IPFS layer upstream from that, which allows us to scale out just the IPFS boxes without having to mess with any load balancing or NGINX issues. On the load balancer layer, we run, we use anycast to route traffic to the two addresses. To the data center that is the fewest hops away from the request origin. So each load balancer node announces a global BGP route for the IPv4 and IPv6 that we run. We use hundreds of metrics, if not probably thousands by this point, to monitor and alert. As far as uptime goes, we have pingdom checks, synthetic checks from the outside of the network. Within our network, we have NGINX metrics, load balancer, error rates, performance, time to first byte, that kind of thing. We also collect go IPFS metrics from within IPFS, things such as go routines, peers, want lists, also time to first byte within IPFS, and also OS level metrics such as IOCPU, generic things. We follow infrastructure as code principles, which means everything that we run is managed in GitHub, and we deploy through CI via Terraform and Ansible playbooks. For progress so far, we've recently hit one billion requests a week on the IPFS.io gateway. It has since gone down a little bit, but it seems to be going back up. So we're hovering around a billion requests, total requests. And we've hit time to first byte of around eight seconds for 95% of our users with a 99.9% uptime. And what we're going for is five seconds. So we will continue to scale and improve our system to ensure that for 95% of our users, it doesn't take longer than five seconds to start receiving content from the IPFS network. All right, fill in for us. So what we do, we operate and monitor core file point network infrastructure, bootstrap nodes, api, chain.love, that's dashboard, disputers, and we're also a core part of running the DevNet, butterfly net, and interop net. We drive operational improvements in tooling and Lotus, and support and enable network developers and operators. Our top goals for 2022, the first one is around api.chain.love, which is a Lotus gateway. This is a service that I'm sure many of you have possibly used. It's the default in Lotus Lite, and Lotus Lite is often used as the introduction to file points. The many new users, they interact with the file point chain through chain.love, and it allows you to interact with it with the chain without running a full Lotus node or a distrort. So we have some very ambitious goals here. We're trying to push it to be able to handle more than 200 requests per second without having latency in the chain thinking. And we're really looking to push Lotus to its limits and develop tooling and improvements in Lotus to reach our goals, because it will be very difficult, I think, with the existing patterns to get to a goal here. We also have a goal to run a Lotus chain backup service that produces backups that are never older than eight hours. Reba has done an amazing job in file point launch of running this, and we're hoping to launch a parallel service so he can sunset his and move on to other things. And we are, in general, trying to reduce the operational overhead for Fill Infra, so we can focus on high impact projects and not get bogged down in some of the manual toil that we have in the past. So how are we doing it? We are monitoring for high uptime and collecting data for continuous performance tuning. We're automating and improving the deployment of our Lotus Core Infra and reducing manual toil for our team and creating and sharing operational tools and resources. And we're also supporting a lot of devs. We are providing access to storage provider hardware and storage for five teams in our data center, and we're leading a managed GitOps platform rollout, which is what Sid had mentioned, which is WEAP, and WEAP will give the ability for Android teams to have autonomous control over their applications and network deployment capabilities. So we're rolling that out within the next month or so, and we will give you more updates on milestones as we start to work with WEAP. So this is a basic diagram, and it's showing we are running our current core Infra in EKS. So we run Lotus and the Gateway and the stats board there, and that's where we're focusing some of our work around deployments and automation. We collect data in Prometheus, visualize it in Grafana, and then we also monitor that data and page and send alerts. Our progress so far was super pumped about ChainDobble because we're seeing a pretty huge increase in usage. The weekly average is currently at 45 requests per second, but that's a 57% increase from 40 days ago, and we have four lines in uptime for that same duration as well. We have three regions where we actually operate our clusters, so we have nine draft nodes in three regions, so it's easy for anyone to join the Filecoin network. And for the stats board, we have a 99.8% uptime in 2022. We would like to get that to three lines, but we're super close. What's next? We have the Filecoin Chain Snapshot Service. It's in its planning phase, and our first milestone is to provide snapshots in S3, which is the current functionality now. And we are also hoping to push on HA and scalable Lotus because we need to ensure that we can keep Chain.Love up and meeting the demand, and we would really love to actually see this service growth super useful to the whole network. And we have a recent Lotus Build Artifact Improvement Plan. There's a link to it there. You can read more about it, but the general idea is to increase the build success rate. And the usability of Lotus Packages and images that get built as part of the CI pipeline. And that's all. Thank you. Thanks. Karin, I'm with Sentinel. Hey, everyone. I'm Hector. Sentinel is another of these things inside NetOps. And our goal is to guide this access of protocol apps technologies through data monitoring. We're especially focused on everything that happens on the Filecoin chain. That involves doing a bit of everything, writing software and running it in our infrastructure, doing a bunch of data warehousing, but also doing monitoring and analysis of the Filecoin chain and dashboards, other things. Our main objective is that this chain data is complete. It's reliable. That means it corresponds to what is actually on chain. That we're able to query that data really fast as soon as it's produced by the chain. And that we can extend those queries for the whole length of the chain, which is when it starts becoming a large amount of data. Of course, it's not only for us internally, it's also for the community to build upon this. That means that we need to make not only the software, but also the data that we extract available for reuse for the community so that they can run their own analysis. And we have to keep all of this running while Filecoin keeps taking great steps and making progress at great pace. This is a very simplified diagram of the Filecoin data extraction pipeline. We have Lili, which I will speak a little bit more in a moment, which is the application that extracts the data from the chain. We push that into a database, in this case timescale. And we have an additional data pipeline, which is essentially storing the whole archive of data also on S3 packets and making it available through Asina, etc. So it's very simple here, but there's a little bit more complexity when you look inside those boxes. One of the main applications that we write and maintain is Lili. Lili is a wrapped Lotus node that watches the chain. And on every epoch, every 30 seconds when the new tips have happened, extracts everything that happens in it. Messages, chain economics, sectors that have been committed, deals, etc., etc. Everything extracted as a structured data into a database. The idea is that we have this running and following the chain perpetually, but also that we're able to use this to also reprocess the chain or extract data from previous moments in the chain. That happens when you were not running during a certain time or when you introduced a back or when someone wants to do something else with the data or when someone wants to process a chain which is not mainnet, etc., etc. This is the diagram of the architecture. I think the thing that we're aiming to move to when we want to escape horizontally and so on. Now it is similar, but things are more contained on a single application, a single demo. The main thing that worries us for Lili is that with FBM and with the growth of the Falcon chain there will be way more things happening on chain that will mean way more data to extract. And that extraction needs always to happen within these 30 seconds that every epoch takes because otherwise you're going to be falling behind. Therefore, we need to find ways to parallelize extraction as much as possible so that we can indefinitely scale and being able always to have this fresh data for analysis. We've done lots of progress. We're at a very stable moment now. We're able to process the chain in time. All the data goes into the dashboards, into the database. All the data goes into the archive. And our database and our archives are available to partners that we support and that build their own applications. For example, Starport has made really nice public stats or public panels with graphs about Filecoin for the community. They make Twitter threats about Filecoin data and so on. And this is all powered by the work that we do in Santina. And Steph is going to talk about this one. Hi, I'm Steph. I'm part of the Santino theme. And I'm mostly focused on the data ingestion and data analysis side. We want to provide data to everybody in the PL Network so that you can make more informed and smarter decisions in your everyday work. And our goal is to build a data platform that enables anyone in the PL Network to perform their own analysis so that you wouldn't have to, let's say, come to me and ask for a query. Ideally, you would be able to do that yourself. So that's kind of what we're working towards. How are we currently doing it? We're creating a source of truth with pipeline that gathers data from different varied sources. So it's not actually only trained data, but also data from our Airtable CRM, Twitter mentions, stuff from elastic search for meteors and event folk, and we also enable the warehouses for the interest group and also BI systems so that people can use their self-service tool of choice, whether that's periscope or looker or observable. Yeah, so currently there's already a lot of dashboards available in periscope and data warehouses such as StartChiff are already queryable given the correct credentials. If you want access to it, you can just do me and you can set something up for you. What's next? We need to automate a lot of existing manual processes. So for example, our archiving operation is actually done, it's triggered by the user. So somebody interfaces into an EC2 instance and then runs a bunch of commands and then the archiving process is performed. But ideally this should be in a pipeline that's triggered with a cron job instead of somebody, instead of a person having to do it. We would like straight or well to find self-service data on that so that hopefully by this year people can ask questions to our data warehouse and get answers directly. Awesome. Thanks a lot, NetOps for the deep dive. Thanks all for everyone who presented and for tuning in this week. We'll be back again in four weeks. Hope everyone has a wonderful rest of the day.


Hello and welcome to the pre-Christmas JavaScript SEO Office Hours. My name is Martin Splitt. I am in the Search Relations team at Google. And I am really happy to answer any questions about JavaScript and, well, Google Search. Today, we have a few questions submitted through YouTube. We have a few people in the audience live today as well. We do these roughly four nights. So every 14 days, roughly, I am doing these sessions. There is a thread in our YouTube channel's community section where you can ask your questions. Or if you want to join the live recording, I'm commenting with a YouTube link in there so that you can ask another YouTube link, a Hangout link in there so that you can join the live recording if you wish. Right. So there are a few questions, very few questions, on JavaScript, actually, but a few questions that touch roughly on JavaScript. So I'll happily have a look at those. Gregory Scott asks, from my understanding, the speed-ranking factor for web core vitals, core web vitals, but roughly, right, would be based entirely on field data and not lab data. Is this correct? Yes. At the time of this recording, that is absolutely correct. What that means, if I'm not wrong, is that the guidance from the lab test, like, throw, lighthouse, web.dev, page speed insights, may deliver results that are inflated scores, or deflated, actually. It might give you very different scores. That is correct, which are pointless. Ah, I disagree. They are not pointless. They are indicative. So they are not necessarily the accurate values that you would see in field data, but they give you a hint on where might be issues. It does not cover everything, obviously. While lab data might show everything is fine, field data might show, actually, things are not very fine. That's why it's important to also measure in field data. But lab data usually is a good cannery in the coal mine. It gives you a feeling for where you are and where potential problems lie. So they are not pointless, but they are not the truth. It's really, really hard to say what is the truth when it comes to website performance, because it really depends on lots of factors. Then there is a, he gives an example on WordPress where changing plugins gave the options to remove the version string from the files which inflated performance scores and was practically useless for field data. Then you know that that's not useful. That's gaming the metrics in that case. So the main question, does this mean that delayed JS function in some of the more popular caching plugins for WordPress lately is just that a trick for the lab data scores that won't have any practical meaning for the field data? Measure. That's not generally like delaying JavaScript to a later point might be useful. It might not. You have to measure if that's a problem for people on your website or not. I would not trust the lab data 100%. Again, the lab data gives you a rough guidance. It gives you like a trace a bullet to figure out where problems might be and debug these problems relatively interactively, which you really can't do with field data. So it has its purpose, but obviously there are things that can gain the metrics, but that's a little pointless because if the users are still experiencing a slow website, that's going to reflect in field data. So be a little careful with that. But if your measurements show that the field data does not benefit from that function, then that's probably an indicator for that being a metric gaming rather than an actual improvement for users. Tobias Merz is asking, hi there, we have a problem with our cumulative layout shift. We implemented a sticky nav without position sticky since it's not supported in all browsers. Our solution is more like bootstrap affix. I don't know what that is, but I know bootstrap, but I have no idea what the affix is. So we listen to the scroll event and set the position fixed top zero when the nav sleeves the top to prevent a jump or layout shift. I have a wrapper around the menu with explicit height. Therefore the wrapper still has the same height even the nav gets position fixed. So there's no layout shift. Everything seems to work fine. It looks good for the user, but the CLS is counting up every time and a lot, why is that so? Without having a look at the specific example, that's really hard to say. I could imagine figuring out a way to take nav out of the nav flow like position absolute, but I was thinking position fixed does that as well. But I would definitely consider asking on either the JavaScript sites mailing list to bit.ly slash js dash sites dash wg with an example URL to look at or maybe the webmaster forum or feel free to go to Stack Overflow as well with these kind of questions. And again, provide a clear example and you can build a fake example that just shows the behavior because without something to actually investigate or look at, it's really, really hard to give an answer to that question. And there's one more question from Gary Scott around the web core web vitals. Hold on, no, I answered that one. Oh, right, it sounds like it's the same question, but no, it's not the same question. It starts with the same introduction, but then it's like, does it make sense from an informational site to block all countries out there except a few bigger ones in order to get the best average field score for that speed? I know I can do that. The question is if I have, for example, low return on investment from countries with slow internet connection with large population, does it make sense to cut them from accessing their website since they have a slow connection that hurts my field scores? No, that's thinking that is laser focused on the core web vitals. And that's really, really, really risky. A, because people from these countries, if they want to access your website, they will through a proxy or what's called a VPN, which really is mostly a proxy for most cases. And then the speed is even slower, so not helping. The other thing is core web vitals and page experiences, one ranking factor out of hundreds of ranking factors. So you should not overestimate the power of this ranking factor. It is important, it is not the most important. And I think if you have useful information and you can get this information to people and get some ROI, you should probably do that. Because again, there's hundreds of ranking factors. Speed is not the only thing. Because if speed would be the only thing, then a blank website would rank really well because it's really, really fast, right? That's not the point. Fast is an important quality signal, but there are other quality signals that really, really matter too. So I would not do that also. That implies a more complex setup, which usually invites more problems. I would not do that. I don't think that's a reasonable thing to do here. And then we have a third question from Gregory. I don't know if you know this, but WordPress decided to reinvent itself with a new editor called Gutenberg. Yes, I know that. They're using web components in there. With installation of the plugin, you can get more current features that they think to implement. It's basically turning the whole page into blocks. I'm not sure if these blocks are only happening when you edit the page, or if that's also in the output of the pages. I would have to look into that as well. Since one page of 2K words and images could actually be something to 20 or 30 blocks or more as each new paragraph is considered a new block. What I noticed on the last change logs is that they would consider splitting styles so that each block has its own style CSS. This means that loading one page could resolve and having 30 or more style CSS files. I would assume that they don't do that when they deliver the actual page, but maybe I'm wrong. That's a question for the Gutenberg team. I would ask them. I would ask them and check what they think because I'm pretty sure they're not doing something for the sake of just doing it. I'm pretty sure they have some reason behind it. And I think performance is on their radar. So the way you describe it sounds like performance issue or potential performance issue. I'm pretty sure they don't do that just for the fun of it. Ask them they are, it's everything is on GitHub. You can ask them the Gutenberg repository why they are doing that and if they are, or what's offsetting the performance hit from that. And I'm pretty sure they have something to say to this. Then we have a question on Hylia, John Miller. Not quite, close enough though. Martin here, hi, hi Rafael. I'm from Brazil. So when I run Intest PageSpeed Insights laboratory data generated regarding my website, it's made for Brazilian users, but it's hosted in the US with the CDN. Is the data from the Brazilian server or an US server? I think it matters, but what matters really is the field data. Yeah, the field data is actually what matters. PageSpeed Insights probably generates it from a US server. If the server is, if your server is hosted in the US and PageSpeed is hosted in the US then they'll likely have a better connection than users coming from Brazil. Even though Brazil and US shouldn't be too bad if the server would be in Australia, I would be more worried than that. But yes, the field data is what you should really consider. Again, the lab data gives you a rough tracer bullet for where problems might be, but it might not show all the problems because again, the disparity between the two field data and lab data. And then that's it from the, no, there's one more YouTube question from Mustafa who is also in the call, I know that. Regarding crawl stats report, what should I do about a huge drop on the crawl stats report from 300K requests to 50 to 70K requests? I checked the performance on the search result clicks and the sessions on GA both look normal. Then my answer is that doesn't seem to be a problem. The amount of crawling that happens is no indication for quality or ranking or whatever. The crawling we do is based on lots of things. And as long as your crawl stat report doesn't show anything like scary as in like your server is actually generating lots of errors or your server is really slow in responding. As long as that's not the case, you should be fine. And thankfully you gave us a sample URL so I can actually take a look and I shall do that here. And as far as I can tell from the coverage, nothing really has changed. So it's not that we are not seeing something or that, as you say, the performance hasn't dropped. So that's not a problem really. As far as I can tell, the crawl is going up again with 200 crawl requests recently Sunday. So that's three days ago. I do see a drop from 300K to 41K-ish, but that itself is not a problem. It's just meaning we crawl less, but that has no meaning on anything like we don't think it's less quality. We don't think we just decided, oh, most of the pages probably haven't updated. We don't need to crawl as much. We only need to crawl a few 10,000 pages, like 40,000, 50,000. And now we are probably seeing that we need to adjust again. So we are upping the crawl budget to 200K. Maybe it goes further up. Maybe it goes further down. It doesn't really matter. As long as you're not seeing any issues in the performance or in the coverage, I wouldn't be worried about that. Also, the increase in crawling could also come from the fact that I think we switched the side to mobile first indexing recently. So it might be that we are re-crawling with Google smartphone now. So that is why the crawling goes up, and then it will probably go back down again. If we establish that we don't need to do as much crawling, that's just it. Again, as long as the performance is fine, as long as the coverage is fine, there's nothing to worry about. Right. And with that, we are through the YouTube questions. And I'm very happy to take audience questions now. Now is your turn, everybody. Pawe. Hi, everybody. I've got a question. I hope not a silly one. So we've got this server-side rendering website built with Gatsby and React. And what I noticed is that a website was really fast for a user. It's a very fast one. I mean, the user experience from the point of user experience, it's a really fast website. But when I look into Google tools like Lighthouse, I just noticed that the site got much slower in Lighthouse after installing Tag Manager. And I know that Tag Manager code is performed synchronously. Sorry for my English. Always. Always. So I just wonder, where does it come from? I just feel that it's related somehow. But I can't figure out what's the reason. And I'm just looking for some kind of explanation, I think. So as I said, the lab data and the field data are not necessarily the same. If you have Chrome UX reports available for the site, if it has enough data points in there that it shows, then I would look into that. And Search Console has it under the Core Web Vitals report. So if those look fine, then I wouldn't worry too much for Lighthouse and web page tests and all of the others, like page feed insights. I know that they have a really hard task, which is to generate a score from a lot of different metrics. Now, these metrics are not all what is in Core Web Vitals. There's more metrics than there are in Core Web Vitals. Core Vitals are just a part of what these tools report on. And to generate a score, they have to mix these metrics somehow. The mix, at least for Lighthouse, the mix is documented somewhere in their documentation. And you can find out how they weigh the different metrics to generate the score in the end. And depending on how that score is generated, you might see interesting fluctuations. And if Google Tag Manager does something that is relatively heavy, but does it in the background, that might not actually affect what users perceive or notice. And that's great. But it might affect one of the metrics that these tools are looking into. Whatever that metric is, it could be like total blocking time. It could be time to DOM content loaded. It could be various different things. It could be the parse time. It could be that the Tag Manager detects these tools and then loads slower or something. And then that mixes into the scores. And then that's why we'd get a lower score. As long as the real user metrics look good, you shouldn't be very too much about that. Again, the lab data testing tools, Lighthouse, PageSpeed Insights, WebPageTest, they give you an indication on where to look. But then you still have to interpret these metrics. A Lighthouse score of 100 doesn't mean anything unless you actually understand that the metrics that you care for are really looking fine. A Lighthouse score of 50 might mean something. It might mean, oh, we should look into this. But it might also just be like, oh, yeah, this is measuring things that we don't really that much worry or care about. So that's not a big problem. Luckily, Web.dev has lots of information on how these metrics work and what they mean so that you can make more educated guess on what you should do about the scores you are seeing. But when you see these discrepancies, and I've heard a few offenders like Google Ads, apparently, is a thing where that can happen. Google Tag Manager is a thing where that can happen. Certain YouTube embeds have this issue. So even Google properties are not excluded from that because the testing tools don't care where requests are made to or coming from. So you might see differing values between the real user metrics and the field data. If you have real user metrics available, that's what I would look into. Field data, sorry, lab data is interesting to just debug things and get a feeling for where you are going, but I wouldn't worry too much about it if there is an issue with just the lab data values. Okay, thank you. I think it's clear. Yeah, and this is what you said. I noticed that the tool shows me some information about total blocking time. So that might be one of factors, yeah? Okay, generally speaking, okay, just... So if I understand correctly, so the important thing is how really user experience the website, yeah? Yes, that is correct. Okay, thank you. You're welcome. And this seems to be like the theme of today because most questions are circling around that. As a general note, I want to say that measuring user experience in terms of responsiveness of the site and speed of the site is ridiculously complicated and has lots of caveats that are really, really hard to quantify. And the goal really is to have something that is a very human interaction as in like how quickly does the site respond? How quickly does it show the content also of all of these things? How much of my CPU does it spin? How much of my battery does it consume? We try to put all of this into a number and that's always a hit and miss. Oftentimes it works in some edge cases, it doesn't. In some edge cases you get reports that don't make sense. And then there was someone asked the question, to be asked the question with the CLS where they're like, we don't think that that's the case. I would try to report if you see like CLS values being very high in Lighthouse, for instance, I would report that to the Lighthouse team with the sample URL so that they can take a look at it because maybe it's just a glitch in the way that CLS is calculated. That is absolutely possible because it is surprisingly hard to get these values accurately. And also to find metrics that are, that's the whole reason with the core web vitals. It's not like, oh, we wanted to make something up so that we are busy. No, it has been that we had lots of metrics and the web has changed and the way that users interact with the web has changed and the metrics didn't no longer fit how people were actually experiencing the web. So we had to come up with new metrics that happened relatively randomly which pissed off people understandably if you are optimizing for the metrics that you are given and then the metrics change and now your optimization work looks like nothing has happened or it actually has made things worse. They're like, what the hell? So the core web vitals give you a more structured and time-slotted way because we are considering updating them once a year roughly and not like in random times throughout the year. So it gives you a more predictable set of goals to look into even though we understand and hopefully you understand these core web vitals aren't perfect either because there will be websites that are really fast for users but don't look great in core web vitals. That's why these metrics keep evolving and keep improving but getting a perfect score for what people are experiencing on websites is really, really hard. All right, any further audience questions? And again, you can use the chat or you can use the microphone and you can use the raise hands feature. Dave. Hi, since we're on a bit of a performance bent today is there a massive benefit on streaming response? Particularly something like an SSR server-side rendered something maybe hydrase later tends to compile it all, bug it all across. I can see there's a few frameworks that I was trying to push towards streaming that initial response. It looks extremely complex in certain parts and it seems to have some drawbacks but is it really worth something pushing towards or do you think it's kind of a case-to-case basis so there's no real rule? I think it's probably on a case-to-case basis but generally speaking, it does make sense if you think about it.  The request comes in, a program runs, generates the DOM or generates the HTML and then sends the HTML over the wire in one big block. So basically what happens is the request comes in and from the browser's perspective nothing happens for a while and then it all comes over. If we could shorten the amount of nothing happens for a while from the browser's perspective I think that would be good because then you could start or the browser can start to build the DOM as the data arrives, which has been the case with static websites. You have a file on disk, you have the browser requesting it and basically immediately as the file is opened the data is streamed over the network so like it arrives bit by bit in the browser. Not like nothing happens for a long while and then the entire thing starts streaming in but that being said, you already hinted at is streaming a HTML response that is generated by any kind of program and I'm not even saying JavaScript specifically. This could be a Java program, this could be a PHP or Perl program, doesn't matter Python. C++ if you really want to have the pain of that. Having that stream the data as it generates it is probably a lot of complexity that usually means where there's complexity there are bugs and edge cases that are surprisingly hard to cover. So I would not be surprised if that is not worthwhile especially if the time that the program runs is in the sub seconds. Like if your PHP script or your HTML script if your PHP script or Node.js script takes like 0.5 seconds then I don't think it's worth the hassle. If it does run for 10, definitely worthwhile. Definitely worthwhile sending the data and 10 is just like in a very extreme number to just make sure that we are talking very extreme numbers here but the reality is somewhere in the middle probably like sub seconds and then everything that is longer than a second you can probably see benefits. Everything that is longer than two seconds you very likely see benefits. But again, then what's the complexity that you invite into your code? Is it worth it? Can we make it so simple that it doesn't generate so much overhead that A, the program runs slower and B, problems happen that we then need to mitigate with even more code. I think that's an interesting venue to explore. I haven't seen as much exploration in the wild yet but I think it's an interesting thing to try out and see if you can actually gain significantly. I remember I did that with WebGL. I was exploring if a certain WebGL format so basically like JPEG for 3D graphics, GLTF if that could be streamed and what you would gain from it and the gains we saw were huge but the complexity we saw in creating these models in a way that they would be streamable was so big that even the huge gains we made and we were talking gains of like 20 to 30 seconds on a 3G connection but it would take tens of hours of a 3D artist with specific tools that are really, really expensive to actually generate these models. So we decided it's not worthwhile and we might as well run into the situation like this with streaming for a server-side rendering framework but I think it's worthwhile to try it out. We should probably try it out as a community. That's a cool idea. Thanks for the question. You're welcome. Oh, to be honest, yes, you can simply open an issue on github.com slash Google Chrome slash Lighthouse. I think that's their GitHub repository anyway and they have an issues tracker and if you say like Lighthouse reports CLS here and we don't understand why then is it Lighthouse? No, it's not. RenderTron is a completely different thing, Lighthouse. You can search the issues here or so either add to an issue that exists or you can add a new issue there, report it and you'll get an answer. Even if the answer is no, that's working as intended and that gives you a hint on that it's not the tooling that's something that you are not seeing there but I would not be surprised if there is a glitch. All right, for the questions, it's funny because the recording will be sent in two things, like I'll get a video and I'll get a text file with it. Always funny when that happens. We do not have further audience questions. I would like to say thank you very, very much to everyone who submitted a question through YouTube. Thanks for everyone who joined today. I hope that you're all safe and healthy, that you have a fantastic holiday time and enjoy and see you in the new year. Thanks, Martin. Merry Christmas, everyone. Bye-bye. Thanks, bye. Thank you very much. Bye-bye. Happy new year.


I'm happy to be with you today. And before these awards and before we present them, I want to recognize one person. He's not getting an award today, but without him, the Navy would not be where we are on energy. And we wouldn't be winning the types of awards that we have. The Navy, the Department of the Navy, is one more presidential awards and Federal Energy Management Program awards over the last dozen years than any other agency or military service. And one of the main reasons for that is Bill Taylor. I was visiting with him on the way in just briefly. He and I came to the Navy about the same time. I was commissioned in 1969. He came into the Navy in 1971. He has had more perseverance than I did. I had a little gap in service from 72 to 09. Bill has stuck with it for 42 years. And he's retiring on November the 2nd. And he's had a major impact on a lot of things that the Navy has done, including as early as the late 80s the geothermal plant at China Lake. So Bill was for alternative energy before alternative energy was cool or hot or in the public consciousness. I often say that the Navy has led in changing energy use from sail to coal, from coal to oil, and pioneered the use of nuclear. I think the rumors that Bill was around for each one of those transitions are probably untrue. But I do want to thank him for all his years of service for the great contributions that he's made, wishing fair winds and following seas, and say that even though your retirement is well earned, you will be sorely missed. So come up here and I'll give Bill a hand. I'm happy to take part in today's ceremony because beside just being an acknowledgment of the excellent work being carried out across the Department of the Navy, these awards demonstrate the progress we've made in the last three and a half years to change the way we think about, we produce, and we use energy. Almost exactly three years ago, I proposed some very ambitious energy goals to improve our navies, our Marine Corps, and our nation's energy security. And when I see the dedication, the commitment that's been demonstrated by the award winners today and by a whole lot more people across the Department of the Navy, I'm confident, absolutely confident that we're going to reach all these goals, including the most comprehensive that by no later than 2020, at least half of all energy, both a float and a shore, will come from non-fossil fuel sources. 50 years ago, over 50 years ago, President John Kennedy stood before a joint session of Congress and announced a plan to put a man on the moon before the end of that decade. That was a great plan. But when he announced it, nobody had any idea of how to get it done. There were no systems in place. We didn't have the rockets. We didn't have the vehicles, the landers. We had nothing. But that's why he did it. And a year later, at Rice University, he said, and I'm quoting, we chose to go to the moon in this decade, not because it is easy, but because it is hard, because that challenge is one we are willing to accept, one we are unwilling to postpone, and one which we intend to win. And we all know how that worked out. 1969, Neil Armstrong was the first human to set foot on the moon within the decade that President Kennedy had laid out as a go. And I think that the energy goals and beliefs are similar in a lot of ways to that goal of a half century ago. US Navy and US Marine Corps pursuing alternative energy and energy efficiency, not because it's easy, not because it's green, not even because it's good for the environment, although those are good side effects. Why we do it is to be a more effective military force, better able to accomplish the mission that the nation gives us. And we're going to achieve these goals. And to paraphrase President Kennedy, we're unwilling to postpone those goals, and we intend to win. And you know the volatility and the fragility of the global energy market and the economic and security ramifications that has for the United States from being over-reliant on foreign sources of fossil fuels or vulnerabilities that we have to address now. We are decreasing the amount of foreign fossil fuels that we use. In fact, we're to the lowest level in a couple of decades in terms of importing oil. We're a million barrels a day lower this year than we were last year. But even if we could produce all our oil domestically, oil is still the global commodity, and it's traded based on speculation and rumor a lot of times. So the price spikes, the other vulnerabilities, the fact that we still buy oil from countries that may not have our best interests at heart of vulnerabilities that we have to fight every day by taking bold steps to make sure that we reach these goals. And those sorts of bold steps have been taken by the award winners here today. And I'm going to mention a couple of them just as examples. All the award winners today have richly earned it. And the several that I'm going to mention have as well joint-based Pearl Harbor Hickam in Hawaii. They're being honored today for converting alternative energy into many megawatts of usable power, harness the strength of the island with thermal, ocean thermal, and with wave energy, harness the Hawaii and sun with solar energy and solar photovoltaic power. When it's being constructed, it's going to produce 10 megawatts of energy. Now, Hawaii has a special reason to do this because it's the state most dependent on imported oil. And for that reason, energy costs there in the country. And it's got a big military presence, Navy, Marines, and all the other services. Right now, Hawaii is in a partnership with the US Department of Energy. And it's transforming the state into a model for greater energy independence. And the things that the Navy Marine Corps team are doing there are helping make that model a reality. We talked about price spikes. And if you want to just get some arithmetic into this, for every dollar a barrel of oil goes up in price, it costs the Navy $30 million in additional fuel costs. In 2012, we had an extra fuel bill of half a billion dollars, $500 million, because simply the forecast didn't see how quickly the price of oil is going to rise. Now, there are not many places to go get that money because there's not really any extra money. The only places really to go get it are operations and training. So it means we steam less, we fly less, we train less. And enough to start platforming. Now, those are decisions that neither I nor any secretary wants to make. So there ought to be a different way. And that different way is by using fuels that hopefully will be less prone to these price spikes that will certainly be domestically produced. And we also, in addition to that, have got to be more efficient. Do exactly the same things just use less fuel. And one of our award winners has been a great example of how to do that, USS Macon Island. I've mentioned Macon Island in so many of my speeches. Tom Friedman wrote a column in The New York Times about Macon Island. And I went out. I was supposed to go visit Macon Island last December off the coast of Malaysia, but the weather did not cooperate with us. The captain at the time was an Ole Miss graduate like I am. And evidently, they had a pretty amazing cake that I missed. I did. And those of you who have served in Asia will understand this. I did get to eat durian that day. That's not something you ever want to do. They say, if you get past the awful smell, that the taste is great. Not so much. Anyway, I went to see Macon Island last week in Port in San Diego. They were just back from deployment. Seven-month deployment. We had budgeted $33 million for fuel for the Macon Island during that deployment. They spent $18 million. They saved almost half of the fuel by using a hybrid electric drive at speeds of under 12 knots. Over the lifetime of that ship, at 2010 oil prices, when the ship was launched, it'll save over a quarter of a billion dollars just in fuel costs. And while that's important, one thing I found when I was on Macon Island was the main propulsion, the officer in charge of the main propulsion, was one of the most enthusiastic people I've ever met. And he kept talking about how, beside the hybrid drive, how the whole crew had gotten involved and how third classes would come in and say, I've found a way we can save some energy. I've found a way we can reduce the energy that we're using here or here and how it was almost a competition to see just how far they could go in doing exactly the same missions with exactly the same high standards, with exactly the same proficiency just using less energy and how that had taken hold as a culture on Macon Island just like it has to take hold and it is taking hold across the Navy and Marine Corps as a whole. So beside the big things that we're doing, like putting hybrid drives on big-deck amphibs and now beginning to retrofit them onto our destroyers, it's the little things, like including energy efficiency in the plan of the day or on the 1MC when they get announced. And I also want to talk about some other ships that aren't award winners today, but that participated in RIMPAC this summer and demonstrated the Great Green Fleet. Nimitz was the carrier and the other members of the strike group were Chaffee, Chunghoon, Princeton, Henry J. Kaiser, and carrier Air Wing 11. We bought biofuels, domestically produced biofuels, put them in the logistics chain, got them to the Great Green Fleet, got them to RIMPAC, put it on the oiler, the Henry J. Kaiser, and got it to the ships and the aircraft. Every single type of aircraft that flew off that carrier flew that day on a 50-50 blend of biofuel and avgas, every single ship. The carrier was nuclear, everybody else operating on a 50-50 blend of marine diesel and biofuel. I flew out on a helicopter that operated on a 50-50 blend. The Australians sent over a helicopter and got refueled. We did air-to-air refuelings that day. But I think the most amazing thing is that biofuel in that supply chain, we didn't change a thing. We didn't change a single setting on an engine. We didn't change a single thing in the supply chain. It was absolutely the same way that we would have done, the same amount of oil. The only difference, when I was talking to people in that strike group, the only difference that some of the engineers said they were noticing was, and the Air Force has a study that sort of confirms this, is that biofuels tend to burn cleaner. And so the engines produce a little more power, and there's a little less wear. But other than that, and that's a good thing, other than that, there was absolutely no difference. So at all our Navy and Marine Corps ships and bases, our shore installations from Panama City to Pendleton would be island and Indian island, blunt and Paris island. We're trying to change a culture and promote a culture of energy efficiency and using different kinds of energy. And I want to say a word about our Marine winners here. The first thing you think about when you think about the United States Marines is probably not art and environmentalists. But I have to tell you, the things that they have done in the US, like Camp Pendleton and 29 Palms, where they've invested real heavily in metering equipment so that we know how to monitor and then how to optimize energy use at Paris Island. That is bringing new energy technology from the top in skylights to the bottom and radiant heating in the floors. And it's changed a culture there, too. And it's gone to the battlefield. Over the past three years, I've been to Afghanistan nine times. And on every single trip, I've seen some of the things the Marines are doing, including in some of the heaviest fighting around Sangen. Third battalion, fifth Marines, reduce their overall energy use by 20%, some outposts, reduce their fossil fuel usage by 90%, and two outposts used no fossil fuel during their deployment. We've got the proof that just by doing solar blankets, roll up, put it in your pack, and use them to recharge radios and GPS, that a Marine company can save almost 700 pounds of batteries. So they don't have to carry those 700 pounds of batteries around with them. And they also don't have to be resplied every couple of days with new batteries. And so the Marines have institutionalized this and that they now have ways with the experimental fobs that they do twice a year to find best technology, best practice, and get it out to the fleet. The last three years of these awards have shown incredible success because of the actions of our award winners. We have the same type of goal that America had 50 years ago in the 1960s. We have a goal that we want to achieve before the end of this decade. And we will achieve it because of the courage, the bold action, the innovation that our winners have shown here today for almost 237 years, 237 years next week, and for the Marines 237 years next month. We have projected our power. We have protected our nation. We're on a path to create a new energy future, which will increase the security of this country because that's what the United States Navy and the United States Marine Corps have always done. Innovate, adapt, make the future more secure and the world a better place. Semper Fortis, Semper Fidebs. Thank you.


Presenting Mr. Keen, Tracer of Lost Persons in The Silver Candlestick Murder Case. A new weekly feature on NBC's All-Star Festival of mystery, comedy, music and drama. Ladies and gentlemen, once again we present Mr. Keen, Tracer of Lost Persons, one of the most famous characters of American fiction in one of radio's most thrilling dramas. Tonight the famous old investigator takes from his file and brings to us one of his most celebrated missing persons cases. Tonight's case is entitled The Silver Candlestick Murder. Mr. Keen is presented by Anderson for fast relief from pain of headache, neuritis and neuralgia. And by Dentine, the gum with breathtaking flavor. And Beeman's Pepsin, the gum that's great to chew and good for your digestion too. And by Chesterfield, Chesterfield's are much milder and with an extraordinarily good taste and no unpleasant aftertaste. If you suffer from pains of headaches, neuritis or neuralgia, you should discover what many thousands have known for years that Anderson brings incredibly fast effective relief. Anderson is like a doctor's prescription. That is, Anderson contains not just one, but a combination of medically proven active ingredients in easy to take tablet form. Probably at some time you've received an envelope containing Anderson tablets from your physician or dentist. Thousands of people have been introduced to Anderson this way. Try Anderson yourself. The next time you suffer from the pains of a headache, neuritis or neuralgia, you'll be delighted at how quickly relief can come. Anderson is spelled A-N-A-C-I-N. Your drugist has Anderson in handy boxes of 12 and 30 tablets and economical family size bottles of 50 and 100 for your medicine cabinet. Ask for Anderson today. Now, Mr. Keen, tracer of lost persons in the Silver Candlestick murder case. The scene opens in the dimly lit drawing room of an old mansion on New York's Upper Fifth Avenue. It's about nine o'clock at night and a rather shabbily dressed but handsome young man has been pacing the room. Suddenly, he notices a photograph on the mahogany desk. Quickly, he walks toward it, his face showing stunned bewilderment. Great Scott, it can't be, but it is. Why, this, this photograph, it's fantastic. I've got to get out of here. I was a fool to have come. Oh, oh, I beg your pardon, I didn't see anyone come in. What are you doing with that Silver Candlestick? You struck me. No, no, don't, don't you... Mr. Keen, my name is Mrs. Grace Denning. I need your help most desperately. Please sit down, Mrs. Denning. Make... Yes, boss. Mrs. Denning, this is my partner. Make cleansing. How do you do, ma'am? How do you do? Mr.  And also that you trace people who are missing. Yes. I want you to find my husband. Neil has disappeared. And I'm so terribly frightened. How long has your husband been missing, Mrs. Denning? Only since yesterday, Mr. Keen. But I know something dreadful has happened to him. Neil is an actor, but acting jobs are scarce. So he's been working as a model for artists and photographers to get money. He's very handsome. Well, yesterday, he had a telephone call. Yes. Go on, Mrs. Denning. As I came into the room, I overheard Neil saying, I'm not going through with it. It's too dangerous. Much too dangerous. There was a long pause. And then he said, very well then, I need the money. I'll be there. And he wrote down an address and hung up the receiver. And Mr. Keen, Neil's face was white as a sheet. Mrs. Denning, did you question your husband about the phone call? Oh, yes. But he was very nervous and evasive. He told me he was going out to pose for a photographer and wouldn't be home until late. Mr. Keen, that was almost 24 hours ago. And he hasn't returned. Well, shown that's mighty queer. I mean the phone call he got. Yes, Mr. Clancy. And let me tell the rest of it. I overheard Neil repeat that address where he was going just before he hung up the phone. So this morning I went there. But it isn't an office building or a studio at all. It's a grim looking old mansion. I kept ringing the bell but nobody answered. Oh, Mr. Keen, please help me find Neil. I'm certain he's in dreadful danger or worse. Mrs. Denning, write down your address on this paper and the address your husband repeated on the phone and the place where he apparently went last night. Very well. Oh, Mr. Keen, you will search for Neil, won't you? Yes. But I'm afraid from what you tell me of that phone call that your husband was involved in a dangerous undertaking and possibly feared for his life. Oh, Mr. Keen, you don't think... It's too soon to guess, Mrs. Denning. Now you go home and wait until Mike Clancy and I investigate and try not to worry. Bless you. Goodbye, Mr. Keen and Mr. Clancy. So long, Mrs. Denning. Mike, I recognize this address where Neil Denning is supposed to have gone last evening. You do, boss? Yes. It's the old Tilden mansion, the home of a rich and elderly recluse, Miss Abigail Tilden. Well, sure. And what would Neil Denning have been doing there, boss? I don't know, Mike. And I don't like it. For instance, why didn't anyone answer the door when Neil Denning's wife went there today? Come along. Let's go there and see what we can find out. This is the Tilden mansion, Mike. Would you ring the doorbell, please? Right, boss. Oh, Mr. Keen, I recall now reading about Miss Abigail Tilden. She's from one of those real old society families. Yes, Mike. In fact, I knew her slightly many years ago. Yes? What is it? My name is Keen. And this is my partner, Mike Clancy. Mr. Keen, the famous investigator? Yes. And who are you, young lady? I'm Elise Tilden. Won't you come in? I take it you are related to Miss Abigail Tilden. I'm her niece. Come into the drawing room, Mr. Keen. Mr. Clancy. Thank you. Elise, my dear. Who are these gentlemen? Oh, this is Mr. Keen and Mr. Clancy, Donald. My fiance, Donald Stiles. Mr. Keen, I've heard of you, of course. Is something wrong? Yes, Mr. Stiles. A young actor and artist model, Neil Denning, disappeared last night. His wife has reason to believe he came here to this house. What? I've never even heard of such a man, Mr. Keen. Nor have I. He certainly didn't come here, Mr. Keen. Elise went out for about an hour last evening, but I was here. No one rang the doorbell. You're sure of that, Mr. Stiles? Positive. No one came here last night. I see. Well, thank you very much, Mr. Tilden, Mr. Stiles. Come along, Mike. Yes, boss. I'm sorry we couldn't be of help, Mr. Keen. Goodbye. Well, now, what do you make of that, boss? Sure, maybe Mrs. Denning got the wrong address. Mike, I happen to notice something in that drawing room. A dark stain on the carpet. It may have been a blood stain. A blood stain? Since preservers. Then those two, Miss Tilden and her fiance, were lying to us. Mike, just on a hunch, I think you and I will have a look in the cellar of this old Tilden house. And let's go round to the back and see if there's a door or a window we might get in. Come along, Mike. Keep your flashlight on, Mike. It's pitch dark in this old cellar. This place is more like a dungeon than a cellar, Mr. Keen. Mike, wait. Turn the flashlight over to the left. There, that's it. Well, it looks like a coal bin. Yes, let's look inside. Mike, look here. Mr. Keen, it's the body of a man. Yes. Oh, and his head's been bashed in by something.  Mike, we found the answer to Neil Denning's disappearance. He did come here to the old Tilden mansion last night, and he was brutally murdered. Mr. Keen, do you suppose that... Well, Mike, someone's coming. Switch off the flashlight. Can you see who it is, boss? Mr. Keen! Mr. Keen! I'm all right, Mike, but whoever fired at us is getting away. The flashlight's broken. Boss, whoever it was, went up some steps. Here, Mike, here's the staircase. It must lead into the house. Come on. Now the door, Mike. Hurry. Well, I'm trying to find the door knob. Well, here it is, boss. Well, it looks like we're in the back hallway of the Tilden mansion, Mr. Keen. But there's no sign of the person who shot at us. Come on, down this hall, Mike. Keen, Mr. Clancy. I was up in my Aunt Abigail's room when I thought I heard shots. You did hear shots, Mr. Tilden. Someone fired at Mike and me while we were down in the cellar. You were down in the cellar? And whoever it was came up the cellar stairs and got away through the house. Or he may still be here. Good heavens. Mr. Tilden, where is your fiancee, Donald Stiles? Well, he left the house about five minutes ago. Mr. Keen, surely you don't think Donald tried to kill you? Well, that's fantastic. Mr. Tilden, Mike, Clancy and I have just discovered the murdered body of a young actor, Neil Denning, in a coal bin in the cellar. What? Oh, no. Is he the young man you came here to inquire about? Yes, Mr. Tilden. Where's your telephone? In the study. I'm going to call the police at once. Oh, but Mr. Keen. Yes? Must you call the police? I mean, it's also dreadful and scandalous. Mr. Tilden, you seem to forget that there's a brutal killer at large, a killer who must be caught before he has a chance to murder again. I know, Mr. Keen, but I'm thinking of my aunt Abigail. She'll be horrified and shocked by the scandal. And after all, why should we be involved? None of us ever heard of that man who was murdered. I'm sorry, Mr. Tilden, but you are very much involved. In fact, until this case is solved, everyone in this house is under suspicion of murder. Mr. Keen will return in just a moment in the silver candlestick murder case. But first, now here's something of interest to you. For breathless moments. For your breathless moments. Chew dentine. The gum with breath-taking flavor. Dentine tastes so good. Dentine freshens your breath. Dentine helps keep your teeth sparkling clean and white. Dentine, the gum with breath-taking flavor.  You'll love dentine chewing gum, for dentine has a wonderful, tingling, nippy flavor that lingers on and on. It's delicious. And remember, dentine helps keep your teeth white, too. Keep dentine handy.  So for breathless moments. For your breathless moments. Chew dentine. The gum with breath-taking flavor. Now back to Mr. Keen and the silver candlestick murder case. When Neil Denning, a handsome young actor and artist model, mysteriously disappeared, his attractive young wife, Grace, begged Mr. Keen to try and find him. Mr. Keen and his partner, Mike Clancy, have visited a grim Old Fifth Avenue mansion and questioned Elise Tilden, lease of its owner, eccentric old Miss Abigail Tilden, and Elise's fiancée, Donald Stiles, who both claim never to have heard of Neil Denning. But a short while ago, Mr. Keen and Mike discovered Neil's body in the cellar of the mansion. Now they're approaching the apartment of Neil Denning to break the news to the widow of the murdered man. And Mike is saying, This is Mrs. Denning's apartment, Mr. Keen. It'll be tough to have to tell her her husband has been murdered. Yes, Mike. But it's so great. Mike, listen. So you don't know what you're saying. I won't listen. Boss, that's Grace Denning's voice.  As soon as you realize that and clear out of here, the better. Mr. Denning apparently has a visitor, Mike. Ring the doorbell. Mr. Keen and Mr. Clancy, won't you come in? Um, this is Alan Page, a friend of my husband, Neil. Alan, this is Mr. Keen and Mr. Clancy. How do you do? How do you do? So you claim to be a friend of Neil Denning's, do you, Mr. Page? Well, sure, when we heard you a minute ago, you weren't talking like any friend to his. So you heard me, did you? Very well, Mr. Clancy. I admit it. I was telling Grace it was ridiculous to ask Mr. Keen to find Neil. He hasn't disappeared. He's probably just walked out on her. Alan, don't say anymore. Grace, I told you Neil was no good even before you married him. I thought he'd pull a stunt like this. It happens you are mistaken, Mr. Page. We have just come to tell Mrs. Denning some very shocking news. Mr. Keen, you don't mean... I'm sorry, Mrs. Denning. Your husband has been murdered. Oh. Mike and I found his body about half an hour ago. No. Oh, no. I'm very sorry to bring you this news. Neil, oh, Neil. Grace. Let me alone, Alan. Let me alone. Mr. Keen, this is horrible.  What do you mean by that, Clancy? My partner means, Mr. Page, that if you're in love with Grace Denning, as you obviously seem to be, the police may consider you a strong suspect in Neil Denning's murder. Why, you're insane, Mr. Keen. It's true I'm in love with Grace Denning. And for her sake, I tried to help Neil get back on his feet. He was an actor and out of work most of the time. Why, I even got a job for him. What kind of a job? Yesterday, a man who belongs to the same club I do said he might have work for Neil Denning and asked for his phone number. I assumed it was a modeling job for a photographer. Neil was doing that work as a sideline lately. Mr. Page, who is this man who is so interested in Neil Denning? His name is Stiles, Donald Stiles. Stiles preserves, Mr. Keen, sir. The man at least Tilden is engaged. Yes, Mike. Mr. Page, how well do you know this, uh, Donald Stiles? Only casually, Mr. Keen. He's a well-dressed chap, always seemed to have money. I never knew what business he was in. I see. Well, come along, Mike. We're going. Right, sir. Mr. Keen, at first I thought this fellow Alan Page might have murdered Neil Denning. But now I... Mike, Donald Stiles denied ever having heard of Neil Denning. Now we know he was lying. But why? Sure, and you got me there, Mr. Keen, sir. Mike, I want you to check on Donald Stiles. Find out all you can about him. Right, boss. But what about you, Mr. Keen? I'm going back to the Tilden mansion where Neil Denning was murdered. And pay a call on old Abigail Tilden. You mean the old aunt who never goes out of her room or sees anybody? Yes. But I'll have to insist on seeing her. As soon as you've checked on Donald Stiles, phone me there. And hurry, Mike. Well, Miss Abigail, it's been many years since I've had the pleasure of seeing you. Mr. Keen, I know why you're calling on me now. I know there's been a murder here in my house. I couldn't help but know with police all over the place. Miss Abigail, last evening did you hear anything unusual? No, I did not, Mr. Keen. I never leave my room. My niece went out for a while last night and her fiancé, Donald Stiles, came up here to my room to keep me company. I could have done very well without that young man's company. You don't approve of Donald Stiles? He's a thorough going rascal. Only after release because he knows that she'll inherit all of my fortune now. Now, what do you mean by now, Miss Abigail? I mean now that I've cut Robbie out of my will. And who is Robbie? Why, my nephew, Mr. Keen, and the finest boy who ever lived. He walked out on me five years ago after we quarreled. He disappeared. That's Robbie's picture there on the table. Oh, yes. Yes. I raised Robbie and Elise, their cousins. But Robbie, my nephew, was my favourite until he left this house. I have no idea where he is, and after all I did for him. That phone call may be for me, Miss Abigail. You can take it on the extension in the hall, Mr. Keen. Thank you. Will you excuse me, please? Hello? Mr. Keen, this is Mike Clancy. Yes, Mike. Well, boss, I've checked on Donald Stiles. He's no good. He owes $10,000 to an underworld character named Job Parish, who owns a nightclub where Stiles throws expensive champagne parties. Yes, go on, Mike. Well, Donald Stiles got engaged to Miss Elise Tilden about three months ago, and the talk's gone around that he's after the rich old aunt's money. I've just been talking to the aunt, Miss Abigail Tilden. And, Mike, I've discovered something. You want me to come over there, boss? Yes, Mike. Get over here to the old Tilden mansion right away. Well, Mr. Keen, I didn't know you'd come back. Oh, Mr. Stiles. Have you found any clue to that young man, Neil Denning's murder? Yes. I suggest you and I go into the sitting room here and talk. Certainly. It's a shocking thing you're finding his body in the cellar of this house. I suppose someone must have murdered him last night out on the street and dragged his body into the cellar to hide it. Mr. Stiles, you can stop lying. What?  Why, Mr. Keen? A few minutes ago, in Miss Abigail Tilden's room, I saw a photograph of her nephew, Robbie, who left home five years ago after a quarrel with his aunt. That photograph bears a startling resemblance to the murdered man Neil Denning. Mr. Stiles, I'm convinced that you were planning a fraud of some kind. A fraud which involved the missing nephew, Robbie, and Neil Denning, the actor who looked just like him. And when Neil Denning discovered it, did you murder him to keep him quiet? No. No.  I'll tell you everything. It's true I did hire Neil Denning to come here last night. I owe a certain big nightclub owner a good deal of money. I was afraid my fiancée, Elise Tilden, would find out and break our engagement. So I had to get money fast. Go on, Mr. Stiles. I knew about Elise's cousin, Robbie, who'd left home five years ago. When I happened to see the actor, Neil Denning's picture in a magazine advertisement, I was struck with an idea. I think I know the rest, Mr. Stiles. You engaged Neil Denning, who was an actor, to impersonate the missing nephew, Robbie. Yes, Mr. Keen. You see, Abigail Tilden is a very old lady. Her eyesight is poor and her mind wanders sometimes. I was sure Neil Denning could fool her into thinking he was her missing nephew, Robbie. And then what was he to do? Neil Denning impersonating Robbie was to say that he'd returned home but that he needed $20,000 right away. I hoped old Miss Abigail would give him the money. Then Neil Denning and I would split. A very daring scheme, Mr. Stiles. I knew my fiancée, Elise Tilden, would be out last evening.  But when I went down to get him, he was gone, Mr. Keen. He disappeared. Donald? Oh, Elise. Oh, fine, Mr. Keen. You're here. Yes, Miss Tilden. I was about to tell your fiancée, Donald Stiles, that I now have proof as to who murdered that young man, Neil Denning. You see, I have in my possession the weapon that was used to kill him. You have the murder weapon, Mr. Keen? Yes, Miss Tilden. And there are fingerprints on it which will establish the murderer's identity beyond doubt. I intend to turn it over to the police right away. Oh, no, you don't, Mr. Keen. Stand where you are. Release that gun! Yes, Donald, I have a gun. Mr. Keen, you're going to hand that silver candlestick over to me.  I'm glad to know that, Elise Tilden, because now I can search this house for it. Then you didn't have the candlestick at all. You tricked me, Keen. Yes, it was a trick, and it worked. All right. I admit I killed that man, Neil Denning, but I did it for you, Donald. Elise, you're crazy. Go on, Elise. You may as well confess. I came home early last night. I walked into the drawing room and saw that man, Neil Denning, standing there in the dim light. I thought it was my cousin, Robbie, come home after all these years. I was frantic. I knew Robbie would win Aunt Abigail over to him again. He was always her favorite. She'd leave all her money to him, and I'd lose everything.  Elise, Elise, how could you?  I know you don't really love me. You'd leave me if I didn't inherit Aunt Abigail's fortune. And so in a moment of panic, Miss Tilden, you murdered the man you thought might take that fortune from you. When I thought it wasn't my cousin, Robbie, but a stranger was too late, Mr. King. So I dragged his body to the cellar, trying to hide it. And that gun in your hand is the same gun you fired at Mike Clancy and me when we were in the cellar. I suspected it when we came upstairs, and I noticed a smudge of cold dust on your dress. But I needed proof. You won't do you any good. I've killed once and I'll do it again. Oh, no, you don't, young lady. Now give me that gun. Let go of me. There, I've got the gun now, Mr. King, sir. And this lady won't be causing any more trouble. You got here just in time, Mike. Donald Stiles here is guilty of attempted fraud, an evil crime to be sure. But it's Elise Tilden who will pay the supreme penalty for the murder of Neil Denney. And so Mr. King finds the solution to the silver candlestick murder case. The mask is off. The mask is off in cigarette advertising. Chesterfield is first to name all of its ingredients, and here they are. Chesterfield uses the right combination of the world's best tobaccos, pretested by laboratory instruments for the most desirable smoking qualities, and kept tasty and fresh by the only tried and tested moistening agents proved by over 40 years of continuous use in USA tobacco products as entirely safe for use in the mouth. Pure natural sugars and chemically pure, harmless and far more costly glycerol, nothing else. And remember this, Chesterfields are wrapped in pure white cigarette paper, the best that money can buy. You can be glad if you smoke Chesterfields because they give you every advantage known to modern science. For you that means that Chesterfields are much milder with an extraordinarily good taste and no unpleasant aftertaste. All for your smoking pleasure and protection. So sound off for Chesterfields and do it today. Listen again next week to Mr. King, Tracer of Lost Persons, a new weekly feature on NBC's All-Star Festival of mystery, comedy, music and drama brought to you by Anison for a fast relief from pain of headache, neuritis and neuralgia. And by Denteen, the gum with breathtaking flavor and Beeman's pepsin, the gum that's great to chew and good for your digestion too. And by Chesterfields. Remember, Chesterfields are much milder with an extraordinarily good taste. And from the report of a well-known research organization, Chesterfields leave no unpleasant aftertaste. Mr. King, Tracer of Lost Persons is based on the novel Mr. King. The radio sequel is originated and produced by Frank and Ann Hummert. Dialogue by Gene Carroll, directed by Richard Leonard. Philip Clark plays Mr. King. Your announcer, Jack Costello. Remember, Mr. King is on the air at this same time every Thursday at 8.30 Eastern Standard Time. Don't miss Mr. King next Thursday when the kindly old Tracer turns to The House on the Cliff murder case. Dragnet Authentic Adventure is next on NBC.


Everybody force and shake it ripping 2023 inception in chrome black baseball eight box mixture number eight random teams. Good luck on the random Then we'll rip Six and one seven times they can't get us off. We all don't pay our bills. All right names first seven times One two three four five six and seven Scott f down to potion and Seven times here on the teams Hello, New England Patriots Torrey Holt. Hello Torrey Holt one you're a bot Two three four five six and seven Brewers down to A's Chrome dust attacks back specifically my right eye Yeah, Scott F with the Brewers potion with the Giants Nick P fillies Ryan B Rangers Vaughn with the Rockies Jerry F White Sox Nico with the Braves Richard L diamond max Jerry F. Guardian sander K Royals Nico R twins Corey G Padres Richard L reds in MQ with the Nationals Eric J Ray's Vaughn B met steric L blue J's Ryan K red Sox Dave E Cubs Brandon L angels George M and Mariners Joseph S Yankees Christopher D Orioles James M Pirates John W Dodgers lead W Marlins Nick P Astros Tom J Tigers Robert C Carlson potion with the A's This is Comedy of errors. Oh, dude Yeah, should we just ban that account from Sam and see how many emails he's willing to create just to make a burner account So I'm surprised Sam didn't make a 10 pay buck in the air is Trent Delfar Honestly pretty disappointed in that. I'll strive getting another Yeah, the promo is pretty damn good for the post season one two hundred nine insane boxes in that one Appreciate you strive Guys we got to get one-on-one filled everything else looking pretty darn solid one-on-one. We got to get filled That's what I'm saying Jake I'm saying Got 2020 flawless. Is it crazy to say that we want the Packers of the break in the 2020 fall? Is it crazy to say that? Want to chase Jordan lover rather than I this current point time? It's not crazy to say that Realistically if you had the Finns Eagles Packers Chargers bangles you'd be happy with any of those QB's in the box to be fair to be fair and in a random team break Green O'Neill Cruz. That's to 99 rookie Gabriel Moreno for the Diamondbacks. That's In here come though and a green rookie Otto Davis Martin to 125 for the White Sox Passing too much dust. Yeah, it'll be frozen like any reason must ash last night Pull one of those inception books Plain and Kyle pulls them I didn't get to oh, we got a redemption in this one Yeah redemption coming up y'all Well grissom green to Valdez for the Red Sox green gunner Orioles Astoria Ruiz Redemption is an Anthony Volpe based rookie and emerging star autograph Yanks. Nice good stuff for the Yankees Congrats on that one And another hit rookie auto patch or not rookie auto patch. Sorry. Just auto patch of Elliot Ramos the 149 Giants I'll take two hits one being a full bag for sure. Well, they can score with you. Can't stop the passes green Abrams Followed by a Austin Riley is 16 to 50 for the Braves New England Joey Galloway. What a legend. That is a Josh young rookie jumbo patch out of the 125, Texas Coolhead Rangers Nice that guy is good at baseball. That's a nice one for Ryan B Good inception here. What about New England Patriots Reggie Wayne? How many yards is a Jones have now? I don't know Don't know Margo green Parazza rookie Yanks green Goldie Zavolasquez and a rookie auto for the Guardians bow nailer at 249 Into the chrome black. This is crazy Burns that is to one ninety nine refractor Francisco Dendorf Lee Lee Mets and of course eager and then a rookie auto for the Pirates Kenan Smith and Jigba That guy's wide open Who was that? What just happened there? What just happened there? Man, that was like a high school blown coverage right there. Shea Langley is green the 99 Aaron judge I was going Scotty It's up Scott so far rookie You as well man next is a rookie autos. You're our and cannot see on for the Marlins you as well I don't mean Bruce. He'll be all the famer. He's definitely a Patriots Hall of Famer One of the best players in the franchise history, but I'm these all the famer will fork I don't think so either. It's so hard for those tackles to get in you really have to be like like an Air Donald type interior defensive linemen to make the Hall of Fame Purple mini diamond or key to 150 morale for the Cubs hard to quantify like their value Do I seen Jerry Jones upset? I Don't hate cowboys, but I don't like Jerry Jones purple mini diamond to 150 morale for the Cubs Next is a green wave the 99 a Bieber for the Guardians Impeccably dressed. I am wearing a late sports cards 2023 national t-shirts. I am doing that right now And I'm wearing some Adidas Athletic shorts as well as some rundown Vans black classics It's like a $30 outfit It go a lot of the 50 for the Dodgers Steve Garvey It works though Steve Garvey fire. I Do like to wear all black a lot Yeah, Mike not good Probably should just trade Michael Parsons doing to New England and CD Blue lava to 75 Pete Alonzo for the Mets Pete Alonzo People are gonna blame Dak and yeah, it's definitely part of Dak's fault But the defense has not gotten like a slight gotten more than one stop today So there were net there was no University. They're winning this game apparently and a full Bay rookie refractor out of the 150 Yankees to Volpe's in a multi Multi-products mixer here. Nice. It's a mixture by definition only price redundant right there Yankees Congrats to Joseph s I'll do it for the break. Thanks. Get it running moving on now to some more baseball


Shell thickness is the last measurement in the 4-H golden egg contest. Egg shell thickness can be influenced by a hen's age, how long she has been laying eggs, and her diet. Egg shells from the broken out eggs are carefully washed out so no egg material remains. The washed eggshells are dried overnight. When clean and dry, the shells are measured at a randomly selected location along the middle or equator of the egg. A pocket micrometer is used to measure the shell thickness. All three eggs will be measured. The number is written on the score sheet and the average of the three measurements is calculated. If the average is over 0.35mm, 20 points are awarded. Those are strong eggshells, sure to get your product to market. Egg shell thickness between 0.34 and 0.31mm receive 10 points while shells less than 0.30mm receive 5 points. Lower shell thicknesses likely indicate that it is time for the flock to molt in order to have stronger eggshells in their next laying cycle.