Page 2 of 2

Re: More about blocklist setting in Basilisk

Posted: 2017-12-19, 13:37
by New Tobin Paradigm
Get me a screenshot of about:buildconfig of the latest binary for linux, please.

Or better yet, use those options and build my branch with the toolkit error console at https://github.com/binoc-central/moebius-contrib/tree/jsconsole-work

Then maybe we can sort this...

Re: More about blocklist setting in Basilisk

Posted: 2017-12-19, 13:49
by JustOff
New Tobin Paradigm wrote:Get me a screenshot of about:buildconfig of the latest binary for linux, please.
Here it is:
vmware_2017-12-19_15-46-15.png
Or better yet, use those options and build my branch with the toolkit error console at https://github.com/binoc-central/moebius-contrib/tree/jsconsole-work
Then maybe we can sort this...
Sorry, but it will probably take years in my VM box.

Re: More about blocklist setting in Basilisk

Posted: 2017-12-19, 14:01
by New Tobin Paradigm
Nothing wrong build config wise.. Guess will wait on Travis.. Least with appending restoration of the Toolkit Error Console we will be able to get to the bottom of these issues once and for all..

THIS is why this is important.. for this exact reason.. Having all your eggs in one basket with devtools is very bad and this is why...

Re: More about blocklist setting in Basilisk

Posted: 2017-12-26, 09:26
by dodona
how to disable extensions.blocklist.enabled and the whole blocklist algorithm permanently?

After each new start of b. or if the update interval is passed extensions.blocklist.enabled is set to true automatically and the mess starts again.
I'm fully responsible for all extensions I use and don't need a nanny software knowing 'better' what is good for me than myself.

Re: More about blocklist setting in Basilisk

Posted: 2017-12-26, 11:27
by Moonchild
This is Mozilla's "settings service" that is causing havoc, which is part of their whole "we decide how you want to use your browser" trip they are on right now, and which was not caught by us until after release (because it was all done on the quiet). This kind of interference will be solved in the next version of Basilisk, since it will no longer be talking to Mozilla's servers for this.

Re: More about blocklist setting in Basilisk

Posted: 2017-12-27, 08:02
by dodona
Moonchild wrote:This kind of interference will be solved in the next version of Basilisk, since it will no longer be talking to Mozilla's servers for this.
Thank you! :thumbup: :thumbup: :thumbup:

Re: More about blocklist setting in Basilisk

Posted: 2017-12-27, 22:53
by gracious1
Moonchild wrote:This is Mozilla's "settings service" that is causing havoc
So now Mozilla is actually altering Firefox's settings without the user's consent or even knowledge? That is really disturbing. :twisted:
I wonder how many other software will follow suit with something like that on their products?

Re: More about blocklist setting in Basilisk

Posted: 2017-12-27, 23:04
by dodona
gracious1 wrote:
Moonchild wrote:This is Mozilla's "settings service" that is causing havoc
So now Mozilla is actually altering Firefox's settings without the user's consent or even knowledge? That is really disturbing. :twisted:
I wonder how many other software will follow suit with something like that on their products?
I never experienced that "settings service" with firefox 1..56. Anyhow, as a temporarily bug fix a extension (or whatever) setting extensions.blocklist.enabled to false with each firefox start would be nice. Is anybody out there who can write such a bug fix extension?

Re: More about blocklist setting in Basilisk

Posted: 2017-12-28, 00:14
by dodona
today was really awful. After each restart our "settings service" made problems. Finally another dialog appeared forcing me to upgrade to the shitty rust known as 57. I had some problem to kill this dialog posting this message.
Guess there is some evil code in firefox < 57 responsible for that mess.

Re: More about blocklist setting in Basilisk

Posted: 2017-12-29, 08:23
by dodona