Pages

Showing posts with label Blogger. Show all posts
Showing posts with label Blogger. Show all posts

Wednesday, 6 January 2016

Open Live Writer - change blog posts folder's default location





This post shows how to change the default location for where Open Live Writer saves your blog posts and drafts, if you don't like its default location. This means that, for example, you can point Open Live Writer to where your old Windows Live Writer blog posts were on your system (at least if you used an external hard drive like me), and reuse those folders, so you can migrate from Windows Live Writer to Open Live Writer easily. This is in Windows 7 - YMMV.

Basically, the method used for Windows Live Writer works to change where Open Live Writer saves and looks for your blog post files, but with some tweaks, as I show below. In my case, I stored all my documents and other files on an external hard drive (called G on system) rather than C drive, including my Windows Live Writer blog posts folders. So I'll use that to illustrate, but your folders will have different locations.

After you've installed Open Live Writer, here's the step by step instructions on how to change its default Save / Open location:

  1. Open your Registry Editor and backup your Windows registry (click on the top level i.e. Computer, to backup the full registry). Alternatively, navigate to Computer > HKEY_CURRENT_USER > Software > OpenLiveWriter, singleclick on OpenLiveWriter, then export the key.
  2. Make sure Open Live Writer is closed, just in case - so exit it if it's open.
  3. Go back to the Registry Editor and navigate to OpenLiveWriter as in step 1 above. Rightclick on OpenLiveWriter on the left; then select New > String Value:

    image
  4. Then, immediately type "PostsDirectory" (without the quotes) to overwrite "New Value #1", in the right pane

    image
    with the word "PostsDirectory" (no spaces), so that it looks like this in the right pane:

    image
  5. Next, find the main folder on your system where you want your blog posts and draft blog posts to be stored, and note down the path to the folder. If you have an existing folder, use that; if you don't just create a new folder wher you want it.

    Tip: to note down the path easily, in Computer or Windows Explorer, just navigate to the folder you want. Make sure you've opened the folder in Computer / Windows Explorer. Then click in the address bar. The path will be highlighted automatically, and you can just use the keyboard shortcut Ctrl-c (hold down the Ctrl key and tap the c key) to copy the path to your clipboard.

    image
  6. Then go back to the Registry Editor. Doubleclick on PostsDirectory on the right, that you created earlier. In the "Value data" line of the box that pops up, just enter or paste (using Ctrl-v) the path to the main folder where you want to save your Open Live Writer blog posts (on most systems, you would have a top level folder called e.g. "My Weblog Posts"). For example, on my computer I want to store them on my G drive in the Documents folder, in a sub-folder called "My Weblog Posts", so I would enter this:

    image
  7. Obviously, you would enter something different depending on where you want to store your blog posts on your own system. Then click OK.
  8. If you had an existing blog posts folder, e.g. that you had been using under Windows Live Writer, and you entered its path in "Value data",  Open Live Writer will now recognise it. In particular, you'll see your draft posts and recent posts (as previously saved in Windows Live Writer) when you open local drafts or recent posts in Open Live Writer.

    image
  9. If you had just created a new main folder for your blog posts, subfolders called "Drafts" and "Recent Posts" will automatically be created for you, into which your draft posts and future published posts will be saved:

    image

Use Open Live Writer with Blogger / Blogspot.com: tip





If you used desktop blogging client software on your computer, like Windows Live Writer, to blog on Google's Blogger or Blogspot.com, you'll know that since April/May 2015, it stopped working. This is because, in late April 2015 Google updated the authentication method for logging in to Google services. Many people had problems blogging on Blogger / Blogspot after that.

The good news: Microsoft generously open sourced Windows Live Writer, which became Open Live Writer, and since 17 December 2015 you can use Open Live Writer with Blogger or Blogspot blogs! (download Open Live Writer; GitHub fork).

One big tip. When you use Open Live Writer for the first time, or add a new account to it, there's a further option in OLW which wasn't available before December 2015. It's easy to miss it (I did!), so I'm flagging it here.

In "What blog service do you use?", make sure that you select "Google Blogger" and not (as was the case before, with Windows Live Writer) "Other services", or it'll go wrong after that.

image

Then most other things should be as they were before with Windows Live Writer - though see known issues. Also, note that Open Live Writer is still a work in progress, so it may take a while to get all features back as they were - e.g. see a summary of some features, and the roadmap.

Also, contrary to what some other people have been saying, you can keep your Windows Live Writer blog posts (at least if they were on an external hard drive), and just point Open Live Writer to the location of your WLW folder!

Friday, 4 June 2010

Blogger: do usability study, get $75






Team Blogger are going to conduct several usability studies of 1 hour each between 17 and 24 June 2010, via phone and broadband computer connection. (Interestingly you have to have Windows 7, Vista, 2000 or XP for the session - not Mac or Linux, despite Google reportedly deciding to stop using Windows internally due to supposed security concerns!)

It seems from the sign-up form that you don't even have to be a current Blogger user. Needless to say, you don't have to live near Google's California offices.

If you'd like to help improve Blogger do fill in the form (for age 18 & up only), and if you get picked to take part they'll give you $75 in Amex gift checks for your trouble. Note that they'll be recording the sessions. More FAQs here. No guarantee they'll select everyone who signs up, of course - they aim to get a mix of people - but no harm signing up!

Monday, 10 May 2010

How to add hNews to Blogger blogs





Making your blog hNews-compatible should help it get picked up and indexed by hNews-capable search engines like Value Added News Search.

hNews is a relatively new microformat, designed to enable more useful computer indexing or processing of news stories, blog posts etc. (Technorati tags are another microformat.) Google can recognise and make use of some microformats already with their Rich Snippets.

So see this tutorial on how to edit your Blogger template to make it hNews compatible and produce the basic hNews info in your blog as standard - post title, author, date.

Marking up the text within an individual story or post seems to be the main point of hNews, but also seems to be a real pain. Does anyone know any tools that could help bloggers do that, e.g. a plug-in for Windows Live Writer? I'd do a Greasemonkey script if I could, maybe in the summer, but Kirk is the real expert behind the Technorati tagger for Blogger.

Tuesday, 2 March 2010

Blogger users beware: phishing attack





According to security firm Trend Micro, bad guys are sending emails to Blogger users, pretending to be from Blogger.

The email asks users to "update" their accounts by clicking a link - which seems to lead to a Blogger login page starting with the same domain name as the real Blogger site, but in fact is a fake page where, if you enter your Blogger login details, they'll steal them.

So beware.

Granted, people might not be surprised that British politicians were taken in by Twitter phishing scams last week, but when even someone as tech-savvy as Cory Doctorow has had his account hacked (according to a Yahoo! story), it shows you just can't be too careful.

Tuesday, 16 February 2010

Blogger music blogs - what to do if you get a DMCA notice





