Include access token when fetching user followers/followings #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GoToSocial requires authentication on these endpoints, and not supplying the token was causing these requests to fail with a 401 error.
As far as I can tell, these calls only ever hit the configured server, and there shouldn't be any issues with providing a token when it isn't required, so I don't think there's any problems with this change. Tested it against my own GoToSocial instance and follower information is fetched with no problems.
Fixes #117.