When Facebook Connect launched over two weeks ago I wrote about their widget policy being overly restrictive. The result was that widgets couldn’t be developed efficiently as users would be forced to upload a cross-domain receiver file after creating the application within Facebook. I was in the process of developing my own widget at the time and was under the impression that the cross domain receiver file must exist on the third-party’s website.
That policy has apparently since changed. Last night Disqus announced that they now support Facebook Connect. The integration is great and I’ve since enabled it on Social Times. Disqus instructs users to simply enter disqus.com as the callback URL when configuring a new application. That means that site owners aren’t actually required to upload a cross-domain receiver to their site.
The result is that with each new widget installation, site owners simply need to create a new application on Facebook. Under the new policy there is one less restriction to getting a widget implemented on your site and it also means that Facebook Connect can be much more rapidly implemented. If Facebook has truly adopted a new policy it also means that we will begin to see many more Facebook Connect widgets implemented around the web.
Facebook could also choose to disable the current implementation of Connect by Disqus. I’m guessing that they won’t and we’ll see many more widgets arrive in the coming days in weeks. If this is in fact a new policy that has been adopted by Facebook, I’m glad that it has been implemented. Users still must connect individually with each site which means that technically no MyBloglog widget could be implemented.
It doesn’t mean that users need an overly complex installation process though which is a great step by Facebook in the right direction.