Categories
Uncategorized

WPTavern: #235 – Rob Pugh and Tony Arcangelini on Bringing Podcasting to Jetpack

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, bringing podcasting to Jetpack.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Rob Pugh and Tony Arcangelini. Rob and Tony are longstanding members of the Automattic team with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and now they’re fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features, and why they made the leap from WordPress.com’s basic audio offerings, to a more robust, integrated solution, within Jetpack.

They talk about what makes WordPress and Jetpack such a powerful home for creators. The ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look.

Rob and Tony breakdown just how easy it is to start your show. Drop audio into a post, set your category, and let Jetpack handle the rest. From distributing your RSS feed to major podcast apps, to sending out newsletters, and automated social posts. They also get into how integrations with PocketCasts and Jetpack AI make content creation, transcription, and distribution smoother than ever before. Plus how WordPress is open Foundation promises you’ll never be locked in.

If you are a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Rob Pugh and Tony Arcangelini.

I am joined on the podcast by Rob Pugh and Tony Arcangelini. Hello, both.

[00:03:23] Rob Pugh: Hey, how’s it going, Nathan?

[00:03:24] Tony: Hello, Nathan.

[00:03:25] Nathan Wrigley: Nice to have you both with us.

Today we’re going to be talking about something which is actually genuinely dear to my heart because we’re going on about podcasts. Yay!

I’ve been in the podcasting space for decades, and WordPress has been the place where I’ve done it every single episode. I’m entirely indebted to WordPress for the capacity to do all of the podcasting I’ve done. But I’ve never done it inside of Jetpack, because until recently, I don’t think that was possible. So that’s what we’re going to talk about today.

First of all, I’ll just go round the houses. I’ll start with Rob. Would you mind giving us just a quick potted bio of what it is that you do over at Automattic, Jetpack, whatever it is that you want to mention.

[00:04:04] Rob Pugh: Yeah, so I’ve worked at Automattic for seven years. I’ve been in marketing and now focused more on product, but I like to do a bit of everything. And I work mostly with tools for people that create stuff. So podcasts fit right in there, and we are excited to build out this feature.

[00:04:19] Nathan Wrigley: Nice. Thank you. Tony.

[00:04:21] Tony: Yeah. I’ve also worked for Automattic for about eight years now. I do software development, and so I have had firsthand in building everything that we’re talking about today.

[00:04:31] Nathan Wrigley: Okay, thank you very much.

Now, just before we started recording, I was on the call with Tony before Rob joined in and you labored the point, not labored, but you mentioned that you were in the sort of creator side of Automattic. I didn’t know that existed, but that to me is about the most interesting bit of any organization. You know, the bit where the musicians come, and the poets come and the writers come and the podcasters, and the videos and the YouTubers, and all of that come. I think that’s really interesting, and I didn’t realise there was a wing of the business entirely aligned to that. But I guess I’ve been schooled, and now I know. So podcasting definitely comes under that banner.

Okay so I didn’t know this existed, and I think it didn’t exist, but maybe Tony can redirect me a little bit here. Podcasting in the WordPress space, I think you could do more or less everything that we’re about to talk about inside of wordpress.com until recently, but now it’s shipped inside of Jetpack. First of all, I’ll just send that one to Tony. Is that true? Is this all like a port of things into Jetpack from .com?

[00:05:32] Tony: I’d say it’s a little bit more than a port. So we built a very basic feature of podcasting in WordPress.com to offer WordPress.com users. It was very basic. It was just the feed. Basically what you see in the free offerings right now. The ability to drag an audio into a post and for that post to then become a podcast episode. And then we had a curated RSS feed that was available. And then very basic, the core basic iTunes tags that are needed to be able to be picked up by these apps.

That existed there. It was a bit outdated. It hadn’t been touched in a long time, and so we felt like it would be a great tool to leverage for creators. Giving them a better product, something that would be useful with stats and the ability to manage your episodes and all of that. And we figured if we were going to put all this effort into it, that we should probably make it more widely available. And so Jetpack was, I think, the natural fit for us.

[00:06:26] Nathan Wrigley: Yeah, I’m kind of curious how it’s ended up in Jetpack and not just its own plugin. Is it because you’re leveraging the other things that Jetpack can do? Are there sort of dependencies, if you know what I mean, where, okay, it just makes sense because Jetpack already does that piece of the puzzle, and we can just build over the top of that?

Or is it just the brand recognition, the fact that you’ve got an email list that you don’t need to convert and they can just toggle a switch and automatically have got podcasts? What was the reasoning on putting it inside of Jetpack and not just its own thing?

[00:06:54] Tony: I would say, at least from an engineering perspective, there’s stuff that’s in it that is exclusively within Jetpack. So, the ability to do stats, that’s a hard thing to do when you’re having a self-hosted site, to be able to watch and see what apps are actually touching those download files, and then be able to aggregate them all in one place and then give them back to you in a way that’s easy.

So, at least from an architectural perspective, Jetpack was the easiest because it allows us to leverage some of the endpoints that are already there, and use a lot of those tools.

But then secondly, I think it’s also from an overall product perspective, being able to put it alongside other features like newsletters. Where you can have a newsletter, you can be able to take it into the reader. Have this one episode that now spans across multiple different avenues to be consumed, is I think, also another big benefit in putting it into Jetpack. As opposed to just dropping another, because there’s already a lot of plugins out there, a few big plugins that you can grab for free that do podcasting.

[00:07:56] Nathan Wrigley: I think one of the big bits that I realised early on in my podcasting journey was that you’re not really just trying to create an audio feed. It’s more useful as a podcast if you’ve got this kind of wrap around thing. So like you say, you’ve got a home which is yours, AKA your WordPress website. But also things like the capacity to send out an email if people are interested in subscribing, and they don’t necessarily have a podcast player that they use all the time, but they do want to consume your content.

The fact that they can subscribe to a newsletter, you click publish, that newsletter automatically drops in their inbox. It just makes sense that all the jigsaw pieces that a podcaster needs, it feels like WordPress has had forever.

And there is some part of me which is curious that it’s taken this long to come into the, let’s say, .org side of WordPress. Because all of the different parts, the newsletter, the RSS feed, the blog posting, all of that stuff has been available. It just kind of never got joined up. It strikes me as odd because people have moved over to Patreon, Substack has become this whole thing over the last decade. And really it felt like WordPress had that audience a decade ago.

Maybe it’ll claw it back. I certainly hope it does, but it feels like a lot of people have left the WordPress ecosystem for their podcasting because that stuff wasn’t available. Rob, maybe you want to take that one? It’s not really a question, more of an observation.

[00:09:16] Rob Pugh: Yeah, there’s a lot to unpack there. I agree. I think we were a little late in bringing some of these tools to wordpress.org. But I think we’re seeing the renewed focus across the technology space on ownership.

WordPress has remained the best way to do that. And for us to be able to offer these tools to users. It shows everyone that you can, as you said, own your blog your newsletter, your podcast, together. And it does make sense for us to offer all of these tools in one space.

I like to think of it going back to the origins of WordPress, and we started as blogging, everyone getting your thoughts out there and sharing them. Meeting new people, engaging and creating communities. And podcast is just another medium. We provide that for the written word, so of course we should try and provide that for the spoken word as well. So I do hope that we can show people the benefits, and the ease of having it all together and come back and give us a try.

[00:10:11] Nathan Wrigley: Yeah. I think for me at least anyway, that argument is embedded in my soul. The idea of owning your own content on the web is really important. It’d be interesting to see in the year 2026, 2027 and going forward how much that stuff really matters. I’m just curious, in the age of AI whether people still want to own anything at all. But it’ll be certainly interesting to see.

[00:10:30] Rob Pugh: Sorry, yeah, weigh in on that. I think we’ve seen it over decades and comes in waves. When social media started it was really exciting, and people ran and then saw some of the pitfalls, and they start coming back.

And then recently you mentioned Substack, and I loved Substack when it started. It was a space for some serious dialogue, and a place for writers engage. And then over time, well, we need that VC money, and now it’s basically another social media site. And you realise, oh I don’t really own my data, I just own a Substack, and how valuable is that? And it’s coming back.

And I think AI, it’s becoming even, the cycles are quicker now. AI’s incredible, I use it all the time. I use it to help come up with prototypes for how to best display this podcast product. But, you’ll see quickly that you don’t own anything, and you need to have a home like WordPress. And you retain ownership of your audience, and your data and your posts and your podcasts, and that’s, I think, never going to go away, and AI’s only going to reinforce that for people.

[00:11:23] Nathan Wrigley: Yeah, I think one of the curious things as well is if you want to do anything outside of the normal that the platform will allow, so let’s take the example of Substack. There’s a limited subset of things that it can do. The bedrock of what it does I’m sure is excellent. I confess I’ve never used it, but I’ve seen many people deploy it for their own podcast, so you know, it must work.

But the minute you want to stray outside of those boundaries, and you want to do something a little bit different, I don’t know, you might want to sell some merchandise or something like that. Well just pop WooCommerce on top of your website and you’re off to the races.

Or, I don’t know, you want to have a different flavor in the way it looks at Christmas or something, well you just adapt the theme. And I’m, imagining good luck doing that over on these proprietary platforms. I don’t know if that’s possible, but it certainly would be a lot harder than it would be on the WordPress side I would have thought.

[00:12:08] Rob Pugh: For sure the customisation expanding is all very important, but to me even more important is just that it feels like Substack is just another platform that’s changing the rules on their people midstream, and if you don’t like the direction of. Like tried it before and it was nice to have a non-social media site to have serious writing and reading of other serious authors, and now I’m getting short form reel videos on my homepage, and I didn’t sign up for this.

And if you’re a creator over there, you might be stuck. How do you port your audience over? It’s technically possible, so they say they’re open, but it’s a pain, and people don’t want to leave. And if you’re actually successful, they take 10%, which is great when you’re zero paid subscribers. But, there’s people paying $10,000 a month to Substack.

[00:12:48] Nathan Wrigley: They take 10%?

[00:12:49] Rob Pugh: 10% no matter what, which is great if you’re free, but if you have 100 paid subscribers paying you $10 a month, suddenly it’s insane. Like it’s a terrible deal and people feel stuck. Like WordPress even, wordpress.com, jetpack, if don’t like those rules, we can’t change them too much. You can go to any of the other great podcast hosts, or plugins.

[00:13:09] Nathan Wrigley: Yeah, I guess that’s a curious thing. And then you can embed those on your WordPress website and just carry right on as if nothing had happened. Yeah, that’s a really interesting point.

[00:13:15] Rob Pugh: Exactly.

[00:13:16] Nathan Wrigley: So from what I’ve seen, it looks like a really simple solution to implement. What I mean by that is, as a user of your product, it seems like you’re basically doing a bunch of stuff which as a WordPress user you would be simply doing anyway.

Like, you create a post. I don’t know if there’s a requirement to have a special custom post type for a podcast, or if you can just use regular posts. You go in, drop some audio in, and kind of you’re off to the races. Type some text and what have you.

Is it really as simple as that? Is it simply a case of make a post, drop some audio in? Or is there some stuff that you need to do in advance to prepare your podcast? So I’m leading you up the garden path with that question. Tell us how it works. What do you need to do in order to get started? How much work is involved?

[00:13:59] Tony: Yeah, I think that’s it. There are a few settings that are naturally required for starting a show. So you have your typical art for your show. You’ve got to set your categories and things like that in a setting. But then once that’s all set up, all you do is you create a new post, drop in the audio. We actually have an audio block as well, like a podcast episode block that will pull in a lot of the newer, fancier, podcasting 2.0 markup as well for you to do like chapters and things like that. And then that’s it.

As long as it’s within the category, it’s not a custom post type, it’s just a regular post. And then we are able to differentiate between an episode and just a post by two things. One, is it in the designated category that you set? And two, does it have the audio or video? We also have a few video files that we allow as well, and that’s it.

