recently blocked sitse

[mellly]

Hi!

I just noticed recently blocked sites on the menu.

It is very risky in my opinion.

When at a site, I allow the least allowable for whatever my needs are. So, if I need video I know which one to allow, if I need to get to the next page on a site, I know which I need to allow - meaning temp allow.

On several sites I visit, I temp allow all. I have to do so on some sites and so I do when I need to.

Problem is that now when I do that, the ones that were recently blocked are now temporary allowed.

The ones that were recently blocked were from the website I was on prior to the current site. I did not disallow the ones showing on recently blocked but I guess that noscript thinks so because I didn't temp allow them.

So if I go back to a site I was on where things weren't allowed, now they are all temp allowed.

And again, the reason those recently blocked are temp allowed is because on the website I visit after that site, I ok'd temp allow all for that site, which automatically makes all showing in recently blocked now temporarily allowed, which is a great risk.

Is there a way to turn this function off?

Thanks!

[Giorgio Maone]

No, the "Recently blocked sites" isn't involved in any way with the "Temporarily allow all on this page" command.
If you want you can turn it off from NoScript Options|Appearance, but I think you're observing something different than you think.

[Melly]

HI. Thanks for writing back!

I'm fairly sure that noscript is temp allowing all recently blocked on a page just left, by giving temp allow permissions to those listed in recently blocked, when I am temp allowing all the most current page I am on.

As an example, I was on search.twitter.com earlier. I did not give it any permissions; and I put my search term in the search site and it worked fine. It didn't need any permissions.

After reading your reply I wanted to test, so I just went to search.twitter.com again, and it's showing that the site is temp allowed.

I never allowed it, never temp allowed it. It's the 'recently blocked sites' getting allowed when a user goes to another site and temp allows all for the current site; which gives recently blocked all temp allowances.

As regards to your mentioning can turn it off via appearances.. does that actually turn it off? or does it hide it from my view?

Thanks so much,
melly

[Giorgio Maone]

As regards to your mentioning can turn it off via appearances.. does that actually turn it off? or does it hide it from my view?

It actually turns it off.
But again, there's absolutely nothing in this function which may cause the effect you're reporting, and in facts nobody else is noticing that.
Are you sure you did not turn "Temporarily allow top level sites by default" on in NoScript Options|General?
Could you check if your problem persist with latest development build?

[therube]

(Just to point out, if you Allow Global, Recently blocked sites shows, "Temporarily allow all from (null)".)

[Melly]

Hi again!

I don't have temp allow top levels by default on.

I just noticed the 'recently blocked' today. Not sure when I last updated noscript, but I think it was a few days ago. Been using it a few days and didn't notice the recently blocked until today.

Yes, I will try to do some examples and give it to latest development build.

Thank you so much for writing and helping me.

Take care,
melly

[melly]

Hi. I never allow scripts global. I'm not sure if you were saying that as a possibility so just wanted to write to say I never allow global.

Every page i go to I have to temp allow (if needed) whatever it is I need, and I use the very least needed.

So for example, http://www.hulu.com will show, temp allow hulu and temp allow facebook.com etc.

I only temp allow hulu.com (and not facebook) to use the site. I use the least possible needed. If I go to hulu after a pc shutdown or after running ccleaner I will again have to temp allow hulu.com on that web site to be able to view videos. Nothing more is needed for that site, so I don't allow anything other than that. I don't set any permanent permissions for any site.

I just wanted to explain how I use no script.

(As a side note to the other post; this may be why others aren't reporting the same problems about 'recently blocked' as possibly others set permanent permissions for sites visited all the time and trusted, but I don't, so I am always in noscript temp allowing whatever it is I need to use a site.)

Take care,
Melly

[Dikaiopolis]

I'm fairly sure that noscript is temp allowing all recently blocked on a page just left, by giving temp allow permissions to those listed in recently blocked, when I am temp allowing all the most current page I am on.

As an example, I was on search.twitter.com earlier. I did not give it any permissions; and I put my search term in the search site and it worked fine. It didn't need any permissions.

After reading your reply I wanted to test, so I just went to search.twitter.com again, and it's showing that the site is temp allowed.

melly

I just went through the same steps, namely:

1- navigate to search.twitter.com
2- input search term 'kennedy'
3- observer search results (lots)
4- check NS by right clicking on the S button at the bottom (status?) bar in that same FX window (used for twitter)
5- observe that twitter.com has not been allowed (the menu that pops up offers to allow it; this means it is not allowed), temporarily or otherwise.

So I have to agree with Maone's original comment: you must be observing something else. Please give the forum exact steps to reproduce, you may need to include your configuration, too.