Yeah, I just saw that this morning, that blogger now uses, if I understand correctly, some distinct Google API. Perhaps it is the same as Atom? LJ, IJ, DW, and DJ can work with Atom, too, no? I think maybe Wordpress will too, but need to look into that. I know that IJ, DJ, LJ, DW AND WP all work with xml-rpc. Best if I don't have to write three different ways to post, but two isn't too bad, one would simplify the whole thing. Heck, I could write one post process and manage where posts are going by setting the relevant variables. Hate to say it, but, at the moment, I have 4 distinct post processes written into this program. Not the most efficient way of doing that. I should pare that down....easy enough. just change the buttons from [command dwpost] [command ljpost], etc., to [post (lj)], [post (dw)], etc. and have one proc proc post (serv) { where $serv is the relevant server/site), or something. Dunno why I didn't just do that...I'm always going the log way around the barn...
I'm wondering what it would take to communicate with Facebook, too. I considering incorporating my denter/tweeter into the same app...if I could add google buzz and facebook, maybe even myspace, the user could have a whole social networking dashboard in one application. Writing something like that in php might be useful, really...a single page with forms for tweet/denting/buzzing/facebook status, & crossposting to multiple blogs. I should learn php. But, in the meantime, I'm either going to do that with Tcl, using what I have here, or in Python. I haven't succeeded in tweeting/denting with tcl's http post method, oddly, while I have with python's urllib. All my blog posting code is using tcl with http post, though. haven't tried that with the py urllib. I just think it would be convenient to have ONE APP TO RULE THEM ALL on the social networking scene. I'm such a geek...
no subject
LJ, IJ, DW, and DJ can work with Atom, too, no? I think maybe Wordpress will too, but need to look into that.
I know that IJ, DJ, LJ, DW AND WP all work with xml-rpc.
Best if I don't have to write three different ways to post, but two isn't too bad, one would simplify the whole thing.
Heck, I could write one post process and manage where posts are going by setting the relevant variables.
Hate to say it, but, at the moment, I have 4 distinct post processes written into this program.
Not the most efficient way of doing that.
I should pare that down....easy enough.
just change the buttons from [command dwpost] [command ljpost], etc., to
[post (lj)], [post (dw)], etc.
and have one proc
proc post (serv) { where $serv is the relevant server/site), or something.
Dunno why I didn't just do that...I'm always going the log way around the barn...
I'm wondering what it would take to communicate with Facebook, too.
I considering incorporating my denter/tweeter into the same app...if I could add google buzz and facebook, maybe even myspace, the user could have a whole social networking dashboard in one application.
Writing something like that in php might be useful, really...a single page with forms for tweet/denting/buzzing/facebook status, & crossposting to multiple blogs.
I should learn php.
But, in the meantime, I'm either going to do that with Tcl, using what I have here, or in Python.
I haven't succeeded in tweeting/denting with tcl's http post method, oddly, while I have with python's urllib.
All my blog posting code is using tcl with http post, though.
haven't tried that with the py urllib.
I just think it would be convenient to have ONE APP TO RULE THEM ALL on the social networking scene.
I'm such a geek...
:)
./tony