Tip until things are fixed: Compose your entries in a text editor and then paste them in right before you go to send. That way if iJournal crashes you still have the entry.

Speaking of livejournal ... What is your icon a picture of? I like it.

No! I see it. I wasn't sure if you were mimicing Madonna or if Madonna was mimicing the source of your icon. I'm digging it.

CVS currently does have local archiving so it will be in the next release. Also, we are poking at the idea of making it a little more automatic about handling such things by changing some of the login behavior. If you need this right now I can compile a binary for you to try out. It would be nice to have more people trying out the new features, after all.

Well, how it is currently set up is that you pick a directory where you want to archive the posts and it will save an entry there right before it sends it to the LiveJournal server. If it crashes or you just want to open it later for some other reason you can use the Open menu item and it will load the post back into the user interface.

The next component to this will be to keep a per-user autosave or saved state which would be refreshed when they login. I will be working on that once I get some free time.

Well, the code that does the archiving is already in CVS and it is pretty simple.

This was actually to be the starting point to what would be a more general extension of capabilities. Currently, the entire UI and most of the code is very closely coupled with the assumption that it is using Live Journal. There is no real reason for this and I think that it would be cool if we could generalize the code such that there is a dictionary of data (I wrote this part for the archiving, already) from the UI which is built when the user hits send which is passed through a post system. This would simply be a collection of objects conforming to some protocol which would each post or save the data to some place.

This is obviously a large design change and not something I feel as though I have the right to say we are going to do, but it would make implementation of any post system very simple and they could even be NSBundle code plug-ins. It would be neat to just install a new iJournal plug-in when you want to start using another blogging site or archiving system and have it just work without it needing to be developed as part of iJournal.

The specific meaning that I would like to give to the offline archiving would be to allow for offline message writing which you could then post simply when you do come online. I know that the tight dependence which iJournal has on being connected has been a small annoyance of mine since I move around a lot and often have to go without always being online.

Is there a better place to discuss this? I feel odd using some stale message thread to discuss future development efforts.

Every once in a while command-a, command-c to copy the contents into your paste buffer. Then if it crashes, paste it back.

Not the best workaround, but it's an easy habit to get into.

you could try xjournal. I haven't had problems with it crashing... there is also phoenix, yax, etc... but xjournal is much more aquified than them.