Interesting project Jon, and great to have comments!!
One other solution to consider is : haloscan - http://www.haloscan.com/
They provide comments and trackback features you can add to any blog/journal/site whatever .
I used this some time ago on my OPML blog courtesy of Mr Winer (the blogs didn’t have comments then).
Check it out it may be a good candidate.
P.S> Ive been having my own comment spam isues recently at Folknology, real nightmare.
> One other solution to consider is : haloscan
I did try HaloScan, and for me it didn’t cut the mustard on either of my criteria: interactive administration and programmatic integration.
Comment by Jon Udell — September 25, 2006 @ 9:05 pm
What other programmatic tie-ins to WordPress beyond the comment feeds would you like?
> What other programmatic tie-ins to WordPress beyond the comment
> feeds would you like?
Hi Matt,
Well, as mentioned, I’d like to be able to control the URI namespace (i.e., specify my own post slugs). And I’d like to be able to read a log of manual actions (e.g., deleted posts) in order to know what to re-synch. But those are just small details.
I think you’re really asking: “Which pieces of WP are service-like in nature, and might be decoupled from WP and used in other contexts?”
Answer: I dunno. Can you think of others?
I’ll take a look at setting the post slug through XML-RPC, that’s something we’ve talked about before. Comments are removed from the feed when you delete one, so if you can detect that you should be good on the deletion side. (I think.)
BTW, we have no problem with you freeloading off the comments here.
In theory you wouldn’t even need to point people here, you could just post to the comments form directly.
I’m feeling really dense at the moment, but what benefit does this architecture provide over just having comments on your main blog? I’m sure it’s got a very compelling value, it’s just that it is not occurring to me what that is yet.
> what benefit does this architecture provide over just having
> comments on your main blog?
Decoupling, and therefore choice. I’ll probably transition off Radio one of these days. For me, now, it’s mostly just an engine for squirting text through a template and uploading the result. But I’d like to unbundle the features of a blog publishing system, because one may give me better namespace control and search, while another handles comments in a way more to my liking.
A service-oriented approach, in other words.
- Jon
Comment by Jon Udell — September 27, 2006 @ 2:22 pm
Good luck. Sounds like a good idea.
Comment by Tonetheman — September 25, 2006 @ 8:14 pm
Interesting project Jon, and great to have comments!!
One other solution to consider is : haloscan - http://www.haloscan.com/
They provide comments and trackback features you can add to any blog/journal/site whatever .
I used this some time ago on my OPML blog courtesy of Mr Winer (the blogs didn’t have comments then).
Check it out it may be a good candidate.
P.S> Ive been having my own comment spam isues recently at Folknology, real nightmare.
regards
Al
Comment by Al — September 25, 2006 @ 8:20 pm
> One other solution to consider is : haloscan
I did try HaloScan, and for me it didn’t cut the mustard on either of my criteria: interactive administration and programmatic integration.
Comment by Jon Udell — September 25, 2006 @ 9:05 pm
What other programmatic tie-ins to WordPress beyond the comment feeds would you like?
Comment by Matt — September 26, 2006 @ 1:14 am
> What other programmatic tie-ins to WordPress beyond the comment
> feeds would you like?
Hi Matt,
Well, as mentioned, I’d like to be able to control the URI namespace (i.e., specify my own post slugs). And I’d like to be able to read a log of manual actions (e.g., deleted posts) in order to know what to re-synch. But those are just small details.
I think you’re really asking: “Which pieces of WP are service-like in nature, and might be decoupled from WP and used in other contexts?”
Answer: I dunno. Can you think of others?
Comment by Jon Udell — September 26, 2006 @ 1:53 am
I’ll take a look at setting the post slug through XML-RPC, that’s something we’ve talked about before. Comments are removed from the feed when you delete one, so if you can detect that you should be good on the deletion side. (I think.)
BTW, we have no problem with you freeloading off the comments here.
In theory you wouldn’t even need to point people here, you could just post to the comments form directly.
Comment by Matt — September 26, 2006 @ 5:15 am
On the part of getting the titles of the Radio blog as stub blog postings on wordpress with the appropriate slug:
http://laughingmeme.org/archives/002203.html has written this WordPress hack
http://laughingmeme.org/code/wp-rss-aggregate.php.txt
you could modify and have it generate the appropriate posting slug from the data in your radio blog feed.
Or you could have a look at this plugin:
http://projects.radgeek.com/feedwordpress/
Comment by Pascal Van Hecke — September 26, 2006 @ 9:36 pm
I’m feeling really dense at the moment, but what benefit does this architecture provide over just having comments on your main blog? I’m sure it’s got a very compelling value, it’s just that it is not occurring to me what that is yet.
Comment by Mike Schinkel — September 27, 2006 @ 11:37 am
ooh! comments, wonderful.
Comment by Hugh — September 27, 2006 @ 1:07 pm
> what benefit does this architecture provide over just having
> comments on your main blog?
Decoupling, and therefore choice. I’ll probably transition off Radio one of these days. For me, now, it’s mostly just an engine for squirting text through a template and uploading the result. But I’d like to unbundle the features of a blog publishing system, because one may give me better namespace control and search, while another handles comments in a way more to my liking.
A service-oriented approach, in other words.
- Jon
Comment by Jon Udell — September 27, 2006 @ 2:22 pm
Okay, I can see that, thanks for clarifying.
Comment by Mike Schinkel — September 29, 2006 @ 7:44 pm