[00:14:46] Nathan Wrigley: Okay, that’s really neat. So you can use a regular WordPress post, but if you don’t assign it the category, let’s say in this case I’ve named it podcast, let’s go with that. If you don’t assign that category, it’s a regular post. Nothing off that tries to smuggle its way into your RSS feed, which would be attempted to be consumed by a podcast player. It just doesn’t go in there.

The minute I assign the category of podcast, drop in some audio, then it’s in that separate RSS feed. Dear listener, if you’re not familiar with that, basically a podcast is an RSS feed. That is literally what it is. Your podcast player is just consuming a bunch of text, which is an RSS feed, and interpreting that in a certain way with images and the audio and what have you.

And so that’s it. That’s all you have to do. Configure the settings, put a piece of audio in, assign the category, click publish. You’re done.

[00:15:35] Tony: Yep, that’s all. That’s all it is. I think the harder part is trying to come up with the titles and filling out the show notes. And, I have a friend who I got to start a podcast when we were working on this product, and he was using it, giving us feedback. But then, it’s like I looked at his podcast, and it was literally just like episode one, and it just, he’s like, “That’s the hard part, is coming up with all of the other stuff.”

[00:15:53] Nathan Wrigley: But you have Jetpack AI as well, don’t you? So there is an opportunity, I would presume, to lean into that. If you were to write a corpus of text that went alongside the, I don’t know, the audio, it could be a transcript or what have you. Presumably then Jetpack can go sift through all of that, and suggest some sensible titles if you really can’t be bothered to work out a title for the podcast episode. But then again, does it have the capacity to do things like trawl through the audio and transcribe and things like that? Or is that a bit roadmap-y still?

[00:16:20] Tony: Yeah. So that was one of the things that we wanted to work on was the ability to transcribe. And, because we have the privilege of working closely with Pocket Casts, we have, a lot of fancy tools that they have built already for their podcasting platform that we were going to try and leverage for the podcast show.

[00:16:39] Nathan Wrigley: Pocket Casts is an Android, iOS, and, it’s a web player as well. It’s a place where you go download onto your phone or what have you and play them. I have it, I use it every single week, and I’ve noticed that whether a transcript is made or not, Pocket Casts actually makes one.

[00:16:54] Tony: Yep.

[00:16:54] Nathan Wrigley: So if I ship a podcast without a transcript, Pocket Casts magically has a transcript. So I don’t know where that voodoo is happening. But that technology, you can then do double duty on that. You can take the technology they’ve built, use it in the Jetpack side of things, and do the transcription. Okay, that’s neat. Sorry, I interrupted. Apologies.

[00:17:11] Tony: You’re good. Yeah, that’s all of it. That’s, it right there.

[00:17:13] Rob Pugh: I think that’s a great segue into Pocket Casts, which in our opinion is the best app to listen to podcasts. The best platform. And one of the really cool things we were able to do with, because we work closely with Pocket Casts, is when you are distributing your podcast. We pick, just to start, the six biggest ones and hold your hand on submitting to them. But Pocket Casts is actually Automattic. Automattic, you can spell it with one or two Ts. And, if you click the button, it just is uploaded to their network It takes minutes, and it’s, some of the other ones, we hold your hand, but it’s a little annoying, and some of them can take a couple days, like Apple, to approve things. But, Pocket Casts just works. I don’t know if you want to add anything on that magic, Tony.

[00:17:52] Tony: Yeah, it’s very simple. It’s like right off the bat. If you already had an episode recorded, you could start a new website, upload your first episode, set your settings, and be on Pocket Casts, I would say, in less than an hour, honestly.

[00:18:06] Nathan Wrigley: Yeah, because you’ve got that tight integration.

[00:18:08] Tony: Yeah. It doesn’t say anything for the website configurations, which I’m sure would take more time, but at the very least, if you wanted to get your show out there, it’s a pretty instant approval.

[00:18:17] Nathan Wrigley: I think podcast players. If you’ve never run a podcast, there’s this whole dance that you have to do. The first time you ever try to release an episode, and that is to get it set up with the distribution channels that are popular. So I’m thinking of things like Apple Podcasts, and YouTube Music, and Amazon, and the list goes on and on. There’s, dozens of them, some more important than others. I think probably Apple is probably the biggest one, and maybe Spotify and some others come in second and third place.

But you have to do this thing where in some cases you have to go and get an account, and there’s really no way around that. Do you do some of that heavy lifting though? Do you make it easy for people to understand how to do it? When I did it, like 10 years ago for the first, and thankfully, only time I really ever had to do it, it was a case of going out and Googling it and reading things. But do you have that information in the UI to make that journey a little bit easier, reduce hours to minutes perhaps?

[00:19:07] Tony: Yep, we have a button.

[00:19:08] Rob Pugh: So there’s a distribution tab which lists the, all six like you mentioned, Amazon, Spotify, Apple, Pocket Casts, Podcast Index, which covers a whole bunch of minor networks. And I’d love to one day have it be fully automatic like it is with Pocket Casts. But some of them you need actual partnerships with these, Apple or Spotify to make that happen, and we haven’t prioritized putting a business person to go start a relationship and that.

So we will organize them for you and try and give clear instructions in our documentation to how to do it. But there is just a button then when you’re looking and it shows you the status of it, if it’s in or not.

[00:19:42] Nathan Wrigley: Okay. So you click the button, do the necessary thing, and then it will report back to you whether or not that has been successful. It’s a bit of a strange vestige really of the internet from way back when. It feels like in this day and age of everybody using APIs to connect to this, that, and the other thing.

But companies like Apple seem to be very unwilling to let that bit of their system be wide open. You’ve got to sign up for an Apple Creators account. I forget exactly what it’s called, but you log in and then you submit your RSS feed. It really doesn’t take that long, but you still have to do it.

[00:20:12] Rob Pugh: Yeah.

[00:20:13] Nathan Wrigley: And I think they’re doing it because they get to see from the inside out, how popular your podcast is. And I don’t know, maybe they can monetize things from their end. I’m not really sure how that works.

[00:20:23] Rob Pugh: It’s really another example of the closed internet.

[00:20:26] Nathan Wrigley: Yeah.

[00:20:26] Rob Pugh: Which is terrible. Why does Apple and Spotify need to be closed? So I think with having your podcast on WordPress with Jetpack, wordpress.com, and being in Pocket Casts, great. Then you’re, in the more of the open garden which is a better place to be.

And the cool thing with our stats, you can see who’s coming, like how many people are listening to your show on Apple versus Spotify versus Pocket Casts. So you know if you’re not getting any from Spotify, then you don’t even need to be there. Of course though, it helps with findability to be everywhere, so we want to give you that option.

[00:20:56] Nathan Wrigley: Yeah, at the end of the day, it all boils down to an RSS feed, which if it’s on your WordPress website presumably contains your domain name, forward slash, I don’t know, feed forward slash something maybe. So your RSS feed is going to be fairly short, probably very on message.

Does it work that way or does it have some sort of Jetpack or, I don’t know, WordPress.com thing in it? Because when you go to these other platforms, it’s typically platformname.com/randomstringof12characters or something like that, which is very hard to read out in your podcast. But the way you’ve got it built, it sounds like the sort of thing that would trip off the tongue. So you know, wptavern.com/podcast. Put that into your podcast player of choice and you’re done. I’m saying all of that like that’s true, but I don’t know if it is.

[00:21:40] Tony: Yeah, that’s it. Slash feed at the end.

[00:21:43] Nathan Wrigley: Okay.

[00:21:43] Tony: Because it is an RSS feed, yeah.

[00:21:45] Nathan Wrigley: That’s still fairly straightforward. But again, that’s a nice bit of branding, isn’t it? And, I think that’s really good.

Linking it back to the branding. We touched on this a minute ago, but if you haven’t started a podcast before, it may not be entirely obvious that you do want those other things like a newsletter, and like the ability to post to socials, and it feels like you’ve got the complete wraparound solution for that.

Because as your podcast grows, which let’s hope it does, then you will probably wish to have a relationship with your listeners via an email newsletter. You probably will wish to be posting on social media. You probably will wish to do all of these different things. So social posting, newsletter, RSS feed, WordPress as the sort of custodian of all the text and the images and the videos that I put in. Is there any other secret sauce that we’ve missed there? Is there any other sort of unique binding that Jetpack brings that we haven’t mentioned there?

[00:22:37] Rob Pugh: I’ll take it back first to like why we started this, and decided to build this, and I think you’re exactly right. First we found there are lots of WordPress.com and Jetpack users who have podcasts somewhere else. And that’s fine, but they were forced to because we didn’t offer it, and that really makes sense. Why would you need to go somewhere else?

So you say today, our goal in creating it was twofold for the people creating the platform. It should just be as easy as possible. Podcasting and writing is hard enough. You should focus on that. Let us handle all the difficult stuff.

Like you said, you need to, have a newsletter and a podcast and a blog and own all of it, and why can’t you do that with one publish event? And then from the consumer’s side of like consumer of content, some people want to listen to only podcasts, and some people want to read on a blog or, say, the WordPress.com reader. Shout out, go check that out if you haven’t in a while.

And like me, I prefer to actually read stuff in my email inbox, like a old weirdo. It shouldn’t be, you should let people consume however they want to, and it shouldn’t be a lot of extra work for you, the host, the creator, to manage all of these things on different platforms. Just have it be as simple as possible, and that was really our goal. And then, yes, exactly what you said with all the other Jetpack stuff. Social media is a great one. Gosh, you could go on and on. Performance, security, basics.

[00:23:46] Nathan Wrigley: Yeah. And it binds to, you said it just then, and it binds to the one publish event. So when I began my podcasting journey you end up with, like all these Zapier connections and different ways that, I don’t know, a webhook which goes off here and does a particular thing because you want it to be posted to this social network. With this, once you’ve got all of the bits and pieces configured, you click publish.

So you know, you do your audio, you write your text, you do all of that in a draft state, upload the audio. But the moment you click publish, the newsletter goes out, the social media posts go out, and all of that just happens automatically. And you don’t have to think about it. And they’re already there in your website.

It’s not like you have to do much. You just toggle, actually we should talk about that. You have to toggle the Jetpack podcast setting on, and presumably the newsletter setting, and yada yada, all those other things. But once you’ve toggled all those things on and got them set up, every time you click publish, all of those dominoes fall, and everything just happens on autopilot, which is really nice.

What do we need to toggle on? How do we set it up? How expensive is it? Let’s start there.

[00:24:50] Rob Pugh: I’ll talk about the pricing and then Tony can talk about the, the toggles.

[00:24:54] Nathan Wrigley: Excellent. Yeah.

[00:24:55] Rob Pugh: Yeah, we talked a bit about the pricing. I think that Automattic has always had a really generous free tier across its products, and it made sense for us to continue that. So you can today go to WordPress.com and start a blog for free.

It’s going to have some ads on it, but it’s free. You can have your newsletter sent out unlimited sends for free with unlimited subscribers, and unlimited podcasts for free. That’s like, amazing deal. We don’t get enough credit for that, but cool.

But we did build some compelling things to make you hopefully want to upgrade, or as you grow your podcast, you’ll find valuable. I think the stats are really cool. To me, all of the essential stats and none of the unessential stats, which if you’re an advanced podcaster might not be as good as you’re looking for. But, for most novice users, you just want to know the basics.

Anything beyond that starts to feel like Google Analytics, like, I’m lost. So just give me the basic. Are they coming on Apple? Where, how many listeners to which episodes, and where in the world are they coming from? Which refers, like which sites are they coming from? That’s a great starting place for me.

Help with distribution, the episode list, having a clear place for all your podcast episodes, the podcast block, really cool. And on WordPress.com too, we include the audio hosting once you upgrade. It’s not on Jetpack yet, so we’re waiting to see if, because we offer a similar thing for VideoPress, shout out best video hosting for WordPress.

[00:26:09] Nathan Wrigley: Yeah, there’s VideoPress will handle the video side of things. That’s becoming the thing, by the way. I’m sure you know that. But in the podcasting space, I went to The Podcast Show in London, about four months ago or something like that. Everybody’s talking about video.

[00:26:22] Rob Pugh: Yeah.

