Greetings. We'll wait until at least five after here to see if anyone shows up. If not sure if this is a holiday. Oh, there's Tom. There we go. Hey Tom. How are you. Am I right?  No, there was no meeting last week. I didn't think so. I'm wondering if there's another holiday for other folks today. Or everybody's cyber Monday shopping, trying to get sales. Yeah. We were you were you off on leave all of next week. Sorry, last week or. That's hardly. Yeah. Yeah, that was the plan. Had to do a bit of work. Always gets in the way. Yeah. We already got the top code. There's the link. What's that? Meeting notes. Shared the link. Yeah. We'll give it a couple more minutes and see your joins. Sounds good. No public holidays I'm aware of today. Let's see we can remove one summit from this one. Yep. And the elephant ETF. No. Okay. Let's make a start. So yeah. So the only upcoming event on the list at the moment is Kubecon EU in April. Let me see. We just written that. So more info on the December 5th. I think that's both the marketing. And the respect us and also any. Program committee interest form. I know I've had. Which is awful. Chat from Swiss com. Who was there last year. Was expressed an interest in. Helping on the program committee. So once we've got a form for that good to share. That's only for the main event. I think. The CODO CFP date is later. I think, isn't it? Yeah, the cloud native telco day. Yeah. Yes. And not open yet. Yeah, okay. Try to have it open in December. Okay. Sounds good. Okay. So generally. The telco events that you know of that would be interesting and good. Right, right in here. Nothing. Global. No. I'm aware, for example, there's the. Layer one, two, three. Something. Congress. Oh yeah. In December. I don't know. I don't know if you can see my screen. Can apologies. The layer one, two, three world Congress. So. There's a cloud native telco bit to that. Around table. But I don't know how. I don't know if it's global or. Whatever that is. Right. We've actually talked with folks in the past. For the layer one, two, three. I think there may have even been a presentation. Or at least request and kind of remember. That one would be a good one. Just. I guess to write it down or I can add it to the. Oh, that's in December. That's like right now, isn't it? Yes. Next Monday to Wednesday. Oh, okay. Finally, I got an email from. One of the organizers. Milad. Keep it together, the agenda. Right. But no, I'm not aware of anything else other than that. Looks like. Robbie's going to be there. Oh, right. Okay. As a speaker. Just scrolling through the speaker last year. Right. Anything in next year. First or second quarter. So. So I was at the UK. Kubernetes community days event last week in London. Right. And the CEO of open UK. Amanda Brock. Mentioned she was organizing an all about open source conference. I can't remember what it was called. I can't remember the URL, which is irritating. And see if I can find it on Twitter. So I'm not all about state of open.com. I can't actually get to the website on this machine because. It's a newly registered domain and my work security. Policies don't allow me to browse such things. All right. That might be of interest. I don't know if it's again, whether it's UK. Kind of focused or just generally about open source, but that might be interesting. Looking at it, that is. In London on the 7th and 8th of February. So it's just like an open source conference or. More in general, or. Yeah, so it's not telco specific. It's open source. Yeah, agreed. Schedule coming soon. Incredible lineup coming soon. Okay. We can't say. Have you been there in the past. I think this is the first iteration of it. All right. From what she was saying last week. You know, who open UK are there. There are. Non-profit body. Advocates for open source and. Open data. Primarily within government contracts and. Technology implementations. I think. But they, you know, they brought branched out into kind of supporting open source in general. All right. Sounds good. So what about the Linux foundation conferences, like the. The open source on it. I know that. Is going to be one in Japan, but I don't know if after that one. If they have an ounce. But it's going to be the next one, you know. Open source summit. North America will be in Vancouver in 2023. That's May though. Yes, that's fine. It's after coupon. Let's see when is the Europe. Europe is September. So even after that. In Spain. Open source summit. Yeah. September. Then. North America, November 6th to 10th. Well, there's quite a few things happening in Japan. Cloud open container con. If they're all co-located with the open source summit. Oh yeah, these are all I see that. Yeah. December. Yep. Okay, let's move on. If there's no more events to write. Is there anything that you have Victor? Interesting events coming next year. Check anything. But yeah, we'll start looking for. So other agenda items I thought it was worth. For those of you who rent to. The one summit. And potentially any of the attached events like the elephant DTF or nephew summit, whether. There's any kind of good feedback or interesting things. So share the group. Sure. Do you want to start Taylor or I can start. Um, The very first thing that came to my mind, I mean, there's a lot of different things happening going on, but. I did. Talk with someone from. The German. The German. The German. The German. Any agriculture department that's doing. Sustainability. Agriculture. And they're. They're using a Kubernetes. With their IoT devices that are going all out. All over the place. So. Interesting. Yeah. I think there's a lot of great stuff. And I think there's some relation to, well, I mean, they were literally at the, the one summit and. Um, The developer forum. And talking about the networking aspects and everything else. So. I had some conversations with them and hoping to get them engaged in. Sustainability and energy stuff. With tying with the CNCS efforts on, so they have a. A group that's focused on sustainability and with best practices that we're looking at that overlaps into networking telecom. So helping to get them engaged. And they had a pretty interesting. That's kind of maybe one of the ones that's more. Off of what we would, I would normally have been thinking about going into. That specific conference. Versus the telecom networking focused. Victor. Yeah. Yeah. Yeah. The one thing that really surprised me about the, especially from. From the awareness. Conference. Or I don't know, like, maybe it's more like. And. Developer testing forum. I just found like. There's a lot of a force in the, in the owner. Side. That was surprised for me because I consider like it's a. I didn't see too much. But it seems like the community is still trying to, to get in there. The last day of the last session of the last day. They were talking about the integration with nephew. So they are retaking the, the efforts to. Try to. Connect on up with a Kubernetes. Different ways. And they didn't know how to do it, but they have an idea. Like the different components that they have to modify it like. So, and. DC. What is the name DC, DC or things as well. So, but yeah, they're, they're still. Very heavy Intel. Interesting on that. About nephew in particular. Yeah. Most of the comments that I heard was like. They are trying to cover too much. And they, they are like putting. A lot of high expectations on that project. So, but in general, I guess that there are certain, certain technologies that has to be. Learn for, for that one of them is. I don't know how they pronounce it. Yeah, it's, it's one of the crucial. Google's. Tool that they are promoting. For, for. So, and, and obviously they are trying to replace him. So they don't want to use him. They want to offer. Or, or the way that they are. Suggesting to. Crazy. The way that they are suggesting to. Crazy and F's are true. Operators. So. Yeah, so basically. It's a kind of radical. Suggestion and. More cloud native. Ways to do things. Let's see how the, the telco industry is. It's open to, to accept all these. New ways to accept. The development. It was, it was kept. And the, the alternative to helm. So. Yeah, it's a. I don't know what, what kept terms. Yeah. Without. Keep it. This one. No, no, no, it's. Key. Be as a Peter and tears at home. Yeah. That one. So it seems like. Kind of provide a similar thing like. Like how. So, but using. What is the name? Yeah. They have a different approach, but so. So basically it's pretty much like. Having a CNF. Using github's. That's. That's idea. Like develop all this.  So you have to go through the. To a workflow where like. Like a BNF vendor has to review it and approve and do all these things. In, in on up. So with, with that field. Basically, you're going to have the similar workflow, but more like a github's. Manor. So. You would have the similar like. Review and approval process, but yeah, it's your best. You're approving the pull request and things like that. And so. So they're also using the backstage technology. It's like a. Spotify. Two. So it's quite interesting like what they're doing. So hopefully. You know, I think this is a new ways has been as happened by the industry because. Yeah, they are still just in on up and trying to feel how to use on up. And how you propose a new ways to do things. Obviously. I don't know if they want to. Reinvest in all these things. Okay. Thank you. Any other comments from. Events. Just trigger thought actually. So Taylor, you were asking about silver. The other day. Which I know resourced at. One summit. I don't know if you wanted to kind of brief overview of what it is. What it aims to achieve. Yeah, that'd be great. So. It started as an idea of. Building a production ready open source telco cloud stack. Which obviously sounds a little bit like. What's been done in open stack and other places before. And is morphed slightly into. What's being called a software framework. Where by the. Companies working within the silver project will. Aim to. Develop. Features and fixes to. Common telco. Concerns or problems that exist in existing open source projects. So rather than focusing purely on being a kind of. Here's a new way of integrating Kubernetes and. Yeah, stuff. Let's let's all club together and work on. Something that's an issue for. Telcos in open source projects. Whether that's Kubernetes or not. The, the, the kind of background to it is. The EU has a program called important project common European. Interest IPCEI. And. This was deemed one of them. Hence why it's being registered with LF Europe. Which was in it, which was launched at the SS summit. In September, I think. So whilst. Whilst it's being launched from Europe. There was. A desire to try and make sure it doesn't become a Europe only thing. The challenge with it is that some of the. Participants. Are also pushing the idea of. Testing and validation center as part of the project. Which. Which obviously then brings it into. A little bit more of a closer overlap with things like. The assured by Annika. Program and the CNF certification program. And so. There are a few of us. Who were involved.  Gail from Ericsson. We've all made the point that. There needs to be. Not just reuse of things like the CNF test suite. It's not just to it. From the silver project. So that it's useful and valid. So hopefully that's the direction of travel is. The people who. The. Telcos and so on. Provides to work on silver. Actually ended up working on. You know, Kubernetes pull requests and. And so on. We'll see. Interesting to. See how that goes. And. Have you heard an interest. And collaboration. And I guess. The. That contribution. Folks. That may be able to join. In addition to people that are, you know, already here. So. The, the only interest I've heard. So, so. The, the seven initial members are. I've heard of interest from. HPE Dell and Intel. Personally. I know from. Talking to other people from those companies. I just mentioned that. Other network vendors like Mavaneer. Have expressed interest in the past. Not, not specifically. Any other operators, but. And. But I. I'm kind of stepping away from silver and someone else in. Vodafone is sort of taking my place because we. We're. We're kind of moving it more towards the. The work we're doing with open run. Rather the work I do. On. Mobile core. We think silver has more. Interest in our man space. So it's being run by someone else in Vodafone. So they may have. Had more interest from other people, but I don't know. All right. Yeah, nice to get. Some of those folks engaged in our working group and. Definitely. Yeah. Yeah. I think we can. Maybe talking about. What the needs are so that we can align it and think. If, I mean, if they're incorporating some now, we want to make sure that. What are, where are they going? And what's missed. What about the O-Ran then? Unless anyone has any questions or comments about silver. So the anything I'll add to what you were just saying is. So what I can do now is share. More openly with. Then. The CNF test suite CNF working group and suggest contributions. Into it. Before silver launched, we were operating under an MOU legal framework. Standing. So there was a kind of limits to kind of how public and. Open. To an extent that we could be and how involved in. Other things we could get. And how much we could share about what was going on, but now it's. Now it's properly launched within each foundation. That's all. Barry has gone. So. So I'm happy to share that information with the people who are running the validation center stuff within silver. That's easy for me to do. All right. Sounds great. Does anyone have questions. For Tom on about silver. Probably I need to start checking that. That links and read information, maybe. Yeah, any questions? Okay. Yeah, I was just. Do you see. Areas where we could have collaboration and work with the run project. Yeah, definitely. I mean, I know some of some of the. Some of the Iran software elements are. Going to be Cuban at his base. So I think the concept of being able to. Certify them using a. Something like the CNF test suite certainly sounds sensible to me. What about overlap with, is there going to be. Incorporation of ideas and. And technology that. Silver and. For any other. Projects that's trying to. Do cloud native. Stack. I'll just call a stack wherever it is. On the stack all the way down to hardware. Yeah. Oh, we're in. Look at nephew or silver. And so. I don't think there's any overlap between silver and nephew. So nephew is. Is concerned with the. Life cycle management of. Cloud native network functions. Whereas silver is concerned with the. The execution environment. So the, the Kubernetes layer and kind of cluster management of Kubernetes down. So it's not. So in effect, I think there's quite a clean. Delineation between. Silver's concerns are and what nephew's concerns are. If I think about other things like. Some of the projects in the open stack. Or if an infra foundation. There is probably some overlap. Things like. Accra, you know. I'm starting X. And so on. And. I'm not sure I could give a good answer as to why. A new thing has been spun up. And. Other than. Trying to fix what was. Potentially not perfect with those other. Solutions. But, um. But again, silver isn't. Isn't going to. Try and be opinionated. About the hardware. In terms of, you know, you have to use. This vendor or this particular type. Other than potentially some functionality. Features like. DPDK. And so. Tom, do you see any. Probably a relation with a. I don't get project or like how. Silver can be. Combined with. Yeah, so, so one of the things.  The three of us were trying to push from a quite an early stage was. You know, we, we, we spent a lot of time building the. Anarchy reference architecture. And the reference. Performance tests in anarchy. And. There was a concern that silver would be. Anarchy reference architecture. So within anarchy, there's a reference implementation. But it, it is. It is purely a reference implementation that is used to. Test. The reference conformance. Test. Sweet. Framework. And the reference. Implementation. What we. We managed to achieve was that we. Silver is now going to essentially be a. An implementation of the anarchy reference architecture. So within anarchy, there's a reference implementation. But it. It is. And the reference implementation isn't particularly useful for. Kind of an external party to anarchy. So. You know, the, the goal of anarchy and the reference architecture was always. You know, community and or vendor implementations would be based upon it. So the anarchy specifications would provide input to the requirements of a. Of a. Stack that would then be deployed. And that's the plan. The silver is that the anarchy reference architecture specs are. You know, input requirements to the stack. And so. The, the gaps that anarchy finds for, I don't know, certain communities features or. Multis features or something else. They could then end up being. The. You know, the PRs, the issues that. Silver collaborators work on. That makes sense. So I think. So I think there's a, there's a kind of double edge to its relationship with anarchy. There's. It will be a consumer of the anarchy reference architecture. However, I think it's relationship with the reference conformance tests and the anarchy badging process is similar to that of the. It's relationships, the CNF test suite. And the CNF. Certification program in the. There's a risk it becomes a. You know, uses the test suite. Sort of the anarchy reference conformance tests. And then adds new ones. That are specific to silver without. Contributing those back to anarchy. And again, you know, we've tried to highlight that. That silver should be contributing back to anarchy, as well as the CNF test suite. It's kind of dependent on. On the project itself, making sure that happens. That's always a problem. Yep. So I'll see a question. Yeah, yeah. That's interesting. Yeah. Thanks. Okay. Okay. Any other questions on silver or anything else related to that? If not, we'll pop onto the. Issues and PR review. I can't think of anything right now, but I'm going to go dig in and probably have more for you later. Yeah, sure. Okay. So there are no requests open. Issues. There are no new ones open. I have not had a chance to. Do anything on the one that's assigned to me. I don't know, Victor or Taylor, whether you've got any updates on the others. I haven't had a chance to. To work on them. Okay. Yeah, nothing for me. I have been thinking about it a little bit over, I guess last week early in the week and. Thank you. What do we want to. Get. What can we get? What do we want to get? What can we get completed? What do we want to complete? And. The. I mean, some of the smaller ones that definitely, you know, like a type that add title to exception stock, we just need to. Knock out. The. The bottom one don't run containers with privilege flag. That would be the, I think, The bottom one. That would be the bottom one. That would be the bottom one related to more of the. Stuff that I do think we should focus on and trying to see how it's going to tie in with. Other things to accomplish. I've been talking about it for a while, but getting more of the best practices. It would be. There's, I would like to get some out. And if y'all are available, I would like to get some of the best practices. I would like to get some of them that we already have content. And it's more of working to take the content and put it in the format. I'd like to do that. And then in addition. Maybe start working on. A write up, which could be a loose version of the best practice where we were not working about it being perfect. But, you know, the summary title and some of the other sections. So, you know, I would like to get some of the best practices. A best practice or set of practices. That are related to. Like silver or in whatever. That we can say here is something that we're working on. And see if we can get other folks interested. So there's the one where we know that, you know, let's just get these outs to the containers of privilege flag that's fine. But we want to get other people engaged. And I think if we can have some topics where there are already part of it, then that would be good. Take what we're talking about. So that's kind of where I'm thinking I want to focus some time over the next. I know we're coming to the end of the year, but through the end of the year and into next year. How do we get more people engaged? Yeah. So you thinking, you know, like a couple of hour working session to sort of batter out the wording and get it into a point where it's ready to be merged. Yeah, that's it. And, you know, as we're doing that, if we're thinking of other ideas for one like to get, you know, a Google doc or something set up where we just start throwing those in there and building out. The next one, but get, get, get. You know, one of them or however many we feel like where we already have content spend that time. And that's beside these items on here, like the add title to exception stock. Yeah. Yeah. Okay. Yeah, that makes sense. If y'all are up for it. I'll, I'll try to throw out some times and. Yeah, I think that makes sense. It'll be a good way to do it. Okay. Any other. Anything. I think that's it. Thanks. No worries. Catch you later. Thank you to you. Thank you.


