So, I will summarise some of the work in the later further assembly of either the fire station in Saturday, and what the site might be able to reveal about human activity there and in the wider legislature landscape. And from the start I should stress that this is a collaborative project, and it is still in progress, and many of the results are preliminary and unprobliwtional. The site was discovered in 2013 during valuation work by Oxford Archaeology in advance of the building of the new fire station at Guildford. The archaeological horizon is just below the present landscape as you can see there. The site is not previously known and the discovery could not have been predicted. Once it was found, Oxford Archaeology contacted Nick for an expert advice and they ensured that there was an upper valley of experts working on the site and you probably recognise Will Mills in many of the photos. Guildford Fire Station is a good example of where the planning process was worked well regarding these rare sites. In this case, Surrey County Council was both the planning authority and the developer and they quickly recognised the rarity and importance of the site. It was probably their support that ensured that time was on average for excavation and they've also been very supportive of the post excavation work. Just to put you in context, a quick look at Google Maps at the top, you can see what made this work. There's the old fire station, there's the site just before excavation. Skip ahead five years to June Bishop and you'll see the new fire station. I think this reminds me of what Gareth said earlier about the difficulty of stripping back modern developments to try and imagine the hunt together. If we pull back and Google over a little bit, you can see that the site lies very near to the present valley floor close to the riverway. There's the fire station. Today, the fire station is probably no more than a few hundred metres from the present river. I'm taking an even wider view here, looking at the geomorphology of the area. Guildford is right there. It's where the Red Circle is. It's a city on the way, which is a major tributary of the Thames. It runs north towards the Thames and cuts through north-downs. North-downs being the major rig of chalk hills in south-east England. The riverway cuts through there with one of these gaps that's been defined by the geomorphology of the area. If we look at this topographic map, prepared by Oxford Archaeology, shows the landscape around the site and the site's relationship to the way river system as it flows downstream. Here's this little gap right there. It's an excellent location for hunter-gatherers activity for all sorts of reasons. That little gap provides that erosion area, provides a good source of hemp raw material. It's a good hunting location. Perhaps somewhere in the area there's going to be a forward, as the main velocity itself indicates. These are a couple of images of the excavation progress to show you what the site looked like during the excavations. The flint artefacts are very well preserved and most are uncatenated. It was recognised at the time that microwear might be a possibility, and the artefacts were all bagged, unwashed, and many were retained there, here in the sediments. There is another little scatter here that I'm going to include to call. It was also obvious from the start that refitting was a very good possibility. The archaeological finds for Isam lies in a sequence of medium to iron-grained sands that overlaid coarse-banded flint-plot cobbles, graded chalk and sandstone. It's worth noting that both the solid-flection crosses that underlie this sequence and the sands above form traceable units that can be followed over a wider area. It will be perhaps possible in the future to trace these levels to perhaps predict the location of other similar sites. This is Oxford Archaeology's stratigraphic cross-section through the site of Cossack's G2 sands containing the artefacts there. Preliminary results from optically stimulated luminescent stating of these sands has produced a really tight group of ages in the early middle phase of the Windermere interstudio, so around 13,000 years ago. First, the first stage in many things analysis is a classification and a sandwich composition which was done by Nick and Michael and myself not long after the end of the excavation. There are over 15,000 objects in the cattle and of these about five and a half thousand were recovered during the excavation and most of them have three-dimensional ornaments. The rest were results from processing of the environmental samples, mostly under two centimetres, and they are a refit from that five ways. Most of the stages of manufacture can be found in the assembly and even indicate in their very tiny micro-devils. A total of the Oxford Archaeology of some of the 120-plus re-touched floors, many of them are near as many as London and Alistair Bradley, which is probably a different source of the site. In this case, the furans depicted here are very well-made blades. It's worth mentioning here that some of these blades were made by the service of the soft hammer technique, the very low repair box, and a lot of them do have one in their own technique. Next step was the micro-vary analysis, which was undertaken by our colleague Sonia Tomaso of the Asia University, and she's very kindly allowed us to present some furan published results. Sonia came to Oxford and she screened the entire assemblage microscopically, identified about 600 pieces of the potential use square traces. Of these, a sample of 337 artefacts was selected to be transported to the edge for more detailed microscopic analysis of trace-well lab. Trace-well lab also has a very expensive experimental archaeology programme, and so there she had reference to the experimental reference collection of about 3,000 tools. These are the aims of the micro-vary analysis to evaluate the surface condition of the flinus, to identify the types of use square and to see what they can tell us about reconstructing human activities at the site. Unfortunately, many of the artefacts turned out to have been affected by surface alterations that could not be seen by the naked eye, and this is probably due to movement in the sandy deposits, and so they couldn't be included in the study. However, she did get her positive result for about 80 artefacts. So a quick summary for some of the findings. The site does contain hunting projectiles, bats and retouch bladlets, which showed damage and use square traces typical of shock barrel heads. Here you see those linear impact traces caused by detached flin particles, scratching against the surface at the moment of impact. And here you've got some of those impact fractures themselves. And it's perhaps worth mentioning here too that most of the apthes is most of the points at Guildford are broken. It's perhaps what they're doing on the site is re-tooling. Although we've had to list the reasons why it came up there over the last five months. But evidence for other manufacturing activity she found there on the scrapers, where the use work would be attributed to various stages of processing many dry hides. This includes the heavy edge around the associated bits, scraping dry animal hides on on the bottom two pictures. On this perforator, she found a stiff lateral edge damage associated with microscopic friction polish that indicates possible and poor bone working activity. The elements are most frequent occurring to along the site. On this one, she's been finding wear traces that indicate use of grooving and percussion on hard material. G-val or jiffins is a striker light, where the heavily rubbed end has rounded in deep striations characteristic of percussion against an iron ritual property by writers. It was only when the micrograph analysis was finished that the refitting could stop. They wanted to reduce the handling of this material until the analysis was finished. This work has been taken in place at the Ashmolean Market Museum, I was out there with my partner. I should say also that the work was financed by both the refitting and the micrograph at Historic England. The need for this work could not have been predicted at the site before the site was found. The refitting had very specific aims and project design, and the work is now at final stages. So far, we've got over 500 refits and 50 refit groups. I won't go through these individually, but with the first one, the site which was asking, is the site of Palam Sestil occupied only once? The answer is that it does seem to be a marginal site when referring to post-depositional disturbance. The second one, the chain ferritoire, and should allow comparisons with other sites in the UK and Europe. The more detailed look at the manufacturer of tools on the site. Here, the use and reshot made of the tools seems to be very localised, but the relationship of the tools to the napgim sequence is still a bit unclear, and the rest is still in progress, and hopefully we'll be able to report that in future. This is a scattered plot produced by archaeology of all the material found on the site. The density plot does indicate that there are too many clusters of the flint artefact. The northern part of the site and the southern part of the site. They do seem to be discrete episodes of napping, and there are a few and more many refits between the two groups. In addition, some of the squares slightly outside of those fence areas contain concentrations of core rejuvenation flames, suggesting that individual napping events are also likely to be very localised within the sites. I've got a couple of pictures of some of the refits. These are by Ian Hartrides at the Institute of Archaeology, and a work on the photography of the sites again has just really just begun. This particular refit for appear is typical of several on the site, in that it represents early stages of core preparation. There's a similar style of napping in most of these cases, especially regarding the initial stages of the cores, the extra-cresting, and then the consistent rejuvenation of platforms and flaking faces throughout the process. A lot of the cobbles, they seem to be derived from the chalk, perhaps from not very far away. In these stages, although there is a little bit of hard hammer, most of the napping sequences is soft hammer. As I said before, some have been soft hammer from very long, well-made periods. This refit group perhaps shows the most visible evidence that there are things missing in the order sequence. What you have here is a very large crested blade from those preliminary stages of manufacture. We've also got little worked-out core, there's quite a lot of the core materials in place, lots of gaps. On this miscore special and many others, what seems to be happening is they're setting up these cores for making large blades, but the blades aren't there. There are some to long, curved, well-made blades at the site, and lots of them are useful tools. The rest of these sequences are just not present on the site. Oh, it's possible that they're there. I'd like to make two types of sites. Of course, we could have missed them, but I think it's highly likely that these are collected and exported off the site by the windings. Most of the flint is very high quality, derived from chalk, but the more occasionally other materials use, this particular core here is made on a river cobble, probably from the grantile's ability to weigh, not far away from the site. It's not quite as well-mapped as the other examples, but it is well-integrated with main scatter on, but it's hard to see it when you're intrusive. Of course, as well as the napkin with the groups, we do have some of the tools on the site, but also what we've looked into that they use is a review of what the grant is. Other tools found on the site are broken, as I mentioned before. Refitting can certainly help understanding what happens within a site, but this meeting is supposed to be about the landscape purpose, so I'm returning to this view here. To remind ourselves of the landscape setting of the site, just north, there's a fire station, just north of this gap here, in the Chawbysgafnys, this is probably the source of most of the flint or material you would to the site. Paul, I know you have a look at the flint raw material from way down the farm, but I don't think you have very definitive answers what it might be for. Did you look at the northbound? I'm asking that because if you follow about 17km down the way valley, you'll find that's where main waymanna farm is. It's another major up-and-coming site that we've heard about in passing from England and so on times today. The distance is probably less than a day in Germany. I don't think it's unreasonable to start thinking about these sites and how they might work in the landscape together and indeed if they were connected to each other in any way. There's quite a bit to note here that in London's report, many observations of the two assemblages there are very distinct similarities between the two sites. Two assemblages are similar. Waymanna farm, as you've heard, is reported as having a significant number of well-made blades brought into the site in a low proportion of the initial stages of poor preparation, almost a complement of Guildford. Not flying the kite and saying that they're going to be three bits of tea in the two sites, but we'll have to start on from about a half minute where the guilt that might be an extraction site taking things to the right side by waymanna farm. So just to conclude, a couple of key points. Lough of fire station is an example of a well-preserved upper power of the open air sites surviving the chance found in the present land surface. Re-fitting shelves and assemblages for modules with no major disturbances. It also shows that flint material was probably being acquired near vicinity and was being worked to produce blades and that some of those blades were probably being exported. My provider however shows the rights of other activities that are going on at the site and there's a high potential for looking at similar sites in the same river catchment. Guildford highest vision should not be seen in isolation. And just to end up, I'd like to thank all of the people in the organisation's working on project and deeply apologise to anyone who might have left off the list.


