redditAll.com is dead, long live redditAll.com

You'll still be able to find this blog at reddit.blogspot.com, but there's a project I'll be announcing shortly that will takeover the domain redditAll.com.

Here's a sneakpeek. Stay tuned to blog.reddit for the announcement or follow me on Twitter if you're really curious.

ireddit developers 280north get fastcompany shoutout

Yes, this has been sitting in my drafts folder for too long. Anyway, check out this slideshow to learn how to make iPhone apps that don't suck and become the next iPhone app millionaire we keep reading about.

Chris Dannen wrote it, who also happens to be the dude who prompted our own iPhone app (now without crashing bug!). Yep, this guy. We've been exchanging emails now and then -- consider all future good reddit ideas the work of Chris.

business of software and how to pitch for a speaking gig

I, or rather, Pierre Francois, was invited to compete in last year's Business of Software conference. In fact, he won a Macbook Air that I'm enjoying to this day.

Well, Neil Davidson published my pitch for getting a speaking spot.

If you haven't signed up for Business of Software 09, what are you waiting for? If you're waiting for a compelling video highlighting what the con is all about, here it is:

the 37 signals dilemma

There's been on ongoing open letter exchange between 37Signals and GetSatisfaction. GetSatisfaction allows anyone to create unofficial customer support communities (like UserVoice) that all both remind me of a much better implemented features.reddit (now defunct). 37Signals doesn't want to have one and feels it "misled our customers into thinking the Get Satisfaction site was an official place to get 37signals customer service and support."

At this point, Jason Fried is requesting that the GetSatisfaction team makes it much more obvious that this is not an official 37Signals site, he outlines a number of changes he'd like them to make.

But here's the dilemma: 37signals has long touted the strategy of saying no to feedback.

That's why you start with no. Every new feature request that comes to us — or from us — meets a no. We listen but don't act. The initial response is "not now." If a request for a feature keeps coming back, that's when we know it's time to take a deeper look. Then, and only then, do we start considering the feature for real.

Granted, Jason isn't in this case a user of GetSatisfaction, but hopefully he'll find this as amusing as I do. I just hope he doesn't expect GS to do anything anytime soon. Heh.