It's great that we have you all here, and that you all gathered today to learn more about JavaScript and search. And the coolest thing is, today, I have the pleasure of not just being the only one presenting this, but I have Zoe with me, who is working on the rendering team. So she is, yes, she's the one from the team that made the new Googlebot happen. So please, like, cheer and give another round of applause. Oh, well, it was a team effort, Martin. Thank you. And it's great to be here. Martin, I know you've done some work around JavaScript and search. I'd love to discuss with you if you have some time. Actually, I have, like, 40 minutes until I have to do the next thing, so let's talk a bit about it. But before, I would like to go into something else. You know, I talk to SEOs and I talk to developers all around the world, and it's great to do that. But I keep getting this sentiment, especially from SEOs, that JavaScript is, like, the worst thing ever, and it's the new flash, and it's evil, and you can't have a successful website if you're using JavaScript. So oh, oh my gosh, Martin, that sounds a little bit extreme. I think both developers and SEOs should work together to make sure their web content works well. JavaScript is a tool, and it can be used to make great websites, but every tool can be used incorrectly and do harm. That is absolutely true, and I think that's such an important point to drive home. I mean, it is an essential part of the web. It is what enables so many new capabilities on the web. At the same time, if you use it incorrectly or if you overuse it, that's a very, very bad thing. And I mean, we see that with things like this, right? We see the graph from HTTP Archive. We see that the amount of JavaScript that we are shipping to users loading our pages is growing and growing and growing over the years. So what I'm wondering is, with JavaScript being an essential part and a good tool if used right, but JavaScript being so much in use, how does Google Search deal with that? Well, we keep improving Google Search for JavaScript sites. At the same time, we make sure we keep crawling and indexing efficiently. That sounds very nice and airy, but do you have any examples for that? Oh, yes. OK. So let's start with the big news. You know Googlebot used to render pages with the engine from Chrome 41, right? Yes, the number one question I got and the number one question I asked you over and over again, it was like, hi, Zoe, long time no see. So Googlebot update, nor Chrome. So we're getting this update? Yes, actually, we already got the update a couple of days ago. So this means we haven't just updated it and we will start crawling your sites with it. We are already doing that. Yes, that's correct. So I somehow like I nearly missed the announcement on Tuesday. That was a little weird, but I think this is fantastic and this is amazing. And just to make sure to get that absolutely right, this is the latest stable Chrome rendering engine. Absolutely. Cool. So that is good news, but what I'm wondering is what does that mean for me as a web developer? Well, it gives you access to over 1,000 new features that is now available to Googlebot when rendering pages. That's really, really cool. I mean, that's not 1,000, but if you look around, you'll see that there's tons of new stuff. So that's great. So we have a modern web rendering service in Googlebot. That's lovely. But I have another question. Do you know what my next question is going to be like? Oh, your next question? Are you wondering if we'll get like four years out of date again? Yeah. So when do we get the next update? Actually, we'll update the render engine regularly. So we'll be more or less around the same as desktop Chrome. Give or take a few weeks. A few weeks. Something like that. We're not making any promises, but that's the idea. A few weeks. That's amazing. I love that. That's really big news. All right. OK. Let me get that straight. So modern JavaScript is the longer blocker for SEO. Absolutely, yes. And what kind of new features are these? Well, you can use pretty much any modern JavaScript feature, including let, const, a whole bunch of new array methods, and so on and so forth. Right. But that's JavaScript language features. What about new APIs? Yes. Many of those are available, too, like Intersection Observer. I hope for that one. So that's a fantastic news. And that probably also means if we have more of the APIs available in the browser, that I don't need as many polyfills as I used to. Right, right. You should still consider providing polyfills for older browsers. But if you have a polyfill that exists purely for Googlebot compatibility, you can remove them. Yes. So I think one of these examples would be I know that one of the JavaScript frameworks shipped polyfill for array.fill as an optional thing for Googlebot. We can, like, kill that. That is amazing. You know, that's great. And these ongoing updates will probably also mean that we update the user agent eventually, right? Yes, eventually we'll update the user agent string to reflect the version of Chrome that we're running. That's cool. So right now, we are telling people of 41 because we don't want to break sites that have it pre-coded, hard-coded. But we'll do that update eventually. That's great. That's amazing. So what else will the future hold? Speaking of the future. What else will the future hold? We're going to update the testing tools, too. We didn't get around to updating many of them yet. But look forward to that in the coming months for them to run Chrome as well. Right. So unfortunately, that means we wanted to make sure that we get you this upgrade as quickly as possible. But that means that we might have some rockiness on the way. But look at it from a different perspective. This means that if the testing tools we provide you with mobile-friendly tests and a URL inspection tool, if they say it's fine, it will definitely be fine. If you get JavaScript errors, you still have a chance to actually make it into indexing. But you have to double-check things. And I think that's OK. You're working on that? Yeah, we're working on it. Sorry for the glitches in the meanwhile. Things like that happen. I mean, there was a huge update. You worked on this for years. And now we finally have it. And I think it's great that you give this to developers and SEOs out there. You can now run modern JavaScript in Googlebot. And I think that's the real update to focus on here. And with all that said, I don't think this is a silver bullet. What I'm wondering is, as someone who's building websites, should I look at something else? Like, can I do something to help everyone on the web? Why, yes, Martin. You should keep your users in mind. Fair point. That's a good point. And look, this example page, it has quite a bit of loading time. It takes a while for the cat pictures to load.  It's lots of cat pictures. And I guess, like, for cats, you can wait a little bit? Yeah, but maybe we can do a little better. The browser streams the HTML as it arrives. But there isn't much that can be displayed right away. We got some script tags, but the body is empty. And the browser won't discover and display the cat images until JavaScript has been downloaded, parsed, and executed. Right, right. So what you're saying is, sure, I load a lot of images, but it could be so much faster. And the browser gives me the capability to do that faster for free. And I'm breaking that. Yeah, and it may hurt your users. Isn't there some way to use your JavaScript framework to produce HTML and ship that to the browser up front? Good question. And the answer is yes. But that brings us into this whole new world of web app architecture. So I think we need to talk a little bit about terminology. So I think the first thing that you want to probably look at is universal JavaScript. Universal JavaScript, that's the same thing as isomorphic JavaScript. Yes, because we don't have enough terms, we have to invent new ones. So it's like universal JavaScript, server-side renderable JavaScript, and isomorphic JavaScript. But it's pretty much the same thing. Cool. And that's just JavaScript code that can run either on the server or in the browser, right? Yes, absolutely. It's kind of nice. So JavaScript itself is a pretty agnostic language, but there's features that only work in the browser, and then there's features that only work on the server. And you want to make sure that you use the subset that works on both sides. And that enables us to do server-side rendering. Ah, yes, server-side rendering. Like the old in PHP days, when the server gets a request, run some code and generates the HTML that is sent to the browser. Exactly, except that we are not running PHP. I mean, you can, but we are talking about running the JavaScript from your framework code basically on the server-side and generating that. And what else is there? So server-side rendering has a few, well, not necessarily drawbacks, but a few characteristics that you want to not forget about. So one thing is it doesn't really give you the quickest response because you have to run it every request. So you can also do pre-rendering instead. Pre-rendering. That happens when you make changes, like at build time or on deployment, right? Absolutely. So basically, instead of doing it on every request, you're only running the JavaScript and you know that the content has actually changed. And that's useful if your content doesn't change that often. So it could be useful on stuff like landing pages, blogs, and so forth. Oh, absolutely. I mean, those are fantastic candidates for pre-rendering because when you have a blog and you know this content isn't going to change until I make an update, until I publish a new post or edit an existing post, then you can run the pre-rendering at that point and just be a static website the rest of the time. Cool. And by the way, I think I heard another term at some point. I think it was hydration. What's that? So hydration is the thing that every human should do properly. You should drink enough and keep yourself hydrated. But in this case, actually, it means something else. It's a variation of server-side rendering because what we discussed so far, pre-rendering or server-side rendering, the pure version just generates static HTML sites. Yeah. And just generating static HTML wouldn't be quite what I want if I'm building an awesome single-page web app. That's the thing. If you build a highly interactive app, you want this interactivity to still be there while the initial content should also already be rendered. So basically, yeah, that is what hydration is about. I see. So it sends the HTML to the browser and then upgrades it in the browser once the JavaScript is downloaded, parsed, and executed. Exactly. So that gives you this nice dynamic nature of the website even if you have the initial content in HTML already. And let's look at how that would look like in a project. So for instance, if I'm using React, I can use something like React Snap. It starts with my home page and then crawls all the links it finds and then generates static HTML for that. But that's pre-rendering. And unfortunately, if you have a regular React application, what you might want to do if you want to hydrate stuff as well on top of it, that means that you also need to do some changes to your code. So again, this is the main application code. You have to make this change that if you see that the root element has already some child nodes, then that means that we actually are in the pre-rendered HTML in the browser and then the app hydrates. But if it doesn't have anything in there yet, then we are on the server and then we need to basically to generate the initial HTML. And is there some other way to do this with React? Yes, especially if you start a project from scratch and have no old legacy code base, then I highly recommend taking a look at Next.js, for instance. I mean, it does require some changes, but it is definitely worth it. But I don't want to rewrite everything. OK, that's a fair point. So the thing is when I said Next.js, Next.js is like a higher-level framework in the sense of it uses your React components, but it gives you helpers for server-side rendering and hydration as well. I see, I see. So, right. This is that, but you might use other frameworks, right, Zoe? What is your favorite framework? Oh, oh, my favorite. I would say. My favorite framework is JavaScript, Mark. OK, well, yeah, vanilla JavaScript, that's a fair point, I think. But if you would be using other frameworks like Vue.js, for instance, you actually have options as well. You have three options for Vue.js. And the first one is the Vue.js server renderer, and that gives you SSR plus hydration. That's kind of cool, you know. And that. But you still have to rewrite a lot of your code, right? Yeah, well, you still have to have universal code in your Vue.application, so it's unfortunate. But, well, if you don't want to do that, there is another option. I think the second option is called the pre-render spa plugin. I like that because I want to be in a spa sometimes. Now, it's like SPA plugin, so it basically pre-renders your page like we saw in React Snap, but it doesn't give you hydration. So this only gives you pre-rendering and not the benefits of hydration. So what if I start a new Vue project? So similar to what we said about React, there's a thing that you should look into if you're starting a new Vue project. And I think the thing that I would recommend you look at is Nux.js. Nux.js is inspired by Nux.js. Surprise! The name is one-letter difference. It does pretty much the same thing as Nux.js for React, but it does this specifically for Vue. But it says pre-rendering right there as well. OK, yeah, you caught me. So it does SSR and hydration, but it comes with a command line interface that you can install. And then you can say, OK, this page, and this page, and this page, I actually want to pre-render as well. So you get to mix and match a little bit. I see. So you can choose one or the other. And what does the server-side code look like? Well, the server-side code depends a little bit. But let's say we use Express.js, which is a pretty popular Node.js server-side code framework or library. The first step is you create the Vue server renderer if you would be using the Vue server renderer option. I see that it creates a renderer with an HTML template. What's all that for? So the HTML template allows you to have the site-wide data, like the general HTML structure, and basically just the Vue application that runs just gives you the content inside that template. I see. And does this template allow interpolation of page-specific data, like the title or meta snippet? Title and meta snippet, yes. So in the next step, whenever a request comes in, because we are now not pre-rendering, but we are doing accesses R plus hydration, when the request comes in, we can specify the page-specific data, and that gets replaced in the template as well. I see. So that will produce a string of the template HTML together with the HTML generated from Vue.js, I guess. Correct, exactly. And once we have this HTML in the string, we can give it to the browser, and that's what it's about, really. Nice. And that works with your Vue.js components? It does, unless they're not written in Universal JavaScript. So you would still have to make sure that your JavaScript also runs on the server. You see a theme is evolving here, right? By Universal JavaScript. So we still have to make edits to make sure our code is Universal JavaScript. But what about Angular? How does it work? So for Angular, it's pretty much a similar story. The project is called Angular in Universal, and it does SSR plus hydration as well. It comes with a bunch of stuff. So if you use Express.js, for instance, it comes with this ngExpress engine that you can use, and you pass in the app server module ngFactory, which is a really easy thing to say. And yeah. So the ngExpress engine runs our Angular app code on the server and generates the HTML we can serve, right? Yeah. It's part of the Angular Universal, like all the hydration code and that kind of stuff piles on top of it. And you have to make some code adjustments, OK? But basically, you get SSR and hydration for Angular that way, and it's pretty well supported. But again, without Universal JavaScript, that's not a good thing. That was a lot to take in. Is there somewhere to learn more about all this stuff? Funny that you asked, because we happen to have made this YouTube video series that's called JavaScript SEO. If you haven't checked that out, go to youtube.com slash Google Webmaster, subscribe to the channel, and check out the JavaScript SEO playlist as well. Cool. Now, we have been talking quite a lot about server-side rendering, server-side rendering, real hydration, and pre-rendering. But last year at IO, I remember that John actually said something about dynamic rendering. So I think that dynamic rendering was this thing that you can use to pre-render, but only do that for bottom crawlers and SEO. So does that now mean that we have the new Googlebot after all? Does that mean that we can ditch that and it's going away? Well, we want site owners to focus on the user experience and content quality. For the time being, dynamic rendering may be useful, but it's not a long-term strategy. Right. But like, so what would be use cases for dynamic rendering then? First and foremost, it's a workaround. Unfortunately, not all crawlers and bots support JavaScript right now. Right, like the social media crawlers, most of them don't run it, and some other search engines don't do that well as well. Right, OK, gotcha. Right. But I think it could also be a stepping stone. Like it's a workaround, but it can be a stepping stone towards improving your website, because server-side rendering and hydration, that's a bunch of work that you have to do, right? Yes, yes, but remember that server-side rendering and hydration bring the great benefits to your users while dynamic rendering, not so much. Right, and that's because dynamic rendering basically only improves your HTML content coverage that basically is in the first stream that goes to the browser, only for bots, not for users. So users still get the slower site if they are unlucky. Yeah, that's correct. So consider dynamic rendering a workaround until other bots have caught up, or you have upgraded your website to server-side rendering or server-side rendering plus hydration. I think that makes sense, yeah. Phew. That was a lot to take in, wasn't it? That was like so much stuff in so little time. But I think it actually gives you all a foundation to build from, and I think that's a very, very important thing to do, isn't it? Like, do you like what you just got? Yes? But wait, there's more. So Zoe, I have got you on stage. I was wondering, now that I build sites and consider SEO, can I also test what I'm building and if it's actually working properly? Ah, well, good question. Let's take a look at a few tools. OK, fair enough. A great first stop is Lighthouse. It's right in your Chrome DevTools. Come on, I know that one. It has the performance audits. It has the practices. It has accessibility. But what does that have to do with SEO? Well, it's also got some SEO audits as well. And they help you improve your website's discoverability and make your users happier. Let's run the audit, and there we go. Here are your results. This is not looking good. I mean, whoops. OK. Yeah, 44 points. But no worries. Many of these are low-hanging issues and easy to fix. The best candidates are probably the title and meta description. Right, yes. Because if you use JavaScript frameworks, you often forget about these. And it's not always quite obvious how to make this happen in JavaScript frameworks. So let's look at React, for instance. React is a great framework. And if you use React Helmet, it's even better because you can do all these things. I React Helmet. Martin, I'm building a website, not going on a bicycle tour. What's that React Helmet for? You should go on a bicycle tour. It's quite nice weather outside. But similar to a bike helmet that might not look fantastic, but is really helpful, it protects you from not looking great in the. I mean, bike helmets oftentimes don't make you look great, but they make things work out for you. So it's similar to React Helmet. React Helmet allows us to add to our template and basically use any props in our component to set the title and the meta description to something that is specific to the page. Let's say I have a product detail page, right? I could take the product name and put it in the title and then some description for the product into the meta description. That's going to look fantastic in search results. Great, great. So this works for React, but what about other frameworks? Right, OK. So the other frameworks, Angular, for instance, has it built in. They're called the title and meta service. And they do the exact same thing. Got it. So here we have the same thing. We take the title and the meta description and put something that is in our component into them to show what's on the page exactly. And now that's Angular and React. You might be asking next, what is about ViewJS? ViewJS has an extension called View-Meta. It gives you this additional method in your components called the meta-info and it does the same thing. And so that's it? Oh, actually for ViewJS, you want to make sure if you use the ViewRouter to switch to history API mode. History mode? What's that for? So it defaults to the fallback mode, which uses hash URLs. And hash URLs aren't exactly great for crawling. I see. So maybe only the home page would be indexed. Yeah, because we're not really crawling this fragment URLs, right? We said that last year in the IOTalk as well. So that's no good. Speaking of no good, Martin, Googlebot only sees the placeholder images on your website. Wait, hang on. That's weird. It works in my browser. So why does it not work here? We have a fresh Googlebot and everything? Yeah, yeah. Well, do you maybe use lazy loading images? I actually do. And I do that like this is the code. So this should be fine, right? I mean, whenever you scroll, I figure out if the image is within the viewport. And if that is, then I load the actual image. So that should be good. Well, Googlebot does support lazy loading. But keep in mind, it may interact with the page differently from your users. In your case, Googlebot doesn't scroll, so the scroll handler isn't triggered and the lazy loading contents aren't loaded. Right. But I guess what I should be doing is I should use something else, like intersection observer maybe? Yes, you could use an intersection observer. This is an API that triggers a callback whenever any observed element becomes visible. It's more flexible and more robust. So I can use the same code to still load my images, but now it's more robust thanks to intersection observer. And that's supported in modern Googlebot. That's amazing. It is. So I wonder, can I also use the new native lazy loading that Chrome's getting? Absolutely. It's still an experimental feature, but worst case scenario, it gets ignored. So feel free. Ah, so that's pretty cool, because it's just this additional thing that we just ignored and it just works. OK, that's cool. That's nice. So you can't run, which is nice. So I can ask you another question, I guess. Is it OK if I ask you another question? Oh, yeah. Go ahead. So I was using Search Console earlier today, and I noticed that we have this weird thing called soft-for-force. Ooh, soft-for-force. No, sorry, not soft-for-force. We have this issue where my pages, I basically update my website, and then they get crawled, but not really discovered, but not crawled yet. So that's the one that I'm having struggles with. What does it mean to be discovered but not crawled yet? Oh, it means Googlebot hasn't indexed your page yet. Perhaps your site's crawl budget is too low for those pages to be indexed. What's crawl budget? Well, crawl budget is a rate limit on how frequently Google can crawl the site. Oh, could you go back to the slide? Oh, sorry. Right, let's stay here for a moment. So yeah, so it's how much Google crawls my site. Yeah, yeah. And we do this to be a good web citizen and avoid knocking over web servers with too many concurrent requests. Ah, OK. Is there something else that I should know about crawl budget? Well, crawl budget also applies to resources loaded from the page during rendering. What do you mean by resources? For example, JavaScript files loaded from script tags or XHR or fetch requests triggered by JavaScript. Those count against my crawl budget? Yeah. All right, OK, so I need to make sure that I'm not making too many requests, I guess. But one more thing, Martin. One more thing, we don't have forever to perform a render. And staying within the crawl budget can be tricky sometimes. To help with this, we cache certain sub-resources across renders. So that means that if I have multiple pages and they all use the same libraries or the same code, you don't fetch it over and over and over again. Correct, Googlebot might just fetch it once and then reuse it. OK, that's pretty nice. So what do you do if my site has an infinite loop? Is it OK? Is it going to be indexing what it's got so far? Yeah, yeah. If your site has an infinite loop, then at some point, we'll cut off the JavaScript and cut off any fetching that might still be going on and return the contents that we have up to that point. That's pretty cool. So that's nice. Is there something else that I should know? Yes, yes. Did you know that we put URLs we discover into a queue and crawl, render, and index them separately? It's not like Googlebot is clicking on links and going from page to page. Damn it. So that means that the render queue is still a thing. We haven't removed that even with a new update yet, right? OK, right. But what if I use, let's say I might have a website that requires you to set a cookie and only if the cookie is set after the set time, we actually show you the content. Would that work? No, that would not work. Googlebot does not store cookies across requests. So it always sees the page like a signed out user would. Right. OK, so it doesn't do that with cookies, but what about the other ways to persist data across page loads? Would you use local storage, session storage, or index DB? These APIs are available, but like cookies, they don't persist data between renders. So they're basically only available within a single render pass. All right, so that means I can't persist data across. OK, right, fair enough. But what about other things like service worker or cache API? Well, currently we don't support the service worker API. But if we did, every render would start with no service workers installed. Oh, right, because basically someone coming from search results is pretty much a first time user, so we can't rely on that. That makes sense. I think that makes sense. So in that case, whenever I use some feature on the web, I need to feature detect if it actually is present. Ah, yes, feature detection is a great idea. Progressive enhancement is a good strategy where different users might be on devices or use browsers with varying capabilities. But you should make sure and also handle the not so happy path. Oh, wait, so what you mean here is error handling, right? Yeah. I need to make sure that my code does that properly. So let's say, ha, let's say there's something like this right here. The idea here would be that I have localized content. So I check if geolocation exists. If not, I just load the fallback content. I think that's fine, right? And then when it exists, I just use the current position to load the localized content. Is that fine or what happens if there's a mistake? Well, imagine the getCurrentPosition function throws an error or an exception. Then your web page's contents would not be shown to Googlebot. Because the geolocation feature is available, but an error happens. Yes, this canon does happen to Googlebot. I've seen it more than once. OK, when? What kind of APIs could be affected? For example, I think this is in another slide, but WebSockets. WebSockets, all right, but also things that require permissions like mobile microphone, webcam. What do we do with these things? We deny all permissions. OK, I think that makes sense. After all, what would the webcam picture look like for Googlebot, like a server room or something? That would be weird. So I think to fix this, what I could do is I could basically just have an error fallback that also loads the fallback content. Yes, and making sure you treat these error conditions appropriately is important. You don't want to leave the mistake of leaving Googlebot or users without contents. Yeah, that would be a mistake. Oh, by the way, you're going to love this because this keeps happening to me. I noticed something in our performance report and search console. So we have the support page, and it is great, but it keeps losing impressions and clicks on the search results. So this is not exactly great, but I don't understand what's happening here because our code is perfectly fine. The site is on Google, it's indexed, and all the content is there when I test it. But there's something weird going on because we figured out that it's not actually fetching the data from the API, but we're not sure why. Ah, well, would you mind showing me the code, Martin? I mean, we are amongst us, so surely. Here we go. So our support bot basically opens a web socket connection and then uses the connect event to show a bunch of initial FAQ data and then give you a welcome message, and then it starts handling the chat code. This is what I mentioned earlier. And what I was worried about when you said your requests don't show up, we don't allow web socket connections in Googlebot for architectural reasons. Oh, OK. So that explains why we're not seeing the data. I guess making that static content and maybe even use the new FAQ structured data is probably a good idea. Right. That makes sense. So I have one more question. I have some time for that. Yes, we have a few minutes left. We have a few minutes left. So basically, I noticed that we have this soft 404 problem, and I'm not so sure what that means. Oh, a soft 404 means you gave us a 200 HTTP OK, but the contents look like an error page. OK, yes. That does happen in my single page application because my server doesn't actually know all the different routes and products that we are serving. So what we do is we give you the index HTML and then the JavaScript runs and figures out if that thing actually exists. And if not, it shows an error, but we can't change the HTTP code anymore. So what would I do in this kind of case? Well, you've got a couple ways out of this situation. You can either redirect to a URL that returns a 404 from the server, or alternatively, you can use the MetaRobots tag with no index. But why do I even have to care about that kind of stuff? Can't you just catch it for me? Well, HTTP status codes, Martin, they're kind of important. They tell Google about how to interpret the response we get. You tell crawlers and user browsers, this is a good URL. Here's some content, and all is good. I mean, that sounds good so far. But in the case of a soft 404, you tell us, this is fine. And then turn around and give us something that says otherwise. It's a bit backstabby. That doesn't sound good. Oh, and it's not good, Martin. HTTP statuses give crawlers and users valuable information. OK. So in that case, can you, like, elaborate on that a little bit more? Oh, all day. So for example, if you remove a page and give us a 404 status, we will remove the page from the index after a short while if it's not coming back online. I guess that makes perfect sense. And that's how it's supposed to be. But let's say this content wasn't removed. It has just moved to a new URL instead. We wouldn't know that. OK, that's fair, because I guess if we just remove it, then you have to rediscover it from scratch. And then you wouldn't know that there's a new thing somewhere else, right? That's right. And that's why using 301 to indicate a redirect is a much better idea. OK, so I got this. But I actually have an idea for you. So hold this. Like, this is, oh my god, I have a fantastic solution to the soft 404 problem. So how about this? I basically just add a noindex to all my pages, right? So the robot doesn't care. But then once I know that the cat that I'm loading actually exists, I change that to please index me. That solves the problem, right? Oh, well, that might not end well. Why? Look, we see a noindex early on. So we could stop the process right there and not take the removal through JavaScript into account. And all your pages would be marked as noindex in that case. So that would remove all my website from the index. That's a terrible idea. I understand that. Now, thank you very much for preventing that from happening. OK, right. Looking at the time, we don't want to hold you all too long. So I think it's time to summarize this a little bit.  But luckily, all of those things are edge cases, right? As long as you follow the best practices and do the right things as a web developer and an SEO, you should pretty much be safe, right? Right, right. And I think it's important to mention that we're continuously working to improve things as well, like the new Chromium headless, the Chromium in indexing. It's good stuff. Yes, and also, so that's the big one, really. But also, it's quite cool that we discussed server-side rendering and server-side rendering with hydration and pre-rendering, because that can also improve the user's experience of your site, not just the SEO side of things. Yeah, hydration. Yes. Also, we talked a little bit about something else, and that was testing. Yeah, testing plus one. Sorry, basically, early test, often. Absolutely. You don't want any bad surprises. Bad surprises, not bad. Is there anywhere to find out more about this stuff, Martin? Indeed, that's a very good question. So again, we have a YouTube channel with lots of content. We also do bi-weekly office hours if we want to hang out with us online and ask us questions. That's a great idea to do that as well. And don't forget the docs. Oh, right. We keep adding new docs all the time. Yes, that's true. And I think the thing that we, both of us, would love to take away from the session for you guys. This is the main point here. We don't want you to vary too much on building stuff for search engines. We want you to build great user experiences on the web. Yes. Our goal is to empower you to build great discoverable web apps and websites. That's why the new Googlebot is such a big leap forward. It is an amazing thing. And we will continue to improve Googlebot and generally Google Search with new features and capabilities. So please, please, please continue to make fantastic content for your users and blow everyone away that comes to your website. And with that being said, I would like to say thank you so much for coming to the Strat. Woo-hoo. You did it. You're very welcome, Martin. It has been a great pleasure having you. And thank you all, Adi-Ann. Thank you so much for being here. If you have any questions, we'll be around. You can ask us questions, follow us on Twitter, check out our YouTube videos. Thanks.