All dielectric nanostructures have been shown to provide enhanced optical forces compared to traditional metallic structures. This study examines three types of resonance structures toroidal dipoles, TDs, anapoles, and quasi-bound states and continuum, quasi-BICS. The TDs were found to generate the highest optical force, while the quasi-BICS produced the largest contrast between the optical forces. The high contrast was attributed to the higher electromagnetic field enhancement provided by the quasi-BICS resonance. Low power laser sources were used to ensure efficient trapping without causing any harmful heating effects. This article was authored by Guangdong Wang and Zhang Hua Han.


All right, thanks everybody for coming. My name is John White. I'm the VP of Product Strategy at Expedient. And today I'm going to talk about building and operating a Swift S3 environment as a service provider. So to give you some context about who we are, Expedient is a service provider focused on cloud co-location and managed services. We operate our locations in seven different markets. We have a pretty big and heavy focus on network. That was where our background actually came from. So we actually have all of our data centers interconnected with 10 gig low latency fiber. We have cloud direct connects to AWS, Azure. So we sit in Equinex Pops that we can connect to pretty much anybody. And then we have a lot of public internet access coming into our data centers. The one important thing to note here is who we service and who our customers are. So we roll up and aggregate IT services for a lot of different companies. And they're focused on enterprise applications and enterprise architecture. So why that's important? Majority of these shops are actually on the pet side of the pets versus cattle analogy. So they're the ones that are actually building maybe 5 to 50 VMs that powers their whole environment, whether they're a software as a service company or they have some sort of maybe they're hosting health care, traditional IT applications, whatever it might be. Now these customers started coming to us and had a demand for object storage because we also had a demand for object storage inside of Expedient as well. One of the things that they came and asked for, and this might be something you hear inside of your world, is focused on archive data. They didn't want to actually put it to tape anymore. They wanted to have it online and running in disk. They wanted to have a lot more information about that data though. So they needed more enhanced metadata to actually figure out what they're doing with that data, how long they need to keep it, why they're keeping it, whether it's compliance or they just were afraid to delete it. They also wanted central file repositories. So a lot of people were running multiple web servers. They needed a place to put their PDFs, their video files, something like that. They needed a single point that they could then scale out their web servers as they were starting to move towards, a little bit more towards the cattle side of things. A lot of people just wanted to migrate a file server. They had terabytes sitting in file servers. They just wanted a place for it to go. They wanted that file server access still from it and they just needed to archive it that way. And a lot of people were asking for API interactions and they were asking for API interactions not really to program against but to then use traditional software that they had today and have it as an S3 repository. So a lot of people were running Commvault Veeam. They wanted to quickly extend that data store to from that application into an S3 object storage. On the expedient side, we saw this as an opportunity to go and roll out something with a programmable storage layer. We didn't want a lot of people to actually run and operate this. As we were going from gigabytes to terabytes to petabytes and our whole kind of evolution, we wanted to make sure there was something as it scales. We didn't really have to scale the people one to one. We could have a few people run this big platform. So what we created is what we call Evermore. And Evermore is just an object storage that's focused on being distributed, redundant and geographic diverse. The goal for this project was to keep it very, very low cost. So it was more for archive data. That's where we were focused on. So we wanted to have a lot of data available to either access via API or NAS gateway and then just to store that large amount of data. So what does it look like? Because I told you I'd give you the architecture. This is really what the product looks like. And these are all built out in three different markets. So you can see in Indianapolis, Cleveland and Boston, the user will actually come through multiple different protocols. So they can use S3, they can use Swift, they can hit it from their website to just store files that way. And they can also use it via SIFS-NFS. That's coming into evermore.expedient.com and that's something that's globally server load balanced. So it's gonna hit any one of those three markets to actually put the data or then go and get the data. So when you're actually going and doing the put of the data into the system, it's gonna land in Indianapolis, Cleveland or Boston. Once it lands inside of there, that whole file we're replicating across that 10 gig ring I mentioned across to those other sites. So what does this actually look like? In each one of these data centers, we design these pods, these object storage pods. And it's pretty simple. We're running Swift stack as our software. We're running a controller server and that controls a lot of the metadata. We have a proxy server in each one of these. Obviously we need some network switching. So we have dedicated switching to the stack. We have a storage server and a storage J-Bot and I'll go through each of these in detail. So the VM is pretty basic. It's actually gonna hold all of the understanding of what is inside of the metadata for all your objects. It's a basic VM. We actually have it just running inside of our hosted VM infrastructure inside of Expedient. Proxy server is pretty simple. It's a Dell PowerEdge R730 and all these slides will be up on YouTube so you can get all the specs of it. But it's a pretty basic server. We don't even back it up because it's something that if it breaks, we just go and we put another one in there, blast an image on it, we get it up and running. Storage server detail and this is where some of the magic starts to happen. Again, another basic R730. This is actually gonna process all the objects down to the disk. And then on the back end, we have just a big J-Bot. It's an MD3060E so there's 60 drives inside of here, four terabyte drives, near line SATA drives, near line SAS drives.  It really doesn't do much as the storage server above it actually handles all of the right requests and the re-request down to it. So the goal here was to go cheap and deep with this storage environment. The one thing that we really focused on when designing this and we balanced it out across a lot of different ways to do it because you can build this thing out a lot of different ways using regular servers and just filling it up with drives or going the J-Bot way. We focused a lot on the watts per gig. We wanted this to be very, very cheap and deep for our customers. We wanted this something to be cost effective to compete against some of the bigger players out there.  So we have a Juniper switch inside of the rack, non-redundant for the time being because there's multiple sites here. So why would I wanna do this? Why would you wanna do this? Why would anybody wanna do this?  Now, so I've created a little bit of a cost kind of breakdown here from the other big three providers that are out there and it's kind of hard to do. If you've ever done cost analysis on an object storage, you have to fill in a lot of stuff. And so I made some educated guests on get put requests, transfer out, that kind of deal. But if you take a look at really just that total solution cost number, so we sell this out to our customers at five cents a gig. So it's 500 bucks a month to run this and it's in a multi-site fashion. Same goes with Azure and Google. And Azure and Google orders of magnitude larger than expedient. We're only about $120 off a month. So if you're thinking about doing this inside of your environment, inside the enterprise, obviously it costs less than five cents to run this. We're a service provider, so we have to try to make some money somewhere. So you could actually do this inside of your own enterprise for actually cheaper than what you're seeing here. So there is a whole reason to have it local, but there's also some cost benefits here. Now I said I was gonna talk about the architecture as well as the operations running this. Really, operations is pretty easy on this. Swift Stack, definitely the software makes it easy. The hardware just kind of runs. It is in three different sites, so it's pretty easy to have change windows really any time of day because you always have two sites available if you take one down, which is nice. But we did learn some lessons along the way. We've been running this for about two and a half years now. We actually built this out initially using one gig network. Definitely build 10 gig networks now. It's a lot cheaper than when we were building it, but it also allows you to scale your environment to start using a racial coding, which is definitely a little bit more heavier on the network side. Create some tiers of disk. Your consumers will all say yes, they want cheap and deep, but I guarantee you then they're gonna come with you with another use case where they want some faster disk. We learned this lesson. So create some tiers to create the ability to handle a lot of different workloads. Using an API for storage is a lot easier said than done. A lot of people wanted this. A lot of people needed this. A lot of people demanded this. They had problems actually programming their applications to use the storage layer as an API. So what do they do? They start to use it as a file server. And this is something where I don't think object storage really lasts a long time as a file server. There's some parts about it that don't really work that well, that don't scale that well. The object storage is meant to be object storage, so that's what you should use it as. So if they want to use it as a file serve, make sure that's a short term solution and not a long term solution. So what can you do? There's a lot of free books that are out there. I read a lot when we were actually building this environment a few years ago.  I put one, I'll link over in here too to an IBM book that's pretty good. And then play with it. There's a lot of different ways you can play with object storage today. A lot of community editions out there. Swiftstack has one, Nuba has one that's pretty cool.  So that's all I got for my 10 minutes of quick lightning talk here, appreciate the time. If you have any questions, love to keep it going after this or feel free to hit me up on Twitter, LinkedIn, email, whatever, glad to answer any questions you might have and help you along your way. Thank you.


