Live data from Hacker News

Hello Firefox, this is Chrome calling

blog.chromium.org

111–120 of 183 posts

Re: Hello Firefox, this is Chrome calling

#111
post #18

Note that Chrome (or the application) chooses to reverse the self-view so that it acts like a mirror, whereas Firefox (or its application) chooses to display what the other person sees . It's a hard choice to make.

Why are they different?

Because then the thumbnail where you see your own face behaves more like a real-world mirror, which is easier to reason about if you want to adjust your position.

Re: Hello Firefox, this is Chrome calling

#112
post #23

Earlier quoted context omitted.

Actually, not really. It's all HTML 5 video elements on the page, so this is all you need: .mirrored { transform: scaleX(-1); } And you can make a button to add/remove that class as needed. However, I do hope the implementations are consistent as to which way it flips the video.

Changing it is easy. Adding options is an easy way to avoid choices. But Jabbles' point still remains: It's a hard choice to make.

I agree that it's a hard choice; I had to make this exact choice last week when working on a video chat service. Possibly because of the nature of the service (tutoring/teaching) it felt incredibly unnatural to see a non-mirrored image of myself. I tried it out both ways and it really did feel quite peculiar, and I had a hard time figuring out my own movements (kinda like trying to shave using two mirrors).

Re: Hello Firefox, this is Chrome calling

#113
post #18

Note that Chrome (or the application) chooses to reverse the self-view so that it acts like a mirror, whereas Firefox (or its application) chooses to display what the other person sees . It's a hard choice to make.

Why would you make it a mirror image? If they have anything written out it would be backwards.

You see a mirrored image of yourself and a non-mirrored image of the other party.

Re: Hello Firefox, this is Chrome calling

#114
post #107

Earlier quoted context omitted.

Interoperability with V/VoIP protocols will still require a translation layer somewhere. That can be on the browser, or on the server, but you will still need some server-side component to relay the signaling information through (eg, websocket proxy), or a browser-interoperability mechanism (for xmpp, BOSH). If the remote endpoint doesn't support WebRTC's flavor of SRTP, then you're going to have to relay media throu…

That's what I meant - most probably some server support will be required. I hope ejabberd and others will address this. Until that WebRTC won't be useful for building web based XMPP/Jingle clients. Regarding codecs - most XMPP/Jingle clients support VP8 and Opus is catching up too. It's not like there are many of them around anyway. Farstream supports both if corresponding gstreamer components are present.

IIRC, ejabberd is agnostic about the XMPP messages going through, you should be able to use strophe.js to craft the proper Jingle packets from the browser's offer/answer session description.

Given codec and SRTP compatibility with clients, eg GTalk (which I don't know about), you should be good to go.

Re: Hello Firefox, this is Chrome calling

#115
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

By your own admission, Skype is the best video communication platform that exists but is far from perfect. It's hard to disagree. Why isn't someone creating something better?

How do you compete with free ?

Re: Hello Firefox, this is Chrome calling

#116
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

Have you tried Google Hangouts? I've had some success with that lately over Skype.

I would expect Google Hangouts to use webRTC when available and use the Talk plugin only as a fallback.

Re: Hello Firefox, this is Chrome calling

#117
post #18

Note that Chrome (or the application) chooses to reverse the self-view so that it acts like a mirror, whereas Firefox (or its application) chooses to display what the other person sees . It's a hard choice to make.

Are there any usability studies on video self-views? What are the precedents from other video conferencing software like Apple's FaceTime and Google Hangouts?

I expect it heavily depends on the application, context and user role. So it's a great thing to offer developers the choice of whether to mirror or not.

Re: Hello Firefox, this is Chrome calling

#118
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

I'm not 100%, because I do audio-only rather than video, but I think Trillian will handle that for Skype, and its a little bit more stable. I agree that Skype is one of the worst apps out there.

Re: Hello Firefox, this is Chrome calling

#119
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

Have you tried Google Hangouts? I've had some success with that lately over Skype.

I love Google Hangouts, and prefer them to Skype, but they bring my laptop to its knees. Multicolored pinwheels everywhere.

Re: Hello Firefox, this is Chrome calling

#120

Earlier quoted context omitted.

And who packages that box?

You're veering awfully metaphorical, but it might be relevant to point out that the crypto implementations in wide use today are typically open source, and the algorithms themselves are public, and widely reviewed by independent cryptographers who have no incentive to do anything sinister.

In fact, they have a good incentive not to do sinister things. If they do, and other cryptographers find out, they will lose a lot of standing in the academic community.
Post reply on HN