The name of this blog was bloggerstatusforreal (that's the unique part). The URL, derived from the name, was http://bloggerstatusforreal.blogspot.com/ (before I migrated this blog to my custom domain, "blogging.nitecruzr.net").
Simple. But what if I didn't like http://bloggerstatusforreal.blogspot.com/? Maybe I would like my blog accessed as http://blog.myowndomain.net/?
The good news is - you're not stuck with http://yourblog.blogspot.com/ (or whatever you just setup). You have two choices, which will let you have a Blogger blog without the Blog*Spot URL.
- A blog published to a Google Custom Domain lets you use a blog with a Layouts template, physically hosted on a Google server.
- A blog published by FTP lets you physically host your blog on an external server, but restricts you to using a Classic template.
Both processes have problems - daily we'll see typically half a dozen trouble reports, from folks using one or the other. Neither Custom Domain publishing, nor FTP publishing, is foolproof; and as Blogger becomes simpler to use, we will see increased use by folks less experienced with computers. Computers and the Internet are becoming less toys for geeks, and more simple appliances for universal communication.
The latter factor will make Blogger Blogs increasingly problematic. Neither Blogger Help Forums, nor Blogger Support, will become redundant in the near future.
Both Custom Domain Publishing, and FTP Publishing, have their advantages.
- Both Custom Domain Publishing, and FTP Publishing, now give you
- Forwarding of the current Blog*Spot URL to the non-BlogSpot URL, so you don't lose readers that continue to use the Blog*Spot URL to access the blog.
- Retention of the current Blog*Spot URL, should you ever need to return to publishing there.
- Custom Domain Publishing gives you
- Ability to use Layouts templates.
- Availability of private blogs.
- Avoidance of known problems with FTP publishing.
- Dynamic HTML, and the many Layouts template features that require Dynamic HTML. This includes the GUI Page Elements wizard, XML based widgets, and full featured labels.
- Dynamic publishing, giving speedy publishing even as the blog gets larger.
- Hosting of your blog on a Google server. This will be more important, as your blog ages.
- Local publishing, eliminating excessive network traffic (which will be more significant, as the blog gets larger).
- No Content Hosting charges (which will increase, as your blog gets more traffic).
- No space limitations.
- No Spinner of Death when publishing.
- Simple setup, just like publishing on Blog*Spot (once you get DNS properly setup).
- FTP Publishing gives you
- Ability to publish on a non-Google server.
- Ability to publish your blog on the same server as the rest of your personal domain.
- Ability to use server side code such as PHP (on host servers that support PHP etc).
- Avoidance of known problems with Custom Domain publishing.
- Control over folder structure in the blog - ability to setup "mydomain.com/blog".
- A GUI control to turn the Navbar Off - no changing template code.
- No worries over blog outages that you can't control (subject to how good your third party server host is, when resolving its own outages, of course).
My suspicion, though, is that FTP publishing has a limited life span. From an economic and support viewpoint, it makes more sense for Blogger to concentrate its attention on Custom Domain publishing, where they control everything but the domain directory process, and can eliminate the uncertainty of supporting communications with hundreds of third party servers, complicated by geographical and network distance issues. I'm going to predict that, as Blogger gets the bugs out of Custom Domain publishing, they'll start to de emphasise support for FTP publishing.