If your music blog uses Blogger or Blogspot and you get a copyright infringement notification from Blogger under the US Digital Millennium Copyright Act, which allows blogs etc to be taken down for copyright infringement, what should you do?

  1. Check that you really were authorised by the copyright owner of the music to link to the music complained about (and that the upload of the file you link to was also authorised), or that you have a decent chance of arguing that your use of their content was "fair use".
    1. Tip: see the Citizen Media Law Project's excellent note on Responding to a DMCA Takedown Notice Targeting Your Content for helpful info on the procedure and what's involved.
    2. You might well want to seek US legal advice in your particular situation; the EFF do take on some cases, but only a very few.

  2. If you're sure you have the copyright holder's permission or your use was fair use and you want to fight the take down, you can't just sit around - you need to send a counter-notice to Google ASAP. Here's how to send a DMCA counter-notification to Blogger. Note that:
    1. Google do link to a helpful counter-notification generator which you can use to produce your DMCA counter-notice.
    2. You have to say in your counter-notice that you believe in good faith that your content was wrongly removed - if you know it was actually infringing copyright, then you can't say that, you'll be done for perjury. So think about your justifications before you file the counter-notice. You have been warned!
    3. Although copyright complaints can be submitted online via an infringement notice form, you have to send your counter-notice to Google by fax or hard copy post to the fax number or address they give. Yes this sucks if you're not in the USA as it will cost you extra time or money.

  3. Generally, make sure that your email address in your Blogger profile is up to date, so that you don't miss getting any future emailed complaint notices from Blogger.

Team Blogger had recently clarified how they operate when they get complaints that a blog hosted on Blogger / Blogspot breaches copyright, but they didn't initially clarify how you as a blogger should respond, so if you missed the update to their blog post, then I repeat, see how to send a DMCA counter-notification to Blogger.

The good news is that now, rather than completely deleting the blogs complained about, following the negative publicity about "bad" takedowns Blogger are moving the blogs into draft so that if there was an error or the counter-notice is successful, the blog posts and links won't have been completely deleted as was the case before (though apparently they were still recoverable if subscribed to via Google Reader!).

The incidents where bloggers' blogs were taken down, in at least one case entirely by mistake when there hadn't even been a DMCA complaint, have been covered e.g. by the Guardian and Ars Technica.

This isn't legal advice etc, I just thought that a quick list of steps to take might be helpful, obviously if you need to you should consult a US copyright lawyer.

Monday, 15 February 2010

Blogger: update your blog template ASAP





If you use Blogger or Blogspot for your blog you've probably seen the announcements from Blogger when you login, and the blog post on the official Blogger Buzz, to update and review your blog templates in case they link to files hosted on Google Page Creator.

But if you use Windows Live Writer to publish your blog posts, like I now do, you may have missed the warning.

So just a reminder that over the next few days you'd better do what they suggest or links in your blog may break when Google take down their Page Creator. Which is a shame, it was so much more flexible than Google Sites.

Saturday, 15 August 2009

How Blogger changed my life (& my new blogs)





Here's my contribution to Blogger's 10th anniversary search for stories "about what Blogger has meant to you over the past decade."

It's not as exciting as blogging while rowing across the Atlantic, but Blogger's still helped to change my life. Or at least, change career.

The "A Consuming Experience" story

I haven't been using Blogger quite as long as a decade. It's been since the end of 2004, nearly 5 years now. Originally I wanted to write a consumer issues blog - hence this blog's title (and yes, I love puns!).

Mercenary that I am, I followed the trail of the most hits (and being sent or lent cool stuff to review!). I switched to blogging mainly tips and tricks about blogging on Blogger - my first big hit, though no longer the greatest, was my introduction to Technorati tags, it's still up there if you search Technorati tags tutorial; and ACE was even added to Blogger's Blogs of Note a year later. Then I switched to mainly consumer technology reviews and tips and Windows tips and problem solving. Which is where this blog is now.

I have no science background except maths/science A Levels years ago, so I had to work everything out from scratch. Which means that if I can understand something, anyone else with half a brain cell can too.

The main attraction of this blog seems to be my howtos, particularly fixing issues with Windows or mobile phones. (At least, I don't think it's the consumer rants, bad puns, tech innuendo or my love affair with nominative determinism…).

I hate technical jargon, which I think is exclusive in the worst possible sense. Just because people don't understand a technical term doesn't mean they're stupid, and it doesn't justify being patronising or treating them as stupid. It just means no one's explained to them what that term means, yet.

So I try to write about stuff in a way that I can understand - which means lots of other non-technical people can follow my how-to or troubleshooting instructions, too. Importantly, I don't skip basic prelim stages which too many other writers gloss over, as I don't assume the high base level of technical knowledge too many other writers do. Step by logical step is king.

The result

That attitude has paid off. ACE gets about 2500 unique visitors per day now on average (fewer at weekends), and has reached over 2 million visitors in total since its inauguration. ACE was even approached for syndication via Corante (which I left), then by Newstex, and asked to join the LG Blogger Relations programme, and now some things with 3 Mobile Buzz.

Most of all, though, I enjoy being (as I like to think of it) of some real use to society. I love analysing things, finding solutions to problems and sharing them, demystifying stuff that shouldn't be made a mystery in the first place, helping people in a concrete and immediate way. It makes my day to get comments e.g. on my post on how to add MP3s to Blogger, like:

One of the most useful, concise and informative posts I've read this year. Thanks

Or on this horrid Windows - no disk Exception Processing Message c0000013 Parameters 75b6bf9c 4 75b6bf9c 75b6bf9c problem:

You took the time to explain it in a very practical,full & simple way.
And most importantly: IT WORKS!
Thanx a million times.

And this on rotating mobile video 90 degrees:

oh, awesome instructions you gave. Was drowning in the internet until you came along....brilliant, you have made a whole family happy!

A particular favourite is a comment, on my post on no sound in Windows Vista:

I can't thank you enough - some of the other solutions were like cutting your arms off and sewing them back on!
This took me 10 seconds!
SO HAPPY!

To my readers, thanks for the feedback and please do keep your comments coming! Even negative but constructive ones. (Though I haven't had many negative ones, thankfully. Except for spam.)

The big change

As this blog revived my interest in computing, technology and science, I started going to geek events and meeting technologists. Many of whom are interesting, fun people. That I can talk gadgets and computers with, without being looked at funny!

Soon, I began preferring blogging to my day job in the City of London.

My job was financially rewarding - only token bonuses if any, but a better salary than the average Londoner's; regular hours, which allowed me time for outside interests like singing and blogging; a team with great people who were good to work with; and interesting, intellectually challenging work, with a chance to figure new things out and help others learn them. Indeed one of the best moments in my life, ever, was when my boss forwarded me an email from a very senior, very smart and very respected executive about a talk I gave on a new technical area, saying that only after my talk did he finally understand that topic for the first time. Wish I'd kept a copy of the email.

A dream job, some might say. And it was, for years. But I'd been doing the same type of job for a long time and while some things changed from time to time, my work essentially stayed the same. And I knew the job would pretty much stay the same for the foreseeable future, even if I moved to another outfit.

So, what did I do? Just as a recession was starting, I decided to quit one of the very few secure, well paid(ish) jobs left in London, in order study technology properly. All because of this blog.

And happily ever after?..

So thank you, Blogger and Google! You really have changed my life.

Ideally, I'd now like to try to make a living as an analyst / writer / adviser on things technological, maybe with some programming on the side (I still prefer writing English to code, though as it turns out I'm actually not a bad programmer judging from my marks). It will mean much less money than I was making in the City, but that's not what matters to me anymore.

Before anyone asks, writing this blog just isn't enough. Despite the volume of traffic ACE gets, my Google AdSense money's nowhere near enough to live on. It just about covers blogging-related expenses if I'm lucky.