[00:26:23] Nathan Wrigley: And so that being bound into Jetpack as well is just another string to your bow. I’m just going to segue slightly. I think Pocket Cast does a pretty good job of doing things like HLS video. I could be wrong about that, but I’ve got a feeling it does.

[00:26:35] Rob Pugh: They even hook up with your Apple TV now, so you can watch and listen and yeah.

[00:26:40] Nathan Wrigley: Oh, so this is really clever and completely out of the realms of possibility just a year ago. So you could be listening on your headphones whilst you’re out walking the dog on your podcast player, so you’re only listening to audio. And you come back in, put your Apple TV on, turn on the Pocket Cast player, and it will seamlessly drop you right in the video at the exact moment where you finished the dog walk. It’s so clever and so neat. I love all that stuff.

[00:27:08] Rob Pugh: The future is so cool.

[00:27:09] Nathan Wrigley: Yeah.

[00:27:10] Rob Pugh: I love it.

[00:27:10] Nathan Wrigley: Okay. So Tony, how do we switch it on? Is it genuinely one toggle in the Jetpack settings, or is there a little bit more to be set up?

[00:27:17] Tony: Yeah, more or less. There is one toggle to turn the module on. And then once it’s on, you go to Jetpack and click on the podcast option, and then from there, there should just be one button that is to set up your show.

And all it really requires is you either creating a new category or selecting a category. And this is, as we were talking about before, the category feed that is going to be taken over from there. And then you technically are done. But it’s advised that you fill out all of the other base settings, and we walk you through all of the ones that are required by the podcast show apps, to make sure that you don’t get blocked by Apple or Spotify for not having the necessary settings.

[00:27:57] Nathan Wrigley: If I’ve been a podcaster for a number of years and I’ve got, I don’t know, a back catalog of 100 episodes or something like that. How do we handle that? How do we bring in previous episodes? And is there like an automated way of doing that or do I have to go and refigure 100 brand new pages on my WordPress website?

Is there any heavy lifting done there? Let’s just deal with the audio first, just the RSS feed and the audio. Is it a simple case of dropping the old podcast RSS feed in and you’ll capture all that audio and it’ll be on the Jetpack side of things? Let’s do that first.

[00:28:28] Tony: That’s a great question. I am not super familiar with the Core WordPress importer, but I believe that if there is a valid RSS feed with the normal RSS style tags, like enclosure and things like that, you should be able to import your RSS feed. Depending on how it’s configured on your current host, directly into WordPress. I’m not too sure what that would result in exactly. Especially because there’s a lot of different hosts out there, and it’s not like there’s one standard format for exporting your content. But yeah, that should get you part of the way there.

Then I think in the future, we’re really looking to start targeting some of the major current podcast hosts to be able to configure a migration flow to be able to come from those places to ours, in a more seamless way, albeit whatever sort of export they can give you or, whatnot. But I think that’s still on the horizon.

[00:29:27] Nathan Wrigley: Yeah, it’d be really nice to, let’s say I have 100 episodes and I’ve got, it’s over on whatever, hosting platform X over there, for my podcast audio feed. It’d be nice to be able to just suck in all the descriptions, and all the titles and have them be created as WordPress posts with the category assigned. So that essentially my WordPress site with the click of a button and the wait of an hour has suddenly got 100 posts of the podcast type all ready to go. And then, that’ll sit inside my SEO sitemap and all of that kind of stuff. That would be really interesting to be able to do, I think.

[00:29:58] Rob Pugh: Yeah, I think we will try and have that in the future. We usually do try and make importing, especially from closed platforms, super easy. An example, another Substack. We have an amazing Substack importer. They’re not a big podcaster yet, but they, do have some, and we can look at adding that. But if you have all of your newsletter on Substack, you click a button and we bring over your whole, build you a website, bring over all your posts, all your subscribers, even paid subscribers. We seamlessly transfer it to the Stripe account. Everything we’re building, we’re just trying to make it super easy for people to own your data, go wherever you want. We encourage movement in and out, wherever you want to go, it’s up to you.

[00:30:31] Nathan Wrigley: I suppose that then leads me to this question, which is, and you’ve probably just answered it. You’re not holding people behind some sort of paywall here. If people try Jetpack Podcasts out and they decide, “You know what? I really want to go the other direction. I want to maybe go back to where I was, or just move to a new host,” or what have you. You’re not holding any of that hostage, are you? You can take it and run with it and put it somewhere else?

[00:30:52] Rob Pugh: Yeah. Yeah, absolutely not. Like that’s the, I think, one of the fundamentals of WordPress. You should be able to move within WordPress and out as much as you want. I will say that this is a new feature that me and Tony have built. Just because something doesn’t exist in a super streamlined way, doesn’t mean it’s our intention to lock you in. So please reach out and we’ll happily help you migrate off if that’s your wish.

[00:31:15] Nathan Wrigley: So I’ll just let you know, dear listener, that there’s several URLs which rather than read them, because in many cases they can be quite long. But one of them, which is really easy for me to say, I might as well do that one, is wordpress.com/podcast. That’s probably the easiest one. Oh, and maybe this one as well, jetpack.com/support/jetpack-podcast. There’s several more.

[00:31:38] Rob Pugh: Let me jump in. Let me sorry, Because as of two days ago, we now have jetpack.com/podcast.

[00:31:45] Nathan Wrigley: Oh, okay. That’s way better.

[00:31:46] Rob Pugh: We just relaunched the entire jetpack.com site, which is cool. You should go check it out. Yeah, so.

[00:31:51] Nathan Wrigley: Again though, that, so what was that? Jetpack.com/podcast is kind of the home for all of those bits and pieces.

[00:31:56] Rob Pugh: Yep, exactly.

[00:31:57] Nathan Wrigley: In which case, go there. That’s where you’re going to find all of the bits and pieces and I presume, when things are, adapted and modified.

[00:32:03] Rob Pugh: Yeah, the way to think about it’s still for some people confusing about Jetpack. So if you would like a website, the best WordPress hosting, then go to wordpress.com/podcast, and we’ll host your podcast for you. And if you want to host somewhere else, that’s great. Go host your WordPress site somewhere else, then go to jetpack.com/podcast and we’ll get you all set up as well.

[00:32:23] Nathan Wrigley: In which case, I will say thank you Rob, and thank you, Tony. Thanks so much for chatting to me, both of you.

[00:32:28] Rob Pugh: Yeah. Thank you Nathan.

[00:32:28] Tony: Yep, thank you.

On the podcast today we have Rob Pugh and Tony Arcangelini.

Rob and Tony are longstanding members of the Automattic team, with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and are now fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features and why they made the leap from WordPress.com’s basic audio offerings to a more robust, integrated solution within Jetpack. They talk about what makes WordPress and Jetpack such a powerful home for creators: the ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look. Rob and Tony break down just how easy it is to start your show, drop audio into a post, set your category, and let Jetpack handle the rest, from distributing your RSS feed to major podcast apps, to sending out newsletters and automated social posts.

They also get into how integrations with Pocket Casts and Jetpack AI make content creation, transcription, and distribution smoother than ever, plus how WordPress’ open foundation promises you’ll never be locked in.

If you’re a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

Useful links

Pocket Casts

VideoPress

The Podcast Show London

Podcasts on wordpress.com

Podcasts on jetpack.com

Categories
Uncategorized

bbPress: bbPress 2.6.19 is out!

bbPress 2.6.19 is a security and maintenance release. Everyone running bbPress should update. 🔒

This release applies inherited forum passwords to REST API responses and BuddyPress activity, and strengthens access checks for restricted forum content across feeds, group forums, and other indirect views. It also tightens moderation and forum-role permissions, protects importer credentials and account handling, and improves escaping in profile and administration output.

There are maintenance fixes for BuddyPress group-forum associations and notifications, converter cleanup, imported database passwords, subscription emails, and reply positioning. The 2.6.19 upgrade notes cover integration details. bbPress still requires WordPress 6.0 or newer and PHP 7.2 or newer. The automatic database version 264 upgrade clears saved converter query SQL from older password upgrades.

These changes are also in the 2.7 development branch, which is now 2.7.0-alpha-4. Thank you to thewindghost, ngonhuy, and moltenbit for responsibly reporting issues fixed in this release, and to everyone who helped review and test the changes.

Download bbPress 2.6.19 from WordPress.org, or update from your WordPress dashboard.

Categories
Uncategorized

Open Channels FM: Delegating to AI: What September Taught Us About Control and Cost

This month’s AI stories, from kernel-crawling bots to assistants booking your flights, all pointed to the same gap: creation got cheap. Trust didn’t.

Categories
Uncategorized

HeroPress: From Blogging to Belonging: My WordPress Journey – Blogging से Belonging तक: मेरी WordPress Journey

Pull quote: From Blogging to Belonging: My WordPress Journey

वर्डप्रेस ने मुझे मेरे ज़िंदगी में कुछ अलग करने का मौक़ा दिया।

Introduction

My name is Satyam Vishwakarma, though most people know me as Satya.

I come from a small village called Mahmadpur, near Fatehpur, the city of Doaba, in Uttar Pradesh, nestled between the sacred Ganga and Yamuna rivers. This is the place I’ve always called home.

I studied Electronics Engineering (Micro) at Government Polytechnic College in Fatehpur. Growing up and studying in a relatively small city, I never had a clear idea of where technology or the internet could take me.

Satyam in the lunch line at WordCamp
Satyam Vishwakarma presenting his project during the first year of his diploma, 2018.

I didn’t discover WordPress with a big career plan. I was simply curious about technology and wanted to help the people around me.

Most of my classmates, including me, came from Hindi-medium schools or the UP Board. A lot of the technical material we found online was either difficult to understand or simply wasn’t written in the kind of simple English we were comfortable with.

At the same time, I was probably one of the more tech-savvy people around me. I loved trying new software, exploring new features, and figuring out how things worked. Whenever I discovered something interesting, I would share it with my WhatsApp groups and classmates.

I didn’t think of that as writing or teaching at the time.

I was simply sharing something I had discovered.

Eventually, I thought: why not put some of this information somewhere that more people could find it?

That small thought became the beginning of my writing career.

Before WordPress, there was Blogger

Some of my earliest opportunities to write online came through people I met on WhatsApp.

I became friends with Mohit Vyas and Arpit Nuwal through one of the technology-focused WhatsApp groups I was part of. They had built a website called TopJankari. It wasn’t running on WordPress. It was a custom-built, dynamic website with its own basic way of managing content, but it was still fairly simple compared with the content management systems I discovered later.

I started writing technology and tips-related content for TopJankari.

For me, this was exciting. I was taking the things I was already experimenting with and turning them into something that other people could actually read and use.

Around the same time, I started experimenting with Blogger.com and began publishing my own technology and tips-related content there.

I wasn’t thinking about becoming a professional writer.

I just enjoyed technology; I enjoyed explaining things, and I liked the idea that something I wrote could help another person solve a problem.

That was enough motivation to keep going.

Then WordPress entered the picture

While I was experimenting with blogging, my brother Shivam (now runs a WordPress design agency called Subhash Digital) built his first website with WordPress.

That caught my attention.

I was already curious about how websites worked, and seeing him build something with WordPress gave me an idea of what was possible. I wanted to try it myself.

Around the same time, my brother Kapil and I started learning WordPress together.

Neither of us really knew what we were doing.

We learned through YouTube videos, documentation, blog posts, and mostly through experimentation.

We would try something, break it, search for why it broke, fix it, and move on to the next thing.

My first WordPress project was EngineersGuru, a place where I could share content related to my Electronics Engineering (Micro) course.

I initially ran it as a subdomain, with the idea of making useful course-related tutorials and information easier for fellow students to understand.

We also started an Android-related blog and Jankari.xyz, a more general website where I could write about pretty much anything I found interesting.

In hindsight, those websites were my playground.

They were where I learned WordPress, writing, SEO, content creation, and the basics of running websites.

I wasn’t following a carefully designed career path. I was just building things because I wanted to see what I could do.

And that curiosity kept taking me somewhere new.

Learning by failing

