I never heard of Pale Moon before! (I don’t get out much! )
Thank you for letting us know Pale Moon doesn’t work. Since it is Firefox based I am surprised it doesn’t work.
Honestly it would be much better to let Discourse know. It would be Discourse that would make any changes. I believe their https://meta.discourse.org/ has a site feedback section also.
Discourse also no longer works with SeaMonkey which is a Firefox fork.
Discourse gives the message that my browser is not up to date, even though it is because it follows the updates that Firefox implements.
In the past I have flagged up at Discourse that SeaMonkey didn’t work with it but never got any response.
Maybe I will try again.
Currently I use SeaMonkey for most things but I also have to have Firefox for accessing this forum and also for doing some payments because some payment sites end up not working with SeaMonkey, probably because they are doing all sort of popup type stuff.
Platform A is continuously developed and aimed for at least what we call Web2.0
Platform B is a tiny oddball clinging to the past that some use due to obscure claims “things was better 10-15-20-30 years ago” and not adopting modern tech, albeit still being developed and making people believe their approach is somehow “better”.
Now, having said that, I am not a fan of Discourse either, but I feel you are being very unfair when you claim it’ Discourse’s fault that SeaMonkey and Palemoon have issues with it.
SeaMonkey never used to have issues with the IPFire Discourse forum. I used to do all my input etc via SeaMonkey since the IPFire forum started using Discourse.
A few months ago Discourse decided that for any browser that is not on their supported list they will no longer serve the full html pages to you or serve the login page, just a very slimmed down web format only.
I admit web 2.0 is a bit of an ambiguous expression, but…
Really… ?
Pale Moon originated as a fork of Firefox, but has subsequently diverged. The main differences are the user interface, add-on support, and running in single-process mode. Pale Moon retains the highly customizable user interface of the Firefox version 4–28 era. It also continues to support some types of add-ons and plugins that are no longer supported by Firefox including NPAPI plugins such as Adobe Flash Player as well as legacy Firefox extensions.
I don’t have to know when I can read. I see nothing that changes my opinion. Flash Player?
Also, the XUL framework has proven a hindrance for future development of both Firefox and Thunderbird and thankfully they are, and have, dropped that so we can finally see a more modern codebase for Thunderbird, which I personally have tried to use numerous times, but had to drop due to this hindrance in plugin and extension development.
Despite the removal in Firefox Quantum of support for XUL-based legacy add-ons in favour of WebExtensions, the stable/ESR release of Thunderbird 60 in mid-2018 continued to support them, although most would require updates, and it did not support WebExtensions except for Themes.
So it is not as easy as “I use this browser because I like it”, when the underlying tech is so interconnected and do not let the browser itself evolve as it possibly could and may also be a hindrance for other, related, development.
On a sidenote, the only reason I know abut XUL is because I once a few years ago read up a bit on what was stalling the plugin development. Bit off topic, I know.
All in all, you can’t expect relatively small players in this market segments to be able to have a strong development and support later, or even most, web technologies out there. They are way below 1% and even if looking a bit in to market shares, and finding no numbers for SeaMonkey or Pale Moon, I would suspect that in regards to market scrutiny’s by StatConter and other agencies, they both fall within the Firefox share. It depends on how they declare themselves to the world.
On the other hand, you can, equally, not blame Discourse for focusing it’s compatibility on the remaining ≈ 98% of browsers.
So keep using what you will, but do not expect everything to work as expected. Many corporate sites are still optimized for Internet Explorer, I hope that is no big surprise…That is why Edge still has the IE Mode button.
To me, privacy and security goes firmly behind my browser choice. Functionality comes third, but if a browser has issues with presenting information I really want to read, like this forum and the IPFire site, well, I can ask the owners if they know about this and it’s causes and if they can do anything about it.
If not, I find a way to read it anyway by using an alternative browser. It is a nuisance of course.
@sec-con is correct in that technology changes over time.
Some thing fall out of favor and disappear.
You may have to look into another browser.
Like
Midori or Canary
Or Brave.
I have bin a long time firefox user
But their browser on mobile sucks.
A modern browser must be mobile friendly
When half of all internet traffic is on mobile devices.
Firefox really needs a overhaul.
I may have to give Opera a 2nd look.
@hvacguy
one can not stop the change, it is futile and not the point here
but the changes must not enslave the users
to act as a follower of the 98% monopoly one can not escape the dilemma
and silly me thought ipfire is an escape to the dilemma
to scetch the ‘conflict’
use ipfire and to participate to the community use edge or chrome
or firefox (but better not it is a dead end )
Don’t blame IPFire for decisions Discourse have taken.
When the forum was changed over to Discourse a large variety of browsers worked with Discourse. They usually gave a warning that the browser was out of date and might not work correctly but I never had any problems ever.
More recently Discourse took the decision to block any browser that was not part of a small list. That is their choice to make. We can all give Discourse our input on this but I suspect there will not be a large enough number of inputs to make much difference.
We will all have to live with that. Changing from Discourse to another forum system is unlikely to be considered due to the amount of work involved in doing so, which would divert the focus and energies of the small group of developers supporting IPFire.
@bonnietwin i am aware of the very limited resources and do not blame ipfire
if time comes and new decisions must be made this very site feedback must not be ignored
and exactly as you wrote: their choice and not enough