W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2015

Re: [remote-playback] Why not use the Safari API?

From: Jer Noble via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Nov 2015 16:41:41 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-153786948-1446655300-sysbot+gh@w3.org>
@mounirlamouri 
> I am tracking a few metrics about the usage of the webkit prefixed 
API (using internal Google tools). 

Google's spider and usage counters aren't browsing the web under a Mac
 or iOS Safari User Agent, so you're missing every site with 
UA-specific behavior. Including, for example, YouTube, DailyMotion, & 
Vimeo, among others, which I'm sure you'll agree is a large percentage
 of internet video. 

So, I would argue that your "internal Google tools" are almost 
entirely useless for this purpose.

That said:

> Thus, as much as I think we should use this API as a legacy to 
understand the UC, I don't think there is any benefit for the Web to 
standardize it as-is.

I agree. For one, "AirPlay" is a trademarked term, so it doesn't 
belong in a spec. And you can "cast" to a remote over a wired 
connection as well as a "wireless" one.  Replace all instances of 
"airplay", "wireless playback" with "remote playback", and you have 
something spec-able. 

-- 
GitHub Notif of comment by jernoble
See 
https://github.com/w3c/remote-playback/issues/1#issuecomment-153786948
Received on Wednesday, 4 November 2015 16:41:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 November 2015 16:41:43 UTC