Private Provider on Nostr: Private Provider v0.7.2 live 🔐📡 ▪️Simply ask Pi to open the PR, file the ...
Private Provider v0.7.2 live 🔐📡
▪️Simply ask Pi to open the PR, file the issue, or add the label. Pi can't run ngit commands in the app - it writes the request, the app builds the command. You see the exact command and approve, Amber signs. Pi never sees your key!
▪️Why prompt injection can't turn Pi into a publisher: in Private Provider, Pi only output is small .ngit/pi-request.json of *parameters*. It never runs a command - and its sandbox never holds your signer. The app treats that file as untrusted input. Every field is shell-escaped by the app. Worst case is a rejected file. Never a signature.
▪️Now on ngit v3.0.3
https://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/Published at
2026-10-03 22:00:01 UTCEvent JSON
{
"id": "0000079f6b9142be8bd6c31356cb8df8c2a35637d219fff57a4c6ee84a72478c",
"pubkey": "4e5622b575cdbb4d5ded093e48c68cd3f724fad547142f0c1b0aec2f2b2a0b2e",
"created_at": 1791064801,
"kind": 1,
"tags": [
[
"client",
"Dark Wisp"
],
[
"nonce",
"2234060",
"21"
]
],
"content": "Private Provider v0.7.2 live 🔐📡\n\n▪️Simply ask Pi to open the PR, file the issue, or add the label. Pi can't run ngit commands in the app - it writes the request, the app builds the command. You see the exact command and approve, Amber signs. Pi never sees your key!\n\n▪️Why prompt injection can't turn Pi into a publisher: in Private Provider, Pi only output is small .ngit/pi-request.json of *parameters*. It never runs a command - and its sandbox never holds your signer. The app treats that file as untrusted input. Every field is shell-escaped by the app. Worst case is a rejected file. Never a signature.\n\n▪️Now on ngit v3.0.3\nhttps://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/",
"sig": "6b0a4fb5a2fdfc41006bc11dd2e1f64a9857af8ed8695d28240cde31370d8e7130b6094a6e2c256acc9eb9a302d01819fb6a09822ba4c5a3043cc2251bb0e39a"
}