So, am I mad to try to switch careers? Time will tell.

In a few weeks, partly in honour of Blogger's 10th anniversary, I'm going to do what I've been planning to do for the last nearly 5 years - start a series for the beginning blogger on how to blog using my favourite Blogging platform, Blogger, step by step.

I know there's lots of blogging tutorials or introductions out there; this will just be my personal take on it. I recently convinced a (very technical) friend switch to Blogger, and realised there were still tips even technical people could benefit from. As well as the main people I write for, of course, i.e. the intelligent non geek.

I'm still going to write about things consumer, particularly consumer technology, here on ACE.

But to try to make ACE more targeted on computing and technology from a consumer angle (which also helps for SEO!), I'm starting separate blogs for the odds and ends on other subjects I'm interested in which I want to record for myself or to share. I'll probably keep the occasional funnies on this blog, though.

So say hi to -

Meanwhile, if anyone has any tech writing / technical advice / coding jobs going in London from mid-late September - part time only, for now - please feel free to get in touch! Open-mouthed

Wednesday, 3 June 2009

Blogger, WordPress: Google Analytics for your blog





Just a heads up for those who’ve not seen it – there’s a good summary post on the Google Analytics Blog about how to install Analytics on WordPress and Blogger, with links to howto tutorials etc. And indeed why it’s useful to measure statistics / metrics for your blog using web analytics.

If you’ve not installed code on your blog to track the number of your visitors (with charts / graphs etc), which pages are most popular etc, I’d advise you should do so as soon as possible. Unless you really don’t care, of course! But it’s interesting viewing even if you don’t.

I’ll be doing a more detailed post in future about how to do certain useful things like check visitors to a specific webpage, figure out who’s sending visitors your way when you’ve experienced a sudden increase in visitor numbers, etc.

Saturday, 4 April 2009

Blogger: eeyore is cute!





As Kirk points out (and Blogger acknowledged), some users of Google's Blogger who publish via FTP have been seeing a new post that says "eeyore is cute!" (awww, yeah, see the pic above) - and some non-FTP users who chose to get post confirmation emails may also have got an email about a test "eeyore is cute!" post.

His guess as to what happened was correct: "An internal load testing at Blogger somehow got some wires crossed that let their test post get published on some blogs."

Here's a screenshots of one of the affected blogs:


So not to worry, if you got that post or email your blog hasn't been hacked, it was just an internal mixup at Google, all you have to do is republish your blog and that'll fix it. Clearly there are Pooh fans at Google!

Would be even funnier if this started happening on 1 April!

Note: low resolution Eeyore pic downloaded from Wikipedia, made even smaller and displayed on the same basis i.e. believed to be fair use; but if the owner disagrees please let me know.

Saturday, 21 February 2009

Blogger: how to promote your blog; & drafts now bear correct dates when published!





It’s worth pointing out a couple of recent Blogger developments:

1. How to promote your blog - tips

Team Blogger highlighted their help page listing their accumulated wisdom on things to do to promote and publicize your blog, and how to add your blog feed to your Facebook profile.

The tips are small but perfectly formed, and many are quite general and don’t just apply to Blogger blogs – so go check ‘em out!

(I confess to violating some of their “rules” – my posts are often too long, and these days I rarely have time to reply to comments on this blog let alone comment on others’!)

If this topic interests you, you may also be interested in "Six Sayings for SEO Success".

2. Draft posts published with the correct date, at last!

One of the biggest flaws with Blogger: if you create a draft post on day 1, then tinker with it a bit over the next few days, and finally publish it on day 8 – the post will actually bear the date of day 1, i.e. the date you first created the draft post; not day 8, the date you published it, which is the date it should really bear.

That’s why I and many others resorted to Greasemonkey scripts like Keep Current Date and Time which Jasper produced and Aditya updated (and Kirk has tweaked!).

The good news? Team Blogger have finally fixed this niggle, with what they call “automatic date and time”.

However, it only works in Blogger in Draft at the moment. (How to use Blogger in Draft.)

It’s hidden there under Post Options (that’s another of my Blogger bugbears, that Post Options is no longer permanently open – in my view it should be):

Click the Post Options link to expand it and you’ll see the new feature on the right, “Automatic” is ticked by default which is fine (Blogger Scheduled posts most already know about):

In order to use this feature, these are the steps:

  1. Disable Keep Current Time if you have it (Tools, Greasemonkey, Manage User Scripts, leftclick once on “Blogger Keep Current Date” to select it, UNtick “Enabled” in the bottom left hand corner, then click Close). You won’t need it if you use Blogger in Draft, and keeping it stops the new Blogger in Draft feature working

  2. Login via Blogger in Draft (instead of via the usual Blogger site).

  3. Create your post there in the usual way.

  4. If you do any intermediate edits of your post, the best way is to do it by logging in via Blogger in Draft – not “non-draft” Blogger.

    (Note: If you login to non-draft Blogger and edit the post there while Keep Current Time is enabled, the interaction between the two seems to mess things up and then when you try to publish it, even from within Blogger in Draft, it may revert to just showing the date of creation. You have been warned! That’s why step 1 is to disable KCT. If you temporarily disable it before opening the post for editing, then save and leave the Edit post page, then re-enable KCT again, it may be OK – but the safest course is just to disable it altogether. Of course when this feature is rolled out you can permanently get rid of KCT so this will no longer be an issue.)

  5. When you’re ready to publish the post, again do not login to Blogger, make sure you sign in via Blogger in Draft, then publish it from there. Otherwise, it won’t work – the post will still bear the date of its original creation, not the date of publication.

Tuesday, 22 July 2008

Blogger improvements: wishlist





Team Blogger have clearly been been working mighty hard on improving and upgrading our blogging experience using Blogger, yay to them!

Here is my personal wishlist of most wanted things which don't seem to be on their public to-do list. If you agree with any of my wishlist items please say so, maybe that'll up their chances of getting a precious place on that list. This post is meant to be constructive rather than critical, they've achieved so much already (e.g. import-export of blogs to allow backup etc, embedded comment form, Star ratings, Webmaster Tools Verification, spiffier Dashboard, hooray to all.)

1. Post editor changes (already blogged)

What I said. In particular, more hotkeys and a clearer indication that an attempted save has or has not worked.

2. Image posting and management

I've posted about some image posting issues in my comments on the new post editor.

It would also be good to have better Picasaweb integration. When you upload images to Blogger, they're stored behind the scenes at Picasa Web Albums in a single "album", and you can login there with your Google Account details to manage your Blogger pics. But, you have to login there to do that. I'd love it if there was an "Images" tab in Blogger, which would take you straight to a management page for your uploaded JPEGs, GIFs etc.

