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.

Reply to this note

Please Login to reply.

Discussion

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.