||[Dec. 5th, 2003|02:10 am]
LiveJournal Client Discussions
Is there any way to simultaneously post to multiple journals, or is the only way to auto-crosspost to loop through a list of journals and send a postevent for each one consecutively? That could take a while, but if its the only way, its the only way.|
This is in devlopment at www.multijournal.com
Hmm... I'm mainly asking because I'm writing a client, looking for more efficient ways to crosspost than looping through a list of journals.
I've though about it and tested it the only way is too loop through.
Hmm. Oh well, Perl's foreach loop is pretty good for that.
Got to get my laptop fixed or set this machine up to dual boot so I can test under linux, the client is to a useful level, before I make the beta release I want to make sure it actually works on Linux(which it should, Perl/Tk with no platform specific code).
Perhaps firing off multiple threads, each making their own postevent? Wouldn't work well for my client, as multithreading can very quickly kill portability, but it might be a technique that would work.
I tried multithreading and it killed perl and wasn't too reliable. Plus everything is being read from a database.
My plan is to have a listbox where whatever journals are selected, are posted to. If none are selected, it goes to your personal journal. Selections automatically cleared after you post(I *might* put a selection somewhere to preserve the selections, but I'm not sure).
2003-12-05 01:18 pm (UTC)
support isn't built-in because, as many others have pointed out, cross-posting is terribly impolite and annoying. making it easy makes it more common. sure, people can post multiple times (as they often do), but (to make an absurd example) we also don't want a box like "post this comment [x] times" because we don't want to encourage spamming comments.
I'd like to chime in with evan
that multiple posts of the same content are rude and annoying, particularly if they all show up on your friends page. Do you really need such a feature?
2003-12-07 12:06 am (UTC)
Indeed. I was considering sticking this in Deepest Sender, but it's just too easy to abuse.