Nostr Web Client

I'm having trouble today configuring my newish gossip account to have write access to relays, and even in publishing the 10002 relay list event itself, which most relays are rejecting because I don't have write access to them.

It feels like (for new user accounts) that nostr is down, a walled garden that you cannot get into. And I'm using tools that most people wouldn't have access to, like a NIP-11 reader.

wss://nostr.wine/ - blocked: not an active paid member

wss://at.nostrworks.com/ - blocked: pubkey not admitted

wss://nostr.oxtr.dev/: ERROR: Websocket: HTTP error: 502 Bad Gateway

wss://nostr-dev.wellorder.net/: ERROR: Websocket: HTTP error: 503 Service Unavailable

wss://eden.nostr.land/ - blocked: pubkey not admitted

wss://nostr-pub.wellorder.net/ - blocked: spam not permitted

I tried to signup to eden.nostr.land but it either times out, or if I click twice it says that I'm paid (but I'm not and it rejects writes).

We need to make this easier. I'm ready to help from the client side if you have suggestions for gossip client.

nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m nostr:npub1xhfxu35se0s63x90v8xr29txr66l5a3m277skshy2zvu3ve0658sla4xw3 nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4

Reply to this note

Please Login to reply.

Discussion

Mike Dilger ☑️ 2y ago

Maybe gossip needs a "Relays > Sign-Up" page with a list of links to relays you can sign up for, based on relays that gossip has discovered and which advertise such a thing in their NIP-11. I see that NIP-11 has changed quite a bit, and I've been too busy to notice.

Ok well my thinking now is that I will do this as I describe here. Please comment if you think I should do differently.

pjv 2y ago

I've been noticing for a while that there doesn't seem to be a clearcut (interoperable) way to determine whether a given relay requires payment to post there or not. If you do a lot of manual digging and searching you can figure it out on a relay-by-relay basis but that seems unacceptable from a UI/UX point of view unless we (devs) want nostr to be geek-only.

I think for this issue what's probably needed is some kind of push to make both relays and clients really fully implement the "Server Limitations" (at least), and also the "pay-to-relay" blocks from the "extra fields" in NIP-11. So relays need to return those fields and clients need to parse those fields and if the relay has `limitations.payment_required: true` then clients should display that somehow so that it's easy for a user to know whether they can post to a relay right off or whether they need to do something special first (pay, configure POW, etc).

Too early for this now, but it would also be great somewhere down the road if there were a NIP that standardized how to pay for pay-to-post relays in a way that it could be implemented within clients such that users could do it all from within their client with a click or two. In my perfect world, this payment would not be limited to bitcoin / satoshis, but would instead be completely agnostic so that relays could take payment however they want and users could choose from among whatever choices the relay offered.

pjv 2y ago

Also nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c, it might be good to allow gossip users to override the default POW settings on a relay-by-relay basis. Or maybe not even need to do that manually but just have a general setting to automatically do whatever POW that a relay requires in `limitations.min_pow_difficulty`.

n 2y ago

#[1]

n 2y ago

#[1]

Cameri🐦‍🔥 2y ago

I checked your pubkey and it’s allowed 😅