You may think you’re a big user of FriendFeed, you may think you have heaps of followers and everything you submit gets liked & commented on.  Sorry, that’s nothing.  Google has spoken and the most important FriendFeed members are…

Deepak & Kevin, congratulations.  Google says you’re more relevant than the About page, the FAQ or the public feed.  That’s pretty impressive!

Additionally, if you go the ‘More results’ page you’ll note that the order goes like this:

1. Homepage
2. About
3. Public Feed
4. Scoble
5. API
6. Bookmarklet
7. Blog
8. Louis Gray
9. Changelog
10. Steve Rubel

Hands up anyone who’s surprised to see Robert at number 4?  Anyone, anyone?

For anyone who’s game, and especially for anyone who’s been having problems with the FriendFeed Comments plugin, I’ve just checked in a new beta release that you can download.  It’s not available through the WordPress auto-updater yet because it’s not been tested sufficiently.  So if you’d like to help out you can grab it here: http://downloads.wordpress.org/plugin/friendfeed-comments.1.6.0beta.zip

There aren’t any major visible changes.  There’s a couple of tidy up changes eg. I removed some inline styles that I should have moved into the default stylesheet, but the major changes are behind the scenes.  Some people were having issues with the plugin not retrieving the information correctly and it seemed to be an issue for people with a large number of posts & comments.  So this new version now stores the data in a custom table on your WordPress database.  This should make things much more efficient and hopefully less error-prone.

If you do install the new update you must deactivate & re-activate the plugin, then go to the settings page & click ‘Save Changes’ before it will work.  If you don’t the table won’t be created and it won’t work.

If you can help out with the beta testing it would be much appreciated.

From the Mozilla Developer Centre:

Whenever we’re asked “when is Firefox going to be released” we endeavour to answer to the best of our abilities, but the truth of the matter is that we’ll only ever ship “when it’s ready”. We have a lot of indicators that help us understand when the product is ready for release: feedback from our pre-release milestones, excitement in the community and the press, availability of compatible Add-Ons, and a large active beta community helping us ensure that the release is compatible with all the various sites on the Internet.

After more than 34 months of active development, and with the contributions of thousands, we’re proud to announce that we’re ready. It is our expectation to ship Firefox 3 this upcoming Tuesday, June 17th. Put on your party hats and get ready to download Firefox 3 - the best web browser, period.

Plus the 3rd Release Candidate is out today.  Unless you’re on a Mac you don’t need it though, as it contains only a single change to fix a Mac-only bug that was causing the system to hang or crash at startup or shutdown.

Currently one of the limitations of using the otherwise great comments service Disqus is that it doesn’t allow you to display trackbacks/pingbacks.  Apparently this will be fixed in a future release of the Disqus WordPress plugin, but for now it’s not working.

The trackbacks you receive are still stored locally in your database, despite them not being displayed, so you can access them. However there isn’t a built-in way to access just the list of trackbacks. Trackbacks are stored as comments in the wp_comments table and are identified by a comment_type of either ‘trackback‘ or ‘pingback‘. (For our purposes here, there’s no real difference between the two. For more info on what the actual difference is, see this page) So, if you wanted to you could write up a bit of PHP that pulled all the trackbacks out of the database & displayed them on your blog, but for a lot of people this is a bit much.

If you look on this page (the FriendFeed Comments Plugin page), you can see a list of the trackbacks that page has received. It’s a very simple list, I’m not displaying the text snippet that usually comes with trackbacks, but that’s just personal preference. If you’d like to be able to display your trackbacks without having to worry about writing code yourself I’ve got a really simple plugin that lets you do this here. The plugin adds 2 functions, get_approved_trackbacks & trackbacks_template.  get_approved_trackbacks takes the post id as an argument and returns a list of the trackbacks that have been approved (moderated) for that post. trackbacks_template is essentially an additional template tag to be used in the same way as comments_template() is used on the single.php template file.

So for example, if you wanted to display the trackbacks before the comments, download & install the plugin. Then open up the single.php template file for your site & find the line <?php comments_template(); ?>. Stick <?php trackbacks_template(); ?> on the line above it. This will display the trackbacks as an unordered list inside a div with the id "trackbackslist" with a h3 heading "Trackbacks" above the list. However if you’d like to style it differently, it will also look for a template file called trackbacks.php in your template folder. If it finds that it will use that to render the trackbacks.  This is what I’m doing here so as to not display the trackback text.  By default the plugin will display that too.

Obviously this is an advanced option, and only for those familiar with HTML & PHP.  For those people, the plugin provides a variable called $trackbacks which is an array of comment objects. The code that I’ve used to display the trackbacks by default is contained in a file called ‘trackbacks.php’ in the plugin folder, which you can copy into your template folder to use as a starting point for styling your own list.

Hopefully Disqus will sort out what it’s going to do with trackbacks, according to Daniel from Disqus it’s coming soon.  I’m pretty happy with their service, they’ve been really responsive to any support requests and they’ve had pretty solid uptime.  The lack of trackbacks isn’t really a big deal to me, but I do like to show who’s discussing my posts. As usual please leave comments / bug reports on the plugin’s page.

One of my mates got a new mac & the other day I was having a play around with it. It is sweet.  The UI is out & out gorgeous, no question. It’s intuitive too, I really haven’t used a mac since I was in high school, but it all just worked.  The photo application using the built-in web cam was a lot of fun & the Time Capsule app is really nice (plus its interface, like everything else, is just plain fun).

The new iPhone looks to be much of the same, beautiful design, easy to use software and, soon to be available, lots of third party apps to install.  The ability to sync with Exchange looks to be a really good feature, this puts it in direct competition with the Blackberry.   The new iPhone will finally get 3G networking support too.  A lot of people wondered why this wasn’t in the original iPhone, but none the less it will have it now.  It’ doesn’t have video recording or video calling facilities, and while some may wonder why, I don’t see this as a problem.  Video calling was the original major selling point of the 3G network, but it really hasn’t taken off.  I’ve got a 3G phone & I’ve only ever made a single video call - when I first got it to test it out - but it’s just not feasible to use normally.

This brings me to my point.  The new iPhone will run on the 3G network, but it won’t have MMS or video facilities.  Have a look at the features page, it ain’t there.  It will take photos, and you can email them or sync them with the new MobileMe service, but you can’t directly send them to other mobile phones with MMS.  It’s certainly not a big deal, but this is such a simple feature I’m really not sure why it would be left out.  It seems like Apple doesn’t want it’s users to know that there are other 3G phones out there, it’s the walled garden all over again.

Read the rest of this entry »

Mozilla has released the second Release Candidate for Firefox 3, if you had RC1 installed it would have come as an automatic update, otherwise you can get it from the download page.  The release notes for RC2 are here. 

There aren’t any new features, this is a pure bugfix release. Ironically though, there are more ‘known issues’ in RC2 than there were in RC1 (21 vs 17). 

The final for Firefox 3 is due later this month I believe.