InformAction Forums

bo elam wrote: B) Time you spend building it? Is so little, is almost none. You do it over time. I hardly ever have to open the NoScript menu to add this or allow that. All the sites I visit regularly are done. Set and forget.

Greetings

Bo

Time for the addon parsing it. Unless you have a proper database, having more rules to check against takes longer time than not finding it in a short one and going for default.
So if you create an evergrowing blacklist of ever changing ad networks and myriads of junk you don't want to load, without actively sanitising it regularly for abandoned sources, if noscript goes "hey, should I allow this?"(to itself) it will have to parse an increasingly long list before going "well, I guess I don't know that one, must then be default" or "hey there it is, I guess I shouldn't then".

You know, the process that happens on every page load.

And again, why do you insist on having this debate in a topic that was troubleshooting a guy with self-expressed limited background knowledge?

Pansa wrote: Time for the addon parsing it. Unless you have a proper database, having more rules to check against takes longer time than not finding it in a short one and going for default.
So if you create an evergrowing blacklist of ever changing ad networks and myriads of junk you don't want to load, without actively sanitising it regularly for abandoned sources, if noscript goes "hey, should I allow this?"(to itself) it will have to parse an increasingly long list before going "well, I guess I don't know that one, must then be default" or "hey there it is, I guess I shouldn't then".

You know, the process that happens on every page load.

And again, why do you insist on having this debate in a topic that was troubleshooting a guy with self-expressed limited background knowledge?

What you say, also applies to a white list. Most people have a large white list, I dont. Once every few months, I clean it up. I can delete all my white listed sites, and wouldn't lose nothing. It would take me maybe an hour, and I ll have it back almost to the last domain. But losing the black list, would take me years to get it back. Irreplaceable.

in my case, NoScript works pretty fast. I got no complain. And has never gotten corrupted.

I am not insisting on having a debate, but you are. You finished your last post with a question. I guess you want an answer, so here you have it. But this is my last reply to you. Bye.

Bo

To answer the question the google script was trusted if you in google.com but if you here you can only see google.com and not it's subdomain that make recapta work. No you don't understand, even if I allow everything under default the script in the page does not work it if I check allow script globally in side the option they work, glad the reload and https function bug are known and it's not a problem of mine, I'm using the globally allow with globa script allowen in private browsing, I will try the normal one and repost in order to make you know if I still have the problems or not.

Even without the private browsing the script are not working regardless of settings and the permission of that setting, google subdomain that allow recaptcha does not appear, i'm almost sure it's bug with noscrpt at this point since most of subdomain a site can have does not appear like they did in 10.1.1, it can be related with 64bit version pof the browser? If they work in your firefox some thing on my end must be.

That was really painful to read.

It's a repetitive problem on the forum.

It was (from my perspective) a rather simple question.
Open the reply window.
Click the noscript button
Look at the information there.
Are both scripts allowed.

Yes, the current behaviour of having to "guess" if that script runs over https or http is a bit annoying.
So is the way it handles subdomains.

But on this forum specifically that is not the core issue.
On this forum the html document your browser processes only has two script sources to deal with.

One is the captcha, which is sourced directly from the google base domain, and the script sourced from this server.
the captcha doesn't come from captcha.google it comes directly from google.com/captcha.....
the other the forum itself.

Just rightclick anywhere and click "view page source". search for "src"

Basically all that noscript does (and ever did) is parse the file that you are send for blocks that say "script" look for "src" behind it, give you a toggle named accordingly and then according to your decisions tells your browser to ignore them or run them.

like this:

Just updated to new version of noscript the verification code works but still I don't know why even if I make trusted the site works like it is untrusted or on default, but it does not revert automatically to default thankfully that bug was fixed, one strange things I noticed is the fact that the number on the noscript icon say ad example 3 (which I thinks is the numbers on scripts on the page) but only 2 are shoved with permission settings, can this be a p'roblems or I'm wrong?

LongTimeFan wrote:Just updated to new version of noscript the verification code works but still I don't know why even if I make trusted the site works like it is untrusted or on default, but it does not revert automatically to default thankfully that bug was fixed, one strange things I noticed is the fact that the number on the noscript icon say ad example 3 (which I thinks is the numbers on scripts on the page) but only 2 are shoved with permission settings, can this be a p'roblems or I'm wrong?

Could you check the trusted "capabilities" portion of the debug output? (options -> at the bottom check the "debug" option)

The reset to default wasn't as much a bug as a failure to communicate what the rule people made actually was. (and again, shouldn't have been an issue on this forum anyway)

As for the number it shows and the number of entries:
One source may run several scripts.
The number shows the amount of scripts blocked, and the list the sources that want to run scripts.

It's empty, there is nothing written inside the windows under debug

LongTimeFan wrote:It's empty, there is nothing written inside the windows under debug

Was that different last week on Thursday? Can you type in it?

I can write in it, last week was full of the list of the settings of noscript even if the list was empty like in was the untrusted tab, I never touch it and I deleted the permissions by setting them on default visually above the debug option.

Then something got royally screwed on your end that I can't replicate.

The only thing I can think of in terms of self-help is creating a secondary fresh profile in firefox
starting it with the profile manager (close firefox; go to "run" -> firefox.exe -p )
And go from there so you can copy a clean set of settings back into the debug window of your current profile.

If there are settings shown above the debug window, but the debug window is empty, something is seriously FUbared.

Writing form the second firefox profile, everthing works fine, and as new profile I needed to reinstall noscript, and everything works fine, in the default profile of firefox instead there are settings shoved above the debug window but not in the the debug window, and reinstalling (removing + reinstall noscript) does not work, it must be something releted to the old 5.x noscipt file the default profile have but he new does not

Also when I fist installed noscript in the default windows the debug option was filled just after the installation, reloaded the page and the debug option was empty.

in the default profile of firefox I meant.

So in the secondary profile it works fine, and you still have the debug output?

Then try copying the content over to the default'S profile debug output.
Maybe that'll fix it.

One issue is that there are still remnants of the 5.x in the "about:config". I have those too, but that greatly surpasses what I can suggest as fixes.