links for 2008-09-12

Links for this article:

]]>

Integrating Disqus and Roller Weblogger on blogs.sun.com

I’ve recently updated my site to use Disqus the blog comment hosting and conversation site.

Done this for two reasons:

  1. Firstly my usually frustration with any status quo means I want more functionality delivered yesterday, and although I’d started to have a look at the functionality I wanted and how I might add it as a Roller macro / velocity code I didn’t want to spend a huge amount of time coding it out (the functionality I specifically wanted was the separation of comments and trackbacks, as well as comment ‘threads’).
  2. Secondly to gain readership and comments from the sizeable blog comment audience that Disqus have built up (Disqus is estimated to be running on over 30,000+ servers).

I’ve already had a couple of comments from Disqus members, and I’ll have to see how it goes before I start heralding it as an unprecedented success, but I’m very pleased with the results (both aesthetic and functional).

Sadly the Disqus comment import function was initially provided for WordPress and Blogger, but apparently wasn’t fully functional; subsequently an update is due out soon that will hopefully include Roller Weblogger. See this Disqus forum entry, and it’s threads for more info: How do I import comments?

Given this was the case I wanted to make sure my blog supported my new Disqus commenting system, but would still show my old comments if there where any for an entry. Here are a few examples:

The code I developed, which has to be separated into two components (number of comments associated with a blog entry, and comment entry form and comment display), is below, but if you use or copy it please note that you need to replace the Disqus supplied JavaScript for my site with your Disqus comments hosted sites JavaScript code. ¨C18C

Combined Roller Weblogger and Disqus Number of Comments code

For comment numbers I’ve broken it down into displaying “n Comments” for Disqus on it’s own, whilst “x Comments (new, via Disqus) and y Comments (legacy, via Roller)” for comments hosted on both systems.

This replaces the code in the Roller Weblogger “_day” template which displays the number of comments per blog entry.

Don’t forget to replace occurrences of ‘eclectic’, my blog handle, with yours (just one, about the fifth line from the end).

## Number of Comments

<a href="$url.entry($entry.anchor)#disqus_thread">View Comments</a>

#set($commentCount = $entry.commentCount)
#if ($commentCount &gt; 0)
    (new, via <a href="https://web.archive.org/web/20090830081824/https://www.disqus.com/" target="_blank">Disqus</a>) and 
    #if ($commentCount == 1)
        <a href="$url.comments($entry.anchor)">$commentCount Comment</a> (old, via <a href="https://web.archive.org/web/20090830081824/https://rollerweblogger.org/" target="_blank">Roller</a>) 
    #else
        <a href="$url.comments($entry.anchor)">$commentCount Comments</a> (old, via <a href="https://web.archive.org/web/20090830081824/https://rollerweblogger.org/" target="_blank">Roller</a>) 
    #end
#end

<script type="text/javascript">
//<[CDATA[
(function() {
		var links = document.getElementsByTagName('a');
		var query = '?';
		for(var i = 0; i < links.length; i++) {
			if(links[i].href.indexOf('#disqus_thread') >= 0) {
				query += 'url' + i + '=' + encodeURIComponent(links[i].href) + '&';
			}
		}
		document.write('<script type="text/javascript" src="https://web.archive.org/web/20090830081824/https://disqus.com/forums/eclectic/get_num_replies.js' + query + '"></' + 'script>');
	})();
//]]>
</script>

Combined Roller Weblogger and Disqus Comment entry and Comments display code

This basically displays the Disqus commenting system, along with any Disqus hosted comments, however if any ‘legacy’ Roller Weblogger hosted comments are found it displays those too.

It replaces the code in the Roller Weblogger “permalink” template which displays comments themselves (the same changes may need to be made to the “weblog” and “searchresults” templates too).

## Comments

<h2>Comments (new, via <a href="https://web.archive.org/web/20090830081824/https://www.disqus.com/" target="_blank">Disqus</a>)</h2>

<div id="disqus_thread"></div><script type="text/javascript" src="https://web.archive.org/web/20090830081824js_/https://disqus.com/forums/eclectic/embed.js"></script><noscript><a href="https://web.archive.org/web/20090830081824/https://eclectic.disqus.com/?url=ref">View the forum thread.</a></noscript><a href="https://web.archive.org/web/20090830081824/https://disqus.com/" class="dsq-brlink">blog comments powered by <span class="logo-disqus">Disqus</span></a>