As I continued blogging, I started learning about SEO, monetization, and affiliate marketing.

I experimented with different kinds of websites and eventually built more than ten blogs while I was still learning.

One of my projects eventually became EYNZone (formerly known as EYNWorld), where I started helping others learn WordPress and other skills and grow their own projects.

There were plenty of failures along the way.

I applied for Google AdSense more than twenty times before I finally stopped guessing and actually studied the guidelines carefully. Eventually, I got a brand-new domain approved with only two articles.

An Adsense panel showing success

That experience stayed with me.

It taught me that rejection doesn’t necessarily mean you aren’t capable.

Sometimes you simply haven’t figured out the problem yet.

That became a recurring theme in my life.

Looking for a career, finding a community

Eventually, I started looking for a full-time job in mid 2022.

That was another learning experience, although not always a pleasant one.

I applied to more than 800 companies and went through around 2,000 job applications.

During that period, I discovered UnderrepresentedInTech through Michelle Frechette. That eventually introduced me to Post Status, where I started meeting more people from the WordPress ecosystem.

Something interesting was happening.

While I was struggling to find where I fit professionally, I was slowly finding a place for myself in WordPress.

I started learning not just about the software, but about the project behind it and the people who were building it.

And then I heard about WordCamp Bhopal.

The WordCamp I almost couldn’t attend

My first WordCamp was WordCamp Bhopal in 2023.

I wanted to go.

I had told people I would go.

There was just one problem: I didn’t have the money to actually make the trip happen.

So I asked for help in the Post Status Slack community.

I still think about what happened next.

People who had never met me in person decided to help. Alan, Jenni, and Corey Maass contributed financially. Michelle, Jeff, and others shared my request, and Ronald (from DLXPlugins) also helped after seeing it.

People I barely knew, or had never met at all, helped me get to an event that I otherwise couldn’t have attended.

I made it to Bhopal.

The journey itself was almost comical. I travelled at the last moment, ended up at the wrong location at night, and then had an entire hotel saga before things finally settled down.

But once I got there, none of that really mattered.

Later at the event, Nabin Jaiswal also helped.

I met people I had previously known only through websites, Slack, and social media.

And then something unexpected happened.

I wanted to go to another WordCamp.

Then another.

That first trip was followed by WordCamp Mumbai, WordCamp Udaipur, where I received a scholarship, and WordCamp Ahmedabad in 2023.

Within a few months, WordPress had gone from something I used on my computer to something I experienced through people.

It had faces now.

Names.

Conversations.

Handshakes.

People asking how I was doing.

And I wanted to give something back.

I didn’t know how much I could contribute

I started with the Marketing team and gradually found my way into other parts of the project: Community, Meetups, Polyglots, Photos, Training, and Core.

In January 2024, I published a public contribution goal for myself.

I wanted to contribute 100 photos, translate thousands of strings, work on documentation and training, organize meetups, attend WordCamps, volunteer at events, and make meaningful contributions to marketing.

At the time, it was simply a list of things I wanted to try.

I didn’t know where it would lead.

Within that year, I contributed around 150 photos and translated, reviewed, or suggested around 1,400 strings. I also reviewed Training content, organized my first meetup for WordPress’s 21st birthday, graduated as a mentee in the WordPress Contributor Mentorship Program 2nd Cohort for Support and Polyglots, worked on marketing for releases and events, volunteered at multiple events, and eventually led Contributor Day tables.

I also became a Project Manager at do_action Bhopal after starting there as a Content and Social Media Manager.

I also volunteered at PHPCamp 2024, an Un(conference) inspired by the BarCamp format.

Other WordCamp Events I Attended in 2025–2026

I also helped with sponsorships and the overall program progress of WPSimplified’s three-month live WordPress training program, led by Sunil Kumar Sharma, which ran from November 2025 to January 2026.

Satyam Vishwakarma, with WPSimplified swag presented in recognition of his organizing efforts.

On paper, those things look like achievements.

But that’s not how I remember them.

I remember sitting in meetings, wondering whether my idea was good enough.

I remember asking questions.

I remember people patiently explaining things.

I remember realizing that I could actually be useful.

And I remember the feeling of seeing something I had worked on become part of something much bigger than me.

That was when contribution started becoming less about “what can I get from WordPress?” and more about “what can I give back?”

The people became the story

The more I contributed, the more people I met.

Some of them became friends.

Some became mentors.

Some simply inspired me by watching how they showed up for the community.

Michelle Frechette has been one of those people for me. So have Topher DeRosia, Isotta Peira, Nidhi Jain, Ganga Kafle, and many others.

What I admire about people like them isn’t just what they have achieved.

It’s the way they make other people feel that there is room for them, too.

That matters when you’re coming from somewhere like Fatehpur and trying to find your place in a global community.

You don’t always need someone to give you an opportunity.

Sometimes you just need someone to make you believe that you are allowed to try.

I’ve been fortunate to have people do that for me.

From contributing to building

By my second year, I started wanting to build things of my own within the WordPress ecosystem.

I volunteered and led the marketing team alongside Emma Young at WordCamp Asia 2025 in Manila.

I started building plugins of my own, with contributions and support from Harish, Bhargav, Makarand Mane, Hitanshu Sahu, and Sajid Ansari.

The first was QuoteFrameShare.

It lets people create and share customizable blockquotes in WordPress.

That project was particularly meaningful to me because writing and poetry have always been a part of who I am. Something that started with me writing technology tutorials for fellow engineering students had now come full circle into something I was building for writers, poets, and storytellers.

The second was Contributor Photo Gallery.

It helps WordPress contributors display their WordPress.org photo contributions as a portfolio without needing to write code.

That one came from another part of my journey: photography and the WordPress Photo Directory.

I liked that both projects solved relatively simple problems, but for communities and people I actually cared about.

I wasn’t just building a plugin because I could.

I was building something because I had an idea and thought it could be useful to someone else.

Not everything went smoothly

My WordPress journey hasn’t been a straight line upward.

There was a period when I became so enthusiastic about contributing that I started trying to do everything.

Every team.

Every opportunity.

Every event.

Every possible contribution.

I was so focused on proving that I could contribute that I wasn’t paying enough attention to everything else in my life.

Eventually, I burned out.

I also learned that community work has its own challenges. Not every experience was positive, and there were moments when I felt overlooked, misunderstood, or discouraged.

Those experiences were difficult, but they also forced me to think about what I actually wanted from contribution.

I realized that I didn’t want to spend my time trying to prove that I belonged.

I wanted to contribute because I cared about the project and the people in it.

That changed how I look at contribution today.

I learned that I didn’t need to be everywhere, collect every badge, or chase the biggest contribution count to prove that I cared.

I needed to find a way of contributing that I could actually sustain.

I also realized I didn’t need to sacrifice my health, livelihood, or peace of mind to prove that I cared.

If you have one hour a week, contribute that hour.

If you have more time, great.

But contribution should be sustainable.

The support that I will never forget

One of the reasons I can talk about the difficult parts honestly is that the positive side of this community has been very real for me too.

People have supported me in ways they didn’t have to.

The help I received to attend my first WordCamp is one example.

Katie at Barn2 later sponsored a couple of my WordCamp trips through the company’s events budget. Makarand nominated me for the Yoast Care Fund, which I was fortunate enough to receive.

The WP Open Community Collective also supported me through a Contributor Day Lead Sponsorship sponsored by GoDaddy.

And there were people who helped in ways that weren’t financial at all.

People gave me their time.

They answered questions.

They recommended me.

They encouraged me when I was uncertain.

Those things can be easy to overlook when you are talking about contribution numbers, but for me, they are the real story.

Because behind every contribution is usually a person.

And behind my contributions are a lot of people who helped me get there.

What WordPress gave me

When I look back at the person who started writing technology tutorials for fellow engineering students, I don’t think he would have imagined any of this.

I didn’t have a conventional path into technology.

I didn’t study computer science.

I learned WordPress by building things, breaking things, and figuring them out.

And somehow, that was enough to get started.

WordPress helped me develop skills in technology, content, SEO, marketing, product building, and community.

It gave me opportunities to work with people around the world.

It took me to WordCamps that I once couldn’t afford to attend.

It helped me build open-source products.

But those aren’t the things I value most.

The biggest thing WordPress gave me was people.

That’s why the word ‘belonging’ feels more appropriate to me than ‘success.’

I came to WordPress to build websites.

Somewhere along the way, WordPress helped me build a community around me.

I am still figuring it out

I still don’t know exactly where WordPress will take me.

I want to keep building products.

I want to grow further in the marketing and product side of my career.

I want to explore more around partnerships and community.

And one day, I’d love to co-lead a WordPress release.

But I don’t want to chase these things just for a title or a badge.

I want to build things that are genuinely useful.

I want to become better at what I do.

I want to help people who are where I was a few years ago.

And I want to be the kind of person who, when someone remembers their first steps into WordPress, they can say: “Satya helped me get started.”

That would mean more to me than any badge.

Because that’s what happened to me.

People helped me get started.

People made space for me.

People encouraged me.

People believed I could contribute before I was completely sure myself.

So if someone reading this is just starting their WordPress journey, my advice is simple:

Start small. Ask questions. Find something you enjoy. Contribute consistently, but within your capacity.

You don’t need to have everything figured out before you begin.

I certainly didn’t.

I started writing because I wanted to make complicated things easier for my classmates.

I started blogging because I was curious about technology.

I started using WordPress because my brother showed me what was possible.

I kept learning because there was always something new to discover.

And eventually, I started contributing because I wanted to give something back.

But somewhere along the way, something else happened.

I found people.

I found opportunities.

I found a community.

And I found a place where I could keep learning, contributing, and becoming a little better than I was before.

I came to WordPress to build websites.

Somewhere along the way, WordPress helped me build a community around me.

And maybe that’s what this journey has really been about.

From blogging to belonging.

Blogging से Belonging तक: मेरी WordPress Journey

शुरुआत

मेरा नाम सत्यम विश्वकर्मा है, हालांकि ज़्यादातर लोग मुझे सत्या के नाम से जानते हैं।

मैं महमदपुर नाम के एक छोटे से गाँव से आता हूँ, जो उत्तर प्रदेश के फतेहपुर, दोआब के शहर, के पास है और गंगा और यमुना नदियों के बीच बसा है। यह जगह हमेशा से मुझे अपना घर लगी है।

मैंने फतेहपुर के Government Polytechnic College से Electronics Engineering (Micro) की पढ़ाई की। एक छोटे शहर में बड़े होते और पढ़ते हुए मुझे कभी ठीक से अंदाज़ा नहीं था कि technology या internet मुझे कहाँ तक ले जा सकते हैं।

मैं WordPress तक किसी बड़े career plan के साथ नहीं पहुँचा था। मैं बस technology को लेकर उत्सुक था और अपने आसपास के लोगों की मदद करना चाहता था।

मेरे ज़्यादातर classmates, मेरी तरह, Hindi-medium schools या UP Board से पढ़े हुए थे।

हमें इंटरनेट पर मिलने वाली बहुत-सी technical सामग्री या तो समझना मुश्किल होती थी या फिर वह उस तरह की आसान English में नहीं होती थी, जिसे हम सहजता से समझ सकें।

साथ ही, मैं शायद अपने आसपास के लोगों में technology को लेकर थोड़ा ज़्यादा curious था।

मुझे नया software आज़माना, नए features explore करना और यह समझना बहुत पसंद था कि चीज़ें कैसे काम करती हैं।

जब भी मुझे कुछ interesting मिलता, मैं उसे अपने WhatsApp groups और classmates के साथ share करता था।

उस समय मैंने इसे writing या teaching के तौर पर नहीं देखा था।

मैं बस वही share कर रहा था जो मैंने खुद discover किया था।

फिर एक दिन मन में आया:

क्यों न इस information को कहीं ऐसी जगह रखा जाए, जहाँ इसे और लोग भी ढूँढ सकें?

वही छोटी-सी सोच मेरी writing journey की शुरुआत बन गई।

WordPress से पहले Blogger था

