hensm
commented
6 years ago - [x] Auth Entirely HTTP-based so can be done from within extension. Should look at removing node module dependencies.
- [ ] Device discovery Same as with CC discovery, will want to modify bridge to report back multiple types of devices and split extension StatusManager into device/status handling.
- [ ] Receiver selection Modify receiver selection process to handle multiple types of receivers and conditions where different device types are valid selection targets.
- [ ] WebKit JS AirPlay API Can be implemented fine. Doesn't seem like sites actually check the UA, so will work fine with Chrome UA and no need for more complex mixed whitelist behaviour.
- [ ] Media sender support Either adding a separate sender code path that calls AirPlay API or (for an interesting experiment) faking the default media receiver and translating into AirPlay API calls indirectly from the CC sender.
- [ ] Mirroring sender support Current screen capture methods not sufficient for AirPlay mirroring. Can't implement protocol in extension either way.