Quantcast
Channel: InformAction Forums
Viewing all 17374 articles
Browse latest View live

Re: Localization NS 10

$
0
0
anm made changes on August 20th. I noticed just yesterday.
I will now return the hackademix version of August 18th.

UPD: Fecit

> And does it need to be updated again before I release 10.1.9.7
No, specially it is not necessary to release "rc" because of it.

Re: Localization NS 10

$
0
0
fatboy wrote:anm made changes on August 20th. I noticed just yesterday.
I will now return the hackademix version of August 18th.

I've pointed the translation coordinator to this thread: I'm confident she knows how to handle this kind of conflicts.
fatboy wrote:UPD: Fecit

Thank you.

fatboy wrote:No, specially it is not necessary to release "rc" because of it.

Not released "because" of it, but latest development build 10.1.9.7rc3 contains it:

v 10.1.9.7rc3
=============================================================
x Fixed preset customization UI showing inherited DEFAULT
permissions if a protocol-level preset exist
x Simplified CSP HTTP header injection, avoiding report-to
until actually supported by browsers
x [L10n] Updated ru (thanks fatboy)

Re: Preset customizations: treating HTTPS and HTTP different

$
0
0
With the latest update (10.1.9.8) I can finally do that: I have set "http:" to UNTRUSTED and can customize http sites, if necessary.

@Giorgio Maone: I am very happy with this update, many thanks!

Re: Preset customizations: treating HTTPS and HTTP different

$
0
0
musonius wrote:With the latest update (10.1.9.8) I can finally do that: I have set "http:" to UNTRUSTED and can customize http sites, if necessary.

@Giorgio Maone: I am very happy with this update, many thanks!

You're welcome :)

Per-site permissions: how to delete an entry plus add ...

$
0
0
Hi,

Version 10.1.9.6 on Firefox 62.0.3 64-bit

Can entries be deleted from the per-site permissions list? (whithout resseting the whole list to default, I mean)

Also:

Trying to add a match for (anyname).sub.domain.com - Writing *.sub.domain.com, clicking the + button, nothing happens.
I have added sub.domain.com, does not work for host1.sub.domain.com
Adding domain.com does work for host1.domain.com.

Thank you in advance.

Regards.

Re: Per-site permissions: how to delete an entry plus add ..

$
0
0
Kallistoi wrote:Can entries be deleted from the per-site permissions list? (whithout resseting the whole list to default, I mean)

Set the unwanted entry to Default, it will be gone when you close or reload the options page.

Kallistoi wrote:Trying to add a match for (anyname).sub.domain.com - Writing *.sub.domain.com, clicking the + button, nothing happens.
I have added sub.domain.com, does not work for host1.sub.domain.com
Adding domain.com does work for host1.domain.com.

I'm not seeing this using a local server and NoScript 10.1.9.7rc3. Trusting sub.domain.com also trusts *.sub.domain.com.

Do you have an example URL where the issue occurs?

Re: [FIXED] (classic) Automatic reload broken?

$
0
0
Giorgio Maone wrote:
whoosh wrote:Is it possible to restore it?

I sent an email to my "lead" there (the one who published the external listing last time).

And this is his answer:
Pale Moon guys wrote:The listing had been removed, as it had been creating too much confusion within our community.

