nsite is a building block for something else; at least for me.

Gateways don't have to be servers, they could be native.

correct link: https://npub1nsyte9neefm3jle7dg5gw6mhchxyk75a6f5dng70l4l3a2mx0nashqv2jk.nsite.lol/

Gateways don't have to be on remote servers, they could be native apps.

If a website goes down for whatever reason and you are trying to access it, you won't care that it takes an extra 2 seconds.

There are many nsites already, here's one:

I haven't deployed it as an nsite. But there are many nsites, here's one: https://npub1nsyte9neefm3jle7dg5gw6mhchxyk75a6f5dng70l4l3a2mx0nashqv2jk.nsite.lol/

nsite.lol is a gateway, it requires a subdomain. There is no "real showcase," just a list of tools for a young ecosystem. Gateways should have simple homepages.

nostr can be used as a decentralized and organically populated datastore with a consistent, permissionless API. That's how I've been using it for the last 7 months

It's a great client