Welp, there goes VORAPIS.

[Kxeon]

Drats. Looks like they dropped support for Pale Moon. Not only does Pale Moon not work with V3 anymore, now guess what; they're apparently also preparing to drop userscripts altogether.
MTube doesn't work anymore either so basically I'm stuck with the regular, yet stupid laggy, YouTube.
Womp womp.

[moonbat]

There's still the polymer engine fixes userscript. Although not as great, it does let you customize a lot and loads faster.

[frostknight]

Or you can use a youtube-frontend like invidio, piped, etc...

They aren't great, but at least they don't lag like crazy.

Google does try to block them, but unless you plan to comment or similar, they are better.

[andyprough]

Or you can use a youtube-frontend like invidio, piped, etc...

I still find the best way is to install mpv and yt-dlp and then use mpv commands from the terminal to see the videos.

[Moonchild]

The brief time I checked it out (with the greasemonkey script) it didn't work at all, so I'm not even sure what we lost.

[vannilla]

VORAPIS was good for normal videos, lives were hit and miss and embeds were broken altogether for me.
Ultimately I use "YouTube web" only with embeds because everything else I do with FreeTube. Yes, it's Chrome in a trenchcoat, but between a Google service spying on me and lagging my browser and a Google service spying on me without interfering with my browser I'll take the second option.

[moonbat]

The brief time I checked it out (with the greasemonkey script) it didn't work at all, so I'm not even sure what we lost.

It's like a time machine for Youtube - takes it back several years ago to what was more desktop focused - information dense, compact and vastly more functional.

Youtube with Vorapis.png

[jobbautista9]

It's a shame that they're taking out userscript support, it made YouTube a lot more usable for me. That said it seems the script's developers are blaming it on the Greasemonkey we're using, since the WebExtensions version apparently works perfectly fine in the last 52 ESR of Firefox. Are we really stuck forever with 3.31.4 for Greasemonkey?

[frostknight]

It's a shame that they're taking out userscript support, it made YouTube a lot more usable for me. That said it seems the script's developers are blaming it on the Greasemonkey we're using, since the WebExtensions version apparently works perfectly fine in the last 52 ESR of Firefox. Are we really stuck forever with 3.31.4 for Greasemonkey?

What a copout, its not their fault or palemoon dev's fault. Its just power hungry corporatist youtube executives and their even greedier ceo, etc...

Basically, rich aholes being rich aholes.

[moonbat]

Its just power hungry corporatist youtube executives and their even greedier ceo, etc...

Basically, rich aholes being rich aholes.

What does the Vorapis dev not wanting to support an older Greasemonkey for userscripts have to do with Youtube's executive management?

[frostknight]

What does the Vorapis dev not wanting to support an older Greasemonkey for userscripts have to do with Youtube's executive management?

I was commenting to jobbautista9

It had nothing to do with vorapis. My bad... should have put off topic I guess.

[moonbat]

It would help if someone could update the Greasemonkey that PM uses to be compatible with the current upstream version, sadly I don't see that happening

[vannilla]

It would help if someone could update the Greasemonkey that PM uses to be compatible with the current upstream version, sadly I don't see that happening

Greasemonkey is a mess that's very hard to work with. Source: I read the source code to the point of being able to find where some features are.

The code quality is not great, but most importantly you when you read it you can really see Mozilla's modus operandi that still continues nowadays.
GM started as your usual toolkit extension, it used XPCOM and all that. Then Mozilla announced that the future was using framescripts or something, so extensions got ready for that and moved everything out from components to framescripts. Then Mozilla announced that rather than using the venerable object interfaces you'll have to use some pure javascript singleton, so extensions started moving everything to this object. Then while people were still working on it, Mozilla announced the end of toolkit extensions and everyone just dropped everything and started anew with webextensions.
That's the legacy of "legacy" extensions: people struggling to keep up with Mozilla's arbitrary decisions and leaving a mess, only for Mozilla itself to leave it all behind without letting people patch things properly. It's the equivalent of producing industrial waste and leaving it to pollute the environment.

