I want the internet in my pocket.

I was bored and got annoyed with nsites being unreliable/slow. So I vibed together this nsite-deck.

- Load any nsite you've visited before when OFFLINE

- Manage locally stored sites at 'home.nsite'

https://blossom.primal.net/289bad06e79ae34afadb99cc107dc797a3ff8406fc63fad203b08abb0e305b9a.mp4

in the video i show:

- Any [npub].nsite gets resolved, locally

- First load = pull from public relays 30ms

- Second load = load from cache 7ms

- Managing cached sites

Source: nostr://npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/nsite-deck

CC nostr:nprofile1qyv8wumn8ghj76twvfhhstnjv4kxz7tn9ekxzmny9uqsuamnwvaz7tmwdaejumr0dshsqgpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg5502tfpf nostr:nprofile1qywhwumn8ghj7mr4de3kscn00qh8xctwv3mkjcmg9enxzund9uqsuamnwvaz7tmwdaejumr0dshsqg88wxhskpwga90umah7kdgq23xjlvwv6wz83r5lfy9m8m3garkkduy3ntru nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfx5ltf6v nostr:nprofile1qy2hwumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t0qqsvswpas8wjgsr8gkmggzd7grt8y8pszq55vsr8lnzs5fwalyfe2jg4yre37

Reply to this note

Please Login to reply.

Discussion

I like it.

Next time you are bored try a cloning machine because we could use a couple more Arjenโ€™s ๐Ÿซถ amazing stuff

Bad ass!

The first load both caches it AND saves to your local relay/blossom setup.

It comes with embedded relay and blossom. If you have your own configured it will use that instead.

I've tested this on Ubuntu (24) and MacOS (Sonoma) btw.

๐Ÿ‘€

I don't get what is happening, are you running something or is it all in the browser? How do I test this?

Regardless of that we should be doing nevent1-sites, immutable, not npub1-sites.

https://gitworkshop.dev/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/nsite-deck

Clone & build this + install script. (Careful if you run on something other than ubuntu or have custom dns stuff set up)

Will upload a bit better vid shortly.

I agree, immutable is what i want as well. I realized only after implementing that nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr just updated the spec. This one still uses the old spec.

nvevent1 in domain name might be tricky as there's a 63 character limit to domains.

One option is to have one immutable event for each version of a site, like a snapshot. And one replacable version of the same event to quickly find the latest version. That way I can 'pin' or rollback any version from my end.

Why?

Is NIP-01 going to be modified with a filter flag so one event per pubkey can be returned?.. .Emulating the filter behavior of addressable events.

We should run a prediction market for this.

Am I missing something or is this not useful except for data that does not change? Nearly all of the websites I use have live or changing data, meaning if I access an offline version of my last visit, itโ€™s useless.

Static site does not equal a 'dumb' website. Nostr clients can be served this way too.

If i have my local relay and blossom server running. I can do everything i want to do while offline. Read my timeline, write responses, publish blogs.

Local resolution is the goal, gateways were a stop gap. This is how the `nsyte run` command works, though it was built as an example and for debugging purposes. This is over nodns yeah?

it's separate from noDNS, but the way I did the capture of the '*.nsite' zone is something i want to bring to noDNS as well. That's something I learned about recently. (easier to deploy in existing systems).