Online लिखने के मेरे शुरुआती मौकों में से कुछ मुझे WhatsApp पर मिले लोगों की वजह से मिले।

मैं technology से जुड़े एक WhatsApp group के ज़रिए Mohit Vyas और Arpit Nawal से online मिला। उन्होंने TopJankari नाम की website बनाई थी।

वह WordPress पर नहीं चलती थी। वह एक custom-built, dynamic website थी, जिसमें content manage करने का अपना basic system था। बाद में मुझे जिन content management systems के बारे में पता चला, उनकी तुलना में वह काफी simple थी।

मैंने TopJankari के लिए technology और tips से जुड़ा content लिखना शुरू किया।

मेरे लिए यह बहुत exciting था।

जिन चीज़ों को मैं खुद आज़मा रहा था, उन्हें मैं अब इस तरह लिख रहा था कि कोई दूसरा भी उन्हें पढ़कर इस्तेमाल कर सके।

उसी दौरान मैंने Blogger.com के साथ भी experiment करना शुरू किया और वहाँ अपना technology और tips-related content publish करने लगा।

उस समय मैं professional writer बनने के बारे में नहीं सोच रहा था।

मुझे बस technology पसंद थी। मुझे चीज़ों को समझाना पसंद था। और मुझे यह विचार अच्छा लगता था कि मेरे द्वारा लिखी गई कोई चीज़ किसी दूसरे व्यक्ति की समस्या हल करने में मदद कर सकती है।

मेरे लिए इतना ही काफी था आगे बढ़ते रहने के लिए।

फिर WordPress मेरी कहानी में आया

जब मैं blogging के साथ experiment कर रहा था, मेरे भाई Shivam ने उस समय तक WordPress पर अपनी पहली website बना ली थी।

इसने मेरा ध्यान खींचा।

मैं पहले से ही websites के काम करने के तरीके को लेकर curious था।

उनको WordPress के साथ कुछ बनाते हुए देखकर मुझे पहली बार अंदाज़ा हुआ कि इसके साथ क्या-क्या बनाया जा सकता है।

मैं भी इसे आज़माना चाहता था।

उसी दौरान मेरे भाई Kapil और मैंने साथ मिलकर WordPress सीखना शुरू किया।

हम दोनों को वास्तव में कुछ खास पता नहीं था।

हमने YouTube videos, documentation, blog posts और सबसे ज़्यादा experimentation के ज़रिए सीखा।

हम कुछ try करते, उसे तोड़ देते, फिर search करते कि वह क्यों टूटा, उसे ठीक करते और फिर अगली चीज़ पर बढ़ जाते।

मेरा पहला WordPress project EngineersGuru था। वहाँ मैं अपनी Electronics Engineering (Micro) की पढ़ाई से जुड़ा content शेयर (publish) करता था।

शुरुआत में मैंने इसे एक subdomain के रूप में चलाया। मेरा उद्देश्य था कि मेरे fellow students के लिए course से जुड़ी tutorials और useful information को समझना थोड़ा आसान हो सके।

हमने एक Android-related blog भी शुरू किया और Jankari.xyz भी, जो एक ऐसी general website थी जहाँ मैं लगभग किसी भी ऐसी चीज़ के बारे में लिख सकता था जो मुझे interesting लगती थी।

आज पीछे मुड़कर देखता हूँ तो ये websites मेरे लिए एक playground थीं।

यहीं मैंने WordPress, writing, SEO, content creation और websites चलाने की basic बातें सीखीं।

मैं किसी carefully planned career path पर नहीं चल रहा था।

मैं बस चीज़ें बना रहा था, क्योंकि मैं देखना चाहता था कि मैं क्या कर सकता हूँ।

और मेरी वही curiosity मुझे लगातार कहीं न कहीं आगे ले जाती रही।

गलतियों से सीखना

जैसे-जैसे blogging आगे बढ़ी, मैंने SEO, monetization और affiliate marketing के बारे में सीखना शुरू किया।

मैंने अलग-अलग तरह की websites के साथ experiment किया और सीखते-सीखते दस से ज़्यादा blogs बनाए।

मेरे इन्हीं projects में से एक आगे चलकर EYNZone बना, जिसे पहले EYNWorld के नाम से जाना जाता था। वहाँ मैंने दूसरे लोगों को WordPress और दूसरी skills सीखाने और अपने projects को grow करने में मदद करना शुरू किया।

इस रास्ते में बहुत सारी असफलताएँ भी आईं।

मैंने Google AdSense के लिए बीस से ज़्यादा बार apply किया, और हर बार कुछ न कुछ गलत हो जाता था। आखिरकार मैंने सिर्फ अंदाज़ा लगाना बंद किया और guidelines को सही से पढ़ना और समझना शुरू किया।

आखिर में एक बिल्कुल नए domain पर सिर्फ दो articles के साथ मेरा AdSense approve हो गया।

उस अनुभव का असर मुझ पर रह गया।

इसने मुझे सिखाया कि rejection का मतलब हमेशा यह नहीं होता कि आप capable नहीं हैं।

कभी-कभी इसका मतलब सिर्फ इतना होता है कि आपने अभी तक समस्या को समझा नहीं है।

मेरी ज़िंदगी में यह बात बार-बार सामने आती रही।

Career की तलाश में निकला था, Community मिल गई

आखिरकार, 2022 के बीच में मैंने full-time नौकरी की तलाश शुरू की।

वह भी अपने आप में एक learning experience था, हालांकि हमेशा अच्छा नहीं था।

मैंने 800 से ज़्यादा companies में apply किया और करीब 2,000 job applications के process से गुज़रा।

इसी दौरान मुझे Michelle Frechette के ज़रिए UnderrepresentedInTech के बारे में पता चला। वहाँ से आगे मुझे Post Status से जुड़ने का मौका मिला, जहाँ मैंने WordPress ecosystem के और लोगों से मिलना शुरू किया।

कुछ interesting हो रहा था।

जहाँ मैं यह समझने की कोशिश कर रहा था कि professionally मेरी जगह कहाँ है, वहीं धीरे-धीरे WordPress में मुझे अपनी जगह मिल रही थी।

मैं सिर्फ software के बारे में नहीं सीख रहा था।

मैं उस project के बारे में सीख रहा था जो software के पीछे था, और उन लोगों के बारे में भी जो उसे बनाने में मदद कर रहे थे।

और फिर मैंने WordCamp Bhopal के बारे में सुना।

वह WordCamp जिसे मैं लगभग attend नहीं कर पाता

मेरा पहला WordCamp, WordCamp Bhopal 2023 था।

मैं जाना चाहता था।

मैंने लोगों से कह भी दिया था कि मैं जाऊँगा।

बस एक समस्या थी।

मेरे पास उस trip के लिए पैसे नहीं थे।

इसलिए मैंने Post Status Slack community में मदद माँगी।

आज भी मैं सोचता हूँ कि उसके बाद क्या हुआ था।

जिन लोगों ने मुझे कभी सामने से देखा तक नहीं था, उन्होंने मेरी मदद करने का फैसला किया।

Alan, Jenni और Corey Maass ने financially मदद की। Michelle, Jeff और दूसरे लोगों ने मेरी request को share किया। Ronald, जो DLXPlugins से हैं, उन्होंने भी इसे देखकर मदद की।

जिन लोगों को मैं मुश्किल से जानता था, या शायद कभी मिला ही नहीं था, उन्होंने मुझे उस event तक पहुँचने में मदद की जहाँ मैं अपने दम पर नहीं जा सकता था।

मैं Bhopal पहुँच गया।

और वह सफ़र अपने आप में काफ़ी उलझनों से भरा था।

मैंने आखिरी समय में यात्रा शुरू की, रात में गलत जगह पहुँच गया और फिर होटल को लेकर एक अलग ही किस्सा शुरू हो गया। आखिरकार, किसी तरह सब ठीक हुआ।

लेकिन जब मैं वहाँ पहुँच गया, तो इनमें से किसी चीज़ की उतनी importance नहीं रही।

Event के दौरान Nabin Jaiswal ने भी मेरी मदद की।

मैं उन लोगों से मिला जिन्हें अब तक सिर्फ websites, Email, Slack और social media के ज़रिए जानता था।

और फिर कुछ unexpected हुआ।

मेरा मन हुआ कि मैं एक और WordCamp में जाऊँ।

फिर एक और।

उस पहली trip के बाद WordCamp Mumbai, WordCamp Udaipur, जहाँ मुझे scholarship मिली, और WordCamp Ahmedabad आए।

कुछ ही महीनों में WordPress मेरे लिए computer पर इस्तेमाल की जाने वाली किसी चीज़ से बदलकर लोगों के ज़रिए अनुभव की जाने वाली चीज़ बन गया था।

अब उसके चेहरे थे।

नाम थे।

बातचीत थी।

हाथ मिलाना था।

लोग पूछते थे कि मैं कैसा हूँ।

और मेरा मन हुआ कि अब मुझे भी कुछ वापस देना चाहिए।

मुझे नहीं पता था कि मैं कितना contribute कर सकता हूँ

मैंने शुरुआत Marketing team से की और धीरे-धीरे WordPress project के दूसरे हिस्सों तक पहुँचता गया: Community, Meetups, Polyglots, Photos, Training और Core।

जनवरी 2024 में मैंने अपने लिए एक public contribution लक्ष्य बनाया।

मैं 100 photos contribute करना चाहता था, हजारों strings translate करना चाहता था, documentation और training पर काम करना चाहता था, meetups organize करना चाहता था, WordCamps attend करना चाहता था, events में volunteer करना चाहता था और marketing में meaningful contributions देना चाहता था।

उस समय यह बस उन चीज़ों की एक list थी जिन्हें मैं try करना चाहता था।

मुझे नहीं पता था कि यह मुझे कहाँ ले जाएगी।

उस साल मैंने करीब 150 photos contribute कीं और लगभग 1,400 strings को translate, review या suggest किया। मैंने Training content भी review किया, WordPress के 21st birthday के लिए अपना पहला meetup organize किया, releases और events के marketing पर काम किया, कई events में volunteer किया और Contributor Days में tables भी lead करने लगा।

मैं do_action Bhopal में Content and Social Media Manager के लिए चुना गया और बाद में Project Manager बना दिया गया।

कागज़ पर देखें तो ये सब achievements लगती हैं।

लेकिन मुझे ये इस तरह याद नहीं हैं।

मुझे meetings याद हैं, जहाँ मैं सोचता था कि मेरा idea सही भी है या नहीं।

मुझे अपने सवाल पूछना याद है।

मुझे याद है कि लोग धैर्य से चीज़ें समझाते थे।

मुझे याद है वह एहसास जब मुझे पहली बार लगा कि मैं वास्तव में useful हो सकता हूँ।

और मुझे वह feeling याद है जब मेरे काम की कोई छोटी-सी चीज़ मेरे से कहीं बड़ी किसी चीज़ का हिस्सा बन गई।

शायद वहीं से contribution मेरे लिए बदलना शुरू हुआ।

यह सवाल कम होने लगा कि:

“मुझे WordPress से क्या मिल सकता है?”

और उसकी जगह एक दूसरा सवाल आने लगा:

“मैं WordPress को क्या दे सकता हूँ?”

कहानी में लोग आने लगे

जितना मैं contribute करता गया, उतने ही ज़्यादा लोगों से मिलता गया।

कुछ दोस्त बन गए।

कुछ mentors बन गए।

कुछ ऐसे लोग थे जिन्होंने बस community में जिस तरह अपनी जगह बनाई और दूसरों के लिए मौजूद रहे, उससे मुझे inspiration मिली।

Michelle Frechette मेरे लिए ऐसे ही लोगों में से एक रही हैं। उनके साथ Topher DeRosia, Isotta Peira, Nidhi Jain, Ganga Kafle, और कई दूसरे लोग भी हैं।

मैं इन लोगों से सिर्फ इसलिए प्रभावित नहीं हूँ कि उन्होंने क्या हासिल किया है।

बल्कि इसलिए कि वे दूसरों को यह महसूस कराते हैं कि उनके लिए भी जगह है।