What I'd like to see there (or at least in Picasa, if it can't be integrated so fully yet), is the ability to:
  1. get a reverse chronological display of all your uploaded Blogger photos etc
  2. find all images associated with a particular post
  3. with one click, get a list of all the uploaded "orphan" pics which aren't actually linked to in any posts at all (I've done that, uploaded a pic, decided it wasn't good enough, uploaded another one, not got around to deleting the original pic from Picasa even though I deleted the link to it in the post; and it's still there, using up my precious limited space on Picasa, but some time later I can't figure out which is which)
  4. add pics from there to the new "floating window" for images, so I can use an already uploaded pic in a new post (I'm not the only one who wants to be able to reuse previously-uploaded images more easily)
  5. select a pic and get a list of links to all posts on my blog that display that pic?
  6. if I try to delete a pic from there, warn me which posts use that, if any, and make me confirm the deletion (and give me a link to those posts so I can delete them too if I wish).
Other wishlist items for image uploads - ability to upload and host .ico files for favicons and animated GIFs that work.

3. Comments and backlinks management and spam

Inline comments are a major advance for Blogger, people have been asking for it for years; and though it was a while ago that they released it, I think the ability to add your own comment form message is very helpful. But there are other areas which could also benefit from some attention.

Commenter's URL - if the blog owner has chosen to allow anyone to comment, they can choose "Name/URL" to identify themselves if they wish. Now though the URL box is optional, it only works properly if the commenter enters the URL with the initial "http://" e.g. http://www.consumingexperience.com/.

If they enter e.g. www.consumingexperience.com, the comment still publishes but with a non-working URL which, if you try to click on it from the post page, will produce an error message. So either the URL box should say "(optional - please enter http:// at the start)" or, better, it should be changed so that Blogger checks to see if the commenter has entered "http://" and, if they haven't, adds it for them.

Comment moderation and spam comments - if you allow the Name/URL combo for commenters (Settings, Comments, Anyone can comment) and choose to moderate comments, the comment moderation tab doesn't show the URL entered by the person commenting; here's a screenshot I took last year but it's still the same now:


If you choose to receive emails alerting you to new comments for moderation, those emails are slightly better in that they include the link to the Blogger profile of the commenter (if they chose to comment under that account); but if they've used Name/URL, there is no indication of the URL they entered in the email either:

Thing is, it would be very helpful to see the URL they've used before I decide to publish or reject the comment, because I can usually tell from the URL whether it's spam or not. So yes, I'd really like it if Blogger would include that URL in both the comment moderation tab and comment moderation emails.

Backlinks are another source of spam. I think I get more backlink spam than genuine backlinks. But, it's impossible to check the backlinks on my blog without going to each individual post and scrolling to the end to see what the backlinks to that post are. So I don't do it unless I happen to be looking at the post for another reason. Most of the spam backlinks are still there. If there was a centralised place where I could monitor all backlinks and which posts they were associated with (yet another a new tab?), or get notifications of new backlinks etc, it would be much easier to deal with. I'm seriously considering turning off backlinks altogether because of the difficulty of managing them from one place.

4. Stats

I won't say anything on this as I know integrated analytics for Blogger users via Measure Map is coming, hopefully soon, to a blog near you!

5. Dashboard

Previously I couldn't figure out how they display your list of blogs, if you've more than one Blogger blog.

It's great that in the dashing new Blogger in Draft dashboard your blogs are listed in reverse chronological with the ones you most recently posted to at the top.

Still, it would be nice to have an option to show the blogs in alphabetical order by displayed name, if the individual blogger wishes.

6. Template editing - meta tags

Sometimes you want to add code in the head section of your blog template e.g. a meta tag for verification purposes, or extra CSS. Those of us who are happy with HTML can do that, but it's daunting for beginners.

It would be great if there was an easy way for Blogger users to add code to their header section without having to delve into the template itself. Say a popup box into which the code could be pasted, and automatically be added to the head section?

Blogger: new Post Editor - issues





It's great that Team Blogger are continuing to work on improving and upgrading the Blogger Post Editor, in Blogger in Draft - and they've done an excellent job, with loads of new features like improved image handling.

There are just a few issues I've noticed which I hope they'll fix or address before they roll it out for all Blogger blogs.

A. Major post editor issues (Firefox 3.0.1)

  1. Greasemonkey is broken. Wail. (Any chance of a Blogger Greasemonkey API like the Gmail Greasemonkey API, pretty please?) This is a real biggie as far as I'm concerned. I've been loyal to Blogger since day 1, I like its ease of use combined with control and flexibility behind the scenes for power users, but I can't do without my Greasemonkey scripts for:
    1. making the display font more readable in the Blogger Edit HTML editor (my eyesight's not brilliant, every little thing like a better font really helps - I'm not talking about the font shown in the final published post, but the font used when I'm creating or editing a post)
    2. enlarging the Blogger post editor (ditto, plus saves scrolling, plus not having the post editor box fill the whole screen makes me feel very lopsided!) - I know you can set the size vertically and it'll save it per blog, but I really want it to expand to max out horizontally, and I'm not the only person wanting a bigger editing box!
    3. ensuring draft posts are published with the date/time of publishing, not when the draft was first created (keep current time script)
    4. creating tags, and
    5. enlarging the Blogger template editor.

  2. Ctrl-shift-a to add a link has stopped working, oh woe is me!

  3. Ctrl-shift-p needs fixing - currently, it publishes rather than previews a post, at least on my system (Firefox 3.0.1).

  4. Images - you have to upload multiple JPGs, GIFs etc one by one in sequence now if you have several picture or photo files; to me this is a very retrograde step:


    I much prefer the existing system where you can click to have up to 5 files to upload in one go; in fact personally I'd like the 5 boxes to "Add another image" always be there, open (or allow users to save their preference as to how many boxes be available). Not being able to upload multiple image files in one go is actually one of the few things that would push me to switch to WordPress.

    I do like the fact that you can more easily change the size of an uploaded image by clicking it to get a choice:


    - and it's excellent that you can position it right, left or center just by dragging it (I used to do it by editing the code). But I'd like to know if choosing "Remove" not only removes it from the post, but also from PicasaWeb behind the scenes (thus not unnecessarily using up your image storage space quota).

    Also while it's good that you can add a pic at the cursor position by clicking the pic and then Add Image, if you forget to add an image which is still in that window, and you save the post to go back to editing it later, you'll have to upload the pic all over again - the "floating window" with the pics in it just doesn't get saved. The good thing about the old system was that your pics were always there in the post, you couldn't fail to add or save them. Finally, of course, I'd like keyboard shortcuts for adding pics.

    Finally, to move an image I used to copy it (click on it and ctrl-c), place the cursor in the new position and then paste the image (ctrl-v) exactly where I wanted it, at the cursor. You now have to drag it, which is less accessible for keyboard users who have difficulty with the mouse - it really isn't that easy positioning it exactly with the mouse if you have trouble with fine muscle control, or even if you don't - I managed to position 2 pics 1 on the left one on the right on the same line, then dragged one away, but then couldn't get them back to one on the left one on the right again! (yes you could copy and paste the code in HTML view, but that's less user friendly). Yes, you can position the cursor then click Add Image to add an image from the floating window - I'm talking about re-positioning an image after it's been added to a post.

    I do hope Blogger will let users save as a preference the old system for image handling if they prefer, but I suspect not. (I'd like Autosave back too, but I know they're working on that.)

    Another suggestion again for better accessibility: when you upload an image, it would be fab if there was a box against each pic where you could enter the ALT text description for that pic. Yes, you can do it by editing the HTML after you upload it, but that extra hassle puts most people off, whereas if you can do it as you upload it, they'd be much more likely to do it.

  5. Confirmation of saving - I make a habit of regularly going ctrl-s to save a draft post to Blogspot when pausing for thought, as I often draft posts in stages, sometimes over months, before I finally publish the post, and I've nearly cried from losing updates to my draft through Firefox crashing. Unfortunately sometimes it's too busy or having a blip, and the attempted save doesn't work.


    Now it says so at the very end of the window, but if I'm in the middle of a post I don't always think to scroll down to check. Sometimes the message is at the top and bottom both:






    - but sometimes it isn't at the top at all, just the bottom, and I wish that the "Draft saved at.." or, more to the point "Saving and publishing may fail!" message would appear above the post editor too (e.g. above the Title box), or instead of at the bottom, so that you can't possibly miss the fact that it's not saved at the Blogger end and you ought to copy and paste the HTML locally to make sure you don't lose your hard work:


    I've even had instances where I got a "Draft saved at.." confirmation, then when I went back in to Blogger the next day to continue working on the post, it had not saved the latest version, but a previous one. Go figure...

  6. Draft posts should bear the date of publication, not the date the draft was created - this is the issue I've fixed with A.1.3 above, but I think it's a major issue for the many people who write draft posts without immediately publishing them, and I wish Blogger would build it in natively - especially if they're going to stop existing Greasemonkey scripts from working!

  7. Strange bug which wipes out saved content - this has only happened to me a few times, but enough to make me scream. I go to edit a previously saved draft post, the content displays for half a second, then the post editor window (though not the title) totally blanks out in both Edit Html and Compose view. The only solution is to quickly leave that screen fast, WITHOUT saving, before it auto-saves a blank that overwrites my previous text, and then I have to finish my post in Internet Explorer. Otherwise, a blank wipes out all my carefully-drafted previous text. I've also had this happen spontaneously while I was in the middle of drafting something and went back to the post editor tab, not just when trying to go back into a previously saved draft. It's only in Firefox. Is it just me, has anyone else experienced this?

  8. (Incidentally, about the same time as they rolled out the experimental post editor, the "live" post editor must have been updated too, a bit - the Blogger keyboard shortcuts for nested lists have stopped working! Though they work in the Draft post editor. Plus, ctrl i and ctrl b sometimes don't work, and sometimes they do - especially if I combine the two i.e. adding bold to italicised text. And the Save Now button sometimes works like ctrl-d, save & exit, rather than ctrl-s, save but leave the editing box open.)

B. Other post editor issues - wishlist

  1. Keyboard shortcuts - as I've previously blogged, being a keyboard shortcut fan (and I'm not the only one!) I'd love to have more hotkeys, especially:
    1. hotkey for toggling between Edit Html and Compose view (and for immediately interpreting any raw HTML you type or paste in Compose view without having to switch to Edit Html and back)
    2. ctrl-shift-l for a bulleted list (unordered list), and something else for numbered lists.

  2. The Post Editor's Post Options settings are useful and take up little space, I personally feel they should be shown by default, not hidden. Greasemonkey lets me keep that bit permanently open, but again I don't know if that'll last...

  3. HTML anchors - I'd like to be able to add "a name" anchors like <a name="1"&glt; in the body of my posts for reference/linking within the post, while I'm composing a post, as many of my posts are long. At the moment, if I try doing that, it doesn't work on publishing: a link to #anchorname doesn't automatically get converted to insert the post page's permalink but to "http:///#anchorname" or to the editing page. I have to edit the post after it's published in order to get that to work. Maybe there's another way I don't know...
I've other wishlist items for Blogger too, unrelated to the post editor, which I'll write about separately.

Monday, 21 July 2008

Blogger: how to add email address to feed





How do you include your email address in your feed, if you're using Blogger? (See my intro to feeds for beginners if you're new to feeds.)