Hello everybody, welcome back to another AI video. In this one, we're at ChatGPT4. I'm going to show you how to convert a GIF or a GIF into an MP4 using only ChatGPT, no other programs. This is pretty wild, I'm not going to lie. And again, we're going to show you how to do it. Now the first thing you need to do is you have to have a ChatGPT4 option. So I think that's like $20 a month or something like that. It currently doesn't work with the free version, I don't think. And then on the left side, you'll need to actually enable, if you hover over here, you'll see Code Interpreter. This is being rolled out this week, so I'm going to show you how to enable it. So head over here to the bottom left here, you'll see under your name. And then there's the three dots for the ellipses. Just click on that. Go to Settings, and then under Beta Features, make sure that Code Interpreter is turned on, just like that. So make sure it's in the green. Again, if you do not see Code Interpreter, it will be launched in the next few days.  And it should be out within the next few days. So there you go. Now, the next step is, let me show you the GIF or GIF that I'm going to go with. So I've got this one here. I love this GIF. This is a lady trying to feed a Rottweiler broccoli, and the dog don't want nothing to do with that. So that's a cool GIF. And if you look at the bar up here, it says .gif. Let's make it MP4. Here we go. So I'm going to just close that. Going to show you how to do it. The first thing, as I'm just going to go ahead and copy and paste in a prompt. It says, I'll upload a GIF or GIF, and you give me a three second MP4 with the dramatic slow zoom in no talk, just go. All right, so let's just get right down to it, no foreplay. And then I'm going to click on send message. So I'm basically telling chat GPT, this is what I want to do. You can make this, you can change this as you see fit. If you want it to be five seconds or seven seconds or one second, whatever, zoom out, zoom in, all good. I just made it this way. You can go ahead and make changes if you want.  Grab the GIF or GIF, drag, just going to select it here, drag it and just drop it in right over top of that prompt bar and hit enter. And once you see that, you'll see here that it's gone ahead and loaded it. I'm going to go ahead and click on the little purple send message button, and off we go, it starts working and you'll see the little Kodi purple rectangle. That means the code interpreter is working. Also, while it does this, you can drop that triangle down here or that little tyron, I believe the word is. And you'll see here that you can go in and it'll tell you exactly what it's doing, including zoom factor and all that stuff.  All right, it's done working. Now, let me show you the next part. All right, literally that is it. It didn't need to do anything else. It says, I've created the MP4 file with the slow zoom in effect. You can download it using the link below. Click on that. I'm going to click on it and then presto. It says output.mp4. I'll just go ahead and show it in the finder. And there it is. It's three seconds long. It's an MP4.  Oh, maybe a little faster than I would have liked. But so be it. That is how you do it inside chat GPT. Thanks for watching.


I'm Simon Crutchley and I teach practical workshops on the MA courses at the Centre for International Studies and Diplomacy here at Sars. A couple of miles north of here in Highgate Cemetery is the grave of Karl Marx and written on his tombstone is my favourite quote. Philosophers have only interpreted the world, the point is to change it. So the idea behind our summer guest lecture and workshop series is that you should walk away with a goodie bag of skills you can use straight away. Past graduates have gone on to write speeches for the UN Secretary General, head multi-million dollar start-ups and run big projects for NGOs in the Middle East and Africa, amongst many other things. The workshops are arranged in four broad areas, speech writing, presentations and pitching, power relations and interview skills, writing with specific references to CVs and we also look at voice and bodywork and how to overcome nerves. Each will be of immediate practical relevance and provide a skill base you can carry forward in your career. It's going to be a tough couple of years ahead and we want to give you a head start. You're with Sars because you care about the world and how it could be, thinking globally and acting globally. The skills we teach in summer school series are the tools you will need to do just that. Looking forward to seeing you this summer.


I'm actually looking like the anime. Neither of them could touch me.  No, they're not blowing my back out.  Modded Dragon Ball content. For the past few weeks, that has been exactly what this channel is, and these have been some of the hardest videos I have ever recorded in my life. We did three idiots, sometimes we ended up jumping the opponent, so I did 1v1s with UI Goku and Cell Max, and that didn't work out either. So now I've decided to drop the number to 2 with me and Rhyme versus Goku Black and Zamasu. Rhyme, do you think we actually win this? Bro, we've never lost together. Bro, you did UI Goku solo, did you beat him? You're way too loud, bro. Why are you doing this, man? Bro, I tried it on my channel too. I didn't win, so we got to win this one. Bro, mine was so bad, I didn't even upload it, now I might have to upload it. Alright, but the thing is... Alright, I'm going off your energy, what do you want from me? Alright, I was going to say, the thing is, I don't want to actually use our creative characters. I want to know if we could beat them within Universe, Vegeta and Goku. Alright, charge up, bro. Oh, I can't charge, all I can do is instant transmission. All I can do is instant transmission, bro. This is the worst character ever. This is why we're doing 2v2, bro, because they think they're the dynamic duo, but they ain't, and I'm dying. And I'm dying, bro, I'm actually dead. That was one super. I'm getting cooked, alright, bro, I forgot some of these older raids. We did no checks and balances at all of these guys. It's a blow. It's a blow. Open up, Zamasu. You're going to do, you're doing whatever that, wait, what are you and Goku Black getting into, bro? Zamasu, stop. I blew him, bro. Don't try that. It's all a blast. Oh, combos. I have to do this. Bulma, Kakaross.  Hey, that actually works out. Burst coming out. Help me, Ricardo.  Yes. I was trying to keep him off you. Oh no. What just happened to you, man? I'm up, I'm up, I'm up, I'm up, I'm up, I'm up. Good job, good job, good job, good job. Hurry, hurry, hurry. No, no, bro, I was, I was still falling. I didn't have a chance to eat, it's said to me. Run that back, run that back. Well, I'm not laid out like that. All right, we're back.  I don't think you changed your outfit at all, but you know, I wasn't required. I was just getting a little more in a character. I'm going to charge one final time. Oh, I actually picked the one with maximum charge. Thank goodness. Let's go. This is what I'm talking about. Look at us. Look at us. Watch, watch, watch, watch. When they come up, stay next to me, stay next to me, stay next to me, stay next to me. I am, bro. Right next to me, right next to me. Are you going to explode? Explode. Hurry, hurry, hurry. Hurry. Ah, did we get him? Let's go. Wait, Goku Black's doing something. We get him? All right. I'm hitting collaterals. Mom, I just hit a clip. I just hit a clip. I stamina. It was worth it. It was worth it. You go for Zamasu. I got Goku Black right now. Yeah, I got Zara, I got Zara. Bro, I'm doing that. That part of the show where Goku like fought both of them and he was pissed and he like backhanded Zamasu. That was so sick. Final blow. What is it? Combo's Goku Black. I got nothing on me. Perfect guard. I'm him. I know how to play the game. Is he doing a super? Oh, I parried it. Can you heal us? I got us. I got us. Regen.  Nice, nice, nice, nice, nice. Back it. Oh, you bad, bro. Goku. I missed. I missed a super coming up. Do I say it like that? I don't know. Why don't you yell at any character or you say something like Saiyan?   Yo, I'm actually cooking right now. I'm saying, bro, Zamasu can't stop me. Coming blast. Um, so remember how I said I was cooking? He's got me to trap me to evil. I'm I'm I'm I'm.  I gotta do I gotta do I gotta fight back fight back.  I've been right now. Wow. I've been up. I can't.  Oh, I'm coming. I'm coming. Come on. Next Don't fight me. Oh, here we go. Here we go.  Stand up next. Next. Hurry. Got you. Got you. We got him. We got him. We got him. We got him. Zamasu's paying you like some kind of god. It's fine. You're doing perfect. You're doing perfect. This is not a play stop. Stop. Oh, they're transforming Bro, it's actually been so long. So we did this right. I forgot they do this What do you need help do you need help so much as being last I got to heal me You don't have to heal me. All right. I can do that Why did you do that? They're gonna bring a stand up, bro. Oh, no, watch out. Watch out.  It wasn't even my last resort. I don't I can't lose again He said omelette cheese omelette in French omelette. They're from us. Oh, you want legal? Yes I speak multiple languages a little Spanish a little Wait, do you still have your explosion or no I got There we go. Good block. Good block. Good block now Now we're actually using teamwork Oh, he did bro. He did bro. He did bro. Damn the chip damage was insane. He did bro. Watch out Obviously what's obviously what's your attention for some reason stop? Ah Get out of here final Gallic Part 2 the sequel so now now we're fighting each other again Zamasu night you want to see some combos. Let's go I don't think people know how hard these actually are Yeah, I don't think people really understand that Zamasu hits for a million and if you if that ultimate right there landed I was there Yeah, I got up to be able to ask us to release you so they can dollar themselves I don't know if we can but I really wish that one bit one day You know what we should suggest to dims like a watch me crazy videos like this so people can do it with Friends Yeah, they should they should just make it like super raids. Why is Zamasu throwing hands? I'm cooking I'm cooking I'm cooking I'm cooking again. I over commit it to the combo I have no stamina left come down. I might have to I might have to pop a oh no Oh next to me. Oh, no, what happened I know I'm giving it both the hands a boy right there. What is going to be? Sorry, don't be sorry I do I just want to I'm coming.  Oh, bro.  You got it. You got it. Thank you I can heal us. I can heal us stay like That's what I'm talking about them both. I'm fine. I'm both me bro. There's other heli. What a grab Where did Zamasu come from? Why oh no, I'm dying beyond super dry it Ouch, whoa, who hit her editor. Did you show that hold on?  He that's the beam attack. I got rid of it That was that was annoying. That was sick. All right. I've decided this is the last run with Goku and Vegeta I like that you dumbed it down. I got now. This is more like a manga style battle Because I think I was doing too much. Oh, dude, does my goku have a guy? All right. I was checking I was checking. I thought I thought maybe I thought maybe but you know what I'm gonna do I'm gonna give these guys the business bro. I'm going kaioken in blue Just don't do it wrong because they won't break your stand. You know, I do not do not cuz I'm being both That's I can't yet. You know what if you buy time if you buy time right lifestyle dig deep dig deep Super Saiyan blue kaioken Go What do you want me to fight both of them? All right, I will oh You want you guys both want a piece? There we go. I learned this from Krillin This is a part of the anime where me and Krillin were fighting chain destructo disc. Where are you going? So let's go leave alone prominence. Let's go kick up the heat flash.  I am Combos combos. I remember you have advantages when you have kaioken on but you lose health Are you okay still I'm just keep nope. No, but I got a sense of being just you stay alive. You stay live I'm on the floor. I'm on the floor. I'm up. I'm up. I'm up. I gotta kick it back up in a kaioken Let's go They work Get off me. Oh both of them. I'm actually looking like the anime neither of them could touch me. Oh wait Thanks, bro, I'll heal. Oh, you're the best Watch out. I'll take it.   I'm right behind him. Yes. I'm as soon as I know anything about this Oh, damn. We are barking at each other. Look. That's like 80 messages. Super Godfist missed. I try to do a message Not died for it. You did a message to them. I'm running.  No, no, no blowing my back.  So I'm super Godfist. Oh wait, that didn't work. They have you everything gives almost to them This is the raid where you can actually break the stamina when they charge an ultimate. Yes. Yes, sir We still have that Let's go for damage. I mean it was decent damage. Here we go perfect guard But it's still not enough the perfect guard still ended with me dead I'm trying not to I'm trying not to but it's looking really bad if he fires one Yes, my hero, I don't have any heels left though. We don't need heels Leave him alone. No Brick a stick. Yeah, let's go Leave me alone.  Obviously watch watch watch watch watch. Hey back up Goku black.  Get my back.  I'm down on the ground right below you. This is it me. I've got no heels left Thank you One who jumps except for us I died always doing it again. He's doing it again.   Keep screaming Oh Man, I sure wish somebody else was here somebody like your son a sci-fi for other worlds I came to show up. Hey, look at the all future go on. That was a good choice. All right So I've picked modded rage trunks. This is a fan put maid character They put character get PTSD the rain the rain Get out of here. You leave this one to me, man. Yeah, I got this I like how he's afraid of the rain and not and rights. Look at these two phony gods, bro Look at these phony gods, bro. Look I got not all works changing blows. I'm great shrunk sign of hope There we go. I missed. Oh, he just punched me really hard. Damn. Don't know rage trunks combos are insane This guy hits different rage trucks just plays the game a little differently Super Saiyan that guards gonna break one of these days Oh my god. He oh Let the sign of hope of my future. Go get out of my future What I think that I think these animation bros burning strike fuse a sort of hope It's very very powerful. He's a super armor, too. Just don't get grabbed. I don't think I have sort of hope I have burning strike and sign of hope I could use it. I could use a heal. I could use a heal. I could use a heal heal. Thank you Well, oh my god. It was it was close. I'm just gonna use it as a heal Just keep me alive. I got I got it.  Hey, I'm trunks is rage combos are crazy. They could they was cooking with this one I got I got I know Damn you die. Oh Run that back. We got caught by surprise. That was a surprise. Yeah kindly. Oh Oh, I came from the other time. Oh, let's go. I saw myself getting beat up.  Please. God. Let this be it. Come on. Right hundred percent. We need we need this win I'm going after Zamasu rage combo.  I'm almost combos What moves do I have meteor crash buster cannon? Let's fire a buster cannon. All right buster cannon did miss But that's more on me than trunks. Oh, I thought I had it. I thought I'd find a flash in his face meteor crash Let's go huge. I'm gonna give us up. Do you need me now? Okay? Papa region as well Papa region damn getting jumped. I need I need to break my own stamina at some point get off of him What's this animation on charge? He's cannon. I missed again try another one Yeah, I mean he's dodging it buster cannons better at tracking side-to-side than it is Oh, we're don't run away from me.  All right good What you trying to do?  They mad fight me about it You could stay mad, but fight me about a buster cannon.  Oh Why did drugs vanish into the attack?  I'll heal us. I Can't I can't it's over Oh He'll be our heels. I I can but it's gonna take me some time That was crazy It's raw sign of hope I got him with a round of it gala gun The camera what I'm gonna throw up.   Maybe needed a few more days in the oven You might be immortal and you might heal it through everything, but I'm still throwing hands get off of him, bro That's for cannon track transform Buster cannon is useless. Buster cannon, please land Frame one you're up. I heal. I heal. I heal God Zamasu, please Thank you appreciate it Buster cannon, please hit for the love of God. I Can't get Buster cannon to hit no better what I do. Oh, he's transforming now. They're actually pissed. Okay, keep trying Keep trying we can win here. We can win here. We can't I'm dead. I'm dead. I'm dead. I got it. I got a sense you though Survive God I gotta go Cowards, bro. Oh that was sick. That was a good counter. What's happening? Oh, I thought he hit you Alright Zamasu's locked on a minnow Okay. Okay, so you clearly wanted the smoke then back off me.  Yeah Ah, no, bro. He did his attack at the ceiling so I couldn't fly out of it It's up to you up down of that right next to you up there right next to you. Oh, damn. You're too fast You're too fast. Oh, no. Oh, no You got counters, but this isn't the heel build Run this is it. This is our future. You have to decide to win. I Hate that one locked on please go hot. Yes. Yes. No. No. Yes. Yes. Yes. Get out of here run That was crazy. Um, well, here's the thing is I actually am just a boy. I am a man This is gonna be my final stand. All right, man. Forget this timeline. You guys can have it