Following the addition of the warnings in our Add-ons Manager earlier this year (to which I've previously explained), there had since been much confusion as to why an add-on with a warning was included on our site in any fashion, be that with a full listing or as an external one (i.e. linking to your site). When an add-on is included on our site it is generally viewed that
this should work without displaying any such warnings, our community has since displayed concerns about its presence on our site and on several occasions requested it be removed for this reason. In addition, due to the nature of the add-on affecting many parts of the browser - the nature of which debatable depending who you discuss with - it has created many support issues within our community that cannot easily be resolved, to the point where we have had to outright refuse support for such users (see https://forum.palemoon.org/viewtopic.php?f=46&t=17619). While there may not have been any issue with NoScript itself, it appeared to create additional issues elsewhere, such that its operation was (by many users) seen as an issue with the browser itself as opposed to the extension.

I am truly sorry about the confusion this situation has caused, however given the ultimate reaction by our community and the subsequent support issues presented by this we have had to take the decision to remove this outright. Users are still able to install the extension from your site, and get updates for it from your site as before; the only difference now is that we would not be able to link to it directly from our add-ons site (as an external listing is exactly that: a link to the site where one can install an extension, and nothing more).

Re: [FIXED] (classic) Automatic reload broken?

$
0
0
Giorgio Maone wrote:
whoosh wrote:Is it possible to restore it?

I sent an email to my "lead" there (the one who published the external listing last time).

And this is his answer:
Pale Moon guys wrote:The listing had been removed, as it had been creating too much confusion within our community.

Following the addition of the warnings in our Add-ons Manager earlier this year (to which I've previously explained), there had since been much confusion as to why an add-on with a warning was included on our site in any fashion, be that with a full listing or as an external one (i.e. linking to your site). When an add-on is included on our site it is generally viewed that
this should work without displaying any such warnings, our community has since displayed concerns about its presence on our site and on several occasions requested it be removed for this reason. In addition, due to the nature of the add-on affecting many parts of the browser - the nature of which debatable depending who you discuss with - it has created many support issues within our community that cannot easily be resolved, to the point where we have had to outright refuse support for such users (see https://forum.palemoon.org/viewtopic.php?f=46&t=17619). While there may not have been any issue with NoScript itself, it appeared to create additional issues elsewhere, such that its operation was (by many users) seen as an issue with the browser itself as opposed to the extension.

I am truly sorry about the confusion this situation has caused, however given the ultimate reaction by our community and the subsequent support issues presented by this we have had to take the decision to remove this outright. Users are still able to install the extension from your site, and get updates for it from your site as before; the only difference now is that we would not be able to link to it directly from our add-ons site (as an external listing is exactly that: a link to the site where one can install an extension, and nothing more).

Re: [FIXED] (classic) Automatic reload broken?

$
0
0
Giorgio Maone wrote:And this is his answer:
Pale Moon guys wrote:[...]

Thank you for looking into it and posting their answer.
So from now on, Pale Moon users should get NoScript from here: https://noscript.net/getit#classic.

I'll admit I'm disappointed with their decision.

Thank you again for continuing support for the classic version of NoScript.

Re: [FIXED] (classic) Automatic reload broken?

Re: Per-site permissions: how to delete an entry plus add ..

$
0
0
Kallistoi wrote:Writing *.sub.domain.com, clicking the + button, nothing happens.


Have you literally written "*.sub.domain.com"? In this case nothing happens, because it's the wrong syntax. You should write "sub.domain.com" which, as barbaz already wrote, trusts all *.sub.domain.com as well.

Re: Per-site permissions: how to delete an entry plus add ..

Re: [Tor] Incorrect default settings

$
0
0
Thanks for directing me to the appropriate thread. I'm not seeing a way to delete this one so it's not cluttering up the board.

Re: How to fix Per-Site Permissions always have to be reimpo

$
0
0
I doubt any of the Tor devs will see this, but I don't understand why, as a way to prevent fingerprinting, they would force the default to trusted instead of leaving NoScript's default settings as default. Did someone over there forget that allowing scripts to run on most sites helps to de-anonymize?

Re: [Tor] Incorrect default settings

$
0
0
That's OK, I'll just lock this as a duplicate.

Re: No More "Temporarily allow all..." Option (Resolved)

$
0
0
Ahh - thank you. I was trying to edit the title (the bold text above "Post a Reply").

Works fine now! :D

Re: Problem Logging into MS Hotmail Account (Resolved)

$
0
0
I'm now using version 10.1.9.8 and I haven't had any more Hotmail Login problems for the last couple of weeks. I think this problem has been resolved (but I'm not sure).

Re: Pale Moon addons site listing discussion split from t=22

$
0
0
Hello Giorgio,

I too would like to express my most sincere thanks for continuing your support for the PaleMoon family.

I'm making a (small :oops:) donation, and I'll encourage other Pale Mooners to do the same.

Best regards from Berlin,
JoeG

"Reverse engeneering"

$
0
0
Hello, i'm not native english, but i hope i can form your imagination.


A present example got me to this, called gmx.de.

I reduced "allowed" to a minimun, that Ads and other stuff wasn't loaded at all and fastend up that page, relative to my "poor" internet. I did that by stopping loading manually and check which pages are showed in "noscript".


Now some time later, they changed something which is checking for something or evaluating, if a pageproperty is successfully loaded, so i get a "you need a modern browser" thingy and breaks my "email-experience".

I would have some ideas to workaround to fix this until another change of their site, but i like to request some ideas to make such situations more easily fixable.


1. A Log (did i miss the information, that there is 1 and where, and how i use it?)
2. Treeing all forks per sitecall to config (instead just listing alltogether), no matter if NewTab, Favorite (realize, that some configs always open new tabs on favorite), Link (maybe reduced to new window/tab) (helpful for my problem mentioned above to maybe even reset just 1 major (domain) site) - OK, there maybe crossovers, mark them as such and maybe make some global settings/categories for such sites (i.e. google stuff, but ther' others u no).
3. About those crossovers, maybe it makes sense, to allow the same site for 1 page, and disallow it for the other? At least it would provide a robust "per domain" structure.
4. A Log that is tabrelated and/or per manual/favorite/link sitecall adress (see 1.).
5. ! A "LOADMANAGEMENT AT FIREFOXSTARTUP" - because Firefox need the longer to start, the larger my database is. At least it was suggested due to fresh FF-Profile, after importing data, slowdown was present (3secs+). I must admit, my PC is about 5 years+ old - maybe it counts.


Thank you.


*To be added, i use Linux Mint 18, check for system is up2date and autoupdate noscript.

Re: Pale Moon addons site listing discussion split from t=22

$
0
0
JoeG wrote:Hello Giorgio,

I too would like to express my most sincere thanks for continuing your support for the PaleMoon family.

I'm making a (small :oops:) donation, and I'll encourage other Pale Mooners to do the same.

Thank you.
Viewing all 17374 articles
Browse latest View live