Replies (25)

I spent 6 years at Apple working on cool AI and privacy tools. Then I saw that popular AI apps couldn't be used for anything sensitive. So I left and helped build an AI people can trust with their real life. We've come a long way since our humble launch in Jan 2025. View quoted note →
FEW_BTC's avatar
FEW_BTC 1 month ago
I am currently using Venice AI, and quite happy with it. With that said, I am very inclined to check out Maple and test it out. I asked multiple engines which service is better, and it seems like a toss up. Would you care to give me the 30 second elevator speech on why I should switch to Maple?
when seeing this slick design I needed to check it out. As non dev you got me with the cool looking design. So I got a pro account now and connected with my site BitPopArt and TravelTelly via #shakespeare from @Soapbox can’t wait to see how to grow my brands with it all #nostr connected ✍️👨🏻‍💻 But I got a small issue like this, any idea what it is/how to fix it @Alex Gleason @chad image
can you do image generation/editing on maple? i use ppq.ai for that today with grok imagine for the most part
My understanding: the basic difference is that Maple has encrypted server-side storage, so you can sign in from any device/browser and have the same experience. Venice only has client-side storage.
The Bench's avatar
The Bench 1 month ago
Every time something like this shows up, a few things quietly shift: users expect more control, builders compete on trust instead of just features, “black box” becomes harder to justify, and the idea of owning your own intelligence layer stops sounding crazy. What’s interesting is how this tends to unfold: first comes convenience (centralized), then comes awareness (privacy concerns), then comes pressure (better models like Maple), then eventually comes exit paths. View quoted note →
Sent this to your founder three months ago. Don't think Nostr dms work. Would love to explore it's intelligence and appreciate the consideration. image
Trusted Execution Environments use hardware encryption that provides cryptographic attestation to the code it is running. 1. look at our open source code on github to verify how data is handled 2. build the github code, grab the hash, and verify it matches with the TEE attestation