Updates to YouTube-Podcaster-Feed-Creator

This weekend I rolled out some updates to the YouTube-Podcaster-Feed-Creator.

This script, which I use to get a true RSS feed with enclosures for video versions of podcasts who use Google Hangouts or otherwise post their videos to youtube, had been broken by Google’s deprecation of their old API as they rolled out v3.

In the old (v2) API, you could just make calls out to an http endpoint like this:


And you’d get back a response you could parse to see all the uploads under that username, out of which you could construct an RSS feed.

For the new API, you need to first generate a server key. Create a project in the Google Developers Console, enable the YouTube Data API v3, and then generate a server key.

For any given podcast, you need to find the relevant Playlist ID. In general, the easiest way is to use the Google API explorer youtube.channels.list, put in contentDetails for “part” and username under “for Username.”

In the results, you’ll see a JSON structure – you’re looking for “uploads” under “Related Playlists” – that playlistId will work with the script to find all videos uploaded by this user.

Configure the script with your API key and the playlist ID, and you get a valid RSS feed with enclosures.

Note: I’ve discovered the feeds produced don’t work with PocketCasts on my iPad – you just get the YouTube Device Support video – but they do work with Downcast.  My guess is they are doing some caching or other server-side stuff that interferes.

What the Drupal Community Can Learn From WordPress: Philosophy Driven Development

(Image courtesy of Maura Teal)

I’ve written now a couple of times about what I think the WordPress community can learn from Drupal, and specifically Dries’ keynotes at DrupalCon, which I always make time to watch.

Now it’s time to talk about some learning in the other direction.

The occasion isn’t Matt Mullenweg’s State of the Word talk from WordCamp San Francisco, though those are always worth watching, nor his recent interview on WP Tavern, though that’s also worth listening to.

Instead it’s a talk by Aaron Jorbin at WordCamp Philly on Why WordPress Works This Way. (The video isn’t yet up on WordPress.tv – I will embed it here when it is).Continue reading →

Managing an Agency Business

Tomorrow night, I’m happy to be a part of the ninth event in the Managing an Agency Business series – this one focused on “managing people, projects and processes to increase day-to-day success as your agency.”

I’ve attended most of the events in the series – I think I missed one or two due to travel – and I’ve always been impressed by the quality and usefulness of the conversation. Hopefully I won’t be the exception to that rule. ;)

My fellow panelists will be Rebecca Marani from Boston Interactive and Adam Gesuero from Image Conscious Studios.

If you’re in the greater Boston area, come say hello. (register here)

Venue: Boston Interactive Headquarters
Address: Schrafft’s Center at 529 Main St, Suite 212 Charlestown, MA 02129
Date/Time: Tuesday June 16th at 6:00pm





What can the WordPress community learn from the State of Drupal (2015)?

Last year I wrote a post about what the WordPress community could learn from the State of Drupal, Dries’ annual address at DrupalCon (aka the Driesnote, carrying a similar importance as Matt’s State of the Word in the WordPress community). It’s time for a 2015 update.

tl,dr; version

What can the WordPress community learn from the state of Drupal?

  • The Drupal Association, which organizes DrupalCon and promotes Drupal adoption via marketing and developer outreach – offers a model for the potential evolution of the WordPress Foundation
  • Outreach is critical. We can’t just speak to the WordPress community but need to reach out to potential users/customers and sell the benefits of the platform in a language they understand
  • A willingness to experiment – with fundraising approaches, with the hiring of paid teams to supplement the open source core project (Mark Boulton design’s work on Drupal 7 for example) – has helped the Drupal community move forward. This doesn’t mean all those experiments would work for WordPress, but we should be open to new approaches
  • The potential for organizational and client attribution on contributions is an interesting idea for rewarding companies who give back – though with caution about unintended consequences in terms of motivation
  • There are benefits to the epochal release cycle from a marketing point of view – differentiating the old platform from the new. I don’t think WordPress should change to a four year re-architected platform cycle, but we should be doing a better job of articulating the more complex platform WordPress is today

The Driesnote

Continue reading →

Is there a single WordPress community, or a single Drupal community?

(Photo credit: Schipulcon 2011 Day 2 Photos under CC Attribution Share-Alike license)

Two recent posts got me thinking about the Drupal community and the WordPress community.

First, Mendel Kurland (whom I’ve been seeing at every WordCamp lately from London to Maine to Minneapolis) wrote on WP Tavern about “A WordPress Veteran’s Take on DrupalCon LA“:

As I flew from DrupalCon Los Angeles, CA to WordCamp Maine, I thought a lot about what the Drupal and WordPress communities could learn from each other. WordPress and Drupal are two community-built platforms and each community is powerful. We stand to learn a lot from each other, because all open source projects matter.

It’s an experience I’ve had many times, having spent much of the last 7-8 years in both communities. (I attended DrupalCon each year from Boston in 2008 through Portland in 2013, and spoke at a number of DrupalCamps throughout the Northeast, while also organizing WordCamp Boston and speaking at WordCamps all over the US).

I used to joke about wearing my WordPress hoodie to DrupalCamps, and my DrupalCamp shirts to WordPress events – but the reality was, in my experience, there was very little overlap in attendees. At Drupal events, people would joke about WordPress as being “fine, for a blog,” implying or sometimes stating outright it wasn’t powerful enough for “real” web needs. At WordPress events, people would joke about Drupal being big and expensive, and fine if you had a team of twelve developers and 6 months or more to throw at a site build.

In reality, the thing which stood out the most to me was how little the members of each community actually knew about the other – as communities or as software projects. (I also spent time in the Sitecore community – where the gap is even greater. At open source events it is common to hear “no one really uses .NET anymore” but at .NET events it is common to hear “businesses don’t really use open source.” Both, of course, are demonstrably false).

The second recent post that spurred me to write was when Dries Buytaert covered the acquisition of WooCommerce by Automattic, concluding:

To me, this further accentuates the division of the CMS market with WordPress dominating the small business segment and Drupal further solidifying its position with larger organizations with more complex requirements. I’m looking forward to seeing what the next few years will bring for the open source commerce world, and I’d love to hear your opinion in the comments.

In some ways Dries’ take on the acquisition actually mirrors my own. The acquisition of Woo by Automattic will improve the ability of WordPress as a platform (and at some point one assumes WordPress.com as a service) to compete with Squarespace, Wix, and Shopify at the level needed by consumers, prosumers, and small businesses. (I also agree with Brian’s coverage at PostStatus – ultimately some of the WordPress.com VIP customers will want ecommerce).

On the other hand, though, I can’t help but see Dries’ post as a not-so-veiled message I’ve been hearing for years in the Drupal community: WordPress is for small businesses, Drupal is for enterprises.
Continue reading →