This seems useful, thanks. It won’t clearly be sufficient to fully fix the issue (as people can always uncrypt the data and add it to training corpus), but it is a good protection against accidental inclusion.
I suppose this would gain more adoption if:
platforms such as HF would start using it alongside CAPTCHAs (so people can look at evals without downloading locally)
if it can be easily used alongside Inspect or other platforms (it may already be, not sure) -- or if inspect incorporates it and allows people defining a new eval to use it without effort.
As for the second point, have you considered patching Inspect?
We considered both of your suggestion (in-browser decryption extension / behind CAPTCHAs and Inspect integration) but are waiting for some feedback from the community on whether people would possibly use eval-crypt if those features existed! Would you? How big of a barrier to usage do you think the first feature is?
Hi Matan, yes, I think I would use it. I think it’s already quite useful even without HuggingFace integration. For instance, we are creating an eval that consists of custom code (relying on Inspect) + text prompts, and I would gladly encrypt the text prompts.
This seems useful, thanks. It won’t clearly be sufficient to fully fix the issue (as people can always uncrypt the data and add it to training corpus), but it is a good protection against accidental inclusion.
I suppose this would gain more adoption if:
platforms such as HF would start using it alongside CAPTCHAs (so people can look at evals without downloading locally)
if it can be easily used alongside Inspect or other platforms (it may already be, not sure) -- or if inspect incorporates it and allows people defining a new eval to use it without effort.
As for the second point, have you considered patching Inspect?
Thanks for the feedback Lorenzo!
We considered both of your suggestion (in-browser decryption extension / behind CAPTCHAs and Inspect integration) but are waiting for some feedback from the community on whether people would possibly use eval-crypt if those features existed! Would you? How big of a barrier to usage do you think the first feature is?
Hi Matan, yes, I think I would use it. I think it’s already quite useful even without HuggingFace integration. For instance, we are creating an eval that consists of custom code (relying on Inspect) + text prompts, and I would gladly encrypt the text prompts.
Glad to hear! We would love to hear how it goes! Feel free to each if there’s any way we can support you! (contact info on my website)