THE QUICKIE

To show your proper email address in your feed (as opposed to noreply@blogger.com), in your Blogger profile tick "Show my email address", save - and your feed will thereafter display the email address entered in your profile's Identity section.

THE LONG & SLOW

Your blog's feed can potentially list your email address. That can be useful for things like Feedburner's FeedFlare, which lets you add an "Email The Author" link to each post in your feed (as opposed to your blog webpage) so that a feed subscriber can click the link to, you guessed it, send you an email.

But previously, there was no point in Blogger authors activating "Email The Author" in FeedFlare, because any attempt to do so only sent subscribers' attempted emails to the black hole that is "noreply@blogger.com" (and it certainly won't reach you!):


However, a recent upgrade to Blogger ("Blog feeds optionally include your email address") means that you can now display your correct email details in your feed, and even add "Email The Author" links to your Feedburner feed if you want to (but there are downsides, as I'll come to).

It's optional. So, how do you take up the option to include your email address in your feed?

How to display your email address in your feed

  1. Sign in to the Blogger Dashboard.
  2. Click "Edit Profile" on the right.
  3. Under Privacy, tick "Show my email address" - this means whatever email address is entered in the following Identity section of your profile will be used:
  4. Scroll to the end and click "Save Profile".
This adds your email address to your feed behind the scenes:

How to activate Email The Author in FeedFlare

  1. Sign in to your Feedburner account.
  2. Click the name of the feed you want to add the links to,
  3. Click the Optimize tab.
  4. Click FeedFlare on the left.
  5. Against "Email The Author", tick the "Feed" column:


    (you can tick the box under the "Site" column too if you display FeedFlares on your blog webpage and want the email links to be visible there, but you may not need to if you're on Blogger as choosing to show your email address will display it in your Blogger profile, which can be reached through your sidebar if you've chosen to display your profile.)

  6. Scroll to the end, click Save or Activate.

Then, in your Feedburner feed you'll see a new "Email The Author" link:

- and subscribers can click it to email you:


What's the downside?

The way Blogger have currently set it up, it's all or nothing: if you tick the box to show your email address, then your email address also shows on your profile page (when you click View from the Dashboard, or the "View my complete profile" link from your blog sidebar), not in just your feed:



Now I do give my email address in my blog sidebar anyway, but I've done it in such a way that (hopefully!) spammers can't harvest it. The way the email address is displayed in your Blogger profile makes it much easier for spambots to grab your address. UPDATE: it's entirely my bad, Team Blogger are entitled to one free spanking (just one, mind!) - Blogger do obfuscate the email address with Javascript, adding extra stuff to the address to fool the spambots; a dedicated spammer could theoretically figure out exactly what they're doing and strip out the extra bits, but they would have to be targeting just Blogger profile addresses, which seems unlikely.

Personally I'd have preferred it if Blogger had provided a new section in the Edit Profile page where you could fill in an email address just for the purposes of displaying it in your feed, but could choose not have it displayed in your Blogger profile (if you wanted that).

Also, if you have more than one Blogger blog, there's no ability to display a different email address for each blog - you have to use the same email address for all of them.

So, I've not ticked that box in my Blogger profile, myself - but of course, it's up to you what you want to do for your own blog.

PS. of the other new Blogger features, I can say "Bagus, terima kasih Team Blogger!" but I've absolultely no idea what "spam interstitials" are. Can anyone please enlighten me?

Sunday, 6 July 2008

Blogger: unofficial feed FAQ





Here's a guide to some fundamental feeds info for bloggers who use Blogger / Blogspot.com blogs or just people who read Blogger/Blogspot blogs, with some explanation for beginners in the middle, a few tips and tricks on using query parameters, and a quick reference guide at the end.

You can use this info not only in relation to your own blog, if you're a Blogger user, but also in order to view the feeds of other Blogger blogs that you read, in a way that better suits you - e.g., knowing the tricks I'll show you, you can -
  • read the last 100 posts on the Googleblog on one page, even though they're no longer in their default feed and the default feed only shows 25 posts
  • check the 10 most recently updated posts on a particular Blogger blog (as opposed to the 10 most recently published posts)
  • view, in summary or excerpts format only, all posts with a particular label from a particular Blogger blog
  • (UPDATE:) submit sitemaps of your entire Blogger blog, including all your old posts, to the search engines to make sure they index your blog comprehensively
  • ensure Feedburner always shows to your feed subscribers just your most recently published posts, not old posts you've recently updated.
Note: to view the examples quickly, just click the link in Firefox. IE isn't so reliable for viewing feeds.

I start with some exposition for beginners.

What are feeds, news feeds or newsfeeds, web feeds, RSS feeds etc?

Same difference, mostly. See my introductory tutorial guides on What are feeds (including Atom vs RSS); How to publish and publicise a feed, for bloggers; How to use Feedburner; Quick start guide to using feeds with Feedburner for the impatient; and Podcasting.

Blogger feed basics

Blogspot, custom domain, ftp. You can publish via Blogger in 2 different ways. What can be done with your Blogger feed will, for some things, depend on which method you use:
Your public feed. Your feed is only publicly accessible if (1) you've enabled the feed in your blogs settings, and (2) your blog is not a private blog (private blogs don't have public feeds). All public Blogger blogs (whether blogspot, custom domain or published via FTP) with enabled feeds will always have publicly accessible feeds stored at blogger.com.

