Re: Network Predictive Actions re-enabled on Nightly

2015-01-21 Thread Patrick Cloke
On 1/21/2015 1:10 PM, Nicholas Hurley wrote: So for a quick answer to your question, yes, there is a frecency-like algorithm for this. It's even tuneable (to an extent) via prefs! (I'm working on a blog post about this feature that will go into more detail on this, keep an eye on Planet Mozilla,

Re: Network Predictive Actions re-enabled on Nightly

2015-01-21 Thread Chris Peterson
On 1/21/15 10:10 AM, Nicholas Hurley wrote: So for a quick answer to your question, yes, there is a frecency-like algorithm for this. It's even tuneable (to an extent) via prefs! (I'm working on a blog post about this feature that will go into more detail on this, keep an eye on Planet Mozilla, h

Re: Network Predictive Actions re-enabled on Nightly

2015-01-21 Thread Nicholas Hurley
On Mon, Jan 19, 2015 at 4:56 PM, wrote: > My point was that just because it is in my history, does not necessarily > mean I intentionally visited it. Maybe I lent my computer to someone else > or clicked on a link by mistake. (By the way, I fully understand why the > assumption that if it's in th

Re: Network Predictive Actions re-enabled on Nightly

2015-01-19 Thread Martin Thomson
On Fri, Jan 16, 2015 at 12:41 AM, Jonas Sicking wrote: > FWIW, a difference in load time of 100ms is quite big. Websites like > Amazon has measured significant changes in clickthrough rates when > they have experimentally increased loadtime by 100ms. > I believe that significant resources have b

Re: Network Predictive Actions re-enabled on Nightly

2015-01-19 Thread clokep
> On Fri, Jan 16, 2015 at 8:45 AM, Nicholas Hurley wrote: > > On Thu, Jan 15, 2015 at 9:44 PM, Patrick Cloke wrote: > >> I did not think you were randomly guessing, I guess I'm not convinced the > >> browser is able to tell what the user has "intentionally" done. > > > > Given that the browser ha

Re: Network Predictive Actions re-enabled on Nightly

2015-01-16 Thread Nicholas Hurley
Argh, I somehow sent this reply to just Patrick instead of the list. Sorry for the duplicate email, Patrick. On Fri, Jan 16, 2015 at 8:45 AM, Nicholas Hurley wrote: > > > On Thu, Jan 15, 2015 at 9:44 PM, Patrick Cloke wrote: > >> I did not think you were randomly guessing, I guess I'm not convi

Re: Network Predictive Actions re-enabled on Nightly

2015-01-16 Thread Jonas Sicking
On Thu, Jan 15, 2015 at 6:44 PM, Patrick Cloke wrote: > Even if not a large privacy concern, I doubt I'll see a beneficial tradeoff > from reducing my connection times by 100ms. I'm sure other people will find > this super beneficial, however. I'll probably give it a try before deciding > what to

Re: Network Predictive Actions re-enabled on Nightly

2015-01-15 Thread Patrick Cloke
On 1/15/2015 9:03 PM, Nicholas Hurley wrote: Patrick, The predictor may issue dns requests or start connections (including TLS negotiations, if necessary) entirely based on browsing history combined with a confidence calculation (the details of which are in the code, but intentionally left vague

Re: Network Predictive Actions re-enabled on Nightly

2015-01-15 Thread Nicholas Hurley
Patrick, The predictor may issue dns requests or start connections (including TLS negotiations, if necessary) entirely based on browsing history combined with a confidence calculation (the details of which are in the code, but intentionally left vague via email because they may change in order to

Re: Network Predictive Actions re-enabled on Nightly

2015-01-15 Thread Patrick Cloke
On 1/15/2015 12:26 PM, Nicholas Hurley wrote: All, I just landed https://bugzilla.mozilla.org/show_bug.cgi?id=1009122 on mozilla-inbound, which re-enables necko's predictive actions capabilities. I won't go into the full explanation of it here, you can find the big information (very little of wh

Network Predictive Actions re-enabled on Nightly

2015-01-15 Thread Nicholas Hurley
All, I just landed https://bugzilla.mozilla.org/show_bug.cgi?id=1009122 on mozilla-inbound, which re-enables necko's predictive actions capabilities. I won't go into the full explanation of it here, you can find the big information (very little of which has changed in this new iteration) in my ori