Yup i wrote this demo in js last year since there was only a C# sharp demo. There are actually 2 repos and it makes sense from the backend. Can also use nip42 auth afaik.
nostr:nprofile1qqsrs7xetkmms4xr5rfm944hh7dl9zekzc47vsex74fphfcu7w6956gpr9mhxue69uhks6tkv46xzmrt9ehx7um5wgcjucm0d5q3jamnwvaz7tmswfjk66t4d5h8qunfd4skctnwv46z7qg5waehxw309aex2mrp0yhxgctdw4eju6t00n89td and I have discussed this and thought the NIP-98 could be used for that.
Discussion
What does it mean to have “auth”?
Well … it means the browser user who claims to be pubkey actually is in possession of the private key. Nothing more.
So, how does this work?
> “- redirect to another site with auth”
Well … it means that the “other site” can use “auth” to allow CRUD operations within the “black box” of their “other server”. Nothing more.
This is usefull for black box apps to interoperate alongside Nostr, but NOT for “sign Nostr events across sites with a single login” solving for the mobile login problem.
Am I missing something?