Nostr notes by mfoster.io

In the modern world, Independence is the byproduct of ...

2026-03-28T18:04:58Z

In the modern world, Independence is the byproduct of understanding what a nonce is.

Heck, my hip hurts just getting out of bed sometimes. :-/

2026-03-24T02:25:06Z

In reply to nevent1q…kznl
_________________________

Heck, my hip hurts just getting out of bed sometimes. :-/

Nostr event nevent1qqs0uew6l293mtc8zvvddr8m0j873w2z8fxx5zp44gaxz6254rxjv3szyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz76twarv

2026-03-23T15:11:06Z

Yes! It absolutely was! 🙌

2026-03-23T13:55:32Z

In reply to nevent1q…vgtk
_________________________

Yes! It absolutely was! 🙌

Nostr event nevent1qqsvnd556ne3nysfvqv5ytjcmvpu80ux8d4te8lplgd2nre0u7r60ugzyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7vyv0eq

2026-03-22T03:17:38Z

Nostr event nevent1qqsz9qz20asq8geln6eckfqwwstdrn954360jnh864xc4hzk45g2ufqzyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7g789k7

2026-03-16T01:21:55Z

😂

2026-03-12T05:34:21Z

In reply to nevent1q…ggmz
_________________________

😂

https://c2pa-check.pages.dev/

2026-03-12T04:08:25Z

In reply to nevent1q…p93c
_________________________

https://c2pa-check.pages.dev/

The key idea is understanding when and how to attach data in a ...

2026-03-12T04:06:54Z

In reply to nevent1q…tqe8
_________________________

The key idea is understanding when and how to attach data in a provenance chain. A Sony camera produces a hardware‑rooted C2PA signature at capture time, signing the EXIF and proprietary metadata inside a secure element. This proves the image was taken on a real Sony device and not generated by AI.Additional manifests such as location, organizational identity, workflow metadata, or edit history can be added later as separate signed assertions. Each added layer must be intentional, privacy‑aware, and auditable, because it expands the legal and trust surface. The result is not a blockchain, but a hardware anchored, append only provenance chain that carries legal weight similar to other cryptographically signed declarations, such as NIP‑62’s “Request to Vanish,” though the mechanisms and goals are different.

https://nips.nostr.com/62

Soon!

2026-03-10T20:44:53Z

In reply to nevent1q…5pek
_________________________

Soon!

I miss my Lycos homepage and MySpace! ...

2026-03-10T19:39:17Z

I miss my Lycos homepage and MySpace!

Nostr event nevent1qqsd6n3wqcx48lpe38eddhl8ugnqe57umskmn6lnt9eesjplyvyd83szyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz78mazrg

2026-03-09T05:18:25Z

∅ ⇄ ◌⁻ · ◌⁺ ⇄ ∅

Louisian Fishing 🎣 ...

2026-03-05T04:45:47Z

Louisian Fishing 🎣

What phone is this?

2026-02-26T23:27:24Z

In reply to nevent1q…kvvh
_________________________

What phone is this?

Nostr event nevent1qqsf0zdz34px3dm5ehur96ak7nqtqucp2rnqq2mrcssfglxe87f2xvszyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7ldnf6r

2026-01-27T19:57:00Z

It’s time to take a Napp. 😴

2026-01-27T19:13:58Z

In reply to nevent1q…ezwn
_________________________

It’s time to take a Napp. 😴

Must be Android unless I am missing something on iOS?

2026-01-14T22:41:41Z

In reply to nevent1q…yknk
_________________________

Must be Android unless I am missing something on iOS?

What App is this?

2026-01-14T20:10:20Z

In reply to nevent1q…23c9
_________________________

What App is this?

What App is this?

2026-01-14T20:09:42Z

In reply to nevent1q…88vk
_________________________

What App is this?

Thank you, great work!

2026-01-09T02:47:46Z

In reply to nevent1q…y4l9
_________________________

Thank you, great work!

This is great, is it in the this repository? ...

2026-01-08T04:45:51Z

In reply to nevent1q…aw2f
_________________________

This is great, is it in the this repository? https://github.com/PrimalHQ/primal-ios-app

Is the iOS remote signer going to be open source?

2026-01-07T02:58:14Z

In reply to nevent1q…3t83
_________________________

Is the iOS remote signer going to be open source?

Nostr event nevent1qqs2s5vr0t7wf8lml80eth0vagw6dzcdtpkk23p4rdl05rmel0jk9ygzyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7ueqvpm

2026-01-03T19:25:38Z

https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-crypto-refresh-13

Immutable Democracy! 🗳️🔏 https://youtu.be/g0nnM5_Z90E

2026-01-03T15:31:56Z

Immutable Democracy! 🗳️🔏
https://youtu.be/g0nnM5_Z90E

Nostr event nevent1qqs8rue2kuqxargx8h8uu4wp7f0fnfkcsj972g6cexk9e0trpyjgt5szyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz77v80an

2026-01-02T07:32:14Z

C2PA https://C2PA.org uses CAWG https://cawg.io/ for identity, I ...

2025-12-31T20:07:05Z

C2PA https://C2PA.org uses CAWG https://cawg.io/ for identity, I am moving towards building prototypes that map context with JSON-LD to CAWG Context https://cawg.io/identity/1.1/ica/context/ for Nostr and bridging it to ProofMode https://ProofMode.org for interoperability.

https://proof-chain.pages.dev/

This is the way! https://youtu.be/LaiN63o_BxA ...

2025-12-19T21:14:58Z

In reply to nevent1q…f3xd
_________________________

This is the way!

https://youtu.be/LaiN63o_BxA

Correct, postMessage is the way to keep the contexts separate. ...

2025-12-19T21:09:40Z

In reply to nevent1q…f4z4
_________________________

Correct, postMessage is the way to keep the contexts separate. You can do the same with OPFS, it’s got some added features with a hidden context by default and is highly performant. You can also back up your signed nostr event notes in an SQLite DB and pin other SHA256 addressable notes via local cache.

https://primal.net/e/1cb0612ff42762b7639e64b641319229d4e7848a4228331f6f27f27fa6c248cd

client.com (page)
│
│ postMessage (cross‑origin, sandbox‑safe)
▼
vault.com (iframe)
│
│ postMessage (same‑origin, internal)
▼
vault Worker (isolated agent)
│
├── OPFS (Origin Private File System)
└── IndexedDB

🙌 Absolutely, I agree 1000% percent, context is everything!

2025-12-19T20:49:25Z

In reply to nevent1q…v75g
_________________________

🙌 Absolutely, I agree 1000% percent, context is everything!

Greed.

