togetherjs

I once had to fix TogetherJS where the proceed button was broken: https://github.com/mozilla/togetherjs/commit/ced91da4bb53bea... Clue: what is the problem with this code?

Isn't this the exact same as: https://github.com/mozilla/togetherjs With the difference that you charge for it? You have all right though, since it's MPL licensed - but i can't find that license anywhere....

Speaking as the principal developer for TogetherJS: In the past we have opted not to work on IE support because we had limited resources, and because we wanted to focus on what we thought were the hard problems: how should the tool act, how do we communicate changes between browsers, how do we integrate with apps, etc. Supporting Internet Explorer was always something we knew we could do, it wasn't a hard problem, but it still required some effort. As such it didn't feel like it was advancing the project. It was never meant as any slight towards IE, just an expedient way to save some time. Also, while we do browser sniffing, we only use that to put up a warning for IE users to alert them that it's not going to work well. This was pointed out on Twitter as though we were actively blocking browsers, in part I think a knee-jerk reaction

If you read up on this it's a simple UA block. IE10 and up support sockets. https://github.com/mozilla/togetherjs/blob/develop/togetherj... https://twitter.com/jdalton/status/390538182116143105

That isn't entirely true. The audio chat won't work in IE10, and IE10 support isn't a priority, but most everything else will probably work: https://togetherjs.com/docs/#browser-support Edit: Ok, looking at the issues tracker, it looks like the current IE bugs basically break togetherjs on IE10. As such, hopefully this issue gets some attention: https://github.com/mozilla/togetherjs/issues/812

[Team member here] We haven't been very focused on the hosting story, in part because lots of people have their own requirements, and we can't predict what they are. And maybe because predicting what they are is boring. I know some hooks for New Relic have been added to the server. It's also a super-simple server that only keeps things in memory, so it's pretty darn easy to handle. Just one file: https://github.com/mozilla/togetherjs/blob/develop/hub/serve... (and only one dependency, for WebSockets).

Both people are accessing the website as themselves. If one person doesn't have permission to see a page, for instance, then they won't see it. And yeah, whoever hits save is the saver ;) Doing something richer than that requires application-specific integration, which we want to support, but we also want to take cues from developers about what that should actually look like. This is one idea we have along these lines: https://github.com/mozilla/togetherjs/issues/372

I think this is what you want: https://github.com/mozilla/togetherjs/wiki/Hosting-the-Hub-S...

Yes, Firefox/Chrome only for now: https://github.com/mozilla/towtruck/wiki/Supported-Browsers

There's also an Addon (https://github.com/mozilla/towtruck/wiki/Addon) which is basically equivalent to a bookmarklet like this where you activate the bookmarklet every time you load a new page. It's only intended to trying TowTruck out (like the bookmarklet).

I am very curious to see what happens with this issue: https://github.com/mozilla/towtruck/issues/5 Given Mozilla's profile and resources, maybe they'll come up with a novel solution!