 We're going to have to share this. Yeah. So hello. Just passed the Bob Barker mic back and forth for the next 45 minutes. So my name is John Jacobi. And I helped David and some other start WordCamp Miami 10 years ago. And so with 10 years of WordCamp Miami and WordPress turning 15 this year, right? Matt was nice enough to stop by and celebrate with us, which is really great. So it's good to see you. And I've, yeah. And so we sort of have a weird tradition of not doing keynotes at WordCamp Miami. It's not, you don't have like a keynote flagship speaker. And I thought for 10 that I would like, oh, how can I help and do something special? And then when Matt said he was coming, this was the most special thing that I felt like we could do. We, Matt does a state of the word every year that is lots of questions and answers, lots of time, lots of presentation slides, numbers, and everything. But my style is generally a little bit more casual, with some fireside chat kind of stuff. And so I started with WordPress 10, 11, 12 years ago and helped Jeff with WordPress weekly on the weekly podcast for about the past year or so. And one of the things that we do with newcomers on the podcast is talk about our WordPress origin story. And mine is, I'm like one of a dozen people who came in, like the side door, because I found BB Press before I found WordPress. I was looking for forum software that did a very specific type of thing and didn't know that WordPress existed. I found a BB Press first. And so Matt, I'm curious, what is your WordPress origin story? Ah, it actually goes back to comments on a blog post. I had started blogging. I've loved and still love blogs. I think they're the most interesting and coolest thing on the internet. And I was reading lots of blogs at the time. And so I thought, how hard could this be? I'll start blogging myself. And went through a series of software, including moveable type, and then B2. And text pattern, and what else was around at the time, blogger. So playing around with all of these, like B2 the best, B2 developments had paused. So I left a blog post saying, hey, I wish something combined all the best elements of all this other software. And this fellow from the UK named Mike Little left a comment and said, hey, if you're serious about this, I'd love to work with you on it. And that was kind of the inception of WordPress. We started working together from across the Atlantic, myself in Houston, someplace in the United Kingdom. I don't remember exactly the city. We'd never met and actually would not meet for several years to come. But we had this shared passion. We were both volunteers on the B2 forums. We both contributed code to B2. And so we just kind of knew each other through the internet and began hacking on it together. He had written a cool extension for B2 called B2 Links. And so he started to bring that in. I was very interested in making the installation smoother because that was one of the sort of key barriers identified in rule type, which was a lot harder to install and get going with. So I thought if we made that easy, that would be kind of good competitively. And we both just started coding and doing everything, like the support, the documentation, the code, the design, unfortunately, a little bit of everything. So that's how it got started. I mean, that was 15 years ago. Where were you in your life? How old were you? What were you doing? Where were you working? What was it? Because I think that we have a room full of developers, designers, people that are building stuff, inventing stuff, apps, startups, servers under the desk. What was it like trying to come up with an idea and meet people online and patch all? We work with GitHub now. It was SourceForge back then. What was your day to day like trying to make WordPress into a thing? Where did the name come from, even? What was the history of it becoming what it is now? That was a lot of things. I'll talk about the name first. The name came from there was a local blogger meetup. I think actually even using meetup.com, which was around even then. And it was just folks who got together as bloggers. And I'd been going since I was too young to get into the venues they would meet at. Do y'all fly in saucer here? Like it's like a beer pizza place. I would go to fly in saucer during the day when they weren't checking IDs and just stay there with my laptop until later when the meetup was. And so that was at the meetup. There is this awesome woman. Her name is Christine Cermule. She had a website called Big Pink Cookie, which was a pretty big and influential blog at the time. And yeah, she came up with the name WordPress. I think she was driving. And we actually had cell phones. And I feel so old. But she called me and she was like, I checked it. The dot org is available. And that's where the name came from. At the time, I had graduated from the high school for the performing visual arts and started attending University of Houston where I was studying political science because the computer courses I took there were really terrible. It was like visual basic type stuff. And my day was kind of ignoring my classes a little bit. I spent a lot of time online with my friends just working on things. I derived about half my income from saxophone, actually. So playing gigs around town, like big band gigs or different things. About 30% from building websites, often for the same musicians that I'd be playing gigs with. And about 20% actually building computers. So buying all the parts, so I put together a computer which would be 10% cheaper than if you bought them from Dell or something. You'd kind of just assemble that, which I actually really enjoyed. And I kind of missed that. So one of the things when I lived in Miami and before we had WordCamp Central, the first WordCamp was technically a bar camp here when I refreshed Miami. So that's where the roots of WordCamp Miami are as refreshed Miami. And my first full-time WordPress gig was for a company that was in Kendall. And so I would commute from where I lived to Kendall. And then I had side gigs. One that was in South Beach. And I was making the haul all over South Florida to handle all these client gigs and projects and do all the legwork all over the place. And when we had met on IRC and we had chatted online and we had known each other from patching and working on stuff, but we didn't meet, I don't think in person, until WordCamp Orlando in 2009 when the whole core team met for the first time. Mark, Peter, Andrew, Jen, and Brian, everybody. And so for the first few years of working on WordPress, once it had a name, once it had a home, once it was a thing, talk about what it was like to build something and have users and how that happened. Because for me, it was in the forums, like you. It was WordPress.org forums. I can help with something. I don't like something. I can fix something. I can guide somebody. We can put you around in a place. But for you, what was that like, building a community and seeing a vision for things and trying to see it through? Yeah, it's a lot like it. It works today, actually. So instead of IRC, well, that's still IRC, but most people are in Slack now instead of many BB-powered forums, and now BB-Press-powered forums. And I think that the best way to get involved is just to dive in with something. And it could be anything. It could be reviews of plugins. It could be responding to reviews of plugins. It could be updating a patch and track. It could be almost any place that you could imagine that you can type something in a box and it goes on the internet associated with WordPress. That was basically how the rest of us all got started with it. Often the sort of Genesis story of someone like a Ryan Bourne, who was a lead developer for many years, he just submitted so many patches that I got tired of dealing with them. So I was like, OK, you do these yourself. And that was how it got started. And it's also good to remember that often these big things can start with a single step. So even though it might feel like you're doing something very, very small right now, it can blossom. Actually, I don't know if you know this. I was a co-founder of Barcamp. Yeah, there were about five of us. And it was because there was something that Tim O'Reilly did called FooCamp. So for friends of O'Reilly. And a bunch of us weren't invited to it. So we're like, why don't we start our own and make it open to everyone versus being an invite only thing, make it someone that anyone can go to, and then also make it not just can anyone go to it, but can this be replicated in a bunch of different cities all around the world? So that was, everyone happened to get a little history on the story. I had driven out from San Francisco to Houston, other way, Houston to San Francisco with my mom, was very worried about me dropping out of school. And I think convinced I was going to starve. She really wanted me to work at Google, not Cnet, where I took the job, purely because of the food, not because of anything to do with Google. So not working at a place of free food, she was very concerned. So she was there for a few weeks, actually, and just mostly cooking things and putting them in my freezer and labeling it and everything. And so at one point, she was like, hey, I'd love to cook for your friends. Why don't you invite them over for dinner and we'll make some spaghetti and stuff. And I didn't know how to tell my mom that I didn't really have any friends yet. I just moved to the city. So I was like, well, who do I know on the internet? So some of those folks who later did interesting things as well, like Christmasina, later invented the hashtag, Tantech-Cellic was a core developer on internet explorer now, I think Mozilla. So they all came over for dinner. Oh, Malik, who's now one of my best friends. These are just people I knew on the internet, answered support emails for something. They all came over. And at that point, that's when we started talking about food camp because none of us were there. I think it was like the Friday of food camp. And we're like, hey, what about bar, bar camp, food bar? That's awesome. That's a great story. So at that word camp, or word camp Orlando, was interesting for me because I was giving a talk about buddy press communities. And in the front row of my talk is you and Jen and Mark and Ryan and Andrew and Peter. All of the word press leads are in the front row of my talk. I'm talking about siloed buddy press communities at word camp Orlando. And your question to me, which I will forever remember, is what do we do about all of these accounts and all of these social networks and all of these silos that we're going to have if we have 100,000 buddy press installs? What are you going to do with that? You're not going to have an account in every single social network all over the place. And my kind of off the cuff answer at the time was you can't. This was diaspora was kind of distributed social networking was starting to be a thing. And in my imagination, the solution wasn't to distribute it. It was to centralize it. It was to take your ID and use gravitar or use wordpress.org or have a site switcher or have a way to have an identity live in the middle and off to all these things, which ends up kind of being jetpack. In a way, you have all these separate word press sites. May or may not have buddy press on them. Connect them together. And now you're kind of good to go. And we have gravitar, your face on things. And we've kind of gone the other way around. And so when I worked at automatic for a little while in the social team, I got to work on jetpack for a little bit. But I'm curious what, obviously, how jetpack is going. But your vision for jetpack is you're implementing it and watching it grow and turn into things. Is it turning into what you wanted it to turn into way back in 2009 and 10 when we were kind of dreaming it out? Yeah, it's getting there. I mean, I'm a big believer in decentralized systems. So if you ever see me work on something that's centralized, it's only because the technology isn't quite there yet to make it decentralized. I would much prefer to all be decentralized. And perhaps with things like, oh, how do we have the same identities across all these hundreds of thousands websites on the web? Oh, could we have a distributed database? Does that look like a ledger? Could something like blockchain? Yeah. So things are starting to come together that could afford, albeit right now in a very expensive way, a better implementation of these. But in the meantime, I want WordPress to be as successful and widely used as possible. So that's kind of the genesis of jetpack. Like, what do we need to put in there that for either philosophical or technical reasons can't go in core, like, let's say, integration with Facebook and Twitter, stats, an image CDN, because we need our sites to load in under five seconds on mobile. And it's not going to do that if your image is unoptimized for different device types and things like that. So all of those things are what we decided to say, well, let's put kind of a single plug-in and get it in as many of the WordPresses in the world. And we have stats that show, like, if a brand new person starts with WordPress, if they have jetpack installed, they are double-digit percentages more likely to keep using that site one month, six months, 12 months later. So there's things like this that show that it's working. But there's still a lot of miscommunication around jetpack, just like there's a lot of miscommunication or misunderstanding about Gutenberg, almost everything in the WordPress world. We obviously need to communicate better. Chris, great, this great presentation. You listed 10 different ways to optimize your images, but not photon and jetpack. So like, there's obviously a lot that we need to do to get the message out there a bit better than has been thus far. So it includes a number of really free things that are great, including photon, which is an image CDN. So it takes all your images, distributes them throughout 26 data centers all over the world. If you go to DNSperf, it is the fastest network, neck and neck with Cloudflare. So basically, it's something that normally you'd have to pay a lot more for, and then optimizes them on the fly for any device. So obviously, devices have different pixel densities. They are different sizes, all these sorts of things. So it can create all that on the fly. But if this were happening on your server, it would be very, very, very, very expensive. But because we've built this kind of global network, I would say one of the things that Automatics has been most successful at is actually the systems, and building up these kind of network of data centers that can do massive processing and massive speeds, basically instilling all over the world. We can now be competitive with like Facebook or Twitter or these other centralized networks. So it's kind of the best of both. You get complete control over the code and to run it wherever you like. But then you have a hybrid where you'll get some of these more centralized-like features, but without giving up the freedom or control that you have with installing it. I think this hybrid approach is actually going to be, in many ways, what I would like to be the future of web software, because the technology is not quite there yet, or maybe the cost is too prohibitive that even if you ran these things, like a video transcoder, image CDN, or maybe the APIs don't allow it, like with centralized services like integrations with Facebook or Twitter, it would be almost prohibitive to get everyone to set all those different softwares up on their computer or on their server. So this is the in-between. And I encourage everyone to check it out and install it. It has some JTRIP code somewhere in there, so. So it reminds me a lot of solar, solar energy. Like, anyone can tack solar on the roof of their house. And that's good, because you get to do it, you get to own it relatively speaking. It's sustainable. It's your solar, but at the same time, there are huge solar farms out in huge places, because they can generate solar more efficiently in a better place with more square footage, and they can ship that solar out to everybody else. To me, it seems really natural to want to take the hard to process things, kind of hide them away a little bit or offload that processing remotely so that it's out of sight. Nobody has to really worry about it. It is just the thing that gets fed back into you. And then there are people or individuals that philosophically want to own it. They want to do their own image crunching. They want to do their own everything. And for that, it is open source. You can run your own instance of photon. The folks at Human Made forked it and have tacky on. There are other instances and ways that we can kind of navigate this. It seems very natural to have one bigger way of doing it that offload that processing and then have one smaller way of doing it individually if it's something that you really wanted to do. And one of the things that the segue there is that one of the phrases that you have used over the years that has kind of deeply ingrained in the WordPress community and the culture and the philosophy is the idea of democratizing publishing. And I think when I would first hear you say it years ago that I didn't really understand what that meant until I was older and started getting more politically involved and kind of was able to see what that vision was. And recently had heard Elon in regards to SpaceX talk about SpaceX democratizing space travel. And I thought like he's listening to WordPress stuff. Like Elon is getting democratizing space travel from WordPress and democratizing publishing. And there are all these little isms that are like WordPress cultural things, code is poetry, democratizing publishing that are like very WordPress specific. And the word, the name WordPress to me is as good or better than like movable type is like really great historically the reference to Gutenberg, Gutenberg itself. All the little hints and respect that gets paid back to the way that we got to publishing on the web now is really neat. But I'm curious, how did that become an important part for you to, I mean not just to pay homage to it but to name Gutenberg, Gutenberg is, I don't know it's really compassionate. I think it's really smart. I think it kind of proves a lot of things. So I guess my question is kind of how did we, how does it get, how do you dream these things up or how do they flow out? Where does it come from? Well like many of these things they come from collaboration, right? The name WordPress itself I didn't come up with. Someone else came up with it. And that's, I was talking to some students earlier and at one point I tried to emphasize, I'll emphasize to you all is that as a kind of a solar coder, we have this vision of like the solar coders sitting in front of the laptop all by themselves. But even from the early days of WordPress that was people in front of the laptop talking to other people in their laptop. Everything that was great that we ever created came through lots of collaboration, lots of contribution. I don't actually, I need to look up because I don't remember exactly how the name Gutenberg came about. But you can see it as a natural outgrowth of two things, one like you said this kind of like illusion to the printing press and kind of the ideas of publishing being an enabling force for both not just democracy but just humanity, like how we connect with each other. But two WordPress is always, I feel like hearken back to the folks who came before us. Every release is named after a great jazz musician. Jazz of course being a music of improvisation and collaboration. There's some solo jazz but not that much to be honest. It's really all about interaction between musicians. There's lots of references in the code and even some of our obscure naming things. If you wonder why the Wiki was called the Codex or the store is called Mercantile. Like these are kind of references to things hundreds of years old sometimes. And we wanna, and I'm a big believer that we're not doing anything new actually. Everything that we're trying to accomplish. I mean some of it was talked about by Stuart Brand in the late 80s or there's pioneers of computing and then pioneers of publishing. And then if you go back pioneers of like what the technology of its day. Like what does it mean to be able to construct arches and then create buildings from that. What happens when you put an organ in it which was some of the most sophisticated technology of its time when you can propyrus. Like all of these things, we don't think of as technologists but they actually really are technologies. Double ledger and counting. I love these things. Because when you go back, we're gonna look hopefully at some point just like you said the idea of democratizing has become kind of democratized. And it's now like a phrase and almost every startup puts in their thing. I'm glad Elon's using it. But like the others I don't know sometimes. But these ideas become, you don't even know, it's so embedded in the culture and so part of the zeitgeist that you just feels like it was always there. And it gets hard to imagine the time before cell phones like smartphones like iPhone, right? Half of you are looking at them right now. What did we do in talks? I don't know. We had laptops actually. I didn't remember that. But they were offline. It was really frustrating. The batteries were dead. The batteries dead, yeah. It was, so I have an idea for a plugin based on everything you just said. So just like Gutenberg is a great name and I don't think that it's any mistake that there are blocks that we're building with because that's what movable type was. They were just blocks. They were letters. Some of them really elaborate designs and flourishes and everything but they were just blocks. Johannes Heidenberg is credited as the originator of cryptography. And so I have this idea, which I will give to y'all to build it because I haven't had time. This could easily be a jetpack thing too. So that is, I think it would be neat in a plugin like this to insert zero with characters into post-contact with a hash to sign them. So if someone plagiarized your content, they wouldn't know it because you would see the zero length character in your paragraph. You would know it was your contact because you would have the source of truth for your blog post. It sort of pays a little homage to cryptography and some old school kind of neat things. But I haven't had time to build this plugin. So for everyone else that's out there, feel free to take this idea and run with it. Yeah, right. I think... What, is it? For five seconds, it's available. It's gone, it's done. But that's one of the things that attracted me to WordPress is the lexicon of historical references because they pick at you and you go, that's neat, what does Codex actually mean? What is Mercurial? I know the word, but what's the history? And so, tiny MCE in Gutenberg, you have said are your sort of white whale and we've talked about it on the tavern on the WordPress weekly, but in as long as I've known you, I've never seen you smile the way that I asked you, how is Gutenberg turning out? Because the visual editor has always been the thing that you like to know could be better. And so, tell everyone a little bit about why you want Gutenberg to be what it is. Yeah, and who was in Matt Cromwell's presentation earlier? Okay, cool. You all both got seats early and probably have a pretty excellent idea of what Gutenberg is. I like that we did the back-to-back mattes. It seemed like a good way to stack it. I think that the web, what we're able to build on the web has evolved so beautifully and the web has kind of turned into its own medium. Like what makes a great web post is entirely different from what would be a good magazine page or a good Word document or anything else and so it's become this own kind of canvas. My colleague John Mehta talks beautifully about how there's different types of design and distinguishes classical design from computational design. So all of the editors that most CMSs have used in the past were kind of more like this classical print design modality where they really, you almost were writing in a box that sort of felt like a page. They were all very derivative of like the, you know, Microsoft Word to be honest. Who's ever done that thing where you like try to rearrange or change the alignment of the image or move it around in the post and then like you just lose your whole life? Okay, okay. Who has ever, including Wordpress today in the past, when did, well you should know, when did Tiny MC come in? Was it 1.5? Which was 2005? Okay, so in the past 13 years, who's ever switched to code mode because the wizard would mess something up? Right, and then you fix it. But I mean, we are incredibly privileged and lucky to be able to switch to code mode and come back out alive. You know, you are very much in the 0.1% of the hopefully 8 billion people that'll be online in 10 years. Because you know that, you understand that code. With Gutenberg, we want to give the flexibility of what many people in this room can create through understanding code. We want to give that power and freedom to everyone. To the next, you know, hundreds of millions of people who come online and graduate to publishing with Wordpress. And I want them to be able to create those pages, those stories that are so compelling because they're not just text and images, properly aligned images, of course. You can have videos, you can have parallax, you can have audio, you can have contact forms, you can have interactive elements. You can have a block that only exists in the world for your site. But you use it at the end of, you know, maybe you ask a question at the end of every post and people do a little poll. Like, there's so much interactivity. And that's what makes the web beautiful is it's two-way, you know. It's what people missed about like the idea of interactive TV. People imagine that once we had this IP delivery networks to every home, that it would be more of like a one-way medium. That it would kind of look like how the dominant media platforms at the time. Just like when they first started making movies, like the very first moving pictures were just videos of plays that people were putting on, you know. We think that the new medium is going to follow the old one very closely. And, you know, WordPress and many others have shown that that's not the case. And with Gutenberg, I want to build the foundation that for the next 15 years of WordPress we'll be able to build on. And that's what's beautiful about blocks is they're starting, as Matt said, it starts with just the editor. It starts with just kind of editing things. It's replacing TinyMC in that edit screen. But it moves to replacing every single other part of what you publish online. And now there's just one concept which is a block. And it's a developer, something you can write once, which is a block. And people can put it in their footers. They can put it in their posts. They can put it on their pages as we do more multimodal publishing in the future. Like, that block can transform to something for email or for mobile or for AMP or for, like, all the other places that your content management system, namely WordPress, can publish to. And maybe in the future, those blocks are viewed via VR. You know, there's so much, yeah. There's so much that this kind of enables us by... It's so rare in software development that you can both make something way simpler. We're going to be able to take about, like, a dozen different concepts in WordPress, including menus, widgets, et cetera, short codes, and kind of simplify them down to this one thing, a block, but also make it much more powerful. And so we're able to do both at the same time. This is kind of a once-in-a-generation opportunity for WordPress. And to the extent to which we execute on it well or not, I think determines, you know, whether there's going to be a WordCamp Miami 20. So no pressure. So I think we have 10 minutes left. And one of the things that I've always admired, because I have a hard time really, truly imagining the enormity of it, is the juggling of the .org side and the .com side. Sort of the spiritual leadership of democratizing publishing and the open-source project. And what I think really is sort of the generosity of letting other people kind of roll with it to implement their vision and their ideas, because there are lots of things that are in WordPress that don't necessarily directly impact democratizing publishing. Multisite. I mean, sure, multiple sites helps that, but it's not a thing that directly does that. Or comments are not necessarily a thing that help democratize publishing, but it is important that there's interaction and that there's dialogue. And so the customizer, being able to make it look beautiful and pretty the way that you want to customize it, is useful, but it doesn't necessarily help people hit publish and, you know, spread what they're thinking or talking about. And I know that you do, which is good. But there's that side of it where there are pieces of it that are not 100% a part of it and that we have a community that gets to decide together what we think that vision is, and you do sort of let people roll with it, even if it's not 100% right or you're not 100% sold. REST API is a good example of that. But on the flip side of it, then you're sort of the top of the dot-com and automatic and the money-making side of it, too. And so, aside from the community pressure of leading a project in the right direction, is the economic pressure of, I mean, 50,000 jobs, I guess, at Automatic now? How many employees does Automatic have? 700? 700,000? No? And so I'm curious if this was your vision 15 years ago and now that this is where you're at, what does your day look like living it on both sides? How do you balance it, the juggle and the height of it or the yin and the yang of it or the ups and the downs of it? What does that look like? Sure. There's a lot embedded in that series of questions. I'll show. I've got lots of questions. I guess a good way to start is like, you dance with the one that brought you. I started with WordPress. The WordPress core hat that I wear is the first hat I wear. So if there's ever something, if there has actually never happened, but if there was something that it's like, it's going to be this or that, I'll go with the WordPress. Part of why that doesn't really come up is because I truly believe that long-term, these are completely aligned. And kind of the experiment with setting things up this way was kind of nonprofit on its own, can do so much, a for-profit owns can do so much. I was really curious to experiment that if we got this kind of working like a flywheel where a nonprofit and for-profit were working together, what could happen and what could be created? And it turns out that what can be created actually dwarfs what any of the approaches of either or without the other has been. The size of WordPress market share dwarfs, even the incredibly successful public companies like Shopify and Wix. We have 20 or 30 X, the number of sites in the top 10 million running WordPress versus these other things, even though they make. Shopify is right now valued at $12 billion. I think that most of the trouble in capitalism actually comes from short-term versus long-term thinking. And that's particularly the public markets have incentives around quarter-to-quarter results, what's going on in the economy, like lots of things that don't actually have to do with the long-term viability and value of the business that's being created, it's going to happen. That's why I'm curious about things like the long-term stock exchange. It's a new project to perhaps create a separate exchange separate from NASDAQ and New York Stock Exchange that can perhaps have long-term incentives and basically incentive structures and ownership structures that encourage long-term shareholders. And for automatic, we only have these long-term shareholders right now. We're a private company and so our investors, we can kind of pick and choose who they are and choose the ones that are in it for the long run. Some of our investors invested out of a 2002 fund, so it's been now 16 years. So you can find this kind of what's called evergreen capital that can really think long-term like you. But at the end of the day, there's lots of conspiracy theories and everything around automatic and everything else. I mean, automatic only makes maybe three or 4% of the money in the WordPress ecosystem. So for every dollar we make, there's about $25 made by other companies in this space. And if you actually look at the history of many successful platforms over the years, that's very consistent. And it's actually something we explicitly target. So I believe that that's actually very, very healthy that for every dollar any one of the companies is making. There's a lot being made outside of that. Why emphasize things like Fire for the Future and others is that right now we're in a little bit of a period where there's some companies coming in very aggressively and so gathering a lot of the wallet share. So they're making a lot of money. But they're not really necessarily putting anything back into the core development. And so that has kind of a double whammy. The core starts to suffer. And then the companies that are contributing a lot back are essentially being outcompeted and put out of business. And so that can create a downward spiral. But luckily the vast majority of folks in the WordPress ecosystem really understand that it's not just software. It's a community. And it's something that you have to garden and grow and invest in for it to continue. The future success of WordPress is not guaranteed. It's going to be the result of a ton of hard work from folks in this room. It's going to be a lot of discussions online. It's going to be a lot of disagreements, but ultimately deciding that if we do this together, it's going to be a lot better than if we do it separately or on our own. And if there's anything that I would hope to be the legacy of automatic, it's setting an example for how to build a business that can both do well as a business, but also create something far, far larger as a movement and contribute to something bigger than itself, bigger than any of the paychecks that any of the folks who work for automatic get. That is this thing that hopefully puts a dent in the universe a little bit, that we call WordPress. And I plan to keep working on that the rest of my life. As long as y'all will have me, I plan to stick around. And I feel incredibly lucky to have found something that can be my life's work from a young age when I was 19. So that experience, you know, sometimes people ask me, like, why aren't you tired of WordPress? But I come to some place like this and I see this, see a beautiful, intelligent, like excited faces. And I walk through the sponsor area and you see all the different companies and I go to the talks and hear how people are talking about things and learning and trying stuff I never would have imagined. And honestly, you can't go to a work camp and come out uninspired, you know? You met someone, you made a friend, you learned something, you heard about something. Even if it's as simple, you know, one of the talks I was in earlier talked about, they saw this presentation and there was like a WPCLI command that like changed your life, you know? Maybe it's that one line that you're going to put on the command line or maybe it's a concept or maybe it's an idea or, you know, something that we talked about the beginnings a little bit earlier. This all starts small. So the germ of something that you are going to hear this weekend could be the thing that becomes your life's work, that you're working on in 15 years. Like I'm working on something 15 years from 2003. So keep that in mind as you go through it and keep coming to work camps. Right on time. Just like Gutenberg. Awesome. David, thank you. Actually, I can set up so if you want to take another five minutes. Oh, wow. So, yeah. We can take some audience questions. I would prefer to not go running up and down the stairs just because it's hot in Miami and I don't want to, yeah. So if we can shout a question and then I'll repeat it for the live stream. You're going to hurt yourself. Yeah, we'll just repeat it. Question. Right here in the front is easy. The question is there's been talks of a team at Google that will be working with WordPress and they put out actually Google is hiring WordPress people. So they're hiring for a WordPress role. And what's going on there? Is that the question? No, that is not a very much true. Google is hiring people to contribute just to WordPress. So they're doing better than some of those WordPress companies. The cool thing is that we make the web, they index the web. It's a complementary relationship. And as WordPress has grown to comprise more and more of all of the websites that matter to Google and something I hear from there is particularly in certain countries because WordPress is localized and to languages and so it has a very good in some countries in some languages which aren't say very commercially interesting to like the likes of like Facebook or someone else. WordPress actually comprises like a large, maybe even majority of all the web content published in that language. So Google is really good at internationalization. They're really good at speed. They're really good at a lot of these things. And you know, it's nice to be able to deepen our relationship with them. I mean WordPress has always been great with SEO and web standards and all that sort of jazz but to actually have them involved in saying how do we make every single site faster? How do we run tests against every single theme in the WordPress directory and show how fast they are doing something next to their ratings? Like that's a lot of what the initial work will do and you might have heard me talk about the Tide project at the state of the word and I almost said Philadelphia in Nashville in the previous year. That's what that is. So Tide is basically a project that's going to say take every plugin, every theme and essentially run it through a suite of tests. Some of what should be organized around performance and then we'll be able to show that impact because there's tons of data that shows that particularly on a mobile device who loves waiting like 10 or 15 seconds to load a web page when you click on it? We got one. The slow web movement. It's like the slow food movement. It's a new thing. So that is typically, you know, we need to get that under three or four seconds for it to matter and for it to be competitive with kind of the app experiences and we're working together to do that so I'm very excited about it. Cool. Last question. Sure. So the question was like we talked about blockchain and JTRIPS watermarking plugin like it's automatic thinking about any of that. Now I'm not here to pronounce our ICO or anything but I, you know, we were one of the first large websites to accept Bitcoin for payments. So there's an editor by the founder of Ethereum whose name I always mess up. Bitcoin Magazine and there's a big, there's a 2012 or 2013 issue with like the WordPress logo on it which is really cool. So this is something that I think, you know, people forget but all of these cryptocurrencies, not all of them, but basically all the ones that matter are all open source. And so it's very, very cool to see like open source start to be paired with business models and maybe bootstrapping like the future Singularity AI all in one. And, you know, many people would automatically see themselves in the following distance early days and keep a close eye on it. But thus far as you've probably noticed like a lot of these things are being investigated by the SEC now, we have waited and will continue to wait until there's like a really, really clear need or something that actually enables in a very user friendly and consumer friendly way something that was impossible to do before. That's where I think that it becomes ultra interesting perhaps that bootstraps kind of the next phase of the internet. So, all right, Maroon, you closed it last time. You can close it this time. Okay, so there are two questions in there. The first or the second was like, is Gutenberg doing any integration with like image sources? Like Unsplash or others so you can like bring images really easily into your Gutenberg post. I don't know if that's in Gutenberg core. I don't think it is. Calypso, which is a different project that automatic makes, has started to integrate a lot of those free image sources. And so we are starting to integrate some of those through that. So perhaps that could be something that we enable through a plugin for Gutenberg in the future because I agree that just being able to type in like, you know, dogs and getting awesome pictures of dogs, it's really cool to have. Another cool feature on Calypso is the, which you can use on WordPress.com through Jetpack or WordPress.com site is the Google Photos integration. I'm really excited about this. So is anyone use Google Photos? I'd recommend checking it out. It's actually really, really good. It puts in all your photos into the Google Cloud and then actually analyzes them all. So you can actually search your own photos for a dog and it'll look through all of your pictures and it actually finds like, there's a painting of a dog in my mom's house. It finds that as well as like the actual dogs and everything else, identify spaces. So there's an integration where you can just click login with Google and then within your media library, all of your Google Photos are instantly there. And so you can click and then just bring them over. So that's in Calypso and Jetpack. So you can run it on any of your sites in Jetpack. To the first question, which is advanced custom fields, ACF is adding support for Gutenberg? I don't know if I can speak to more of whether that's going to be editable in the front end or not. But the idea with Gutenberg is to basically decrease the distance between what you see on the front end and the back end, while still having a really rich interface for being able to edit it. So when you see some of these pure front end approaches, one, they can often be like, just like a pure, whizzy wig moving images around can sometimes get stuck in a little bit. And two, they often don't exist on mobile. And we think mobile is going to be a really, really important part of that next 15 years. So that's why we took the slightly separate approach that we did. But I'm pretty excited about it becoming a lot more of creating tighter conceptual links between what's on the front end and the back end. Cool. And thank you all so much for this exciting day. I really enjoyed it. Thank you, John.