@npub1qe3e...zefe has wss://relay.nosto.re been updated to accept the v2 kinds?

nsites enable interesting possibilities that are extremely portable. They also have the potential to go viral because of how they work. Here is a very basic "napp homepage" application I put together to demonstrate what I mean. This nsite isn’t built for my npub, it detects the npub through the gateway, and from that, it has everything it needs to behave like a personalized application. So what? Well, what this means is that when an nsite follows this pattern, it can propagate from one user to the next without requiring the user to build the site themselves or upload any additional blobs. The blobs are already there, all the nsite needs is your npub and for you to sign and publish an event. Just click "borrow this" to see what I mean at the link below: https://npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx.nsite.run/ The possibilities here are endless. Producing viral sites with this medium has an incredibly low bar of entry and is wildly participatory. For instance, you can detect that an authenticated npub (NIP-46, NIP-07) is the same as the current page's npub and then provide them an interface to modify something in the app, such as a background. That data could be persisted in 30078 events, and then other users would see that modification. This is all without touching the blobs themselves or updating any source code. The network effect potential of this is immense. The "borrow this" button will soon be released as a package as well as a bundle hosted on Blossom for direct import into any nsite. Stay tuned. @npub1derg...xzpc @PABLOF7z @hzrd149 @npub1hw6a...65gr @fiatjaf @Alex Gleason @npub1gzuu...a5ds @npub1jlrs...ynqn @npub132er...zmdh @npub1l3cg...6vs2 @npub182jc...m4rf @npub1c03r...sgwx @Sync @npub1qe3e...zefe @npub149p5...722q Sidenote: Work will need to be done by gateways to conduct trust rankings similar to those done by Zapstore. #nsite

who's going to be the first to host an nsite gateway over FIPs?