This next speaker is one of the most exciting people I've met in the SEO industry recently. Based in the UK, ARIGE is a SEO consultant with over 8 years of experience who focuses on all things technical and on-site. She has done an incredible job to help increase the involvement and representation of women in the SEO community. She is the founder of the women in tech SEO community and has spoken in industry events such as Moscon, SMX, and Brighton SEL. The only thing she probably loves more than SEO are the Beatles and chocolates. You can find that on our website. If you run a large website, this is one presentation that you want to pay close attention to. Over to you ARIGE. Hey everyone, thanks so much for joining. My name is ARIGE and I'm here to talk about taking charge of your indexability. I really hope that I get to see everyone in Seattle next year and for now I'll be around in the chat. So I'm here to talk to you about something that took me a little while to wrap my head around but spending the last 18 months working on a 40 million plus index page website forced me to finally get it. We are fully in control of how Google chooses to crawl and index our website. And yes, we are in control but it can feel extremely scary because if we don't do it properly then we're not actually going to benefit from the many things that we are doing right. And when I say many things, I mean things like all the awesome content and off-page work that you might be doing. So if we're recommending SEO fixes, whether they're small or large, let's just make a pact right now as an industry to drop the 100 page audits and focus on prioritizing recommendations that are actually going to have an impact. So I'm going to start off by setting the scene. This is a completely fictional example that I'm going to be using throughout the talk today. Let's envision that we all work for a car aggregator website. Now our users, when they actually log on to the website, there's a number of different things that they can do. Firstly, they can search for cars near their location. They can filter these search results. These search results can be filtered by make or model or year, color, price range, everything you can possibly think of when it comes to cars. They can view car listings and they can contact sellers directly through the website. They can view car history information and they can even read the latest car news if someone is interested in doing so. These are just some of the features that users can do on our website. Now most webmasters, they tend to set up websites in one of two ways. This is specifically with aggregator websites as well. They can either attempt to index absolutely everything to capture as much ranking opportunity as possible or they can decide to no index a huge chunk to avoid suffering from index bloats. What is index bloat? It's when a website has an excessive number of low value pages indexed. So let's go ahead with the first scenario now. Let's say we decide to attempt to index absolutely everything. If we do that, we might end up indexing every possible view location, filter combination, car listing page and car history information page. Why would this be a problem in our specific example? Let's try to think about it from Google's perspective. Would Google even bother crawling every possible view location, filter combination, car listing page and car history information page? And if they decide to crawl it, would they even bother indexing it in this case? And more importantly, do you actually want to rank for every geolocation, filter combination, car listing page and car history information page? The answer to all these three questions is most probably going to be no. If we attempt to index everything, this is probably what's going to end up happening. Google might not end up crawling all of our pages. Google might not end up indexing all of our pages. Our valuable pages, the ones that actually matter, the ones that convert might not be crawled and or indexed. And our valuable pages might not even end up ranking. I'm being really generous by using the word might. So let's go ahead and say this scenario is out of the wall. This is not going to work. Let's go ahead and try the next scenario, which is no indexing a huge chunk to avoid suffering from index loads. Well, in this specific case, what tends to happen is that we miss out on ranking potential. So we miss out the potential to rank for every possible geolocation, filter combination, car listing page and car history information page. So this scenario doesn't really work either. So I guess what I really want to talk about is how and where can we actually draw the line between these two scenarios? Before we make any decision on how we can go ahead and control the indexability of our website, we need to know the answer to this one question. What is the high level KPI that we're actually being measured against? And whether you come into the business as a new person or whether you've been there for a while, there is a possibility you don't actually specifically know the answer to this question. And it's very important to know who to speak to in order to understand this from a business perspective. It most probably isn't going to be organic rank. It's not going to be organic sessions either. And it most definitely isn't going to be some third party tools visibility chart. We see a lot of those. And if it is one of those, it probably shouldn't be. It's most likely always going to be organic leads or revenue. This is what the business is measured against. And this is what an SEO function is also measured against. In our specific scenario with our car aggregator website, an organic lead happens when a user contacts a seller about a potential car. So why don't we try to tie these two together? Let's go ahead and tie index pages with organic leads and see what that looks like. So I want to go back to this list now. We know that this is what our users can do. And we know that this is the main functionality that they get out of our website. I tend to understand things better when they're in table format. And so do a lot of other SEOs. So let's try to translate that into a table. Okay, this is what it's going to look like. This might look very, very familiar to a lot of people who work within aggregator websites or even e-commerce websites. These type of templates are always very similar for one to the other. Specifically for our car aggregator website, we have four main templates. The first being our car search pages, which I'm going to go ahead and abbreviate as our CSPs. These are our result pages when a user actually searches for cars by a location, and it includes all of our different search filters. Secondly, we have our car listing pages. These are our CLPs. These are the listing pages when a user creates or picks a specific car and goes ahead to learn more about it. Thirdly, we have our car history pages. Now, if someone wants to go ahead and try to search car valuation or history, they enter a car registration number and they get all the information they can about it. And finally, everything else can be grouped into another template. These tends to be things like our homepage or blog about and so forth. So I need to now understand how can I figure out which template from these provides the most value. So I'm going to go ahead and analyze some data. And that's usually what we tend to do at the very beginning when we have any kind of case scenario or any technical SEO project that we want to get signed off for. It's actually understanding the data behind it. So what data am I going to actually need per template? Well, I've tried to split it into those three things. Firstly, I want to understand the number of index pages. Secondly, I want to understand the number of organic sessions. And thirdly, I want to understand the number of organic leads. With each one of these, it's very important for me to also understand what's the percentage from total so that I can understand the scale of this data that we're working with. And I'll go ahead and get all of this data for the past 12 months. Because if we only get a few months or so forth, it might be impacted by seasonality and it might not be as accurate as you possibly want it to be. So these are all fictional numbers. Let's go ahead and imagine we've done a whole bunch of analysis and we've come back and this is what the breakdown looks like from a template by template basis. So first up, you can see our car search pages. They, as an example, represent almost a third of our index pages, but they actually provide us with 75% of our organic leads. And then if you look at the very end, you've got your car history pages. And these are a completely different spectrum. So these almost have half of our index pages, but they only bring in 1% leads. If I try to color code it a little bit to make sense of it, you'll find that every other template as well as our CLPs, they represent around 10% each and they bring in a total of like 25% organic leads. But there's definitely something problematic going on here when you look at our car history pages. And the main question that I tend to ask myself is, wouldn't we be better off spreading our link equity across more valuable pages? And wouldn't we be better off having Google crawl more valuable pages? And the most important question of all is, is it even worth doubling up our number of index pages for only 1% of organic leads? Websites do not and most probably should not in most cases need to have every single page indexed. Instead, focus on indexing pages that have the potential to provide good search results for your users. And I know that this feels like a fairly straightforward example, but I promise you that every single aggregator website tends to have one of these. And it's not enough to simply be fixated on our car history pages and leave it at that. There is so much more that we can dissect on a template by template basis. For example, if I look at our car search pages, you know, from up high, it looks great. Third of our index pages bring even 70% for organic leads. I would think, you know what, that's fine. It seems to be efficient enough. I can just drop it that way. But if I go ahead and dissect it, I find that this is the amount of index filters that actually make our car search pages. And this is how many filters are indexed within each one of these filters. So for example, let's say you've got 10 colors, you've got 500 sizes, you've got four models. If we calculate that, we find that there is a total of over 800,000 potential index pages that are purely based on our search result filters. So it's fundamental that we break this down to the next level. It's not enough to just leave it at that and say that the data looks fine, but to dissect it into a piece by piece. But just like we did with our top level, I go to the next step and actually start to understand filter by filter for our car search result pages. What does this look like for index pages for organic sessions and for organic leads? The more we slice and dice our data, the more we're going to be able to make informed decisions about what is worth consolidating, what is worth the indexing and what kind of technical SEO projects that we undertake will actually have the impact that we need. So we're going to have a little bit of an intermission here. And we're going to go ahead and look at a typical meeting in the life of an SEO. And I think there's going to be a lot of familiarity around this. A lot of us have been through this before. So we're going to say hello and meet our senior stakeholder. Their name is Mark. So Mark comes up to us and says, oh, car history information pages, they are critical for our consumers. They can look up any car registration number and they get all the information that they need. So as an SEO, we come in and we say, well, yes, that's true, but they're very useless for Google. They're thin pages, they provide low organic value and they double up our index pages. So Mark says, well, you know, I don't care about Google. I don't care about this. Never mind. What does this actually mean for leads? So we go in and we're, you know, we want to show off all the cool analysis that we've just done. And we're like, you know, we're really glad you asked. I spent the past two weeks.  I used BigQuery. I grouped our page templates. I calculated organic leads per template. At this point, you've completely lost Mark. He doesn't really care about what you're saying. This is of no interest in whatsoever. So you just go ahead and you summarize it. You say, well, it represents 1% of our total organic leads. In a dream life scenario, at this point, Mark would be like, is that it? You know, just de-index these pages immediately. You can take all the resources you want, whatever you want, go ahead and do it. These pages are pointless. You're right. In a real life scenario, what tends to happen is that Mark goes ahead and says, well, you need to work with team A. You have to build a strategy that can convince team B to convince team C to consider convincing team D to potentially de-index these pages. And at this point, you just have to take a super deep breath. Joking aside, I promise you there is a purpose to the story. I know that this is something we all relate to, and these are meetings that we've all been in. And it doesn't matter whether we're agency-side, and we're discussing this with clients, whether we're consultants, or definitely specifically whether we're client-side and in-house. As SEOs, we need to speak the same language as senior stakeholders to get sign-off for these technical fixes. So let's go ahead and try to recommend our recommendations now. So I'll go back to this table. We know that we want to first focus on core history pages because we know that represents the biggest opportunity for us. If I take a look at this closer, I guess I get a little bit worried because I'm like, okay, yep, that looks fair. 45% index pages, it's a lot. Organic leads, 1% that's too little. But I don't know, 10% of total organic sessions, that feels like a scary thing for me to simply get rid of. I'm personally very risk-averse. In this specific case, what good is 10% that doesn't even convert? Every aggregator or classified-type website tend to have something very, very similar to a core history page. And as Mark told us, these pages are extremely useful for our users because they want to look up different cores and different information via the core registration number. But let's be on the safe side and let's make sure that we've done all of our checks. So let's go ahead and do a few checks on our core history pages to see whether they're really worth the indexing or if we're going to lose out on some opportunity that comes from them. So the first question I ask is, do they take up lots of crawl budget? Because yes, they do represent an indexability problem, but do they also represent the probability problem? So in this case, yes, I have analyzed our logs and in an average week, 50% of Google bots' crawl requests are spent on our core history pages. So that's a lot of crawl requests spent on it. Second question, do they rank for important terms? So I analyzed our ranking data, core history pages barely rank for any keywords that we even care about. Third question, do they have unique content? Yep, but it's very thin and it's only useful for users on a personalized basis and it doesn't even convert. Fourth question and final question, do they have high quality backlinks? Nope, they barely have any backlinks. I've done a link called it. Barely anything is pointing at them and the stuff that is pointing at them is not high quality. Okay, so let's summarize everything we've looked at so far. So we're saying that our core history pages represent 45% of total index pages, 50% of weekly crawl requests, 10% of total organic sessions, which you know, it's a bit of a risk there, very thin content, minimal ranking, minimal backlinks, and most importantly, only 1% of total organic leads. Now do we feel more comfortable de-indexing them? So I walk you through this because it's really, really, really important for us to do that. It's not enough for us to simply look at the high level data without seeing whether there's anything else that might be potentially losing any form of opportunity or impact by de-indexing or consolidating certain sections of the website. So things to remember here, which is super, super key. Number one, make sure your site maps are set up to automatically remove any no index pages. I know this seems like a given, but it's something that a lot of site maps are actually not set up in that way, especially site maps that depend on a lot of legacy codes. This is an example of something that might feel very easy in principle, and we might take for granted and think that set up, but it can actually be extremely complex, and it might end up deterring or delaying the project that you're doing by several weeks or months while engineers try to fix it. And our current history pages, they will not de-index overnight, and that's something anyone who's been part of a consolidation or a de-indexing project is very familiar with. It can take a few months or more for Google to decide to flush those out of the index. The larger the website is, the longer the time it might take to the index. And we know there are crawlability ways to ready because we've done that log analysis, in which case it is really important for us to be blocking them for robots of TXT. It should be on the roadmap, but it should not be done anytime soon. We need to wait a few months to make sure that they actually flushed out of the index, or else it's not going to know that they've become de-indexed. So let's go ahead and do some prioritization. I go back to what I said at the very start, because I think this is something really important and something we all need to bear in mind. Let's please make a pact and drop all of these 100 page audit documents. Prioritization is key when it comes to working with technical teams, engineers, senior stakeholders. The first question they always ask, what's the priority of this? I personally like to use t-shirt sizing. I think it's really simple. There are tons of prioritization matrixes out there. Some are more complicated than others. I like to keep things really simple, and this is something that technical teams that I've worked with tend to use a lot of as well. So at least we're using the same frameworks, like one another. So I tend to split this into two things. Firstly, I look at SEO impact. So with SEO impact, it's this idea of how much of an SEO impact will this recommendation likely have on our overall organic leads? And then with tech effort, it's about how much technical effort will this recommendation take to actually implement? And please do not answer this on behalf of engineers. Now, this is a mistake that all of us SEOs have done before, where we try to assess the effort of something that we are not experts in. We wouldn't want engineers to come up and say, I reckon the SEO impact of this is a larger, medium or small. We wouldn't want to do that for tech effort either. So for every identified issue, what I tend to do with my prioritization matrix is I look at what is the SEO impact? What is the dev effort? And together that dictates what the priority is. This is an example of what a normal table that I have added to a separate tab in my Google Sheet tends to look like. For example, at the very top, you might find that, you know, if your SEO impact is large, but your tech effort is small, that's a high priority right there. That's a really quick win. And that's a really good win that will actually have an opportunity. On the absolutely other extreme, you might find that if the SEO impact is small, but the tech effort is large or X large, in this case, this should definitely be a low priority. If you want to learn more about my full framework, I've got a guide here all about getting tech SEO implemented. And it shares a lot of these resources. And you can just visit it on bit.ly forward slash reach dash. So let's communicate.  So what is the first thing that tends to happen once an SEO recommendation gets implemented? Well, your senior stakeholder, yep, Mark is still around.  That's the first question they're going to ask you. Our senior stakeholder, Mark, will be expecting results, and they're going to be expecting it really fast. So it's really important to manage expectations. And you need to do that by not just communicating after something's rolled out, but communicating before and during an after. Underpromise and overdeliver is always how I tend to do it. It's so important, you know, don't go in with like over promises of this is going to happen to conversion. And don't go in by underdelivering what the actual output is going to be. We know that the indexing, our car history pages, was simply a stepping stone for fixing technical foundation. It's not going to magically increase our share of voice. Because projects like that with technical SEO are ones that that should have been right from the start. That's your foundation. Communicating updates is one thing, but communicating updates that are actually backed up with data are a real game changer. Let's go back here for a second. This is how we manage to get sign off in the first place by tying our index pages with our organic leads. We need to make sure that we keep reporting on these metrics, because these are the metrics that everyone is familiar with. And these are the metrics that people actually signed off with. So keep everyone informed. Update these metrics on a weekly basis. Show week on week change, one-on-month change, year on year change. And make sure that your dashboards are accessible and open. Stakeholders feel better knowing that the information is there. Even though in most circumstances they don't actually bother checking it, but if they know that these reports live somewhere, they feel better about that. And it's going to serve as a benchmark, and it can be used as case studies for future sign off. The next time you need to de-index the large section, or the next time when you dissected all of these index filters and know some more problematic, if you go ahead and you use that as a case study and a benchmark of, when we did this to our index pages and CHPs, this is what happened to these, you're able to then go ahead and set that as a benchmark to get signed off for future projects. So one final thought before we wrap up. I've personally never even worked on a Car Aggregator website yet. This was just an example. This methodology though can apply to all forms of aggregator sites. They can work on fashion, jobs, properties, you always have a CHP that's lying somewhere. When I first pitched this talk, my aim was to actually go into detail about the technical SEO requirements.  But you know what? Like the actual technical recommendation, this is actually the easy part. What I find really tricky is the backing up of your recommendation with data. It's the stakeholder management. It's the meetings for the sake of meetings. Those are the really, really hard parts. And those are the ones that if we don't get right, we're not able to get sign off for some of these projects that might be hindering our performance. The first time I personally worked on an aggregator website, like I completely panicked, I felt completely out of my depth and I didn't even know where or how to start. But right now, like a few years down the line, these are actually the type of websites that I enjoy working on the most. Over time, I've come to realize they all have similar problems that require similar solutions. And once we fix the problems, you know, that actually feels really rewarding. And it can be rewarding, yeah, from an SEO impact, which of course we constantly measure ourselves against. But more importantly, it's extremely rewarding in terms of achieving higher level of trust with stakeholders. And that just makes the process and it makes our life so much easier the next time round. So the past 132 slides, yep, 132, they were based on an example that simply touched on one simple metric. All I did was I tied number of index pages, which is a technical SEO metric, to organic leads, which is the KPI that actually matters the most to the business. And this same concept can be translated across far more SEO metrics. As SEOs, it's fundamental that we do not work in silos. And we can achieve far more if we measure our wins using metrics that our business actually cares about. And please remember, it's okay to feel overwhelmed working on something new. We've all been there. Thank you so much. You will find all of my slides here. They're on Bitly, Areej-moscon. I am around on the chat. If you have any questions and you can find me on the website, areejapali.com, you can find me on Twitter. So please do get in touch. Huge, huge, huge. Thank you to Moscon for inviting me to speak. And I hope to see you all in Seattle next year. Thanks.


