1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tor?

Discussion in 'Black Hat SEO Tools' started by someperson666, Feb 29, 2012.

  1. someperson666

    someperson666 BANNED BANNED

    Joined:
    Feb 23, 2012
    Messages:
    49
    Likes Received:
    0
    Ok i was using the tor bundle which has noscript of course, then closed my laptop lid.
    when I opened and logged in again it was slow since I had many tabs in both chrome (non-tor) and firefox (tor)
    only on firefox i got a message "a script is running that is slowing computer down do you wanna stop it" or someshit like that.
    question, anonymity leak?
     
  2. someperson666

    someperson666 BANNED BANNED

    Joined:
    Feb 23, 2012
    Messages:
    49
    Likes Received:
    0
    bump3replies
     
  3. someperson666

    someperson666 BANNED BANNED

    Joined:
    Feb 23, 2012
    Messages:
    49
    Likes Received:
    0
    bump for repliaes srsly.
     
  4. playerb

    playerb Junior Member

    Joined:
    Aug 25, 2010
    Messages:
    116
    Likes Received:
    54
    did you whitelist (even temporarily) any site in noscript?
     
  5. someperson666

    someperson666 BANNED BANNED

    Joined:
    Feb 23, 2012
    Messages:
    49
    Likes Received:
    0
    no
    js is enabled by default tho, could it be it
    my computer was just slo as fk
     
  6. playerb

    playerb Junior Member

    Joined:
    Aug 25, 2010
    Messages:
    116
    Likes Received:
    54
    if you're allowing js, then yeah that's why you would've got the warning. the slowness most likely came from the fact that the browsers probably swapped/paged out (dumped the data to hdd from ram), so when you opened the lid again, it was reading a lot of info from hdd .. bit of a guess , lol
     
  7. Grizzy

    Grizzy Senior Member

    Joined:
    Nov 11, 2008
    Messages:
    919
    Likes Received:
    999
    I wouldn't worry about it. If no script is set to disallow everything then it must have been a browser component that caused the unresponsive script warning.