Hmm, I don't think I have heard of that problem happening, before. Try deleting the plist (~/Library/Preferences/com.warped.iJournal.plist) and tell us if that fixes anything.

Here, it is because that is likely the cause. What you are talking about sounds like a preference issue since iJournal just reads what you have specified and sends that to the server. There is no logic, in the client, that would make it start back-dating the entries, for no apparent reason. Thus, there is probably something in the preferences which tells it to do this or part of the state was saved strangely and not properly reset. Deleting the plist will solve both of these problems.

In general, the reason to do this is because of the aforementioned saving of state potentially not being reset (which would be strange since it should be reset after a successful post, so it probably isn't that) or inconsistencies within the plist arising as a result of how different versions of iJournal may have changed the uses of some keys (that happens sometimes, but the only interesting one of these was when the login data changed from the plist to the keychain and this doesn't sound like that is the problem, here) where old entries are confusing the newer logic.

The other issue is that this may not be a problem with iJournal and many complaints, within this community, are not things which we can address. Remember that LiveJournal is always changing and sometimes a new change is buggy. Failing that, sometimes there are caching problems between the different servers that host the journals. This is often a reason for nearly random friend list strangeness and it is not something that we can fix. The more general problems here are simply because of the server being busy. We can't fix that, either. However, erasing preferences can resolve some data inconsistency problems and also removes old login data which many people are holding from former versions of iJournal. Such login data shouldn't be kept in clear text, within the plist, now that we have the Keychain.

Within the larger scope of Mac OS X applications, plist deletion is probably the second most likely solution to some random problem after permissions repairs because a program will start doing strange things if it records data which describes an invalid application state or behavior which would be inconsistent with the current state of the filesystem, or some other system component. By removing the plist, you resolve these problems by reverting this persistent state to nothing, and letting the application start with a clean state.

im always pissed off