Stats 48 hours after we launched tgethr

Also I am always interested to hear the number of requests/second generated from a link. This is useful in benchmarking your site setup to make sure you'll be able to comfortably handle the load.

Hopefully we've made it a ton simpler and more secure.

Some examples about security:

I don't believe if I setup a private Google Group with my coworkers about a password or upload a sensitive file, that any of that would be encrypted with SSL.

Also with an email certificate and a little setup, I can easily send and receive encrypted emails with my group. If I want to send that password or document to my group, I don't have to worry about the email being sent in the clear to this 3rd party application. I also don't have to worry about the emails that the 3rd party app sends out. If the group is setup as "secure", tgethr is only going to send out encrypted emails if we have people's public emal certificates. If we don't, they'll get links back to the app where they can login and view the conversation under SSL, until they send us their cert.

This feature is definitely inspired by the constant worry we'd have about what we can and can't put into a message on other SaaS collaboration tools we've used, because of the emails that it sends out. "Better not share the username/password in XYZ trouble ticket, because it's just going to send it out in the clear to everyone else."

It's also inspired by Rackspace. We love using Rackspace. Those guys kick ass. But their support system just sends me emails with links in them to login and view the discussion online over SSL. I like using email, and this email is full of text, but none of it is actually about the ticket. Because rightfully they know they shouldn't be sending these sensitive emails about our hosting over unencrypted emails.

So we put something tgethr to take some of the worry away about these types of issues.