Footnote on website is quite confusing
> For safety investigations, we also run Clio on a subset of first-party API traffic, keeping results restricted to authorized staff. Certain accounts are excluded from analysis, including trusted organizations with zero retention agreements. For more information about our policies, see Appendix F in the research paper.
They clarify API's excluded
> "Because we focus on studying patterns in individual usage, the results shared in this paper exclude activity from business customers (i.e. Team, Enterprise, and all API customers)."
Submitted multiple times in past few days. Here's a link to the most upvoted one as of now:
https://news.ycombinator.com/item?id=39865340
VoiceCraft: Zero-Shot Speech Editing and Text-to-Speech in the Wild (jasonppy.github.io)
I see a description for why webrtc-rs was picked and it seems to center around the impact to build time and size. It would be helpful to know what other factors were considered.
>Why webrtc-rs as the WebRTC library?
> WebRTC has many libraries that we could have used. The first one we evaluated was Google’s implementation known as libwebrtc. The time required to fetch+download would have been too much of a burden for the OBS code base. These metrics come from a Macbook M1 with a 400 Mb/s connection.
They clarify API's excluded > "Because we focus on studying patterns in individual usage, the results shared in this paper exclude activity from business customers (i.e. Team, Enterprise, and all API customers)."