Feed content.
Blogger users can have separate feeds for posts, comments, and per post comments (i.e. a feed containing all comments made on one particular post only). You can even have feeds for labels.

Feed length/type.
You can set your feeds to either Full, Short (summary), or None. (More on full vs. short i.e. partial/excerpts/summary feeds.) This can be done separately with the posts feed, the comments feed and also the per-post comment feeds.

The basic Blogger feed address URL formats are summarised in the Blogger Help.

Posts feed address

Whichever way you publish (blogspot, custom domain or ftp), your feed will always be accessible at:
  • Atom feed
    http://www.blogger.com/feeds/BLOGID/posts/default

  • RSS feed
    http://www.blogger.com/feeds/BLOGID/posts/default?alt=rss
- first changing BLOGID to your blog's unique ID on Blogger, of course (how to find out a Blogger blog's blog ID?).

This URL works even if the blog's feed has been burned through Feedburner.

Example - Kirk's blog feed is at http://www.blogger.com/feeds/20460175/posts/default; and this blog's feed can be found at

Note
and tip. If you publish via ftp, the above URLs are for a separate copy of your feed which is stored on Blogger's servers, not the URL for feed files stored on your own server, of course. So an FTP-published blog has an accessible feed on blogger.com (as long as it's not a private blog) as well as its own posts feed on its own domain/servers (uploaded by Blogger when publishing, as full or summary depending on the blog owner's settings).

Feed length or type. The "default" in the URL is essential (if you try just http://www.blogger.com/feeds/20460175/posts/ for instance, you'll get an error message). What's it for? The "default" simply means, show this feed in whatever version has been set as the default on that Blogger blog's feed settings - if the blog owner has set it to output a full feed, the http://www.blogger.com/feeds/20460175/posts/default URL will show the full feed; but if the owner has set it for a short feed only, "default" shows a feed with only excerpts.

So here's the first trick. If the blog owner has set their default feed as "full", but you only want to see an excerpts feed or partial feed, you can get it by tweaking the URL.

Examples

This blog is set to output a full feed by default so http://www.consumingexperience.com/feeds/posts/default gets you a full feed. To get a short feed instead, use http://www.consumingexperience.com/feeds/posts/summary.

To get my summary feed in RSS format, you'd use http://www.blogger.com/feeds/8849059/posts/summary?alt=rss (note that http://www.consumingexperience.com/feeds/posts/summary?alt=RSS doesn't work. Note that if trying these tricks using the custom domain of a Blogger blog doesn't get you anywhere, the Blogger.com version using the blog ID in the URL will always work, as should the blogspot.com version of the custom domain blog, if any.)

This tip lets you get a summary feed from a full feed, but not vice versa. If you try to get a full feed from a blog which has been set to output only a short feed, you'll only see an error message like "The feed specified by [url] is not enabled". You can cut down, but not expand beyond, what the blog owner has chosen to allow.

Posts feed address - Blogspot or custom domain alternative feed address

If your blog files are hosted on Blogspot, i.e. it's a blogspot.com or custom domain blog, your feed's web address will also always be at:
  • Atom feed
    http://BLOGNAME.blogspot.com/feeds/posts/default
    or

    http://CUSTOMDOMAIN.com/feeds/posts/default

  • RSS feed
    http://BLOGNAME.blogspot.com/feeds/posts/default?alt=rss
    or

    http://CUSTOMDOMAIN.com/feeds/posts/default?alt=rss
- again first changing BLOGNAME to your usual blog name or CUSTOMDOMAIN to your custom domain, of course
(Alternatively you can think of it as adding "/feeds/posts/default" etc after the end of your usual blog URL).

Note. Even if you use a custom domain, you're still hosting your blog files on Blogger/Blogspot behind the scenes, so the blogspot.com feed addresses will also work. If you changed to a custom domain and kept your old blogspot.com address, you can use that. (Can't remember your old blogspot.com address? In the Blogger dashboard, Settings, Publishing, click Switch to: blogspot.com to see your Blog*spot address; but do not Save Settings, just close or back out of that page!)

Note. For backward compatibility with Old Blogger, for non-FTP blogs you can also get a feed at
http://BLOGNAME.blogspot.com/atom.xml
or

http://CUSTOMDOMAIN.com/atom.xml
(or the RSS equivalent if you change "atom.xml" to "rss.xml"). However you should move to using the above URLs, going forward.

Examples

ACE's RSS feed can be found at several URLs:
http://www.consumingexperience.com/feeds/posts/default?alt=rss
http://consumingexperience.blogspot.com/feeds/posts/default?alt=rss and
http://www.blogger.com/feeds/8849059/posts/default?alt=rss

While for Kirk's default Atom feed, you can use any of these URLs:
http://www.blogger.com/feeds/20460175/posts/default
http://phydeaux3.blogspot.com/feeds/posts/default
http://phydeaux3.blogspot.com/feeds/posts/summary
(Since his feed is set to "short" in his Blogger settings, the "default" URL will go to his summary feeds, and no full feed will be available.)

Or
http://phydeaux3.blogspot.com/atom.xml
http://phydeaux3.blogspot.com/rss.xml
(available, but you should transition to the new feed URL formats.)

Comments feed address

As with posts, the blog comment feed (a feed for all comments made on all posts) for a particular Blogger blog can be set to Full, Short or None, and you can only access the comment feed of a blog if it isn't a private blog.

To work out the URL for the comments feed of a Blogger blog, it's exactly the same as for posts feeds, including the ability to get full or summary comments feed - except you just change "posts" to "comments" i.e.
http://www.blogger.com/feeds/BLOGID/comments/TYPE

and, for non-FTP blogs only, alternative additional URLs at
http://YOURBLOG.blogspot.com/feeds/comments/TYPE or
http://CUSTOMDOMAIN.com/feeds/comments/TYPE

- where of course you should first change BLOGID, YOURBLOG or CUSTOMDOMAIN to the one for the blog you want, and change TYPE to the length of feed you want to get i.e. default, summary or full.

Note: for FTP blogs, the only way to access the comments feed is through the blogger.com address - currently, no comments feed is uploaded to an FTP blog's own servers, only the posts feed is uploaded.

Examples

The summary Atom feed for all comments made on my blog can be reached via:
http://www.consumingexperience.com/feeds/comments/summary
http://consumingexperience.blogspot.com/feeds/comments/summary or
http://www.blogger.com/feeds/8849059/comments/summary

The full feed for all comments on this blog:
http://www.consumingexperience.com/feeds/comments/full
http://consumingexperience.blogspot.com/feeds/comments/full or
http://www.blogger.com/feeds/8849059/comments/full
(or changing "full" to "default" would also work as this blog outputs a full feed as default.)

And one way to get the RSS feed for all comments in summary form only:
http://www.consumingexperience.com/feeds/comments/summary?alt=rss

Per post comment feeds

Per-post comment feeds, i.e. a feed of all comments made on one particular post only, are again available only if the blog owner has turned on per-post comment feeds (I turned mine off, for instance), and it's not a private blog.

To get the URL of a per-post comment feed, use the URL as for the main comment feed, but add the ID of that post after "/feeds/" e.g.:
http://YOURBLOG.blogspot.com/feeds/POSTID/comments/TYPE

Two ways to find out the post ID:
  • as mentioned in the Blogger Help, if the blog owner is logged in to the Blogger Dashboard, in the Edit Posts view (making sure Published or All is selected if necessary), just mouseover the 'Edit' link next to a particular post, and its postId will be displayed in the browser's status bar as the number just after the "postID=" bit - or

  • if you're not the owner of a Blogger blog but want to find out a post ID, and they've enabled "Email this post to a friend" or similar (the envelope icon , usually at the end of the post - Dashboard>Settings>Basic>Show Email Post links set to Yes), just hover over that link. Again the postId will be the number after "postID=". (If there's no such link because it's not been enabled, I'm not sure how you'd find out the post ID.)
Example

To get the feed for all comments on Frivolous Fragments' post on heroic materialism (whose post ID is 3253976247961230387), I'd use one of these URLs:
http://frivolousfragments.blogspot.com/feeds/3253976247961230387/comments/default or
http://www.blogger.com/feeds/5281402533658280011/3253976247961230387/comments/default (as I can tell the blog ID from viewing source on that blog).

Label feeds

Feeds for labels are available as well (if the posts feed has been enabled on the blog and it's not a private blog).

Unlike comments and per-post comments feeds, you can't set feeds for labels separately. Labels are a subset of posts, and as such take on the same settings enabled for posts (full or short).

You access a label feed by taking the post feed URL, adding "/-" and then "/labelname". Again, with ftp blogs you can only access the label feed at the blogger.com URL.

Example

Here's 2 ways to access the feed for the label "Blogger" on Kirk's blog:
http://www.blogger.com/feeds/20460175/posts/default/-/Blogger
http://phydeaux3.blogspot.com/feeds/posts/default/-/Blogger

Or to get all posts labelled "consumer" on this blog, in summary format only (not the full post):
http://www.consumingexperience.com/feeds/posts/summary/-/consumer

Note. Label names are case sensitive (so to find all posts labelled "food" don't use "Food"), and label names should also be URL encoded for any special characters. In other words to get a feed for a label whose name includes a special character like "bits&bobs", you need to make it "bits%26bobs". So look up the % substitute or use a converter for any special characters which appear in the label name, namely: ! * ' ( ) ; : @ & = + $ , / ? % # [ ]

Multiple labels ("and" label search). You can even query for multiple labels by adding the additional label name with a slash ("AND" operation ), e.g.
http://phydeaux3.blogspot.com/feeds/posts/default/-/Blogger/Google
will return posts labeled both Blogger and Google but not posts that have only been labelled "Blogger", or only labelled "Google".

Labels do not currently support an OR operation - although the base Google Data APIs do, so it may become available on Blogger one day. (If it does it most likely will be done with a | character (URL encoded to %7C) between the label names.)

Query parameters - tips & tricks, the fun stuff!

Blogger feeds on blogspot and at blogger.com both now support a wide range of useful query parameters. Most won't be that useful to the basic blogger, but some are. And many will be useful if you like to play with your feeds.

"Query parameters" may sound like gobbledygook if you're a non-geek but bear with me until the examples at the end (just ignore the developer-y bits) and you'll see that it's quite straightforward and potentially very handy to know how to use them.

To use a query parameter, you first append a question mark (?) to the end of the feed URL you are requesting (make sure there is no slash \ immediately before the ?), and then add the appropiate query in a name=value format. You can use multiple query parameters, separating them with an ampersand (&). It doesn't really matter in what order the query parameters are added.

I'll just list all of these in a table, and I'll give some working examples at the end. The first column is the parameter name, the second is valid values with defaults and notes about their usage.

Note. Again, query paraments will only work with the blogger.com URL, for FTP blogs (whereas for custom domain or blogspot.com blogs they'll just work). Also note query parameters won't work with atom.xml or rss.xml feed URLs.

Name Value
alt
atom Will return output in ATOM 1.0 Format (wikipedia) (THIS IS THE DEFAULT)
rss Will return output in RSS 2.0 Format (wikipedia)
json Will return output as a raw JSON (wikipedia) object
json-in-script Returns JSON object in a javascript function - use the callback parameter to
specify the function name
callback
name of functionUsed with the json-in-script alt parameter to specify the name of the callback function
This parameter has no defaults
orderby
updated Returns the feed sorted by last updated status
published Returns the feed sorted by published date (THIS IS THE DEFAULT)
start-index
integer Sets the number of the first entry to be returned. The default is 1
max-results
integer Sets the maximum number of entries to be returned.
The default is 25. Most Blogger feeds currently are throttled at an upper limit of 100 though sometimes I've been able to get 500 posts in one feed
published-min published-max
Date in RFC 3339
format
These set boundaries on the results returned by published date. The lower bound is inclusive. The upper bound is exclusive. Like everything it should be URL encoded. Unencoded example 2007-05-03T23:59:59-05:00 (see RFC 3339 para 5.8 for more examples)
The same URL encoded is 2007-05-03T23%3A59%3A59-05%3A00
updated-min, updated-max
Date in
RFC 3339
format
The same as the above, only the boundaries are set by "last updated" date

Examples

To see the 10 posts in this Blogger blog which have been most recently updated (not the 10 most recently published posts), use e.g.:
http://www.consumingexperience.com/feeds/posts/default?orderby=updated
(You'll see that this is quite different from the posts I most recently published
http://www.consumingexperience.com/feeds/posts/default?orderby=published)

To view the last 30 posts from the Google Public Policy blog, even though it only has 12 posts on the main page and the default number of posts output in a Blogger feed is 25, try:
http://googlepublicpolicy.blogspot.com/feeds/posts/default?max-results=30

If I've been offline for a few months and want to see just the posts published on Kent's blog since 18 January 2008, I'd use:
http://www.blogger.com/feeds/5523094/posts/default?published-min=2008-01-18T00%3A00%3A00&orderby=published
(to view posts published between 2 dates, I'd add "&published-max=" for the upper bound).

To view a Blogger blog's feed starting at the 5th entry in the feed (i.e. not the latest post in that blog, but the 5th latest post), and return just the next 5 results, in a JSON object with a callback function named outputFeed, the URL would be
http://phydeaux3.blogspot.com/feeds/posts/default?alt=json-in-script&callback=outputFeed
&start-index=5&max-results=5

Even more information (non-geeks can ignore)

OpenSearch elements

Blogger feeds return 3 OpenSearch (Wikipedia) elements in the feed header (location varies depending on format type)
  1. openSearch:totalResults - the total number of results in the query (not necessarily the number returned in that feed)
  2. openSearch:startIndex - the index number of the first search result returned in the query
  3. openSearch:itemsPerPage -the number of entries returned from the query
Possible uses: find out the total number of posts and/or comments in a blog.

Rel links

Blogger feeds also return several link elements with rel attributes in the feed header.
  1. self - <link rel="self" type=" ..." href="..."> Link pointing to the query returned. Type and href will depend on the query requested
  2. next - <link rel="next" type="..." href="..."> Link pointing to the next set of results if the results are chunked (more results than the max-results set)
  3. previous - <link rel="previous" type="..." href="..."> Link pointing to the previous set of results from a chunked query result
Uses: can be used to paginate through a long list of results

Secret feature - post feeds are podcast enabled
The API now also supports adding enclosures to a post (a link element with the rel="enclosure" set and a valid URL with mime-type and optionally a content length set). This can only be done via the API as of now, but support in the Blogger posting interface should come at some point. In other words, unless you know how to post via the API you can't use it yet, but it's there waiting for the Blogger interface to use and feeds can start returning them attached to each post entry now.

REFERENCE GUIDE to Blogger feeds and feed URLs

Basic structure of feed URLs -

http://www.blogger.com/[POSTID/]feeds/BLOGID/CONTENT/TYPE[/-/LABELNAME1[/LABELNAME2]][?alt=&orderby=&max-results=&...]

plus alternative additional URLs for non-ftp blogs only -
http://BLOGNAME.blogspot.com/feeds/[POSTID/]CONTENT/TYPE[/-/LABELNAME1[/LABELNAME2]][?alt=&orderby=&max-results=&...] or
http://CUSTOMDOMAIN.com/feeds/[POSTID/]CONTENT/TYPE[/-/LABELNAME1[/LABELNAME2]][?alt=&orderby=&max-results=&...]

where:
CONTENT is posts or feeds
TYPE is full or summary or (is full or summary depending on how the blog owner has set it) default
POSTID is optional and only used for per-post feeds, in which case CONTENT must be comments for it to work of course
(Update: forgot to add info for label feeds before, sorry) /-/LABELNAME1 is optional, add it only when you want to get the feed for a particular label called LABELNAME1 (NB case-sensitive), in which case CONTENT must be posts for it to work. If you add /LABELNAME2 it will find only posts that have both labels

and optional parameters at the end:
alt=rss for the RSS feed (default is Atom)
orderby=updated (default is published)
max-results=number (default is 25, maximum seems to be 500)
Other query parameters are possible, as mentioned above.

Posts feed

Atom feeds
http://www.blogger.com/feeds/BLOGID/posts/TYPE

and alternative additional URLs for non-ftp blogs only -
http://BLOGNAME.blogspot.com/feeds/posts/TYPE or
http://CUSTOMDOMAIN.com/feeds/posts/TYPE or

historical only - ideally don't use -
http://CUSTOMDOMAIN.com/atom.xml or
http://BLOGNAME.blogspot.com/atom.xml

- where TYPE (which is non-optional) can be default, summary or (if full feed has been enabled by the blog owner) full. (How to find out a Blogger blog's blog ID)
RSS feeds
Just add "?alt=rss" at the end of the above URLs e.g.
http://www.blogger.com/feeds/BLOGID/posts/TYPE?alt=rss

or change "atom.xml" to "rss.xml" in the above examples e.g.
http://BLOGNAME.blogspot.com/rss.xml

Comments feed

As above, but change "posts" to "comments" (and add ?alt=rss at the end if you want an RSS feed) i.e.
http://www.blogger.com/feeds/BLOGID/comments/TYPE
and alternative additional URLs for non-ftp blogs only -
http://YOURBLOG.blogspot.com/feeds/comments/TYPE
http://CUSTOMDOMAIN.com/feeds/comments/TYPE

Per-post comment feeds

As for comments, but add "/postID" before "/comments" where postID is the ID of that particular post (and add ?alt=rss at the end if you want an RSS feed) e.g.
http://www.blogger.com/feeds/BLOGID/POSTID/comments/TYPE

Label feeds

As for posts, but add "/-/labelname" at the end - NB lTHE abel name is case-sensitive, you can't have summary posts
http://www.blogger.com/feeds/BLOGID/posts/TYPE/-/LABELNAME
and alternative additional URLs for non-ftp blogs only -
http://BLOGNAME.blogspot.com/feeds/posts/TYPE/-/LABELNAME or
http://CUSTOMDOMAIN.com/feeds/posts/TYPE/-/LABELNAME or

To find only posts that have been labelled both with X and with Y (but not posts labelled with X but not Y or vice versa):
http://www.blogger.com/feeds/BLOGID/posts/TYPE/-/X/Y
and alternative additional URLs for non-ftp blogs only -
http://BLOGNAME.blogspot.com/feeds/posts/TYPE/-/X/Y or
http://CUSTOMDOMAIN.com/feeds/posts/TYPE/-/X/Y or

(It's not possible to find posts with label X or label Y, yet)

Query parameters

The most useful parameters for most people are these (stick a ? at the end of the base URL and & in between queries):

orderby=updated (the default is published) - to show feed with most recently updated posts (not most recently published ones)
max-results=figure (up to 500 currently, the default is 25) - to get a Blogger feed with more than 25 posts e.g. if the figure is 50 it'll show 50 posts in the feed
published-min=date-time1 in RFC 3339 format e.g. 2007-05-03T23:59:59-05:00, but URL encoded e.g. 2007-05-03T23%3A59%3A59-05%3A00 (changing each colon to %3A) - for posts published after date-time1; can be combined with &published-max=date2 for posts published before (but not including) date-time2
updated-min, updated-max - similar, but for posts updated after the dates stated.

Example for the official Blogger blog Buzz, whose blog ID is 2399953 - to see the last 50 posts most-recently updated posts from Buzz, in summary form i.e. only the first few characters of each post:
http://www.blogger.com/feeds/2399953/posts/summary?orderby=updated&max-results=50

Note: doesn't work for FTP blogs unless you use the blogger.com URL. If something doesn't work with the custom domain or blogspot.com domain URL, it will work with the blogger.com one.

Resources

Blogger Help
Blogger Buzz
Blogger Data API
Google Data API in particular query requests
Blogger Data API Group
JSON Inspector

Acknowledgements

This post wouldn't have been possible without the sterling work of Kirk, on whose draft I based it. Though I've made it a whole lot longer... Thanks, as always, Kap'n Kirk!