talospace.com/2021/11/51552-javascript-tests-cant-be-wrong.html SeaMonkey PPC port when!?

tomman all good on paper only unless you can buy hardware at an at least ok price. Same with arm. Other than tinker systems like the rasberry nothing on the market.

it's the same case of those "Respect Your Freedom" cellphones: noone cares about FOSS firmware and open schematics if you can't buy one in over half of the planet (and in the few places where you can, the pricetag means "freedom costs money, so not really freedom")

but hey, makes nice clickbait for Hackernews and FOSS blogs

I suggest tomman becomes leader of the SeaMonkey Project and frg_Away has to report to him

lolno

tomman knows the fuckin score

why not?

you don't want to be my subordinate, believe me

well I WOULDN'T be

frg would tho

and I would like to see that

you don't

but i do

i really really do

that's a very weird pastime, yo.

Hey, so I saw that the shadow on the 17th of nov asked about an error with bitchute resulting in not being able to play videos, I wanted to bump that to see if he or anyone else had worked around it.

Error:

TypeError: window.Plyr is not a constructor

Errors only present when running firefox, specifically I went to another state and used a different computer to access my account, and upon return I was unable to watch videos on firefox, still able to watch them with Midori, any help?

Hey, so I saw that "TheSHADOW" on the 17th of nov asked about an error with bitchute resulting in not being able to play videos, I wanted to bump that to see if he or anyone else had worked around it.

Error:

TypeError: window.Plyr is not a constructor

Errors only present when running firefox, specifically I went to another state and used a different computer to access my account, and upon return I was unable to watch videos on firefox, still able to watch them with Midori, any help?

BitChute work-around by cartel, forum.palemoon.org/viewtopic.php?p=221844#p221844

ohnoez, I'm famous :D

Hello, is it normal that ChatZilla on SeaMonkey (2.53.10) doesn't read SeaMonkey's SSL certificate exceptions?

I added an exception for the GameSurge's SSL certificate but ChatZilla still says that the certificate is invalid although SeaMonkey properly recognizes the certificate as valid thanks to the exception.

FoxMcCloud45 check if Bug 1738597 applies.

frg_Away This bug does happen but I already added 563 and 6697 to the variable so I could add NNTP and IRCS exceptions; the exception exists in SeaMonkey, it's just that ChatZilla doesn't seem to see it.

FoxMcCloud45: is there information about the irc server for GameSurge somewhere?

IanN_Away Yes, here: gamesurge.net/servers . Only the Prothid.NY.US.GameSurge.Net supports SSL/TLS over 6697.

The SSL/TLS certificate exception in SeaMonkey reports StartCom Ltd, and an expiration date in December 2019, so I'd say it's configured correctly.

Okay I found the problem and solved it

The Network was registered with capital letters, as specified on the website: Prothid.NY.US.GameSurge.Net

However, the security exception applied to the lowercase domain: prothid.ny.us.gamesurge.net

So I changed the server address from the former to the latter and it works now.

Thanks for your time nevertheless, sorry for bothering you.

FoxMcCloud45: I don't think it should make a difference

I guess it shouldn't but it does, for some reason

Most likely a string comparison in ChatZilla

* a strict string comparison in ChatZilla

FoxMcCloud45: yeah, need to some forcing of lowercase I think

+do

OK, managed to get BitChute working here, now that I reviewed it a bit

of course it gets stuck loading because (most likely) of the broken regex or something

but if you use the Inspector to hide the loading DIV (id=loader-container), and clear the opacity:0 on .transparent class, you'll be able to watch the video

while the definitive fix (again: most likely) will be to figure what JS it wants to get implemented (could be the regex capture group, could be something else?)

at least the site isn't THAT broken, and can be used with a little bit tampering

(but the best way is to avoid using web browsers to watch videos in first place - mpv+yt-dlp are your friends!)

the site fully loads, but whatever JS breaks does break near the very end, so the loading DIV never goes away

the other relevant JS error is: TypeError: window.Plyr is not a constructor

ah, so this is a Plyr: cdnjs.cloudflare.com/ajax/libs/plyr/3.6.9/plyr.polyfilled.min.js

...and indeed our broken regex is there

so yeah, indeed it's the missing support for capture groups breaking the flow on that 3rd-party lib

CLOSED WONTFIX USECHROME HEALTHYWEBECOSYSTEM

you can't catch regex errors if the regex is in the form /...your regex here..../

BUT!

you CAN if you use the construct new RegExp("...your regex here...")

developer.mozilla.org/en-US/docs/We…erence/Global_Objects/RegExp/RegExp oh, so literal notation will force compilation of the regex, and any errors from it aren't catchable

while the RegExp constructor is meant for dynamic/user supplied (*shudder~*) regexes

