Thursday, August 25, 2011

Can't connect in Chrome? Try ws=1!

EDIT: 08/31/11 ?ws=1 is no longer needed as we now default to websocket for Chrome users! 

In an attempt to debug Chrome and what is causing people to not connect please try the following:

Try to enter your room, example:

If it doesn't work, add ?ws=1 to the URL, so try this URL instead.

Adding ?ws=1 forces the browser to use a different communication mechanism called "websockets", which is faster but only works in Chrome.

Please let me know if you Chrome users have any luck with this hack. If it works, try joining all rooms with ?ws=1 for a speedier experience!



No comments:

Post a Comment