Well well well...
The infamous email seems to have eluded my email address, and the vemenous reply by some of you is at least partially shared by myself. It's simply a knee-jerk reaction to the situation, not because we are suddenly non-supportive of Scream.
Yup, you infopop folks will need to deal with the chaos that naturally occurs at times like this. I've developed not a liking nor a disliking for you, I suppose you'll earn either in the coming weeks. I've never dealt with UBB directly except where it involved W3T in some fashion (conversion scripts, which we've had a lot of requests for, etc.), but I've dealt plenty with Rick and he's always shined. I have to believe this decision, even though I don't completely understand it, is the best one - there may be some details I'm not privy to.
As for those of you angry / upset (choose your adjective) over this decision, my request is that you hold that in check long enough to see how these fellas earn our trust. This is of course up to you, but those are my plans.
Strategically, UBB has been a weaker (in terms of backend capabilities), more froo froo, easier to install program, the latter point being a significant selling point. Marketing W3T seems like a good "heavy traffic" alternative for its customers. I'm in complete agreement that it's an unwise decision to take on the stigma of UBB to W3T - image is a VERY important factor in marketing. I'd either stick with WWWThreads or name it something entirely new - naming it UBBThreads implies it's going to be like UBB, which is what you all have said is not going to happen, aside from a few minor consistencies. See the contradiction?
Reconsider the name...
There will be a lot of motivation on the part of Infopop to keep as many of you loyal customers as they can. I for one will stay on the boat because of Scream. If in the process they show themselves as worthy of my loyalties, then I will try to be as helpful for them as I have for W3T.
