Blogger Babes

It turns out Blogger beta isn't a wasted effort at all! For one thing, you get the "dog" (looks to me so) replacing the B of the Blogger. I realized only today that using the beta is a privilege accorded only to a few lucky ones (I didnt notice because privileges are so natural for me *snicker*).

As I said somewhere, it is good for the non-tech people, as it uses those AJAX enabled snippets to arrange layouts according to the user's taste. The general population (who doesn't even have the desire) wouldn't now have to get their hands dirty with HTML and CSS. Adding custom code for statistics is just drag-and-drop, keeping the flow intuitive.

Close to hell for us techies, 'cause you cannot live if you cannot customize; and that's just what Blogger doesn't let us do at the moment.

The better thing is that, with the beta release, Blogger marks the shift to the dynamic web. Wonder why it has taken them so long, all the rest of the services are long established on it.

By dynamism of the web, I mean that you no longer have to publish your blog every time you make a change in the template. Old blogger used to publish pages of your blog to its server, and serve the appropriate pages whenever a request arrived. With the beta, the pages would be created on the fly, no more publishing.

All the bitching was due to the fact that I had recently delved into the Blogger codebase, and had come up with really interesting tricks like customizing the individual pages, recent comment box on the sidebar, intuitive layouts; and then *poof*... Blogger beta strips me of any right to modify my template.

These snippets are available if any of the old Blogger people (or the beta users who haven't switched to layouts) want them for their blogs.

The Craze Beta

What is with everyone coming up with the beta editions of their offerings these days? Starting with Gmail Beta, we get Windows Live Mail Beta, Yahoo! Mail Beta, Yahoo! Photos Beta, Flickr Beta, and now, sweet Blogger goes beta too!

For many services, going beta just means getting AJAX-ified, with little or no improvement in features (Windows Live Mail leads the contest), only getting a face-lift and incorporating oh-those-cool-functions on the page that have nothing whatsoever to do with cutting the round trip time...!

With a sense of loyalty to the technology and the tech community (not to mention the need to be the first in trying things out - izzat ka maamla), I have officially switched to the new Blogger Beta. Switched - 'cause, ummm, beta could be exciting; officially - 'cause Blogger Help says you cannot opt out of the Beta!

So what does this beta has to offer over the old version? For one, the "privileged ones" now have a separate, red carpeted entrance at http://beta.blogger.com. Ordinary mortals should stick to their filthy swamps and keep using the lowly Blogger home page to log in.

The Blogger people have added support for tags - or "labels" as they call them. Der ayed durust ayed is the only thing that comes to mind.

And there is this supposedly cool Layout feature, that help you manage the "template" of your blog. Beware, the "template" word is hushed now, if you're cool, you'll have a layout.

So the layouts help users "drag and drop" widgets, or little snippets (previous posts, profile, description etc) on the page. Intuitive it is, but couldn't achieve its full potential until the "Edit HTML" option starts working. Gives us "power users" that creepy feeling of helplessness!

That means my little blog page has some AJAX elements in it. How I have been dying to have a little Ajax, that would keep my dishes clean... Who said God doesn't listen?!

Oh, and by the way, you'll have to comment by choosing the "Other" or "Anonymous" option on the comments page, your logged in nick wouldn't work here. Of course, what did you think? Its Beta!

Besides that, all the functionality is unchanged. They have tried to spruce up the Dashboard a little, with cramming the various blog-specific options, and the Blogger Buzz posts. Heck, they even forgot to fix the bug that occurs in the Rich Text Editor that it doesnt convert line breaks to hard line breaks :\ So it'd be better to stick to posting via e-mail!

Buss ooper say make-up kiya hai, under the hood its all the same!

Returning to the Craze Beta, I forgot to tell you: Flickr has gone a step ahead, its now Flickr Gamma!

And that gives an excuse for procrastinating office work too. Whenever somebody wants to take you to task, just claim that you've gone beta!

Sm**ing the night away...

Meeting with an important client in the morning, and I have just smoked the night away...

Rings and smoke and despair, acting as a warm blanket over me, taking me in their arms, cajoling me, killing me. Must get around it somehow, the day is already doomed.

Blogger Reds

There seems to be (yet again?) a problem with my Blogger template. It somehow magically decided to just fly away, leaving me with a bunch of useless code. The backup of my customized template was in my puked up PC, which refuses to connect to the LAN.

So I have uploaded a temporary template, a very stripped down version. But hey, it would load faster, isnt it?

Bear with it for a few days. I'll bring up a rocking new template!

Sending mail with System.Web.Mail (.Net 1.1)

If you thought that it was a serious shortcoming that .Net framework 1.1 wasn't able to send email through SMTP servers that used authentication, you are in grave ignorance. On the surface of it, yes, you cannot send an email with the standard System.Web.Mail.MailMessage class; but you can of course play tricks on the Exchange server (yeah, that's what I get out of it that this things works only on an Exchange server) to make it authenticate you.

There is a namespace called http://schemas.microsoft.com/cdo/configuration that does those funny (and highly interesting) tricks. First we would check how to use a simple SMTP server (no authentication), and then we will use authentication to send a message.

//using System.Web;
//using System.Web.Mail;

//The simple SMTP Server
MailMessage message = new MailMessage();
message.From = "src@someone.com";
message.To = "dest@someother.com";
message.BodyFormat = MailFormat.Html;
message.Subject = "This is a spooky mail!";
message.Body = "Heheh, just kidding!";

SmtpMail.SmtpServer = "your.server.address"
SmtpMail.Send(message);

Now lets check out a server that uses authentication. Microsoft provides the CDOSYS object to achieve just that. You wouldn't think they were so dumb that they didnt incorporate some lousy authentication mechanism! Add the following lines before the SmtpMail lines.

message.Fields[
"http://schemas.microsoft.com/cdo/configuration/smtpserver"
] = "your.server.address";
message.Fields[
"http://schemas.microsoft.com/cdo/configuration/smtpserverport"] = 25;
message.Fields[
"http://schemas.microsoft.com/cdo/configuration/sendusing"] = 2;
message.Fields[
"http://schemas.microsoft.com/cdo/configuration/smtpauthenticate"] = 1;

//Most of the times the @domain is necessary with the username
message.Fields["http://schemas.microsoft.com/cdo/configuration/sendusername"] = "username@domain.com";
message.Fields[
"http://schemas.microsoft.com/cdo/configuration/sendpassword"] = "urpassword";

//If only the server uses SSL, in this case, the smtpserverport field would be different too
message.Fields["http://schemas.microsoft.com/cdo/configuration/smtpusessl"] = true;


And that would do just fine. There you go, I just saved your time and money!

[P.S. To those whom these lines look like Greek, I must say that this post appears as a record!]