[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Tor breaks slashdot
- To: or-talk@xxxxxxxxxxxxx
- Subject: Tor breaks slashdot
- From: "Michael_google gmail_Gersten" <keybounce@xxxxxxxxx>
- Date: Mon, 5 Mar 2007 11:35:13 -0800
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Mon, 05 Mar 2007 14:35:29 -0500
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gtHuHukHJuLGs8Ztrw9nO0XsNqKRKGS1NqNFl9kAqRDCkj+RzUuPg1EYPY7Oi6nUc6+Qd0fSYZYuXzxgzt53JXXwtFETCD+37OM/RIleTL3Olk9u7ljK/3H1QS6AcZ2k11qUQz7TI1GHv08jmDxySnW8WLaQYQJX+EAyDN//p/g=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=aLMD/aFZrio8J8zueSeF+FvRP4QrBBFKJJvN4eba01fHToxBROzby3bomdHYicslbRAQhOFUJj67iGevTANZMAH3YjrsuBSzi5vwB0hIn/NCwFXNen8TflYKhosMUWqErNcveE4wPWhT86lYRQFtpbMeen0lWYsO9FQHUv7EYlc=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
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.