Re: [tor-dev] Tor Friendliness Scanner

On 3/17/19 8:18 PM, Ryan Duff wrote: Hi again, On Sun, Mar 17, 2019 at 7:40 PM teor > wrote: Most sites block by IP (or IP range), so a direct connection using the exit node's IP should give you very similar results to a Tor circuit using the exit node's

Re: [tor-dev] Tor Friendliness Scanner

Hi again, On Sun, Mar 17, 2019 at 7:40 PM teor wrote: > > Most sites block by IP (or IP range), so a direct connection using the > exit node's IP should give you very similar results to a Tor circuit > using the exit node's IP. > Thanks teor! The point still stand though even though my

Re: [tor-dev] Tor Friendliness Scanner

Hi, > On 17 Mar 2019, at 08:04, Ryan Duff wrote: > >> The way we intended to do this was to send our FF "ground-truth" >> collection through Tor, and specifically through the same exit node as >> TTB uses. This way we can isolate the variable to the differences in the >> browsers, rather than

Re: [tor-dev] Tor Friendliness Scanner

Hi Kevin, Really interesting project! The way we intended to do this was to send our FF "ground-truth" > collection through Tor, and specifically through the same exit node as > TTB uses. This way we can isolate the variable to the differences in the > browsers, rather than any network or other

Re: [tor-dev] Tor Friendliness Scanner

Hello everyone! Thanks for the feedback! Please see my inline comments. Santiago: > I wonder if you could share a link to the source code for people to give > you feedback/audit or implement fixes/features themselves. I will be posting the source code once I'm a little further along. Roger:

Re: [tor-dev] Tor Friendliness Scanner

Hi! Kevin Gallagher: > Hello tor-dev! > > My name is Kevin and I'm a PhD student at NYU. Recently I've been > working on creating a "Tor Friendliness Scanner" (TFS), or a scanner > that will measure what features of a given website are broken > (non-functional) when accessed on the Tor Browser

Re: [tor-dev] Tor Friendliness Scanner

On 3/4/19, Kevin Gallagher wrote: > Recently I've been > working on creating a "Tor Friendliness Scanner" (TFS), or a scanner > that will measure what features of a given website are broken > (non-functional) when accessed on the Tor Browser (TB), along with > actionable suggestions to improve

Re: [tor-dev] Tor Friendliness Scanner

Hi Kevin, It may or may not be of any use, but here is a content from an etherpad that a number of Tor folks worked on a while back regarding 'tor friendly sites". Sounds like you have a robust way of going about this, so this is provided as food for thought. peace gunner Designing a web site

Re: [tor-dev] Tor Friendliness Scanner

On Mon, Mar 04, 2019 at 03:58:58PM -0500, Kevin Gallagher wrote: > To generate a method of determining ground-truth, we decided to modify* the > Firefox (FF) browser to log all of the steps of the creation of the Content > Tree (also called the DOM tree) >[...] > We have moved ahead with

Re: [tor-dev] Tor Friendliness Scanner

Hi, > We have moved ahead with development (though have not yet finished it) and > are (hopefully) very close to a working prototype. I was wondering if there > was feedback on this method, or if anyone can consider an angle we have not > that would either make the TFS more robust, easier to

[tor-dev] Tor Friendliness Scanner

Hello tor-dev! My name is Kevin and I'm a PhD student at NYU. Recently I've been working on creating a "Tor Friendliness Scanner" (TFS), or a scanner that will measure what features of a given website are broken (non-functional) when accessed on the Tor Browser (TB), along with actionable