I tried to remember one website which got better because of a general ui / branding update in the last two years or so and failed to come up with one. All I see is either bloat or mobility first with a forked up desktop experience. And I really like functional updates and not against visual ones either.

TIL

the whole problem would have went away if only devs bothered testing on OMGOLDDANGERMINES, er, ALTERNATE browsers more frequently

use your fancy regex on a constructor

it throws? It means your client is using Not Chrome or old Firefox... or something else!

catch it, and do something (anything but "please upgrade!")

reminds of my former dayjob, where SeaMonkey was my lead dev browser, with Chrome on a second display for testing

and if needed, VMs with IE11, IE8 (yes, we still had to support it... although eventually its need went away as noone was actually using it), and latest Firefox

...good luck supporting IE (or Windows browsers in general) from your fancy new M1 Macs, tho - I guess you can always rent VMs in The Cloud™

tomman well we are behind with development and hard to justify to test for 0.01% market share browsers. But the real problem is mozilla basically destroyed the codebase to become a chrome clone and it is either follow them and loose your identity or fork.

frg_Away: and that's what we get when we let MICROS~1, er, Alphabet, Inc. dictate the web standards. Sadly devs love shiny, even if only less than 10% of the new web standards additions are genuinely useful

Not sure to understand what you mean. SeaMonkey cannot integrate the new Firefox engine, or are the developers not willing?

Or will SeaMonkey end up like Pale Moon?

capture groups? Cool. WebUSB? Battery API? Web components?! Useless bloat!

FoxMcCloud45: it's hard to do things when manpower is VERY limited, and your upstream (that's Mozilla) insists into reinventing the wheel every week to please their Google lords

not a dev, but from what I've seen, backporting stuff from recent FF releases is becoming a uphill struggle thanks to Mozilla stubbornness to become Chrome

I don't really know how Firefox evolves internally to be honest, I thought they sticked with Quantum/Servo and that's it

doesn't help that Google and folks have declared the web to be a Living Standard, that means, there is not a set of standards set in stone and you code against those

nope, you get new useless bloat and APIs added nearly monthly

pure madness

Hmm. What about WebKit stuff?

FoxMacCloud We still update for an eventual comm-central release but it is an uphill battle and not enough people around. But so much is gone upstream that I am not sure I even want it. Full themes, basic ftp support, some bookmark fields, xul extensions and and and. Web extensions don't cut it and are only good for content and it will be very hard to support them outside of the browser component.

^

Does that mean that supporting "Web extensions" would imply needing both a "Firefox XPI" for the browser component and a "Thunderbird XPI" for the rest?

FoxMcCloud45: it's a completely different standard, less powerful

I know uBlock provides different XPIs for both softwares.

and really meant for web browsers

and web browsers only

with a ton of features crippled by design

Well yeah, but Google literally owns Web standards now though. So much for Chromium/Blink/V8 adoption.

and the never-ending threat from Google to cripple the standard even more, in the name of "sekuritah"

Security is just a way to justify changes for their own interests, though.

Some hybrid. Thunderbird calls them mail extensions but the functionality they provide is basically all implemented in TB itself. It is not all "lego" only but foundation would need to be provided by SeaMonkey. I can see it for the browser part but have a hard time to see it for integrating mail apis without 5 to 10 people working on it.

Can't wait to see how the Privacy Sandbox will be a fun tech to manipulate. /s

FoxMcCloud45: bug 1742502 if you are interested in the fix for cZ

Short of getting Google/Alphabet dismantled a-la-Bell System, it's only gonna get worse :/

Thanks for creating the issue IanN_Away , I don't think I have access to my Bugzilla account anymore anyway.

Nevertheless, we're going off-track. The matter is SeaMonkey's development.

Sometimes I think SeaMonkey should do a Patreon or something, but the problem (as I see it) is not money, but manpower

From what I understand, Mozilla's deep changes into the Firefox codebase makes it hard to integrate in SeaMonkey, and some features like WebExtensions are downright impossible.

we just need more people, particularly devs well versed into the Mozilla codebase

So, essentially getting Mozilla devs to work on it.

Wonder what those laid off Mozilla devs from last year are doing nowadays...

FoxMcCloud45 we do what we can for sure. Webext is not impossible but all the frontend code needs to be reimplemented and/or ported.

FoxMcCloud45: not necessarily impossible, just brain mushing

I see. So, essentially a huge pile of hard work.

not for the faint of heart, and definitely too much for an one-man army

yes or we would have a 2.57 by now. But is is either to update 2.53 and keep it halfway up to date or not relasing anything for a year or 2 or 3.

Oh yeah, 2.57 is the build in development for a long time right? With a beta version on wg9s.com

Basically a pre alpha and not feature complete.

Especially if its scope also evolves as Firefox goes on.