I heard your voice through a photograph
I thought it up and brought up the past
Once you know you can never go back
I've got to take it on the otherside
Centuries are what it meant to me
A cemetery where I marry the sea
Stranger things that changeed my mind
I've got to take it on the otherside
Scarlet starlet and she's in my bed
A candidate for a soulmate bled
I push the trigger and I pull the thread
I've got to take it on the otherside
(parts of Otherside by RHCP)
Monday, March 16, 2009
Monday, March 9, 2009
Sunday, March 8, 2009
Daemon
Well, as you might (or might not) have gathered from my previous post, I've recently had the good fortune of reading "Daemon" by Daniel Suarez. Those interested in finding out more about the book can either visit its official site, or they can go to the trouble of googling for it. The book has got some awesome reviews, and it's the best geek-book I've read (although I understand that it's very easy and interesting for non-geeks as well) since Snow Crash by Neal Stephenson, but that's what this post is about.
Apparently, the last page of the book mentions something about something, and points the reader to the About the author page for further details. On visiting the said page, one will see a rather strange picture of the author. One that fans of ASCII art might find familiar. However, what is different about this particular sample of coloured ASCII art, is that the text itself hides a message in encrypted form.
Now, it seems that not many readers are aware of this, because on googling for it, I only found one relevant link: the one at Ethical Hacker. The people there have given a long and rather complicated guide to decoding the code by writing a program in C#. After which they've given rather vague and cryptic hints about writing a script to scrape the webpage periodically, as the author suggests. After several attempts (and several failed executions), I was about to hurl my keyboard across the room in frustration when I saw the "Forums" link at the top of the page.
There I saw that one of the users had had success in decrypting the code in merely 10 lines of Python code (excluding "include" statements). However, his code was rather incomplete (at best), so I set about writing my own.
And so, after two hours, I've written a script that checks the page, gets the RegexDate from there, compares it with a date stored in a local config file, and if the two are different then it proceeds to decrypt the web page and creates a text file containing the decrypted message on the user's desktop. And to top it off, it also uses gnome's libnotify to pop off a permanent notification announcing that the page has been updated.
To run this script, one will need to install pyDes, a python library that allows the user to decrypt base64 DES encoded strings. This library can be found here. It's a small download, just follow the instructions given on the page to install it on your system.
Windows users will need to modify my script to save the location of the config file. I believe changing sys.path.expanduser('~') to sys.environ('home') should do the trick. And you will also need to comment out the lines in which I call upon the notification system to display a notification. If you want something similar, try calling up dialog boxes from win32.
Oh, and the Ethical Hacker people have tried to ensure that only readers of the book will be able to decrypt the message by putting the encryption key as "Gragg's key" in their code. I have no such qualms, and hence have put the actual key in my code. The reason behind doing this is that only readers of the book would actually be interested in my script, so there seems to be little reason to stop them, or to force them to rack their brains trying to solve the "little riddle".
Apparently, the last page of the book mentions something about something, and points the reader to the About the author page for further details. On visiting the said page, one will see a rather strange picture of the author. One that fans of ASCII art might find familiar. However, what is different about this particular sample of coloured ASCII art, is that the text itself hides a message in encrypted form.
Now, it seems that not many readers are aware of this, because on googling for it, I only found one relevant link: the one at Ethical Hacker. The people there have given a long and rather complicated guide to decoding the code by writing a program in C#. After which they've given rather vague and cryptic hints about writing a script to scrape the webpage periodically, as the author suggests. After several attempts (and several failed executions), I was about to hurl my keyboard across the room in frustration when I saw the "Forums" link at the top of the page.
There I saw that one of the users had had success in decrypting the code in merely 10 lines of Python code (excluding "include" statements). However, his code was rather incomplete (at best), so I set about writing my own.
And so, after two hours, I've written a script that checks the page, gets the RegexDate from there, compares it with a date stored in a local config file, and if the two are different then it proceeds to decrypt the web page and creates a text file containing the decrypted message on the user's desktop. And to top it off, it also uses gnome's libnotify to pop off a permanent notification announcing that the page has been updated.
To run this script, one will need to install pyDes, a python library that allows the user to decrypt base64 DES encoded strings. This library can be found here. It's a small download, just follow the instructions given on the page to install it on your system.
Windows users will need to modify my script to save the location of the config file. I believe changing sys.path.expanduser('~') to sys.environ('home') should do the trick. And you will also need to comment out the lines in which I call upon the notification system to display a notification. If you want something similar, try calling up dialog boxes from win32.
Oh, and the Ethical Hacker people have tried to ensure that only readers of the book will be able to decrypt the message by putting the encryption key as "Gragg's key" in their code. I have no such qualms, and hence have put the actual key in my code. The reason behind doing this is that only readers of the book would actually be interested in my script, so there seems to be little reason to stop them, or to force them to rack their brains trying to solve the "little riddle".
Tuesday, March 3, 2009
Irony
Sunday, February 22, 2009
Of mice and seniors
I remember, in my first year I was quite close to a department senior named Ayshwarya. We used to talk about a range of topics, and once I complained to her about how I was barely getting any time for myself, what with lectures for eight hours a day, two to three quizzes each week (as part of the much-hyped "continuous evaluation system" here at BITS) and two hours of department work. She assured me that I was leading the "ideal" BITSian life, and that departments had after all been created with the aside of giving jobless BITSians something to occupy themselves with, there being very little to do here, what with we being in the middle of nowhere and all.
My main gripe at that time was that I had no time for introspection, for thinking about where I was and where I was headed. Now, I find myself in a situation wherein I have more spare time on my hands than I know what to do with. Life is indeed ironic to the extreme.
Anyways, talking about senior-junior relationships, it's occurred to me that "ragging" (although what happens here can barely be called ragging) is probably a unique way for losers to increase their own self-esteem. Ok, I realize that the above statement was really vague, so let me make myself clearer.
Basically, to the gullible juniors who come on campus, seniors come across as have-been-theres. Meaning individuals who've "been there, done that". I'm not exactly sure as to how this comes to pass, but most seniors, even those individuals whom you would judge to be complete losers under normal circumstances, come across as larger than life heroes (and heroines) during "interactions", as a consequence of which most juniors end up regarding their seniors as their own personal heroes, their mentors, someone they look up to and seek to emulate. In the junior's eye, nothing that the senior does could possibly be wrong, and they are correct and infallible in every possible way.
So what happens when these illusions are shattered? When the juniors come to realize that their seniors are human after all, and that they have their own weaknesses and glaring faults?
Well, just ask my juniors.
My main gripe at that time was that I had no time for introspection, for thinking about where I was and where I was headed. Now, I find myself in a situation wherein I have more spare time on my hands than I know what to do with. Life is indeed ironic to the extreme.
Anyways, talking about senior-junior relationships, it's occurred to me that "ragging" (although what happens here can barely be called ragging) is probably a unique way for losers to increase their own self-esteem. Ok, I realize that the above statement was really vague, so let me make myself clearer.
Basically, to the gullible juniors who come on campus, seniors come across as have-been-theres. Meaning individuals who've "been there, done that". I'm not exactly sure as to how this comes to pass, but most seniors, even those individuals whom you would judge to be complete losers under normal circumstances, come across as larger than life heroes (and heroines) during "interactions", as a consequence of which most juniors end up regarding their seniors as their own personal heroes, their mentors, someone they look up to and seek to emulate. In the junior's eye, nothing that the senior does could possibly be wrong, and they are correct and infallible in every possible way.
So what happens when these illusions are shattered? When the juniors come to realize that their seniors are human after all, and that they have their own weaknesses and glaring faults?
Well, just ask my juniors.
Saturday, February 14, 2009
Minor Grievances
Out of all the fond memories I have of my first year warden, Mr. Sanjiv Chandran, one particular memory stands out high above the rest.
It was the starting of my second sem. Tapan, my then-sidee, had just got a new comp and had set it up, and Harsh, his roomie, was particularly eager to play the game Prince of Persia: Warrior Within. So, at his behest, I'd gotten my copy of the game, and we were installing the game on Tapan's comp with the door wide open and game music pouring out of the speakers, when our beloved warden walks in.
Now let me outline the positions of all the players in this scenario. Harsh was sitting in a chair at the comp, peering at the screen, while I was next to him and maneuvering through the game's installation screens. Tapan was behind us somewhere, doing his own thing. Chandran walks in, and stares at Harsh for a couple of minutes, and Harsh stares back, unable to move, akin to a deer caught in the headlights of an incoming truck.
"What are you doing?"
"Installing a game... Sir," Harsh manages to speak.
"Get up."
(If this were a baseball game, this would be strike 1 against Mr. Chandran.)
Harsh gets up, and Mr. Chandran kicks the chair behind. And I kid you not here, he literally kicked it back. Then he opened his mouth to say something, and realized that the music would undermine his soprano, so he ordered us to stop the music.
Now, the game had chosen this time to ask us to insert the next disk, and Tapan's hands were probably shaking, so he couldn't quite manage to exit the installer. All this time, Harsh was mumbling something I don't quite remember. Anyways, Mr. Chandran finally got tired of the music and switched the comp off from the mains.
That was strike 2.
Unfortunately for him, he probably had no knowledge of what a UPS is, because to his everlasting amazement the computer refused to switch off and instead started beeping, which only aggravated him further. He got apopelectic with rage and started yelling at us. Fortunately, Harsh had the presence of mind to switch off the speakers and switch the mains back on.
After this Mr. Chandran proceeded to threaten us with, progressively, suspension, expulsion and deportation, as was (and is) his norm. And then he picked up Tapan's 8k TFT monitor with two fingers and threated to throw it at him.
That was strike 3.
And this is just one example of what Mr. Chandran does. In my first year, he wouldn't let us:
1) Sit in one room and talk
2) Sit in one room and watch a movie
3) Walk around in the hostel wearing shorts
4) Play music
5) Watch movies (even alone)
6) Play computer games
All of the aforementioned activities had to be carried out in a clandestine fashion, with sentries posted to warn us if the warden were to be sighted.
Mr. Chandran is still here, and from what I hear he still rules over his hostel inmates the way a prison warden rules over the prisoners. In the aforementioned game of baseball, Mr. Chandran would have been out at strike 3, with a probability of him losing his job for
a) Invasion of personal privacy
b) Threatening a person with damage to him or his personal property
c) Alienation of our basic human rights provided by the constitution
Ok, so maybe not the third one, but he was definitely out on the first two counts.
So why am I writing this here? Well, I don't know, guess I'm just venting. And plus, I hear that several BITSian profs regularly monitor BITSian blogs looking for miscreants washing the institute's dirty laundry in public, so...
It was the starting of my second sem. Tapan, my then-sidee, had just got a new comp and had set it up, and Harsh, his roomie, was particularly eager to play the game Prince of Persia: Warrior Within. So, at his behest, I'd gotten my copy of the game, and we were installing the game on Tapan's comp with the door wide open and game music pouring out of the speakers, when our beloved warden walks in.
Now let me outline the positions of all the players in this scenario. Harsh was sitting in a chair at the comp, peering at the screen, while I was next to him and maneuvering through the game's installation screens. Tapan was behind us somewhere, doing his own thing. Chandran walks in, and stares at Harsh for a couple of minutes, and Harsh stares back, unable to move, akin to a deer caught in the headlights of an incoming truck.
"What are you doing?"
"Installing a game... Sir," Harsh manages to speak.
"Get up."
(If this were a baseball game, this would be strike 1 against Mr. Chandran.)
Harsh gets up, and Mr. Chandran kicks the chair behind. And I kid you not here, he literally kicked it back. Then he opened his mouth to say something, and realized that the music would undermine his soprano, so he ordered us to stop the music.
Now, the game had chosen this time to ask us to insert the next disk, and Tapan's hands were probably shaking, so he couldn't quite manage to exit the installer. All this time, Harsh was mumbling something I don't quite remember. Anyways, Mr. Chandran finally got tired of the music and switched the comp off from the mains.
That was strike 2.
Unfortunately for him, he probably had no knowledge of what a UPS is, because to his everlasting amazement the computer refused to switch off and instead started beeping, which only aggravated him further. He got apopelectic with rage and started yelling at us. Fortunately, Harsh had the presence of mind to switch off the speakers and switch the mains back on.
After this Mr. Chandran proceeded to threaten us with, progressively, suspension, expulsion and deportation, as was (and is) his norm. And then he picked up Tapan's 8k TFT monitor with two fingers and threated to throw it at him.
That was strike 3.
And this is just one example of what Mr. Chandran does. In my first year, he wouldn't let us:
1) Sit in one room and talk
2) Sit in one room and watch a movie
3) Walk around in the hostel wearing shorts
4) Play music
5) Watch movies (even alone)
6) Play computer games
All of the aforementioned activities had to be carried out in a clandestine fashion, with sentries posted to warn us if the warden were to be sighted.
Mr. Chandran is still here, and from what I hear he still rules over his hostel inmates the way a prison warden rules over the prisoners. In the aforementioned game of baseball, Mr. Chandran would have been out at strike 3, with a probability of him losing his job for
a) Invasion of personal privacy
b) Threatening a person with damage to him or his personal property
c) Alienation of our basic human rights provided by the constitution
Ok, so maybe not the third one, but he was definitely out on the first two counts.
So why am I writing this here? Well, I don't know, guess I'm just venting. And plus, I hear that several BITSian profs regularly monitor BITSian blogs looking for miscreants washing the institute's dirty laundry in public, so...
Thursday, January 22, 2009
Confusion
Well, for those of you who still read this blog (statcounter says there were two visits yesterday and 13 in this week, so guess not everyone has given up on me) might be wondering how I went from three posts a week to one in three months, the simple answer is that I just couldn't think of anything to write.
I mean, in the beginning, when I first made my blog (not this one, this is the third one. Or maybe the fourth, I forget) I blogged about all the cool stuff that was happening to me at BITS. You know, stuff like meeting religious zealouts, my first interaction with the (in)famous Sajiv Chandran, experiences with drunk friends and so on. Later, in my second year, I blogged about disappointment, dashed expectations and heartbreak. Most of my posts were metaphoric, thereby ensuring that nobody other than those I was really close to would be able to fathom the depth of the posts. And considering that the people falling in that category numbered three of four, well, you get the picture.
The central driving factor behind all of my posts was, as Ramya pointed out to me, intensity. The stuff that I blogged about was stuff I intensely felt something about, be the essence of the feelings joy or sorrow. What changed over the summer holidays was that I lost most of whatever intensity I had. And no, it wasn't because something disasterous happened to me in the hols.
Another small reason for my not blogging was that my vocabulary and command over the English language seem to have diminished, no doubt due to the brojen combination of English, Hindi and Tamil that most BITSians converse in. Which is a very bad thing, considering that I will have to appear for GRE these hols.
Anyways, moving on... I guess what I'm trying to say here, is that I'd stopped blogging for all the wrong reasons. You don't have to blog to let the world know how much you're hurting, or to make the whole world laugh with you and get their appreciation. You blog because you want to. Because you've just found or done something cool that you want to shout out for the whole world (or atleast your subscribers) to hear. And maybe, in the process, to get a small bit of satisfaction from knowing that there are people who take time out of their busy lives to find out what is going on in yours.
So, what is going on in my life right now is...

