Brainstorming!

Objectives: Reduce dependency on traditional domains across my Nostr web app.

Why: Traditional domains are centralized and controlled by governments. Not ideal for freedom tools/apps.

Idea: Create a lightweight static website called "NostrHub," which will serve as a quick-access hub to all my other Nostr web apps.

Plan:

1. First Step: Host the lightweight NostrHub website on Nostr relays and IPFS, making it accessible through TOR, IPFS gateways, Freenet, and other decentralized storage or P2P access options.

2. Second Step (my favorite, though a bit unorthodox): Convert the NostrHub website/code into an offline bundle that can be shared as a zip file. When unzipped and clicked, this bundle will open the NostrHub page in your browser, running locally without relying on domains or web hosting—essentially self-hosted.

The offline website bundle also addresses a more fundamental issue with the web ecosystem. Unlike traditional websites, offline bundled sites can’t be unilaterally changed or modified by the developer, making them trustless and truly giving users full control over the website, its code, and any updates.

This approach will eliminate the single point of failure posed by centralized domains, make all apps easily accessible, and provide users with a more private way to access them.

This is a rough outline. Suggestions for improvements are welcome!

nostr:nevent1qqszsed8nghq3u57vx0zpwsvs3ujvjw2f3vxgjnnq2cw83l26tp7acqpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tczyrr0wpmlz6va2r8e92t990ltl7kqtlrgg2u7uwgs38v4nw9dt4y06qcyqqqqqqggkx6kh

Reply to this note

Please Login to reply.

Discussion

Awww I haven’t seen you in a long time gorgeous friend 💜🫂

Awww I have missed you 🫂🫂

Likewise,

I took a break to concentrate on my PhD and other objectives. Fortunately, everything worked out well.

By the way, I'll always be a part of Nostr. 🤍

Wonderful to hear 💜🫂

So far

Achieved: Unified dashboard for all my Nostr apps.

In progress: Reducing domain dependency.

Added: Quick shortcuts for Nostr backups, publishing notes & blogs, and accessing zPay.live purchases.

nostr:nevent1qqs8lfvqnz54qw86akqmgczappdurlcqmvsf7sd8d8usvzcgncssxegpzpmhxue69uhk2tnwdaejumr0dshsygxx7urh795e65x0j25k22l7hlavqh7xss4eacu3pzwetxu26h2gl5psgqqqqqqssm96qf

The first prototype of zap.store ever featured something like this, nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr packaged the nostrudel PWA into a .pwa file that we assigned the application/pwa+zip mime type to (offline bundle). This "pwa" would then be deployed and served locally. Plan to put that back! Maybe we can work on an interoperable standard?

Sure, is there any functional implementation of this standard at the moment?

Btw nostrudel is a highly capable PWA client, it could really play a very significant role in the Nostr web app ecosystem, especially micro-apps.

Agreed!

Implementation not really. But it's so simple, pretty much what I described is what we got working

Check out https://nsite.lol/ and https://github.com/nostr-protocol/nips/pull/1538

Its exactly what you described in step 1

Thanks, I think this might be it. I tested some other Nostr web hostings, & this one is by far the best. It's super straightforward & effectively mitigates the fundamental issues.

Interestingly, I was open to all types of options, even outside Nostr. I tested dozens so far, and Nostr is literally the best option I've found. We really might be onto something.

Demo: https://nostr.download/d025c2ee6291ccf396c8d01582b6d700c41e20b53552d06b7fefb86aae6c81d7

Glad it works :)

If your interested in helping we have a small telegram group for fixing bugs and new ideas https://t.me/+Ho8zFD8QId01MmMx

Thank you for the invitation. I'd love to! 🤍