This week on WPwatercooler, join your hosts Jason Tucker, Sé Reed, and Jason Cosper for a captivating conversation exploring the dynamic world of AI in the realm of WordPress. Together, they’ll discuss how artificial intelligence is revolutionizing various aspects of WordPress, from streamlining code development to enhancing content creation with smart algorithms. They’ll share their insights and experiences, and highlight the latest AI tools reshaping the way we interact with and manage our WordPress sites.
WPwatercooler
EP452 – Doom or Boom: AI in WordPress
Panel
The WP Community Collective supports and funds individual contribution and community-based initiatives for the open-source WordPress project. WPwatercooler are supporters of WPCC and you should be too!
Episode Transcription
Jason Tucker:
[0:09] Oh, this is episode number 452, Doom or Boom, AI in WordPress.
Sé Reed:
[0:16] What’s it going to be, folks?
Jason Tucker:
[0:20] I’m Jason Tucker. Go over to my website, Jason Tucker.blog for fun stuff.
Sé Reed:
[0:26] I’m Sé Reed at sereedmedia on most of the things all over the Internet, wherever those things are.
Jason Cosper:
[0:32] And you all know who it is. This is your boy, Jason Cosper, AKA Fat Mullenweg, and we’re back at it again on the world’s most influential WordPress podcast.
Jason Tucker:
[0:41] You can go listen to that podcast wherever it is. You can find great podcasts.
And come hang out with us on Discord. Links are in the description below.
Jason Cosper:
[0:51] Surprisingly more active than I remember from the last time when I checked in.
I mean, I hang out there, but sometimes I just forget.
Sé Reed:
[1:01] It’s the icons.
Jason Cosper:
[1:02] Icons.
Sé Reed:
[1:02] You know what? Definitely the icons. I added the icons and really just, it pops.
Thank you, thank you. Also, it’s not, it’s, um, what I realized this week was that the WordPress, I knew this, but it didn’t, like, kind of click for me.
But I’m saying this because it’s really relevant to any of our listeners or, and just us in general.
The WordPress Slack is specifically intended to not be, be and in fact has been quoted as being not a water cooler channel, water cooler or water cooler instance, water cooler being, uh, you know, the chit chat that there’s often a channel for in Slack instances, but there is not one in WordPress Slack.
And I have, I had the amazing revelation this week that our discord is the WP water cooler. What?
Jason Tucker:
[1:55] Are you kidding me? We lived up to our name? Holy crap.
Sé Reed:
[1:59] That means everyone can come over and chit chat and we’re not gonna like, you know, make you contribute.
I mean, you should, but like, we’re not going to make you contribute.
Chit chat and you can share memes and you can like, you know, post random stuff and gifs, especially memes and GIFs heavy on the memes and GIFs.
Anyway, I have that idea. So like…
And especially with Twitter, like literally imploding into itself, like WordPress needs a place to chit chat.
And the post that Slack is good sometimes for stuff, but still Slack.
So anyway, come on over and invite your friends. We’ve got icons.
Jason Tucker:
[2:33] It’s free too.
Sé Reed:
[2:34] It’s free. And we have icons. Did I mention the icons? Okay.
Jason Tucker:
[2:37] It’s free. We have icons. That’s awesome. That’s literally our, our tagline.
Sé Reed:
[2:42] It’s free and we have icons. Oh dear. Icons were not added by AI.
I chose those with intention.
And I realized though, another thing I realized this week, I was shown by a friend, speaking of our show topic, AI can give you emojis based off of text prompts.
I’m like, wait, what’s happening? I think it’s like the singularity, right?
Like if we feed in text and it comes back with emojis And then we’re like, here’s the AI emojis. Like, yeah, I, it like kind of blew my mind a little bit.
It’s part of a bigger project. But just that component.
I was like, I was now I have to go in and be like, Hey, chat GPT, can you please interpret this text for me?
Jason Tucker:
[3:33] That’s actually that’s actually not a bad idea.
Sé Reed:
[3:36] That’s actually not a bad idea. What’s your vibe on this?
Jason Tucker:
[3:39] Give me the general Yeah, before you send it, it could be your drafts, where like you write a thing and you put it in drafts and you send it to it and you’re like, hey, can you tell me what you think about this?
Which is exactly what I did for this show topic.
Sé Reed:
[3:53] That’s right.
Jason Tucker:
[3:53] Because this topic’s title, I read the title and I thought doom or boom, like boom, like it blew up and it’s gone. Like, you know, that’s what my brain was thinking.
Sé Reed:
[4:03] Suggestion, let’s just say.
Jason Tucker:
[4:04] But more of a boon, but you know, yeah.
Sé Reed:
[4:08] It’s like a boom time, like the gold rush. That’s the thing.
But so what did you do with that title? You fed it into the did say come up with a good title or not?
Jason Tucker:
[4:19] And it goes, yeah. And then say goes, well, shoot, let’s do it.
Jason Cosper:
[4:25] You asked it to come up. You asked it to come up with some titles as well.
And man, it really got stuck on some suggestions. Yeah, they were awful.
Jason Tucker:
[4:36] And you know what’s funny is you can tell it. You can say like, can you just stop mentioning this word? Yeah. Like I know you love this word.
And then it’s just hyper focus on another one. Yeah. And it goes like, oh, okay. Let me go find another buzzword to go, to go use. Yeah. Yeah.
Sé Reed:
[4:50] It really, really, it’s, it’s so good for specific stuff, but honestly the validation component.
I also, I put on Mastodon at one point. I, I recently experimented with all the, all the AIs just to see which one I like.
Results, chat, GPT, hands down, there’s no comparison. The other ones are lame.
But I did use BARD, which seems like, you know, more of a soft approach, sort of like, I don’t know, it’s weird. It’s like, I’m going to Google that for you. It’s kind of like Ask Jeeves. But like, like BARD, I feel like Ask BARD.
But like, if Jeeves were like more AI-y, had been more of a chat bot.
I feel like that’s the personality that BARD has.
My favorite thing about Bard is the drafts, but not the point.
Point is, I asked it. I told it I was tired.
I said, I’m tired. And it, because I was, and it was like, I’m so sorry you’re feeling tired. Maybe you should take a break and rest. And then it like gave me like all these points. It was like, you might consider taking a nice walk.
You might consider calling a friend, you know, maybe have some water.
And then I really hope you’re able to work through this and make sure to take care of yourself because otherwise, you know, you could get burned out.
Jason Tucker:
[6:01] Funny tech talks to get to make you happy.
Sé Reed:
[6:04] Thanks, Bart. No, Bart is not going to refer me to tick tock probably.
Jason Tucker:
[6:07] No.
Sé Reed:
[6:09] Yeah. Here’s some YouTube shorts.
I don’t want to meet. Man, maybe we can talk about this is a little side tangent.
But maybe next week we can talk about when big systems go offline.
Like when I panic texted you guys about Google going offline.
We’ll talk about that next week.
Jason Cosper:
[6:29] That was I use DuckDuckGo. So I was like, I don’t know what Sae is talking about.
Sé Reed:
[6:36] But this is Google thing.
Jason Cosper:
[6:39] I mean, I still use the the bang search if you just add like a exclamation G to whatever search on DuckDuckGo, it’ll route the thing to Google.
So like if I don’t like the results, you can, Yeah, I just add that little extra bit or whatever. It’s, it’s handy. It’s helpful.
Sé Reed:
[7:00] You’re like, no, you suck. Try again.
Jason Tucker:
[7:04] Yeah. So I also asked AI, what should we talk about on the show based off of the title that you it was just like, oh, you should talk about how AI is going to change the way in which you would use WordPress. I’m like, wow, thanks.
I really We appreciate you going through the extra, you know, I wrote all this fluff around it, which it loves to write fluff.
Sé Reed:
[7:30] And, and I wish I could get it to like not be as fluffy, but this specific fluff, that’s actually what I wanted to talk about.
Jason Tucker:
[7:39] Yeah, please.
Sé Reed:
[7:40] Uh, so the, the, well, there’s two main things I’ve been using chat GPT for all the AIS, but chat GPT, as I, as mentioned, uh, is, uh, One is helping me with my code, which is awesome.
And the other one is filler content for all my websites and all the clients that are not giving me content.
So I’ve just been generating content, they’re popping it up there.
And then they’re like, oh, we need to edit that. And I’m like, don’t you? You should totally edit that. That’s a great idea.
And then they like change it and they’ll give you like the edited text.
But like, it is so much easier than being like, I need text to fill this blank spot or this lorem ipsum text because so many of my clients literally cannot envision what they want there.
They know what the message is, but if it’s not there, they can’t envision it.
So really, it has streamlined my content development.
Because it’s not just random filler text, it’s custom filler text, right? So it can sound almost right. And it’s so good at writing.
Jason Tucker:
[8:48] The client’s just going to go like, this is perfect. Thank you.
Sé Reed:
[8:51] I mean, hey, whatever. I’m telling them it’s AI generated.
I’m like, I didn’t write this. I just, you know, fed in some prompts.
This is so, you know, do with that what you will.
But yeah, they, it’s been great. It’s fluffy though. That’s the thing.
So like, it’s really good at marketing text. And that’s because I think so much fluff and selling stuff is on the internet.
Like that is, you know, a big source of its data. And there’s so much marketing ease out there that it’s, you know, it’s like this racist used car salesman.
Yeah, it’s- That’s like the problem with AI.
Jason Cosper:
[9:33] It really is. And there was what the Washington Post a story on this just this week about the data that was used to train a lot of these AIs came from places like the anti-trans Kiwi farms and other hate sites and things like that where it’s like, ooh, maybe you guys like, so a little bit of your text.
Sé Reed:
[10:02] Like, literally, even just Reddit. Like, Reddit is, why wouldn’t it be used?
It’s so much conversation and people, but like, we’ve all seen where Reddit goes when you go into the depths.
Jason Cosper:
[10:14] I mean, there’s a little bit of Breitbart peppered in over the top of your content.
Yeah, a sous-sault, if you will.
Sé Reed:
[10:28] It’s not funny. It’s like not funny that exists. It’s just funny to think of it as the the sous-sault of it. But it is not actually funny that that is the case.
So I just want to be clear about what I’m laughing at. Here.
Jason Cosper:
[10:41] It’s clearly it’s a little, little little reminder that you need to be careful about the stuff that you are copying pasting from a chat into your, into your site, you need to, even though you have something that I mean, I have in in a few occasions, I tend to be a little more reticent to lean on AI because I’m concerned about some of the garbage that it might spew out.
And then we’re just putting this up on sites.
And to train the next version of GPT or whatever, it’s going to start talking about, yeah, yeah, it’s the Mobius strip or whatever, or no, it’s not.
Sé Reed:
[11:31] It’s the snake eating its tail. Yeah, or a burrow. Or both. But this is actually even worse because it’s, it’s with, like, reduction, like, what’s that copy reduction? There’s a term.
Jason Tucker:
[11:46] Yeah, Yeah, it’s shitty content all the way down is what it’s like a principle or something about like, yeah, it’s like taking a photocopy and then photocopying the photocopy, which then gets photocopied.
And then you fax it and then you photocopy it again.
Jason Cosper:
[12:03] We’re 12 minutes in I’ve already dropped or boros and Sue song.
I think I’m actually my cap this week.
Sé Reed:
[12:13] I’m not wearing my geek shirt, I’m wearing my, I’m not an existential threat to WordPress’s future. So here, speaking of my t-shirt and geek.
Jason Cosper:
[12:21] I was gonna say, do we think that AI.
Sé Reed:
[12:23] Yeah, that’s the question, that’s exactly.
Jason Tucker:
[12:26] Yeah, that’s right.
Sé Reed:
[12:26] Ask it.
Jason Cosper:
[12:27] Please, no, no, no, say, please, I insist that you ask it.
Sé Reed:
[12:32] I wanna ask it, cause I want you to answer it. And I’ll also answer my own question, as we all know, all of us here and our listeners.
But is AI an existential threat to WordPress?
Done.
Jason Cosper:
[12:48] If, if you are using an AI code generator that is potentially trained on non GPT, or I’m sorry, non GPL, there’s so many G’s now.
So many G words, non, non g, p, l, content that you know, you run the risk of including something.
Sé Reed:
[13:12] Wait, wait, wait, hold on. That was you’re saying it’s OG GPL, and then it’s non GPL when it comes through.
So it’s non OG GPL.
Jason Cosper:
[13:21] Well, one, you’re not crediting the source of where you got the code from.
But also, you are not. I mean, they’re basically they have trained the AI is they have trained some of these AI is on public repos that may have a license that is not GPL compatible, that may be under a proprietary license that says, Hey, this is why this JavaScript code, whatever, shouldn’t be used.
And they had to essentially that the plugin, I agree with that.
The plugin team, though, specifically, Mika put her foot down and said, Hey, like use of code generators, like you need to go through the due diligence if you’re going to have something write a plugin for you that you’re going to put in the WordPress repository, which requires it to be under a GPL license to actually make sure that that code is GPL licensed.
Sé Reed:
[14:29] So I have two questions based on that. Well, I have one statement and a question. Uh, one.
[14:36] I have been working in WordPress for all of it.
I don’t really build in anything else, right? So I am constantly, well, now less so, but like in my whole career, constantly in forums, on documentation sites, pulling snippets, this, that, from all sorts, from gists and gits and whatever, right?
[15:02] All the Gs. and pulling them together into code that is used for my client sites.
And I’m not necessarily, I’m not publishing that code again.
I’m not, it’s like the whole, I’m selling the collecting of the code and the assembling of the code, whatever.
But I have not ever checked any of that code for any sort of licensing because, well, I guess, because it’s WordPress stuff, right?
And I’m just like, oh, it’s WordPress. It’s like just open and free.
So the idea that there would be some code that would come through, that it would like, you know, spit out some code that would be proprietary or non-licensed is like, or unlicensed, I don’t know, or not usable the way that I’m using it or whatever to like be used.
Not appropriately licensed, not appropriately licensed. Yeah.
Like I, one, I wouldn’t know how to check that.
And two, um, what, like, is this literally like, what is proprietary code then at this point? like because there’s so many ways to like write.
[16:10] A thing? Like, you know, like, you know, like, I don’t understand, like, does, is it, it’s like, copyrights for literature, you know, if you take a section, like, that’s a certain length, it’s not taking, it’s just exerting.
And then if you use it for, like, fair use or something. Yeah.
And so you can’t take like, you know, three paragraphs, but you can take two paragraphs.
Like, like, is there some correlation to that?
Or is it just like, this code is copyrighted and therefore you can’t use this tag like that? I just, I don’t even understand how you could own code, which is like, you know, letters and numbers. I don’t understand.
Jason Cosper:
[16:53] See, you are coming at this from an interesting place. Like as you have grown, you know, and built sites and helped clients out and everything else, you know, all WordPress, I mean, outside of being told to learn JavaScript deeply, but up until the past few years, all WordPress is PHP, but not all PHP is WordPress.
Sé Reed:
[17:21] And that is like the big distinction is any PHP code- I would not know the difference between what is, because that I don’t know.
Jason Tucker:
[17:31] And a lot of developers don’t too, because you end up with the stuff, which you’re probably trying to get to Cosper is that the developers that write, you know, the build stuff, they know how to write in PHP.
They don’t know how to write WordPress flavored PHP to be able to, to actually build a thing.
Like they’ll go and rebuild an entire like navigation thing for like, you know, for like a menu system or something when there’s like a Walker and a, this and that, and like, you know, these things that are already pre-built to kind of make it all work.
Jason Cosper:
[18:01] I know a ton of PHP developers who are like Laravel PHP developers, and then they get into WordPress because they think, oh, here’s where some money is, even though they’re probably making tons of money with Laravel.
But they’re like, Oh, yeah, I can. I know PHP already.
It’s like Jurassic Park. This is Unix. I know Unix. It’s like, this is PHP. I know PHP.
And then they come over.
Sé Reed:
[18:25] No Unix in that one. That’s a bad example. because it worked.
Jason Cosper:
[18:29] They come over and then they realize like, Oh, wait a minute.
The the thing that I’m trying to do here. So I have seen plugins and and themes and other like bits of code that are built for WordPress that it’s it’s kind of the WordPress shim.
And then it calls out to Laravel, and they build it the Laravel way.
And and then, you know, have something that effectively, like, takes what they’re trying to do and like shoehorns that into WordPress.
It’s a little horrifying. It’s valid.
You can absolutely do it.
Sé Reed:
[19:08] I can’t see. But like, how would let’s say, chat GPT spit that out, right?
How would you like because if that code exists, maybe it’s in the maybe it’s in the repo, maybe it’s, know, it’s published somewhere on GitHub, whatever, and it’s read that, and it’s, you know, using that as like, it does try to do best practices.
So if you ask for a WordPress plugin, you know, I think it does try to follow the WordPress documentation, which it’s obviously all read as well. It’s out of date.
It’s read more of the codecs than I have. That’s what I’m confident in.
Jason Cosper:
[19:44] I have asked it to just just to see its its chops and everything else.
Historically, whenever it will manage to come back. But when we had WordCamp Orange County, for several years, I judged the plugin of Palooza and was doing like the code quality and stuff like that.
So I’m familiar with what good WordPress code looks like.
Some might argue, especially on the plugin review team that if they’ve seen my code that I may not necessarily know what good code looks like.
However, they have been very kind to me and allow me to fix things.
But besides the point, I’ve, gone and had chat GPT, like, hey, can you make a WordPress plugin that does this thing?
And sometimes it does it in a way that I wouldn’t have done it.
But I’m like, Oh, yeah, that would work.
Like it would, I can see this for this kind of implementer class of people that we have in WordPress, who may not want to come to someone like me or even, I’m sorry, say like you or whatever and say like, hey, I need a little, I need a solution here.
Sé Reed:
[21:10] I don’t build plugins for people. I would be the person doing that.
So I think there’s two big AI conversations that really affect WordPress.
One is what we’re talking about in terms of generating code, creating little plugins.
I think, so that’s one, and then I’ll get to the other one in a second.
But in terms of the creating plugins, there’s two components of that too.
One is creating micro plugins that are for site-specific issues or places to like hold team customizations or functionality like that.
That could be really useful for, especially if we were able to get like a more up-to-date chatbot, which I think there are some of the WP chat is like going to be is trained off of like the newer docs. So it’s not as old.
[22:01] Like so it’s not ending at 2021. So like I could see like how much easier, like I don’t want to ever spin up my own plugins even just for little things because I then I have to maintain it.
And then when the new version comes out, I have to like read that whole thing and be like, does this, cause any of this and like, you know, do a little difference checker.
I’d be like, am I using any of these functions? And like, you know, So I could really see the value in just popping that in and saying, hey, according to the new docs that are available, does anything in this plugin conflict?
We good? Okay, great. So that would be like a really easy check for more custom bespoke plugins and for me, that would definitely encourage me to do so.
Also, I could be like, hey, take this snippet of code and spin it into a plugin called this, and I could just download it and pop it up instead of even having to write my own, just even just to write the the plug-in.
Jason Tucker:
[22:53] Files, you know, I mean, you could get, you could get like, you know, like code, code, pilot, copilot to go and like refactor the code based on the latest and greatest.
Sé Reed:
[23:03] Yeah, yeah. But those are that aspect.
But there’s also the plugin aspect of people trying to make commercial plugins, where they’re, which is what Mika had been talking about in that post they did for the plugins team, which was that they have already seen a bunch of like code that is a copies, exact copies of plugins that are already in the repo, because the chat’s like, Oh, here, you want to plug in that does this, here’s one, you can have this one that I already know about.
But then those people were submitting it back to the repo as a new plugin.
So there’s that weirdness, right?
That’s a whole people using the code to build plugins to like, in theory, inundate the repo.
And there’s been some chat in post status about, I think, David Bassett, I believe, is compiling a list somewhere, which we’ll find for the show notes, of AI plugins in WordPress.
And he was saying, oh, I think we’ll have probably a hundred by the end of the year. And I was like, a hundred?
[24:07] How about a hundred thousand? Or like, you know, 10,000?
Like, there’s no way we’re just gonna have a hundred. And then like, literally like a day or two later, he commented, he’s like, just kidding.
We already have a hundred. It’s like, I was like, right. Yeah.
So like that’s happening.
Like there’s people are using this tool to create all sorts of plugins, whether they’re for custom, for bespoke, or for submitting to the repo, which free still, right?
But then you have the commercial layer of people who are both so many, there’s so many layers to this, this is wild.
Both in the commercial layer, people who are making plugins that use AI, so like the every alt from master WP that’s about, yeah, automatically writes all your alt text.
I’ve seen a bunch of other ones that like do that sort of thing.
So that’s that’s plugins that use AI. And then there’s also the plugins that are like, going to be tried to sell be sold for premium that are made with AI, not even necessarily having to do with AI, introducing a new layer of competition, because maybe you can make an events calendar kind of clone with way less overhead and sell it for way less, right?
You could like outprice with like a cheaper product.
[25:24] So there’s like, how, like that is so intense.
So when some of those perspectives are like, boom, like, wow, like there’s this opportunity to create new plugins and solve new problems and sell them to clients, innovate on stuff, and then also doom in terms of, are we just going to be completely inundated with, just, we already have so many plugins, right? Is it and not necessarily even just in the plugin repo, just on the market all over.
Jason Tucker:
[25:58] And how many pull requests are going to be AI generated stuff?
Sé Reed:
[26:02] My god, I hadn’t even thought about that.
Jason Tucker:
[26:04] So I just saw auto pop in the chat and he’s gonna be like, Oh, boy.
Sé Reed:
[26:08] Oh, well, auto auto popped in the chat. I AI is definitely well, it’s not terrible at coding for the level that I’m I’m at, but it’s definitely, you know, it’s not, it doesn’t, it already has plenty of errors for like basic level stuff. Like I have to fix.
Jason Cosper:
[26:25] You’re not going to write the next WooCommerce with AI.
Sé Reed:
[26:29] No, but here is something that it will impact the WordPress community on.
Another way that it will impact the WordPress community is in things like meeting notes or community summaries or getting work done, pull requests, small fixes, that type of stuff.
In terms of even on the marketing team, which I’m co-rep of this year, I’ve used it for different things.
We’re creating this prompts. This is a plug for a campaign that we’re going to do a show on, but I’ll give you a plug now. We’re doing a campaign called WB20 for blogs to blogs.
We’re writing prompts for 20 days of prompts for the WordPress community.
Contributor popped into the doc last night and was like, where should I put my AI-generated prompts?
But I’m like, well, here’s fine. He’s like, I want to keep them separate.
And you know, they’re not, they don’t necessarily fit the perfect thing.
But like the point is, is that like.
So I made a separate section for it, right? And it’s like, here’s the AI stuff, and here’s the human-generated one.
So this is already impacting the community.
It’s already impacting the way that that operates.
[27:42] There’s nothing to stop someone from making a pull request, doing some AI stuff with it, testing it, and then putting that in. And not that they would claim it as their own.
That doesn’t matter to me. But there’s no way to know.
So it will definitely impact us.
Jason Cosper:
[28:02] That’s what all that this is going to make Hacktober 2023 just living hell for maintainers.
Jason Tucker:
[28:09] Just auto GPT the whole thing.
Sé Reed:
[28:10] That’s what’s going to happen. Trying to review, like, this is the thing, like maybe there should now be a button.
Like, was this generated by AI just so that you could be like, okay, I’m going to look at the human ones first or, or, or just so that the, the literal amount, because you could generate so many different solutions, right?
Jason Cosper:
[28:27] Like, I, but that relies on the people not bullshitting you with that.
Jason Tucker:
[28:33] Right. Yeah.
Jason Cosper:
[28:34] Oh, yeah. Yeah. It’s, yeah. This is an AI wink.
Jason Tucker:
[28:38] Yeah.
Sé Reed:
[28:39] There’s no way to tell just like with the code and the license.
There’s literally no way to tell other than, you know, maybe it sounds a little stuffy and fluffy, but like, especially if you’re dealing with a community that’s very much English as a a second language. I don’t know.
Like, you know, you’ve learned off of TV and marketing. Why wouldn’t you also sound like that? You know what I mean? Like there’s no way to, and also there can be tools.
Another thing that I think Master WP released is a business English tool, which like allows you to like convert any text into like kind of standard business English.
Or yeah, to like, you know, just make it easier to, in theory, communicate in business, but wow, the the flattening of human experience is just like imminent.
Jason Cosper:
[29:27] I am not terribly, if you couldn’t tell, I’m not terribly bullish on AI with the whole you know, garbage in garbage out and kind of, I kind of have a little bit of a jaundiced eye, like looking at a lot of this stuff and the things that it generates.
But human made And Tucker, I know we’re right near the end of the show, but if you can pull this up real quick.
Sé Reed:
[29:54] The irony of this is like the funniest thing. We laughed about it a lot on our little chat. And we’ll laugh about it in Discord with you.
Jason Tucker:
[30:01] Oh, yes, yes, yes, yes, yes. Yes. OK.
Sé Reed:
[30:03] Yeah. I’ll hold up real fast. Irony is overwhelming.
Are you doing it? I want to say, we’re all like, now we’re waiting to see the thing. There we go. Yeah.
Jason Cosper:
[30:15] So, yeah, if you scroll down a little bit to the demo video.
Sé Reed:
[30:18] Wait, wait, wait, before you scroll down, I just, anyone who’s looking at the screen right now and seeing, well, not right now, but, you know, see the header, which says human made and the logo, and then it’s this generative content WordPress AI.
Jason Cosper:
[30:30] Right. But the demo that they have and we’ll describe it here. yeah, that’s the video.
It’s Artemis, the new trip to the moon, and it they are entering in a block a prompt to like, hey, give me a list of all of the attempts to go to the moon.
And then they type in, hey, turn that into a table.
Sé Reed:
[30:59] Yeah, I was like, is that a table? Yeah.
Jason Cosper:
[31:03] And then it said, add another column that says what what the budget is for this.
It’s okay, perfect. Order that by year in ascending.
Sé Reed:
[31:13] We need to not read a video on the screen.
Jason Cosper:
[31:18] What is your- I’m doing it for the folks listening to the audio, but the amount of, and I’m sure that there are some things that are being done here to kind of lessen the time that it takes to generate all this, but the things that they are able to do with this of just collect this data for me, this is something that like you would have to engage a person to like go, and this isn’t like having a bunch of creative, you know, content, like filler content and stuff like that.
The demo and it will make sure that- coming from human made.
Sé Reed:
[32:00] It just boggles my mind.
Jason Cosper:
[32:03] I love those guys. In the show notes, it is super wild, and it is one of these things where I’m like, oh, yeah, having just a little kind of assistant that sits off at the side, and then you’re like, yeah, hey.
Sé Reed:
[32:18] You mean like Clippy? This is like our Clippy millennial Clippy dreams is what AI is. That’s why we’re all taking to it so much, because Microsoft has been training us for this moment where it’s like, yeah, I always wanted Clippy to talk to me like chat GPT.
I genuinely wish that they would it would like instead of being it should have like re released Clippy and then millennials would have just been like all hail Clippy.
I mean, kind of rad, to be honest, you don’t know what I’m saying about Clippy, then we’ll put a link in the show notes.
Microsoft Word in the early days, right?
Jason Tucker:
[32:53] This was pretty badass. Like I’m, I’m actually impressed. I’m I’m really impressed with what that will come up with.
Sé Reed:
[33:00] The thing about all AI is you have to know what you want. and that is the biggest blocker to developing.
A website anyway, the tools are not actually that hard.
Asking it to do that is roughly the same thing as especially right now Gutenberg clicking three columns and adding pictures, right? Like, if you of course, if you integrate that, it can be a lot faster, because you’d be like, look through open verse and put in, you know, three stock photos for this, whatever.
But you still have to ask it for what you want, right?
But it pulls up the data. That’s, that’s the interesting part is that actually, that data and talking about copyrighted, like, there may be weird rules on software copyright, but what about the rules on like written copyright?
Because it doesn’t say anything about where that language came from. Right?
It’s like, is that just like straight Wikipedia? You know, so it’s common sentence.
So that’s, that’s the problem of AI.
Jason Tucker:
[33:55] Not only how is the AI code being made, but what the stuff that it’s generating, you know, there’s that whole conversation about the artists and Jason Tucker, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, he, Jason Tucker, he, he, he, he, he, he, he, he, he, he, he, he, he, That was a Google search that somebody did.
Jason Cosper:
[34:08] And now we have switched positions and my work here is done. Jason hit the out.
Jason Tucker:
[34:12] Oh, look at you. Here’s the outro. Someone do the outro. Here we go.
Jason Cosper:
[34:25] Well, both say and Jason are on mute. So I’m going to go ahead and encourage you to like and subscribe to WP on YouTube, Apple Podcasts, Google Podcasts, Stitcher, Spotify, if you’re into that sort of thing, and subscribe to it. I’ve been Dicky, he’s the best. Bye. For say.
Sé Reed:
[34:44] Now I’m broken too? And we’re…
Likes, Bookmarks, and Reposts
5 responses to “EP452 – Doom or Boom: AI in WordPress”
-
… liked this!
-
… reposted this!
-
… commented on this.
-
… liked this!
-
… liked this!
Leave a Reply