Shosho app currently can't connect.
Does NIP-42 auth still work with a redirect?
Has the API itself changed? Different endpoints or queries or responses?
Trying to diagnose.
Discussion
* meant NIP-98 not NIP-42
Yea i dont think i change fix it on my side, its because NIP-98 has the full URL and the host part doesnt match, if you redirect then your NIP-98 event will be rejected, you need to manually update the app to use the new API endpoint
I figured. Is there any possibility to continue to run the old endpoint until I can migrate?
I am AFK for a week.
I am attempting to connect to the new API
"zap.stream/api/v1/account" With NIP-98 auth returns 200 with html body rather than expected API response
I also tried
"api.zap.stream/api/v1/account" returns 404
"api.zap.stream/api/nostr" returns 500
Do I have the right URL and auth?
Is this routing to the API correctly?
The new URL is api-core.zap.stream, there is way to use redirects because nip98 has the full URL in the auth event
No, the data was migrated to the new database, the old one is readonly
I will have to disable host name validation by modifying the backend maybe, checking
I have tested and can connect with the new url.
If the old API is no op, and the new API has the same endpoints, then serving the new API from the old domain would solve my issue.
Is that possible?
I think its up to your client code to follow redirects with Auth header, i think it has to be done manually, the reason for the redirects is that the api path is different on core, ill try to do something on my side first, if that doesnt work for you you can use the new api URL