If you trust that system not to be compromised, then you may as well have just sent the secret plain-text.
In what way or in what scenario does this ever grant you MORE secrecy?
> and I'm not sure everyone is comfortable with E2E encrypted comms as a way to share secrets.
I'd live to know what would make people uncomfortable with this, because your system is, in practice, exactly that :)
> What makes this unique is that it's minimal work to do this with a big level of security that you can run on your own.
I love that this can be used over any channel, secure or not, but I would prefer if we all just switched to proper secure communications everywhere. In 2024 there is no good reason not to anymore.
And if I take your point and consider self hosting this, then it's much easier and better to install proper secure communication with my peers.
Again, I'm not against the idea of allowing secure exchange of secrets in an insecure environment, but as engineers if we really want to solve problems we should look at the real one: why are communications not secure, and how to fix this. This is not a technical problem, it's a societal one, and the solution might be societal. Unfortunately as engineers we tend to suck on the social level so we don't want to see it, but it's height time we take the plunge.
The whole idea around this was an open-source research project that people can use day-to-day or enhance to share secrets with a zero-knowledge system. What makes this unique is that it's minimal work to do this with a big level of security that you can run on your own.