Interesting stats:

• 21 web services analyzed
• 10 (48%) are using OAuth (including YouTube)
• 5 (24%) are using AuthSub (also including YouTube)
• Dopplr is the only non-Google property using AuthSub
• Tumblr is the only property using plaintext passwords, although Posterous is using HTTP Basic, which is basically plaintext

Looks like OAuth is gaining some real traction, and in fact if Google switched over to using it, it’d have a real hold on the authentication space. That would probably be a good thing. Next up in my adventure will be seeing how truly conformant/compatible all these OAuth implementations are, and how portable my code be able to be in accessing them all.

If you’d like to add any others that you know about, please throw them in the comments and I’ll add them to the table above so everyone can find them.

I got my most recent copy of the ‘Google Friends‘ newsletter, and towards the end, completely unrelated to anything else in the newsletter, they offer a definition (sort of) of what a Wiki is. They provide a link to Wikipedia and then leave it at that.

Google have already delved into the world of blogs (they own Blogger.com and run their own GoogleBlog), so I guess it was only a matter of time before they got into wikis as well. I wonder where this is going to go… especially since Yahoo! is already an avid supporter of Wikipedia at least (hosting some of their servers).

Turns out that it was because I was reloading webpad in a window which I had previously used it, so the session (containing filenames etc) was still active. When webpad loaded, it was triggering the ‘save’ operation, and saving the now-empty main window as the file I was previously working on. All I’ve done is make it so that you can’t write a blank file now — if you want to delete something, you should be using the delete operation in the file dialog anyway.

One step closer to release! Blogs are still a sticking point tho… how/what to support on Blogger.com/MovableType is the thing holding me up. Complete blosxom support is already in there, and works wonderfully – I’m using it to maintain my blogs and website. The Blogger Atom API sounds really ugly and excessively complex, but I’ll let it stabilise a little more and then have a proper look at it I think…

As Robert discovered in this post, the server that responds to API requests moved from plant.blogger.com to www.blogger.com, so basically I was posting authentication requests to a server that didn’t exist. This has been rectified now and it appears to be operating properly.

Enjoy your blogging folks

This problem appears to have been happening for the last couple days at least, so let’s just hope that Blogger sort it out soon. I wonder if their fancy new Atom API is going to be any more reliable?

In the meantime, sign up to the mailing list to be the first to find out when it’s available and working properly again.

Thanks to those who have emailed me to let me know that it wasn’t working