Yea the slider was the default component vidstack uses, I do agree it would be a good idea to use a drop down instead.
Materialious uses ReturnYouTubeDislikes for dislikes and likes, this option can be disabled in settings.
This interface uses the Invidious API. So if YouTube breaks Invidious & Materialious, once Invidious is fixed, Materialious is also fixed.
fair enough! Materialious very much meant for people who use Invidious and are comfortable with JS.
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)
Agreed, should have an alart for missed canaries. Each canary has "statements" you publish new statements to update ur canary. This provides a signed record of passed canaries.
Browser extension or even mobile app could be another aspect of further securing validation. Currently we do store a offline backup for each public key in idb storage & a signed copy if you have a account for further validation if the URL hash has been tampered with.
Thank you for your kind words ❤️❤️
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!
----
has been a old and off project for a few months. Would call it niche in terms of people who care about e2ee tools, but in general how insecure surveys are shouldn't be as common place as it is.
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!
----
Certbot is great when using Nginx (or Apache2), but if you can use a different engine. Its worthwhile checking out Caddy!
Worthwhile plugging Obtainium what is helpful for pulling prebuilt apks off Git
Thought this comment he made was odd about Proton mail.
The site is filled by beautiful black screen without JavaScript enabled.
Like yes, its a bit difficult implementing local encryption or decryption without js enabled.
Has some good messaging, I'd say most of his comments are pretty widely known concerns or limitations.
Like obviously web apps still rely on trust from the host, but it minimizes the attack surface massively.
this is /Privacy not /SavingMoney... Spotify (and all the leading platforms) collect data on you.
Just your average nothing conversion.
"System messed up once, trans people shouldn't exist"
Maybe with the Materialious frontend
https://github.com/WardPearce/Materialious
Cough cough might be a plug