ACNetGLSL VS YouTube.js

Kind of unrelated, but how difficult do you think it would be to hack support for glsl shaders in a browser? I tried to look into it once, but got a bit lost in the media source side of things. My idea was to try to add glsl shaders as post processing to video streams like in mpv but without having to jump through all the hurdles of passing data to mpv.

Example of a shader I was playing with https://github.com/TianZerL/ACNetGLSL

I'm not sure if what I'm doing is wrong or if there's something wrong with the shader itself but I can't get it to apply on the video, it states on the page that you're supposed to check using Shift + I then 2 to see if it's enabled (and from my experience, there's supposed to be something like 'user shaders') but I don't see any. I'm using portable setup but I've placed the shaders on both my portable config and %appdata% folder, but still no luck.

Shader version for Mpv version is here

shader

BTW, I don't understand the workaround: https://github.com/iv-org/invidious/pull/4552/files

Which was taken from here: https://github.com/LuanRT/YouTube.js/pull/624

Could anybody explain it to me?

There is a javascript library for interfacing with Youtube's API directly. It can also run on browsers. Using this, it's pretty easy to create a simple extension that replaces the default video player with your own. You can do a lot to improve your experience this way. I've made one which allows for higher quality streaming, pre-buffering video in the background, more subtitling options, etc... [2].

[1] https://github.com/LuanRT/YouTube.js

You can try Tod usw this youtubei.js

Love this approach. We can just bypass all the normal web scraping and get the structured data straight from the source. These APIs are usually no less stable than the ever changing HTML structure anyways.

Case study: YouTube.js

https://news.ycombinator.com/item?id=31021611

https://github.com/LuanRT/YouTube.js