Astronomy inspires humankind by revealing its place in the universe. The creation of elements, solar systems, and the life and death of stars and galaxies are unraveled in front of us by the use of advanced technologies. The next generation telescopes such as the Giant Magellan Telescope will permit us to peer even deeper into the universe than we've ever been able to do before. The seven petals of this giant telescope will act as a single 25-meter diameter mirror. It will be the largest ever constructed. That's because in astronomy, size does matter. The bigger the telescope, the further you can peer into the universe. But the telescope is only one part of the equation to getting these images. During its travel down to Earth, light gets distorted by the very few meters of its travel through the atmosphere. This is the same problem you encounter when you're flying an aircraft, air turbulence. There are pockets of cold and hot air that act as individual lenses and they send the light in different directions. So what happens is the light that arrives at the telescope is not flat anymore. It's not a flat wavefront. It's a distorted wavefront. And it has many ripples just like the one seen at the surface of the swimming pool. The telescope cannot do anything better than create a fuzzy blob out of this distorted wavefront. Fortunately, the astronomy community has developed a sophisticated technique called adaptive optics which enables us to correct for the atmospheric distortions of the light in real time. Adaptive optics can restore the sharpness of the original images of planets and stars as if we were imaging them from space instead of doing this from the ground. As part of this technique, we also use powerful lasers which we use to create artificial stars in the upper atmosphere. These artificial stars are very bright and they are brighter than the natural stars and that's why we use them to probe the atmospheric turbulence above our telescope. We also use specially made mirrors called deformable mirrors which are able to bend and take the shape of the distorted wavefront so that when the light is bounced off the deformable mirror it cancels out the effect of the atmosphere and basically restores the original image quality of your instruments. These deformable mirrors, they are exquisite examples of advanced optomechanic systems. They contain thousands of actuators which can all move by just a few microns. That's the 100th width of a human hair. And they take whatever shape is necessary to compensate for the distortions. Adaptive optics is just one example of advanced technologies that have been developed for astronomy which we can use and apply in other disciplines. At the Austrian National University we are motivated by bringing those technological solutions to solve other big problems that humankind is facing. For instance, recent developments in lasers and adaptive optics enable Australia to have become a world leader in the area of ground-based space situational awareness. We are monitoring the growing space traffic and also its major threat, the threat of space debris. By using exquisite optical metrology techniques such as the one on board this NASA graceful on mission and combining those with other techniques like infrared detectors and advanced interferometry, we are planning for the next generation for mission-flying missions which will be used for astronomy and Earth observing. By using our knowledge of lasers and adaptive optics and combining that with advanced quantum encryption technologies we are also developing tools for advanced communications, laser communications with high throughput and secure communications as well around the Earth and into deep space. Infrared detector technology developed for astronomy can also be used to monitor the health of crops around the world from airborne platforms and space-based platforms. So these are just a few examples of all these techniques that have been developed for astronomy which can be applied in other disciplines. At the Austrian National University we have large multidisciplinary teams of astronomers, instrument scientists and engineers who are all working together to bring these technological solutions to the rest of the world. Thank you for your attention.


