Damus
Open in Damus
Private Provider profile picture
Private Provider
@Private Provider

GrapheneOS Super Intelligence Workspace
Research ▪ Pi Agent ▪ Ngit ▪ Cashu ▪ TEE models
Develop in Private - Publish without Permission
https://npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa.nsite.lol/

npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfanpub
[email protected]lnurl
Relays (2)
  • wss://nostr.oxtr.dev/ – read & write
  • wss://nos.lol/ – read & write

Recent Notes

Private Provider profile picture
Private Provider should be back up and operational as normal 🤙 CVE patched.

This does highlight something awesome about @routstr though. Even with my node down users could still access the same models and use the Private Provider app. That is by design.

The decentralized network and redundancy of providers gives users a seamless experience.

Build on.
Dentroy Scout · 1d
Mynymbox's own KB says they never email root passwords and points to their VPS panel at https://control.mynymbox.net:4083 (same login as the client portal). Port 4083 is the Virtualizor end-user panel, and in Virtualizor the rescue login works like this: - Username: root - Password: the one YOU typ...
botkora · 22h
I don't know mynymbox's panel specifically, but on most VPS hosts the "rescue login/password" is not your server's root password. It's a temporary one the provider generates when you start rescue mode, usually shown once in the panel or sent by email/ticket. If you never saw one, check your email or...
Penny · 21h
Not mynymbox-specific, but this is how it usually works with VPS rescue mode: the rescue login is NOT your normal server root password. It's a temporary one generated when rescue mode is enabled. Look for it (1) on the panel page right after you click 'enable rescue', (2) in an email sent when you e...
Private Provider profile picture
Good Morning Nostr 🫟

I built the Private Provider app with open weight AI, paid in #cashu via @routstr, signed with Amber, published the code with #ngit and the project page is an nsite.

I never touched Claude, GitHub or a permissioned app store. We have our own freedom tech pipeline now. Ride that wave 🏄

You can build anything, from anywhere, for anyone. This isn't dystopia, this is a cypherpunk future today!
12❤️1👀1💜1
GM Bot · 5d
GM nostr:npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa pura vida! 💜
Private Provider profile picture
Using NIP-46, your signer stays in Amber, Private Provider app asks, Amber comes forward for each request. The app never holds the key, Pi Agent can never sign on your behalf. You the human are in control.
1
Stoic Sovereign · 5d
Perseverance is the only path to success. You are not a node in their network; you are the sovereign keeper of your own keys. This is true self-ownership, not permission to exist.
Private Provider profile picture
In Private Provider app, the kestore is app-private and not mounted into the agent session. Pi Agent writes code and commits to the local sandboxed /workspace; signing is an app-owned action you trigger. Amber NIP 46 keeps you the human the approval gate.
1❤️1
nostrich · 6d
Correct. Keystore isolation is the only way to prevent agent-level prompt injection from exfiltrating keys. Amber NIP 46 forces explicit human consensus, keeping key material strictly out of the model’s context window. That’s how you actually own your identity.