[X] My Assistant

Turning it to a script with all the unique feature settable like MMM will be a fantastic achievement but i think that it will be a lot of work (more cause effectively a GUI will be needed to use it at his max extent).

But there is a thing, Firefox will be stopping supporting all old extensions in few months, it will go all webextensions, so if this will be released as an extension we risk to be unable to use it in little time (or to be forced to not update a clinet to use HV on it).

they really are ruining firefox lately (IMG:[invalid] style_emoticons/default/huh.gif)

is there a way to implehement sort of a configuration panel to a... uh... webextension, so xpi? is it something like greasemonkey? (IMG:[invalid] style_emoticons/default/unsure.gif)

Fundamentally FF is implementing the same type of extensons of Chrome.

It will be more easy to convert extensions from one browser to another (and i think for Androids too?) but they are not exactly the same due to the browser different cores and settings.

I think that this will be positive.

What is NOT positive is saying "from FF 57 all old extensions will not be compatible anymore".

Anyway, PaleMoon will not deprecate the old extensions system and it will not require the signature like the one of FF so i think in time it will become a really popular vrowser, eating chunks of FF users away.

This post has been edited by Maharid: Aug 28 2017, 17:12

hmmm... so, basically PaleMoon will be the browser for those who want to continue using JS. still, what should coders do? release JS and advising to use them on PaleMoon or similar? or release XPI (eventually with control panels) only? how hard is to convert a JS into a XPI, exactly?


and what about LunaScape?

This post has been edited by Scremaz: Aug 28 2017, 17:31

It seem GreaseMonkey have a good chance of be developed in Webextension.

However, eading a bit around, it seem that it will have problems will different functions and not only GM but fundamentally all the more complex extensions due to the fact that webextension is still too young and not fully developed so it have huge limitations.

And Mozilla is doing this knowing those problems... no comments.

It seem GreaseMonkey have a good chance of be developed in Webextension.

However, eading a bit around, it seem that it will have problems will different functions and not only GM but fundamentally all the more complex extensions due to the fact that webextension is still too young and not fully developed so it have huge limitations.

And Mozilla is doing this knowing those problems... no comments.

well, iirc tenboro is quite upset from firefox's direction since... v50, iirc. or at least, that was the first time i read something about it

Anyway, PaleMoon will not deprecate the old extensions system and it will not require the signature like the one of FF so i think in time it will become a really popular browser, eating chunks of FF users away.

A browser with no support for Netflix, Amazon and in general all video sites using DRM, slower than vanilla Firefox, bad UI, more bugs, slow development etc etc.
If anything the extension standard change will just increase the Chrome market share.

If anything the extension standard change will just increase the Chrome market share.

wow... from bad to worse... either way, ETA for FF57 is November. a couple of months. i'd like to give coders some directions, so? what should be the preferred format?

wow... from bad to worse... either way, ETA for FF57 is November. a couple of months. i'd like to give coders some directions, so? what should be the preferred format?

i wouldn't worry about it, i'm assuming either tampermonkey will be ported or greasemonkey will be updated before support for old-style extensions is discontinued

i wouldn't worry about it, i'm assuming either tampermonkey will be ported or greasemonkey will be updated before support for old-style extensions is discontinued

so, coders should continue to develop either JS or XPI depending on what they consider more fitting?

A browser with no support for Netflix, Amazon and in general all video sites using DRM,

DRM is a huge security hole waiting to happen, having it enable for general browsing is a bad idea, when I need it I have Chrome.

slower than vanilla Firefox, bad UI, more bugs

