The nsite specification was updated recently, and the ecosystem has become stagnant. While some issues remain in the specification, the root note changes simplified and optimized nsites, speeding up resolution by at least 3x and reduces resolution and deployment error rates when compared to nsite v1.



In the spirit of moving fast and breaking things, I have updated http://nsite.run to include an e2e demo. https://nsite.run now includes an interface to deploy an nsite with a few clicks, has an nsite v2 gateway, blossom server and nsite relay. The gateway at http://nsite.run will eventually become a forwarder that picks an online gateway once there are reliable v2 gateways online. The services provided by https://nsite.run exist solely so that "it just works," but the goal will be for it to eventually disappear and replaced by community ran infrastructure.

Should you update your nsite libraries? Up to you, go at your own pace, keep an eye on the specification. If you update your existing software, or produce new nsite v2 related software or services, just submit a pull request to the repo (github.com/sandwichfarm/nsite.run) and one of the admins will help you get it merged. Also be sure to add your software and service offerings to awesome-nsite: https://github.com/nostrver-se/awesome-nsite

nsyte v0.22.0+ is now nsite v2 compliant without backwards compatibility. nsite v2 compatible releases are available pre-releases on github, otherwise build from source (recommended ofc). If you you use nsyte and don't want to upgrade, use v0.21.x. Newest v2 compatible release has many new features that help further diagnose potential deployment issues: https://github.com/sandwichfarm/nsyte/releases/tag/v0.23.0

@hzrd149 @florian @Sync @Lez @Lez Koma @c03rad0r @Sebastix @Alex Gleason @Gigi @PABLOF7z @Schlaus Kwab @Soapbox @Kieran @Sats McRyan

This is my last contribution to nostr, for a while. It's been real.