Damus
falsefaucet · 3w
I don't understand why when someone is trying to reach out and make a product better/safer. This is the response... Prove it. Like it's not nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg...
Dustin Dannenhauer profile picture
The real question is if it’s a problem with Maple or with TEEs in general. Maple is clear they aren’t better than local AI - you should use that for maximum privacy.

Also, what exactly should Maple be doing differently? That’s what I meant by “prove it”. Where is the guidance on how to do better? What line of code is the problem?

By not providing solutions you’re just throwing shade on a project that is genuinely trying to bring better privacy to users and we need more of this today.

2
semisol · 3w
This is a problem with Maple. A TEE has no persistent memory. All persistent state needs to be outside the TEE, and data and encryption keys must be reinjectef on each startup if there is any state. In Maple’s case, the data is stored in an external Postgres DB. And the keys to protect the data ...
falsefaucet · 3w
as i said before im a moron. and have little to zero technical knowledge of this stuff. i assumed the original post you quoted was quite clear regarding the TEE's and the keys. seems semi chimed in for themselves. so they can explain it better than i ever could hope to.