Sorry about that. A little bit of technical difficulties. As short as that, my name is Chris Wickman. I'm a staff engineer at WP Engine out of... based out of Florida. I'm a WordPress core contributor. I'm a speaker. I've taught computer science, blogger. I've had a whole lot of roles in the WordPress community, including one of the first plug-in sales to a major company. I sold better WP security. I've taught this stuff for a long time. Actually, I typically speak on security or privacy, which has been an interest since my first day as an airline pilot, which happened to be 9-11. It was a great career sign, let me tell you. I've been around the WordPress world, though, for about ten years now, and mostly teaching on security, privacy, things like that. Today's talk, though, is about where we've been as WordPress and where we're going with WordPress. Specifically with things such as Gutenberg, what the future of the software is and where the community is going along with that software. In order to talk about where we're going, the first step is, of course, where we've been with this software. Where we've been, there's two things where the community's been and where the WordPress software itself has been. Let's talk a little bit about where WordPress has been. This is the growth chart of WordPress in roughly the entire Internet. It's the percentage of the top 10 million websites on the Internet that use WordPress. One interesting thing about this is, instead of this line dropping, it's actually growing a little bit faster this last year. As of October 22, we're up to 32.1% of the entire Internet runs on WordPress. That's a lot of the Internet. It looks even better when you compare it to the competition. These are the top seven content management systems on the entire Internet. The next closest thing is Joomla. I have a lot of good friends who use to work in Joomla. To be honest, I don't know anybody who works in Joomla today. There are people out there. It's the number two content management system, but the scale of installs is so vast that it's actually much harder to find somebody that works in even the number two compared to something like WordPress. Of course, if WordPress is going that quickly, is there even room to grow further? Yes, there is. The top content management system on the web is still no content management system at all, but WordPress is kind of conquering that one. The lines, especially this last year where the lines really start to converge are telling. There's an awful lot of potential going on here, but still 46% of the entire Internet doesn't use a content management system at all. These might be flat file generators if you use something like Jekyll. Oftentimes, they're going to be counted as no content management system, simple HTML sites. There's still an awful lot of that stuff going on. There's single page sites and other things that are happening. That's a heck of a lot of opportunity for WordPress, especially as we move into things like Gutenberg. As WordPress does with the current text editor, trying to create the layouts for a lot of these sites that are still no content management system is very difficult today. That's where a lot of the opportunity relies on Gutenberg. That's where the software has been. And then there's also WordPress the community. The community I want to emphasize too is not the ecosystem of WordPress. WordPress is still, at its core, a tool. Even in this talk, I've divided WordPress the tool or WordPress the software from WordPress the community. They're very different things. The ecosystem is the combination of everything we have going on, whereas the community itself is that the people that are working on everything, all the different aspects of the community, whether it be the Netherlands WordPress community, whether it be the South Florida WordPress Meetup Group, which happens to be my home meetup, WordPress can't be you. Different products, gravity forms, GiveWP, Genesis. These are all different communities we've heard of. And as you scroll down the list, if anybody here that's on Facebook or Twitter or anything, we see these communities really in a more pronounced fashion on things like Facebook, the Advanced WordPress Meetup Group, the WordPress Hosting Meetup Group, the WordPress Security Meetup Group, and all the Slack channels. I don't know about you all. How many people in here are on Slack in one fashion or another for work? So a little more than half the room. I was up to 24 different Slack teams the week before I switched to this computer a couple of weeks ago. Admittedly, I need to clean some of those up, but most of them are different WordPress communities, from security to privacy to all the different types of areas I've focused my attention on over the last couple of years. And that's where WordPress is going. It's been evolving for 15 years now. The 15th anniversary of WordPress, as WordPress itself, happened this past May. Before WordPress, it was actually another project called B2 Cafe Press that Matt Mullinowick had forked back in 2003. So this is a long-time, long-running, evolving project that still has a long way to go. And of course, the immediate where we're going then becomes WordPress 5.0, which is officially supposed to launch in less than a month. We have the first beta came out, I think it was Wednesday. It was a couple of days late. It was due out the 19th of October. I think it was the 24th that it actually launched. But that first beta is leading up to WordPress 5.0 and especially this Gutenberg editor. Gutenberg is the tiny MCE editor that you're used to. Gutenberg replaces all of it. It's going to replace the way we work with content. It's going to replace the way we work with pages. We work with menus. We work with widgets. We work with plugins, the way we work with themes. Everything with the WordPress Gutenberg editor is simply different. It's the next evolution of WordPress. Instead of using your widgets, now we're going to have things like blocks for layout, which allows a whole lot of new opportunities for WordPress. Think of it as an app store.  Over the years, we can install gravity forms. We can install caldera forms, whatever it might be. However, with blocks, we can take this even to the next level. If we need a SaaS product, we're working with Salesforce. We're working with our payment gateway. There could be a block for this. You go out and you can download the block. Install it similar to a plugin and just put the block in your site and it's almost a entirely new style of an app. It's a very richer ecosystem for much more fine-grained controls. How many giant plugins do we have now? If we want the feature of a contact form, we wind up with a plugin that gives us a content form, spam control, you name it. Little hover cards when we hover over things. There's maybe 50 features in some of these plugins. One of the benefits of Gutenberg will be the ability to install this feature as a single item, get exactly what you need with it, and not have to worry about all the cruft, which includes training, maintenance, and all the other things that go along with some of these giant plugins in the way that we've done WordPress for so long. Another big advantage to this, too, is content is still portable. There's a lot of good page builders out there that have kind of filled this role for many years now. Beaver builders, Elementor, Divi, these are great products in and of themselves, but one of their big weaknesses has always been content portability. Anybody who's built a site in Divi or Avada, if you want to remove that product later on, it becomes very difficult. Gutenberg handles a lot of that. Everything's actually just stored as post-content with some markup in it. It's a very different way of looking at content than anybody's tried before with this type of thing. It's so flexible, in fact, and one of the biggest markets right now for Gutenberg blocks is Drupal. The Drupal CMS is one of the biggest markets out there, and one of the best-going markets for Gutenberg blocks right now. That's how portable this technology is becoming. So if that's not saying something, WordPress's mission has always been to democratize the web. Democratizing the web doesn't necessarily mean WordPress is a core database. It means democratizing the web, period. Gutenberg is a very big step in that direction, just in the fact that Drupal in particular, but also I've heard Joomla communities looking at it for various items, and other systems are looking at Gutenberg to incorporate into their own systems. It's kind of like TinyMCE was, which TinyMCE is the current editor way back when it was adopted 12, 13 years ago, but now with a whole new level of being able to make this data portable, available, and granular, just the way we need, you know, the way your customers need to use it. It is very JavaScript heavy. It's based in ReactJS, which is a little bit different than what we've been doing before. And also it's currently, well, as I wrote these slides the other week, it was currently a plugin entirely. You actually had to go out to the plugin store and install Gutenberg. With the release of WordPress 5.0 Beta 1, it is included as the default editor now. And when WordPress 5.0 is released, it will be the default editor for WordPress 5.0. It's feature-ready as of version 4.1, which was about a week ago. So as quickly as WordPress 5.0 is coming along, Gutenberg itself was only feature-ready about a week ago. So that should tell you something about where the state of bugs and things are if you were to try this, and that is something I have to warn you about. But the thing is feature-ready. So if you were going to try to, if you have clients that you're going to launch in December, if you have a client you're going to launch in January and you're working on this site, now is a really good time to get yourself familiar and get your clients familiar because it is ready. Things are not going to change in the way that you're working with it from what we have right now. Like I said, and the final release is slated for right before Black Friday, the 19th of November. So take that as you will. That is when it's released. To kind of give you an idea of how big this project already has been, originally they wanted this to be on 100,000 sites and 250,000 posts before they were considered merging it. As of when Matt wrote that a month ago, Matt Mullen was the founder of the WordPress project. He's the CEO of Automatic. He's been around this stuff a long time, but their numbers were 420,000 sites as of a month ago were running Gutenberg. So there is adoption of this thing already. There is a lot of eyes on it. There's a lot of things going on with it. And it is going to improve a lot of things. The improved editing experience really is kind of amazing. There's a lot, it's different. If you're very used to typing in Microsoft Word, this is different. This is not going to look like what you're used to working on. But as you, most people who are new to the system, new to WordPress and just have already started with Gutenberg and are not familiar with the old stuff, find it very much more difficult to go back in everything I've seen than people it is, for people to go forward into the new stuff. It's going to allow, like I said before, easier integrations to other services. When we're dealing with JavaScript, when we're dealing with things that we're not pulling things into the database and we can go directly out and integrate with other services, it becomes a much easier thing to integrate, like I said, your payment gateway maybe. A different type of content form, different types of social media posts, whatever it might be, the integrations available with this are amazing. Also rapid site building. The difference between pages, posts, other forms of content are going to virtually disappear. If you can have a block that might indicate, for instance, if you were working for a school and you had a block that indicated each teacher's name, that you just put on the content and then arranged in a menu, that's a lot easier than trying to figure out, well, if I go to staff over here and then I put this page over here and put this widget over there, everything's in one place now. The training.  If we're familiar with WordPress, oftentimes that's not the case of our clients or our customers. So the ability to train people and make sure everything's in one place and make it easier for them to edit the content they need is really going to be kind of amazing. And that is going to lead to a much easier adoption for new WordPress users. WordPress has been an easy sale for many of us for a long time because of the available integrations, because of things like gravity forms, because of how mature the market is. The ability to now take this to the next level and make it easier for our users is going to really help us step up that goal. It's not so much about what's easier for us as a tool. It's what's easiest for our users to actually edit things in. And if they're coming from something like Drupal, if they're already using Gutenberg, your job's done for you. It's already sold. They've worked with this stuff already. So now you can use the tool set you know, WordPress, whatever WordPress add-ons you might use, and integrate that all together with a much easier sale for your customer. And a much nicer experience for them. And of course, blocks and... Gutenberg editor is actually stage one. The next phases of modernizing WordPress are going to include things like widgets and menus, which I believe is phase two. There's going to be things like themes. There's even been a quote by Matt Mullenwig that phase four of the modernization of WordPress, the Gutenberg project, could be core multilingual. In this room I would mention that's a much bigger deal than for someone like myself, because that's always been a plugin. And how many of those plugins, WPML is a great plugin, Babel is a great plugin, but how many of us have fought with those plugins over the years in order to try to keep things going? The ability to have that in core and support it in core, where all your plugins, all your blocks can use core multilingual, assuming that does go in for, that is a quote you can find him on WPTev and say in that, but it's not an official item, there's no official roadmap there. But if that was to go in core, the ease of use for international users, for people that aren't from the United States or not English first countries, is just amazing. So there's a lot of potential. There's still questions. When I was asked to do this talk, when I was speaking with the organizers about this talk, one of the things was, oh, forget Gutenberg, I'm tired of hearing this, I'm tired of hearing the problems, there's still issues. Probably the core issue that we're going to hear the most about, and this room in particular has some very big people involved with this issue or the accessibility issue. Right now, in the United States, if you work for a university, we can't use Gutenberg. I just left the University of Florida last month, so I've only been working with WP Engine for a little while. They're scrapping their Gutenberg integration right now at the University of Florida. It's not accessible yet. Because the universities are required by law, and depending on where your country is, depending on what industry you're in here, if you have accessibility requirements by law, you may not be able to go to Gutenberg on November 19th. That's not to say it's not coming. People are working on this. WP campuses agreed to sponsor an accessibility audit. There's a call for proposal out right now to make sure that they are covering all the bases. But this is an issue we have to think about at the moment. It's still bugging. It's not released yet. It's production software. It's beta software. So if you put this on your client's primary site right now, they're going to find bugs. Notice I didn't have any screenshots of this. There's a reason for that. Every time I tried to make a screenshot of my Linux computer here, some sort of bug, it was just weird graphics glitches. As I was searching for screenshots, I tended to find it was all people screen-shotting weird bugs and graphic glitches. It's not quite ready for prime time. But there are a lot of people using it. There's still a learning curve. The editor learning curve, if you have a user that's been writing WordPress for the last 10 years as a blogger, there's a learning curve there. It's going to take them a couple of hours. If you're a developer that's been writing PHP for the last 10 years, there's a learning curve there. That's going to take you a couple of months, if not weeks. There's quite the learning curve on the code side of things. This is using something called ReactJS. WordPress has always typically been PHP, HTML, a little bit of CSS, and JavaScript on top. Now JavaScript is first. So that is going to be a learning curve for your agency or for your shop that's building stuff for it. Integration with existing sites. If you have a site with 50 plugins in there and it's all custom code, it's going to take a while to get that code up to speed. Data portability. If your data isn't something like Avada, Divi, not to pick on these plugins, they're great products. But if you're already using one of them to try to get the data converted over to some of this, it's going to take a little bit of time. And project updates tends to be one of the biggest things I hear of a concern right now. Typically WordPress historically has had a very rigid we do not put new features in a .release. Right now we're 4.9.8. That .8 should never be a new feature by its own admission. 4.9.6 was a huge slew of new features for Gutenberg. So if you're working for Enterprise, a large company that relies on stable and predictable upgrade cycles, there's a little bit of a question right now. These are all issues that as great as Gutenberg is we do have to think about. So I do want to make sure that they're put out there. However, all of these issues are being slowly worked through. It's not like the core team doesn't know about them. It's just not quite there yet. But again, the product hasn't released yet either. It's something to think about. And we see all kinds of things. This I would agree with because currently Gutenberg sucks. Here's the problem with collective thinking at automatic. There's the range of this. If you search for Gutenberg on the web, this was just a tweet search I did the other day. I tried to get this as close to this, as close to today as possible as I updated this. But there's also a lot of positive going on. If you're using ACF, it's fully Gutenberg ready. If you're using, I believe Gravity Forms is added or close. Yoast, I believe you guys are Gutenberg ready at this point. More and more of this is coming online. Again, it's still not released so that everybody's still kind of working out their integrations. But things are coming along quite well. Regardless of what you see of people who have tried it. And if you've tried it, your plug-in's not ready for it. People get mad. You see an awful lot of tweeting. You see a lot of social media response on the bad. But not a whole lot on the good side of things. The stuff I see from people I try to introduce this to tends to go more like this. I blog for the first time. When I actually try using it, okay, it takes a little bit. There are some bugs and it does take a little getting used to. But the writing experience, the user experience is better than what you've had before. And that's really the pinnacle of this. It will be easier training. It will be an easier experience compared to the onboarding from what you've had previously when trying to introduce a customer to WordPress. And again, editor is phase one. Just because we're done with the editor, Gutenberg project as a whole, the modernization of WordPress is not complete. The next step will be widgets and menus. So instead of having a separate widget and menu editor, need a little more coffee this morning. Instead of having a separate editor for each, these are going to be moved into the block systems. You'll have menu blocks. You'll have widget blocks and things like that. Beyond that, then they're talking about theme and plug-in APIs being converted to being more useful with blocks. There's a lot of things going on as things move forward. So we're in the very early stages of the modernization of WordPress, but it's coming in. It's really going to be an improved experience. So then who's going to use this stuff? What's the whole point? Why bother doing this? You hear this stuff about backwards compatibility. WordPress still supports PHP 5.2, which has been dead for close to 10 years now. It still supports other... There's been a whole lot of legacy we don't want to upgrade. So why the upgrade thing now? And it's because there's so many opportunities right now. WordPress has always been blocks. Then small businesses. Now it's becoming bigger and bigger in the enterprise. WordPress was always developers and site admins, the freelancer who's building sites for their clients. But now we have designers making careers, content writers making careers, project managers, sales. In other words, every aspect of business is now part of WordPress. Whereas historically, when we talked about somebody, if I was to queue this room 10 years ago, 90% of the room would have been a freelancer or somebody that's building their own blog or building a blog for a friend, something along those levels.  The evolution of WordPress is not just the blog. It's still there. But we're moving further and further into the enterprise. And we can see that with just some of the brands that are using WordPress today. I apologize this is very U.S. centric. That tends to be what happens, especially as I blatantly stole this from my boss, Jason Cohen, from WPage in this particular list. But this was a couple of weeks old. Just some of the various brands from the BBC, Viacom, Microsoft, National Geographic, all the brands using this and not just as their blogs. This is being used for all kinds of different technologies now. And it's not even used as their main sites. It doesn't need to be. One of the big advantages of WordPress is it's quick to spin up. A site for, say, Microsoft that would normally cost them $2 to $3 million, they might be able to get away with $100,000 to $200,000 on WordPress. In the enterprise, this level of scale, this level to quickly iterate and get a site done in six weeks for a tenth of the cost is really where the strength is. It doesn't need to be the primary CMS. And there's a lot of growth there. If you're out there trying to sell people, this has to be your only content management system. That's simply not true anymore. There's a lot of niche for this. 53% of WP engines' respondents, as they were polled, used two or more CMSs. I can tell you from my own experience, this is the UF Health website that I just left. We used WordPress as our sec... Technically, it was our secondary content management system even there. We had 800 sites about and over 30,000 daily users, including an intranet that had over 40,000 users on it. It was just a matter of how many of those logged in a day. Our main, this particular, this is actually Drupal 7. Obviously, it's a need of a little redesign, design's dated, that tends to happen. But the rest of our stuff is almost entirely WordPress for our front-facing sites. We have two giant WordPress multi-site installations covering almost the full 800 sites. And then even on top of that, we still have very custom-built things. We have a directory system that integrates all kinds of academic sources for the sake of... It's built in PHP, Vue.js. So it's one tool in our toolbox. WordPress is not the end of the goal. It's a tool to help us reach the end of our goal, to reach our users. And that's an important thing to remember as we're trying to sell new people. It doesn't have to be the only thing they're working on. And it's still its greatest weakness or its greatest strength, whether you're dealing with enterprise, whether you're trying to sell a site that's worth $300,000 that Adobe is trying to charge $2 million for, you wind up with the integrations that become... It's single greatest strength. Everything's already written. The size of the community, the size of the ecosystem around WordPress means chances are, you don't need to reinvent the wheel as you would with a proprietary system. From 2011... Back in 2011, there was approximately 150 different marketing SaaS items. And this is the MarTech evolution. MarTech is the blog that puts this out every year. The 2018 version of MarTech is up to over 7,000 different sites that integrate different marketing services. Nearly every one of those has an integration with WordPress already available. I'll be honest, I don't know how US-centric this is versus how centric this would be for different services in different parts of the world. But the concept is there. If you're trying to integrate your customer with anything they need, WordPress probably already has it for you. That's not changing. That's getting stronger, especially with the ability to build blocks. Different types of services, especially stuff that was displaying content retrieval, is much easier with blocks than it was trying to pull things, store it in the database, build all this custom stuff to support it, and then wait for caching or something else to break. This is going to be easier on your hosting. This is going to be easier on pretty much all aspects of WordPress in order to make sure that things are still moving and your customers getting exactly what they need. They're kind of zooming on this. This is the 7,000 from 2018. I can't read any of them individually. They're just so stuffed in there at this point, but the idea still comes across. There's just so much out there that we can integrate with in this point. So then it begs the question, is building a theme still redundant? If you're still doing this the old way, if you're just building a theme, if you're just building that blog, should we rely on the word, should we move on to new technology? Is what we've learned over 10 years, do we have to move on to the new stuff? No, we don't have to move on to new things. So don't let this stuff scare you. This is a lot of new, and if you're used to doing things a different way, that's fine. You can still keep going. The web interfaces aren't going anywhere. We're still using HTTP. There's still RSS feeds. You can still build emails. You can still do Classic Editor. Now we just have new ways to develop for this. You can interface with WordPress from the API level. API is application programming interface. So instead of what a user is supposed to see, this is what another computer is supposed to be, you can get data out of it from computer to computer instead of just sending it to a person. You can interface from it from the command line, which is on your Mac or your Windows, you go to the terminal, you can start typing things and you can pull up WordPress that way. These are going to be strengths. These are different ways instead of just having one or two ways, we're not just building web pages anymore. We're building all kinds of integrations meant for being consumed by all kinds of users, most of which aren't even human at this point. We can be consumed by another computer, another service. We can make SaaS services. Progressive web apps. All these new technologies are available, but not required. What does this mean for WordPress work? So what does this really mean for our jobs? It's just simply new opportunities. If you're a developer, learn an interface. If you're working with the front end, if you're building HTML layouts, templates, great. You might need to add React to it to get the most power out of it in order to make the sale, but you don't have to learn an entire new skill set. You're adding some to your existing skill sets. There's other opportunities and themes in Veon. I don't actually write PHP code anymore. I work in WordPress. I'm writing in Golang. Golang is a Google C-based language. I see I'm not the only one in the room. It's a C-based language developed by Google about 10 years ago that's built for command line tools, built for desktop tools, really. I don't write any PHP in my day job anymore, and I still work in WordPress. It's a new opportunity for me, and frankly, after 10 years of writing PHP plugins and that, I get a little burned out. It's been nice to be able to switch and still be in WordPress, still be in the community I know, and do other things. Of course, for designers, they're probably in the best shape with this. Layouts of all these different integrations and everything. The sky's the limit there. And then non-text. Even if you're doing something, if you're a writer, the ability to make content easier just means more content's going to be available. It's going to be easier to get that content in. There's more opportunity to use your skill sets, whether it's in content, project management, or just about anything else. The opportunities are there. We're selling to bigger clients. We're including more people. We're branching out into new areas. The opportunity is there for all of this. It's not just the developer's world anymore. It's not just the site admin's world. That's just one part of it. Everything else is going to go from there. So if you're willing to scratch someone else's itch, in other words, if you have a problem you need to solve, if you see a problem out there, the opportunity, especially right now as things are going, is really there. I would say go big or go home with it. Just take up that opportunity, move forward with it. There's very little plugins out there right now using building blocks. So if you want to learn blocks, start putting your code out there. Fender WP security was a plugin I built. It's now iThemes security. I sold it to iThemes. It'll be five years ago next week, I think. It was one of the first big plugin sales. I was a student at the university and it was called Code. Don't ever look in the code of that plugin if you want. Some of the old stuff is a little odd, but it was one of those, I had a need where I was working to build something, so I took it and ran with it with a plugin and it's built an entire career leading to my Golang work today. There's all kinds of this stuff, especially right now, probably right now, more so in the last 10 years with Gutenberg, with these new integrations to take a new idea and run with it, design. It's all right there right now. So then your next step, then, is to simply get involved with it. I give this talk a lot about community and there is a... I can't pronounce names this morning. There's the community workshop next. This is just kind of a quick overview. I would say that if you are interested and you really move forward, you've already taken the next step just by sitting in this room. The fact that you're here at Gutenberg, you're trying to learn WordPress. So there's the next step. I would suggest today, though, get out and enjoy the hallway track. The hallway track is simply... if there's a slot where you're not necessarily interested in the topic, take that opportunity to network here. I live in Florida currently because of WordCamp Miami and the hallway track. I work at WP Engine quite honestly because of the hallway track at various WordCamps. I'm a fifth WordPress company. I've never applied for any of the jobs I've had. It's all been networking through various items or through various conferences. So take that opportunity, especially with ideas in Gutenberg. If you're a designer, maybe it's team up with the developer. This is the type of place where you're going to find the work and the help to move forward with this stuff. And take it beyond the conference. I couldn't find a Utrecht WordPress Meetup on Meetup. That might be because it insists on searching Florida for me. It's out there. These Meetups are out there from WordPress to designers to Drupal. Girls Who Code is a huge Meetup right now in the United States. You name it, there's React Meetups, Golang Meetups. These are the great spots to take these skills to the next level to get involved in your local community. The Austin WordPress Meetup is the one that got me involved in WordPress at first. So, I think he's been to this camp before is why I picked this slide. The guy on the left, Mendel from GoDaddy. He was one of the guys that helped pull me into the Austin WordPress Meetup back in the day. You can do even if you're too far from things, just join us on Slack. make.wordpress.org You have to have a WordPress.org account. But this is the Slack team. Weekly meetings from dev, from timelines, from accessibility to privacy. All these meetings happen on Slack. WordPress.org Slack channel. Every week, just about every team has some sort of meeting. So if you want to get involved, that's the place to do it. And do it your way. Find your passion. Don't let somebody tell you that if you don't know React, you can't make it in WordPress. If you don't know Gutenberg, whatever it might be, the list goes on. Developer is one role in this ecosystem. It's one role. There's all kinds of roles. And there's only becoming more and more every day. The amount of jobs I see every day from support people to project managers to content, especially content writing jobs, I've seen so many more of lately. The opportunities are out there. Don't let somebody tell you you can't do it. Don't let somebody tell you Gutenberg's going to stop you from doing it. This is not the end of WordPress. This is a new beginning. This is where WordPress is going. And it's going to be new opportunities without the loss of the old opportunities. So if you're still working in PHP, still a lot of opportunity for it, there's just more things you can learn now. So thank you all for coming out this morning. I hope that gives you a little bit of an idea of where WordPress is going, where Gutenberg's going. Okay, my name's Chris Wigman. You can find me as Chris Wigman on, well, pretty much anything from WordPress.org to the WordPress Slack to GitHub. Thank you very much. Is there any questions before I close? I think we have a couple of minutes. Either it's too early in the morning or I talk way too fast. Thank you all very much for coming out.