2025-12-18T07:54:25Z

In reply to nevent1q…p8cz
_________________________

Greed.

I have been pushing the noble curves as well. Both indexDB and ...

2025-12-18T06:11:37Z

In reply to nevent1q…lqpn
_________________________

I have been pushing the noble curves as well. Both indexDB and OPFS are origin specific so the solution is definitely in handling the keys. One advantage of OPFS is you can’t view it via inspecting the web app in the browser without an extension. It’s sandboxed just like indexDB, but isolated out of the default tools which helps hide some of the attributes of the data structure.

I’m trying to wrap my head around the differences between using ...

2025-12-18T05:50:07Z

In reply to nevent1q…ys54
_________________________

I’m trying to wrap my head around the differences between using IndexedDB, OPFS, and SQLite in your scenario. I’ve been researching the idea of running an isolated iFrame on client.com for vault.com and passing data between the two origins via postMessage. In that setup, is there anything in NostrPass that prevents rogue extension <script> injections from compromising the page context?

I created this demo writing to an SQLite DB in OPFS and using ...

2025-12-18T04:09:45Z

In reply to nevent1q…h0xm
_________________________

I created this demo writing to an SQLite DB in OPFS and using postMessage via the Baseline Broadcast Channel API.

https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API

I like to think of it a side load private file system bound to a ...

2025-12-17T23:35:55Z

In reply to nevent1q…9927
_________________________

I like to think of it a side load private file system bound to a domain based identity i.e., my origin vault could be mfostr.me.

That is a good question, It is bound to the origin binding: OPFS ...

2025-12-17T23:29:41Z

In reply to nevent1q…h0xm
_________________________

That is a good question, It is bound to the origin binding: OPFS storage is origin-private. Even if an extension injects code, the storage it accesses is scoped to that origin. It cannot cross into another site’s OPFS. So if you’re on NostrVault.tld, injected code can only touch NostrVault.tld OPFS, not NostrClient.com’s or a rogue extension.

The rogue extension would have to have host permission to access the Origin Private File System (OPFS) and eventually our goal goal is to encrypt the data at rest with OPFS with an OpenPGP cert from the NFC card so a rogue extension wouldn’t know how to interpret it or what to do with it, if it got access to it.

#AskNostr #Nostr 👀 WebWorkers and iFrame isolation with ...

2025-12-17T18:49:19Z

#AskNostr #Nostr 👀 WebWorkers and iFrame isolation with window.nostr.signEvent(), as if it were using any NIP-07 extension, represent a great move in the right direction. I recommend that Nostr developers pay attention to OPFS capabilities versus IndexedDB where possible. OPFS avoids metadata leakage and is now part of the Baseline in all browsers. 🔏

https://primal.net/e/nevent1qqs8tqf99ddes0jh4lngxaaxjm3r39kc3xvqeh2xjxg7pjmwd87q68qnrcn50

quoting
naddr1qq…t8qe

NostrPass: Decentralized Identity

How a privacy-first vault is making self-sovereign identity actually usable

If you've spent any time in the Nostr ecosystem, you've probably experienced the friction: copying and pasting your private key between apps, wondering if you just exposed it to a malicious extension, or worse—losing access to your identity because you forgot where you stored your nsec. For all of Nostr's promise of decentralization and censorship resistance, the user experience around identity has been, frankly, a mess.

NostrPass emerged from a simple observation: if we want Nostr to go mainstream, we need to make key management invisible to users while keeping it completely secure. It's a password manager for your Nostr identities—but unlike traditional password managers, it's built from the ground up for decentralization, with your keys never leaving your device and zero knowledge on the server side.

After months of development and several architectural pivots, NostrPass now offers something rare in the crypto world: bank-grade security that doesn't require users to be cryptography experts.

The Core Problem: Keys Are Hard

Let's be honest about the state of Nostr identity management. Most users are doing one of several terrible things:

The Browser Extension Gamble: Installing a browser extension and hoping it's not malicious. Every Nostr app can now access your keys through window.nostr, which is convenient—until you realize you've given every webpage full access to sign anything.

The Copy-Paste Nightmare: Manually copying your nsec between apps. This exposes your private key to clipboard managers, screen recording software, and shoulder surfers. It's also incredibly tedious.

The Single-Identity Trap: Using the same identity for everything because managing multiple keys is too painful. Want a professional Nostr presence separate from your personal one? Good luck remembering which key is which.

The Recovery Panic: Storing your key in a text file, a password manager not designed for crypto, or worse—not storing it at all and hoping you never lose your browser data.

NostrPass solves all of these problems with an architecture that's both more secure and dramatically easier to use.

How It Actually Works

The magic of NostrPass happens in the space between your browser and Nostr apps, using a technique that's both elegant and battle-tested: iframe isolation with cryptographic operations in a Web Worker.

When you integrate NostrPass into an app, you include a small SDK (about 50KB) that creates a hidden iframe pointing to your vault. This vault runs on a completely different origin—meaning it has its own separate storage, its own separate execution context, and browser-enforced security boundaries.

Here's what happens when an app wants to sign an event:

The app calls window.nostr.signEvent() as if it were using any NIP-07 extension

The NostrPass SDK sends a secure message to the vault iframe

The vault checks: Is this app allowed? What permissions does the user have?

If needed, the vault UI appears asking for permission or PIN unlock

The vault sends the event to a Web Worker where your actual private key lives

The Worker signs the event using audited cryptography libraries

The signed event travels back through the chain to the app

At no point does the app see your private key. At no point does the main thread see your private key. The Worker holds decrypted keys only in memory for the duration of your session, clearing everything on logout or timeout.

The Cryptography Stack: Why We Chose Noble

Early versions of NostrPass explored using WebAssembly for cryptographic operations—compiling Rust crypto libraries to WASM for maximum performance and security. But we ran into several problems: large bundle sizes (500KB+), compilation delays on initialization, and debugging challenges when things went wrong.

Instead, we bet on the Noble cryptography ecosystem—a collection of audited, production-tested JavaScript libraries that have processed millions of real cryptocurrency transactions. This turned out to be the right call.

Noble gives us:

Schnorr signatures via @noble/curves/secp256k1—the same curve Bitcoin uses Hierarchical deterministic keys via @scure/bip32—generate unlimited identities from one seed Mnemonic recovery phrases via @scure/bip39—industry-standard 12 or 24-word backups Secure hashing and key derivation via @noble/hashes—SHA-256, PBKDF2 with 100,000 iterations AES-256-GCM encryption that uses the browser's native Web Crypto API when available, with a pure JavaScript fallback for mobile HTTP contexts

