vr000m

6 ms·

1.
by vr000m 4mo ago
I think being able to code by talking is going to be the future. However we need to figure out how to switch between different projects and have it do what I mean and not what i say. Speech is a lot more imprecise and perhaps less coherent
2.
by vr000m 2y ago
The latencies in the table are based on heuristics or averages that we’ve observed. However, in reality, based on the conversation, some of the larger latency components can be much lower.
3.
by vr000m 2y ago
Daily now supports dial-in and dial-out, https://docs.daily.co/guides/products/dial-in-dial-out#main Which means you can connect a bot to a call, and tell it dialout to a phone number and it will.
4.
Daily’s Global Mesh Network(daily.co)
28 points by vr000m 4y ago|1 comments
5.
by vr000m 4y ago
High level overview of how video is delivered to 100,000 participants using mesh/cascaded video routers (aka, SFUs) with 200ms latency. Servers are geographically spread, servers coordinate with each other to route media. Selectively f
6.
by vr000m 4y ago
Reminds me if the work from @lkozma in 2007, http://www.lkozma.net/wpv/
7.
Our new European call server region can benefit call performance(daily.co)
1 points by vr000m 4y ago|0 comments
8.
by vr000m 4y ago
Agreed, all of the early HTTP based streaming was about HTTP progressive download. Microsoft’s smooth streaming was dominant in the early 2000s used it too. Glad that Twitch has been using it. For me, DASH and HLS are just manifests or play
9.
by vr000m 4y ago
Agreed and thank you for the contribution. Alas, the work is now embroiled in breaking it apart into smaller parts.
10.
by vr000m 4y ago
Unfortunately modern routers made multicast unrounable, otherwise, we’d all be using mbone
11.
by vr000m 4y ago
All the listed protocols came after HTTP. RTSP, SIP borrowed heavily (albeit badly in retrospect) from HTTP. I do not have all the historical context (early 90s), but for WebRTC, the idea was to not define any new protocol(s) or do a clean
12.
by vr000m 4y ago
Pavlov’s comment is correct. I came to add that soon the stream can be stored on customer’s own S3. Ergo, you’d be able to do a call in real-time, store it on your S3 account and make it available for streaming. On your own S3, this would b
13.
by vr000m 4y ago
In the case of QUIC, it is likely that the streaming would be over H/3 (HTTP3) or HTTP over QUIC. They may fallback to H1 or H2 but typically over a long enough time, firewall rules become more relaxed.
14.
by vr000m 4y ago
Most common browser implementations use an Open GOP. That means an IFrame is implemented when needed. On scene change or when there’s high motion. Only naive implementations would burst an IFrame on to the network, most pace them. And if ne
15.
by vr000m 4y ago
Webrtc protocol doesn’t dictate 1 or 2. Although browsers do implement some of their own assumptions for this. By default the client side buffer can be orders of 100s of milliseconds. this is as you pointed out tuned for real-time or live a
16.
by vr000m 4y ago
ICE is needed when both parties are NATes, if one party was not mated, we’d not need ICE in webrtc either. Agree on 2. On 3. The videobridge needs state on who is on the session and who to forward to. that requirement doesn’t go away with Q
17.
by vr000m 4y ago
A future blogpost will talk about all the networking work that went into optimizing for these large size participation. Webrtc uses a few protocols. RTP is very central to it, ICE and SDP are also very important protocol for NATs/firew
18.
by vr000m 4y ago
Agreed. My calculations are totally skipping finding/updating the manifests or exchanging the SDP Offer/Answers.
19.
by vr000m 4y ago
Media over QUIC is interesting. For RTP or peer to peer QUIC, there is more work to be done. But you will end up engineering many of the same things as webrtc suit of protocols (ICE -- STUN, TURN, MULTIPLEXING, etc). QUIC and webtransport c
20.
by vr000m 4y ago
Low latency HLS is creating partial segments by bucketing 200ms of frames instead of 6s segments in standard HLS. Whereas in webrtc, the endpoint is sending the frame as soon as it is ready. The apples apples comparison here is 0ms (in webr
21.
Video Live Streaming: Notes on RTMP, HLS, and WebRTC(daily.co)
164 points by vr000m 4y ago|81 comments
22.
15,000 person real-time interactive live streams(daily.co)
1 points by vr000m 4y ago|0 comments
23.
by vr000m 4y ago
One thing to consider is if you would have One API and a few knobs to control the experience and not have to worry about the underlying protocol-, reliability-, latency- aspects to build that experience. (particularly not worry about the sh
24.
How and why Daily is using Rust for our WebRTC APIs(daily.co)
138 points by vr000m 4y ago|27 comments
25.
Rethinking Levels, Promotions and Salaries(daily.co)
130 points by vr000m 5y ago|196 comments
26.
by vr000m 5y ago
This was set up in 2019, the team having some fun! Thanks for finding us.
27.
by vr000m 6y ago
We do have a free plan, it’s not publicly listed at the moment. If you do under 20 000 minutes or so a month, it should not prompt for a credit card.
28.
Callstatsio acquired by 8x8 for WebRTC monitoring(twitter.com)
1 points by vr000m 6y ago|0 comments
29.
WebRTC UWP and callstats.io integration sample released(blogs.windows.com)
3 points by vr000m 8y ago|0 comments
30.
WebRTC from Candidate Recommendation to Proposed Recommendation – How?(callstats.io)
4 points by vr000m 9y ago|0 comments

More ›