[Moonchild]

If that's the case, can't it be forked from a point before they did all this, and get a pure XPCOM extension? Nobody says they must use the latest iteration as a starting point.

[Nuck-TH]

It won't have newer GM API features. Which means that even less modern scripts will work.

[vannilla]

If that's the case, can't it be forked from a point before they did all this, and get a pure XPCOM extension? Nobody says they must use the latest iteration as a starting point.

Probably, yeah. Depends on how far back you go as the packaging and installation of Firefox et al. extensions changed at some point in time (of course).

It won't have newer GM API features. Which means that even less modern scripts will work.

Not like they are available now, you just need to implement them. If anyone steps up to make a fork, that is.

[Kxeon]

New Info:
Someone has created a version of V3 that comes in extension form instead of userscript form! It works quite well and actually fixes that stopping problem!
Apparently it's because of the token being generated correctly this time instead of not working at all and being null.
It's a test version, thus why I'm not posting it here. I wonder if I should?

Here's the transcription of some of the troubleshooting thread from the V3 Discord (only a portion of it, after the xpi was sent):

[23:07] Gastroschisis?: @pandakekok9 @Forte @Kxeo @Nuck-TH Let me know if it works. Keep in mind that it's only a test version, quickly put together to confirm it functions better than the god-awful greasemonkey solution.
File Type: unknown
turbolauncher.xpi
13.59 KB
[23:23] Forte: ok video playback has lasted longer than 40 seconds, that's a step up
[23:24] Gastroschisis?: That's a massive understatement.
[23:24] Gastroschisis?: It generates a potoken properly, which means the player won't crash.
[23:24] Gastroschisis?: And it's a native firefox extension.
[23:25] Forte: excellent
[23:25] Gastroschisis?: So it's going to be faster than greasemonkey or any script ever could.
[0:14] Niko: You can even embed native code in those old Firefox extensions
[0:14] Niko: Only thing they had going for them
[0:15 rnornrny: wow a quick turnaround
[0:16] Niko kirasicecreamm: Wdym quick turnaround?
[0:19] rnornrny: after many decades of v3 being terrible on pm it just becomes normal
[0:20] Niko: Well, yes
[0:20] Niko: You could optimize it very well for Pale Moon
[0:21] Niko: Reprety could rewrite all of V3 in x86 assembly just for Pale Moon users
[0:21] Niko: And it would ironically be the fastest version of V3
[0:23] Gastroschisis?: reprety wouldn't ever want to have anything to do with making v3 work on pale moon.
[0:24] Gastroschisis?: understandably so
[0:24] Gastroschisis?: he's not a masochist like me
[0:25] Niko: Would you rewrite V3 in x86 assembly?
[0:25] Niko: I wouldn't
[0:25] Niko: x86 assembly is horrifying
[0:26] Niko: And you're better off doing the majority of work in C
[0:34] Gastroschisis?: "This" was pale moon, not assembly.
[0:35] Gastroschisis?: Not for free no.
[1:01] Gastroschisis?: That would be a full time job for months at the least.
[5:21] Reprety: i wouldnt write anything in assembly
[5:21] Reprety: lol
[6:35] rnornrny: thats just a evil task

I have a feeling sooner or later, a special & complete version of the extension will be released. Hopefully.

[moonbat]

Someone has created a version of V3 that comes in extension form instead of userscript form

You mean web extension form. That's irrelevant for UXP browsers.

[jobbautista9]

No, one of the devs in the Discord made a separate restartless xpi that is compatible for Pale Moon (though the install.rdf still only targets Firefox for some reason, probably didn't know what PM's UUID is). It works perfectly again like the userscript before.

I would link the xpi here, but I'm gonna wait for the dev's permission for that.

[moonbat]

Woah, that's great news indeed! Showing PM some love!
Is there a link?