The result? A 100KB crypto bundle that initializes instantly, debugs easily, and runs on every platform from desktop browsers to mobile WebViews.

Multiple Identities: The Killer Feature

One of NostrPass's most powerful features is effortless multi-identity management. Under the hood, it uses BIP32 key derivation—the same technology Bitcoin wallets use to generate unlimited addresses from a single seed.

Your master seed generates a tree of identities:
Master Seed
├── Identity 0: Personal (your main social presence)
├── Identity 1: Professional (work-related content)
├── Identity 2: Anonymous (privacy-sensitive discussions)
├── Identity 3: Bot account (automated posting)
└── ... unlimited more
Each identity is a completely separate Nostr keypair with its own:

Public/private key Permission settings per app Usage history Customizable nickname

But you only need to remember one password (and optionally a PIN for quick access). Everything else derives deterministically from your master seed.

Want to post professional technical content without linking it to your personal identity? Switch identities in two clicks. Need a burner identity for a controversial discussion? Generate a new one instantly. The friction of managing multiple Nostr identities drops to zero.

Permissions: Granular Control Without the Hassle

Most Nostr signing solutions are all-or-nothing: either an app can sign anything, or it can't sign at all. NostrPass gives you surgical precision.

Permissions are set per-identity, per-app, per-operation type, and even per-event-kind. Here's what that looks like in practice:

Social Media Client:

Text notes (kind 1): ALLOW (auto-approve, no prompt) DMs (kind 4): ASK\EVERYTIME (always prompt) Get public key: ALLOW NIP-04 encryption: ASK\PER\SESSION (ask once per session)

Professional Publishing Platform:

Long-form articles (kind 30023): ALLOW Comments (kind 1): ALLOW Arbitrary data signing: DENY Get public key: ALLOW

Unknown New App:

Everything: ASK\EVERYTIME (maximum security until you trust it)

The permission system learns from your habits. If you always approve something, you can set it to ALLOW and stop seeing prompts. If you're trying a new app, leave everything on ASK\EVERYTIME until you trust it.

The Security Model: Defense in Depth

NostrPass doesn't rely on a single security mechanism—it uses layered defenses that would all need to fail simultaneously for an attack to succeed.

Layer 1: Origin Validation
Every message between the app and vault is checked against a whitelist of allowed origins. A malicious website can't just start sending messages to your vault.

Layer 2: Iframe Sandbox
The vault runs in a sandboxed iframe with restricted permissions. It can't access the parent page's DOM, cookies, or localStorage. Even if the parent app is compromised, it can't read your vault data.

Layer 3: Web Worker Isolation
All cryptographic operations happen in a separate thread. Private keys are never deserialized on the main thread—ever. Memory inspection of the main thread reveals nothing.

Layer 4: Process Isolation
The vault runs on a different domain than the app. Browser same-origin policy provides hardware-enforced isolation—the operating system won't let the processes share memory.

Layer 5: Encryption at Rest
Your vault data is encrypted with AES-256-GCM before storage. The encryption key is derived from your password using PBKDF2 with 100,000 iterations. Even if someone gets your IndexedDB data, it's useless without your password.

Layer 6: No Plaintext Storage
Private keys are never stored unencrypted. When you unlock your vault, keys are decrypted in the Worker's memory and cleared after one hour or on logout.

This isn't security theater—it's the same multi-layer approach banks and cryptocurrency wallets use to protect billions of dollars.

Decentralized Sync: Your Vault, Everywhere

Most password managers store your encrypted vault on their servers. NostrPass does something more aligned with Nostr's philosophy: it publishes your encrypted vault as a Nostr event (kind 30078).

When you sign up or make changes to your vault, NostrPass:

Encrypts your entire vault with your password

Signs the encrypted blob with a special "storage identity" derived from your master seed

Publishes it to Nostr relays as a replaceable event

Stores a copy in your browser's IndexedDB for offline access

When you log in from a new device:

NostrPass queries Nostr relays for your vault event

Downloads the encrypted vault

Decrypts it with your password

Restores your identities, permissions, and settings

This means:

✅ No central server holding your data ✅ Cross-device sync through Nostr relays ✅ End-to-end encryption—relays only see encrypted blobs ✅ Zero knowledge—NostrPass can't decrypt your vault ✅ Censorship resistance—published on multiple relays

If NostrPass the service disappeared tomorrow, your vault would still be on Nostr relays, decryptable with your password.

Real-World Usage: The Experience

Let me walk you through what using NostrPass actually feels like.

First Time Setup (2 minutes):

Visit vault.nostrpass.com

Choose a username and password

Optionally set a 4-6 digit PIN for quick unlock

Your vault creates your first identity automatically

You see a recovery phrase—write it down (seriously, do this)

That's it. No email verification, no KYC, no phone number. Just username + password.

Using an App (seconds):

Click "Login with NostrPass" on any integrated app

The vault appears—either full-screen for first login or as a small popup for quick unlock

Enter PIN (or password if session expired)

Approve permissions if first time using this app

You're in

The next time you use that app, it might not even prompt you—if you've set text notes to ALLOW, it just signs them instantly.

Switching Identities (1 click):

Most apps that integrate NostrPass show an account switcher—click your current identity, pick a different one from the dropdown. Done.

Managing Permissions (when needed):

Open the vault dashboard to see all apps that have accessed your identities, what permissions they have, and when they last requested something. Revoke access with one click.

Mobile: It Just Works

Because NostrPass is built on web standards, it works everywhere browsers work—including WebViews in native mobile apps.

React Native developers can embed NostrPass in a WebView:
&lt;WebView
  source={{ uri: 'https://your-app.com' }}
  injectedJavaScript={
    (function() {
      const script = document.createElement('script');
      script.src = 'https://cdn.nostrpass.com/embassy.js';
      document.head.appendChild(script);
    })();
  }
/&gt;
The Noble crypto libraries include automatic fallbacks for environments where the Web Crypto API isn't available (like mobile HTTP contexts), so everything works seamlessly.

We've tested NostrPass in:

iOS Safari Android Chrome React Native WebView Capacitor/Ionic apps Progressive Web Apps

It works everywhere. No native code required.

For Developers: Integration in 5 Minutes

If you're building a Nostr app, integrating NostrPass is almost trivially easy:
&lt;!-- 1. Include the SDK --&gt;
&lt;script src="https://cdn.nostrpass.com/embassy.js"&gt;&lt;/script&gt;

&lt;!-- 2. Use it --&gt;
&lt;script&gt;
  // Get the user's public key
  const pubkey = await window.nostr.getPublicKey();

  // Sign an event
  const event = {
    kind: 1,
    content: 'Hello Nostr!',
    tags: [],
    createdat: Math.floor(Date.now() / 1000)
  };
  const signed = await window.nostr.signEvent(event);

  // Publish to relays
  await publishToRelays(signed);
