Bitlbee Mastodon aborts a connect to Mastodon 3.0.1 with 404

I've been using your bitlbee plugin and I've been quite pleased with it.

I noticed a problem with a specific instance: mastodon.coder.town. The login attempt looks like this:

Logging in: Verifying credentials
Logging in: Getting home timeline
Logging in: Logged in
Error: Stream closed (404 Not Found)
Signing off..

My first thought was that the instance had a problem with API access. But I was able to login through pinafore.social. The notable difference is that pinafore never expects the user to supply the base_url. That service simple figures it out. So I wonder if my problem could be that having base_url = `https://mastodon.coder.town/api/v1' is incorrect. I'm not sure how to discover what the correct API URL is, but it would certainly be useful if the bitlbee plugin could auto-default to a correct base_url the way Pinafore apparently does.

– Gavin 2020-01-17 16:57 UTC

Tags: Open

Comments

Can you build the latest commit from the master branch? There were some API changes and perhaps you are running into it. The latest version actually ignored the URL path and tries to figure out what hostname to use based on your account.

– Alex Schroeder 2020-01-17 21:42 UTC


This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.