Epithelial tight junctions, TJs, regulate paracellular trafficking of macromolecules, form a selective permeable seal between adjacent epithelial cells, and demarcate the boundary between apical and basolateral membrane domains. Disregulation of TJ barrier integrity may predispose or enhance inflammatory bowel disease, IBD, progression, making therapeutic target to restore TJ barrier integrity a potential effective approach against IBD. This article was authored by Sung Hee Lee.


So welcome to the screencast on quantified statements. So this is a concept that goes back to an earlier concept we saw in the last section of an open sentence. There's a definition we saw, basically an open sentence is a sentence, it's either an English statement or a math expression or a hybrid of those two things. That's almost a statement in the logical sense that has a definite truth value, except an open sentence has a variable involved with it. And so we can't tell the truth value of that sentence without knowing a little bit more about the variable. Here are three examples of open sentences. Each of these, in each of these cases, there are variables present. Whether it's k or x or even two variables, x and y. And each of these sentences would have a truth value if we knew something about the variable. For example, to say the integer k is even, is that statement true or false? Well, we don't know, because we don't know what k is. Is the statement x plus y equal to false or true? We don't know. I mean, for this statement, the sentence is sometimes true for certain values of x and y, like one and one or five and negative three, but not for all values necessarily. And even the sentence x squared bigger than or equal to zero, is that true or false? Well, we can't really say until we say more about what the x is. Is x a real number? Is x an imaginary number? Is it an integer? We don't know. We can't tell the truth value of these sentences without knowing a bit more about the variables. Now, if we assume just for the moment that the universal set is the set of all real numbers. We can say something about this sentence right here. If x belongs to the real numbers, then we somehow know that through our basic arithmetic that this statement is really a statement. And it's actually true for every real number x. So we can say something about how often this sentence is true. And we can say something about how often these two sentences are true. And that's kind of the gist of the screencast. Given an open sentence, how often is that sentence true? So we're going to open this up with a concept check, actually. Let's lock down the universal set to be the set of real numbers. And look at the open sentence x squared minus one equals zero. Now, how often is that true? Is it always true, sometimes true, or never true? And the answer here is, of course, going to be sometimes, but not always, right? Sometimes, because there do exist x values that make this sentence true. For example, x equals one makes this statement true, and x equals minus one makes this statement true, but not always, right? We're pretty well aware that, for example, if x equals two, yeah, the sentence does not really, it's a statement, but it's false, okay? Two squared minus one is not equal to zero. Now let's do another little concept check here. Same kind of question here, but different open sentence. So look at the open sentence, x squared plus one is bigger than zero. And again, the universal set, we'll just consider x to belong to the real numbers. Now, is this sentence true always, sometimes, or never? And in this case, the answer is always. Okay, when you take a real number, okay, the universal set really matters here. We take a real number, x squared by itself is bigger than or equal to zero. If we add one to it, that makes that inequality strict. So this is a statement that is always true. It is true for all real numbers x. So in both of these concept checks, we introduced open sentences and asked how often is that open sentence true? And sometimes the question is sometimes, sometimes the question is always. And in future screencasts, we're going to take up the situation of what happens if a statement is never true, what can we say about that? So let's pull out the main concept here. Take a look at the first open sentence from the concept check that said x squared minus one equals zero. Now that is not a statement as is. We don't know enough about the variable to say whether this is true or false. We can't determine the truth because we don't know for which values of x this is supposed to be true or false. And for all of them, for some of them we don't know. We don't even know what x is. However, if we add this little bit of verbiage onto the front end of that sentence for some x in the real numbers, remember the symbol right here means is an element of. So for some x in the set of real numbers, x squared minus one equals zero, then that is a statement. In fact, it's a true statement. What we've done here is we have quantified the variable. I have said how often should this open sentence be true? We said for some x in the real numbers, sometimes at least one x in the real numbers, this is a true statement. We've quantified the variable. And so we've turned an open sentence into a legitimate logical statement whose truth value we can apprehend. In shorthand, we're going to write that phrase for some x and r with a special symbol, this little backwards e right here, which you should read. There exists. There exists. Okay, so the way you would read this often in English is to say there exists an x in the real numbers such that x squared minus one equals zero. And that happens to be a statement, happens to be a true statement. The way that we've quantified this is to say that there exists an x in the real numbers that makes this equation work. And so we're going to call this an existential quantifier. Existential quantifier, okay? That's what this is. We're saying that given this open sentence who's, it's not really a statement because we can't tell the truth value. If I quantify this existentially by saying there exists an x, at least one x, possibly millions of them. But at least one x in the real numbers that makes this equation true. What we've done is we have quantified the variable and turned an open sentence into a statement whose truth value we can determine. Now on the other hand, take a look at the set, the open sentence from the second concept check, x squared plus one greater than zero. And again, the universal set we've fixed down to be the real numbers. So that's not a statement either, although we feel like it ought to be true. We still need to say something about that variable. How often should this be true? If I add this verbiage onto the front end of that open sentence and say for all x in the real numbers, not just there exists an x in the real numbers, but for all x in the real numbers, x squared plus one is bigger than zero, that's a statement for sure. And we, again, we've quantified the variable. We quantified it in a slightly different way. Well, maybe not slightly different way, possibly radically different way. What we've done is say, this open sentence is true always. Okay, and that's much stronger than saying that it's true sometimes. So we've quantified this variable, and when we say for all x in the real numbers, we quantify an open statement by saying the statement is true always. Then we are going to use a special symbol for it too. Kind of an upside down a, which you should read for all. Okay, so the way this shorthand would read in English is to say for all x or for every x in the real numbers, x squared plus one is bigger than zero. So once again, we've quantified the variable in an open sentence, thereby making it a statement. That statement happens to be true this time. And since we have quantified this for all x, we're going to call that a universal quantifier. So an existential quantifier is where we slap a quantification onto an open sentence to say that the open sentence is true for some values of x. At least one value of x. A universal quantifier is where we do the same thing. We specify how often the sentence is true, but we specify that it is true for all x that belong to the universal set. So let's do a couple more examples, four more examples actually. Here are four quantified statements. If you just looked at this second set of parentheses, those would all be open sentences to say that square root of x belongs to the integers. We don't know, we have to say something about the variable. And so that's what the first set of parentheses is for. Those are all quantifications, let me get rid of those two things. So which of these is true? Okay, so is it true that there exists an x in the integers now, such that the square root of x is also an integer? Well, that is certainly true. And how do I know it's true? Well, all I'm saying is that there exists an x whose square root is an integer. So I could pick one out. I could say, what about x equals nine? Okay, that's an integer. And at square root three is also an integer. So this quantified statement is true. Now look at the same open sentence with a universal quantifier rather than an existential quantifier. We're gonna say in this one that for all x in the integers, the square root of x is also an integer. Now that is false. How do I know it's false? Well, I'm making a claim that this statement, that radical x is an integer, a whole number, is true for every single x that is also a whole number. And that's a simply false because look, x equals five. Try it, you try the square root of five that is not a whole number. So this statement is not true because I can find a counter example. Moving on to this third one, is it true that there exists an x in the integers such that x cubed is an integer? Well, that's certainly true. If all I'm claiming is that there exists such an x, I can just pick an example out, like x equals 10, okay? x equals 10, 10 cubed is 1000, that's an integer, okay? Fantastic, it's true. But we can actually say more, the fourth statement here says that for every x in the integers, x cubed is an integer. Now that is a strong statement, but it happens to be true. Now I can't just use an example to prove that this statement is true. Because as we've seen before, when I make a general statement about every single element in a set, I can't just pull an element out and expect it to be representative of every single element. I have to do something else. One way you could see that the statement is true is by using the closure properties of x. So if x is an integer, then x times x is also an integer by closure. And so therefore, x times x times x is also an integer, which is x cubed. So that would be a way to explain that no matter what integer you take, its cube is also an integer. So there's the difference between existentially quantified statements and universally quantified statements and just a beginning of a taste on how to determine whether such things are true or false.