&lt;/script&gt;
That's literally it. The SDK auto-initializes, creates the vault iframe, and exposes window.nostr exactly like NIP-07 extensions do.

If your app already supports browser extensions like nos2x or Alby, it already supports NostrPass with zero code changes.

Self-Hosting:

Don't trust the hosted version? Self-hosting takes 5 commands:
git clone https://github.com/bigmarh/nostrpass.git
cd nostrpass
pnpm install
pnpm build
 Deploy /apps/vault/dist to your server
Point the SDK at your vault:
window.initNostrPass({
  vaultUrl: 'https://vault.yourcompany.com'
});
Now you're using your own vault instance. All the security properties remain—you still can't see users' keys, they're still encrypted end-to-end, sync still works through Nostr relays.

The Road Ahead

NostrPass is production-ready today, but there's still a roadmap of features we're excited about:

Near-term:

NIP-44 encryption support (newer, better encrypted DMs) Hardware wallet integration (sign with Ledger/Trezor) Social recovery (M-of-N threshold recovery with trusted contacts) Passkey/WebAuthn support (sign in with biometrics)

Medium-term:

Advanced permission rules (time-based, amount limits for zaps) Audit logs (complete history of every signature) Multi-device approval (require multiple devices to sign sensitive events) Developer SDK for React, Vue, Svelte

Long-term:

Professional security audit (we're in talks with several firms) Bug bounty program Formal verification of critical crypto code Browser extension version for even tighter integration

Why This Matters

Nostr has the potential to fundamentally change how we communicate online—no censorship, no centralized platforms, no algorithmic manipulation. But it can't achieve mainstream adoption if managing keys requires a computer science degree.

NostrPass makes self-sovereign identity accessible. Your grandmother could use it (with a good tutorial). Developers can integrate it in minutes. Power users can self-host it. Privacy advocates can audit it.

Most importantly, it doesn't compromise on security to achieve usability. The cryptography is conservative, audited, and battle-tested. The architecture is defense-in-depth. The code is open source.

If Nostr is going to grow beyond the early adopter crowd, tools like NostrPass are essential—they make the promise of decentralization tangible for people who don't want to think about key management.

Try It Yourself

The best way to understand NostrPass is to use it:

Visit nostrpass.com

Create run the demo

Try it with any Nostr app that supports NIP-07

Or if you're a developer, integrate it into your app and see how your users respond to a dramatically simpler auth flow.

The code is on GitHub, fully MIT licensed. We welcome contributions, security reviews, and feedback.

Built with:

Noble Cryptography - Audited JavaScript crypto nostr-tools - Nostr protocol implementation SolidJS - Reactive UI framework TypeScript - Type-safe development

"opensource", cryptography, security,identity,nip-o7,privacy,nostrpass

I’m focusing on origin iFrame isolation combined with OPFS ...

2025-12-17T18:43:38Z

In reply to naddr1qq…xqg4
_________________________

I’m focusing on origin iFrame isolation combined with OPFS (Origin Private File System), which is now a baseline capability in modern browsers: https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system. OPFS is gated behind Secure Contexts https://www.w3.org/TR/secure-contexts/, ensuring that these APIs are only available in environments served over HTTPS or equivalent.

Unlike IndexedDB, OPFS avoids metadata leakage. With IndexedDB, even if the stored data itself is protected, attackers can sometimes infer information from exposed metadata such as database names, schema details, or object store structures. This can reveal sensitive application logic or usage patterns. OPFS, by contrast, provides a simpler, file-like interface that doesn’t expose this kind of structural metadata, reducing the attack surface.

OPFS is also faster because it operates a layer closer to the file system, making it more efficient for handling large binary data and streaming workloads. This performance advantage is particularly useful for applications that need to persist signed content. For example, SQLite can be used on top of OPFS to capture signed posts in a vault for backup. Since these posts are addressable by their SHA‑256 hash, they can be stored and retrieved deterministically, ensuring both integrity and verifiability. Here is some research on how notion use SQLite and WASM to speed up their project. https://www.notion.com/blog/how-we-sped-up-notion-in-the-browser-with-wasm-sqlite

Here is also some documentation from Google for origin policy related info https://developer.chrome.com/blog/sqlite-wasm-in-the-browser-backed-by-the-origin-private-file-system

Coming from the SolidProject.org ecosystem, I began this research before discovering Nostr: https://mfosterio.github.io/ldux-local/ . It was intended for research only. I shifted gears when I discovered Nostr and have been focusing on wrapping my head around NFC, ISO 7812, NDEF, NTAG424 DNA, OpenPGP, GnuPG KeyGrips, and related technologies. WebWorkers and iFrame isolation provide secure, origin-bound contexts that enforce browser-level security boundaries, aligning with the Secure Contexts standard, but when you add OPFS, it’s like putting that model on steroids.

I look forward to watching your project. Great design kick off and this is heading in the right direction.

I agree with this 💯, I just got off the phone with someone ...

2025-12-17T14:47:18Z

I agree with this 💯, I just got off the phone with someone trying to login to their meta business account. Centralized systems are siloed into servers by domain law. Pay attention to how facebook structured the profile to be a route i.e., facebook.com/username vs username.facebook.com this was done by design so they can lock you into a system where your data is ultimately theirs.

quoting
nevent1q…edc3
"Proprietary software is an injustice. It denies users freedom and keeps them divided and helpless."

— Richard Stallman (Free Software, Free Society, 2002)

#cypherpunk #bitcoin #privacy #freedom #proprietary-software #justice

🎶🎼🎵♾️ #nevent1q…0ypz

2025-12-15T04:24:14Z

🎶🎼🎵♾️

quoting
nevent1q…0ypz
Want to run a PWA in the background?
Easy, just play music constantly, and the OS won't kill the app.

Alex Gleason (nprofile…lf00) blew my mind with this hack!

Nostr event nevent1qqsz3kjwp4npefgjmylqrld20ls2ufh2jprpwc5mp6pz335w0vgv3rqzyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7u2jes4

2025-12-15T03:33:42Z

https://fountain.fm/episode/lCEWRNdRinE54fTwipVr

https://nips.nostr.com/EE

lol

2025-12-15T03:14:23Z

In reply to nevent1q…2akw
_________________________

lol

Content is king 👑! The more we lift each other up by ...

2025-12-15T01:43:45Z

Content is king 👑! The more we lift each other up by following, sharing, and celebrating one another’s posts the stronger the signal we send. Every like, every share, every connection becomes a ripple that reaches our friends and family, inspiring them to join in and engage with our invitations. Together, we’re not just building momentum we’re building a movement. ✊

#AskNostr #Nostr

Nostr Notes Everywhere! ...

2025-12-14T18:07:10Z

In reply to nevent1q…nhc2
_________________________

Nostr Notes Everywhere!

Amen 🙏

2025-12-14T16:46:41Z

In reply to nevent1q…ald5
_________________________

Amen 🙏

We are doing it for sure.

2025-12-13T15:19:22Z

In reply to nevent1q…27fv
_________________________

We are doing it for sure.

It will be our year! The world will be better with open ...

2025-12-13T14:18:11Z

In reply to nevent1q…zlay
_________________________

It will be our year! The world will be better with open protocols. We all win, when we tear down the walled gardens.

Nostr event nevent1qqsva2n77j2ds4n570tcmka464lgafpa7juxmy6stlhwnn9zk2a8ctczyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7s0ykjz

2025-12-13T14:05:58Z

We need a verifiable SHA256 WebComponents marketplace. ☑️🔏 ...

2025-12-13T05:04:02Z

We need a verifiable SHA256 WebComponents marketplace. ☑️🔏 #askNostr
https://youtu.be/n-cHJ6tNOKk

Yes! I am digging the THANK MY BITAXE Zap! ⚡️

2025-12-13T04:18:49Z

In reply to nevent1q…n94v
_________________________

Yes! I am digging the THANK MY BITAXE Zap! ⚡️

This is a vector! 🏹 ...

2025-12-13T02:34:06Z

This is a vector! 🏹

Bittersweet This Life! ...

2025-12-12T03:45:14Z

Bittersweet This Life!

WoT! https://freakoverse.github.io/wotonnostr/

2025-12-11T03:31:10Z

WoT!

https://freakoverse.github.io/wotonnostr/

Nostr event nevent1qqs8vn4pcszrtectkfm5hyx88rttu5ncqk90gssa56scg542ddma4cczyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz7hx6kwl

2025-12-07T03:20:14Z

It’s been out for a while now. It’s all over the place, but ...

2025-12-06T23:01:43Z

In reply to nevent1q…lr2n
_________________________

It’s been out for a while now. It’s all over the place, but you can share the blossom url by removing the quotes and spaces. https://v.nostr.build/ “GBcUfYYjdODcTnF0” .mp4

With the help of #Nostr the #Bitcoin block will be the native ...

2025-12-06T21:55:32Z

With the help of #Nostr the #Bitcoin block will be the native currency and settlement layer of the internet.

#askNostr Is this how you feel about #nostr? I know I do! ...

2025-12-06T19:37:59Z

#askNostr Is this how you feel about #nostr? I know I do! 🙋🏻‍♂️ We will not give up until mainstream adoption.

quoting
nevent1q…2ear
Some may say, we’re wishing our days away. No way, and if it's the price we pay. Some say, tomorrow's another day. You stay, we may as well play. Walking on the moon.🚶🏻🚶🌒🌜🌙

🤣

2025-12-05T04:09:18Z

In reply to nevent1q…mc7y
_________________________

🤣

Gotcha, it gets confusing because of the number ordering. Thanks ...

2025-12-05T01:48:36Z

In reply to nevent1q…4s00
_________________________

Gotcha, it gets confusing because of the number ordering. Thanks for pointing that out.

Any goals towards Gift Wraps?

2025-12-05T01:40:21Z

In reply to nevent1q…2926
_________________________

Any goals towards Gift Wraps?

#Nostr in a nut shell. 👀 ...

2025-12-03T18:22:31Z

#Nostr in a nut shell.

👀 https://link.springer.com/content/pdf/10.1007/BF00196791.pdf

🤳🔏🚥🛜

This is the most valid point there could ever be. The right to ...

2025-12-03T15:58:20Z

In reply to nevent1q…ad0g
_________________________

This is the most valid point there could ever be. The right to privacy is stronger than any argument out there.

I’m with you over here in Louisiana.

2025-12-03T02:45:47Z

In reply to nevent1q…cgt0
_________________________

I’m with you over here in Louisiana.

https://os.ryo.lu

2025-12-02T05:11:41Z

https://os.ryo.lu

#nostr watches will outperform both Apple and Android ...

2025-12-02T03:40:55Z

#nostr watches will outperform both Apple and Android smartwatches by a wide margin.

Some may say, we’re wishing our days away. No way, and if ...

2025-11-30T08:38:06Z

Some may say, we’re wishing our days away. No way, and if it's the price we pay. Some say, tomorrow's another day. You stay, we may as well play. Walking on the moon.🚶🏻🚶🌒🌜🌙

Makes sense!

2025-11-30T00:33:15Z

In reply to nevent1q…mr82
_________________________

Makes sense!

https://github.com/markqvist/Reticulum/discussions/1002

2025-11-28T00:00:02Z

https://github.com/markqvist/Reticulum/discussions/1002

This! 💯 #nevent1q…zuf6

2025-11-27T23:18:49Z

This! 💯

quoting
nevent1q…zuf6
nostr wins if it stops trying to be a twitter clone and starts being the invisible layer underneath apps you actually want to use. like bitchat for location-based messaging, diVine for entertainment, whitenoise for private messaging, zap.stream for streaming, shakespeare for vibe coding, etc.

it wins by unbundling into 50 different apps that all talk to each other, rather than one giant app/corp that traps you. it's all about the ecosystem.

Engineers should be honored more. GE Euclid Lamp would make lamps ...

2025-11-26T13:55:05Z

Engineers should be honored more. GE Euclid Lamp would make lamps like this sometimes when people retired.

Yes, the more developers the better! We need to keep spreading ...

2025-11-24T00:29:05Z

In reply to nevent1q…kufg
_________________________

Yes, the more developers the better! We need to keep spreading the word!

X client? Most of the clients are open source. ...

2025-11-24T00:24:16Z

In reply to nevent1q…y9t3
_________________________

X client? Most of the clients are open source.

https://github.com/PrimalHQ

Play around with https://nostrdebug.com it’s helpful.

2025-11-24T00:19:29Z

In reply to nevent1q…kl0h
_________________________

Play around with https://nostrdebug.com it’s helpful.

Wouldn’t it be nice if they just joined the nostr effort. ...

2025-11-23T23:44:05Z

Wouldn’t it be nice if they just joined the nostr effort.

quoting
nevent1q…y0gh
They're coming for diVine's hype!
nevent1q…w6xa

Nice! I look forward to checking it out! Great work! 🙌

2025-11-23T22:26:45Z

In reply to nevent1q…97t0
_________________________

Nice! I look forward to checking it out! Great work! 🙌

Do you have a demo?

2025-11-23T22:05:43Z

In reply to nevent1q…wd69
_________________________

Do you have a demo?

AI driven plaforms that aren’t transparent and remain outside ...

2025-11-22T20:46:23Z

AI driven plaforms that aren’t transparent and remain outside your control don’t serve your best interests. They shape your choices in ways you can’t see and that’s not healthy for individual autonomy.

This dynamic is visible in many centralized platforms, including Meta/Facebook. Facebook was one of the first commercialized social media platforms to endure, and its design choices like structuring identity around “facebook.com/username/” were intentional ways to keep people tied to their ecosystem.

But technology doesn’t have to work this way. Decentralized, self‑sovereign protocols offer a different path:

🔑 What they mean for you:
- You control your identity instead
- You decide what to share and with whom
- Trust is verified in the protocols
- Communities thrive without surveillance‑driven business models

🚀 The future of social connection isn’t about being locked into platforms it’s about freedom, portability, and sovereignty.
Moving toward open, decentralized protocols means reclaiming control and building healthier digital spaces.

The sky glowed above the Ark Encounter with the beautiful colors ...

2025-11-21T04:17:59Z

The sky glowed above the Ark Encounter with the beautiful colors of the aurora borealis last week during the intense geomagnetic storm.

“The heavens declare the glory of God, and the sky above proclaims his handiwork” (Psalm 19:1 ESV).

https://youtu.be/0XVCc5zwPlU

2025-11-21T02:32:47Z

https://youtu.be/0XVCc5zwPlU

Louisiana 🐊🎣☀️ ...

2025-11-21T02:06:01Z

Louisiana 🐊🎣☀️

ProofMode! 🔏 https://divine.video/proofmode-spec

2025-11-21T02:00:42Z

ProofMode! 🔏

https://divine.video/proofmode-spec

Prime numbers in a synchronized flow create an interesting visual ...

2025-11-21T00:30:22Z

Prime numbers in a synchronized flow create an interesting visual experience.

Don’t go chasing HTLC waterfalls! #nevent1q…ld0m

2025-11-19T06:17:55Z

Don’t go chasing HTLC waterfalls!

quoting
nevent1q…ld0m
My Friend Jimi - Chasing Waterfalls

The first Nostr transistor!⚡️ ...

2025-11-19T05:55:23Z

The first Nostr transistor!⚡️

Never Ever! ...

2025-11-19T02:28:17Z

Never Ever!

💯 It goes deeper than that. i.e., CloudFlare tunnels and ...

2025-11-19T00:25:58Z

In reply to nevent1q…lw39
_________________________

💯 It goes deeper than that. i.e., CloudFlare tunnels and Umbrel Nostr nodes were still running, but this is only for backing up your Notes, not for relaying them. The clients, NIP-05s, and LNURLs that were CloudFlared through the tunnels remained 🆙 This is 🔑!

Kajoozie Maflingo (nprofile…6rp8)

TheRupertDamnit (nprofile…zgsu)

Derek Ross (nprofile…j2ae)

rabble (nprofile…w9q6)

Alex Gleason (nprofile…stca)

Alex Gleason (nprofile…ag5n)

Shelby (nprofile…65xx)

nprofile1qqsdvyn2a7s68p0hj4f59z593rzzy7dj66vmh28qj0p4pdvqq0xj8ecpzamhxue69uhhyetvv9ujuct60fsk6mewdejhgtcpz3mhxue69uhhyetvv9ujuerpd46hxtnfdu8necsr (nprofile…ecsr)

npub1avyq5j6ec7593qdslh5d6afln9q8yzt622e40gjln99f25c64wlscslw72 (npub1avy…lw72)

Incog (nprofile…hhcx)

https://apps.umbrel.com/app/cloudflared

https://apps.umbrel.com/app/nostr-relay

💯 It goes deeper than that. i.e., CloudFlare tunnels and ...

2025-11-19T00:01:17Z

💯 It goes deeper than that. i.e., CloudFlare tunnels and ...

2025-11-18T23:57:36Z

In reply to nevent1q…jc4p
_________________________

💯 It goes deeper than that. i.e., CloudFlare tunnels and Umbrel Nostr nodes were still running, but this is only for backing up your Notes not for relaying them. The clients, NIP-05s, and LNURLs that were CloudFlared through the tunnels remained 🆙 This is 🔑!

https://apps.umbrel.com/app/cloudflared

https://apps.umbrel.com/app/nostr-relay

This is why LNURL and NIP-05 is flawed. Centralized HTTP DNS ...

2025-11-18T14:18:07Z

This is why LNURL and NIP-05 is flawed. Centralized HTTP DNS servers are not the way.

I ran across this last night from Tim Bouma (nprofile…cxxj) and it’s an interesting approach to the issue. We should look into BitTorrent Mainline DHT as well.

🤳🔏🚥🛜🚥🛜

https://github.com/trbouma/dnspub

The primal.net http service is down because the data is in CloudFlare. The funny think is that CloudFlare tunnels to physical infrastructure would work.

quoting
nevent1q…s27z
Funny that a lots of zap verification are failing because of cloudflare and dependence on lnurl. Maybe we should make that nostr native somehow with bolt12 zaps.

This is why LNURL and NIP-05 is flawed. Centralized HTTP DNS ...

2025-11-18T14:15:29Z

quoting
nevent1q…s27z
Funny that a lots of zap verification are failing because of cloudflare and dependence on lnurl. Maybe we should make that nostr native somehow with bolt12 zaps.

💯 Percent! This is why everyone needs to run their own node in ...

2025-11-18T13:51:17Z

In reply to nevent1q…we26
_________________________

💯 Percent! This is why everyone needs to run their own node in their home and the future of the internet needs to be decentralized.

CloudFlare tunnels to your own nostr relay. Let’s decentralize ...

2025-11-18T13:49:37Z

CloudFlare tunnels to your own nostr relay. Let’s decentralize the internet.

quoting
nevent1q…4nzc
No cloud flare issues with my personal relay…

With the CloudFlare outage it’s more and more of a sign that ...

2025-11-18T13:39:06Z

With the CloudFlare outage it’s more and more of a sign that running decentralized nodes in our homes is important.

Everyone is so busy posting their selfies, watching reels, and wishing everyone a happy birthday on Facebook they don’t realize how unstable we are with centralized internet.

Nostr event nevent1qqs0laqvauc480lpzcf32hpqa69d8snckmv3jjrhdd869xulrj4h3xqzyr0h8xjvj80z32mwxr747n9f4ulhs9n0u4yr9f4crfuze07q3yxz72k4q6a

2025-11-18T06:23:45Z

In reply to nevent1q…wkyf
_________________________

https://github.com/wujifoo/nostr-bip-85-prototype Not sure if ...

2025-11-18T06:22:49Z

In reply to nevent1q…5k5v
_________________________

https://github.com/wujifoo/nostr-bip-85-prototype

Not sure if this is what you had in mind, but the concept is similar.

FYI: I logged in with my nsec and all the accounts I follow got ...

2025-11-17T03:08:09Z

In reply to nevent1q…6vtj
_________________________

FYI: I logged in with my nsec and all the accounts I follow got removed. I was able to restore them but I wanted to give you a heads up.

GnuPG https://gnupg.org/ Content Credentials in ProofMode ...

2025-11-17T02:12:39Z

GnuPG https://gnupg.org/ Content Credentials in ProofMode https://proofmode.org/verify.html change the game from centralized X.509 certificates to utilizing OpenPGP and https://opentimestamps.org OTS.

Here is the C2PA specification. Let’s continue to decentralize proof of personhood! 🤳🔏🚥🛜

https://spec.c2pa.org/specifications/specifications/2.2/index.html

Thank you rabble (nprofile…udwt) for bringing this concept to Nostr.

We have been working with GnuPGP on keygrips computed internally as a hash over the canonical S‑expression of the public key parameters for ISO-7816 NFC cards in NeoPGP via JCOP. These would work as good notary keys for decentralized privacy based OTS attestations.

GnuPG KeyGrips! 🔑🔑🔑

The desire for Vine and non AI content broke Nostr.com 🤣 ...

2025-11-16T20:10:07Z

The desire for Vine and non AI content broke Nostr.com 🤣 Humans will win!

Derek Ross (nprofile…qljc) I am inspecting your vine post

https://divine.video/video/794e4b16a040e773efedd6af23b47fca411e0b6fa274a9180e5043faaacde1ba

I am seeing kind of 34236 in Nostr Debug Tool and found it in NostrHub

https://nostrhub.io/naddr1qvzqqqrcvypzp4mt8lnqzkn3tap6g00r5ps045fvvd84m0x0ql78q9g0plc8gsxuqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqp9hxjupdxucj6mm8qe2f66

How is this going to be supported in other native clients. I have been showing all my Normie friends that use Instagram and TickTock Olas but it is so buggy.

It looks like Nostur is recommending Olas and I can’t find the sha on Primal.

I did see where you posted about the Android app. I am using an iPhone but also downloaded the apk on my Android as well that rabble (nprofile…udwt) shared but all it showed was a divine logo. Is there an APK I am missing?

I also found the blossom video and it is in this post. I am just wondering how it can span across the media of primal and other already built native apps for more interactive content.

This will be a huge win to get not tech folks into Nostr and dominate open provable social media. 🙌

I am wanting to join the efforts and have some ideas around https://NationLocal.com as well.

quoting
nevent1q…p7pf
Hey Nostr,

I need your help. Divine.video as you might have seen is a new video nostr app that i've been working on for the last 3 months.

It got MUCH more attention than I was expecting. Hundreds of millions of people viewed, liked, or shared videos about it. I've got some of the biggest original Viners in my DM's begging to get back on it. The TestFlight hit it's 10k limit in a few hours.

I'm excited but also really stessed out. We've had lots of bugs and Apple and google have been their usual black boxes when it comes to app review.

A bunch of folks have stepped up to help, Derek Ross (nprofile…9kky) got the android build working for example.

Lots of things have broken, nobody really knows how survive a flash flood. I'm sharing this because I need help. We've got a chance to really grow nostr, the idea of a video app that's not got AI slop and does focus on something more human is resonating. People hate what's happening to tiktok, instagram, and youtube shorts where algorithms and the platforms love of AI generated content going viral is taking over. Instead of fighting back we see AI only platforms like MetaAI and Sora. This is an assault on the very idea that people are central to social media. I think big companies see the shine of AI generated content and dream of a world without all these pesky rabble making demands of platforms. If only they could replace the creators with bots.

This call to action felt right to me, but holy shit I had no idea it'd go so viral.

The app has lots of bugs, and we need appstore approval, but at the moment the biggest problem I have is relays. I need you, the nostr community's help. I started out with strfry which we know scales but lacks search. So i started using nosflare, https://github.com/Spl0itable/nosflare , by Luxas (nprofile…4nss) which worked pretty good when we had dozens of users but has had scaling issues and has been hard to debug. But Nosflare is cool. I was able to easily add nip-50 search support, and because it runs on cloudlfare i hoped would scale horizontally. When I told Luxas (nprofile…4nss) I was using nosflare, he said i should have told him... but again I didn't think this would escalate so quickly. So then we tried using the ditto relay https://github.com/andotherstuff/otherstuff-relay by Alex Gleason (nprofile…t7fy) and put a bunch of really beefy servers behind it. Even then it's struggling to keep up.

The thing is, we're pre-launch, we have 10k users in testflight and a mostly read only site at divine.video which is a react app.

I'm a really terrible sysadmin. Yes I've helped run my own mail server since the 90's but I hate it and i'm not good at it. I know my way around my command line, I've compiled my own kernel from source, but fuck i hate it. And now i've got to setup and scale servers to realize the dream of something i've worked on for the last 8 years. I need your help, but maybe i'll digress...

In 2017 I decided to learn crypto, i joined a startup, quantstamp, and built their testnet, a SAT solver to verify smart contracts. I quit because I came to see how scamy the world of ICO's and tokens were. I'm not the only Nostr dev to have explored the 'darkside'. I started my company to build decentralized social, initially trying to take secure scuttlebutt to the mainstream. I built planetary.social, and worked with amazing dev's like mplorentz (nprofile…w4p8) and others we saw Nostr arrive and we pivoted! We built Nos.social, which i'm really proud of but it never took off.

A few months ago I was in talks to help start andotherstuff, but i was also very frustrated with running a company, I wanted to build stuff myself. So I stopped managing people, started a podcast, and really dove in to building with agentic programming. I built a bunch of things I threw away. A lot of bad experiments. In the course of the revolution.social podcast i kept hearing about Vine. I listed to the "Vine 6 seconds that changed the world" podcast: https://vine-six-seconds-that.captivate.fm/ and I talked to people about this social media platform that was shutdown when Jack@nostrfan.com (nprofile…zx6m) was trying to save Twitter when he returned as CEO.

I thought, well Vine is cool, I know folks like PABLOF7z (nprofile…srrg) and others have build nostr video apps, how hard could it be to make a nostrvine app. I started coding, that's why the repo is still called nostrvine: https://github.com/rabble/nostrvine Turns out that it wasn't that had to make something that sort of worked.

Then I thought, it'd be cool to dig up some old vines. I searched the internet, found some on youtube, some on the way back machine, and I thought oh cool, i found a couple hundred popular old vines. Then I hit the motherlode, a community internet preservation project called archiveteam had run crawlers to archive the site: https://wiki.archiveteam.org/index.php/Vine they had about 2.7 TB of vine data, but in these very hard to work with WARC files that are 40GB each! I spent a month or more learning to parse and extract the files. I realized i had the meta data for most vine users, millions of comments, and hundreds of thousands of actual vine videos! It was a nightmare to parse because of the size of the files, the messiness of the data, and the like. But it was a consuming fun project, a puzzle.

At the same time, I was learning about flutter, I've had to rewrite the nostrvine codebase many times as i learned about riverpod, figured out how to get the UI to update smoothly while interacting with nostr. Getting the app to run fast and smooth was really hard. I also had to figure out how to host the damned videos in a way that works. I tried google cloud, cloudflare, and bunny. I made TONS of workers to run all of these services to make the system working. I also was seeing how much people, myself included are frustrated by AI slop, taking over social media. I have an old friend who runs a non-profit tech org, The Guardian Project, they'd make a tool for verifying videos are real for documenting human rights abuses. I thought, hell i could use this proofmode thing they've got to verify that videos are real. People like realness.

Over the last few weeks the pieces came together, I was scheduled to speak at WebSummit with jb55 (nprofile…5cp7) and also to interview Cory Doctorow (nprofile…9grd) on the main stage talking about enshittification of the internet, and how we can resist it, by building things like Divine.

I talked to a reporter from Tech Crunch who'd written a positive article about AndOtherStuff, and she was excited to write an in-depth piece about my vine clone. Once the date was set, I had no choice to go forward. Was the app ready, NO NOT AT ALL. I was literally coding up releases on the plane while flying to Web Summit in Lisbon. I started submitting the app, and getting rejected. It got much better really fast, and basically works.

On the stage at WebSummit when I introduced diVine, the audience clapped politely. I showed the app to people and they sometimes said "oh this will be big" and wanted to play with it. But if you've ever made software, and you show it to people, everybody always finds something nice to say about it.

I had so little faith in diVine taking off that I was planning on taking a few days off to explore Morocco before heading to a non-profit software dev meetup in SF. It was only the last minute that I decided I might need be near a computer and internet connection post launch to see how things are going. Until diVine launched I thought the highlight of my trip and WebSummit would be that a podcast network wanted to pick up revolution.social and help me build an audience around the podcast.

I have never seen anything like this excitement. Just look at tiktok: https://www.tiktok.com/search?q=divine there is a wave of people excited about it. There's a wave of news about it: https://news.google.com/search?q=divine%20vine&hl=en-US&gl=US&ceid=US%3Aen Folks are saying that I'm taking on TikTok, and it's been on the evening TV news all over the place.

This is a dream. More excitement than I ever could have dreamed of. Creating a social media app that reflects all the values I laid out in rights.social . Building something people love and are excited about. When the app's been up, the new videos are amazing, so funny, so creative. When Jack launched Twttr, we didn't get this reaction. It took a lot of time for twitter to emerge as a star. The scaling issues didn't even show up until a year after twitter launched. When Kevin launched Instagram it got 150K signups in the first few days, and I was blown away at how fast it was growing.

If it hadn't been for my messing up getting in to the appStore, and having my relays collapse under the traffic, diVine would have grown much faster. Somehow it hits a nerve.

This is where I need your help, the Nostr community. I've already got help from a ton of folks like the folks from Team Soapbox (nprofile…mrhy) and heatherlarson (nprofile…pa8a) and others i'm forgetting right now... But we need more help. Let's do this as a community.

We're building a permissionless, open future that can't be shutdown by corporate owners. But we only get there if the tech works. We don't get to integrate cashu and show users how there's another business model for social media if we don't make an experience that people enjoy using.

Here's where we are. We've got the new nip for replaceable video events, which is supported by divine and amethyst... https://github.com/nostr-protocol/nips/pull/2072/files we've got the proofmode verification spec i proposed: https://github.com/nostr-protocol/nips/pull/2109 and my weird fork of nosflare which adds the ability to do filter requests that sort on things other than timestamp, it lets us find the most popular old vines: https://github.com/rabble/nosflare

The blossom server for media running on cloudflare mostly works, bunny is mostly working to scale serving the content. But fuck our relays are having trouble. Partially it's because divine doesn't optimize how many relay connections it does, so help with that would be appreciated.. but mostly it's we need to scale the relays, we need to work fast, and reliably. I'm trying to not talk much about Nostr and not make users understand anything about how nostr or keys or relays work.

We need a network of relays, we can dedicate for this, scale horizontally, which respond quickly, and support search. We could have search relays + normal content ones, but doing that requires updates to the released app, which is hard to do because we've got a delay of a day or more per release. So it's best if we can put this all behind relay.divine.video.

In terms of content moderation, my tactic is to provide a pretty heavily moderated experience on the primary relay and media server. But users own their keys, and the app lets users change or add relays and switch media servers. That way we can provide both freedom and the curated experience of users we're enticing away from centralized corporate social. And all of this is open source.

So help! I need nostr sysadmins and scaling folks. Please help. We don't have much time to catch this wave, and I'm in over my head. If you can help, reach out, rabble@rabblelabs.com or send me a DM, i'll add you to a slack room, and we'll figure it out.

Join me and we'll make a social media revolution to make revolution possible.

https://youtu.be/IguMXrgfrg8

2025-11-16T04:01:48Z

In reply to nevent1q…g4zw
_________________________

https://youtu.be/IguMXrgfrg8

I am wanting to build a Nostr app for https://NationLocal.com I ...

2025-11-16T01:37:21Z

I am wanting to build a Nostr app for https://NationLocal.com I was thinking about verifiable businesses, events, and in person offers via BLE and Bitchat. We need local marketing for businesses and maps besides Google and Facebook. Any other ideas? I want to have NFC attestations to verify the location based signed events.

I am wanting to build a Nostr app for https://NationLocal.com. I ...

2025-11-16T01:35:39Z

I am wanting to build a Nostr app for https://NationLocal.com. I was thinking about verifiable businesses, events, and in person offers via BLE and Bitchat. We need local marketing for businesses and maps besides Google and Facebook. Any other ideas? I want to have NFC attestations to verify the location based signed events.