I sit next to our support "team" pretty frequently :)
We've had a couple painful SSO integrations (when they were home-grown, as you correctly point out), but we've pretty much got the rough edges sanded down now. I don't think we've had a tough one in a while.
We are a bootstrapped, profitable, distributed team of nine very friendly humans.
We're looking for a strong C++ dev with experience creating great Linux apps to lead development of our new client (currently in alpha – launching publicly soon).
I'd rather just make this free. In fact, if you email [email protected] and say you want to use Tuple for educational purposes, we'll make you a free-forever account.
Indeed! The bulk of the work to support Linux has been separating out a cross-platform real-time engine that the UI layers of each platform can plug into. Toppling the Linux domino will make Windows much easier.
> I think the problem is closing the window shuts down the screen link but not the whole pairing session, but people don't realise they need to separately end the call.
Ah hah! This is totally it. Closing the screen share does not end the call (intentionally). I can decide I don't want to see your screen any more, but still want to talk to you. Definitely a debatable design decision, though. It actually used to work the other way.
Live Share is great if your pairing session is extremely code-focused. But if you're jumping between the browser, terminal, IDE, docs, Xcode simulator, etc., you begin to want to see your pair's entire desktop.