Main

• Home
• Post Atom Feed
• Comment Atom Feed
• Blogger Profile
• Contact
• About

Latest

• Recursive Tabs to Spaces Converter
• Converting tabs to spaces
• Learning about the FHS /srv
• Semantic MediaWiki
• South African Embassy
• Green Card Lottery 2008
• Zend Framework Google Login Example
• Custom Muti Widgets
• Google Social Graph API and PHP 5.2
• Google AJAX Feed API Muti Example

Archives

• June 2004
• July 2004
• August 2004
• September 2004
• October 2004
• November 2004
• December 2004
• January 2005
• February 2005
• March 2005
• April 2005
• May 2005
• June 2005
• July 2005
• August 2005
• September 2005
• October 2005
• November 2005
• December 2005
• January 2006
• February 2006
• March 2006
• April 2006
• May 2006
• June 2006
• July 2006
• August 2006
• September 2006
• November 2006
• December 2006
• January 2007
• February 2007
• March 2007
• April 2007
• May 2007
• June 2007
• July 2007
• August 2007
• September 2007
• October 2007
• November 2007
• December 2007
• January 2008
• February 2008
• March 2008
• April 2008
• May 2008
• June 2008
• July 2008
• August 2008
• September 2008
• October 2008
• November 2008
• December 2008
• January 2009

Zoopy Development Suggestions

From a developers perspective, I had a couple of ideas for new features that could be included inside of Zoopy. Since Zoopy has become a major source of local media material it is very handy to be able to integrate it with other social applications and content rich websites. Hopefully others in the local tech community will be able to join me and think of more cool ideas for them. Please comment or blog and leave a link in the comments to your post if you have anything to add.

One of the few things that unfortunately disappoint me a bit about Zoopy is that they do not currently have much of an API. I understand why as there are probably not too many African developers at the moment that would make good use of it, so investing a lot of expensive development resources into developing an extensive API is probably not all too practical. However, there are certain little things they can do that will definitely make a big difference, or well, at least to me.

The first thing I would really like to see is oEmbed support. oEmbed is a relatively new standard but already implemented in various places. Flickr has support and there are also many other popular ones supported at oohEmbed such as Youtube, etc. For those that don’t know about oEmbed yet, it is a standard for exposing metadata and even code for embedded content.

The second thing is most definitely Gnip support. In other words, Zoopy must become a Gnip publisher. Gnip makes it very easy to keep track of new posts, usually to online social services, in real time. For example, you can subscribe to my Twitter feed via Gnip and every time I post something to Twitter Gnip will make an HTTP POST to your server informing your web app of my latest post. Something similar would be really cool in Zoopy as every time I post something new Gnip could help notify the various syndicators out there in order to spread my content more widely more quickly and efficiently.

Well, that was my main two things. If you have any suggestions, as I said, please add!

Posted by Charl van Niekerk on Friday, October 24, 2008
Get TimesURL