Invidious is currently broken due to Google changing things trying to stop 3rd party clients. But eventually Invidious will catch up and Google will give up for a bit.

yea considering its FOSS it was good enough compared to a lot of the other clients for me to move away from Symfonium

https://github.com/CappielloAntonio/tempo

Waterfox is a neat project, but is often slow to implement security patches from Firefox upstream.

Materialious doesn’t use remote fonts by default, only as a backup if local font loading fails. For some reason ublock in hard mode makes local font fail loading & remote font is used.

Materialious contains zero trackers. Believe this was a issue with ublock falsely flagging local fonts as trackers or something, someone else open a issue on the repo with a similar issue. Feel free to review the source code for any trackers.

It requires the Invidious instance to have the correct COR values for Materialious, but yes connects to a existing instance.

Materialious does currently just use Invidious’ API. If extending it requires a custom backend it will be a completely different project (what will still be using Invidious)

Isn’t just a theme, is a completely different application built on top of Invidious’ API. What works completely differently to Invidious’ current UI. A LOT of things are handled different then how Invidious handles it on their frontend. Replacing Invidious current interface with Materialious isn’t a good idea, because its quite a bit bigger & requires JS compared to Invidious’ current UI.

Calling Materialious a theme would be like calling clipious a theme.

I believe loading videos directly works, but discover/trending doesn’t to my understanding.