Server support is way more important than client support, because clients can add it as needed if DVMs support it. This is a self-own because Coracle doesn't encrypt DVM requests.

Reply to this note

Please Login to reply.

Discussion

The issue with this is a little that you need to know which DVM you want to address the search request to, in order to encrypt the request. Can't do a "look here's a request, who wants to answer to it". 🌝

That is a very good point 🤔

A good half-measure would be to use ephemeral keys to sign the request so the results would be public, but the user's identity would be hidden.

For example, yes. Or, as long as there's only 2 content search DVMs (that I'm aware of) could encrypt to these 2 directly, but that's not very generic.

noogle.lol is now encrypting search requests 🌝

Noo you broke my cool client!

It shouldn't break tho 🙃