@gabriel Interestingly #PaleMoon ignores the styling and description of the #RSS feed, because it is a RSS reader (it never removed that functionality from #Firefox) and has its own styling for feeds. It's not necessarily a bad thing though! If you're using a reader then you probably don't need the styling anyway :sagume_think:
Friendly reminder that XULRunner, the standalone Gecko runtime that once powered web-based applications like Songbird and that was abandoned by Mozilla Corporation has been revived and now builds atop Goanna. Learn more at the Pale Moon forums announcement: https://forum.palemoon.org/viewtopic.php?f=62&t=30913
#CloudFlare is again having trouble working on browsers other than the few they mainly target.
Now did they just decide not to support anything else in "Turnstile" (which is a departure from "Browser Integrity Check", which IIRC had fallbacks), or are they again requiring that all requests include headers only some browsers send?
Affects at least #SeaMonkey and #PaleMoon, and isn't so easy to debug given the minified and changing JS of turnstile (likely intended, but doesn't help here...).
A reminder that #CSSnesting is still a working draft in the #W3C under the #CSSWG. Please mind #webcompat when using this relatively new feature. IOW, don't make your #CSS break because you assumed everyone right now is using the latest version of #Chrome / #Chromium, #Firefox, #Safari, or #Edge. They might not even be using a mainstream #browser to visit your website (I am using #PaleMoon for example)... :seija_coffee:
@gabriel I don't really have the best answer that can apply to all open-source browsers out there; I don't think it can be universal. One thing's for sure though: if they want to rely entirely on donations, that's totally cool! If they want to rely entirely on partnership deals and profits from a corporation, that's fine too, just make it absolutely clear that you're doing that (so no using the exact same name preceding "Corporation" and "Foundation" please).
I can tell you about one browser called #PaleMoon whose monetary model I know well and is simple: development benefits from both donations and a search partnership deal with #DuckDuckGo. However they're able to do this because they don't have to spin-off a corporation to take the DDG money (which probably just number around some thousands of dollars or maybe even just some hundreds, all I know is that donations still make up most of the revenue). And most of the time it isn't really money that is holding back Pale Moon's development, but lack of developers who can work in the CSS and JS engines.
So that's why it's not simple to answer that question. But if you really want an answer, I guess just accept both kinds of money and try to make it legal? Not sure how Mozilla could do that though... And it's not simple to let the browser's development just be entirely funded by donations either, because while there is no doubt a dedicated amount of users who will give out money, I am skeptical it can be enough to sustain the speed of development Firefox is in right now with its 4-week release cycle.
A few years ago Mozilla snubbed bitcoin donations.
Small FOSS projects like #PaleMoon reject donations in cryptocurrency (especially Bitcoin) too, due to how unstable its market price is (gotta convert it back to real cash you know, so you can actually use it to feed yourself) and how it's most notoriously used in crime. It has nothing to do with your conspiracy thinking that corporate influence is somehow behind why FOSS projects don't want your crypto; it's practicality in the real world which from time-to-time again that field has failed to deliver.> Their priorities are clear.
Which is to get real funding, not what is essentially shares in the stock market.
The W3C, founded in 1994 by web inventor Tim Berners-Lee, has quit X and declared the fediverse to be their primary social media channel. Follow them at: @w3c
@fluepke#W3C has pretty much become a rubberstamp for the #Google-led cartel that is the #WHATWG. An organization that doesn't give smaller browsers like #PaleMoon, #LadyBird, and #Lynx a voice in the writing of specs for web standards like #HTML5 and #CSS3 does not deserve support, and should not be seen as an ally of the #openweb.
@f09fa681 Issue #552 of whatwg/html pretty much explains for itself what it means for contributions which don't get "enough implementer interest" in the #WHATWG despite having a significant #webdev grassroots support.
This obsession in making sure at least two "implementers" have the feature baked into their codebases is frankly bull and is one of the factors of why we have such a #Google-biased #web. Theoretically it's there so that every feature would be certain that there are players backing and seeing that feature being useful and good for the #openweb, but in reality it has become Google's veto in most cases, with the popular being one of the victims here. It has been a standard for quite some years, yet Chrome's developers seem to have an extreme case of "Not Invented Here" syndrome and decided not to implement it for whatever reason. Maybe they really don't have an interest in it and are therefore in "patches welcome" mode like a corporation would do in #opensource. Or maybe, they saw it as a threat to their Google #WebComponents because it pretty much satisfies most of the usecases their toy project #ShadowDOM is designed to solve, and web developers don't want to deal with such a complex feature just to limit the scope of their #CSS. Whatever the reason is, this should not kill a feature that has been long-awaited by many web developers to be supported in their #browsers and is backed by a well-maintained and developed #browser (which is #PaleMoon in this case).
Allowing comments in GitHub issues is ultimately useless if the final decisions are made by a closed cabal of big "implementers" who as history has shown has been pretty much Google's lapdogs most of the time.
It's Pale Moon's turn now. This web browser is a fork of an old Firefox version, maintaining some features that Mozilla removed. They've named their Gecko fork Goanna.
And as expected, our site works just fine on Goanna!
God, #Gentoo users are such insufferable people...
elected to bundle an old version [of libwebp]
Really? This PoS makes it sound like #PaleMoon had a choice to not bundle third-party libs.
Hey asshole, maybe you've forgotten that Pale Moon is not just a Linux browser, but also a Windows and macOS one. Tell me how your beloved system libs will help those platforms, you smartass
@mima The intelligence of the average #Gentoo user is astounding. And the fucking entitledness too.
If you're really worried so much about that libwebp vulnerability, then patch it yourself? Or use make it use system libwebp? For the latter though, you're just not allowed to call it #PaleMoon.
For one of the popular forks of Mozilla Firefox, we have WaterFox Automatic Install for Linux, which allows you to install a pure stock, unmodified copy of WaterFox for your choice of either a system install or personal installation with automatic updates.
For another Mozilla Firefox fork, often recommended for older systems, we have Pale Moon Automatic Install for Linux, which provides you a pure stock, unmodified installation with your choice of either performing a system or personal install, along with automatic updates.
Anyone working on a new browser engine?
Something that's definitely not Chromium.
I quite like Goanna and WebKit. Wish both had more devs behind it. Goanna is very light on resources though, but can struggle with these 6 TB perpetual JavaScript websites of today. #goanna#palemoon#luakit#Epiphany#Gnome