Nostr Web Client

Thanks, just tested the integration. It seems to be working basically correctly, except that inbox is misusing the `auth-required:` prefix to block non-DM filters, even when auth is already successful. Coracle handles it fine, but it may confuse other implementations, `blocked:` is the correct prefix. nostr:nprofile1qyghwumn8ghj7mn0wd68ytnvv9hxgtcqypex583xrnryw3n5aq59uw23kwa38xlf5aeart85nhyx3kuxrgwpzjh056v the reason you might not be seeing inbox connect is coracle requires the user to enable messages to avoid a million signature requests. Try visiting the messages page and see if it connects. nostr:nprofile1qyv8wumn8ghj7cmjv4shgu3wdehhxarj9emkjmn99uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3samnwvaz7tmrv4kxcctj9ehx7um5wgh8w6twv5hsz9mhwden5te0d9hxymmc9ehx7um5wgh8w6twv5hsqgpass40an279ylj3dnz0yehqj3lhr8p2w4fr4us4vgldf6j639y954mdm05, I'm also seeing none of my recent messages coming from inbox. I'm not sure if this is intentional adherence to outbox (in which case it's correct), or if your scraper/multiplexer isn't working as intended.

franzap 7mo ago

Earlier today, filter was not connecting either.

I am trying out nostr.land for a bit. Maybe that sheds some light on all this? I'll report back.

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcpr9mhxue69uhkscnj9e3k7unpvdkx2tnnda3kjctv9uqzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezyx6uqg given I *only* have wss://nostr.land (and just checked my 10002 on purplepag.es) why is Coracle broadcasting my latest post to 5 relays (nostr.land, nostr.wine, inbox.nostr.wine, creator.nostr.wine, etc)?

Reply to this note

Please Login to reply.

Discussion

franzap 7mo ago

Appreciate the level of information you put in Details!

However, more puzzling results:

Dikaios1517 7mo ago

Coracle will write replies to the inbox relays of those you have tagged in the reply. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is using relay.damus.io, nos.lol, and hbr.coracle.social as inbox relays. nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz is using creatr.nostr.wine, among others.

Silberengel 7mo ago

Yes, this is what is redundant with filter.nostr.wine, as it also does that. It is its own mailbox implementation.

Dikaios1517 7mo ago

Interesting. I knew about its blastr relays, but did not know it also uses NIP-65 for replies to post to the inbox relays of those mentioned.

Is this something we should be expecting relays to handle for us, rather than clients?

franzap 7mo ago

I think our collective paranoia is negatively affecting UX.

As long as these all-in-one relays do not censor it's a superior solution with less waste.

Censorship incentives are low, they can be swapped immediately for a different provider and affect their brand reputation.

Silberengel 7mo ago

Yeah, we have a set of powerful community relays, and clients mostly just mess them up.

And every client is different...

hodlbod 7mo ago

Our collective paranoia is all we really have

atyh 7mo ago

who sent you?

franzap 7mo ago

Some paranoia is helpful, it is also possible to go too far!

hodlbod 7mo ago

Check your "max relays per request" setting. If you are sending/requesting from fewer than than number of relays, coracle will fall back to that number. Coracle wasn't really designed for relay selection tuning, but to "just work" no matter how bad people's configurations were. That could be changed, but it's unclear to me how much it would only work for power users.