Dr. Figlent, the checkpoint inhibitors, can you just come in a little bit about what's known about the durable response? Like do they stop working after a certain amount of time, are they curative, or what happens like after? Yes. So what Alan and Ed pointed out, thank you, is the process by which we study cancer drug development. And it is a process. And drugs often get approved or not approved early in the course of things with more information coming later. So what we know about the checkpoint inhibitors is that there's a subpopulation of kidney cancer patients that benefit. We know that of that subpopulation that benefit, some of them have responses that are now lasting for several years. Most of those patients have not had discontinuation of those drugs. The drugs have been continued. So we haven't answered the question of whether you can stop and watch. Nor do we know whether those will be responses that exist a decade from now. So the key to clinical research is being committed and to understand that you take things in a stepwise fashion and that not all the answers are available in the beginning. Now that complicates things for patients and for doctors. We would all like to know all the answers at the moment that we have to address a patient. But oftentimes we don't have an insufficient data set. So what we do is we await FDA approval, which is based upon a set group of criteria, and then those patients are followed extensively over time to see what happens beyond. So the questions that you've asked are good ones. The questions that you've asked have no answers. And yet we are all enthusiastic about answering those questions with that class of drugs. The difficulty I'm about to demonstrate as I try to put this question together is probably reflective of all the questions we patients struggle with, sometimes not even knowing what the question should be. But I was trying to understand a recent report which indicated, as I understand it, the BAP1 and PBRM gene expressions more or less, some over-express, some under-express gave some guidance as to which is a way to separate out more, I guess, more responses to drugs. And obviously that's not much of a question, but kind of a bewildered look at what's happening. Can you clarify that for what that whole idea perhaps encompasses? Ed, you want to address that? Yeah, so what you're reading about, I think, is really great. And Dr. Kim actually touched on it a bit also. So while we do a lot of these clinical trials, we've actually been trying to collect tissue and blood samples from patients to answer some of those questions that are implied in the way you're asking your question. We would love to know which patients we should put on which particular drugs, or even just by the genotype, as Alan slides were showing, which genetic factors will kind of say, well, yours is a really more indolent cancer. And so we really shouldn't get too far ahead of ourselves, whereas your cancer, though it's tiny, actually is kind of a nascent sports car. And if we don't stop this thing now before we blink too much, this thing's going to be all over the place. These types of genes that you're hearing about are amongst a large list of candidate biomarkers for helping us to distinguish those cancers. And I think Dr. Figlin at the start of today's talk had already implied that what we'd like is for our language to evolve while it will probably still include clear cell, papillary and whatnot, to actually start getting into PBRM positive or negative tumors and include other markers met and whatnot that might help us to distinguish these things. So I would say post it. There's a lot of information out there, and it's important. And we are, and I can tell you, this is a very deep-seated interest here at Cedars. So I think the challenge for cancer patients and cancer doctors, I'll try and divide into two pots. There's an enormous amount of information that is constantly bombarded to the cancer patient without any filter of what's important and what isn't important. So generally what you need as a cancer patient, in my view, is a team that's managing you that can help figure out what's noise and what makes sense and what's important. For the cancer doctor, there are cancer doctors like the three of us that spend our lives thinking about things that are not yet ready for primetime, and there are cancer doctors that are waiting for primetime before they think about anything. And what you have to decide as consumers is what serves you best to participate and navigate through your own care. Similarly, if we had simple answers, we would just put them out there. There's no effort on any of our parts to hide or not make available information that could help you be managed better, and anybody that's ever been to see me or Allen knows if we think your care is better served because of your specific tumor that would be better served someplace else in our city or in the country. We just tell you about it. So I think that what you've identified are genes that came out of the TCGA analysis whose implications are now biomarkers for prognosis, but as yet have no targets for therapeutics and are clearly not the whole story. Hello. So we hear lots of things about the FDA. Some people think that they are doing a great job protecting us, and other people think that they're slowing down the process sometimes and not allowing drugs that might be helpful to come to market sooner. Are there other drugs available in other countries that people take that haven't made their way through the FDA here in the United States? Yeah, so I'll give you my perspective on that, and that is that all great drugs come through the United States first, period. There's nothing that I'm aware of in cancer that has come through another industrialized country, a second world country, or a third world country that justifies its use that hasn't been vetted and studied in the United States. Thank you. Okay.


