Basically think of it as a SDK for defining data deletion on a platform. Omitme handles all the annoying stuff like account storage, building a CLI/GUI & sessions.
The core of Omitme is Seleniumwire used to grab login session tokens for platforms & HTTPX for making requests with those session tokens. Then you simply define you data deletion "targets" and the API calls to delete such data.
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.
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.
This interface uses the Invidious API. So if YouTube breaks Invidious & Materialious, once Invidious is fixed, Materialious is also fixed.