Rikki

Wow, that's a blast from the past!

It's a MySQL restriction more than anything. By default, MySQL doesn't allow fulltext searching with less than 4 characters. This can be configured on the server, but then searches become horribly inefficient.

It's unlikely we'll have a skin by default that's specifically for iPhone, simply because it's only one device. There will be a better LoFi skin in a later release, though.

We could have added hundreds of lines of HTML to add rounded corners, but for something so unimportant I don't think that's worthwhile. It doesn't affect the usability of the software, so in our opinion, it's something that the newer browsers can use, and the older browsers can just ignore :) Not everyone is going to want rounded corners on their skin, which would leave them with all those extra tags that would be useless. Personally, I think creating a working base then enhancing it where browsers support particular features is a better way forward than trying to strong-arm all browsers into one pixel-perfect rendering.

The bulk of the IPB3 documentation is now delivered inline in the ACP - click the 'Get Help With This Page' button on any page to load it :) We'll be adding to what's available over time.

You don't double click, you click the 'Show All Emoticons' button.

Don't worry, we have competition besides vB :)

Let's just be clear, the standard editor works fine - it's the RTE specifically that doesn't work in WebKit.

Welcome, we hope you enjoy using it :)

Our editor didn't support Webkit in 2.x, and we weren't able to add support in time for 3.0. It's something we're going to look into adding in a future version, and sooner rather than later :)

I was going to put bfarber on the homepage, but I figured we wanted people to stick around and buy something. :P

It's just a random picture someone posted to the gallery. I would guess a model...

Indeed, I'm doing usability studies on the site. I find this kind of thing fascinating... We've already made a couple of small tweaks to the site based on these :)

Things... - Client area is going to be messy for a little while - Same for order process, both are integrated with Nexus so pulling them apart for the new design is going to take a little longer - Resource site won't be changing for a while - Download manager, community projects etc. aren't forgotten but we'll be adding them in due course - Demo will be fixed soon

Regarding skins, there is simply no way we can do a major version upgrade and make skins compatible. I understand that's a reason to keep on 2.3.6 right now, but we hope you also understand that to move things forward, we had to redo things.

It's hardly fair to say they're copying in all honesty. A forum looks like a forum, there's only so much you can do to change it without alienating users. Plus, when you go fully tableless & semantic, you're kind of guided into a particular structure by the tags you choose to mark up the data.

We're all getting ready to go on vacation :P

They're tab-indented, although it's difficult to make out since everything is wrapping.

Line numbers are very difficult to implement unfortunately. Tabbing is acknowledged, and searching is unnecessary, all browsers have a built in ability to do it :)

How'd you mean?

You'll be pleased to know there is now a big improvement in rendering on IE6. It is not perfect and we still don't officially support it (and the experience will not match that of other browsers), but it is a little more presentable for those users still stuck on it.

That said, for a later version we're going to see about writing something a little better to use. At the very least I would like to get the ability to press Tab in place. The full syntax highlighter simply wasn't working out though.

If you click the little green arrow next to a user name anywhere on the board, it will show a handy little popup overview, and from there you can find all their posts/topics :)

That's a fieldset - different browsers render them differently. It's perfectly normal :)

It's not a perfect solution, but another option is hook into the includecss hook in globalTemplate->includeCSS, and manually insert a style tag with your css.