I've been using the Facebook Comments Box on this blog since I parted ways with Disqus. One issue with the Facebook system is that you won't get SEO credit for comments displayed in an iframe. They have an API to retrieve comments but the documentation is pretty light and so here are three critical tips to get it working.

The first thing to know is that comments can be nested. Once you've got a list of comments to enumerate through you need to check each comment to see if it has it's own list of comments and so on. This is pretty easy to handle.

The second thing is that the first page of JSON returned from the API is totally different from the other pages. This is crazy and can bite you if you don't test it thoroughly. For https://developers.facebook.com/docs/reference/plugins/comments/ the first page is https://graph.facebook.com/comments/?ids=https://developers.facebook.com/docs/reference/plugins/comments/. The second page is embedded at the bottom of the first page and is currently https://graph.facebook.com/10150360250580608/comments?limit=25&offset=25&__after_id=10150360250580608_28167854 (if that link is broken check the first page for a new one). The path to the comment list is "https://developers.facebook.com/docs/reference/plugins/comments/" -> "comments" -> "data" on the first page and just "data" on the second. So you need to handle both formats as well as the URL being included as the root object on the first page. Don't know why this would be the case, just need to handle it.

Last but not least you want to include the comments in a way that can be indexed by search engines but not visible to regular site visitors. I've found that including the SEO list in the tag does the trick, i.e.

I've included the source code for an ASP.NET user control below - this is the code I'm using on the blog. You can see an example of the output on any page with Facebook comments. The code uses Json.net.

FacebookComments.ascx:

FacebookComments.ascx.cs

Not to pick on British Airways but yes, that screenshot is real. It's a marketing email opt out that has not only been pre-populated in favor of spam but has then also been disabled.

Previously.

It has been brought to my attention that I've been whinging too much recently. 

So I'd like to take a break from that and say how much I'm enjoying feedly. It's a wonderfully well designed RSS reader. I use the Chrome Extension version and the Android app. It preserves the Google Reader keyboard shortcuts so I can sail through my subscriptions and it brings back social sharing. 

I looked at feedly once before and didn't really get it. I thought it was just one of those algorithmic recommendation news manglers that tries to guess what you want to read. It might do that on the home page but the 'All' view is a perfect replacement for Google Reader. 

I love it. I want to pay for it to make sure it stays around. Thank you feedly. 

I've been slowly becoming aware that Google Maps is eating up a lot of the power on my phone (an HTC One X with Android 4.1). Yesterday as my battery was near death I saw it was up to 25% of total usage on a day when I hadn't even run the app. Something had to give. I'd already turned off Google Latitude a few months ago so the culprit had to be whatever secret-squirrel location sniffing the phone does behind my back.

Android has about a million different incomprehensible weasily location options. At least in 4.1, I've seen some evidence that 4.2 is a bit better. The bargain with 'Google's location service' seems to be that if you don't send your data to them they won't send it to you. At least I think so, the description changes when you check or uncheck the option. I've had this off for today and my battery has a lot more juice. It means that Google Now doesn't work, but so far that doesn't seem to be a loss. It might hurt other apps as well, but so far I care more about not having a dead phone at the end of the day.

I just discovered that Disqus started running adverts on my blog without permission. It's probably been going on for a little while and I should have paid more attention, sorry.

By 'without permission' I mean that I'm sure I clicked though and didn't read a terms of service document that said they could do what the fuck they like to my site. And reading other accounts of this issue I'm sure I filed without reading the email they sent out that mentioned this new 'feature' in passing. So in a legal sense they probably had all the permission they needed. In a moral sense they're switch-and-bait scum of the highest order. 

They should have made this feature opt-in and then sent out an email explaining it in detail. Some sites don't want to run ads. You could have non-commercial Creative Commons content on a site that is suddenly a commercial concern. 

It's a free service and at some point they need to make money, fine. If this had been presented as an option I might have considered it. If they wanted to charge for the service I'd probably have paid for it.

Instead I've disabled Disqus and hastily hacked in Facebook Comments which should be coming online as I write this post. 

A side effect of this is that all the existing comments are currently unavailable. I have an archive and will try to get them resurrected soon.

(Since writing this post I have also ditched Facebook comments and now have a fully home grown solution that I moderate by hand.)