##showWeblogEntryComments($model.weblogEntry)
##showWeblogEntryCommentForm($model.weblogEntry)

<br></br>

#set($commentCount = $entry.commentCount)
#if ($commentCount &gt; 0)
    <h2>Comments (old, via <a href="https://web.archive.org/web/20090830081824/https://rollerweblogger.org/" target="_blank">Roller</a>)</h2>
    #showWeblogEntryComments($model.weblogEntry)
    <br></br>
#end

Additional benefits that I’ve picked up by implementing Disqus include:

  • Following commentators.
  • Having my, and my sites, comments followed.
  • Being able to easily ‘reblog’ my comments and make blog entries out of them (looking forward to trying this, although I haven’t yet).

Finally here’s my Disqus profile for you to have a look at: https://www.disqus.com/people/wayne_horkan/

Links for this article:

Setting up del.icio.us blog posting on blogs.sun.com

Recently I have received a number of emails about del.icio.us blog posting “links for” working with blogs.sun.com (BSC) or rather not as the case may be, as they have all vented frustration about it not working (either well or at all).

Dave Johnson, the man behind Roller Weblogger itself (the platform BSC runs over), suggests alternative approaches to achieving the same result, most notably using a standalone tool described in “delicious.com Blog Posting tool“.

I was similarly frustrated having just configured the delicious blog posting tool (and getting it to work), however I have since found that the issues I faced were due to not reconfiguring my XML-RPC password after the recent upgrade to the external Identity authentication and authorisation security mechanism used to access BSC.

To get it to work again I had to reconfigure both my BSC and del.icio.us accounts.

Setting up your BSC account for del.icio.us blog posting

First off I had to go into the “Your Profile” page in my BSC account.

Then I had to configure a “Web Client API Password”, as in the screen grab below.

Setting up your del.icio.us account for del.icio.us blog posting

After reconfiguring my BSC account I had to change the user name and password combination in the del.icio.us blog posting settings page.

The user name now needs to be set-up as your email address (and not the old style BSC user name, which matched your blog ‘handle’), whilst the password needs to be configured as the same as the “Web Client API Password” above, see the following graphic for more detail.

Another item to note is that “blog_out_id” needs to be set as your BSC ‘handle’, whilst I’ve found “out_cat_id” has little effect (as the posts default to whatever “Category for posts received via clients” is set to in your BSC blog preferences).

Remember to set “Enable weblog client support?” in your BSC blog preferences to get any of this this to work in the first place.

¨C11C

Since reconfiguring the two accounts above it’s been working consistantly and I feel safe enough to blog about it as a way forward.

I originally found out about setting up del.icio.us blog posting from the blog post “Posting from del.icio.us to Roller” from Lars Trieloff’s Collaboration Weblog. This worked fine until the change to access was implemented at BSC, and would presume it’s advice still holds for the majority of cases (outside of BSC).

¨C12C ¨C13C¨C14C

Links for this article:

links for 2008-09-06

Links for this article:

links for 2008-09-05

Tabs, Used Right: The 13 Usability Guidelines (Jakob Nielsen’s Alertbox) Tabbing advice from a Web Guru… …..

Links for this article:

links for 2008-09-04

Bored of Internetshire By Tim Caynes Simply the best blog I’ve ever seen, Tim Caynes rejection of the Blogosphere. …..

Links for this article:

]]>

links for 2008-08-31

welcome to vue cinemas – the ultimate cinema experience Our other local Cinema – ‘Star City’ in Nechells, although we don’t go too often as it went through a spate of being ‘stabbing central’ at night and hasn’t shaken off that image well so far. ….. 1 Trackback

links for 2008-08-30

Horkan – Hungarian for ‘snort’

I’m not winding you up on this one, check this out from Dictionary.com:

Horkan - Hungarian for 'snort' from Dictionary.com

I should think that a number of you will be more than a little amused.

My banana yellow Yamaha V-Max

And a series of posts about motorbikes wouldn’t be complete without my own current ride, this lovely banana yellow Yamaha V-Max.

www.flickr.com


That’s right, it’s just a big ol’ engine and a pair of wheels, lol…

A pint after work…

Kieron, Darren, Ian and Graham at the Fine Line.

www.flickr.com

Graham Helsby and his *BIG* sandwich

Here’s my mate Graham with a very large sarny…

