BitcoinJungle on Nostr: I bought the domain nostr.house … I have a vision for it, but am wondering if ...
I bought the domain nostr.house … I have a vision for it, but am wondering if anyone can point me in the direction of the easiest/best way to build it out…
I want to let users create their own relay as subdomains…Say `bitcoin.nostr.house`, `surfing.nostr.house`, `steak.nostr.house`, etc..
But for the UX, I want a user to just add a relay in their client. They shouldn’t have to go to some website to see if a relay exists and create one if it doesn’t.
Say they enter `wss://knitting.nostr.house` as a new relay in their client. If the subdomain `knitting` doesn’t exist yet, we’ll set up a new `nostr-rs-relay` instance for that subdomain. If it already exists, it’ll just connect that user to that relay.
Ideally I’d like to be able to do all this without modifying `nostr-rs-relay` itself. Perhaps just a middleware script?
Anyone do something like this before where accessing a subdomain creates a new application instance?
I want to let users create their own relay as subdomains…Say `bitcoin.nostr.house`, `surfing.nostr.house`, `steak.nostr.house`, etc..
But for the UX, I want a user to just add a relay in their client. They shouldn’t have to go to some website to see if a relay exists and create one if it doesn’t.
Say they enter `wss://knitting.nostr.house` as a new relay in their client. If the subdomain `knitting` doesn’t exist yet, we’ll set up a new `nostr-rs-relay` instance for that subdomain. If it already exists, it’ll just connect that user to that relay.
Ideally I’d like to be able to do all this without modifying `nostr-rs-relay` itself. Perhaps just a middleware script?
Anyone do something like this before where accessing a subdomain creates a new application instance?