Open h3poteto opened 5 years ago
I'm hoping it is helpful to add a bit of context about "what happens now" when trying to connect Whalebird to pixelfed.social:
When clicking to add an account, I am successfully sent to Pixelfed's oauth page:
However, clicking the "authorize" button causes the page to render again instead of passing it back to the app.
I suspect it might have to do with Pixelfed's OAuth not working well with urn for the URL? In other words, this might not be something that Whalebird can fix. I'm hoping I'm wrong, though. :)
The problem could be much deeper than this. I've found several applications have a hard time connecting to pixelfed successfully. Whalebird is one that actually finds a way to at least offer the OAuth page, which is a huge step over a lot of the other clients! I think one other client actually handles the redirect, but fails at that point, and only one client (Mastonaut) has ever successfully connected to Pixelfed.
Possibly related:
@h3poteto ok, awesome! thanks. :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can remove the stale label with /remove-stale
comment. Thank you for your contributions.
/remove-stale
/remove-stale
/remove-stale
Describe
Support Pixelfed.
I think that we will need intermediate layer which absorb the difference between Mastodon, Pleroma, Pixelfed, and Misskey. refs: #816
Why
https://tabletop.social/@angeles/103226545305746275