I’ve been talking about OpenID, and hoping that it catches on so that everyone can use just one login credential to all the sites that are OpenID-enabled. It may or may not affect the user-experience. I guess it depends on how efficient servers communicate with each other. Kyle Neath points out 5 reasons why he would not be implementing OpenID. From what I’ve read, I think he simply disagrees with sites requiring an OpenID, not the ones that are OpenID-enabled. Having OpenID as another option to authenticate yourself is good, but using OpenID ONLY to authenticate yourself is not good. And he raises valid points.
I noticed the latency since last night when I tried logging in and seeing if there were any new amusing twits to while away my time. And just now, 10:13 AM GMT+8, I get this error message:
So what else is new, you might ask.
Well, I have recently tested and deployed OpenID here in the site. I’m not really new with OpenID since I have been using my own domain as my own OpenID with the help of Sam Ruby’s article and phpMyID. However, I haven’t opened up my site for OpenID users registered with other providers, and from what I hear from the open source community, it’s a lot of work.
Fortunately, there’s WP-OpenID, a WordPress plugin that works for WordPress 2.5 (or at least, its latest version). I just installed the plugin like any other WordPress plugin, edited one of the files according to the steps from the support page (because there’s this bug of an error that appears everytime I click on the settings of the plugin), and it now works like a charm. However, I have no idea if it works as it should since I haven’t done other diagnostic tests besides posting a comment using my OpenID, and I didn’t notice any conflicts with other plugins, so if you notice something out of the ordinary, please feel free to leave a comment.
Feeling adventurous? Want to try it out for your blog? Go ahead and give it a try. However, I would suggest that you read the threads and discussions on the plugin’s page. You might run into some issues that were already addressed there. Or not yet addressed. User beware.
So far, so good. But Twitter is still down. Oh wait. It’s up now (10:23 AM GMT+8). Yay. Now what?!
Catching wind from TechCrunch, Microsoft is now trying to befriend the open-source community by releasing 30,000 pages of documentation for Windows. And it’s not all crap documentation. Specifications for Vista, Server 2008, Office 2007, and others are included.
Microsoft is providing a covenant not to sue open source developers for development or non-commercial distribution of implementations of these protocols. These developers will be able to use the documentation for free to develop products. Companies that engage in commercial distribution of these protocol implementations will be able to obtain a patent license from Microsoft, as will enterprises that obtain these implementations from a distributor that does not have such a patent license.
Not yet open-source but Microsoft is starting to embrace the force that is open-source (rhyme unintentional). Or are they really? One can speculate. And Microsoft is doing all this in the name of Interoperability and Data Portability. This may also be in line with their participation in the development of OpenID.
The Redmond giants released this in a form of a promise. But as far as cliches go, promises are made to be broken. I still can’t trust Microsoft. And this move of theirs is just making me more paranoid. I’ll just keep my fingers crossed in the hopes that someday, there will be better interoperability between Microsoft and Open Source software.
It’s been a while since I posted something about OpenID, and I didn’t even give it the focus it deserves. Recently, it has been announced that Yahoo! will be implementing the said open source technology as a way for its 250 million users to signin to OpenID-enabled sites. They are in the process of making it work, so don’t get your hopes up. At least, not yet. Public beta testing will start on January 30th, according to their website. This is great for the OpenID project as it will get the exposure it needs to be embraced by the public.
Anne Zelenka of GigaOM posted an article about WordPress becoming the next social networking profile, which basically makes me think about my blog and it becoming a social network. The article talks about blogs in general, and WordPress as the platform in particular, as a social network. Although it wasn’t mentioned in the article, I’m assuming that they were referring to the WordPress application and not the WordPress.com “free blog” site. Anne did a good job in pointing out the trend that is currently happening in social networking circles.
In case you have no idea what OpenID is, it is a way of managing your online identity in the sense that if you have one, and the site you are visiting supports OpenID and requires you to login to contribute to a discussion, you don’t have to sign-up or register with that site and you don’t have to create yet another username and password for that particular site. All you have to do is use your OpenID and you are automatically in. It basically makes site registration simple by using a universally recognized identification system.
After releasing plugins for WordPress 2.3, that is. I have reached a point in my blog life that I am clueless as to what I can actually share in my posts other than WordPress stuff that might be Greek to most of the visitors. Then again, visitors might be looking for WordPress stuff. But, little has been going on with the development of my plugins, and themes, for that matter. I feel that the plugins are doing what it’s supposed to be doing, and my themes are showing what it’s meant to be showing.
Why did I release those things in the first place, anyway? Well, I was hoping to inspire future bloggers to learn a thing or two about PHP, Cascading Style Sheets, and how WordPress works. And to also show them that if a noob like me can do it, so can they. However, the documentation of my plugins and themes are somewhat insufficient, if not non-existent. When I say documentation, I mean a detailed explanation of how the plugin or theme was developed from scratch.