Finally, a bit deeper on the board. I like Mike Williams a lot. He is currently the wide receiver 40 for this year, but I've got him as the wide receiver 33. And a lot of that is because I want low-cost exposure to the Chargers offense. They've got a rebuilt offensive line. Joe Lombardi is there to be their new offense coordinator and it's a second year with Justin Herbert. All those things are things that make me think this offense is gonna score a lot of points. And if they do, Williams should benefit. He was a deep ball maven last year. He had 30% of the team's deep balls. If we look at just the games where Keenan Allen was healthy. In those games, Williams was volatile, but a lot of that was because he didn't score touchdowns. With that body type, you do expect those touchdowns to come. So to me, Mike Williams, a guy to target if you want to get low salary exposure to this Chargers offense, which I very much do.


So, thanks for joining us. We looked ahead to our rear-range game with Barnsley this Tuesday. Slightly obviously a unique situation, the fact that the teams were both put in and everyone was ready to go for the game last Tuesday. Do you expect Barnsley, I suppose, to stick with the same again? Are changes, obviously, perhaps, and they've lost this Saturday? Yeah, difficult to say really. From our point of view, we're just picking the team irrespective of what went on last week. Just looking at the lads of combat from international duty this morning, taking into account the travelling they've done. Looking at the mid-training and just picking the team we feel is going to give us a best chance of progressing tomorrow. As well as you mentioned those in nationals, obviously gives us one or two extra options than probably what we had last Tuesday. Yeah, Mezzah, Rory and Lee are all back. Obviously, Rhys isn't back with us until later in the week. We've got those three back, so that's good for us. Today was important just to have a look at them because when they're away you don't really get a chance to know what they've been doing in terms of their training load. So yeah, just had a look at them this morning and hopefully get the balance of the side right to have a real good go at Barnsley tomorrow.


