#34263: Library selection for using WebRTC for the project. -------------------------------------+------------------------------ Reporter: HashikD | Owner: (none) Type: task | Status: needs_review Priority: Medium | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: snowflake-mobile | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------+------------------------------
Comment (by cohosh): Replying to [comment:6 arlolra]: > Sorry if this was covered elsewhere but is using pion, like the rest of the snowflake ecosystem, not an option? This is a good place to discuss this. I don't think we need to worry about using a different library for this project. If we were planning on reusing code from the stand-alone proxy-go instances that would be one thing. But given that we have to implement a UI with this (similar to the webextension) it doesn't seem like code sharing is an option. Another possible advantage to using pion is that it '''might''' give us more control if the Chrome WebRTC implementation is fingerprinted and blocked. OTOH, maybe the Chrome WebRTC implementation is more popular with other apps and is less likely to be blocked. Not knowing which way this will go, I'm inclined to go with whichever library is easiest for us to maintain the project. As far as interoperability, pion has been careful about testing to make sure their code plays well with other WebRTC implementations. If we have problems we should definitely upstream them but I suspect we'll be okay. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34263#comment:12> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs