kineticflow

Hey, I'm the developer.

I'm just using /chats/ API, so whatever that API spits out, I display on the front of the app. I'll probably switch over to upcoming_json soon since that's more accurate these days.

About TIME.

Exclamation points for sale!

! ! !

I can confirm that the chat now works in IE11. Thank you very much

Bellevue, WA (hi fobwashed!)

I made GB apps for Windows and Windows Phone. (<- Let me know if this isn't apporpriate for this thread, wasn't sure)

I wonder what will happen next year - all ticket sold out before Twitter announcement?

@laika:

Thank you very much for actually solving the issue instead of "why u no use Chrome". Now I'm a happy subscriber.

I reported this before, it still feels like GB is doing something with the user agent. websocketstest.com definitely works with IE11 on my network. If I change the user agent to, say, Chrome, using the exact same browser and network, the chat works perfectly fine. So it's not the browser, and it's not the network either.

Also, not everyone is "forced" to use IE11 - some people like me use IE because it syncs across my Windows phone and my tablet. The same reason for using Chrome if you have an Android phone.

The user agent for IE11 on Windows 8.1 is:

Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko

----

Edit: just read edgework's post that says "I got into today's chat with IE11."... I definitely believe you, I wonder what is going on with OP's and my setup then. :(

Just adding a data point: it seems to work for me in Firefox.