Add a telemetry to see how many users have HEVC MFT support
Categories
(Core :: Audio/Video: Playback, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: alwu, Assigned: alwu)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
2.47 KB,
text/plain
|
chutten
:
data-review+
|
Details |
Assignee | ||
Comment 1•1 years ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Comment 3•1 year ago
|
||
Comment on attachment 9354935 [details]
data review request
DATA COLLECTION REVIEW RESPONSE:
Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. This collection can be controlled through the product's preferences.
If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, Alastor Wu and the media playback team are responsible.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
Is the data collection request for default-on or default-off?
Default on for all channels.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does the data collection use a third-party collection tool?
No.
Result: datareview+
Comment 5•1 year ago
|
||
Backed out for causing mochitest failures in test_MediaSource_hevc_mp4.html and test_hevc_playback.html
- Backout link
- Push with failures
- Failure Log
- Failure lines: TEST-UNEXPECTED-FAIL | dom/media/mediasource/test/test_MediaSource_hevc_mp4.html | Test timed out. -
TEST-UNEXPECTED-FAIL | dom/media/test/test_hevc_playback.html | video started playing
Assignee | ||
Updated•1 year ago
|
Comment on attachment 9354935 [details]
data review request
I'm just nosy, and have no idea to the background or development, but two questions i would ask is:
-Can this telemetry potentially be combined with other telemetry we (moz) collect to fingerprint a particular user?
-If/when hevc hardware encoding is implemented, why should data collection be ongoing? Surely you only need the number of hardwares able to support the protocol. Which will inevitably grow. Please explain why PERMANENT data collection is necessary? Also please provide a potential point in time where a review of this data collection process can take place with the view to either ending or continuing. would i.e.. 2 years be enough?"
Thinking of the users data. Too many corps suck up data, blind and bore them with extremely lengthy, incomprehensible legal jargon with 10+ links to outside sites, per paragraph of the original terms.
If we nip it here, quell the data slurp, we can help make the product AND the user better.
Comment 8•1 year ago
|
||
bugherder |
Description
•