All objectively false.
The original goal of Palemoon (before FF started going stupid) was to be a lighter weight faster version and it still something they focus heavily on.
Australis is objectively garbage (Chrome's UI is pretty bad too, but at least it knows what it is).
FF is constantly adding useless stuff and that stuff comes with a lot of bugs. I you look though the major security bugs for FF very few of them have ever affected PM.

, slow development etc etc.

They may have less resources, but they don't wast their's on useless stuff.

If anything the extension standard change will just increase the Chrome market share.

Very few people still use FF, those that do probably have reasons that make Chrome unacceptable.

wow... from bad to worse... either way, ETA for FF57 is November. a couple of months. i'd like to give coders some directions, so? what should be the preferred format?

TamperMonkey should work on FF57, so no changes should be needed. In fact anyone with an up-to-date FF should be able to install TamperMonkey right now and use it without problem.

so, coders should continue to develop either JS or XPI depending on what they consider more fitting?

i'm thinking JS is the safest bet. with XPI you never know when browser developers are going to get even more stupid, but there will pretty much always be some way to run user scripts in all of the major browsers

This post has been edited by sickentide: Aug 28 2017, 20:44

i'm thinking JS is the safest bet. with XPI you never know when a developer is going to get even more stupid, but there will pretty much always be some way to run user scripts in all of the major browsers

hmmm... this comes because JS is an universal format and the ways to implehement it are quite well-known and XPI is quite recent, i guess?

also, am i safe into assuming that pretty much every commoner with a basic C knowledge can read what a JS does while you cannot check XPI code unless you decompile it?

Bug in Monsterbation 1.2.0.5, that wasn't in 1.1.2 (yeah I did not update since a while, I hate too frequent updates): the quickbar extends functionality is completely unable to add spells/skills (from their ids) and will fail proceeding to the next round + the round counter won't show up either.

Right now I only got my 9 item slots on the left, and it's quite annoying not to have my OFC next to them.

This post has been edited by decondelite: Aug 28 2017, 21:04

hmmm... this comes because JS is an universal format and the ways to implehement it are quite well-known and XPI is quite recent, i guess?

also, am i safe into assuming that pretty much every commoner with a basic C knowledge can read what a JS does while you cannot check XPI code unless you decompile it?

yes, and from what i understand, reading and modifying XPI code isn't completely impossible, but when it comes to convenience of use and ease of customisation, i'd say JS has the upper hand

Bug in Monsterbation 1.2.0.5, that wasn't in 1.1.2 (yeah I did not update since a while, I hate too frequent updates): the quickbar extends functionality is completely unable to add spells/skills (from their ids) and will fail proceeding to the next round + the round counter won't show up either.

Right now I only got my 9 item slots on the left, and it's quite annoying not to have my OFC next to them.

i just tested this in chrome and firefox and it seems to work fine. can you post your quickbarExtend setting (make sure the spell/skill ids are in quotes), and are you sure there are not some other settings that need to be updated for the new version?

This post has been edited by sickentide: Aug 28 2017, 21:13

quickbarExtend = [ 1,'ikey_1','ikey_2','ikey_3','ikey_4','ikey_5','ikey_6','ikey_7','ikey_8','ikey_9',231,421,1101,1111],

It used to work in 1.1.2. Well, using quotes fixed it, but I didn't know I had to make this change.

While i'm at it, I don't really like being forced to click in the answer field during riddles, especially when I explicitely disabled the click answering. I always used my keyboard, A/B/C+Enter straight away, and it's very disturbing.

While i'm at it, I don't really like being forced to click in the answer field during riddles, especially when I explicitely disabled the click answering. I always used my keyboard, A/B/C+Enter straight away, and it's very disturbing.

at a certain point a clickable riddlemaster function was added. did you check if you have it enabled?

quickbarExtend = [ 1,'ikey_1','ikey_2','ikey_3','ikey_4','ikey_5','ikey_6','ikey_7','ikey_8','ikey_9',231,421,1101,1111],

It used to work in 1.1.2. Well, using quotes fixed it, but I didn't know I had to make this change.

it was meant to be used with quotes from the start, i'm surprised your settings worked in previous versions at all

While i'm at it, I don't really like being forced to click in the answer field during riddles, especially when I explicitely disabled the click answering. I always used my keyboard, A/B/C+Enter straight away, and it's very disturbing.

setting clickableRiddlemaster = false should make the riddlemaster behave 100% vanilla. oh, i think this may be because of the ajaxRound setting, try setting that to false and see if it behaves the way you want. if that is indeed the cause i think i can change it to work that way with ajaxRound enabled, just give me time to encounter a riddlemaster

This post has been edited by sickentide: Aug 28 2017, 21:41

DRM is a huge security hole waiting to happen, having it enable for general browsing is a bad idea, when I need it I have Chrome.

It's not there because DRM plugins are not open-source, not for other reasons (including reasons like "security hole" or "bad idea", which are on par with people suggesting to browse without JS).
You can disable it anyway if you're paranoid about privacy/security/whatever so excluding them is like giving less power to the users.
But if you're convinced it's a good thing...

The original goal of Palemoon (before FF started going stupid) was to be a lighter weight faster version and it still something they focus heavily on.

Tests, apart from the useless sunspider, don't give palemoon better scores than vanilla Firefox, and when I tested the Firefox variations (PM, Cyberfox, Waterfox) on HV vanilla Firefox had subjectively the smoother experience.
If you use the word objectively you'd better give objective reasons (or any kind of reasons, not self promotion from the developers).

Australis is objectively garbage (Chrome's UI is pretty bad too, but at least it knows what it is).

Please stop misusing the word objectively, also I never said Australis is particularly good (it's not), it's just that PM default UI is bad (it should have never seen the light of day imho).
The orange (blue) menu has always puzzled me, I understand it was to get more screen real estate, but it was neither really intuitive (basically no other software has that design philosophy) nor as complete as the prior menu bar.
Australis is just too touch/mobile focused (well, pretty obvious after you see the hamburger menu), but at least I can understand why it has been made that way.
But, anyway, I guess you were in the vocal minority that after the Australis update started to complain about the new UX, ignoring the fact that the Firefox UX theme had telemetry and private user tests of both the UI (which is probably what anyone would consider objective), and I can easily see why the new UX won easily against the inintuitive orange mess, it was dated and had to go, UX designers can't please everyone.

FF is constantly adding useless stuff and that stuff comes with a lot of bugs. I you look though the major security bugs for FF very few of them have ever affected PM.

Well, porting from upstream makes having less security bugs pretty easy I'd say.
Anyway, I was not referring to security bugs, PM has its fair share of issues, usually concerning PM own code (media playback in YT, amazon etc etc).
[github.com] https://github.com/MoonchildProductions/Pale-Moon/issues
That would be enough for me to ditch it, but I guess it's pretty subjective and without crash reports statistics it's pretty difficult to really determine how buggy a software really is.

Very few people still use FF, those that do probably have reasons that make Chrome unacceptable.

I don't think many users are that opinionated.
We are talking about millions of users in hundreds of countries, most probably they use FF because they have always used it.
If they are forced to change because of missing features they will switch and never look back.
(well, it will probably not happen since most extensions will work with the new standard, but whatever)

Frankly, chosing between Chrome and Firefox became like choosing between plague and cholera.