I'm going to encourage everyone to take a seat if we could. Pick a spot for the moment that lets you see the screen up front because we're going to start with a little bit of a show this morning. So go ahead and just pick a spot and sit down and we'll start with a little presentation this morning and get you all oriented to what we know about Barry Street so that you can help us with what you know about Barry Street. Just some simple logistical things. If you're dying for a cup of coffee, the coffee shop sort of in the courtyard around the way is open. If you go towards the football stadium off to the right hand side as you're going through that courtyard as a coffee shop, at the end of the hall here are restrooms if you need them and we have a morning's worth of activity for you so I'm going to put you to work. I am grateful it's not pouring rain right now and I'm glad it was gray enough to get you to come out this morning so thank you very much for being here. This morning we're going to work on a little exercise because there is a City of Fort Worth project here that is going to consider new zoning for the area. So we're going to talk a little bit about the project. I'm going to talk a little bit about this kind of new zoning. We're going to talk about the charrette exercise that you'll be engaged in and then we're going to talk a little bit about some initial analysis. I don't know if you had a chance to kind of walk around and see these maps that were on the wall. They're also in a packet on your table so that you can use them and talk from them during the course of the morning as the discussion goes on and I'll show them to you in the show and point out some things that I think are of interest in each of them. So the goals of this project, overall this project got started because the T was expecting Tex rails new station at Klebern and Berry and that had implications. That meant that new development was likely to come in response to that new transit and of course that was two years ago when we initially negotiated this contract and we've been in limbo for a bit since and during the time that we've been in limbo the T has discovered that really the first phase of the T project for the Tex rail is running from downtown to the airport. We're two stops south of that. So we're not getting our rail station in that first phase. It is coming. It's inevitable that it will come and there will be a station at Klebern. I'll show you the station location that's been selected when we get there. But one of the early things was to make sure that development in this corridor is ready for that transit when it comes. That we have transit ready development. That we have better resiliency for these neighborhoods and by resiliency in this case we're thinking especially of the ability to bounce back after a big storm and specifically the stormwater and flooding issues that exist in the area. And then another of the project goals is to get the zoning tuned up to implement the community's plan. After the urban village plan was prepared there was really no implementing zoning prepared for that plan. And so it's been time for a number of years to get the zoning tuned up in the area. So there are a number of project partners working with us on this. NCT cog is the funding entity part of their sustainable development projects. They're working with the city of Fort Worth as the principal client. The T is involved, TCU as a major player in this area is involved, and of course the Berry Street initiative who really early on was pushing for changes in this corridor and is sort of key to making sure we head off in the right direction. So we have a project boundary that looks like this red line. And you don't have to understand it exactly. It's on the maps in front of you and we can talk about it some more during the course of the day. But that project boundary is basically about a block on either side of Berry with a piece coming down Klebern so that we can deal with the zigzag stuff that's there because Klebern comes through at an angle instead of coming through straight. So they've asked us to look at that piece as well. But mostly it's about Berry Street from the university all the way over just a little bit past Sixth Avenue right before you go under the viaduct there under the other rail line. So there is also a parallel project and we've asked them to join us here today and so during the course of the day take a few minutes and come up front here and have a look at what's on this front table because the entire watershed here which is being called the Zoo Creek watershed. So a larger area is also being studied. The stormwater challenges of this area are created by something more than just Berry Street and those need to be dealt with on a larger basis. So there's a parallel project working on that. So let me introduce the project team. So my name is Lee Einzweiler. I work with Code Studio out of Austin, Texas. I have two people from my office here today, Colin Scarf and Megan Scornia. Our firm is mostly works on zoning across the country. We've successfully completed zoning codes for places like Denver, Raleigh, Memphis. We're working on Los Angeles's code right now. We just finished one for Cincinnati. So zoning is kind of our thing. But we love to plan and zone at the same time which is a little bit of what we're doing here. We've brought with us then a team that includes this stormwater team. From half associates we have Ben Pilant and Terry is here, Francois de Cope is here. Anybody else from half? No? Good. From the DeChaiso group who is doing our transportation and parking, we have Tom Simerly in the back corner of the room here. Civic economics, Daniel Houston is here. And did I see Don? Don is here from Birkenbaum Landscape Architecture. And in addition, then our public outreach is being handled by Open Channels Group and Janaba is here in the back. She has reached out. Hopefully you saw something digitally or you saw a sign somewhere or something else. Those are the kinds of things that we are trying to do to make sure that we can get some people here. So what are we working on in this project? Well, we have some key steps. We had initial analysis, some of that is completed and you'll see the results of that today. We have the charrette for public input right now. Following the charrette we'll be working on this development plan which is the foundational document for doing the new zoning and finally the form-based code itself. So at least two more key times you'll see us when we bring the plan back to the community and then later when we bring the zoning back to the community. So what is this whole form-based code thing? Well for a long time zoning has been a whole lot about use. We cared a lot whether you were the butcher, the baker, the candlestick maker, right? And we carefully sliced and diced the city to say butchers and bakers over here but not candlestick makers but candlestick makers can be over here but not butchers or bakers. And in doing that we missed out on a lot of the fundamentals about the character of the places that we wanted to live in. And form-based codes are really a call for change, a call for a new approach to thinking about zoning focused much more on the form of development, a much more long-term vision of things and not quite so much on use, doesn't mean use is not part of the package. So the zoning structure usually is use and density, some management issues and some form issues. And unfortunately conventional zoning what we've been doing for a long time is kind of weighted like this, heavily towards use and density as the most important controls and failing to deal very effectively with form. Whereas form-based zoning really gets at form and takes a lighter touch on use. And so how do we illustrate that? Well usually planners use red on zoning maps for things that are commercial. So this is red on a zoning map and so is this. And if we actually care about which one of those we want then we can't be use-based and we can't be totally focused on density and intensity. There's some other things about the difference between that picture and that picture that matter about that commercial development. And that's what we're here to talk a little bit about. So some of the basics, the placement of the building. Where the building is far away from the street we waste infrastructure in building these kinds of streetscapes up front that are parallel to the sidewalk the shopper is actually on back in front of the store. We get the parking location wrong.  Right out front. And so when we set up parking location right out front however in certain settings we run over little Susie on her trike as she's trying to ride her trike around the block. So the parking location really does matter. The same form without the parking in front makes a big did a difference. So height is one of the other challenging things. When we measure height only in feet we get Paris. We get Washington D.C. We get South Lake Texas some of you might recognize. Everything the same height whereas when we measure height in stories and feet we often get a more varied answer to our street fronts. So how you do these things how you regulate makes a difference to what you end up with. Now in height of course the biggest problem is whether you think the change is too extreme. If you've driven around your own streets here that's local. Windows and doors seems like we shouldn't have to tell people to put windows and doors on buildings right but actually we do have to tell people to put windows and doors on buildings. Use is now sometimes as much as anything about what goes in the ground floor and how might that be different from what goes in the upper stories. So is there residential or offices above retail that might be an important distinction here. And finally public realm kinds of questions. This is a street in Alexandria Virginia that probably carries at least two times and maybe more than two times the volume of Berry Street. And yet the pedestrian feels safe crossing at the mid block which would not likely happen on Berry Street unless you're a daredevil. So the point is that a modern code if you want this end result on the right hand side not suggesting this is what we want for Berry Street but if you know what you want you can code for it and that's the idea here. So what is today? Today is really an opportunity to involve the public in the design of what we want and in this case we'll be confirming a lot of the past work that the public has done. So you've got the station area plan and some other plans in front of you the urban village plan just want to make sure that stuff is still real. Want to make sure that you understand the zoning that's in place now and the height that it might allow and make sure you're comfortable with that. We're basically going to be here through Wednesday and on Wednesday night right here we'll do a final presentation of where we think these things are headed. So you get a chance to come back and see us fairly quickly. This is our week. It includes this morning's session. For those of you who are interested one of the nation's best experts in pedestrianism Dan Burden is going to lead a little walk this afternoon. It's part of a parallel project called Blue Zones. I don't know if any of you have been involved in that but the Blue Zones project is bringing Dan Burden and I encourage you to take advantage of it. Be a relatively short walk one mile total I think is what they're thinking a half mile out and a half mile back. It's going to meet at University of United Methodist Church at 1.30. A lot of us from the Charette team are going to go just to see Dan in action. In addition our design studio will be here on the third floor in the ACAF room and you're welcome to come back during the week and see what's going on. We'll be presenting that back to people in a casual fashion in a pinup that you can just drop in anytime on Monday night that open house and we'll be doing our final presentation then on Wednesday. But there are two other opportunities. If you are narrowly interested in what's going on with the economy in this specific area you can come at Monday at lunch. If you're narrowly interested in what's going on with stormwater you can come on Tuesday at lunch and we'll do a separate little lunch and learn session.  Anyone is welcome. So what is this process like that we're engaged in this week? Well I'm going to show you some of the pieces and give you a little sense of it. We study the area. One of the things we're already battling about is how wide are these streets? What's the stormwater problem? Can we reduce the stormwater problem by reducing the size of the streets? Is there any way we can get at some of those fundamentals that really would make a difference here? Asheville, North Carolina while we were studying the project area. This is the neighborhood design workshop. We run them on Saturday morning because we find we typically get the best turnout. It's delightful to have you here today. We're going to design with you today at the tables and at the end of this session we're going to present back. When we present back you'll hear what's happened at some of the other tables so you'll also get the opportunity to sort of see what others might have been talking about. There's Dan's walking tour. Dan is the huge mustached man.  We run an open design studio that you're welcome to come join us in during the course of the week. And we will be running a series of technical meetings where we have the representatives of various city departments and other entities coming to see us formally and talk to us about the ideas and make sure that we road test them. The drop-in open house is something you can swing by on Monday and on Wednesday we'll be doing a presentation of the work in progress that we've gotten to by then. So let me show you just a little bit of our initial analysis. So one of the things is how many of you actually live within the boundary, within the red line on my project area? Anybody? Ooh, a couple of good. Oh, and one in the back. Awesome. But how many of you live on this area map? Does everybody else at least live on the map? We have a couple of outsiders, I know. But for us, it's important to kind of get a sense of what's going on in the place. So we made this map to just kind of say, the medical district is a huge influence. It's up here. This is the shopping over here, et cetera. So if you think that there are more things that we should know about the general area, feel free to mark those on your map as we go through the course of the day. There's an aerial photo included there. If you guys need to look at sort of what's on the ground today, that's in your packet. One of the things that we always look at is the block pattern. And around here, the block pattern is really good, except when it's not. And when is it not? Can't get through the high school site. Got to go around it. And for the most part, can't get through the university site. Key places, admittedly, we can get around. It's a small university, and so it kind of works. But there are some very large blocks of land with no streets in them. The building footprints, one of the fascinating things when you just look at the buildings is you can definitely see where the residential neighborhoods are and where the commercial activity is. And you get a pretty good sense of the place when you just look at the buildings themselves. You can see the industrial components up along the train track. You can see the schools. You can see the grand mark shows up like that wonderful figure eight now, and the university. Existing land use is included in your packet in case you're sort of curious about what's going on there. The extent of the flooding in the area. Now, this is a composite image that we have made. The stormwater folks have a more accurate image up front. But in general, the lightest color is the extent of 100-year storms inundation. So it might be only an inch deep, but it's actually water on the ground. The darkest one, though, is the inundation you get from the two-year storm. And the fact of the matter is the two-year storm inundation is almost as extensive as the 100-year storm, which tells you that you're flooding a lot in very minor storms. Our understanding is that the pipe system here holds about an inch and a quarter of rainwater showing up in an hour, for example, fills the pipes. So when you hear about a storm that had three inches in an hour, it's going to flood. And those are the places that will flood. Major transportation. The T station here is shown just south of Berry at Cleburne. You can see that there. And of course, you all know what the major street network looks like. We have included some existing parking counts. We literally went and counted the parking lots. And we did not count the garages, but the garages are included there. You can see them marked with a big G. The bus routes and their stops, the bicycle system. One of the fascinating things is that a decision was made at a certain point in time that university north-south is an acceptable route for bikers to ride on. But Berry east-west is not. And so the bike route system set up by the city shows alternate routes other than Berry as the key bicycle routes. The neighborhoods, this is as much for us as anything.  But this is to help us understand the neighborhoods. I guess one intriguing thing is, of course, there is a huge hole here between Blue Bonnet Place neighborhood in Rosemont that is a neighborhood that doesn't have a name and is underrepresented. School attendance zones would be fascinating to match this up with home value. It is a significant impact in this area. Renters versus owner occupy. This is a fascinating map which tells us the things here are actually more normal than one might expect near a university. Part of that is because so many students live on campus and actually they're pushing, of course, to get more students on campus. The year in which the homes were built, to us, this is fascinating to see the patterns and then be able to go look at the housing in those areas based on the years that they were built. The existing zoning in the areas included in the packet. And more importantly, the height allowed by the existing zoning. So this darkest blue along the Berry corridor is 60 feet of height, which is allowed by the zoning today. And in fact, the university's ownership to the north of Berry is actually in a planned development which might allow more height. The grand mark, for example, I believe exceeds the 60-foot height limit. But for the most part, the corridor to the west of Cleaveron is that 60-foot height. And then as you move further east on Cleaveron, it moves down to 45 feet. The neighborhoods are mostly at 35 feet with some along university, especially there at 32 feet. Future land use, which really is a question of some plans that have been done recently. So these are some existing plans, the so-called Goodman Plan, the Urban Village Plan, and the Station Area Plan. There are some little excerpts on your tables that you can have a look at if you'd like. But basically, the most important in our minds is the Urban Village Plan, which claims to be a consensus plan. Here's the drawing for it. It's made up of these various building blocks, which are explained on the pages before. So one of the questions today has to be, do we believe the Urban Village Plan? Is that really what we want to achieve in this area? And make sure that we're all on the same track. The Station Area was originally thought through as a fairly significant transit oriented development, in which the station and a big mixed use development would take place in the triangular piece right there south of Berry. On the other hand, I'd like to share sort of the most recent plan by the T. Because the station is not coming yet, they have bought substantial land and cleared the houses. You can see it down there. It's really the open space that's there. It's about a half of a block between Wayside and Frazier. But it reaches all the way over the little triangle to get to the track area. And it would allow for a bus transfer station as an interim use of that site. The principal reason for this is because it's very hard to get from the Cleburne bus routes to the Berry bus routes. It's a dangerous intersection to be crossing. And if they could actually bring the buses for both of those routes through this transfer station, it would give them a great opportunity to transfer in a more safe way. So that's what's shown here in the little drawing is the buses queued up for the transfer facility and then some parking that would be associated with the station area. So what we'd like to do now is put you to work. And that work is going to be facilitated by someone from our group. What I would like to do is see if we can somewhat consolidate the tables. So it looks to me like we have about five tables worth of folks. So let's try and use these five in the front of the room.  On the facilitator sheet, there are times set out there. And they're going to kind of manage our time for the next while and help you work on thinking about the future of Berry Street. So thank you very much. And let's go to work. Last flood, it only lasted about 30 minutes. And it kind of went right in between here. And we helped them through our building sink, because we had. Though the adjacent property is not here.   And you're welcome to come see sort of where we're at. And tell us whether you think some kind of course correction is needed, whether we're headed the right direction or not. And then as I suggested on Wednesday, we'll be back here to do a more formal presentation of that material as far as we've gotten during the course of the week that we're here. So I encourage you to get people involved in those ways. In addition, the design studio, which will be here in the ACA room, is open. We have technical meeting schedule. We have other things scheduled. But people can stop by the design studio, who didn't get a chance to come by here Saturday morning. So if there's someone you think has a strong opinion, especially about a narrow issue that they just want to point out to us and help us understand, it'd be great to have them simply drop by the studio. The basic working hours are, if you consider it, a little bit like the business day. We'll be here beyond that. But it would be nice if we had some working time without visitors. So we are hoping that people will simply drop by pretty much during the working day. We're showing the design studio open until 7 PM each of the evenings. So that's one element. You can follow along the project on the city's website. And that's the best way to link away to something else. Katie, who's been here, and Artie, who's been here. Are they both here somewhere? There's Katie and Artie. Are the city's representatives? You're also welcome to reach out to the city planning staff and talk to them about this. I want to remind you of just a couple of things. Some of you came in a little later. And maybe you didn't take a moment and sign in, which is fine. But if you'd sign in on your way out, that would be great. Also, you have full page comment sheets if you really feel like writing us a message. And then you have a little idea sheet there. We'd love to get both of those back. You can drop them off at the sign-in table as you leave as well. And finally, those of you who want to take the walking tour, it's meeting up at the University of United Methodist Church right there at Barry and Forest Park. And that will be at 1.30 while the weather is not great. It could have been raining or 95 degrees. So I think it might be a good afternoon for a little walk. So with that, I'm done with the formal portion of the show. And now I'd like to have those of you who've been designated to introduce your big ideas from the tables come up and join me over here. So who is going to represent table number four? Come on up. So three big ideas, if that's what you've got for us. I'm Alicia. And I'm Linda Joe. The three big ideas we talked about was an accessible park that was walkable. One issue that we have in where I live and around here is the sidewalk issue. So making something 36 inches wide for wheelchairs to access and then be able to enjoy a park. Also, our second idea was really talked about hiring an architect while preserving the site and the culture of the neighborhoods and everything, not constricting innovative design solutions and sustainability. Our third idea was reducing the hardscape. We've got the areas closer to TCU that have been redeveloped. But then as it goes farther east, it kind of breaks down. So you get the parking lots as your streetscape, moving the parking to the rear, and more landscape. Yes, and so going back to the sidewalk issue, making sure the sidewalks continue downberry street, all accessible. And we know that multi-use facilities are a part of the design. Having those include some three-bedroom housing for small families. We don't feel there's really a market for that. We talked about the height. Right now there's a five-story building on the street and if that's max, maybe that's OK, but having a variety down to one in two stories. And then just being material conscious as far as what we're putting on here and making sure it looks like it fits in. Did you want to talk about here? And we were interested in there's, as you go down the downberry street, some of the buildings are old and very dilapidated and they're empty. And I'm actually part of an organization who would like to tear some of those buildings and rebuild prettier buildings and repurpose them for use to help coordinate with agencies around TCU and TCU and the medical district and everything. And just make it more beautiful by getting rid of old buildings and putting up prettier buildings. I appreciate that. And who's on table one? I think, by the way, that's the first tag team report back I've ever had, so that was good. Table one? Oh, thank you for volunteering. I did not volunteer. I was selected. I'm sorry. Yeah, how are you all doing? My name's Todd. Actually, I'm the associate vice chancellor for facilities here at the university. So I have a little bit of pro-keel perspective on this, except for the fact that we all agree that vibrant community is important to all of us. So we had three. Actually, we ended up putting four issues on there, so sorry, you got to listen to an extra one. One we talked about was flexibility as we developed this. When we were looking at the corridor along Barrie, recognizing right now that the current plans call for many facilities that look and feel like the Grand Mark, the six plus story, very large on the curb, as a university, recognizing we are a prominent property owner through this is the opportunity for that town-gown relationship that could embrace the university rather than kind of hide it behind a bunch of very tall retail apartment buildings. So some flexibility that would allow some development here that would feel more along the lines of the institutional field of the university. Up and down university boulevard and such. Walkability was very important, not only from this particular stretch of Barrie, but throughout the communities around here so that there would be some interconnectivity, some of the opportunity to walk on the street, but as well as opportunities to get to the streets. Many of the neighborhoods and places don't have easy sidewalk access and such. And along with that, the physical piece of that is also the safety and security. So that then you start talking about lighting, you talk about the uses of the spaces and just a vibrancy that would make it safer for people to work. Again, the three is kind of the same as we talked a little bit of the flexibility to embrace the university. The university has a, we are growing in national prominence. We think we have something to provide to the community and it might not be retail and apartments. And then I think really what one of the most important things that we talked about was a fourth was transition. Whether it be between retail and the university, whether it be between the university and the neighbors, whether it be between retail and the neighbors, is that we will tend to focus on specifically what's on the street, but what's really gonna be important is how you capture each and every one of these requirements and then transition them from one to another. Whether it be a walkable space that transitions to a retail space that transitions to a neighbor, that transitions to a park, that transitions to a university, that that's really where the fine tuning is gonna have to go to image facilities on the road is one thing, but to actually work them so they transition between uses, I think is gonna be the big challenge for all of us. Thank you, Todd. So how about table three next? Who's representing table three? That's you guys. Come on up. Okay, my name is, okay. Okay, thank you, Keith. My name's George Appleby, 2909 Bemberg Boulevard here in the TCU area. And we came up with several ideas to help make this transition, but mostly Jim and I, one of my neighbors have come up with some negative responses. We'd like to see the city address before they even do anything else. And that's the issue of crime, code compliance and too much traffic in our neighborhood, which I think would help the area, a lot of potential. We'd like to see more traffic choke off in this area and maybe some parking over by the TCU area centrally located for Berry Street. Good friend Faith over there said she would like to see less efforts of blocking traffic off to her street on Sandage off of Berry. You want me to say that? And her husband Jim fixes traffic tickets if you need a traffic ticket fix. Okay, Keith tried to squeeze us on a decision on a transition area from the single family homes to the big buildings on Berry Street. And the only thing we could come up with is maybe townhouses and Jim and I both, we're not speaking for the whole neighborhood. We're just speaking, that's our opinion. We'd like to see either townhouses or single family homes and then maybe a park-like atmosphere between them. Let's see, a little bit more green landscaping and more single family building in the area. Instead of buying a home and turned down building a foreplex, how about a single family home, okay? And that's basically what we came up with. That's good, thank you very much. Let's give him a hand. And our final table number two, oh, do we miss one? We're very disturbed because we didn't really come up with these all enthusiastic ideas. But you definitely need the, I'm gonna say next sentence, but when you do that, it's all typically what the building looks like. You don't look like that in the middle of the minute. People who have true concerns. So, Keith is sorry, he's sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. I'm sorry. Thank you very much I'm sure that we didn't get that so you did? Sure. This problem is going down before you change the selling on this. We need the October by the way. It's nice to destroy something like this. You have problems for so many planning with three hours ahead of you your position, There is easy to do to resolve before you go forward with anything. And that's to show you that we will please protect this period and instill form for it in all campuses. Okay, I'm Martha Jones. I live at 3136 Wabash Avenue, and we spent a lot of time talking about what doesn't work before we came up with what would. And I was at that zoning hearing too, and I feel like that has to be incorporated as well into our ideas because if the neighborhoods disappear, then I think it will really deter what could happen here. We came up with three general ideas. The first one was to preserve the adjacent neighborhoods so that density occurs within the Berry Street corridor. We didn't talk about transitions, but that's kind of an underlying thing, a part of that. The second idea is we came up with the form-based code that should honor the Urban Village Plan, providing walkable, dense, diverse, or diversity with a mix of uses, both commercial and residential. And then the third idea is to retain affordable housing east of Cleveland Road and encourage affordable housing west of Cleveland Road. Thanks very much. So I think it's kind of fascinating. There is a little similarity to what some of the conversations have been. There's certainly a lot of food for thought for our team and the designers. I will very clearly state I can't fix code enforcement. I can't fix some of those kinds of things, but it doesn't mean those issues aren't going to be reflected in the material we pass back to the city. So those ideas have been heard. They're going to be part of the way that we report back on these issues. We look forward to seeing some of you again. We hope during the course of the week we'd like to see you Monday night drop in and see where we're getting at. And Wednesday for the final presentation, if that's all you can spare, that would be great. So thank you all for coming out today. And we hope to see you again. Thanks very much.


