consider packaging WEBCAT functionality as a library #60
Description
One idea is to package a subset of WEBCAT's functionality as a library that could be integrated into other privacy and security sensitive related browser extensions e.g. extensions like Metamask. One advantage is adoption, WEBCAT can be widely adopted in existing browser extensions and the sites/frontends they interact with would be early testers and then after stabilization, users of WEBCAT.
This would be a significant effort since we'd need to design the right API, package it up (and refactor the existing browser extension to use said library), and ensure the enrollment infrastructure is solid. There's also the risk that if something is stabilized at the browser level that we can use for integrity/transparency, we may need to modify how things work on the WEBCAT side.