Digg is Hiring LAMP Programmers

From Joe’s shout:

It’s 6PM on a Thursday night and I’m about ready to head over to the Open Web Awards presented by Mashables.com to celebrate Digg’s wins with a few of my fellow Diggers. The only downer is that we don’t have more Diggers to share the fruits of our labor with.

I went to San Francisco last June to meet with the Digg team, and I can certify that if you have the skills, already live in the area or are willing to move there, you MUST apply. It’s not just for show, this team really rocks!

Unfortunately (arguably), I can’t move to SF, family and all, so this one’s not for me.

Digg Images and New Categories Launch Tonight

From Digg the Blog: Images and new categories launch tonight:

Hey everyone. Believe it or not, the dedicated images section you’ve been waiting for finally goes live later tonight. Lots of changes in this release: New universal taxonomy, new images cawler, sorting and duplicate image detection, etc.

I know someone who worked hard on this one, and must be happy to see it go out the door. Nervous, but happy.

We Should Not Bite the Hand that Diggs

I’ve been noticing that Digg has been getting a substantial amount of cr*p about things they’ve done on and with the site recently. Nothing new or exceptional, as every popular Web outfit gets the community treatment once in a while, but now that the dust settled a bit, I just wanted to express the following thoughts.

I had the pleasure to meet with some of the Digg crew in San Francisco last month, coincidentally hours before they released their new commenting system. What I saw was a group of people who, on top of being passionate about their respective vocations, actually believe in the product they bring us. This is a relatively rare and precious thing, and I think that as a community, we should nurture it as much as we can.

I’m definitely not saying we should just fall into blind fanboy-ism and idolize their every actions, but I do think that there’s a [not so] fine line between constructive criticism, which is usually welcomed by any self-respecting professional, and plain old bashing, which can be the most depressing aspect of public releases. And it’s not like they’re not listening (1, 2).

Yes, I do think that a balance between surprise releases and usability testing could gain to be developed. And yes, I do understand that sudden changes to something you enjoy can be offsetting for users. But I also know that they’re cultivating a tight-group/almost-family-like atmosphere amongst their ranks, and that the last thing I want is for the people behind the code to be nudged anywhere close to just being yet another bunch of salary makers, in yet another faceless corporation.

So I say, keep on guys, and thanks for your efforts. I’ll happily keep on digging and watching the site evolve.

And no, I’m not going to submit my own post to Digg. ;)

Web 2.0 Expo and Conference

The O’Reilly Web 2.0 Expo is just finishing up, and my co-worker and I had a blast with most of it. Working in the academic sphere, it really feels great to get first hand confirmation that we are perfectly on track with the rest of the industry with our vision of what is to come. Now, if only we were given the means to do it all as fast as we can dream it, which is always a challenge in a large public institution. But we’re working on that. :)

One of the highlights of the conference for me, was to find out (confirm) how close the Digg architecture is to the one that we’ve been developing for our university for many years now: LAMP (though we use PostgreSQL), memcache, Linux, clustering, etc. They actually seem to be facing some challenges that we’ve already tamed in the last year and a half. They’re hiring, by the way.

On the other hand, it was my first time in San Francisco (about time…), and I won’t lie: it’s even better than I imagined it would be! Truly a fantastic city, populated with wonderful people. First time, but definitely not the last one, especially given that I just don’t have the time to stay a few extra days to visit Berkeley, Oakland, San Jose, Santa Cruz, Cupertino, Mountain View, etc. Next time!

On this, I’m going to go and enjoy the city before I have to leave tomorrow morning.

Integrating the Upgraded Digg Tools in Blogger

Digg.com released a worthy upgrade to their site integration tools today, with such neat new features as combining the submission process and Digg box, etc. Since I have previously published a method of integrating the first incarnation of the Digg tools in your [new] Blogger posts, it is now time to post an update to take the new features in consideration.

Before you start, make sure that your blog is set to save post pages. This is a Digg (and other social sites) requirement, since we need unique URLs to submit. To verify, go to your Blogger Dashboard » Settings » Archiving » Enable Post Pages? Select yes and save.

Then go to your Blogger Dashboard » Layout » Edit HTML. Be sure to check the Expand Widget Templates checkbox.

Locate the following code in the template’s XML:

<p><data:post.body/></p>

And replace it with:

<p>
  <span style="margin-right: 10px; float: left;">
    <script>
      digg_url = '<data:post.url/>';
    </script>
    <script src="http://digg.com/tools/diggthis.js"> </script>
  </span>
  <data:post.body/>
</p>

You’re done! It’s now as simple as this.

You can also try the new, more discreet, compact mode:

<p>
  <data:post.body/>
  <span style="margin-top: 5px; float: right;">
    <script>
      digg_url = '<data:post.url/>';
      digg_skin = 'compact';
    </script>
    <script src="http://digg.com/tools/diggthis.js"> </script>
  </span>
</p>

Personally though, I’m not too keen on displaying Digg boxes showing 0 diggs when the content has not been submitted yet, nor am I interested in showing the digg box on all my posts. So I’m still going to use my original solution and just update the URL of the Digg javascript from /api/ to /tools/ in my template. Overall, it is a more involved option, but I’d rather have flexibility than ease of use.

Ultimately, I’d like to see another mode (digg_skin variable) where unsubmitted content sports a simple button (like the Digg Guy), and the box only starts to show if and after the content has been submitted.

As a side note, it’s probably going to get fixed quickly, but the compact mode of the new tool had a bug with url targeting that made the submit form show in the tiny iframe the Digg javascript outputs.

Update: 2007-07-26: Updated formatting after import from Blogger.com.