marius on Nostr: #[0] I have the server side (on #[1]) and client side on the link aggregator that ...
npub1u27r9h3j9pvrplaffsmpn698e8xhmuqhdgcxldv67ammql9pumnqha3qfq (npub1u27…3qfq) I have the server side (on npub12d09x24e3veh9chfcr27t6mhkagj5c82vk6tqw98lvtzn46l4xpsxfszqa (npub12d0…szqa)) and client side on the link aggregator that uses it as a backend, called npub128acrfwfs4rnl4fdhzrl88gcsq96rhyqxrc9qf5d0e4trkp23kfqa5fdgf (npub128a…fdgf)
But sadly I didn't interop with other clients/servers for either of them.
The main challenges that I can think of:
1/ when a user wants to login using a new client to the server it should be dynamically created on the server.
2/ discoverability of OAuth2 endpoints for each actor - this is handled somewhat by the AP spec.
But sadly I didn't interop with other clients/servers for either of them.
The main challenges that I can think of:
1/ when a user wants to login using a new client to the server it should be dynamically created on the server.
2/ discoverability of OAuth2 endpoints for each actor - this is handled somewhat by the AP spec.