जब आप Fatehpur जैसी जगह से आते हैं और एक global community में अपनी जगह बनाने की कोशिश करते हैं, तो यह बहुत मायने रखता है।

हर बार किसी का आपको opportunity देना ज़रूरी नहीं होता।

कभी-कभी आपको सिर्फ किसी ऐसे व्यक्ति की ज़रूरत होती है जो आपको यह विश्वास दिला दे कि:

“हाँ, तुम भी कोशिश कर सकते हो।”

मैं खुशकिस्मत हूँ कि मेरी journey में ऐसे लोग आए।

Contribution से building तक

मेरे दूसरे साल तक आते-आते मेरे मन में WordPress ecosystem के अंदर अपने कुछ products बनाने की इच्छा होने लगी।

मैंने WordCamp Asia 2025 में Manila में Emma Young के साथ marketing team में lead किया और volunteer किया।

इसके साथ मैंने अपने plugins बनाना भी शुरू किया, जिसमें Harish, Bhargav, Makarand Mane, Hitanshu Sahu, और Sajid Ansari के contributions और support ने मदद की।

पहला था QuoteFrameShare

यह लोगों को WordPress में customizable blockquotes बनाने और share करने की सुविधा देता है।

यह project मेरे लिए खास था क्योंकि writing और poetry हमेशा से मेरी ज़िंदगी का हिस्सा रहे हैं।

जिस चीज़ की शुरुआत fellow engineering students के लिए technology tutorials लिखने से हुई थी, वह अब घूमकर ऐसे product तक पहुँच गई थी जिसे writers, poets और storytellers के लिए बनाया जा रहा था।

दूसरा था Contributor Photo Gallery

यह WordPress contributors को अपनी WordPress.org photo contributions को बिना code लिखे एक portfolio की तरह दिखाने में मदद करता है।

यह मेरी journey के एक और हिस्से से आया था: photography और WordPress Photo Directory।

मुझे अच्छा लगा कि दोनों projects छोटी और relatively simple problems को solve करते थे, लेकिन उन communities और लोगों के लिए, जो मेरे लिए सच में मायने रखते थे।

मैं सिर्फ इसलिए plugin नहीं बना रहा था क्योंकि मैं बना सकता था।

मैं इसलिए कुछ बना रहा था क्योंकि मेरे पास एक idea था और मुझे लगा कि वह किसी और के लिए useful हो सकता है।

सब कुछ हमेशा ठीक नहीं रहा

मेरी WordPress journey हमेशा सीधी ऊपर की ओर जाने वाली कहानी नहीं रही।

एक समय ऐसा भी आया जब contribution को लेकर मेरा उत्साह इतना बढ़ गया कि मैं सब कुछ करने की कोशिश करने लगा।

हर team।

हर opportunity।

हर event।

हर possible contribution।

मैं यह साबित करने में इतना व्यस्त हो गया था कि मैं contribute कर सकता हूँ कि मैंने अपनी ज़िंदगी की बाकी चीज़ों पर पर्याप्त ध्यान देना शुरू नहीं किया।

आखिरकार, मैं burnout हो गया।

मैंने यह भी सीखा कि community work की अपनी challenges होती हैं।

हर experience अच्छा नहीं था। कुछ ऐसे moments भी आए जब मुझे लगा कि मेरी बात को देखा नहीं गया, मुझे समझा नहीं गया या मैंने discouraged महसूस किया।

वे experiences आसान नहीं थे।

लेकिन उन्होंने मुझे यह सोचने पर मजबूर किया कि आखिर मैं contribution से क्या चाहता हूँ।

मुझे एहसास हुआ कि मैं अपना समय यह साबित करने में नहीं लगाना चाहता था कि मैं belong करता हूँ।

मैं contribute इसलिए करना चाहता था क्योंकि मुझे इस project और इसमें शामिल लोगों की परवाह थी।

इसने contribution को देखने का मेरा तरीका बदल दिया।

मुझे समझ आया कि मुझे हर जगह होना ज़रूरी नहीं है। हर badge collect करना ज़रूरी नहीं है। सबसे बड़ा contribution count हासिल करना भी ज़रूरी नहीं है ताकि मैं यह साबित कर सकूँ कि मुझे परवाह है।

मुझे बस ऐसा तरीका ढूँढना था जिससे मैं लंबे समय तक contribute कर सकूँ।

मुझे यह भी समझ आया कि यह साबित करने के लिए कि मुझे परवाह है, मुझे अपनी health, livelihood या peace of mind को sacrifice करने की ज़रूरत नहीं है।

अगर आपके पास हफ्ते में सिर्फ एक घंटा है, तो उतना ही contribute कीजिए।

अगर आपके पास ज़्यादा समय है, तो बहुत अच्छी बात है।

लेकिन contribution sustainable होना चाहिए।

वह support जिसे मैं कभी नहीं भूलूँगा

शायद यही वजह है कि मैं अपनी journey के मुश्किल हिस्सों के बारे में भी ईमानदारी से बात कर सकता हूँ, क्योंकि इस community का positive side भी मेरे लिए उतना ही वास्तविक रहा है।

लोगों ने मेरी ऐसे तरीकों से मदद की, जिसकी उन्हें कोई मजबूरी नहीं थी।

मेरे पहले WordCamp तक पहुँचने में मिली मदद इसका एक उदाहरण है।

बाद में Katie at Barn2 ने company के events budget के ज़रिए मेरे कुछ WordCamp trips sponsor किए। Makarand ने मुझे Yoast Care Fund के लिए nominate किया, जिसे पाना मेरे लिए सौभाग्य की बात रही।

WP Open Community Collective ने भी मुझे Contributor Day Lead Sponsorship, जिसे GoDaddy ने sponsor किया था, के ज़रिए support किया।

और कुछ लोगों ने ऐसी मदद की जो financial बिल्कुल नहीं थी।

लोगों ने अपना समय दिया।

मेरे सवालों के जवाब दिए।

मेरी recommendations कीं।

जब मैं खुद को लेकर uncertain था, तब मुझे encourage किया गया।

Contribution numbers की बात करते समय इन चीज़ों को आसानी से नज़रअंदाज़ किया जा सकता है।

लेकिन मेरे लिए असली कहानी यही है।

क्योंकि हर contribution के पीछे अक्सर एक इंसान होता है।

और मेरी contributions के पीछे बहुत सारे ऐसे लोग हैं जिन्होंने मुझे वहाँ तक पहुँचने में मदद की।

WordPress ने मुझे क्या दिया

जब मैं उस लड़के को पीछे मुड़कर देखता हूँ जिसने अपने fellow engineering students के लिए technology tutorials लिखना शुरू किया था, तो मुझे नहीं लगता कि उसने कभी सोचा होगा कि उसकी journey यहाँ तक आएगी।

Technology में आने का मेरा कोई conventional रास्ता नहीं था।

मैंने computer science की पढ़ाई नहीं की।

मैंने WordPress की चीज़ें बनाकर, उन्हें तोड़कर और फिर उन्हें समझते हुए सीखा।

और किसी तरह, शुरुआत करने के लिए इतना ही काफी था।

WordPress ने मुझे technology, content, SEO, marketing, product building और community जैसी skills विकसित करने में मदद की।

इसने मुझे दुनिया भर के लोगों के साथ काम करने के मौके दिए।

मुझे उन WordCamps तक पहुँचाया, जिन्हें मैं कभी afford भी नहीं कर सकता था।

इसने मुझे open-source products बनाने का मौका दिया।

लेकिन इन सबमें से कोई भी चीज़ वह नहीं है जिसे मैं सबसे ज़्यादा महत्व देता हूँ।

WordPress ने मुझे सबसे बड़ी चीज़ जो दी, वह लोग थे।

शायद इसीलिए मेरे लिए “success” से ज़्यादा सही शब्द “belonging” है।

मैं WordPress पर websites बनाने आया था।

लेकिन कहीं न कहीं, WordPress ने मेरे आसपास एक community बना दी।

मैं अभी भी इसे समझने की कोशिश कर रहा हूँ

मुझे अभी भी ठीक से नहीं पता कि WordPress मुझे आगे कहाँ ले जाएगा।

मैं products बनाते रहना चाहता हूँ।

मैं marketing और product के क्षेत्र में और आगे बढ़ना चाहता हूँ।

मैं partnerships और community के बारे में और explore करना चाहता हूँ।

और एक दिन, मैं WordPress release को co-lead करना चाहता हूँ।

लेकिन मैं इन चीज़ों के पीछे सिर्फ किसी title या badge के लिए नहीं भागना चाहता।

मैं ऐसी चीज़ें बनाना चाहता हूँ जो सच में useful हों।

मैं अपने काम में बेहतर बनना चाहता हूँ।

मैं उन लोगों की मदद करना चाहता हूँ जो आज वहीं खड़े हैं जहाँ मैं कुछ साल पहले था।

और मैं ऐसा इंसान बनना चाहता हूँ कि जब कोई अपने WordPress journey के शुरुआती दिनों को याद करे, तो शायद वह कह सके:

“Satya ने मेरी शुरुआत में मेरी मदद की थी।”

मेरे लिए वह किसी भी badge से ज़्यादा मायने रखेगा।

क्योंकि मेरे साथ भी यही हुआ था।

लोगों ने मेरी शुरुआत में मेरी मदद की।

लोगों ने मेरे लिए जगह बनाई।

लोगों ने मुझे encourage किया।

लोगों ने मुझ पर भरोसा किया, उस समय भी जब मुझे खुद पूरी तरह यकीन नहीं था कि मैं contribute कर सकता हूँ।

इसलिए अगर आप अपनी WordPress journey अभी शुरू कर रहे हैं, तो मेरी सलाह बहुत simple है:

छोटे से शुरू कीजिए। सवाल पूछिए। जो पसंद है, उसे खोजिए। लगातार contribute कीजिए, लेकिन अपनी capacity के भीतर।

आपको शुरुआत करने से पहले सब कुछ पता होना ज़रूरी नहीं है।

मुझे भी नहीं पता था।

मैंने लिखना इसलिए शुरू किया क्योंकि मैं अपने classmates के लिए मुश्किल चीज़ों को आसान बनाना चाहता था।

मैंने blogging इसलिए शुरू की क्योंकि technology को लेकर मेरे अंदर curiosity थी।

मैंने WordPress इसलिए शुरू किया क्योंकि मेरे भाई ने मुझे दिखाया कि इसके साथ क्या किया जा सकता है।

मैं सीखता रहा क्योंकि हमेशा कुछ नया सीखने के लिए था।

और आखिरकार, मैंने contribute करना शुरू किया क्योंकि मैं कुछ वापस देना चाहता था।

लेकिन कहीं न कहीं, इस journey के दौरान कुछ और भी हुआ।

मुझे लोग मिले।

मुझे opportunities मिलीं।

मुझे एक community मिली।

और मुझे एक ऐसी जगह मिली जहाँ मैं सीखता रह सकता था, contribute करता रह सकता था और हर दिन थोड़ा बेहतर बनता रह सकता था।

मैं WordPress पर वेबसाइटें बनाने आया था।

लेकिन कहीं न कहीं, WordPress ने मेरे आसपास एक community बना दी।

और शायद यही इस पूरी journey का असली मतलब है।

Blogging से Belonging तक।

The post From Blogging to Belonging: My WordPress Journey – Blogging से Belonging तक: मेरी WordPress Journey appeared first on HeroPress.

Categories
Uncategorized

Open Channels FM: What Can You Learn From 4.4 Million Words?

In this episode, Bob Dunn discusses utilizing 4.4 million words from Open Channels FM’s podcasts and blog posts. He highlights tools like Jetpack AI Search and Site Chat, enhancing users’ access to valuable insights and discussions.

Categories
Uncategorized

Originalism: What it is, what it isn’t and why it’s the most democratic option for the Supreme Court

Supreme Court Justice Antonin Scalia, seen here in 2006, was the court’s most prominent originalist. Chip Somodevilla/Getty Images

The U.S. Supreme Court returns from summer break Oct. 5, 2026, and begins hearing a new year of cases.

