Relay Management now available

Reply to this note

Please Login to reply.

Discussion

Nice!

Documentation of contract management probably should not rely on nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s or nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 goodwill / not nuking their relays.

Yall should consider:

1) funneling customers into paid professional relays like nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz nostr.wine, and agree on a term of data storage, geographical redundancy, server redundancy

2) consider sigit spinning up a contract โ€œkindโ€/equivalent relay with characteristics described above

#otherstuff

That's not my relay!

For some reason we didn't get this notification! For info - we don't rely on (or push) public relays, we use the relays defined by the user (extension / nip-05 / kind 10002) plus the app-relay (sigit relay unless self-hosting and self-adjusted).

Is it possible to allow #Citrine local relay support for automatic backup? Tried but field won't accept ws://

Great feedback - yeah that's not working right now but we'll fix it for the MVP!

Here's the issue: https://git.nostrdev.com/sigit/sigit.io/issues/297

this was fixed some weeks ago: https://git.nostrdev.com/sigit/sigit.io/releases