Hello everybody, I'm EvilRabbit and today we're going to give you my honest review on the Mazda RS steering wheel and Mazda R9 wheelbase. So if you guys are looking to pick up your own Mazda racing equipment, make sure you use the referral link down below in the description. If you guys follow me on all social media, I'll just find the description box below. So without further ado, let's get to the review. So with first looks at the Mazda R9 wheelbase, I was pleasantly surprised with the size of the base. It was a super compact design and incredibly small for what I anticipated. It being a direct drive wheel, there's not much moving components inside. So I was pleasantly surprised with how small and the styling that Mazda put into the R9 wheelbase. The aircraft grade aluminum was incredibly nice, super durable and just flowed very well in the wheelbase. The size with the styling combined was going to make it really nice when it went on my rig. So that it would just be super sleek and super clean. The polymer back was definitely a nice touch with all of the plugs and everything on the back. And I believe that also helps with some sort of heat. Now the output shaft with the Bluetooth connectivity, so there's no wires in it, was definitely a huge thing for me. With having broken pins in my fanatech before, it was nice to see something that was not going to have any issues with pins going in and out all the time. Just the overall appearance and aesthetics of it and the size and the compact design of it was definitely something that I was excited when I first opened it up. You know, of course, you get the Mazda racing stickers in the box and everything like that. It's always great when companies give you stickers because I mean, it's always cool to have a sticker when you get something really nice. And as I said, the polymer back combined with the aircraft grade aluminum and all the connecting points and the symbol power button on the back was definitely a huge benefit for the base. And I just couldn't get over how small and compact it was and the aesthetics were amazing. The subtleties going into the RS steering wheel. When I first took a look at it, I could not get over how well the quality of the leather and the stitching was. I could not really find any imperfections in the leather or in the stitching on it. I was looking all over, could not really find any imperfections. The magnetic paddle shifters made out of forged carbon fiber match the front face of the forged carbon fiber front face and the magnetic parts of the shifters gave a nice textile click, which made it very good when you were using it because you could feel it and you could feel when you were shifting gears and it helped prevent bump shifting. The toggles and the dials were very nice when they had, you know, the very good clicks into place. They weren't wobbling around. The textile feel of the keyboard switches for all the buttons was definitely nice because you could really feel when you were using them and the joysticks were a nice touch because looking around and glancing around for drifting or racing is always a huge thing to have on your thumbs. So the quick release on the back, the Mazda quick release, the D1 spec style quick release was definitely amazing. It was built very well, was not going to give any slop in the wheelbase. It was going to make for a very solid connection and limit any type of wiggle or movement or anything like that. Combined with those retractable pins on the inside of the quick release for the Bluetooth connectivity was great. Initial setup of the wheel was so simple. I was very pleasantly happy with pulling up the Mazda app on my computer, turning the wheel on and it recognized the wheel right away, plugging the steering wheel in. It just recognized it right away and it went to as simple as turning my wheel to center, clicking the center button and it was set up and ready to go. It was also very nice that in the software, Mazda has some presets for like GT, for drift, for kart, for formula. And I found those were very good starting points for forced feedback. You didn't have to go searching the internet to try to find some settings. Those just worked. They were very good basic feedback settings. They felt really good when I was racing and felt very good when I was drifting and it was great to see some presets. So people wouldn't have to go figuring out what would, you know, all be on the wheelbase when it comes to forced feedback and settings like that. You could use their presets and have a very good base to tune and fine tune it yourself and make it how you want. One of the biggest advantages I found with this base was that Bluetooth app because of the wheelbase being Bluetooth to the rim, they have an amazing app that you can just download on the app store. Connect to your wheelbase and on the fly, change your forced feedback settings, change your presets, change your parameters, change your lights on your shifting for your RPM lights. Everything like that can be changed on the phone on the fly. You can save profiles, which is really great if you have multiple people and you're going in and out. If you're doing, say, an endurance race like we did with the 12 hour race where we changed multiple times and we all had different driving styles. So hopping immediately into a set of Corsa ACC, I was pleasantly happy and utilizing those dials for traction control and breaking the RPM shift light dialed into how I liked it, tracking from the outsides to the center and then flashing when it was at RPM was super bright and super noticeable. The feedback initially with the base setting only turned up to 900 degrees on the GT setting felt amazing. I really felt that I was able to feel what the car was doing when it needed to when I was locking up the brakes in certain sections. I could feel when the front tire started to slip because the wheel would have a reaction and at the road feel being turned all the way up made for a very good responsive feel of what was happening in the game. And it's very nice that you can fine tune everything to make it feel how you want it to. If you have a real world car, you could tune it to be having such as no power steering or power steering and it just felt amazing. I felt myself after getting used to the smaller diameter wheel being used to a 350 wheel that I found myself running. I felt smoother and faster lap times. Not really sure how much faster it actually was definitely going to be doing in comparison of lap times of my other wheel bases to see if the direct drive system was actually faster and I felt like I could be smoother. The precision of the direct drive was definitely noticeable from my other wheels being able to see one to one in game with my wheel in my hand was really incredible. The feedback when you're hitting rumble strips going into dirt or grass because that did happen. You were able to tell a difference between pavement curbs and dirt, which was just a testament to the direct drive wheel system. And overall the magnetic paddles were great and good for feeling and textile and shifting. And the magnets prevented any type of bump shifting or vibration shifting that I've had before on some other wheels where I'd slap it to shift gears real quick and it would bounce and double shift. There was none of that with the Mazda RS wheel. Those magnetic shifters were definitely very strong and very quick. And I also personally love the really loud clunk they make when you're shifting. It kind of makes you feel like you're actually shifting in a real car because it just has that nice feel, that nice clunk. Just like if you were in a real GT car or something like that and you go into gear, you get that nice feeling, that nice clunk in the seat. This kind of in its own way replicated that for me. So the quick release, there was absolutely no slop in the wheel. I could not find any type of play in it, which was great. I didn't feel any flex in the wheel, nothing on the base. So overall it was a much sturdier base than I was used to. And I feel like that is just also a testament to why I felt like I was driving quicker and smoother than I was prior. So those shift lights being able to be programmed however you want them and every color you want is great for fine tuning it for what you want to be able to see in your peripherals when you're driving. Having it flash either solid red at RPM max or how I have it going blue to pink to red and then the whole bar flashing when I want to shift was definitely something that I found myself enjoying and seeing other than just looking at it on the screen. I could pay more attention to what was going on in front of me and I could just see that out of my peripherals. Something that is incredibly awesome and never realized how much it helps until you have it. So the dials, everything being at your fingertips was great and it just felt so nice in ACC that I can't wait to continue to do more racing on it. I only did try it in ACC but I did hear the Mazda R9 base does work very well in other games such as eye racing. Jumping immediately into drifting because you guys know the base drift setting of the R9 wheelbase on Mazda's app felt incredibly good off the rip. The mechanical feedback and everything that was in the car felt really good. The wheel rotation speed was faster if not about the same speed as my prior wheels, my club sport, but it just felt smoother. It didn't feel like it hesitated, didn't have a weird stepping motion. It was more of a flow wheel rotation which I found was super easy to make for better transitions and smoother transitions. But one of the biggest wins I found when I was testing this was the fact that a factory NRG 2.0 quick release or D1 spec quick release or other quick releases of that size just snap right on. So it's a big win in Mazda's category for drifters who have say a wheel like this, which was my buddy's wheel taking it and just taking it off your real car, throwing it right into on the rig with no fancy adapters. Nothing like that not having to have a specific quick release like the Fanatec ones are buying all these weird adapters. It just fits on and works. The wheelbase works without having a Mazda wheel connected to it. So in my mind that was a huge win for Mazda and their system. It was incredible and I can't get over it enough. It just felt so good out of the box with the presets they have with some fine tuning on it. You can make it even better and it just works, which is incredible that they've spent the time to make those presets and make them work the way they did. And I just had so much fun ripping that thing around with that wheel as well as the Mazda wheel with the shift light flashing in my face, rev banging and drifting. It just was overall an amazing experience. So overall in conclusion, I can't thank Mazda Racing enough for sending out the RS wheel as well as the R9 base for me to get a chance to drive with and make this review for you guys. I'm definitely excited to continue to use this Mazda R9 base and the RS steering wheel in my drifting endeavors with the SDA as well as continuing it on the channel because it's definitely a solid base. So overall my impressions are extremely great base for the buy just coming in over just over $400. The R9 base is a very great ecosystem and like I said before, with the ability to use a quick release style from a standard car or even get this quick release and put it on to a standard wheel is a big win. The feedback feels great. Once again, I can't thank Mazda Racing enough for sending this stuff out to me. A big thank you to them and a big thank you to you guys for coming back and watching more episodes here on the channel. If you guys want to keep seeing stuff with the Mazda base, make sure you subscribe to the channel. I would appreciate support. If you are looking at picking up your own Mazda Racing equipment, make sure you check on the referral link down below. Click on that. It'll take you to Mazda Racing Store. So once again, as always, I thank you guys for coming back and watching. I'm EvilRabbit. I'll see you guys on the track.