www.flickr.com


Now that’s a *Big* sandwich…

Three pals bikes; a BSA low-rider, a Yamaha Genesis EXUP Streetfighter, and a mint Honda VFR

Keeping with this weeks motorbike theme, here’s some photos of three pals bikes that I helped them sell on ebay last year.

First up is Bob’s wonderful, but insane to ride (unless you were Bob), BSA ‘Low Rider’.

Second is Martin’s Yamaha Genesis EXUP ‘Streetfighter’ (mainly fairing removed).

Third is a friend of a friends bike, in that’s it’s Ricky’s brother Joe’s bike, an almost mint condition Honda VFR.

www.flickr.com


And yes, they all sold double quick…

Castle Bromwich Hall Church Fete

Our local C of E Church, St. Mary and St. Margaret’s Church, in Castle Bromwich, just before the arrival of our new Parish Priest, Gavin Douglas, and family…

www.flickr.com






What do Facebook, del.icio.us, and last.fm, all have in common this month?

Yes, that’s right; they are all suffering from functionality issues due to design flaws introduced in their last look and feel upgrades.

Looks like this is the month for it, because in rapid succession we’ve seen changes at all three of these web2.0 stalwarts.

So how have these changes effected functionality, and what’s the real problem at hand ?

  1. Facebook
    If your a Facebook user then you will have noticed the option to use ‘new’ facebook, which, although keeps the quite fixed layout (and color theme), moves applications onto a seperate ‘page’ (or tab rather, although it behaves as a page).
    The major problem with this is settings between the new and old Facebook layouts don’t appear to be compatible, which points to access control being about the UI and not about the data itself.
  2. del.icio.us
    So del.icio.us have introduced a ‘richer’ look and feel, but appear to have lost some of their elegant simplicity. A shame, because for a service like del.icio.us I’d rather have function over form.
  3. last.fm
    Similar to the issue with del.icio.us, but in this case their is a huge user community hankering for backwards compatibility with the old look and feel, who want a similar ability to the recent Facebook refresh in being able to ‘swap’ between the two UI designs.
    Perhaps this isn’t such a good idea, because like the current Facebook issues, who’s to know what settings and access controls are locked into the UI and not the user data.

Along with the recent problems at Twitter around “outbound SMS messages” it’s turning out to be quite the month…

Last years photos from Sun’s Customer Engineering Conference 2007 (CEC 2007)

Found these the other day, posted up to Flickr…

www.flickr.com

A visit to the National Motorcycle Museum

Yep, it’s Dad boring the poor kids senseless with the absolutely wonderful National Motorcycle Museum; we live that close that we’ve been so often they’ve only just let me take them there again…

If you like Bikes, no scratch that, if you *LOVE* bikes, then it’s definitely the place for you.

www.flickr.com


And that’s right, I’ve tagged this ‘Heaven’.

Microsoft’s very public “Blue Screen of Death” crash out at the Beijing Olympics

First reported by RiverCoolCool on his blog: https://rivercoolcool.spaces.live.com/blog/cns!D6F05428A2B8CB48!1570.entry

Then by Gizmondo: https://gizmodo.com/5035456/blue-screen-of-death-strikes-birds-nest-during-opening-ceremonies-torch-lighting

Now it’s at the Register: https://www.theregister.co.uk/2008/08/13/olympics_blue_screen_death/

But what’s genuinely amusing about this is the comments that are coming up, they range from the obvious to the really quite odd.

There are the standard comments lambasting Microsoft, but I think these should be disregarded; basically because they are boring in the extreme and especially given how interesting some of the other comments are.

Comments at the Register can be found here: https://www.theregister.co.uk/2008/08/13/olympics_blue_screen_death/comments/

The comments seem to be breaking down into a number of camps:

  1. The “Are they genuine?” camp
    There’s the camp that are questioning if the images themselves are real, or if they’ve been “photoshop”ed.
  2. The “Is it a hooky copy of MS Windows?” camp
    Plenty of people seem to be questioning if these are valid versions of Windows. Now this is just disingenuous; by implication (and directly, sadly, such as “it is in China after all”) it is being insinuated that this is what should be expected of China. I think this is pretty base, and hope it receives the contempt it deserves.
  3. The “Is it a Hardware error?” camp
    This group state that it’s a hard ware error that no OS could have responded to. Many add that at least you get this specific H/W error message with Windows.
  4. The “Have Microsoft done this on purpose ?” camp
    Now really this is like coming home to find that the life has turned into Bizarro World. Some of these conspiracy theorists note that one of the blogs in question is “supported” by Microsoft, others suggest that it is a ploy to get people to upgrade and move from XP to Vista.

