does the post_also.module support myspace blogs or can I add it in as an option?

I don't think myspace uses a standard API to blog but I could be wrong. I found a few 3rd party links that might help, but honestly, I can't make this a priority. I did open an account there, so I will eventually/maybe test/play with it.

don't worry about it Millette....just thought I would ask.

As an idea/suggestion. Would it be an idea to create the module with .INC files so people could create their own Post_also.module add-ons. For example.

Where the facebook.inc or lastfm.inc contains the necessary hooks to automatically update their facebook.inc or lastfm.inc journals when they update their Drupal blog.

If that's too complicated or something that's easier to include in the settings page, disregard. Just thought I would mention it.

Great suggestion, I'll keep it in mind :)

In fact, I'm going to hack on it right away.

Millette,
Phil has managed to stir up interest in adding MySpace functionality to your module. Myself and maybe one other developer are interested in helping you make this happen. I have a CVS account, so I can work that way, or at least submit patches from the latest CVS. Are you interested in this? If so, would you mind giving a general overview of your module and how it functions? I'll download the code and start looking at it as well.
I heard that there may have recently been an API released. If not, the code from WordPress posted on this thread may serve as a good reference point.
Thanks,
Jonathan

Here's a link to a possible more recent version of the WordPress code.
http://noumenon.roderickrussell.com/myspace-crossposter-v2-released

Ha, this could be interesting. I'll welcome the help, of course :)

I will try to do a proper release today and set the table so we can add other server types, like MySpace. Thanks!

Thanks for the reply millette. I'll let the other dev know and we'll start posting a strategy in this thread.

Hi all,

Sorry to be late to the thread, I've been emailing directly.

As far as the API goes, I realized that I forgot to include the code in my previous email so I think there was some misunderstanding. At this point, MySpace has indeed opened up their API to developers, one of whom has put together a function to access blog services. As opposed to other 3rd-party API's, this one is done through official MySpace channels and as such should not break with future upates (famous last words, I know).

The code is fairly straightforward:

As you can see, this is designed to add a "post this on myspace" link to existing content. As is, the script obviously needs to have the appropriate drupal variables inserted to suit our purposes. The script requires only one of the variables to be passed (though will accept all) of either title, content, or url. Location refers to a choice of where content should be inserted into the MySpace profile (which for our purposes should always be passed as '1' which is the code for 'blog'.

A couple of obvious limitations:
1) This script requires the user to be logged in to MySpace at the time of submission. As such, we'll have to seek out an additional function to allow for automatic login based on a user-supplied username/password combo.
2) The script automatically directs submissions to a confirmation page. While this is only *slightly* annoying, it does seem to defeat the whole spirit of crossposting (i.e. to minimize the amount of additional steps required to post to multiple sources). While this may be a nice and simple place to start, it may ultimately be a reason to search for an alternate API. On the other hand, we may be able to embed this functionality into a larger macro through which we can dictate that the 'confirm' button is submitted. While this will still technically pass the post through the confirmation, we may be able to make it invisible to the user.

Note, changing the status back to active based on the existence of a MySpace API - are we still interested in pursuing this?

Great work Jay. I think the main thing now is to figure out how we want to integrate this with Post Also. Do we want to do a quick n' dirty start and just throw in a .inc file? Would it be better to try and work towards a crossposting API that anyone will be able to develop their own crosspost add-on module for? (It obviously would from a coding and universality standpoint, but as far as time and effort to get an initial product, it is the lesser option.)

I'm really okay with either approach. I'd like to hear Millette chime on with his opinion. I don't know much about XMLRPC, but I'm not certain the MySpace API conforms to those standards. Either direction we go, we need to figure out what needs to be changed in Post Also to make it happen. This will include menu structure, form additions through nodeapi, and user preference settings. The obvious benefit of developing an API is that we don't have to reinvent all of these things every time a new Social Network site comes out. We just feed crosspost's API the relevant data, and then do the brunt of processing in our modular add-on.

Food for thought. Anyone else have a dish?

Just thought I'd update this thread with the emergence of a new module for the ping.fm service.

http://drupal.org/project/pingfm

It cross posts to multiple applications, like myspace, livejournal and others. ALthough it requires signing up to the ping.fm service to do that.

Would be great if we could have a native Drupal solution to do the same...