Tezal Shanghai Our eastern China Tezal course is located in the city of Shanghai. Known as the Paris of the East, Shanghai is the largest and most prosperous city in China. The city's long international history makes it a popular draw for tourists, and its many historical landmarks sit side by side with more modern examples of China's recent economic boom. Once the financial center of the Asia Pacific region, Shanghai is well on its way to reclaiming its position at the heart of international commerce. The granting of British, French and American concessions in the 19th century has given Shanghai a unique blend of western and Chinese architectural styles exemplified in the area of the city, known as the Bund. The Bund was once home to banks and trading houses of several European and American companies, and is one of Shanghai's most popular tourist destinations today. Shanghai is also home to the world's largest collection of art deco buildings due to a construction boom in the 1920s and 1930s. More recently, Shanghai has found itself at the center of mainland China's rapid economic growth. The growth has had a marked impact on Shanghai's architecture with buildings such as the Shanghai World Financial Center and the Oriental Pearl Tower giving the city its unique skyline. Shanghai's modernity is balanced with more traditional examples of Chinese life such as the Yaowen Garden and City God Temple. Shanghai has numerous attractions to keep visitors entertained including the Shanghai Art Museum and the Shanghai Natural History Museum. The city is also home to some of the best dining, shopping and nightlife in the whole of Asia. Shanghai's extensive public transport network includes bimesses, trams and a metro system which connect the city and its environs. Trainee accommodation is situated close to all the amenities you will need during your stay with the best nightclubs, restaurants and shops located just a short walk away. The training center is just a short right away on the metro and all the major attractions can be found within seven stops. TESOL course participants do not need to arrange accommodation with us and are welcome to organize their own place to stay. The course fees listed on our website include all course related lessons, materials, teaching practice, assessments, certificates, references, lifetime job assistance and more. There are no hidden costs or extra charges and the prices you see on the website are the prices you will pay. Getting started. All fluent English speakers aged 18 years and over are eligible to apply for our course. The application process takes no time at all and you will receive a prompt response from us. Once your application has been approved, you will then receive further information regarding the content of the course and study schedule as well as accommodation choice, travel arrangements and payment options. Bear in mind that just because you take your course in Shanghai, it doesn't mean you have to stay here to teach. Lifetime job assistance is included with your course and this extends to other parts of the world and our certificates are recognized globally. Please note that due to recent regulation changes only native speakers of English can work legally as teachers in China, though there are no nationality restrictions for attending the course in Shanghai.


