Added an example of this functionality to the small zap-galaxy project I vibe coded https://zap-galaxy.shakespeare.wtf/ The app is now aware its deployed as an nsite and shows a picker of previous versions of itself. then when a version is selected it will navigate to that specific version. The version is isn't hard-coded, its fetched live from nostr relays so that when a new version is deploy it will show up in the list. or the user can load the latest version that stays up-to-date with the deployment. View quoted note →

I vibe coded support for publishing nsite versions from shakespeare. based on the pending PR

GitHub

Add aggregate hash and pinned sites to NIP-5A by hzrd149 · Pull Request #2287 · nostr-protocol/nips

The PR adds an optional x tag, a new 5128 pinned site manifest kind, and the upstream "app" tags to NIP-5A The goal with the aggregate ha...

This will allow apps built in shakespeare and deploy as an nsite to have a history of all previous versions. so if you vibe code a cool nostr app and deploy it users can always go back and run older versions. This is hard to show with screenshots, but this effectively enables "internet archive like" behavior for nostr apps deployed from shakespeare

GM protocol now supports images, at some point I should stop spending tokens on this dumb app 😁

Zaps coming to gitworkshop. I can't wait to start zapping issues and PRs :D View quoted note →