We had chatted a bit about this. I have an access token in my Pinafore client, so wasn’t affected by the whitelisting change; while some others were.
You made a suggestion at Nolan’s Git, and he has now updated the Admin Guide including the string that is needed to permit a new connection.
If you see this in the output:
Then Pinafore should work as expected!
Otherwise, if the instance admin would like to whitelist only certain websites (including Pinafore) to work with CORS, then they will need to make sure that the server echoes:
That is a header on https://koyu.space/api/v1/instance – and I don’t see the “Access-Control-etc” there atm.
Nolan has a link on the page with suggestions on how to enable that in Apache and Ngixx, etc.
Just a note, if possible. Otherwise I continue to use the web client Thank you!
I use the Beta or Development server – https://dev.pinafore.social