Life is short. It's a phrase thrown around all the time. You've probably heard it at some point, with each day that passes, time seems to go by faster. When things slow down or we find ourselves in a rut, it can feel like we're wasting our lives. So, with that being said, here are 5 ways you can stop wasting your life right now. Help someone. Sometimes we struggle to see the value our life brings to the world.  If you have memories of someone doing something nice for you just for the sake of it, you know how good it feels to be helped in some way.  You might say that that person has had a positive impact even if it was small. You can have a positive impact as well by helping people look out for people in need and help them without expecting anything in return. If you feel like you're not accomplishing your life goals or you're existing in a state of purgatory, getting nothing done, try to spend your time on selfless acts. A 2009 study on the benefits of giving sums it up nicely. Happier people give more and giving makes people happier, such that happiness and giving may operate in a positive feedback loop. Work towards a goal. We're willing to bet that at some point in your life it was something you wanted to be or do so badly that it consumed all of your thoughts. Maybe you achieved that thing. Maybe that dream just went poof. Who got distracted by something else or disillusioned as you came to the realization that this thing isn't what you thought it would be. For example, how many kids want to be a firefighter? They grow up and realize that this job is hard and risky. Suddenly, they're amongst the rest of us who know the truth. Chasing a dream is difficult. But just because you might not become an astronaut or an actor doesn't mean you're wasting your life. You can start with small goals. Maybe you've always dreamed of having a swimming pool or a really nice computer or a specific pet. Let these dreams guide you. Chase these dreams with everything you have. What you'll find is an increase in self-belief. You might become more stressed depending on the goal but striving to achieve something teaches you that you're capable of achieving your goals. As Dr Laura King describes, writing about your goals is also extremely important. It offers you a way to re-evaluate and gain perspective on your life. Be social. Sometimes we find purpose in our friends. Sometimes how busy we are isn't up to us as we focus on working or studying. Perhaps you're still in the process of finding a job and you feel like you're wasting time just searching for jobs but getting nowhere. Use this time to see the people you love. Go out with your friends and family. It doesn't have to be expensive even if you just visit them to talk. In their research, Chayun Lim and Robert Putnam explain that there is an increase in life satisfaction amongst religious individuals. This is attributed to the fact that they have a space to be social as well as build social networks and not based on the religion itself. If you aren't religious there are many other ways to build social networks and find communities. If you don't know where to start, why not join the Psych2Go community by subscribing? Experience as much as possible. It sounds like a huge task to undergo. Remember, the keyword here is possible. If you can't afford to travel for example, whether you don't have enough money or enough time, don't worry. Focus on what you can experience. See local bands play live, spend a day in nature, week by week try a different coffee place and find your favorite one. There are an infinite amount of experiences to be had in a single human lifetime. Even laying on the floor staring at your ceiling fan with someone you love is an experience. Not every experience will be a positive one but every experience can leave an impact. Researchers from the Journal of Positive Psychology suggest that people do not seek out experiences as much as they do material goods because of the value we place on them. We value material goods more because their value is easy to understand but the value of experiences is abstract. These experiences will last forever as memories. A life full of good memories couldn't have been a waste. You can't put a price on that. And this leads to the last point. Forget about wasting your life. Unless you committed some heinous crime, no life is wasted. Your life is valuable. We go through times of stress, times of boredom and times of loneliness. It happens to everyone. The quote by Martha Troyley Curtin rings true. Time you enjoy wasting is not wasted time. An easy life is not necessarily a good life but neither is a hard life. If you truly feel your precious time on earth is being wasted, try some of the other tips that feeling of emptiness can be reduced by staying busy and achieving small victories day by day. The key is to seek these victories and experiences. They won't always just come to you. If this video helped you feel inspired to change a few things in your laugh, why not leave a like, ring the notification bell to get notified whenever we post more content like this. And remember to join the SexGo community by subscribing. Thanks for watching!


In this video, I'll go through the steps you need to follow to verify your blog in Search Console if you publish it through Blogger. In order to verify your website with Blogger, you must be logged into Search Console with the same account used to manage your blog. After you click Add Property, add your website URL under the URL Prefix option, and click Continue. That's it. Your blog should be verified automatically after this step. Thanks for watching, and check the Google Webmaster YouTube channel for more videos on Search Console.