Mr P's invention

1/2 shot Drambuie
1/2 shot amaretto
Pour over rocks into a small glass, then fill with orange juice.
Float a couple of drops of Sambuca on top.

We are drinking cosmos or a close approximation. Yummy either way. And since I rarely drink these days, it's going straight to my head. Tee hee.
Cosmos are yummy too. I realize I am revealing a hidden streak of girliness when I say this, because my usual drink is bourbon or Scotch on the rocks, which is sufficiently butch to fit with the image. Pink. Pink drinks. Mr P loves pink drinks. And pink shirts.
To re-comment in case you do not see my comment on your earlier post and with respect to ljmigrate:

"Can I use this to copy posts from one LiveJournal to another (e.g. nsf_writing to natf) rather than from one LJ site to another? I really hope so. If not, do you have any recommendations?"
Okay, I have not personally tested that scenario (from one site to the same site, different user name). But theoretically it should work, and I have a report from one user who tried it. So you *should* be able to do this.
Thank you for the reply. I may test it out first on a couple of my name-holding-but-empty LiveJournals. I am hoping to consolidate all of my content containing LJs into my permanent account.
Good news! It does preserve the date and time of the original entry when it has copied them!

Bad news, it does not copy f-locked posts, but that might be because the journal I am copying them to is not on the FL of the journal I am copying them from. More testing needed!

Ah - oops - it did copy them but this account was not in the destination account's FL! ;-p

Edited at 2009-03-24 01:19 pm (UTC)
Boooo - when trying to migrate the posts to this account, I am getting a bunch of errors like this:

Fetching journal entry L-13 (create)
migrating entry to natalief
ERROR: Fault: Application failed during request deserialization:
not well-formed (invalid token) at line 62, column 330, byte 1521 at /usr/lib/perl5/XML/Parser.pm line 187
<Fault Client: 'Application failed during request deserialization: \nnot well-formed (invalid token) at line 62, column 330, byte 1521 at /usr/lib/perl5/XML/Parser.pm line 187\n'>
Traceback (most recent call last):
File "./ljmigrate.py", line 1018, in synchronizeJournals
code = int(e.faultCode)
ValueError: invalid literal for int() with base 10: 'Client'

Could that be because I was logged in as one of my other accounts at the time?

Edited at 2009-03-24 01:43 pm (UTC)
Further info:

17 entries migrated or updated on destination.
Fetching journal comments for: nsf_writing
Local xml archive complete.
Now generating a simple html version of your posts + comments.
188 new entries, 0 new comments (since 2003-04-07 22:00:07), 2 new comments by user
Run ended normally: Tue Mar 24 14:26:17 2009

So, it is backing up all 188 entries but only migrating 17. This is a huge pity - any ideas why it might be? I would *really* like the content of all of my diverse livejournals to be in my permanent livejournal - for some measure of posterity.

Edited at 2009-03-24 02:34 pm (UTC)
Error in the error handler! Let me attempt a fix for that today. The migration retry is failing for this reason, i think.
Trust me (the medically retired but still able to do a bit pedantic software and website functionality and usability tester/QA from HECK!!!!) to be able to break something without trying too hard! Anytime you need something tested... ;-p
I'm working on this today. So far I haven't been able to duplicate your error condition, but I should be able to fix it just based on your bug report despite that.
I'd have been happy with just the amaretto & orange. But he insists on playing mad scientist. Sometimes with horrible, horrible results.