Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hello Firefox, this is Chrome calling

blog.chromium.org

Post reply on HN
Print view View original

51–60 of 183 posts

Re: Hello Firefox, this is Chrome calling

#51

Post by cousin_it »

TylerE wrote: post #48
dbaupp wrote: post #32

Earlier quoted context omitted.

This is possible with current technology: $(document).keypress(sendKeypressInfo)

Won't the Same Origin Policy limit the exposure via ajax?

They don't have to use ajax. They can load an image with an arbitrary url and pass the keypress data in the url parameters, or dynamically create a script tag, or create an iframe and submit a form in it, etc. The script tag method also lets them get data back from the remote endpoint, if the remote endpoint is kind enough to encode it as JSONP.

Re: Hello Firefox, this is Chrome calling

#52

Post by Bjartr »

taeric wrote: post #46
hayksaakian wrote: post #42

Earlier quoted context omitted.

It's so that if you tell your mother to get google chrome, she does not also have to get a separate plugin.

You aren't exactly making this sound more free. I would honestly prefer it if I could just buy her a large TV and we could setup video calls with it. (They already have cameras built in nowdays.) Hell, why stop at the TV. Her phone likely has all that is needed for this. Does this go any further to making that happen? I guess I can see how it does. I mean, the idea is that this protocol can be used to communicate bet…

At a technical features level? Absolutely nothing. This provides nothing to an end user that they couldn't already get. The only thing this changes, from an end user perspective, is the number of steps it takes to do things.

tl;dr: This is an evolution of browser standards, not a revolution in consumer software (from an average end-user POV)

From a developer POV, this is pretty cool because now it is (or at least, is well on its way to being) significantly easier to build an app that relies on real-time media shared between peers with only the only onus on the end-user being having an up-to-date browser. The simplest and most obviously useful application of this is a basic VoIP tool.

Re: Hello Firefox, this is Chrome calling

#53

Post by hellopat »

I haven't really been keeping up on WebRTC, so forgive this fairly ignorant question.

Will the framework allow me to create a one to many connection? ie. presentation mode where one person could broadcast their audio / video to many viewers? Or is it simple a 1:1 connection?

Re: Hello Firefox, this is Chrome calling

#55

Post by wubbfindel »

untog wrote: post #44
criley wrote: post #38

Earlier quoted context omitted.

It's a hard choice for the human who has to pick one or the other and justify that decision.

In what way? The developer should have no problem justifying the decision. "It's what the camera sensor sees". I absolutely understand the application in webchat and why you would want it to be mirrored at a page level , but I'm at a loss to understand why the browser implementation would try to reflect that.

"reflect" tsk boom!

Re: Hello Firefox, this is Chrome calling

#58

Post by taeric »

Bjartr wrote: post #52
taeric wrote: post #46

Earlier quoted context omitted.

You aren't exactly making this sound more free. I would honestly prefer it if I could just buy her a large TV and we could setup video calls with it. (They already have cameras built in nowdays.) Hell, why stop at the TV. Her phone likely has all that is needed for this. Does this go any further to making that happen? I guess I can see how it does. I mean, the idea is that this protocol can be used to communicate bet…

At a technical features level? Absolutely nothing. This provides nothing to an end user that they couldn't already get. The only thing this changes, from an end user perspective, is the number of steps it takes to do things. tl;dr: This is an evolution of browser standards, not a revolution in consumer software (from an average end-user POV) From a developer POV, this is pretty cool because now it is (or at least, is…

I think this is ultimately my confusion. I'm at the point now where I'm actually usually advising family members on devices that rely less on browsers. Why not show a chat from gmail/whatever in a browser to a regular app on an android/ipad device? Even better, include another app in there. Just to really drive home how "open" this is.

Also, why is this stuff better than SIP related technology from a while back?

Post reply on HN