Going on, everyone. Sam here, late in sports cards. I'm in 23, top scone, black, baseball, hobby, 12 box. Case number 8, pick your team style. Names and teams, for some reason they're not in the right order. Alex G with the Braves, Angelo D. Marlins, Brian A. Reyes, C. Hwang, Padres, Chris S. Redsox, Darryl M, Guardian's Giants, Edward P. Cardinals, Jeremy H. Twins, Jesse K. Yanks, Jonathan H. Phillies, Jordan N. Rockies, Junya S. Tigers, Kayla D. Bax Orioles, Lee Wan-Wai, Angels, Mark L. with the Mariners, Mark A. Astros, Nelson S. Brewers, Potion H. Royals and Pirates, Ryan B. Royals, Scott J. Cubs, White Sox, Athletics Nationals, Simon M. with the Dodgers, Stephanie Reds, and then Vaughn with the Rangers and Metz. So good luck here, everybody. Stephen J. with the A's Tigers Guardians in the next one. So half the teams off the board. Thank you, Stephen. We are down to just the Brewers, Giants, and Nets. Only teams left. Only spots left on the morning here. Morning slash afternoon. So very easy day. You guys killed it as per usual. That's customer base in the entire world. So do appreciate you all. Oh, okay. I got you. I got you, Paul. Absolutely. I got you. I got you. What's up, brother? Yes, sir. I do know that. Let's see it, man. There's Adley Rookie. Blue to 75. Shohei. There you go, Angels. Very nice. And then A. Corbin Carroll. That's a good first pack. Very good first pack. First auto is going to be Gold Mini Diamond. Andrew Jones, 23 of 50 for the Braves. Very cool. Let's go, man. Potential Hall of Famer this year. I personally think he still has the weight of year or two, but he very well could make it. Who knows? Who knows? All right, Tim Anderson. Refractor KB, Chris Bryant to 199. And Mike Trep. Thank you, Mr. Scott. With the Giants and Nets, just the Brewers left, everyone. Just the Brewers left on the day. And Ozzie Smith, the Wizard. Nice one there. Cardinals. Congrats on that. Very cool. That is a Shea Langlairs Rookie. Gold Mini Diamonds. Zack Neto, 50 of 50. Rookie for the Angels. Nice. Grats on that, Los Angeles. And an Oswald Paraza. And Oswald Paraza. And we've got Auto for the Mets. Petalanzo. Nice one there, Vaughn. Polar Bear. Petalanzo Bay Sauté. For New York. Three really nice autos so far. Three Vets. Couple of legends. All right, Volpi Rookie for the Inks. What am I supposed to do? There's a 299 Shohei Otani. Another one. Ball in Jersey, not for Polar Bear.  Let's go, Scott. And Braden Shoemake. All right, let me drop you guys a link to Fanatics Live with Rich. He's got five to go in his next case. Rocky's available over there. Again, that is a six-box half case he's doing. He's ripped through a bunch of them so far. He's got like three breaks left. He's got five, seven, and 24, everybody. Five, seven, and 24. So three breaks left with Rich. That is gonna be the big hurt. Frank Thomas. Grats on that one there for the White Sox. That's the one we get, Sam Trigger, just taking off as Frank. Was that you? Let's go, Scott.  That's awesome, man. Josh Young Rookie. That is a purple Francisco Lindor to 150. Lindor. Lindor. Yeah, give it. Shift. Will you mind showing them the door? All right, take it away, Penny. That Penny is such a beautiful, yeah, such a way with words. Tom Glavin. Nice one there for the Braves. All like really solid vets so far. Like everybody's a Hall of Famer, basically. Other than Peter Lanza, who's still active. Got gold coming up here. Miguel Amaya to 199. That is a gold Yordan, 32 of 50. Yordan Alvarez and Dominic Fletcher. Hell yeah, Dylan. Let's see it, man. And we've got a Kyle Stowers. Refractor, Rookie Otter, 150 for the O's. There you go. Is that Kayla I want to say, right? There you go. Kayla, it's a good start. See if we can continue on with the Oriole Rookie Autos. That'd be nice. Or the Diamondback Rookie Autos. Nice. Good stuff. Good stuff. We've got Bobby Witt. That is a Gunner Henderson on the variation. There you go, Kayla. Nice one there. Gratz on that and a 199 Matt Olson. Gratz on that one there, Braves. And Paul Goldschmidt. Nice one for the Cardinals to go with the Ozzie Smith. Not bad. Former MVP. Absolute stud. Another potential Hall of Famer. Potential. Not for sure. Wouldn't say for sure now. It's harder in baseball to make it than any other sport. I feel like football needs to give it out. Yeah, football is bad.  Basketball, if you go to the stadium and have a poll, so you're all famous. There's Corbin Burns. There's Salvi Perez to 150. Gratz on that one there, Royals. And then Luba. There's also Gold coming up here, I believe. True Gold for the Cubs. Caleb Killian. Rookie Otto, 34, 50. Nice one there, Cubs. And that's Scott again, right? There's Scott J. Yes it is. There you go, Scott. Good stuff, buddy. True Gold, Caleb Killian, Rookie Otto. Can never hate on a True Gold, the 50 from Tops. Let's go, baby. First round buy right now. Come on. Right. No, I agree on that, Caleb. We've got one of those either Ivories or the Finest Features. Got one of the Short-Friend Thoughts. Not seen an Ivory yet. No. Seia Suzuki. Green to 99. Masataka Yoshida. Nice one there for the Sox and Luis Castillo. Let's see what this is all about. Looks like the, essentially, yeah, the Ivory. It is Albert Pujol, 6 of 30. There we go. Yeah, Ivory Autograph Card. These are fire, man. Those do look really clean. That is clean. I wasn't sure of it looking at the picture on the website, but looking at person. In person, this looks gorgeous, dude. That is sick. Going to Edward P. and the Cardinals. Congrats, buddy. That's a really nice card. Really nice card. Yeah, these Ivories are sweet. The Checklist. Let me just run you guys through the Checklist of the Ivories really quick, too. That looks like a pristine card. Yeah, absolutely. That looks like it. Absolutely. So here is the Ivory Checklist. Aaron Judge, Albert Pujol's, Adley Rochman, Corbin Carroll, Francisco Alvarez. Gunner Henderson, Gabby Moreno, Ichiro, Josh Young, Juan Soto, Michael Harris, Mariana Rivera, Mike Trout, Riley Greene, and Vladimir Guerrero Jr. That's a pretty solid card. That's a good Checklist, man. Now you did. You called that, Kayla. You called that for sure. Good stuff right there is right. That was awesome, man. Riley Greene, right? Bobby Miller Rookie. Blue Lava to 75, Ozzy Alves. That's on that. Braves and a Mookie Betts. That was a great addition, those Ivories. And Trey Turner on the Auto. Nice one, Phillies. That's Philadelphia. Very cool. We still just have the Brewers left in the next one. All right. Yeah, just the Brewers left in the next break, everybody. A lot of pencil out, I know. Just the Brew Crew. All right, Clayton Kershaw. Greene to 99, Trishon Kossus for the Red Sox. And Ozzy Alves. Slammin' Sammy Sosa. Scott, congrats, buddy. Nice one there. Sammy Sosa. Carrie Bonds is in it. Yeah, Travesty. Very nice. There we go, Scott. Take that, buddy. Nice, man. Let's go. Happy for you, Scott. You got a green auto behind it. These cases have gotten kind of crazy these last two. They're getting better. They've gotten kind of insane. Tanner Bibby Rookie. 2199 Yuri Perez. And Byron Buxton. And then we've got a green Eggy Rosario. One of 99 Rookie Auto for the Padres. Congrats on that. Yeah, but he's also on the Tiger, so no one cares, unfortunately. All right, do a quick recap here. Some of our base autos. We've got Sammy Sosa. Trade Turner. Paul Goldschmidt. Tom Glavin. Frank Thomas. Peter Lonzo. And Ozzy Smith. Wow, what a bot. All right, so our caller. These are the non-autos. Gunnar Henderson Variation. 2199 Yuri Perez. Matt Olson. Miguel Amaya. Chris Bryant. 250, Salvi Perez. Francisco Lindor. 299 Shohei. Masatake Yoshida. Trishon Kossos. To 75 Ozzy Albis. Shohei. To 50, Zack Neto. And Jordyn Alvarez. We had Kyle Stowers. 2199. Eggy Rosario. 299. Gold is Andrew Jones. Caleb Killian. And Albert Pujols. 230 on the Ivory. Sick one there. That'll do it for the break, everybody. Thanks again for the fill. Up next is number nine and five.


