I'll take a quick moment to share my favorite web app which uses WebRTC: Instant.io [0]. I use it all the time to transfer files among local devices, or to send medium to large files to friends.
Apple Announces Full WebRTC Support in Safari 11
141–150 of 167 posts
Re: Apple Announces Full WebRTC Support in Safari 11
#142What WebRTC apps can we expect will be mainstream in, say, 6 years? I'm just trying to picture what this technology will allow (or replace).
We at Lookback use WebRTC to do live streaming research sessions for desktop, iOS, and Android. Works pretty neat, even though you need a SFU (a rebroadcaster) to support heavier load than a few peers watching. So the style of doing P2P for video sort of gets lost anyway ..
Application neutral WebRTC rebroadcasting becomes a commodity this way though, so it should become quite cheap.
Re: Apple Announces Full WebRTC Support in Safari 11
#143SO excited about this. Data-channel and all. Non-jailbroken torrenting on iOS at long last :P https://webtorrent.io/ Also, definitely worth trying out this AR.js demo if you're running the beta: https://freinbichler.me/apps/web-ar/ Always thought it was a little peculiar that the Media Capture APIs are tied to what is otherwise a very data/protocol-oriented spec. Wish we could have had a camera feed in a canvas eleme…
How would this allow you to torrent on iOS without jailbreaking the device? My phone, though an iPhone 6, seems to shut down Safari if I've been using other apps long enough. I can't imagine it staying alive long enough to torrent anything large.
[deleted]
Re: Apple Announces Full WebRTC Support in Safari 11
#144Earlier quoted context omitted.
Is that a political or technical decision?
Is that a political or technical decision? One obvious technical issue is that, as far as we know, there's no VP8 decoding hardware in any of Apple's products; implementing VP8 decoding in software might be more of a power drain than Apple wanted.
> there's no VP8 decoding hardware in any of Apple's products
But what I found interesting in the WWDC session you linked to was that a lot of Apple products don't have hardware HEVC decode and\or hardware HEVC encode support. Apple has implemented software HEVC decoding and encoding in a lot of places. From that perspective, adding support for VP8 and VP9 wouldn't be much different.
Re: Apple Announces Full WebRTC Support in Safari 11
#145Earlier quoted context omitted.
I always find it disappointing when video from Apple doesn't work in Firefox. There are quite a few JavaScript libraries available these days which support HLS in browsers which don't have built-in HLS support but Apple doesn't make use of them.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in.
Apple was doing video [1] long before Firefox and the web were a thing; perhaps it's Mozilla that needs to get with the times and industry standards.
Re: Apple Announces Full WebRTC Support in Safari 11
#146It would be interesting to see surveys about mobile IPv6, will it get along with P2P? Will mobile users get P2P video this way or have the operators crippled end-to-end connectivity?
Re: Apple Announces Full WebRTC Support in Safari 11
#147I saw this yesterday on twitter and my thought was "they don't support webrtc yet?!? seriously?" It sometimes baffles me how apple is holding up progress on the web - and that they aren't criticized more for it.
Maybe you were still in middle school but there was a time when the web was dead and IE killed it. Mozilla and Apple resurrected the web.
Apple famously refused to allow Flash on iOS and in doing so single-handedly did more to push HTML5 standards than anyone else. I'll also point out that WebRTC has gone through numerous iterations to such a degree that a lot of WebRTC sites don't work with Safari 11 because they're using old non-standards-compliant variants of the API.
The typical HN web dev seems to load their site in Chrome, click around a bit, and call it a day. That's not healthy for standards or the web, but it sure is lazy and expedient for a very narrow group of people.
Chrome is not the web.
Re: Apple Announces Full WebRTC Support in Safari 11
#148Earlier quoted context omitted.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in. Apple was doing video [1] long before Firefox and the web were a thing; perhaps it's Mozilla that needs to get with the times and industry standards. [1] https://en.wikipedia.org/wiki/QuickTime
> perhaps it's Mozilla that needs to get with the times
Mozilla is with the times. HLS works well in Firefox. You just do it with JavaScript and it's disappointing that Apple doesn't bother to do that on their website.
Here's an article on JavsScript based HLS from a couple of years ago:
Re: Apple Announces Full WebRTC Support in Safari 11
#149TypeError: nativeMediaDevices.addEventListener is not a function still some bugs maybe...
This is a capturing API, I guess?
Using webrtc-adapter, all of my webrtc code instantly worked. Though it doesn't seem to want to connect to firefox peers.
Re: Apple Announces Full WebRTC Support in Safari 11
#150Earlier quoted context omitted.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in.
Apple should stop fooling around, and start using DASH+MSE instead. But being Apple, they have very hard time letting go of their NIH and lock-in. Apple was doing video [1] long before Firefox and the web were a thing; perhaps it's Mozilla that needs to get with the times and industry standards. [1] https://en.wikipedia.org/wiki/QuickTime
DASH is being with the times and standards. HLS is being Apple.