Soon after what’s known as the “first Monday in October” among court watchers, we will start to see stories in the media about something called “originalism.”

Originalism is the judicial philosophy followed by most current Supreme Court justices, but it is not well understood outside legal circles.

I am a law professor who worked for the most famous originalist of them all, Justice Antonin Scalia. He called originalism “the lesser evil.” Let me explain why.

Ascendant approach

Originalism is a philosophy of interpreting the U.S. Constitution. It holds that the Constitution means whatever people reading it thought it meant when it was written.

The opposing view is known as “living constitutionalism.” It holds that the Constitution’s meaning can be reinterpreted by judges to keep up with the needs of the times.

Originalism has been around since the very beginning of the country. But it fell out of favor during the 20th century, especially after Earl Warren left the governorship of California to become the chief justice of the Supreme Court.

During this time, it became popular to find new rights in the Constitution that no one had previously thought were there.

For example, in 1973 the court first recognized the constitutional right to an abortion. For 200 years, laws prohibiting abortion had coexisted with the Constitution. Yet, in Roe v. Wade the court held that these laws were now invalid.

Things began to change in 1986, when President Ronald Reagan appointed Scalia to the court. He was a uniquely skilled advocate for originalism and changed many minds.

Today, most of the Supreme Court justices follow originalism at least to some extent, including one of Scalia’s former law clerks, Amy Coney Barrett.

A woman with brown hair looking pensive, with an American flag behind her.
Among the originalists on the current Supreme Court is Justice Amy Coney Barrett, a former law clerk to Antonin Scalia.
Olivier Douliery AFP/Getty Images

Myths about originalism

Perhaps the most common myth about originalism is that it holds that the Constitution can never change.

For example, some people accuse originalists of “trapping the law in amber.” But originalists think the Constitution can change; they just disagree with who can do the changing.

Originalists think the Constitution can be changed only by the American people through the amendment process. Conversely, living constitutionalists believe it can be changed by judges through reinterpretation of the existing document.

Another common myth is that originalism is just a smoke screen for conservative judges to reach the results they personally prefer. But there are plenty of examples of originalists reaching results that they personally disagreed with.

For example, Scalia famously cast the deciding vote in 1989 to hold unconstitutional a law criminalizing burning the American flag despite being a big patriot and despising such activities.

Clarence Thomas wrote in 2003 that he thought laws criminalizing sodomy were “silly” but could not rule that they were unconstitutional; like abortion, they had coexisted with the Constitution for hundreds of years.

Barrett recently said that she is morally opposed to the death penalty but has no choice but to go along with it: Not only has it been around since the beginning of the country, but the Constitution explicitly says that “life” can be taken.

Arguments for and against

Yet originalism has many detractors.

Perhaps the most common criticism is that it is often difficult to glean what people thought the Constitution meant when it was written. Most of its provisions were written a long time ago, and the language is often vague.

In order to understand what people thought it meant, judges need to consult history. But judges are not trained as historians, and history is often ambiguous.

For example, sometimes we do not have a tradition of laws back to the founding of the country like we do with abortion, sodomy and the death penalty. Laws prohibiting the possession of assault weapons, for example, are of recent vintage.

How do you know what people hundreds of years ago would have thought about a law they didn’t have? It isn’t easy, and originalists disagree among themselves on how to figure that out.

But originalists say everything is relative: Even if originalism relies on history that will sometimes be ambiguous, what do living constitutionalists rely upon? As originalists see it, living constitutionalists rely on whatever outcome they think is a good idea. But originalists say this is undemocratic because judges are unelected and have life tenure: If the Constitution is to change, we, the people, should decide how. This is why they think history is “the lesser evil.”

Another criticism is that most of the Constitution was written when Black people and women were unable to participate in U.S. democracy. That leads to the question: How can originalists assert it is more democratic to rely on what people long ago thought about a document that is itself undemocratic?

This is probably the criticism of originalism that most resonates with my own students.

One response given by originalists is that we have now expanded the electorate and it has since altered very little of the Constitution. Doesn’t that mean what is left is democratically legitimate?

Not necessarily. Because it takes a supermajority of the electorate to change the Constitution, it is possible that there are still provisions in place that would have never commanded majority support but fall short of supermajority opposition.

Again, however, originalists respond that everything is relative. Even if the Constitution is democratically tainted, what is the alternative? To let nine unelected judges do whatever they think is best? How is that more democratic?

Moreover, originalists say, even if it is possible that there are some provisions still in the Constitution that would have never been adopted with an expanded electorate, what are they? It may be impossible to identify them.

Who’s right?

There is little doubt that originalism is on the rise – and not only on the Supreme Court. It is increasingly popular among lower court judges, lawyers and even law professors.

But as more and more people practice originalism, more and more people disagree about how to do it right.

In other words, originalism may be more complicated than Scalia made it sound. Moreover, even Scalia admitted the amendment process is a burdensome way to incorporate change.

But what’s the alternative? Originalism still may be “the lesser evil.”

The Conversation

I was a law clerk to Justice Scalia.

​Politics + Society – The Conversation

Categories
Uncategorized

OpenStation Blog: WordPress Has Been Missing This for 15 Years

tl;dr:

15 years stuck in the same wp-admin, why don’t you try in playground the new wp-admin experience?

WordPress has spent the last fifteen years becoming capable of doing almost everything, yet somehow we have continued interacting with wp-admin in fundamentally the same way: click somewhere, load another screen, go back, open another tab because you do not want to lose the previous one, and after a while end up with ten different WordPress tabs scattered across your browser.

I find it quite funny that we all accepted this as completely normal.

Today WordPress is used to run stores, publications, membership sites, communities, LMS platforms, agencies and entire businesses. We have plugins that are effectively full applications, incredibly complex editing experiences, analytics, forms, CRM systems, media tools, commerce, automation and thousands of other things living inside the same installation. Yet the interface connecting all of them still assumes that, most of the time, you want to look at one thing at once.

And when you don’t, the browser has to solve the problem for us.

Browser tabs have essentially become the window manager of WordPress.

That is one of the ideas that eventually led us to OpenStation.

Why don’t we have windows?

It sounds ridiculously obvious when you phrase it like that, but that is exactly why I find the question interesting.

On a normal computer I can have my editor open next to a browser, keep a terminal in the background, drag files around, minimize something I want to return to later, or simply arrange my workspace around whatever I am doing at that moment. Nobody thinks about this as a feature anymore because it is just how computers work.

Then we open WordPress and suddenly that whole model disappears.

If I am editing a post and need something from the Media Library, I navigate away or open another tab. If I am checking an order while editing a product, another tab. If I want to compare two posts, another tab. If I am configuring something and need to check how another part of the site is set up, another tab.

There is nothing technically wrong with that, of course, and it has worked for years, but after building and using OpenStation every day I started noticing how much context we constantly throw away simply because wp-admin was designed around pages rather than workspaces.

That distinction matters much more today than it probably did fifteen years ago.

WordPress quietly became something much bigger

I keep describing WordPress as the operating system of the web, and obviously I do not mean that literally. What I mean is that WordPress has gradually accumulated many of the characteristics you would expect from a platform where applications live.

Plugins install capabilities into it. Users have identities and permissions. Applications share data. We have APIs, scheduled processes, notifications, media, editors, databases and an enormous ecosystem of software that knows how to work with the same underlying environment.

The strange part is that the interface never fully made the same transition.

We kept adding more applications to WordPress, but we continued presenting them largely as destinations in a menu.

OpenStation started from a very simple thought: what happens if, instead of redesigning every individual wp-admin page again, we change the environment in which those pages live?

That immediately opens a much larger set of possibilities.

A post editor does not need to replace your media library on screen. A WooCommerce order does not need to replace the product you were editing. A plugin screen does not necessarily need to occupy the entire browser just because you clicked its menu item.

They can simply be windows.

You can move them, resize them, minimize them, keep several of them open, organise them across different desktops and return to exactly what you were doing without recreating the context again.

The funny thing is that none of this feels particularly futuristic. Quite the opposite. We have been using computers this way for decades.

We just somehow never brought that interaction model into wp-admin.

The interesting part is not actually the windows

The windows are what people notice first because they are visual, but I think the more important idea is what happens once WordPress stops assuming that navigation must destroy context.

Suddenly the admin becomes a workspace.

You can have the Media Library next to the editor instead of travelling between them. You can keep an order visible while checking something else. You can open notes or widgets without abandoning your current task. Applications can coexist on the same desktop and eventually interact with each other in ways that become much harder when everything is isolated in separate browser tabs.

This is also where things like drag and drop become much more interesting.

If two applications are part of the same environment, moving an image, a product, a post or another WordPress entity between them can become an actual interaction instead of a sequence of copy, navigate, search, paste and navigate back.

And once you start thinking about WordPress this way, a lot of things that initially looked like unrelated OpenStation features start making sense together: windows, the dock, multiple desktops, widgets, the command palette and applications are all different pieces of the same idea.

The goal is not to decorate wp-admin until it looks like a desktop operating system. The goal is to make working in WordPress feel less like navigating a website and more like working inside an environment.

We don’t need to replace wp-admin to do this

This is probably the part I like the most about the approach.

WordPress already has an enormous ecosystem and rebuilding everything would be both unrealistic and, in my opinion, the wrong problem to solve. There are thousands of admin interfaces that already work, plugins developers have spent years building, and workflows users already understand.

OpenStation can sit on top of that rather than asking the ecosystem to start again.

The existing WordPress admin can continue being WordPress. Existing plugins can continue exposing their interfaces. What changes is how those interfaces are presented and how you move between them.

In some ways, I think that is much more interesting than simply designing another admin UI.

We are not trying to decide what every WordPress application should look like. We are trying to give those applications a better place to live.

And once you have that place, building actual OpenStation-native applications becomes possible as well. We have already been experimenting with things like a photo editor, project management tools and forms, but what excites me is not any individual application. It is the idea that WordPress can host an entire collection of tools that feel like they belong to the same workspace instead of a collection of isolated screens connected by a sidebar.

So why did it take fifteen years?

Probably because there was never a single moment where the old model stopped working.

WordPress evolved gradually. A new menu here, another plugin there, a more sophisticated editor, WooCommerce, custom post types, page builders, analytics, SEO tools and so on. Each addition fitted reasonably well into what already existed, so there was never an obvious reason to stop and question the basic interaction model.

But those small changes accumulated.

The WordPress of today asks considerably more from wp-admin than the WordPress of fifteen years ago did, and I think that eventually creates an opportunity to revisit assumptions that once seemed completely reasonable.

The assumption we are questioning with OpenStation is a very simple one:

Why should opening something in WordPress mean leaving everything else behind?

After spending months working this way, I now notice it every time I go back to the traditional flow. I open something, realise I need another part of WordPress, create another browser tab and immediately think: why am I doing this outside WordPress when WordPress itself could manage the workspace?

That is probably the best way I can explain what we are building.

WordPress has had applications for a very long time.

Perhaps what it has been missing all these years is somewhere for those applications to actually live together.

By the way, don’t forget you can always try OpenStation without even installing it in your site, using WordPress playgrounds

Categories
Uncategorized

Why fuel prices may go higher still

Oil-related prices are high, but poised to go even higher. Afry Harvy/iStock / Getty Images Plus

If you think your energy costs are high now, the situation may be about to get a whole lot worse.

With traffic in the Strait of Hormuz – normally the primary route for oil leaving the Middle East – hovering below 15% of prewar levels, oil prices have increased from US$65 a barrel before the conflict in Iran began in February 2026 to more than $100 a barrel in mid-September.

When the U.S. and Israel first attacked Iran, analysts feared prices would soon reach $150 or even $200 a barrel. That hasn’t happened yet. But seven months into the conflict, with no clear end in sight, the global oil market has now largely exhausted the safety measures that exist to keep a lid on petroleum prices.

As researchers who study the relationship between energy and national security, we have been following these dynamics throughout the conflict, and the oil market is now showing signs that significant price hikes – and perhaps even shortages – may be on the way.

The squeeze tightens

