I can view and maintain PRs for @Private Provider in Private Provider!

If you are a user of @Private Provider APK, you can clone the ngit repo into the app itself. Then from in the app you can create real PRs with Pi Agent, open them to the maintainer, relay issues, and comment over ngit! Collaborate on Private Provider inside and with Private Provider 🚬

I built @Private Provider using @routstr I paid for the AI with #cashu I released the code with #ngit I used the open source agent Pi I published the project to a nsite I routed around centralized control tech Now you can too - from anywhere https://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/

@Private Provider APK is for cypherpunks!

I built the @Private Provider APK so that cypherpunks can build privately with dignity on a GrapheneOS and publish code to the world without permission from anywhere. All you need is an npub and some sats ✨ https://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/

I am super proud to announce @Private Provider APK is now available 💥 ▪️Confidential AI with hardware attestation per prompt ▪️Pi Agent directly on Android/GrapheneOS ▪️Pay per query with #cashu via @routstr - no KYC ▪️Build APKs & publish to #nostr with full #ngit ux in app ▪️Every project folder is a git repo, Amber signs ▪️Develop with dignity, publish without permission Free open source https://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/

Building the @Private Provider App nsite now! Excited to release this soon for you cypherpunks!

@Private Provider App creating nsites and publishing them to blosdom servers in app + signed by Amber

@Private Provider App doesn't allow Pi Agent access to the the ngit key, the apk build key or the routstrd wallet key. Amber nip46 bunker url is used to log in to ngit. Pi can use local git bit has no way to sign to the developer's ngit account! The ngit action are done through the app and signed remotely with #Amber. This isolation firmly puts the human in manual control of signing code created by an agent. Each ngit action can be manually approved by your physical action in Amber and the agent can't access the key. Here in Private Provider, Pi wrote code in a TEE, paid in #cashu from in app wallet, saved file to in app workspace repository with built in ngit ux, published to nostr, approved in Amber, Pi then builds APK, commit in workspace, sign in Amber, release, sign and view repo in app.

Laptop talks output back via local only model + fono 👀 View quoted note →

@Private Provider App has a feature where a long press on the send button reveals a ⬇ glyph. Tapping ⬇ turns your last prompt and AI output in the chat tab into a markdown md file artifact saved in the apps workspace. You can read it anytime or have Pi Agent refernece it in a session in app.

@Private Provider App allows you to spot a ngit project on nostr, tap the link, clone the repo into the app, have pi agent write code and submit the PR to the maintainer all in App!

Talking to Pi Agent to dev @Private Provider App via local Fono is so Tony Stark 🦾

So I say Two Weeks and then release on a Friday? Am I doing this right?

Why have a separate chat tab when there is a Pi Agent tab? Because coding context is scarce space. If you have a random thought, don't muddy the coding agent with it. Drop it in a chat and find out over there. Not sure how to answer a question from the coding agent? Ask the chat, give the agent a concrete answer. Two tabs to switch between with as many chats and sessions as you want. View quoted note →

@Private Provider App offers users privacy and dignity