?

Log in

No account? Create an account
Ever wished you could save a rare photograph in your journal? - LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Ever wished you could save a rare photograph in your journal? [Feb. 26th, 2004|10:10 am]
LiveJournal Client Discussions
lj_clients
[shaurya]
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.

Couple of screenshots

How it looks on start up

How it looks ater selecting an image, the picture that started it all in this case

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.

Cheers!
linkReply

Comments:
[User Picture]From: cryo
2004-02-26 10:00 am (UTC)
otherwise known as: how to turn LiveJournal into UseNet.. welcome to the 80's!
(Reply) (Thread)
[User Picture]From: dottey
2004-02-26 10:19 am (UTC)
LOL!
(Reply) (Parent) (Thread)
From: shaurya
2004-02-26 08:12 pm (UTC)

Nice userpic :)
(Reply) (Parent) (Thread)
From: shaurya
2004-02-26 07:43 pm (UTC)

I'm getting there.

I'm not familiar with UseNet. Do educate me if you find the time.

Thank you for your feedback :)
(Reply) (Parent) (Thread)
[User Picture]From: xb95
2004-02-26 10:28 am (UTC)
Ehhh, you might want to be careful about putting huge images in your journal directly like that. Taking hundreds of kilobytes to store an entry in your journal isn't going to make the LJ people very happy.

LiveJournal is going to be providing image hosting soon enough as it is, so perhaps it's best to wait until then for the system that is designed to host images than to inflate the size of said images and throw them in your journal.
(Reply) (Thread)
From: shaurya
2004-02-26 07:56 pm (UTC)
Ehhh, you might want to be careful about putting huge images in your journal directly like that. Taking hundreds of kilobytes to store an entry in your journal isn't going to make the LJ people very happy.

I do agree with you and believe me; I did consider the possibility of such a reaction.

However, with reference to another reply of mine here, no system is completely secure and in the end it's stability depends only on the capability of the people who maintain it and on the integrity of the people who use it.

LiveJournal is going to be providing image hosting soon enough as it is

That's good news, I didn't know that.

so perhaps it's best to wait until then for the system that is designed to host images than to inflate the size of said images and throw them in your journal

Sure, but as I said, what's to prevent people from filling their journals with other kinds of copy-pasted text, like forwards, ebooks, news articles etc? These can run into pages and pages sometimes, much more than any single image and as I said in the other comment, the conversion increases the file size by about 10%.

Anyway, yes, I do agree that the tool could be misused but I think Lj does have some caps for post and comment length. At least, it does for comments, I'm not sure about posts.

As I said, it's just something I made for myself one morning to solve a problem that'd been bugging me for a long time - how do I save this photograph?

Just thought I'd share it with you, that's all :) Thanks for your feedback.
(Reply) (Parent) (Thread)
[User Picture]From: oosabeansaladen
2004-02-26 11:26 am (UTC)
I'm not very familiar with how base64 encoding works but if converting an image to text makes some of the character be "new line", the LJ server will convert it to a BR tag on the fly. This could seriously break you file if I'm not mistaken.
(Reply) (Thread)
[User Picture]From: wooble
2004-02-26 01:51 pm (UTC)
Not if you use the "Don't autoformat" option, it won't.

Not that I necessarily think turning LJ into storage for base64-encoded binaries is a good idea.
(Reply) (Parent) (Thread)
From: shaurya
2004-02-26 08:23 pm (UTC)
Not if you use the "Don't autoformat" option, it won't.

Good point :) but that isn't necassary either. Do check out my reply to oosabeansaladen's comment too.

Lj may add br tags to the html but when you copy the text from the browser and paste it into the text box in the application; you're just going to get line breaks again, not br tags.

Not that I necessarily think turning LJ into storage for base64-encoded binaries is a good idea.

No, it isn't.

But it is a journal and sometimes I feel like saving a special picture or photograph in your journal, don't you? :)

I've voiced my views on the matter in some of the other replies on this post. Please do read and feel free to reply.

I have no wish to cause any kind of harm to Lj.

Even I have developed quite some attachment to it over the last two years and if this is going to be a problem, I can take it off the net.

But what's to prevent someone else from making one? As I said, it was one morning's work, for me.

For all we know, people may already be using such things and ignoring them isn't going to make it go away. At least if we on Lj think of such possibilities, we can also take suitable action to make sure they are used properly.

Thank you for voicing your thoughts :)
(Reply) (Parent) (Thread)
From: shaurya
2004-02-26 08:04 pm (UTC)
Good point but as the br tags are just html, when you copy the text again from the browser, you'll just get line breaks which are taken care of by the app.

Essentially, you get back exactly what you saved in the first place. The br tags are just Lj's way of making sure it shows up the same way you saved it :)

I've already tried it, do try it out. The application cleans up and unnecassary line breaks anyway.
(Reply) (Parent) (Thread)
[User Picture]From: rog
2004-02-26 04:59 pm (UTC)
ergh. That is a waste of space.

Nifty idea, but it's a somewhat dodgy solution looking for a problem, IMHO. There are better ways to store and share images (and files in general).
(Reply) (Thread)
From: shaurya
2004-02-26 07:30 pm (UTC)
Sorry about that (the earlier reply), that comment was an update on my original post.

I agree, there are better ways of storing and sharing files, I host my own images (like the ones in this post) on other servers.

But there are times when I need to store something on my journal itself, something like an important photograph which I want as part of my diary/journal.

I wrote this tool for such things.

As for space, yes, images do take up space but the conversion itself adds little more than 10% to original size so in the end it all depends on whether the storage is used or misused.

Thanks for your feedback :)
(Reply) (Parent) (Thread)
From: shaurya
2004-02-26 07:35 pm (UTC)

Update on original post

I've not tried that base64 link (the google search) out.

The link was on a reply to the original post in my journal.
(Reply) (Thread)