Wish the videos were working. It would be really cool to adjust the style as well

Yes please improve surf forecasting!

This is great, I'm currently studying for Security+ and will be using this. Where are the practice questions from?

Thank you!

Trombone! I joined a couple of community bands and they are always something to look forward to

Seems cool! Was getting into WebRTC last year and this would have helped a lot. Is the pricing for this available yet?

Looks to be $0.05 / realtime GB

https://blog.cloudflare.com/whats-next-for-cloudflare-media

What bandwidth does a typical video call use per hour?

First TB is free. I would assume at least 1.5 Mbps for HD so ~5.4 Gbph ... ~.7 GBph so 3.5¢ per hour if my math checks out.

Unclear if that would multiply by number of callers.

Depends what codec! For 1280x720 with a VMAF score of 90 this is the numbers I use.

* H264 - 1.25Mbps

* VP8 - 1.00Mbps

* VP9 - 700kbps

* AV1 - 550kbps

What did you find difficult about WebRTC? What could have been better/easier?

To me it was that all tutorials are very outdated, using deprecated browser APIs, and/or using packages and services that abstract away WebRTC (SimpleWebRTC deprecated package and service, PeerJS, etc...), and none of them using TypeScript.

So I wrote my own WebRTC app that solves all of those issues [0].

I really liked your book, but there's no code in it at all, and I'm a person that learns more by following examples and applying them.

I honestly found it a bit weird that a book about WebRTC has no code at all.

[0]: https://github.com/adhamsalama/webrtc

Thanks for your contribution and maintaining the pion library(I am a user). The thing is that WebRTC usually isn't a complete solution, many don't want to have p2p but a p2s2p(which usually means distributed computing/SFU) solution, which makes developing an application way too complex.

I couldn't tell if this was a joke.

Why do you think this was a joke?

I have have been trying my best to make WebRTC more accessible [0] [1]. It's powerful, but the complexity makes it challenging.

[0] https://github.com/pion

[1] https://webrtcforthecurious.com

Thanks for your work -- I've used pion before myself.

Then you know the answer to that question. I imagine on a thread like this that would only tread the surface of the complexity, the first question will always be "What the hell even is STUN, TURN, ICE, SCTP, DTLS, SRTP?"

And thats the beginning of the complexity. But it's also a naturally complex problem. So, I thought it was a joke.

I usually look for duplicate issues that aren’t being addressed, or if there’s just a lot of seemingly non-trivial ones that go unanswered

For me the presence of a stale bot that automatically closes issues after 30 days - like Bulma - is a major red flag.

Sweeping issues under the carpet actively makes your library worse, only because one really values the vanity metric of "closed/open issue ratio".

Github star count is another useless metric, often inflated by "star this on github" widgets on the homepage.

I wish the auto-close bot could be considered a red flag for the exact reasons you stated, but unfortunately it’s in effect on tons of actually good projects, so it’s not useful as a signal.

Big fan of your articles! I have a few bookmarked that I like to read every now and then

Cool. I hope they are helpful.

Looks cool, did you compose the backing tracks yourself?

I wish :( For now I am taking free resources wherever I can find it and for the rest it comes from youtube, but more of a temporary measure. I’m in contact with a few artist and am trying to get properly licensed tracks for most, if not all, scales asap

That’s what made it easier for me. I would be that drive-by user in discord or searching for “Good First Issue” without even being remotely interested in the project. Now I try to focus on using it first. It was mostly an ego thing I had to move past

Ansible caught my interest! I setup a dev server and have been wondering about using Ansible to install my development dependencies on a new OS

You’re welcome to take a look [0] at what I use now; it’s designed to be used with Packer to build QEMU images for Proxmox.

Also it’s not really set up how I now prefer to do things, hence the total rewrite that’s underway. When that’s done, I’ll archive this repo with a link to the new one.

[0]: https://github.com/stephanGarland/packer-proxmox-templates