Tor at the Heart: Firefox

The article describes it as upstream patch that is disabled by default which allow Firefox to be less discriminative when it comes to accepting patches.

Re: Tor at the Heart: Firefox

#5

Post by mburns » Tue, Jan 03, 2017, 10:59 AM UTC

saurik wrote: post #3

Why did they make up this term "uplift" instead of just saying "upstream"?

https://wiki.mozilla.org/Release_Management/Uplift_rules

Re: Tor at the Heart: Firefox

#6

Post by akavel » Tue, Jan 03, 2017, 11:23 AM UTC

mburns wrote: post #5

saurik wrote: post #3

Why did they make up this term "uplift" instead of just saying "upstream"?

https://wiki.mozilla.org/Release_Management/Uplift_rules

Truth said, I can't find an explanation/definition of what actually an "uplift" means there?

Re: Tor at the Heart: Firefox

#7

Post by gsnedders » Tue, Jan 03, 2017, 11:37 AM UTC

akavel wrote: post #6

mburns wrote: post #5

Earlier quoted context omitted.

https://wiki.mozilla.org/Release_Management/Uplift_rules

Truth said, I can't find an explanation/definition of what actually an "uplift" means there?

Typically landing a patch on a release branch, "uplifting" it from the main development branch (but occasionally uplifting it from thin air into the release branch).

Re: Tor at the Heart: Firefox

#8

Post by noja » Tue, Jan 03, 2017, 11:43 AM UTC

I'd like to see the canvas fingerprinting dealt with in Firefox mainline, it's used everywhere.

Re: Tor at the Heart: Firefox

#9

Post by rahrahrah » Tue, Jan 03, 2017, 12:03 PM UTC

I wonder how first party isolation will deal with both serving stuff from CDNs and serving stuff from different domain names which actually below to the same owner. For example,

YouTube streaming data is served from googlevideo.com,

most Reddit media is served from redditmedia.com, etc

Re: Tor at the Heart: Firefox

#10

Post by leojackson » Tue, Jan 03, 2017, 12:04 PM UTC

akavel wrote: post #6

mburns wrote: post #5

Earlier quoted context omitted.

https://wiki.mozilla.org/Release_Management/Uplift_rules

Truth said, I can't find an explanation/definition of what actually an "uplift" means there?

It looks like this page is designed for people who already know what an "uplift" is, but wish to implement it properly. That being said, it also appears that "uplifts" will include bug fixes made in Tor Browser and sent upstream to Firefox, rather than just features added (but disabled by default) as was implied in the OP article. I would have assumed that bug fixes made in a downstream product would already have a mechanism to find their way to Firefox. Maybe "uplift" was the term all along for that mechanism, or is a rebranding of it?