Comment on Expanding Materialious to other platforms
Scolding0513@sh.itjust.works 6 months ago
I agree with Mora. it’s a really bad idea to make this in a whole different project. it splits up communities, creates confusion, and reduces anonymity sets.
Why not work with the invidious team and get your theme added to the project, and maybe contribute the other changes you may have made?
god knows invidious needs a way better UI/UX anyway
Ward@lemmy.nz 6 months ago
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.
Currently Materialios a theme would be like calling clipious a theme.
Scolding0513@sh.itjust.works 6 months ago
yeah but clipious just connects to existing invidious instances, so it’s just a frontend to invidious. you are making your own frontend and backend both
Ward@lemmy.nz 6 months ago
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)
Scolding0513@sh.itjust.works 6 months ago
does it connect by default to already-existing invidious instances? guess im confused now