Re: Tor breaks slashdot

2007-03-30 Thread Michael_google gmail_Gersten

I spoke too soon. It is still broken. And, further investigation now
tells me what's going on.

The repeat case: Go to slashdot. Log into an account that uses the new
discussion system. View any page.

Expand a "hidden" discussion topic. It will work.

Switch to Vidalia. Ask for a new identity.

Switch back to firefox. Try to exand another hidden discussion topic.

Vidalia will show a connection opens to slashdot, and then closes.
Nothing else will change in the browser -- you will not see the full
text of the discussion (only the short blurb that came with the
original page), and you won't see the parent/reply buttons.

It is not so much triggered by Tor, but by using a different
connection than the original page.

Since Tor will change connections after (I think) 10 minutes by
default anyways, this can occur without using "new identity".



On 3/30/07, Michael_google gmail_Gersten <[EMAIL PROTECTED]> wrote:

On 3/5/07, Michael_google gmail_Gersten <[EMAIL PROTECTED]> wrote:
> Tor seems to be destroying slashdot's new "hidden, display on demand"
> discussion format.
>
> Test environment: Firefox 2.0.0.2, Mac os 10.4.8, privoxy 3.0.6, tor rc 9.

Ok, the pictures for this are up at http://www.stb04.nccom.com/ftp/tor-slashdot/

Please note: This was broken in rc 9. It is working (tested today)
with rc 12, Mac os 10.4.9, and Firefox 2.0.0.3. Same privoxy :-).

I don't know which upgrade fixed it, but it does work now.



Re: Tor breaks slashdot

2007-03-30 Thread Michael_google gmail_Gersten

On 3/5/07, Michael_google gmail_Gersten <[EMAIL PROTECTED]> wrote:

Tor seems to be destroying slashdot's new "hidden, display on demand"
discussion format.

Test environment: Firefox 2.0.0.2, Mac os 10.4.8, privoxy 3.0.6, tor rc 9.


Ok, the pictures for this are up at http://www.stb04.nccom.com/ftp/tor-slashdot/

Please note: This was broken in rc 9. It is working (tested today)
with rc 12, Mac os 10.4.9, and Firefox 2.0.0.3. Same privoxy :-).

I don't know which upgrade fixed it, but it does work now.


Re: Tor breaks slashdot

2007-03-05 Thread Ringo Kamens

Just upload them to imageshack, potobucket, etc. and link to the from here.
Ringo Kamens


On 3/5/07, Michael_google gmail_Gersten <[EMAIL PROTECTED]> wrote:


What's the proper way to send screenshots to this list?

> Is there a chance that you could give a more detailed description
> or even provide some "before" and "after" screen shots where you
> highlight the problem?
>
> I visited the URL above, but I'm not sure what a "display on demand"
> feature looks like or how the navigation is supposed to work.



Re: Tor breaks slashdot

2007-03-05 Thread Michael_google gmail_Gersten

What's the proper way to send screenshots to this list?


Is there a chance that you could give a more detailed description
or even provide some "before" and "after" screen shots where you
highlight the problem?

I visited the URL above, but I'm not sure what a "display on demand"
feature looks like or how the navigation is supposed to work.


Re: Tor breaks slashdot

2007-03-05 Thread Fabian Keil
"Michael_google gmail_Gersten" <[EMAIL PROTECTED]> wrote:

> Tor seems to be destroying slashdot's new "hidden, display on demand"
> discussion format.
> 
> Test environment: Firefox 2.0.0.2, Mac os 10.4.8, privoxy 3.0.6, tor rc 9.
> 
> For this test, everything went through privoxy. Slashdot page is
> http://it.slashdot.org/article.pl?sid=07/03/05/041215&from=rss
> 
> Privoxy config file contains one relavent line:
> 
> ## forward-socks4a / localhost:9050 .
> 
> This line was either commented out, or uncommented, to switch tor on or off.
> 
> Observed behavior: When commented out (tor turned off), clicking on
> the hidden discussions first displays the "initial burst" that appears
> to have come in the original web page, and after about one second, the
> rest of the article and article header appear, downloaded on demand
> from slashdot.
> 
> When enabled, the next (first) one also appears. After that, no more
> will download.
> 
> When disabled again, there will be one more "does not appear". After
> that, they will all appear.

Is there a chance that you could give a more detailed description
or even provide some "before" and "after" screen shots where you
highlight the problem?

I visited the URL above, but I'm not sure what a "display on demand"
feature looks like or how the navigation is supposed to work.

It would also be interesting to know if you freed the browser cache
between the requests and if you can reproduce the problem without
Privoxy.

You might additionally want to increase Privoxy's debug level to
see if and how the requests differ.

> The delay of one between enabling/disabling, and actual, I'm guessing
> to be privoxy noticing a change to its config file.

That's probably correct. Privoxy reloads it's configuration file
with the first request after the change was made, but that request
itself will still use the old settings.

Fabian


signature.asc
Description: PGP signature


Tor breaks slashdot

2007-03-05 Thread Michael_google gmail_Gersten

Tor seems to be destroying slashdot's new "hidden, display on demand"
discussion format.

Test environment: Firefox 2.0.0.2, Mac os 10.4.8, privoxy 3.0.6, tor rc 9.

For this test, everything went through privoxy. Slashdot page is
http://it.slashdot.org/article.pl?sid=07/03/05/041215&from=rss

Privoxy config file contains one relavent line:

## forward-socks4a / localhost:9050 .

This line was either commented out, or uncommented, to switch tor on or off.

Observed behavior: When commented out (tor turned off), clicking on
the hidden discussions first displays the "initial burst" that appears
to have come in the original web page, and after about one second, the
rest of the article and article header appear, downloaded on demand
from slashdot.

When enabled, the next (first) one also appears. After that, no more
will download.

When disabled again, there will be one more "does not appear". After
that, they will all appear.

The delay of one between enabling/disabling, and actual, I'm guessing
to be privoxy noticing a change to its config file.