February 26th, 2004

Simple import script written

I just finished a marginal hack on top of "Charm", a Python command-line LJ client that lets it import from Bloxsom flat blog data files.

It worked for me (tm). It converted http://blog.asheesh.org/bin/blosxom.cgi to http://blogs.jhu.edu/~gooftroop. (Hopkins Weblogs currently runs LiveJournal.)

I know some people around here expressed an interest in a simple whatever-to-LiveJournal import client. The code I used to do this is quite simple, and it could easily be incorporated into Charm. For now, though, if someone wants to use it, email me at ljimport@asheesh.org. When I get another few minutes, I'll give this script a name and put it up on a web page.
  • shaurya

Ever wished you could save a rare photograph in your journal?

Without having to depend on a third party server?

Well, this would be a good reason to have a tool that can convert images to text and back.

So, an application (zipped, 40Kb) for the purpose; you'll need the .Net framework (the link for general users) to get it to run.

Once you get it running, you could convert images to text and save them in your posts. Then later, you or your friends could view/save them by converting the text back to images.

It's a standard binary to base64 string conversion, not my proprietary code, so you could use any base64 decoder later to get the image back.

My application is just an easy-to-use tool that does this encoding and decoding for you.

The project (zipped, 45Kb) for those who want to have a look at the code. The interface is not very professional but it's just a small application and you can always use the code to change it if you want.

All the error messages are directly from the framework. Do let me know if you get any. Feedback/Suggestions are welcome. I wrote this yesterday morning in about 4 hours so it probably could do with a little improvement :) Let me know.

Collapse )

Also, for those who came in later, another application specifically for converting livejournal's CSV backup file to easily readable html; something I did more than a year back.

For that particular application, I would recommend the original DOS or console version of the application rather than the .Net one. I use the DOS one myself.