Legacy XPI release of Project V3 [ VORAPIS ]

[v3core]

Hi! As there are a few Pale Moon users of V3 (Old YouTube Layout), we are thrilled to release a version of the V3 Launcher (Auto-Update) in legacy XPI extension format.
You can download it here:
https://vorapis.pages.dev/#/home/download
( the direct link is: https://vorapis.pages.dev/auto_redirect_vlturbo_xpi_revision )

Hope you like it, and that this post isn't against the forums rules ^^

[jobbautista9]

Very nice, thanks! I've switched from the userscript version to this one and it works the same so far.

You might also want to consider having your extension indexed in the add-ons site by the add-ons team, as documented in http://developer.palemoon.org/addons/si ... r%20add-on

[tellu-white]

( the direct link is: https://vorapis.pages.dev/auto_redirect_vlturbo_xpi_revision )

The direct link is:

https://vorapis.pages.dev/product/v3/game_service/patcher/PatcherJSC_TURBO_250624.xpi

[v3core]

Very nice, thanks! I've switched from the userscript version to this one and it works the same so far.

You might also want to consider having your extension indexed in the add-ons site by the add-ons team, as documented in http://developer.palemoon.org/addons/si ... r%20add-on

I was actually hoping someone would mention where is guide to publish an add-on, but sadly I got an error:
Unable to Comply
Jetpack (Add-on SDK) style extensions are not supported
when i try to upload it to https://addons.palemoon.org/panel/addon ... what=addon

[sinfulosd]

I'm getting an (Internal Error) error page, trying to download the extension to my browser.

We really need a direct download link of the extension to our official add-on website and/or atleast a direct Git link for it as well.

Edit: It's working now, but the point is still the same here.

[v3core]

I'm getting an (Internal Error) error page, trying to download the extension to my browser.

We really need a direct download link of the extension to our official add-on website and/or atleast a direct Git link for it as well.

Edit: It's working now, but the point is still the same here.

Here is the fully local version of the extension, but is WebExtensions ManifestV2
https://vorapis.pages.dev/auto_redirect ... e=20250628

So I don't think it can function in old Firefox without Launcher

[UCyborg]

Extension version doesn't work at all if browser is set to not store history.

Also user script version suddenly stopped working, all I see are GET requests leading to Vorapis.user.js download, but page just stays blank, no errors in console except complaint about unrecognized require-trusted-types-for directive. The browser has been open since last Monday. CTRL + F5 doesn't change anything. It works in the freshly opened new instance of the browser. Mind you, I'm not trying to use both user script and extension at once.

The year is 2025 and still we can't expect the software to function correctly over longer running period. Things haven't changed much since the days of Windows 98.

[MasterSlenderTR]

Extension version doesn't work at all if browser is set to not store history.

I thought I was the only one with that problem (see viewtopic.php?f=3&p=263645) it’s crazy that it was caused by having the history disabled.

[v3core]

The year is 2025 and still we can't expect the software to function correctly over longer running period. Things haven't changed much since the days of Windows 98.

I am sorry that V3 doesnt work for you, I suggest disable the history settings.
However, I dont understand this arrogant remark about "in 2025 still dont work well" given you use a browser that follow 2016 web standard with extra settings that again change the normal way website work.
I have tested both Firefox 52 and Chrome 49 a lot while developing V3 and it seems to be in a functional state, but I cannot guarantee perfect support, especially since this browser cannot run WebExtensions MV2 (making it nearly impossible to debug in the first place).

[Moonchild]

The year is 2025 and still we can't expect the software to function correctly over longer running period. Things haven't changed much since the days of Windows 98.

That's a very narrow view of the world you have, there ;P

you use a browser that follow 2016 web standard with extra settings that again change the normal way website work.
...
this browser cannot run WebExtensions MV2 (making it nearly impossible to debug in the first place).

I'm sorry but your own view of this project is incorrect as well. We aren't following 2016 web standards (and we aren't a Firefox 52 rebuild). The fact that our latest fork point was back then doesn't mean we've been sitting on our hands since then.
Just because we've made the decision to keep powerful XUL extensions alive and not to adopt a limited (and actually risky) hybrid of web tech and browser UI extensions that are akin to trying to force a square peg into a round hole, doesn't mean we've been standing still as a whole. I know it makes it difficult for add-on developers to keep native compatibility because they have to target different extension technologies, and I do really appreciate the effort you're putting in to having a native XPI available for UXP-based browsers, but please do try to see it in the context it's in, and that Pale Moon is actually a modern browser that adopts sane current web standards as much as possible.

As for the add-ons website; the Jetpack error is because Tobin explicitly excluded acceptance of these types of extensions when designing Phoebus (the add-ons website software). We can look into disabling that check and allowing jetpack extensions but it'll need time to work through the code and see if there are specific issues with the jetpack format in terms of the manifest processing or not.

[MasterSlenderTR]

I suggest disable the history settings.

Is it not possible for the extension to work without relying on history? As far as I know, no PM extension ever relies on history, so I think it'd be better to update the extension for making it not depend on the history feature.

Also, thanks for creating the extension since it's rare to see new XUL extensions these days.

[MasterSlenderTR]

You use a browser that follow 2016 web standard with extra settings that again change the normal way website work.

Fyi, Pale Moon supports new web standards such as WebComponents (https://developer.mozilla.org/en-US/doc ... components) and Firefox 52 from 2017 doesn't.

[v3core]

I suggest disable the history settings.

Is it not possible for the extension to work without relying on history? As far as I know, no PM extension ever relies on history, so I think it'd be better to update the extension for making it not depend on the history feature.

Also, thanks for creating the extension since it's rare to see new XUL extensions these days.

The only explain possible for V3 dont work with the settings is that it also affect LocalStorage functioning, V3 cannot work without LocalStorage Api

The year is 2025 and still we can't expect the software to function correctly over longer running period. Things haven't changed much since the days of Windows 98.

That's a very narrow view of the world you have, there ;P

you use a browser that follow 2016 web standard with extra settings that again change the normal way website work.
...
this browser cannot run WebExtensions MV2 (making it nearly impossible to debug in the first place).

I'm sorry but your own view of this project is incorrect as well. We aren't following 2016 web standards (and we aren't a Firefox 52 rebuild). The fact that our latest fork point was back then doesn't mean we've been sitting on our hands since then.
Just because we've made the decision to keep powerful XUL extensions alive and not to adopt a limited (and actually risky) hybrid of web tech and browser UI extensions that are akin to trying to force a square peg into a round hole, doesn't mean we've been standing still as a whole. I know it makes it difficult for add-on developers to keep native compatibility because they have to target different extension technologies, and I do really appreciate the effort you're putting in to having a native XPI available for UXP-based browsers, but please do try to see it in the context it's in, and that Pale Moon is actually a modern browser that adopts sane current web standards as much as possible.

As for the add-ons website; the Jetpack error is because Tobin explicitly excluded acceptance of these types of extensions when designing Phoebus (the add-ons website software). We can look into disabling that check and allowing jetpack extensions but it'll need time to work through the code and see if there are specific issues with the jetpack format in terms of the manifest processing or not.

Thanks for clearing it up

[UCyborg]

I'm just being realistic, I don't sugar coat and I'm certainly not politically correct. While my remarks are never meant to be offensive, people seem to quickly take it so.

Anyway, I've been observing the software since I was the kid, so well for over 20 years now. Major part of my day job is dealing with complaints how this or that doesn't work properly in the software that's developed at my workplace. It's the same old song over and over again.

I used to spend my free time fixing bugs in old games, all at x86 assembly level. Modern Samsung smartphones have periodic reboot programmed as part of the maintenance. My car's infotainment occasionally reboots out of the blue.

So, nothing Pale Moon specific, you see glitches EVERYWHERE. I just happened to have my browser recently opened for longer than usual and I pointed out my observation.

Though extension not working in private mode is interesting, nothing in the extension code screams "don't work in private mode".

Don't get me wrong, I'm a happy user of VORAPIS, I took turbolauncher.js from the old version of the extension before you released it officially and use it as user script, that generally works with history on or off. I'm of opinion user script is sufficient unless the extension can offer deeper integration.

The year is 2025 and still we can't expect the software to function correctly over longer running period. Things haven't changed much since the days of Windows 98.

That's a very narrow view of the world you have, there ;P

That was slight exaggeration, but some patterns repeat.

[sinfulosd]

I used to spend my free time fixing bugs in old games....

Off-topic:
Are you the same person who made this patch for max payne, since the author of the patch has the exact same name as yours, written in the exact same way?

[UCyborg]

Off-topic:
Yup, that's me.