it's already there and with AuthPolicies, meaning developers can write custom logic to decide how to handle AUTH challenges on a per relay basis (e.g. "auto-auth for user's NIP-65 relays and ask only once per new relay", or "auto-auth for user's follows NIP-65s")

Reply to this note

Please Login to reply.

Discussion

oh yeah, i'm gonna test it and give a feedback report from a dev perspective, so you better not be lying

care to explain this difference?

#primal is a joke on DMs right now, #coracle actually works

god i hate how lame this shit is

whoops

anyhow, point is shown... primal.net is not working with DMs at all let alone authed, i wrote an auth flow to get around the problem of no auth on most clients and it works perfectly on coracle and it was working ok a few days ago on primal but now, no beans

you don't realise how broken this shit is bro, at least nostr:nprofile1qyfhwumn8ghj7mmxve3ksctfdch8qatz9uqsuamnwvaz7tmwdaejumr0dshszxthwden5te0dphkgmrzdajzumn0wd68yvfwvdhk6tcqyztuwzjyxe4x2dwpgken87tna2rdlhpd02va5cvvgrrywpddnr3jyhdw0my has some dev discipline

It's probably relay selections, I don't think primal is very good at that

yeah, that's kinda a big problem...