Andrew Nacin shared publicly last night the fact that Rdio support will be in 3.6 via oEmbed:
@Rdio oEmbed support will come in WordPress 3.6. See http://core.trac.wordpress.org/ticket/24242 . The issue is @Spotify does not offer an oEmbed endpoint.
He also directly pinged Spotify with a request:
@spotify, if you add an http://oembed.com endpoint (mad easy) for the Play Button, it’ll be included in the next @WordPress release.
I’m not a user of either Rdio or Spotify (am I missing out on something or what?) but from the responses it would seem that many of you are.
Music is such a large part of our lives that without it I literally wouldn’t function and none of these blog posts would ever get finished. This is a true story if there was ever one to tell!
So adding more musical embeds sharing what you’re listening to makes complete sense. It’s hard to imagine that at one point music on the internet wasn’t even available and if you did you “embedded” it in the background of your site to auto-load much to your visitor’s annoyance.
I remember that on one of the very first blogs that I ever had (Xanga) I managed to do this and at first people were astounded, sharing comments about how “awesome” it was to have this music greet them when they first encountered the site. It was pleasant background and “mood” music, or so I thought.
After the first week, though, people were asking me to take it down lest they blow their brains out. I didn’t oblige immediately because I didn’t see the problem but eventually I came around to the fact that this looping musical file wasn’t necessarily everyone’s cup-o-tea.
And yes, you can even ask the staff here at WP Daily – my musical tastes aren’t exactly “cool” but I’m ok with that! And I’m glad to see more support for all types of music through WordPress.
Are you a Rdio user or Spotify user? What other music systems and technology would you like to see in WordPress natively?
Join the conversation