Earlier quoted context omitted.
http://www.quora.com/37signals/Why-doesnt-37signals-own-base... They didn't own basecamp.com then, now they have. "Project name is bigger than domains" is a part of lie part of true: Product and it's name important but if you can't get the domain just be arrogant and say to people it doesn't matter. But because you know the importance of the domain name , when you have money and chance get the domain and rule the wor…
We purchased the domain from the previous owner a few months ago. We wanted to use it to launch the new Basecamp since the Classic version used basecamphq.com. We wanted to keep the URLs separate so this seemed as good a time as any to make it happen.
The all-new Basecamp is live
121–130 of 156 posts
Re: The all-new Basecamp is live
#122It works.
Good job 37signals. You instill so much confidence in your in attention to details in your product. Much like the recent known Rails security vulnerability that you never addressed and now Github was compromised as a result.
Re: The all-new Basecamp is live
#123It says on the front page:
8,000,000+
projects managed with Basecamp
99.94%
rock-solid uptime reliability record
97%
of customers recommend Basecamp
Yet all of those stats are for the legacy Basecamp Classic product and not for this brand new product they created, which has a completely different code base, which was just released TODAY.Re: The all-new Basecamp is live
#124Great, they basically removed all the features we use in Basecamp Classic :)
Seeing this new Basecamp product makes me even more so want to use the OLD Classic version ... yet I can't.
Re: The all-new Basecamp is live
#125Free plans by using a test credit card # (e.g. 4111111111111111). It works. Good job 37signals. You instill so much confidence in your in attention to details in your product. Much like the recent known Rails security vulnerability that you never addressed and now Github was compromised as a result.
Re: The all-new Basecamp is live
#126Free plans by using a test credit card # (e.g. 4111111111111111). It works. Good job 37signals. You instill so much confidence in your in attention to details in your product. Much like the recent known Rails security vulnerability that you never addressed and now Github was compromised as a result.
I don't see a problem with accepting a test credit card. Once your free trial is over, then they'll email you a message saying your card can't be charged and you'll be expected to update it.
Re: The all-new Basecamp is live
#127Re: The all-new Basecamp is live
#128I basically like the changes and nothing was dropped that I used, and they upgraded my favorite basecamp feature; Simplicity. I do however have some concerns about a couple things:
* Information density is improved in a lot of places it needed to be, however the todo list where it was good in the old site is much worse in new basecamp, you get around half the amount of todo's on screen as before.
* The WYSIWYG editor is not perfect and taking away textile leaves me without the tools I need to format messages with code, nested lists and many other essential things.
Re: The all-new Basecamp is live
#129Not sure how 37signals can claim 99% uptime when on the first day of launch, it's not working.
Re: The all-new Basecamp is live
#130Earlier quoted context omitted.
I don't see a problem with accepting a test credit card. Once your free trial is over, then they'll email you a message saying your card can't be charged and you'll be expected to update it.
No, this is a major bug because they are trying to authenticate the credit card before accepting the input in the form field. Meaning, if you type "1234567891234567" that won't work, yet a test credit card # does work.
The validation that they are doing when you enter the card is just Luhn validation.§
This is basically just to ensure that the numbers entered into the field "at least have the possibility of being a valid credit card". No processing of the card is being done at this stage.