dougwbrunton

We wrote a blog post detailing some of the shenanigans we had to pull with the Teams APIs in order to get this going: https://frameable.com/company/tech/how-we-built-multiple-scr...

My first job was technical support for an internet service provider in Seattle (seanet.com). Dan Kegel's ISDN page was in my OmniWeb bookmarks (we were a NEXT shop), and got me through many rough calls.

Later in life I had the pleasure of working with Dan at Oblong Industries.

I'm such a fan of his work, and him as a human.

It whines at `ldd`, too, but that ain't stopping me.

Okay, thanks.

Thank you.

Is there a bug in the command line parsing there? I can't see it.

Which OS? There is an issue open for Firefox on iOS: https://github.com/team-video/tragopan/issues/3. Is yours different?

Is the toolbar jumpy (which is a known problem, I've just opened an issue for it at https://github.com/team-video/tragopan/issues/5), or is the zooming jumpy?

I've opened an issue to track this request: https://github.com/team-video/tragopan/issues/4

What browser/os was giving you trouble?

Thanks for the report - I've filed it at https://github.com/team-video/tragopan/issues/3

I couldn't reproduce the Chrome jumpiness - what version of Chrome/iOS was giving you trouble?

Now I just want to see those holiday decorations :-))

I think if I were in your shoes right now I might use a peer to peer video conferencing application that relies on tried and true p2p e2ee (or build one, it's not hard).

Insertable streams are new, and less proven.

An honest question, do you visit sites served by Cloudflare? Is point-to-point encryption okay for your use cases there, or do you have security concerns that require e2ee for your communications?

I think the biggest difference is that Zoom's implementation will be opaque, and Jitsi (and mediasoup's, etc.) will not be.

https://webrtchacks.com/true-end-to-end-encryption-with-webr...

https://jitsi.org/blog/e2ee/

https://github.com/versatica/mediasoup/issues/383

Yes!, at the cost of recording, speaker stats, and all participants having a pre-shared secret. Or you could use a peer to peer service that doesn't use a media router, if you have few enough participants.

Insertable streams are coming, along with e2ee through media routers. The Jitsi folks are doing great experiments there, and I'm happy they have taken the lead.

You should do whatever you want to do, you are your own human.

My biggest question about Zoom's implementation is, how can we trust it? They haven't proven themselves to be trustworthy, so it's a big ask for the world to believe their latest pitch.

At https://team.video instead of lying to you and saying we do end to end encryption, we tell you that we do point to point encryption: https://team.video/pages/security

This allows us to identify the active speaker, keep some statistics on who spoke in the meeting, and rely on mediasoup's fantastic media router ("e.g. hey, we missed a keyframe there, can you give one to me?")

(edit: omit needless words)

mediasoup has a remarkably well considered API and architecture.

I cannot recall seeing a public Jensen report that didn’t result in better software. Kudos to the Jepsen team and their clients.

Awesome, thanks!

When you work in a google doc, do folks work in their own sections of the doc, or is it a free-for-all? How do you coordinate the work after the meeting?

I signed up for the beta. One question I had based on the site, is the primary space there a collaborative document? As in the video call and document are in the same window?

I'll check that out, for sure. At first glance, the freehand drawing bits feel a bit rough with a mouse.

In my experience influence is earned using much of what you outline. Lovely blog post.

Sweet! We're actually prototyping comments and getting feedback on those mockups and prototypes right now. If you're up for a quick chat about pain points and the comments feature, please reach out directly, I'd love to chat. I'm doug at plectica dot com.

Here's a link to an editable copy of one of those maps to get a feel for how it works (changes won't be saved) -- https://www.plectica.com/maps/embedded/CW8BMJWS3/edit

We've made some tradeoffs between flexibility and constraints/structure here -- any feedback is most welcome!