Yesterday’s release brings some new cool features and one major bugfix to sixgroups.com:
Twitter-Backchannel
You can now send a copy of your Livecommunity posts to Twitter:

When sending tweets from sixgroups.com you can choose between eight different icons to express your current mood. We also use these icons to identify posts from sixgroups.com to prevent them from showing up in the Livestream a second time.

Global Twitter search
Up till today the Livestream would only show Tweets from sixgroups users. Now you can also chose to display Tweets from the global Twitter search.
Find your friends on sixgroups.com
Finding people on sixgroups.com you already know by email has just become a lot easier. Import your contacts from your webmail adress book (eg. Gmail, MSN, Yahoo, etc) and we will tell you, who of your mail contacts already has a sixgroups.com account. Contacts who are not on sixgroups.com yet, can be invited to join. Of course we do not store your email address or password for this service.
Safari overhaul
So far we have treated Safari as a second class citizen. With this release we have fixed some JavaScript issues and a login problem in the Livecommunities related to pretty strict third party cookie regulations in Safari. We are happy to announce that all known Safari bugs have been eliminated or worked around with the current release (tested on the Safari 3.1).
OpenID fixes for Yahoo OpenIDs
A bug with OpenID Login with Yahoo OpenIDs discovered by Bernd Schmitz on Saturday night , that made us precautiously disable OpenID logins in general for ~24h, has been fixed too. When people tried logging into sixgroups.com using only http://yahoo.com as OpenID URL, the system stored a wrong OpenID for those users. Instead of using the proper Yahoo OpenID URL, which the server returned after authenticating (e.g. http://flickr.com/photos/username ), http://yahoo.com got saved as their OpenID in the database. When these users then tried logging in with http://yahoo.com as OpenID URL, they ended up being logged in as the first user that was found the DB with this URL (in this case the user art99). Luckily only two users were affected, the error has been fixed and OpenID Login is now fully functional again. We are really sorry for the caused inconvenience.







