Your Ad Here

Radio 8

I’ve been playing with Radio 8 and so far I like it. The news aggregator part of it is better than it was in the past. With previous versions, I seemed to lose news on occasion, but with 8, things appear to be fine.

Radio is now more focused on weblogging than it was before. A Radio license includes hosting space for your blog, and the blogging tools are now more sophisticated. But here’s my problem with the Radio way of blogging. I have to blog from this machine. I want to blog to my own server from my laptop, my desktop, and my office and I can’t easily do that with Radio’s desktop-based system.

Scoble points out that he hates a centralized service for publishing. He wants to have everything local and publish to the server. Personally, I want a Web service for my blog. I want to have a Web interface that I can use from anywhere to edit and publish my stories. I also want a more feature-rich editor that I can use whether I’m online or offline. The editor should be something I install on the machines I use the most, and I should be able to seamlessly publish from any of them without worrying that the other machines will be out of sync. If the data is centrally stored then there’s no synchronization needed.

I use Blogger to manage this blog. The data is all stored on Blogger’s servers and then published by FTP to my servers. And I use blogBuddy as a desktop client for much of my editing.

What I would really like to do is use Radio as my desktop client and publish to my site through Blogger’s XML-RPC interface. There’s a simple example of how to connect Radio to Blogger, but it doesn’t use the Radio browser interface, which is the reason I want to use Radio in the first place.

Radio is based on Frontier’s powerful scripting language. You can write macros to make Radio do many things. So what I would like to do is wire the Radio blog editing interface to Blogger over XML-RPC. It shouldn’t be that hard except for one thing. Where’s the developer documentation? I could worm though all the code that builds the Radio interface and figure it out, but it would still be nice to have some docs so that I don’t have to. Dave, are you listening?

Update: It appears that Dave is listening. I’ve already seen those tutorials, but they don’t really get into managing the existing Radio content management system. I’ve been digging into the scripts taht power Radio and I have a few ideas, but I’d still like to see Userland document the thing. After all they are trying to encourage people to develop things for Radio.


Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Lijit Search

Best Of

Recently Read

Get More

Subscribe | Archives

Recently

Sprout Test (May 7)
A test post for Sprout widgets.
Product Leadership (May 3)
An anthology of product leadership writing.
Fighting Monster patent claims (Apr 16)
The patent bully picked on the wrong little guy.
Peavy's pine tar (Apr 6)
Jake Peavy's cheating
Bush and Morgan on inner city baseball (Mar 30)
Morgan and Bush discuss the role of baseball in the inner cities.
Not a fork (Mar 27)
We have no intention of forking Drupal. That would be nuts. So what are we doing then?
Eating our dogfood in the sausage factory (Mar 26)
Recursive development for the new Drupal powered community platform.

Subscribe to this site's feed.

Elsewhere

Feed Crier
Get alerted by IM when your favorite web sites and feeds are updated.
SacStarts
The Sacramento technology startup community.
Pinewood Freak
Pinewood Derby tips and tricks
Del.icio.us
My tagstream at del.icio.us.
Waddlespot
My son's Club Penguin community. News, blogs, tips, and tricks.

Contact

Adam Kalsey

Mobile: 916.600.2497

Email: adam AT kalsey.com

AIM or Skype: akalsey

Resume

PGP Key

©1999-2008 Adam Kalsey.
Content management by Movable Type.