I like the idea of materialious and am interested in its expansion into other projects (does proxitok even work right now?). But I would prefer it if it was more of a theme for each project instead of a new service, though adding in features aside from theming would probably be harder🤔
Yea, Materialious is a bit more complex then a theme as it has a lot of custom client side logic (Like sync parties, playlists, etc).
If I expanded Materialious you'd still be able to use just Invidious or Safetwitch etc.
But Materialious at its core would still be built off the API of giants. So it wouldn't be reinventing the wheel for scrapping/handling data from twitch, YouTube etc.
Haven't used Proxitok in a while, so not sure if its working currently. ~~Seems to be in active development tho.~~ Misspoken, doesn't appear to be working & hasn't been updated in awhile
I used ProxiTok just yesterday, and it loaded the video fine.
I believe loading videos directly works, but discover/trending doesn't to my understanding.
The prospect of an unified frontend for all social media is also kind of appealing, ngl😄
Yea just need to avoid it from being bloated. The idea would be to have a global feed, what you can filter by platform.
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
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.
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
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)
does it connect by default to already-existing invidious instances? guess im confused now
It requires the Invidious instance to have the correct COR values for Materialious, but yes connects to a existing instance.
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
Additional Resources: