Alex Kirk

Sorry about this, I’ve fixed this in version 2.8.7, released just now. It was a very simply typo.

Thank you for updating your report that were able to identify and fix the problem yourself. Highly appreciated!

Hi! Thanks for sharing this usecase! Do you have a Github account and would be willing to share this at https://github.com/akirk/friends/issues ? If not I am happy to relay this there to track it.

I don’t have immediate plans to implement this but I see some obstacles where I’d be curious how to solve them. For example: who should choose which feeds to be followed per user? i.e. what if one user adds an RSS feed to a person they follow and another one doesn’t want that?

Alright, it turns out it was a combination of two things: On the one side a bug on Friends that I fixed with the newly released 2.8.4. Additionally Manton of micro.blog fixed a detail in their implementation of webfinger. Thanks, Manton!

Could you please try again and tell me if it works now with the new version? Thanks!

I see! Looks like there is currently a bug at micro.blog regarding their ActivityPub implementation. I’ve contacted the founder and hope to get it fixed soon.

Hi! Are you trying to subscribe to a micro.blog using ActivityPub? Typically this would actually be via a JSONFeed like this:

The plugin is WPS Hide Login.

Thanks, this allowed me to fix it: https://github.com/akirk/enable-mastodon-apps/pull/49 (not yet released).

The Elk redirect URL looks fine. Luckily they are open source, so it fails here:

https://github.com/elk-zone/elk/blob/3adf92ea56f7237ff8918d153d132c1ce688b236/server/api/%5Bserver%5D/oauth/%5Borigin%5D.ts#L44

Could you just try to manually delete the app and then use the new option again? Maybe something failed there the first time.

which I later saw wasn’t listed as supported on the plugin page.

The list on the plugin page is not intended to suggest support. In theory, all Mastodon apps should be supported. A big part of the problems come from assumptions that those apps make based on how Mastodon implements their API vs. how they defined it in the API documentation.

The setting let me log in to elk and click the Authorize button, but then I got:

{“url”:”/api/jseggers.com/oauth/https%3A%2F%2Felk.zone?code=9a6720bfbf63bdf48ced9d4e31429fcacca8efb2″,”statusCode”:400,”statusMessage”:”Could not complete log in.”,”message”:”Could not complete log in.”,”stack”:””}

Hm, this indicates to me that the redirect URI of the app was not retrieved correctly from the redirect_uri provided. Could you check in your settings under Apps? The redirect URI should start with https://elk.zone/api/, for you it might miss that elk.zone?

To solve this, I probably need to make the redirect URI editable.

Yes – I have a plugin that changes the login URL. I disabled that and now get to the login screen.

This is good news! Would you mind sharing which plugin you are using so that I can investigate how we can make them play nicely with each other?

I authenticate and then I get the following:

{“error”:”redirect_uri_mismatch”,”error_description”:”The redirect URI provided is missing or does not match”,”error_uri”:”http:\/\/tools.ietf.org\/html\/rfc6749#section-3.1.2″}

For which app is this?

However, I’m getting the message in the app that says, “Required field ‘url’ of type String was null in Account”

Thanks, I’ll try and see if I can find in which field this happens.

Tusky keeps crashing

This might be caused by the same problem from above.

I get the following with Elk: {“error”:”invalid_client”,”error_description”:”The client id supplied is invalid”}

This is likely because you have deleted the Elk app, thus the credentials it’s trying to use no longer exist. I have released 0.6.2 which has a new setting to remidy this: please activate the “Implicitly re-register the next unknown client” setting and try again.

ERR_TOO_MANY_REDIRECTS

Could it be that you are doing something to your wp-loing URL? The authentication happens there and it identifies the URL via teh standard wp_login_url() which looks like it’s failing. Does it display the URL with too many redirects? Is it your wp-login URL?

Hi Jonathan, sorry for the trouble! Could you try your own blog URL in this tester app that I created? https://akirk.github.io/mastodon-api-tester/

Clicking “Authorize” should then take you to your WordPress login page and back again after authorizing.

Then you could click the “verify_credentials” endpoint to see if it’s working.

If not, the tester should be able to show you an error message that should help us here in identifying the problem.

Hi, thanks for flagging this but I am not sure the plugin is causing this. It doesn’t try to access a htaccess file.

The IndieAuth plugin used to make problems but my fix was merged and is included in the latest version 4.4.0. Could you try and disable that plugin? If it works now, I need to rework the fix for IndieAuth.

Hi, sorry about your trouble!

Fedilab should work but could you get me the exact error message?

One other thing you can check is on the Settings > Mastodon Apps page whether Fedilab is listed under apps.

Thank you very much!