LQ Wiki reaches 3,000 articles

The LQ Wiki just reached 3,000 articles today. This is a goal we’ve been chasing for a little while. While reaching this goal took slightly longer than I had anticipated, participation at the LQ Wiki has really been picking up lately (which is fantastic). We have a number of very high quality regular contributors and traffic in general has been steadily growing. The recent addition of OpenID should also serve to further encourage participation. If you haven’t contributed yet, head over and take a look. You can choose either the CC by-sa license or the GFDL, so all your contributions will remain freely redistributable. As always, if you have any feedback, do let us know.

–jeremy

We now support OpenID

With the permalink issue resolved, it’s time to start work on improving the blog now. I’m happy to announce that one of the first moves is to support OpenID. You can now comment here using your OpenID account. The LQ Wiki is also an OpenID consumer. If you have any issues or spot a bug, let me know.

–jeremy

The LQ Wiki is now an OpenID Consumer

As promised, the LQ Wiki now allows you to log in using OpenID. You can convert an existing account if you have one, or simply login with an OpenID as a completely new user and start editing. I’d like to thank Evan, whose extension made adding this relatively painless. One thing to be aware of if you are thinking about implementing OpenID (you should be) and are planning to use curl. Some versions deal with RFC 2818 – 3.1 Server Identity differently than others. A snippet:

Matching is performed using the matching rules specified by [RFC2459]. If more than one identity of a given type is present in the certificate (e.g., more than one dNSName name, a match in any one of the set is considered acceptable.) Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com. f*.com matches foo.com but not bar.com.

What does that mean to you? Well, I was using jeremy.lq.myopenid.com to test. In some implementations of curl (7.12.1 in this case), the *.myopenid.com cert works fine for that domain. In other implementations (7.10.6 in this case), you get a error:

certificate subject name ‘*.myopenid.com’ does not match target host name ‘jeremy.lq.myopenid.com’
Just something to be aware of as many of the gratis OpenID providers seem to allow this situation to happen. Hopefully you’ll come across this blog post before banging your head on your desk for 10 minutes wondering why code works in some places and not others.

–jeremy

Quick OpenID Update

A quick follow-up to this post. OpenID has really been on fire the last month or so. Support from the likes of AOL and Microsoft have been announced, a future version of Firefox will likely support it and Yahoo! has a sort of unofficial support for it. As my previous post announced, the LQ Wiki will be the first LQ site to support logging in via OpenID. This should be implemented by next month. After chatting with Evan on the topic at LinuxWorld, I am also considering the possibility of LQ becoming an OpenID server. This would allow you to use your LQ credentials to login to any site that consumes OpenID. One question I have is – is this something people would be interested in? There are plenty of free OpenID services available, so I want to think carefully before proceeding unnecessarily. If you're unfamiliar with OpenID and are interested, you can visit the official site and this simplified explanation. The one main issue I see with OpenID is the potential for phishing exploits, which is well explained here. Hopefully the next revision of the spec will address this issue.
–jeremy

Follow

Get every new post delivered to your Inbox.

Join 3,972 other followers