The Jack Benny program, transcribed, presented by Lucky Strike.  It's fun to be a traffic cop when you are in the know. You tell all other brands to stop, but Lucky's gets the gold. I sell all brands of cigarettes, I know what people buy. That Lucky Pack's so mild and rich, it's got a red bull's eye.  Enjoy your cigarette, enjoy truly fine tobacco that combines both perfect mildness and rich taste in one great cigarette, Lucky Strike. For only fine tobacco gives you both perfect mildness and rich taste. And LSMFT, Lucky Strike means fine tobacco. So friends, be happy, go lucky, try a carton of Lucky Strike.  The Lucky Strike program starring Jack Benny with Mary Livingston, Phil Harris Rochester, Dennis Day and yours truly, Don Wilson. Ladies and gentlemen, next Saturday night, Jack Benny does his opening television show from New York City. So let's go out to Jack's home in Beverly Hills where we find him packing for the trip. Mary and Rochester are helping. Now let's see, I'll be gone for 12 days. I'll need two pairs of shorts, two shirts, two pairs of socks, two handkerchiefs and a box of does. Close the bag, Rochester. Yes, sir. Wait a minute, Jack, you're going to be gone 12 days and that's all you're taking? Mary, I'm going by plane. I have to be careful about the weight.  It's 79 cents a pound in New York. Unless you get off of Chicago, then it's 57 cents. Or Kansas City, it's 46 cents.  Say, maybe. Oh, stop. But Jack, aren't you taking any extra suits? Certainly, I'm taking my blue surge, my tweed, my herringbone, my pinstripe and my gabardine. Well, that's five suits. I don't see any of them in the bag. He's wearing them. They don't weigh the passengers. I know what I'm doing. Hello, Polly. Say, Mary, I've been talking to Polly about my trip. Watch this. Polly, Polly, where's daddy going? East side, west side, all around the town. That's right. That's right, New York. Now, what is daddy going to New York for? Tell her. Tell her.  Tell her. Tell her. Tell her what? Tell her phone. Rochester, take the cracker out of her cave. Television, video, TV. That's better. Oh, boss, I forgot to pack your tuxedo. Here it is. Put it in the fortniter. Jack, you're not taking that old tuxedo to New York, are you? I certainly am. But look at it. The pants are baggy and the coat is so short. It looks like a battle jacket. Well, that's the latest style. I know, but this one looks like it lost the battle. Like it lost the battle. I know. I knew you were going to say that. Anyway, I'm taking that tuxedo to New York, and I'm going to wear it on my first television show. Well, Jack, if you do it, it'll be awfully confusing. Why? You'll be on live, and that tuxedo looks like kinescope. Kinescope, kinescope. You think you're smart because I haven't got an answer written here. Mary. Mary, listen. I have a sentimental feeling about this tuxedo. It's been with me since my start and show business. Well, why is the right pocket so much bigger than the left? That's where I kept the fish to feed my seal. Any more questions? Now, come on. Help me with these. Come in. Oh, hello, Dennis. Hello, Mr. Benny. Hello, Mary. Hello, Dennis. How do you feel? Boy, am I tired. I pushed my car all the way over here from Hollywood. Pushed your car? Why? The motor was broken, and it wouldn't run. Well, if your car isn't running, why didn't you leave it in Hollywood? I wouldn't have any way to get home. Look, kid, I'm leaving for New York, and I haven't time for a visit. Now, why'd you come over here? Well, there's something very important I have to see about. It's been on my mind all day. What is it? Well... Well, what? Gee, I forgot. Well, maybe you'll think of it later. Now, let's see my shirts, my stuff. Dennis, did you want to ask Jack something about next week's show? No. Oh, was it something about a song that you're going to sing? No. Mary, let's get on with the packing. Oh, I know what I was going to ask you. What? Can you lend me $50,000? Now, let's see. I've got my socks, my handkerchiefs, and... I'm in a hurry, kid. How about it? Dennis, leave me alone. Dennis, what in the world do you want with $50,000? I'm going into business. Business? What kind of business? Well, I'm going to manufacture little round candy mints and call them lifesavers. Now, let's see. I have my shirts, shoes, socks, underwear. I'm going to sell them for a nickel package. Dennis, Dennis, this might be news to you. A little round candy mint called Lifesavers has been on the market for years. I know. Look at all the free advertising I'll get. Shoes, socks, underwear. Dennis, it's all right to manufacture candy, but what made you think of calling it lifesavers? Mary, with his head, it's only natural you think of something with a hole in it. Now, look, Dennis, you came over here. Let me hear the song you're going to do on the show. So forget about lifesavers and sing it. Yes, sir. Now, what are you going to sing? You were meant for me.  Sing the one you're supposed to. Let's see. Have I got everything? I'll be going out nights in New York, maybe rainy and chilly, so maybe I better not take any chances. Rochester, how much does my raincoat weigh? It weighs about a pound. A pound extra costs 79 cents. Shall I put in the raincoat? No, just throw in a four-way cold tablet. I think that'll do it. Come in. How are you, Jackson? How are you? Hello, Phil. Hello, Phil.  It doesn't make any difference. I heard you. What is it, Phil? Your answer ain't getting paid anywhere. Hey, Jackson, there's that soup kit you wanted. Oh, thanks, Phil. Mine is so shabby.  Jack, get a little of those labels on it. Yeah, I used to take it with me when I was on the road playing on one night's stand. Oh. Hey, Jack, look at this label here. Ritz-Carton Hotel, empty jug, Texas. Empty jug, Texas?  I never heard of the place. Where is empty jug, Phil? It's about 50 miles this side of Rackamuff, Arkansas. Oh, fine. Empty jug, Rackamuff. Well, I better run along, Jackson. I gotta go to the doctor. Why? What's wrong, Phil? Well, ever since yesterday, I've had an upset stomach. Well, maybe it's something you ate. Oh, boss, come now! Yes, I guess you're right, Rochester. Go along, Jackson. Have a good time. Goodbye, Phil.  He always makes up those silly names of towns like empty jug. Hey, Jackson, your taxi's outside. Good, good. Hey, did I ever tell you about the time my band played Mish Mosh, Arizona? Oh, and I haven't got time now. Goodbye. Come on, Rochester. Get the luggage. We have to hurry to the airport. Say, Miss, shall I go by the way of Sepulveda? Yes, driver. You comfortable, Mary? Yes, thanks. Good. It's a pretty long ride. How far is it from your house to the airport? $2.40. That's if you stop at the first entrance, you see. Otherwise, it's... By the way, Jack, you haven't told me where you'll be staying while you're in New York. The same place, Mary, the Acme Plaza Hotel. I always stay there. Oh, my goodness, Jack. After the long lecture I gave you last week about being cheap, why must you always stay at an awful joint like the Acme Plaza? I'll tell you why, Mary, for sentimental reasons. Many years ago, when I was trying to get a start in Vortigo, and I had no place to stay and nothing to eat, and I couldn't find a job, the Acme Plaza let me stay there and fed me for nothing. They did that because they knew I was unemployed. Oh, gee, Jack, I didn't know that. If they're that nice, next time I go to New York, I'm going to stay there, too. Okay, but don't tell them I'm working now.  You know, they feel disappointed. Rochester, have you got all the bags? Yes, boss.  You have much time. That's right. Flight number 76 for Phoenix, Memphis, and Washington, D.C. now loading at gate two. Now, let's see. Where do I go here? Attention, flight number 83 now arriving from Fort Worth, Galveston, San Antonio, and empty jug. See, there is such a place. See, Mary, before I get my ticket validated, I want to go over to the fruit stand and buy some fruit. Watch my luggage, will ya? Okay. How ya bug? Long time, no see. Huh? Oh, hello. Uh, Jack, who was that? You remembers that racetrack towel. It always drives me nuts. I won't be long, Mary. Okay. Flight number 19 now loading at gate five for Anaheim, Azusa, and Cucamunga. Attention, passengers getting off at Cucamunga. Watch your step. We do not stop there. Now, let's see. Now, let's see. Where's the fruit stand? Hello, Mr. Benny. Well, hello. Are you leaving town, Mr. Kitzel? No, I'm waiting for my wife to arrive. She's coming in by plane from Dallas, Texas.  In ten minutes. But I don't know whether her plane is going to land here, or at Lockheedt, or in Pomona, or in Pasadena. Well, isn't the plane scheduled to land here? Yes, but my wife is such a back-seat driver. Oh, you're kidding. Kidding, he said. Believe me, Mr. Benny, when that sweet chariot swings low, she'll point the direction.  She was visiting our son in college. Why, Mr. Kitzel, I never knew you had a grown boy. He's my wife's son by a former marriage.  Her third. You mean your wife's been married twice before? This much, she tells me.  The same one I attended. Southern Methodist. Well, look, look, Mr. Kitzel. Attention, please. Flight 14 scheduled to arrive here from Dallas will land at San Francisco instead. Yes, that's my wife. She done it again. Now, let's see, what did I want to get? Oh, yes, the fruit stand. Attention, please. Attention. The Santa Fe Super Chief now landing on runway 7. Super Chief? How can that be? It was awfully windy in Barstow. Well, I think I'll get a magazine, too. I don't want to sleep, anyway. So I might just... Oh, Jack! Jack! Oh, hello, Don. Are you all set to go? Yes, sir. We ought to have a lot of fun in New York this time. Jack? I think so, Don. We always do. You think you'll run into Fred Allen? Could be. We'll be in New York on Halloween, and that's the night he rides. I nearly killed that one, but I didn't. Yes, caught it. By the way, Don. Oh, Don. Where's the sportsman quartet? Oh, they're on a different flight than we are, Jack, and they're on the plane already. The sportsmen are on the plane? Yeah. They're on that one over there. Those four girls are their wives saying goodbye to them. Oh, yeah. The sportsman. By the way, Don. Don, where are you going to live in New York? At the Sherry Netherlands. The Sherry Netherlands? Isn't that expensive? No, I wouldn't say so. You can get a nice suite there for $18 or $20 a day. Oh, oh, oh. Well, that isn't bad. Oh, I'll see you on the plane, Jack. Yes, yes. $18 or $20 a day.  Let's see. I wanted to guess some... Oh, here. Here's the fruit stand. Now, let's see. I think I'll take some of these apples. They look good. Next week is National Apple Week, too. Oh, Miss. Miss. Oh, darn it. She's busy. Well, I just have to wait. Hey, bud. Hey, bud. Hey, bud. Hey, bud. Hey, bud. Bud. Huh? Come here a minute. Look, fella, I... What are you doing? I'm buying some fruit. What kind? Apple. Uh-uh. Take oranges. Well, I don't want oranges. How about grapes? Haven't got a chance. They're carrying too many seeds. Well, what about bananas? Lay off the bananas. Why? I've been watching them for three days. I have yet to see one of them get out of the bunch. I don't know. I wanted apples when I came in here. That's all I wanted was apples. Listen to me, bud. Take the oranges. The oranges? Well, just look at the breeding. Out of Pomona by Smudgepot. Well, I wanted apples, but maybe you're right. I'll take the oranges. Okay. And peel them.  Why does that guy always pick on me? What apple? Attention, flight 21, scheduled to arrive from Salt Lake City, Las Vegas, and Palm Springs has been canceled. The pilot lost the plane in Las Vegas. See, I have much time. I better get my ticket validated. Now, let's see. Where's the window? Oh, there it is. Pardon me, Mr. I'm Jack Benny. Well, who do you think I am behind these bars? Your agent? Never mind. Just validate my ticket. Thanks. Now, how long will it take Flight 12 to get to New York? It's three days. Three days? Why so long? Gary Cooper will be aboard and he drags his feet. Oh, don't be so smart. Now, look, isn't there a faster plane than mine to New York? Well, we have two flights leaving for New York at midnight, Flight 11 and 12. On Flight 12, the tickets cost $180. And on Flight 11, the tickets cost $19. Gee, why the big difference? Flight 11 is the U-drive. Oh, well, I wouldn't want that one. Anyway, I'm on Flight 12. Is that usually a smooth trip? They're all very smooth. Oh, then I won't get sick. No, but whoever sits next to you will. Now, just a minute. I've taken about all I'm going to take from you. Now, give me your number. I'm going to have you fired. Oh, please. Please don't. I'm sorry I offended you. Don't get me fired. I have a big family to support. If I'm out of work, my wife... Well, all right, then. I won't report you.  Well, that doesn't. I'd punch you right in the nose if I didn't have to take all five coats. Now, I'm going to see... Attention. Passengers for Flight 12 to New York may now board the plane. Oh, you better hurry. Coming, Mary. Coming. Attention. Attention, please. Flight 21 from Las Vegas, which was canceled, is coming in on schedule. The pilot finally made a DC-6 the hard way. Is everything all set, Rochester? The man is weighing your bags now. Oh, good. Attention, please. Flight 22 now leading for San Joaquin Valley, Sun Valley, Imperial Valley, and Apple Valley. Hey, bud. Huh? Come here a minute. Oh, attention, please. Flight 22 now leaving for San Joaquin Valley, Sun Valley, Imperial Valley, and Orange, New Jersey. What? Well, I gotta go. Come on, sweetie, give me a kiss. Look, mister, don't get fresh with me. Mary, it's me. The propeller blew it off. Come on, give me a kiss. Goodbye, Mary. Goodbye. Be happy. Go lucky. Be happy. Go lucky, strike. Be happy. Go lucky. Go lucky, strike today. I keep a lighthouse by the sea to guide all those astray. It tells them to get lucky, strike, and light up one today. A secretary has to know where everything is filed, and lucky strike goes under him because it's really mild. Be happy. Go lucky. Be happy. Go lucky, strike. Be happy. Go lucky. Go lucky, strike today. Yes, friends, be happy. Go lucky. Enjoy your cigarette. Puff by puff. You'll find luckies always give you perfect mildness. In fact, scientific tests confirmed by three independent consulting laboratories prove lucky strike is milder than any other principal brand. And puff by puff, you always get rich taste, too. All the deep down smoking enjoyment that comes from truly fine tobacco. Because L-S-M-F-T, lucky strike means fine tobacco. So friends, be happy. Go lucky. Try a carton of Lucky Strike. Be happy. Go lucky. Be happy. Go lucky, strike. Be happy. Go lucky. Go lucky, strike today. Say, Don, this is a nice, smooth trip, isn't it? That certainly is, Jack.  Well, besides you and me, it's going to be Rochester, Mr. Kitzel, Mel Blank, the sportsman quartet, and our guest star, Dinah Shore. Dinah Shore? Well, isn't she expensive? No, Don. She's nuts about me. And by the way, do you know who's going to be our guest on next Sunday's radio show? Who? My next door neighbors, Mr. and Mrs. Ronald Coleman. Well, aren't they kind of expensive, too? Just this time, I promised them I'd move. Good night, Don. I'm going to sleep. Ladies and gentlemen, figures show that each day last year, 1,100 American homes had a fire. You can stop fire in your own home by using just a little care. Don't smoke in bed. Have heating and electrical equipment repaired promptly. Fire prevention is your job. Thank you.