While OTs (there are several variants) are a promising approach for distributed authoring, I think the complexity of implementing them is still prohibitive. Surely there is a better way...
I have been reading papers on this looking for a "clean" way to solve this (in the context of packet loss, latency, etc).
There are other approaches out there. One example which uses character based changes and is worth checking out is here:
PAPER wikisym.org/ws2010/tiki-download_wiki_attachment.php?attId=15
CODE https://github.com/gritzko/ctre
I feel like it is time someone solved this collab. editing thing once and for all and shared the code with everyone. (Firepad? https://github.com/firebase/firepad/)
We provide a similar service here at Firefly: http://usefirefly.com/ Except our stuff is definitely production-grade software, works across all browsers, and supports dynamic DOM changes.
Good to see some big names taking their own spin on co-browsing.
Interesting. It seems this may be one of Mozilla's first(?) forays into a potentially paid service: hosted TowTruck accounts.
Since it runs on a central server, that server will either be Mozilla's or yours. I know I don't want to deal with that hassle -- I'd much rather pay someone else to run the service -- and I can't imagine Mozilla's going to do it for free at scale.
Mozilla hasn't yet pulled a Reader, as far as I know, but I would be worried about their dedication to a hosted service like this.
The server is super-simple, it just relays messages between the clients, it doesn't interpret or change messages at all. We're keeping the server simple so that we can do things like replace it with WebRTC data channels, or... just basically keep our options open. It's also great for development or freezing – since the changes are almost exclusively in the client there's no special coordination you have to do to switch versions, you just make a copy of the client code.
I'm guessing at some point we'll have to make the server a little more sophisticated, like maybe for authorization. But maybe not! We'll try our best to find other ways.
Also of course it's completely open source, so we can't actually pull a Reader ;)
Mozilla is already running Persona free at scale. If they let WebRTC do most the heavy lifting I don't see why they would have any issues running TowTruck free at scale.
I made a (much shittier, slightly different) version of this for a hackathon a while ago as a chrome extension! Basically, it lets people go through a webpage and talk about it together, or let one person "present" a webpage to others. The element the presenter is hovering over is highlighted to all others, they automatically follow his/her scrolling and navigation (to other pages), you can annotate with stickies on a page and it has a chatbox.
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 worked for a company that did this years ago as a commercial tool. Also the solution worked on IE8+ with plugins for chrome and FF. Nice that Mozilla is doing the same.
Looks like it uses WebRTC, at least for audio and avatars. The state of the DOM as it changes is handled elsewhere. Is this FF / Chrome only at the moment?
Really like the mention of audio/video integration coming soon.
Likely not the market they really had in mind, but this could be an awesome extension to forums. Definitely an upgrade on the standard chatbox so many are still stuck with, and it's great that you don't need to give out personal details to start a call or private IM.
The killer feature here is "Real-time authoring" but this still doesn't exist for virtually any web application, like PHP, Rails, etc. without refreshing and gets even worse with compiled languages/frameworks such as Java/.NET/etc.
So, is this aimed solely as a mockup collaboration tool?
[+] [-] human_error|13 years ago|reply
[+] [-] srobertson|13 years ago|reply
[+] [-] general_failure|13 years ago|reply
[+] [-] navs|13 years ago|reply
I'd be far more willing to trust Mozilla than Google or Apple. As Firefox OS has shown, they're committed to the web.
[+] [-] smosher|13 years ago|reply
A lot of the recent stuff was in the wings, but the announcements have been coming incredibly fast lately.
[+] [-] pie|13 years ago|reply
Given Mozilla's profile and resources, maybe they'll come up with a novel solution!
[+] [-] ivansavz|13 years ago|reply
I have been reading papers on this looking for a "clean" way to solve this (in the context of packet loss, latency, etc).
One good approach I was able to understand is Neil Fraser's Differential Sync http://neil.fraser.name/writing/sync/eng047-fraser.pdf
There are other approaches out there. One example which uses character based changes and is worth checking out is here: PAPER wikisym.org/ws2010/tiki-download_wiki_attachment.php?attId=15 CODE https://github.com/gritzko/ctre
I feel like it is time someone solved this collab. editing thing once and for all and shared the code with everyone. (Firepad? https://github.com/firebase/firepad/)
[+] [-] friism|13 years ago|reply
[+] [-] meltzerj|13 years ago|reply
Good to see some big names taking their own spin on co-browsing.
[+] [-] rattray|13 years ago|reply
Since it runs on a central server, that server will either be Mozilla's or yours. I know I don't want to deal with that hassle -- I'd much rather pay someone else to run the service -- and I can't imagine Mozilla's going to do it for free at scale.
Mozilla hasn't yet pulled a Reader, as far as I know, but I would be worried about their dedication to a hosted service like this.
[+] [-] ianb|13 years ago|reply
I'm guessing at some point we'll have to make the server a little more sophisticated, like maybe for authorization. But maybe not! We'll try our best to find other ways.
Also of course it's completely open source, so we can't actually pull a Reader ;)
[+] [-] htilford|13 years ago|reply
[+] [-] zaptheimpaler|13 years ago|reply
[+] [-] combataircraft|13 years ago|reply
[+] [-] nicholasreed|13 years ago|reply
[+] [-] Tautologistics|13 years ago|reply
[+] [-] ianb|13 years ago|reply
[+] [-] marizmelo|13 years ago|reply
[+] [-] jwandborg|13 years ago|reply
[+] [-] toddmorey|13 years ago|reply
[+] [-] ianb|13 years ago|reply
[+] [-] michaelmartin|13 years ago|reply
Likely not the market they really had in mind, but this could be an awesome extension to forums. Definitely an upgrade on the standard chatbox so many are still stuck with, and it's great that you don't need to give out personal details to start a call or private IM.
[+] [-] mbesto|13 years ago|reply
So, is this aimed solely as a mockup collaboration tool?
[+] [-] cromwellian|13 years ago|reply
[+] [-] carey|13 years ago|reply
Edit: Actually, they’re really different things.
[+] [-] indubitably|13 years ago|reply