-
|
I'm playing with the Mastodon API to create a web app that visualises a user's Mastodon timeline. This will be something that possibly only I will think is cool, but I still want to make it open to other users if I can. I've set up a Mastodon instance to test this with. I happened to set it up following this documentation using a I realised this creates a minor problem when the application tries to access a user's Mastodon account using OAuth. If a user tells my application what they consider to be their server name, example.com, then I don't actually know their instance URL to do the auth. I (finally) realised that WebFinger may be the answer to this. I could request something like If this is the right way to do it, would it be a useful addition to the documentation on obtaining client app access. It sure would've helped me, but is it too niche? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
You're on the right track, webfinger is a good way to resolve the instance URL for OAuth. This is standard practice in the Fediverse for resolving account details and it should work across Mastodon instances. Should be addded to the docs. |
Beta Was this translation helpful? Give feedback.
-
|
My instance has a different |
Beta Was this translation helpful? Give feedback.
-
|
Differentiating between WEB_DOMAIN and LOCAL_DOMAIN might cause issues for some apps. Can you normalize usernames to LOCAL_DOMAIN on your end? |
Beta Was this translation helpful? Give feedback.
-
Sorry, what do you mean by this? |
Beta Was this translation helpful? Give feedback.
-
|
I mean that if you have multiple domains, ensure that usernames are consistently mapped to your LOCAL_DOMAIN in your app's logic. If you're running an app interacting with Mastodon and you encounter issues with usernames from different domains (WEB_DOMAIN and LOCAL_DOMAIN), you should ensure that your app uses one consistent domain (preferably LOCAL_DOMAIN) for all operations like OAuth. Does that help or am I misinterpreting your question? |
Beta Was this translation helpful? Give feedback.
You're on the right track, webfinger is a good way to resolve the instance URL for OAuth. This is standard practice in the Fediverse for resolving account details and it should work across Mastodon instances. Should be addded to the docs.