Investigate possible fingerprinting means via the Streams API
The fingerprinting concerns that immediately jump out here are triggered by
There are more advantages too — you can detect when streams start or end, chain streams together, handle errors and cancel streams as required, and react to the speed of the stream is being read at.
We need to check how fine-grained the timers are for starting/ending streams or whether one could get fingerprinted by how fast the client side can process incoming data. There might be more.
The concerns are somewhat mitigated as the big win by combining that API with ServiceWorkers is not available to Firefox 68 ESR.
The bug where this got enabled is: https://bugzilla.mozilla.org/show_bug.cgi?id=1505122.