Frankly what’s so very wrong with the idea that the pictures are genuine, that it is a valid copy of Windows, that there hasn’t been a hardware error, and that, just perhaps, software goes wrong occasionally?

It just takes a little application of Ockham’s Razor to see the truth here.

No outbound Twitter SMS for Europe, the UK and, frankly, most of the World

I received the following email this morning, apparently they’ll be no more outbound Twitter SMS for Europe, the UK and most of the rest of the World. The only countries to be keeping the outbound SMS service are Canada, India, and the US. Apparently it’s all down to the charges that our mobile network operators charge us for SMS delivery, which initially Twitter had been subsidising, however they can’t afford to do that any more and have begun to “rein in the cost” by disabling the service. I can’t blame them, however I think it’s a shame that they set a precedent by enabling this functionality, only to take it away.

Oh, and good luck to them as they “negotiate with mobile operators in Europe, Asia, China, and The Americas” but I can’t see this service coming back any time soon. And I wonder how long it will be before people are trying to find a way round this decision, potentially by spoofing a US, Indian or Canadian address, given that each of the solutions they have suggested have a cost to the user (either to deliver the SMS itself or to contribute to the datalink to the WAP service).

Changes To Twitter SMS

Hi,

I’m sending you this note because you registered a mobile device

to work with Twitter over our UK number. I wanted to let you

know that we are making some changes to the way SMS works on

Twitter. There is some good news and some bad news.

I’ll start with the bad news. Beginning today, Twitter is no

longer delivering outbound SMS over our UK number. If you enjoy

receiving updates from Twitter via +44 762 480 1423, we are

recommending that you explore some suggested alternatives.

Note: You will still be able to UPDATE over our UK number.

Before I go into more detail, here’s a bit of good news: Twitter

will be introducing several new, local SMS numbers in countries

throughout Europe in the coming weeks and months. These new

numbers will make Twittering more accessible for you if you’ve

been using SMS to send long-distance updates from outside the UK.

Why are we making these changes?

Mobile operators in most of the world charge users to send

updates. When you send one message to Twitter and we send it to

ten followers, you aren’t charged ten times–that’s because we’ve

been footing the bill. When we launched our free SMS service to

the world, we set the clock ticking. As the service grew in

popularity, so too would the price.

Our challenge during this window of time was to establish

relationships with mobile operators around the world such that

our SMS services could become sustainable from a cost perspective.

We achieved this goal in Canada, India, and the United States.

We can provide full incoming and outgoing SMS service without

passing along operator fees in these countries.

We took a risk hoping to bring more nations onboard and more

mobile operators around to our way of thinking but we’ve arrived

at a point where the responsible thing to do is slow our costs

and take a different approach. Since you probably don’t live in

Canada, India, or the US, we recommend receiving your Twitter

updates via one of the following methods.

m.twitter.com works on browser-enabled phones

m.slandr.net works on browser-enabled phones

TwitterMail.com works on email-enabled phones

Cellity [https://bit.ly/12bw4R] works on java-enabled phones

TwitterBerry [https://bit.ly/MFAfJ] works on BlackBerry phones

Twitterific [https://bit.ly/1WxjwQ] works on iPhones

Twitter SMS by The Numbers

It pains us to take this measure. However, we need to avoid

placing undue burden on our company and our service. Even with a

limit of 250 messages received per week, it could cost Twitter

about $1,000 per user, per year to send SMS outside of Canada,

India, or the US. It makes more sense for us to establish fair

billing arrangements with mobile operators than it does to pass

these high fees on to our users.

Twitter will continue to negotiate with mobile operators in

Europe, Asia, China, and The Americas to forge relationships

that benefit all our users. Our goal is to provide full, two-way

service with Twitter via SMS to every nation in a way that is

sustainable from a cost perspective. Talks with mobile companies

around the world continue. In the meantime, more local numbers

for updating via SMS are on the way. We’ll keep you posted.

Thank you for your attention,

Biz Stone, Co-founder

Twitter, Inc.

https://twitter.com/biz