Many things / nsites seems to be broken at the moment.
Time-outs / 404's everywhere...
Are things too centralized atm (Blossom servers offline / not available)?
Discussion
My nsite.lol gateway has been really unstable lately, and I think some relays have been removing old nsite events automatically. I don't think there is any issues with the blossom servers, they seem to be serving the html,css,js files fine
I setup a relay that only accepts nsite events, so maybe that will help?
wss://relay.nsite.lol
I also have issues with my gateway https://nsite.nosto.re and just like you I also have a relay there which accepts nsite events ;)
cool, but not sure its necessary to accept 24242 events since they are ephemeral. also would be good to accept 10002 events since they help find pubkeys relays
True
For 10002 I also run the https://profiles.nostrver.se
The most reliable way to access nsites now is to use the nsyte cli by nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx
Then "nsyte run" will start a local gateway
It is still having some issues, and I haven't been able to track down what's going on. Would be good to have a second pair of eyes on it.
👍🏻 Havent used it yet, I always used nsite-cli from nostr:npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxc so far
It is former from nsyte-cli, has binaries, doesn't require npx, supports bunkers + many other useful features
We need more blossom servers. Dynamic blossom server discovery over nostr would be useful as well.