Earlier quoted context omitted.
I am pretty sure that E2E encryption is impossible today if you are using a WebRTC SFU since there's no spec for it. The closest thing is PERC Lite [1] which no browsers support, though maybe you could cobble something together native. Is there some path I didn't know about? 1. https://www.meetecho.com/blog/meetecho-and-cosmo-strike-agai...
I don't know about browsers, but I know that Signal implements E2E-encrypted phone calls using WebRTC for signalling.
Show HN: Coscreen.co – a radically different remote collaboration tool
141–150 of 188 posts
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#142Earlier quoted context omitted.
Does that mean you use the JS Screen capture api to capture each and every window separately? I would’ve thought that’s too much for typical (laptop) cpus but have to admit I never tried this
We're capturing them natively and are working on another major performance improvement which should make it at least as efficient as other major solutions.
The way I understand you, coscreen captures each window shown individually.
Doesn’t that also mean that overlapping windows are captured in full? I can’t try it out atm so perhaps if you could leave a comment on cpu usage for encoding as well as bandwidth (upload) compared to a typical Screen Sharing solution with a single screen that would be great.
I’ve been toying with the idea of getting a MacBook with cores > 4 for precisely that idea: capturing every single window, streaming them out to a separate machine for analysis of what’s happening in them and possibly making them accessible for collaboration as well, all without losing too much performance
I believe somewhere in this area is a lot of productivity waiting to be unlocked with better tools, not just for typical remote use cases but for any kind of office work
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#143For the next update please explain things before hand in your page!
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#144Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#145OP here, we believe that the time has come to let remote workers and highly agile teams get stuff done together in a very different and much more natural way. CoScreen is a remote collaboration tool that enables exactly that. Problem: Pretty much anyone who has ever worked remotely knows it - today’s remote collaboration solutions provide much better screensharing quality and reliability (thanks, Zoom) compared to a…
How much does it take to pay a hunter on PH in order to be featured these days? asking for a friend.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#146Earlier quoted context omitted.
It's not called a "machinetosh". It's Macintosh, or Mac for short. Named after the McIntosh variety of apple ( https://en.wikipedia.org/wiki/McIntosh_(apple) ). "Windows is used way more than [Macintosh] on developer machines." - Citation needed. Macs are extremely popular among web developers, and are required for iOS developers, both pretty major categories of "developer".
Thanks for the historic context ;) Edit: + Stats from the Stack Overflow Developer Survey 2019 Windows: 47.5% MacOS: 26.8% Linux-based: 25.6% Source: https://insights.stackoverflow.com/survey/2019#technology-_-...
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#147Earlier quoted context omitted.
Couldn’t agree more. Yesterday I was browsing the top product of the day to see what future competition was like and the product was a color swatch that gave you similar colors for inspiration. It looked like they mashed together a codepen with a color swatch api I’ve starred but I won’t even bother linking to here. It’s sad for sure.
Could it be that there aren't that many exciting new products coming out? Or is that blasphemy?
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#148Excellent idea, brilliantly executed. But as a CTO, I would be concerned about the security implications. It makes sense to route traffic via a central server because P2P does not scale to large numbers of participants (which is why things like the Jitsi Videobridge exist despite WebRTC P2P being a thing), but it means your customers have to trust you not to get hacked, be compelled to, or otherwise misplace/record s…
I'm curious about this statement. Intuitively it seems there is already an algorithm to near-optimally distribute updates to a sparsely connected mesh network. You'd want two or three connections from each peer to another, not N:N. Optimal is not necessary as long as you have at-least-once semantics on message delivery; a node can just ignore messages it's seen already, as long as it's not too often. Is there a name for this existing algorithm?
On top of that you could overlay a symmetric session key and you'd have full E2E. Then central server would be session initiation only--which could still do authn/z to hand out session keys--and billing/metrics.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#149Earlier quoted context omitted.
This is so good! How does it work with selecting text and copy-pasting? In the Sublime Text example, can Bob overwrite Alice's clipboard.
We're still figuring this out and will probably get inspired from remote desktop solutions. But reach out to us if you have specific ideas
Also: this would be a major feature request from me. The ability for me to paste code into someone's else text editor (or copy out an error message) when I'm helping them would be a major productivity boost.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#150Earlier quoted context omitted.
I gave up in fustration, the site has no real information, no system requirements, no installation information. does it run on linux? I like the idea but i have a department with 100 fedora workstations in it.
Thanks as well, it's macOS-only for but we're working on other OSes. It should work on anything that runs macOS Mojave and higher and at least on 5-6 year old Mac Books.
Where as pretty much all Windows users in game dev seem to have 2 or more monitors.
Are you expecting lots of mac users to buy a second monitor or use an iPad for this second monitor or is my experience just atypical and lots of mac users have 2 monitors?