And no, I haven't gotten a job at Apple. not even an internship (though not for lack of trying. Basically, I got Leopard working on my PC (and I know that's illegal, thank you for asking) and I have to say, while all the flak and criticism that Apple is getting for their stubborn policy of having one and only one way of doing anything might be well and justified, Mac OS X is still one magnificent piece of art. You know how all Apple fanboys will tell you that everything "Just Works"? Well, there's right. Everything does just work. Even on my PC, on which Mac OS X is not supposed to run, so I'm sure you can imagine how well it would work on Macintosh computers.
And surprizingly, all of this is on a Unix backend. That's right, the glittery GUI of Mac OS X runs on the same system as FreeBSD, OpenBSD and the other BSD's. And everything works, at the first try. I've been using it for over two weeks now, and I haven't had to open the console even once (although I did open it, but that's because I love the commandline). Compare this with linux, where chances are high that you'll have to open up the trusty console and tinker around with the system within an hour of installing the system, whether it be to get your lan card working, or to get some sound to pour out of your speakers.
And Linux (Ubuntu 8.04), even with a custom-compiled kernel, takes atleast a minute to boot and a little less than a minute to shut down, while Leopard, running on my hardware with a generic intel kernel, boots in 15 seconds and shuts down in 5.
Now why can't Linux be more like this?
I mean, in the beginning, when I first made my blog (not this one, this is the third one. Or maybe the fourth, I forget) I blogged about all the cool stuff that was happening to me at BITS. You know, stuff like meeting religious zealouts, my first interaction with the (in)famous Sajiv Chandran, experiences with drunk friends and so on. Later, in my second year, I blogged about disappointment, dashed expectations and heartbreak. Most of my posts were metaphoric, thereby ensuring that nobody other than those I was really close to would be able to fathom the depth of the posts. And considering that the people falling in that category numbered three of four, well, you get the picture.
The central driving factor behind all of my posts was, as Ramya pointed out to me, intensity. The stuff that I blogged about was stuff I intensely felt something about, be the essence of the feelings joy or sorrow. What changed over the summer holidays was that I lost most of whatever intensity I had. And no, it wasn't because something disasterous happened to me in the hols.
Another small reason for my not blogging was that my vocabulary and command over the English language seem to have diminished, no doubt due to the brojen combination of English, Hindi and Tamil that most BITSians converse in. Which is a very bad thing, considering that I will have to appear for GRE these hols.
Anyways, moving on... I guess what I'm trying to say here, is that I'd stopped blogging for all the wrong reasons. You don't have to blog to let the world know how much you're hurting, or to make the whole world laugh with you and get their appreciation. You blog because you want to. Because you've just found or done something cool that you want to shout out for the whole world (or atleast your subscribers) to hear. And maybe, in the process, to get a small bit of satisfaction from knowing that there are people who take time out of their busy lives to find out what is going on in yours.
So, what is going on in my life right now is...

And no, I haven't gotten a job at Apple. not even an internship (though not for lack of trying. Basically, I got Leopard working on my PC (and I know that's illegal, thank you for asking) and I have to say, while all the flak and criticism that Apple is getting for their stubborn policy of having one and only one way of doing anything might be well and justified, Mac OS X is still one magnificent piece of art. You know how all Apple fanboys will tell you that everything "Just Works"? Well, there's right. Everything does just work. Even on my PC, on which Mac OS X is not supposed to run, so I'm sure you can imagine how well it would work on Macintosh computers.
And surprizingly, all of this is on a Unix backend. That's right, the glittery GUI of Mac OS X runs on the same system as FreeBSD, OpenBSD and the other BSD's. And everything works, at the first try. I've been using it for over two weeks now, and I haven't had to open the console even once (although I did open it, but that's because I love the commandline). Compare this with linux, where chances are high that you'll have to open up the trusty console and tinker around with the system within an hour of installing the system, whether it be to get your lan card working, or to get some sound to pour out of your speakers.
And Linux (Ubuntu 8.04), even with a custom-compiled kernel, takes atleast a minute to boot and a little less than a minute to shut down, while Leopard, running on my hardware with a generic intel kernel, boots in 15 seconds and shuts down in 5.
Now why can't Linux be more like this?
Subscribe to:
Posts (Atom)