Opened 7 years ago

Closed 6 years ago

#7006 closed project (fixed)

Easy html5 streaming support in Tor Browser Bundle

Reported by: arma Owned by: mikeperry
Priority: Medium Milestone:
Component: TorBrowserButton Version:
Severity: Keywords: SponsorJ
Cc: runa, tails@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Here's what we promised:
"The Tor Project will design and implement improvements to allow Torbutton and/or the Tor Browser Bundle to allow users to stream native HTML5 video media which doesn’t require special plugins or Adobe Flash technology. We have developed prototype support for the HTML5 video streaming used by Youtube, Vimeo, and other popular video websites."

The concrete deliverable (which shouldn't limit what we do, but also shouldn't be skipped entirely) is that Tor will "provide a detailed written report with its design to improve Torbutton to provide additional application layer security and improved streaming media support for Tor Browser Bundle users." by, if I have my math correct, May 2013.

This project is intended to be a catch-all "security and privacy improvements to TBB" with a focus on making sure html5, and whatever other streaming media we can handle, get enough attention.

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by mikeperry

#6248 could be part of this on the usability front. We could also ditch the NoScript click-to-play stuff entirely and see if we can write out own. It might be less failure prone if built in to Firefox (the click-to-play barrier often causes breakage, in addition to being scary and confusing).

#5666, #5856, #6253, #6786, and maybe #5293, #5798 and #6564 are all HTML5-related privacy bugs that could be rolled into this. More may appear under tbb-linkability and tbb-fingerprinting as time goes on.

comment:2 Changed 7 years ago by mikeperry

That first one is #6428.

comment:3 Changed 7 years ago by mikeperry

Also related: #3347. Youtube has resumed requiring the opt-in url these days.

comment:4 Changed 7 years ago by runa

Cc: runa added

comment:5 Changed 7 years ago by T(A)ILS developers

Cc: tails@… added

comment:6 Changed 7 years ago by mikeperry

Status: newneeds_review

Enough of the ticket from my comments have been solved that I felt comfortable disabling the NoScript barrier for HTML5 video (#8386). This should make things substantially easier.

I would like to solve #5666, #5293, and #5798 still if we can. but those not a blocker for calling this solved in my opinion.

So: the last remaining question is if #3347 actually would change the youtube usability experience. Based on my observations, it makes no difference if we set the opt-in cookie because the major youtube usability issue is that ad-supported videos with ads only work with Flash, not HTML5.

comment:7 Changed 6 years ago by mikeperry

Resolution: fixed
Status: needs_reviewclosed

De-childing #3347. I have not encountered any youtube videos for which it makes a difference. HTML5 playability seems to be a property of each specific video, and seems independent of the opt-in.

I also am calling this closed, as the HTML5 video experience should be significantly better now in both the stable and alpha TBB bundles.

Note: See TracTickets for help on using tickets.