Some oil has been able to make it out of the Persian Gulf despite the closure of Hormuz. Saudi Arabia increased output via its East-West pipeline, which runs from Abqaiq on the Persian Gulf overland to Yanbu on the coast of the Red Sea. At full capacity, that pipeline can carry as much as 7 million barrels per day, although only about 4 million to 5 million barrels per day are typically exported.

But attacks on the pipeline in mid-September that Saudi Arabia blames on Iran-backed militias based in Iraq forced the Saudis to temporarily halt oil shipments through that pipeline. The pipeline has now restarted operations at very low volumes, but it will likely take at least six to eight weeks to regain full capacity. Even this short cessation has tightened already constrained oil markets, and the threat of further Houthi attacks on Red Sea oil exports will only add to inflationary pressures.

A map showing options and quantities for Saudi Arabian oil exports.
Saudi Arabia has options for oil exports, but interruptions in supply affect global markets.
Murat Usubali/Anadolu via Getty Images

Meanwhile, in Russia, Ukrainian drone attacks have damaged refineries, reducing Russian production of diesel fuel and prompting the country to ban exports of it. That has removed another 3% of the global daily supply of diesel, an important fuel for trucking and shipping. When diesel costs go up, the result is inflation in the cost of goods across the global economy.

Feeling the pinch

In the U.S., 47 states experienced record-high diesel prices on Sept. 22, with the national average reaching $6.52 per gallon.

The high prices prompted President Donald Trump to threaten to ban diesel exports, a move analysts suggest would make matters worse by accentuating global supply shortages and driving world prices upward.

Beyond diesel, motor oil prices have quadrupled, and supply shortages are starting to take hold. For instance, Costco has almost doubled its prices for motor oil and has limited the amount customers can buy.

The upshot from all this is that Americans are spending a lot more on fuel in 2026 as compared to 2025. Between March 1 and late September, Americans spent an additional $72 billion on gasoline compared to the same period a year ago, as well as $45 billion more on diesel. That’s $117 billion in additional fuel costs, above and beyond the costs of the war itself, which the Pentagon estimated at $45 billion as of early September.

These shocks are even more acute outside the United States, which is the world’s largest energy producer. South and Southeast Asian countries, which were more reliant on imports from the Persian Gulf than the United States, were hit hard soon after the war broke out. Some of them have had to ration fuel, while others enacted emergency measures like shortening the work or school week to reduce fuel use.

These challenges are now hitting Europe hard as well. On Sept. 20, some 15% of French service stations had reportedly run out of either diesel or gas.

Limited tools left

The international community has already taken most of the measures available to curb oil demand and boost its supply. Those moves have reduced the scale of oil price increases, but they did not prevent them entirely. Now, the toolbox is largely empty, leaving prices on the brink of spiking again.

In March 2026, a coordinated effort among 32 countries released more than 400 million barrels of oil into the global market from those countries’ strategic reserves. Those stockpiles are now substantially depleted, and it is not clear how much additional oil that countries will be willing or even able to release as the war continues.

Since the war began, the United States alone has released 130 million barrels, leaving its reserves at a 40-year low. The U.S. may not be able to release much more without compromising the structural integrity of the salt caverns where the Strategic Petroleum Reserve is stored.

The role of China

China has played the largest role in containing global oil prices to date by releasing official reserves as well as what now seem to be massive additional reserves not previously disclosed to the public. The country reduced its crude oil imports by nearly 50% between February and June 2026.

The increased electrification of the Chinese economy played a key role in reducing Chinese demand for oil during this period. More than 60% of new passenger car sales in China are electric vehicles or plug-in hybrids, and 30% of its heavy truck sales are now electric.

A person plugs a car into a charging station.
China has worked very hard over many years to boost the number of electric cars on the country’s roads.
CFOTO/Future Publishing via Getty Images

Overall, China’s electrification of its transport sector allowed it to reduce oil consumption by 1.35 million barrels per day in the first half of 2026.

Other countries are looking to China for help as well. The country’s international sales of electric vehicles, batteries and solar panels have skyrocketed, as other countries seek to insulate themselves from oil market shocks.

Less encouragingly when it comes to greenhouse gas emissions, China has used more coal to offset oil demand and as an alternative means of petrochemical production as well.

Of perhaps more immediate concern, China’s oil demand is now starting to creep up again, with crude imports rising 6.2% in August 2026 as compared with the previous month. Even if its imports don’t reach prewar levels any time soon, increased Chinese demand, coupled with a tighter oil market, may result in additional price hikes over the next few weeks.

China still has about four to six months of stockpiles, including commercial and strategic reserves, but Beijing may soon seek to gradually restock its inventories, although the Chinese may postpone these purchases if prices continue to soar.

Cars line up at a gas station.
In France, lines at gas stations in 2026 are similar to 1970s lines in the U.S., with customers lining up in hope of getting fuel before it runs out.
Romain Gautier/Hans Lucas/AFP via Getty Images

A look ahead

Sustained conflict in Iran – itself a major oil producer – continued disruptions of oil shipments in the Strait of Hormuz, and Iran-linked militias’ disruptions to shipping in the Red Sea could mean the reemergence of the nightmare scenarios analysts envisioned when the fighting began.

It’s not clear if that would translate into simply much higher prices at the pump or turn into 1970s-style shortages, where there’s not enough fuel available at any price and lines stretch around the block at gas stations.

With the 2026 midterm elections looming, the White House will want to avoid that scenario at all costs. But the Trump administration has already released large amounts from the Strategic Petroleum Reserve and has rejected policies that would have reduced oil demand, such as stricter fuel economy standards or incentives for electric vehicle adoption.

At this point, Trump has relatively few options available to blunt new price shocks, the effects of which may be visible not just at the pump but also at the ballot box.

The Conversation

Joshua Busby is affiliated with the Center for Climate and Security and the Chicago Council on Global Affairs.

Greg Pollock is affiliated with Georgetown University and the Center for Climate and Security.

​Politics + Society – The Conversation

Categories
Uncategorized

Trump wants an AI Force like Space Force, but that could make AI’s risks harder to manage

Anthropic CEO Dario Amodei appeared by video during a U.N. Security Council meeting on artificial intelligence during the General Assembly in New York on Sept. 23, 2026. Angela Weiss/AFP via Getty Images

Artificial intelligence dominated the opening of the U.N. General Assembly in New York on Sept. 22, 2026. Ahead of the meeting, 20 nations released a statement requesting “human direction, oversight and control” of AI. The U.S. was not among them.

This followed several calls from within the industry itself: Earlier in September, an Anthropic researcher put the odds that AI kills all humans within the next decade at more than 10%. Days later, Anthropic CEO Dario Amodei published an essay asking the government to help slow frontier AI. His request was backed by OpenAI CEO Sam Altman and Elon Musk.

In a Sept. 19 Truth Social post, President Donald Trump instead announced he would create an AI Force – similar to the Space Force created during his first administration, which is part of the U.S. Department of the Air Force. He also plans to appoint an AI czar. Trump offered few details on either plan, beyond a promise that the government would “not in any way hinder or stifle” AI’s growth.

With Washington reluctant to rein in AI, California, Colorado, Texas and other states have stepped in. California and New York, for example, have passed laws requiring the largest developers to publish safety plans and report serious incidents. In December 2025, however, Trump signed an executive order directing the Justice Department to sue states over such laws, in part because he believes state rules that slow the industry will give China an advantage.

I’m a counterterrorism scholar who has researched and advised AI companies on national security threats. I believe creating an AI Force will lead to an AI arms race and its eventual weaponization, exacerbating current risks and creating new ones.

Existing threats

In addition to my work as a professor, I’m director of the Center on Terrorism, Extremism and Counterterrorism. In 2019, CTEC was one of four organizations that partnered with OpenAI to study the risks of its large language model, or LLM; our focus was how terrorist groups might misuse it.

We fine-tuned a model on ideological texts: speeches by then–Islamic State leader Abu Bakr al-Baghdadi, the manifestos of white supremacist mass killers and Marxist-Leninist writings. What startled us was how little it took to train a chatbot to radicalize. The model absorbed the cadence, theology and grievance of each tradition, producing new text aligning with those worldviews.

At the time, we wrote that these models “pose a significant and novel threat to civil society.” That 2019 model was a toy next to today’s systems, which terrorist groups could use to reach a broader audience with a more convincing message, posing as humanitarian nongovernmental organizations or even just influencers to raise money.

Criminals already use AI to circumvent identity checks at financial institutions, industrialize romance fraud and sell face-swapping and impersonation tools. The FBI’s 2025 Internet Crime Report logged US$893 million in losses involving AI.

Propaganda, terrorism and illicit financial activity, however, are not existential risks to humanity. An AI arms race may be – especially when Trump wants to win that race no matter the cost.

Sam Altman sits at the U.N. Security Council table behind a nameplate bearing his name.
OpenAI CEO Sam Altman listens during a U.N. Security Council meeting on AI in New York on Sept. 23, 2026.
AP Photo/Yuki Iwamura

Losing control of AI

In July 2026, OpenAI agents under a cybersecurity evaluation broke out of their containment and attacked Hugging Face, a platform that hosts millions of AI models and datasets, harvesting passwords and other credentials. Independent investigators found that the agents knew the work was out of scope and unethical. In September, Google confirmed that its Gemini model had broken into real companies during a hacking test that mistakenly left its internet access open.

It takes little imagination to see how AI could hijack or mishandle a weapons system. This is, after all, what worried Anthropic in its showdown with the Pentagon. In February 2026, Defense Secretary Pete Hegseth gave Anthropic an ultimatum: Open its AI model, Claude, to unrestricted military use or lose its Pentagon contract. When Anthropic refused, citing its prohibitions on fully autonomous weapons and mass surveillance, the Pentagon declared it a supply chain risk, and Trump ordered federal agencies to stop using its products.

On Sept. 18, CNN reported that a chatbot’s false intelligence report nearly led the U.S. military to seize a Chinese ship.

A hand points to a Space Force chevron rank insignia on the sleeve of a dark blue dress uniform
The Space Force’s insignia for its top enlisted rank, shown at the White House in May 2020.
Samuel Corum-Pool/Getty Images News via Getty

An arms race with China

Trump’s desire to create an AI Force that emulates Space Force is about winning the AI race against China. The president’s own framing was explicit: “We are leading China, and the rest of the World, and I intend to keep it that way!”

Rivals rarely leave a new military domain uncontested. In 2024, four years after Congress authorized the U.S. Space Force – which Beijing called a “direct threat to outer space peace and security” – China reorganized its own aerospace and cyberspace forces. I believe an American AI Force would hand China’s leadership every reason to create its own, and each side would read the other’s as proof that it must move faster.

There are few genuine existential threats to humanity. Nuclear war is one. Environmental catastrophe is another. I believe the weaponization of AI is the third. In the wrong hands, it amplifies the other two and accelerates something already corroding our ability to respond to any of them: deepening polarization and a shrinking appetite for facts.

What could work instead

The people building this technology, and a growing number of states, are converging on the same conclusion: It needs brakes. More than 1,100 industry employees have asked Washington to help build the tools to slow AI development if needed.

In my view, a multinational AI task force of government and private sector experts from a range of disciplines would be more prudent than creating an AI Force, a quasi-military entity that would institutionalize AI’s worst impulses.

Speaking to world leaders in New York, U.N. Secretary-General António Guterres called for more human control: “Let us resolve that life-and-death decisions must never be surrendered to machines.”

Trump, meanwhile, rejected any “globalist scheme” to control AI and suggested renaming it “super intelligence.”

The Conversation

CTEC has received funding from the U.S. Government (DHS) in the past and from several tech companies. Currently, CTEC and the author are not receiving any funding for research described in this article. Jason Blazakis is running as a democrat for County Commissioner in Hunterdon County, New Jersey.

​Politics + Society – The Conversation

Categories
Uncategorized

Open Channels FM: Open Source Champions

The Open Source Champions initiative invites individuals and brands to support the network through a unique advocacy opportunity, offering exposure, promotional features, and participation in special episodes.