> Then again, it can't be worse than the status quo, so still good that you're working on this one way or another! Thank you. To clarify, private.sh != search

> Then again, it can't be worse than the status quo, so still good that you're working on this one way or another! Thank you. To clarify, private.sh != search provider (gigablast). Thus, it would take collusion between both to couple the identity of the searcher to the search query. private.sh does not have access to the private key associated with the public key that's used to encrypt the search query!