👀 soooo, need to move to encrypted calls now? 🙃
Built a goofy little project this morning: https://shamebot.coracle.social/
It just pulls recent searches made via DVM and shames the people who made them. Tsk tsk.
Inspired by a tool for looking at DVM stats I found this morning: https://dvmdash.live/recent/
Discussion
Guess so!
No problem, my DVMs support encryption, clients just have to use it in the request.
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.
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.
