Can't connect to instance where account url is different from subdomain the api is listening on
Example: https://social.vivaldi.net
https://social.vivaldi.net/api/v1/instance
{
"uri": "vivaldi.net"
...
API calls should be made on social.vivaldi.net, but as it stands now we will save "vivaldi.net" and use that as a domain... It won't work. Not ideal.
We should reconsider using a normalised version of the user's input instead of just taking what the server says...
Edited by Matthieu