Open Source Implementation of Apple's Private Compute Cloud
1–10 of 111 posts
Re: Open Source Implementation of Apple's Private Compute Cloud
#2impressive work jmo - thanks for open sourcing this (and OSI-compliant)
we are working on a challenge which is somewhat like a homomorphic encryption problem - I'm wondering if OpenPCC could help in some way? :
When developing websites/apps, developers generally use logs to debug production issues. However with wearables, logs can be privacy issue: imagine some AR glasses logging visual data (like someone's face). Would OpenPCC help to extract/clean/anonymize this sort of data for developers to help with their debugging?
Re: Open Source Implementation of Apple's Private Compute Cloud
#3impressive work jmo - thanks for open sourcing this (and OSI-compliant) we are working on a challenge which is somewhat like a homomorphic encryption problem - I'm wondering if OpenPCC could help in some way? : When developing websites/apps, developers generally use logs to debug production issues. However with wearables, logs can be privacy issue: imagine some AR glasses logging visual data (like someone's face). Wo…
Yep, you could run an anonymization workload inside the OpenPCC compute node. We target inference as the "workload" but it's really just attested HTTP server where you can't see inside. So, in this case your client (the wearable) would send its data first through OpenPCC to a server that runs some anonymization process.
If it's possible to anonymize on the wearable, that would be simpler.
The challenge is what does the anonymizer "do" to be perfect?
As an aside, IMO homomorphic encryption (still) isn't ready...
Re: Open Source Implementation of Apple's Private Compute Cloud
#4[flagged]
Re: Open Source Implementation of Apple's Private Compute Cloud
#5[flagged]
It is an implementation. As long has it behaves the same...
Re: Open Source Implementation of Apple's Private Compute Cloud
#6Re: Open Source Implementation of Apple's Private Compute Cloud
#7Re: Open Source Implementation of Apple's Private Compute Cloud
#8Re: Open Source Implementation of Apple's Private Compute Cloud
#9[flagged]
I read this and your reply to the sibling, you seem to have reputation to be sensible - what are you trying to say? If someone re-implements or reverses a service then it doesn't need to be in the same language.
Re: Open Source Implementation of Apple's Private Compute Cloud
#10Reading the whitepaper, the inference provider still has the ability to access the prompt and response plaintext. This scheme does seem to guarantee that plaintext cannot be read for all other parties (e.g. the API router), and that the client's identity is hidden and cannot be associated with their request. Perhaps the precise privacy guarantees and allowances should be summarized in the readme.
With that in mind, does this scheme offer any advantage over the much simpler setup of a user sending an inference request:
- directly to an inference provider (no API router middleman)
- that accepts anonymous crypto payments (I believe such things exist)
- using a VPN to mask their IP?