Is this the ugliest browser in the world?
Yes. Yes it is.
January 18, 2005
December 18, 2004
December 13, 2004
Random leetness.
I just had to copy two files to a floppy disk because FTP was being an ass. So I check the values of the two files, tap them into Calculator and bang. The answer, was startling, and threw me for a second: 1,337.
The two files were zip archives of screen designs I'm being forced to create for college work. And I think they r0x0r compared to the tripe everybody else has turned in, because:
a) They're all using Paint or Paint Shop Pro
b) I'm using Macromedia Fireworks MX 2004 7.0.
That's all I came here to say. Yes, I am proud of myself.
December 12, 2004
Ok, who's selling the Internet on e-bay?
After a total hard drive failure, I'm back a few months on $FOOBAR development. Everything is now transported to a point of about August. Hence the $FOOBAR.
So, this is nothing interesting. Just another Adsense/Adwords oddness shot. I probably do too many of these, but e-Bay's are just weird. Apparently, in order to sell something on e-Bay, they require that you must own the right to sell it. I wonder if the merchant is a Mr. T Berners-Lee?
Note: I was looking at Web design tools on Tucows Linux
November 08, 2004
Political Spam
While casually looking at my Spam folder, I noticed this e-mail.
For the lazy, the crux of the humour is the subject line:
Bush is re-elected. Pro-zac anyone?
It's not the funniest thing I ever read, but unusual as far as the contents of my Spam folder is concerned, so I thought it was worth blogging.
And I'm levelling out the balance with that, by following with this...
There are many machines I simply must own. The main one on my list right now being the RipDrive. But as I've wanted a laptop/notebook for ages now, I've decided that I should actually go and buy one myself*. So, when I save enough money, I will own one of these fantastic IBM Thinkpad A31 Series machines...
Click for specs
* Fact is, I'm not the only one residing in the house in which I do, to desperately long for a laptop. So, after all the arguments were fought of who should use a laptop if and when one is bought, it will be a day of immense pleasure on my part when I take my WiFi enabled, Linux powered ThinkPad A31 Series Notebook out of reach, into another room. Leaving everyone else to deal with an Intel Celeron 366MHz, 64MB RAM dialup-connected Windows ME machine stuck in the corner.
I may open up my WiFi to the Celeron machine. Then again I may not. I need each and every one of my 750 kilobits per second. I wouldn't want to have to share them all.
And to anyone thinking "...wtf. Why doesn't he just get a Sony Vaio?", I direct the following phrasing:
Are you INSANE?
Vaios suck. One short Googling-for-Notebooks session taught me that. It was short, because I decided on the better option: Going for a Thinkpad. They rock more.
Besides; I just cannot deal with a touchpad. Many a time have I nudged the cursor on a laptop by brushing the touchpad while I type. Thinkpads have a Trackpoint in place of the touchpad; a small stick-type thing that sits somewhere in the middle of the keyboard, which is very intriguing, but I hear they're very sensitive, (ergo: usable, despite how they're portrayed in product images [see above]) and sound cool anyway.
That, and I like their TV ads.
October 29, 2004
Mini-rant
Oxford pair suspended for hacking.
This is just a little mini-rant about the media; its perception of technology and its use of terminology.
I've come to accept that the words 'hacker', 'hacking', 'hack' and 'hacked', when used by non-geeks, will always pertain to be descriptive of illegally gaining access to a computer system, the right to which one does not legally have; and possibly doing damage to data and/or computer systems which do(es) not belong to the user.
Fine. Every time I mention the difference between a hacker and a cracker to somebody, I get funny looks and my less-than-learned pupil dismisses the lesson as wrong and based on bad information. If it was the right terminology, they wouldn't use any other terms on the TV, of course.
So I've taken to using ThinkGeek's Black/White Hacker Hats to describe a 'hacker'; The Black Hat Hacker being of course nasty and evil (they often run Windows but have a good understanding of UNIX -- Their ideologies are dismissed by the open-source and Linux communities, so they stick to Windows -- but they're not stupid.) and the White Hat Hacker being the naturally inquisitive ('What Happens If I Do This...?') geek with an undying passion to solve technical problems (often creating them out of thin air when there appears there are none to be solved).
But again the media don't know what they're talking about. This is different from labelling someone the wrong kind of hacker. The students in the linked article apparently downloaded a program which was freely available from a mere Google search. That to me is not hacking. In either sense of the word. Black Hat Hacking, which is presumably what the article intends to reference, would be pulling up Emacs, Vi, or pico, or your favourite text editor, and writing a hack in your favourite language.
As I said, these two students are not White Hat Hackers trying to expose security flaws in the network; They're not even Black Hat Hackers trying to spy on everyone from the comfort of an isolated terminal -- these students are no more than Script Kiddies. The lowest of the low on the computing annoyance scale.* These people barely know a line of BASIC, have little knowledge of networks or security and are usually just as vulnerable a target as their intended victims. The only way they're able to harm anybody is with scripts they download from various sites or IRC channels; Usually proof-of-concept stuff when a new security hole props up.
* Might be worth a note that these students appear not to have intended on doing any damage, and their whole expedition was just to expose security holes in the network. (A mixture of Script Kiddies and White Hat Hacking, in a way, I guess.) My advice to anybody who notices such holes in a network like this, is to try and take your own measures to protect your own data (such as, don't let the master copy anywhere near such a network), but ignore the fact that the problem is there.
In my experience, SysAdmins (I mean here, the ones who aren't offended to be called 'IT Support'. My apologies to any SysAdmin who reads Slashdot. You're likely exempt from my judgement) are thick, don't understand how things work, and don't care for your complaints that there are holes in the system. You will be ignored.
Sometimes however, the Script Kiddie may know a bit of code, and may write their own scripts. Well bravo for learning to code, but -1000 gk pts for being a pain in the ass.
I guess it's my own fault, being wound up. Reading tech news at a site other than Slashdot.
I must be mad.
Anyway. That's all I came here to say. That, and, in other news, progress on the blog project, the whole point of this blog being here in the first place, is coming along very nicely indeed.



