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.
Yea just need to avoid it from being bloated. The idea would be to have a global feed, what you can filter by platform.
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
Maybe with the Materialious frontend
https://github.com/WardPearce/Materialious
Cough cough might be a plug
Home page is the "popular" page what is pulled from Invidious' API. Basically just the popular videos people have been watching on that instance.
I enjoy confusing people.
Yes anyone can host Materialious on their own server! Does require you to host Invidious too.
For the last month I've been working on a modern, material you interface for Invidious.
Github (Leave a star if you want)
For the last month I've been working on a modern, material you interface for Invidious.
Github (Leave a star if you want)
For the last month I've been working on a modern, material you interface for Invidious.
Github (Leave a star if you want)
For the last month I've been working on a modern, material you interface for Invidious.
Github (Leave a star if you want)
For the last month I've been working on a modern, material you interface for Invidious.
Github (Leave a star if you want)
Github: https://github.com/WardPearce/Purplix.io
View our canary: https://purplix.io/c/purplix.io/3ZjhTlZRWv8iqa6sn9yJ3TRiIkVbwITOOlwLjJD36jQ
Purplix Canary is a free & open source warrant canary tool what helps you to build trust with your users.
It allows you to inform users cryptographically if your site has been compromised, seized or raided by anyone.
Purplix uses DNS records to verify the domain the canary is for, giving your users confidence they are trusting the right people.
Each domain is associated with a unique key pair. The private key is generated locally and securely stored within the owner's keychain. When a user visits a canary from a specific domain for the first time, their private key is used to sign the public key. This signed version of the public key is then automatically employed for subsequent visits, effectively mitigating man-in-the-middle attacks and ensuring the trustworthiness of canary statements from the respective domain.
Canaries can include signed documents to help users further understand a situation.
Users are automatically notified on the event of a new statement being published.
Visit our site: https://purplix.io
Support us on Github: https://github.com/WardPearce/Purplix.io
Purplix Survey is a free & open source survey tool what can't read your questions & answers.
With traditional surveys you are one data breach, one rouge employee or one government warrant away from all your user's data being exposed. Purplix uses modern encryption techniques to keep your user's data away from any actors.
When you create a survey, we encrypt your title, descriptions & questions with a secret key. This key is then stored encrypted in your keychain. When you share your survey with others using a link, the key is stored in the link for your participants. This ensures that your survey questions can only be read by your participants.
Every survey has its own unique key pair. The private key is securely stored in your keychain, while the public key is used by users to encrypt their answers. Only you have the means to decrypt the answers once they are submitted. When you share a survey, we include a hash of the public key in the URL to prevent main-in-the-middle attacks.
Survey creators can opt-in to use VPN blocking, requiring a Purplix account or IP blocking. IP blocking works by storing a hash of the IP salted with a key not stored by Purplix, minimizing the attack surface of tracking submission locations, these IP hashes are only stored for 7 days or until the survey closes. Users will always be informed when any of these features are enabled.
Fill out a survey!
----
Visit our site: https://purplix.io
Support us on Github: https://github.com/WardPearce/Purplix.io
Purplix Survey is a free & open source survey tool what can't read your questions & answers.
With traditional surveys you are one data breach, one rouge employee or one government warrant away from all your user's data being exposed. Purplix uses modern encryption techniques to keep your user's data away from any actors.
When you create a survey, we encrypt your title, descriptions & questions with a secret key. This key is then stored encrypted in your keychain. When you share your survey with others using a link, the key is stored in the link for your participants. This ensures that your survey questions can only be read by your participants.
Every survey has its own unique key pair. The private key is securely stored in your keychain, while the public key is used by users to encrypt their answers. Only you have the means to decrypt the answers once they are submitted. When you share a survey, we include a hash of the public key in the URL to prevent main-in-the-middle attacks.
Survey creators can opt-in to use VPN blocking, requiring a Purplix account or IP blocking. IP blocking works by storing a hash of the IP salted with a key not stored by Purplix, minimizing the attack surface of tracking submission locations, these IP hashes are only stored for 7 days or until the survey closes. Users will always be informed when any of these features are enabled.
Fill out a survey!
----