Hey guys, it's Nate, AKA The Foot Accountant. Welcome back to the channel. What a weekend it has been on FIFA 22 in foot birthday because EA, we thought one-pack glitch was pretty crazy. Two days in a row now, we have had different packs and SBCs inside of FIFA 22 that have been glitched giving out the incorrect rewards and it's dropping prices on the market because people are selling cards from their teams, going and trying to get the tokens or the SBC fodder that they need to get these SBCs done and to try to do the SBC or get the pack during its glitched state in order to get compensation, right? That's kind of what's been going on this weekend and two days in a row, we have had this happen. First, yesterday with the mid or prime icon player pick that was giving out icon moments cards and then of course on Friday, you guys remember the foot birthday team one-pack was giving out cards from foot birthday teams one and two. So we're gonna talk about all of that madness and how it's impacting the market because prices are down even further across the whole entire game. We were looking at this Mbappe card yesterday at what, 630,000 coins? Yeah, now this guy is like 570K and he was even a bit lower than this because so many people are going out and trying to do that icon glitch for the mid-prime player pick while it was active to try to exploit that a little bit and it's a pack glitch, right? It's not like a gameplay glitch where you're really gonna get banned from it because you can say, hey, I was just trying to do the SBC to get the cards from the pack but everybody kind of knew there was a glitch going on with that. So we're gonna talk about that today, how it impacted the market and of course today on Sunday is a really, really big day. Many release, more foot birthday cards coming into packs and there is a massive, a huge foot birthday player SBC that is scheduled to be today. We're gonna talk about that in this video as well. So if you're enjoying the uploads, make sure to hit thumbs up and of course, subscribe if you are new. Now the SBC yesterday on Saturday that caused all of this craziness is the mid or prime icon player pick SBC. Now it's out and it's repeatable but it is only, you can only do it once and then it resets every couple of days. So I did it yesterday, I rarely do these SBCs. I saw that it was glitched and the glitch was it's a mid or prime icon player pick but it was giving out icon moments cards. A lot of you guys know this but just to cover it quickly, for those who don't, this player pick was giving out icon moments items. I'll even show you the player pick that I did on my companion app. I did the SBC and I got prime gigs, mid-stoy clock and moments, that's IE. So I was able to get a moments player from this player pick. I obviously took this moments that's IE but this is the SBC that everybody was running and doing yesterday, right? If you take a look at some of the comments on this tweet, you know, look at the cards that people are packing from this. Moments Zanetti and moments Bergkamp, brand new moments icons. There's a moments right in that one, right? Let's see, some people weren't getting moments cards but a prime Pushkas, okay. And then other guys like, I don't even know if this is real or not but like Maldini, Hullet and Roberto Carlos, that screenshot looks a little bit sus but I'm gonna believe it and that's nuts. That is nuts. Look at this, bro. A moments Cruyff and a moments Zanetti. If I scroll and continue to scroll down through this player pick, like Guardiola, somebody got there, somebody got a prime Pele. Like, look at these moments cards that are popping up in here. There's another Desai and this one. Moments Balik, right? It's just all over the place as people were packing moments cards from the SBC yesterday and EA tweeted out, right? They addressed this issue and they said, we are aware that the mid-prime icon player pick included icon moments items. This issue was addressed earlier. We will be following up with the impacted players in game in the coming days. So not only do we have EA going to be compensating people for the issues that happened with the foot birthday team one pack, this 10 swap token item here that was giving out foot birthday team two players, we now have EA that's going to be giving out some the mid or prime player pick to people again. I would imagine those that did pack the icon moments cards would be getting another player pick like myself included, right? Since I packed this moments Desai which actually fits slots in perfectly to the squad. And I'm actually really excited to try this guy out. They're not going to take this card away from you because you've got an item that wasn't supposed to be in the pack. They're going to compensate, right? Because what they advertise as mid or prime icons, there was other items that were in that pack.  It's the same thing as with the foot birthday team one pack that was on Friday when that was glitched. I feel like if anybody opened the mid or prime yesterday during the glitched period or open the foot birthday team one pack during the glitched period, you should receive compensation. It's probably not going to happen until like Tuesday, Wednesday, Thursday, like later on this week. But since everybody was knowing that that SBC was glitched and they knew that compensation was likely, which as we see now from EA tweeting it out, it is going to happen. Everybody yesterday on the market was in a frenzy once again and they went out and they sold cards from their team to try and go and fund doing that icon player pick. And hopefully getting lucky. So the whole point here was if you were doing that, there's a nice undercut from Boppy. If you were doing that player pick, the hope was you would pack a moments card or open it during the glitched period and get compensated so that you would get the player pick again. It's kind of weird because we know that it's a glitch and that EA would probably compensate people but you can actually turn that into a little bit of an advantage. So look at it however you want to, but since I had a lot of fodder in the club, I said, you know what, let's just go for this and give it a shot. And it worked out. I know some of you guys went and got some cool cards as well. So we'll see what happens with compensation and we'll see what EA sports do with this. But again, since everybody was trying to take advantage of this opportunity, prices on the market dropped literally everywhere. The cards impacts. If you take a look at so many of these graphs on the game yesterday, you just see prices dropping immediately. It was right at the 6 p.m. timeframe when these cards dropped in price. I mean, take a look at Fakir, right? $5.95, down to $5.33 and then down even further to $4.97 where he is right now. It hit a lot of the out-of-packs cards. I mean, of course, the current impacts, I was like, DiBala, I was selling DiBala for 1.57 million coins yesterday. Like right here, I sold DiBala right in here.  But it's also the out-of-packs market. Take a look at for birthday team one. Ronaldo's 4.2 million coins. Who else is down? The other card's 4.50. How low is OdaGuard during all the madness yesterday? I'm sure he was even lower than 4.50. He was down at 4.50. Then he bounced back to 4.75, still down at 4.50. And as you take a look at the rest of the out-of-packs market, let's see who else was down. Marez, I saw Marez at like 700,000 coins. He's back up to 7.60. As you can see here, see this panic down to 700, boom. Back up to 7.70 where he is now. Ronaldo Sanchez, if I can find his card, this card continues to drop. And a lot of these prices, I don't expect them to rebound. Again, it's kind of the same thing that happened yesterday or two days ago on Friday with the glitched foot birthday team one pack. A lot of these prices aren't gonna just bounce back, especially after yesterday when so many people were selling cards from their team to go and buy SBC fodder to get the SBC done. You can even see it when you look at these fodder prices. Take a look at Holland, 23, 24,000 coins yesterday. The glitch is active and known and happening. This guy spikes to 32,000 coins. Then of course, as the hype kind of dies down and it's not glitched anymore, EA tweets out. And now as EA is running lightning rounds late into the night, Saturday night into Sunday, these fodder cards are kind of dropping down again. So it's even for these fodder cards, it makes a very interesting investment opportunity. If you bought these cards on like Friday night when we were talking about it or Saturday before the whole glitch madness was happening, you got a really, really great price. But even as we head out of this weekend into this week of good content and into today with maybe a big time foot birthday player SBC, some of these cards are still looking buyable at their current prices because of how low they've gotten with the supply this weekend. So that was kind of how the market reacted yesterday to all of the madness of that glitched pack. And that's why prices are down. I mean, it's not just the cards that are in packs right now that are dropping at price. It was the whole entire market out of packs cards, icons, especially with the brand new icon moments that were released out yesterday in the game as well. A lot of those cards got to cheap prices like right away. I mean, look at this, Danny Elvis down over a hundred thousand coins from yesterday. Actually, it's really funny to look at this CELAS card, right? CELAS foot birthday was like 80, 90,000 coins yesterday. Right now, this guy's like 50K. I think he's even less than 50,000 coins on the market at the moment, crazy. For the price drop offs that we saw yesterday. Now again, I know there's a lot of coins that are being put onto the market with lightning rounds and stuff like that, but for a lot of the out of packs cards that dropped a lot yesterday, yes, some of the really, really rare ones you saw rebounds on, like the mores. But even a guy like Renato, he didn't really rebound in price, right? This guy was like 1.15, 1.2 million coins. Well, he's still 1.06 for a really, really rare road to the final card. And again, like a guy like Mbappe, who we look at all the time to see market crashes and see where his price goes, because people buy and sell this card a ton since he's one of the most popular cards in the game still at this point of the year. Down a hundred K in two days. Like I don't expect Mbappe, especially with a Player of the Month SBC coming later on this week. I don't expect Mbappe or the market really in general to bounce back a lot because so many coins were taken off the game yesterday because that SBC that they released, or not that they released, but the SBC that everybody was doing was a 500,000 coin SBC. If you think about it, it makes sense why cards like Mbappe and cards like some out-of-pack specials were down so much yesterday and were panic sold, like that Mars that we looked at. If that was the reason why everybody was panic selling, which I think it was, this is a 500K SBC, which is not that easy for a lot of people to complete, especially when it's a glitch and it's in a timeframe where it's probably not gonna be glitched for that long. So that is why you saw the market movement like you did yesterday and that's why you saw all the prices dropping. It was because of that SBC and all of a sudden people realizing, oh my goodness, this is glitched out. It's giving out icon moments cards. Everybody running onto the market to try to do those SBCs and get those cards in their team because of that glitch. So today on Sunday is gonna be a very interesting day as well, content-wise, because we're gonna have more pack supply, we're gonna have more lightning rounds. These foot birthdays are getting very, very low again tonight, just in general. This foot birthday noir, I bought on Friday night at like 138,000 coins. I think it was like right in here, 138K. I bought this dude. He spiked to 180, got really rare.  He's now down to 118,000 coins. I mentioned that I sold DiBala at 1.57. And you just take a look at all of these cards and they just keep dropping continuously, but there's gonna be more lightning rounds today. There's gonna be more content. There's gonna be more foot birthday cards in packs. One of those that we think we might see in packs today is Sancho. A Sancho foot birthday card is an item that we would expect to see later. It was leaked as a part of a team to a foot birthday, a five star, five star Sancho card. So that would be a really, really dope item if they did release that today. But I don't think that's the most hype part of the content that we could see today. There is a massive SBC. And then we have to talk about this for a second because this is a player SBC. This guy has not had specials this year except for a ones to watch and he's been injured. So he hasn't had like any special cards this year. And it's a PSG member. Sergio Ramos, SBC. These are the stats that we should see on the Ramos card today on Sunday. This is the SBC that we should be seeing. Now, evidently it's a five star skill move, Sergio Ramos, which is interesting, but it's PSG and it's Ramos and 83 pays to me is not quite enough. I was hoping for 85, kind of like they did with the DeVry SBC, maybe even a little bit more than that. But this is gonna be the card that everybody is excited about today. It's a PSG SBC. So as you've seen on the market, as a lot of cards have been panic sold, people know this SBC is coming and they're getting ready for it. And it's gonna be a hype SBC. It all depends on the price as it always is, right? It all depends on the price. If this Ramos is gonna be a good SBC or not. I mean, if you take a look at his base card, which is all that he has in the game right now, besides the ones to watch, which has a plus one rating over it. He's gonna have 83 pace and a five star skill moves. He's high, medium work rates. That's why I was hoping for a bit more pace. But 83 pace on this card probably means he's gonna have like 85 acceleration and like 81 sprint speed or something like that. So hopefully maybe EA can, I don't know, they'll just boost up the pace a little bit more. But his defending is gonna be cracked. His physicality is gonna be cracked. Ramos always has a pretty good item in FIFA. It's just the work rates that let him down a little bit. But again, just because it's Ramos, so many people, and because of the PSG meta of this game, so many people are going to want to go out and do the SBC as long as it's not crazy expensive. This has guys like left-back Nuno Men's, right? Or the team of the year, Donnaruma. A lot of these cards dropped yesterday with all of the frenzy, the craziness of everybody trying to go do that player pick for the icon moments cards and pack those players. But you've seen these prices bounce back up. Like Donnaruma was 175,000 coins yesterday in the peak of the panic selling. And he is back up, I think, to almost 200K. Yeah, he's 195, so he's back up 20,000 coins. The Nuno Men's that we just looked at, he has started bouncing back up. I even think that Hakimi team of the year might be a little bit higher in price than what he was. I think he was like 630s or 640s because of the Dani Alves. Yeah, right now he's 670s. So people are preparing for these cards to come out. And on the flip side of things, some of the like the Marquinhos special cards are down at price. This version of Marquinhos, who I bought some on Friday to try to trade with, with the Ramos leaks that have been out, this guy's gone from like 300, he's 299, man. Like what? Bro, this guy was 400,000 coins literally two days ago. And now that Ramos is leaked, he is down so incredibly low. Now this price right here is really, really cheap. And there's a lot of panic selling here, a lot of people are trying to get this card out. And maybe other PSG centerbacks like Kempembe are gonna be affected today. But it really, again, depends on the Ramos price as to where the market does react and how cards go up. Are the PSG links gonna go up in price to this Ramos or is it gonna be overly expensive? You know, they've done better SBCs. The SBC that we got yesterday with the Cochlear card, it's not bad, but it's not amazing. It's just kind of in between. And the DeVry SBC, this SBC is like under 100,000 coins to do. I know the stats don't look that great, but it is decent links. It's just kind of like it has a 50-50 up vote, down vote on foot bin. But the DeVry SBC and the Rice Rice Baby, right? The last three SBCs that we have had have been an improvement from what we've seen before this. So hopefully the Ramos SBC today is really nice, good price and maybe a little bit more of an upgrade than what we would expect. Other SBCs that are coming today is one thing I do wanna check. I don't know if the Prime icon pack, there's a Prime icon pack that is out too. Does this expire today? No, it still has a week. So I don't know if we're gonna get a new icon upgrade today. We have the mid or prime, no longer glitched, is still here. And we have the Prime pack that is still available for seven days. So I would be surprised if we got another icon upgrade SBC. Now I don't know anything about icon player SBCs. Hopefully they just save those until we get icon moments. But probably another swap token today as well, whether it's an objectives or an SBC. And the mini release, which will feature Sancho, I believe, and that Ramos. So it's gonna be a pretty big day of Sunday content. And especially after all of the madness with the compensation, everybody's waiting on that. Again, if you did the icon player pick yesterday, whether you got a moments card, whether you didn't, I don't know how EA's gonna do that compensation or for the birthday cards. But I feel like that's gonna be later on this week. It's gonna take them a couple of days as they always said, right? It says impacted players will be messaged in the coming days on the game. So it's gonna take them a few days. Everybody was doing it yesterday and trying to kind of take advantage of that opportunity. So they have a lot of people to kind of work through and a lot of stuff to look at when doing that. So that's kind of what's going on on the market right now. A lot of prices are dropping because the cards impacts again are insane. The SBC content's been pretty solid. And these glitches are just compounding that, right? Because people are trying to take advantage of the stuff that they can take advantage of. And that's why a lot of these prices are going down on the market right now. So if you have any questions, make sure to drop them down below in the comments. I'm excited for a big day today on Sunday. I'll be streaming live for the content drop. Of course, with the time change, it's gonna be an hour later for me, which will be interesting. But for a lot of you guys, it won't change. So if you did enjoy the video today, make sure you hit thumbs up and subscribe. If you are new, it has been Nate, The Foot Account. And I will catch you guys later. Peace.