|
Size: 2920
Comment: Describing the current situation
|
Size: 2413
Comment: Fixed issue with long wait
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| !BitlBee has native support for Mastodon in the works. You can take a look at this [[https://github.com/kensanata/bitlbee|fork] with its [[https://github.com/kensanata/bitlbee/blob/master/protocols/mastodon/TODO.md|TODO]] list. | !BitlBee has native support for Mastodon in the works. You can take a look at this [[https://github.com/kensanata/bitlbee|fork]] with its [[https://github.com/kensanata/bitlbee/blob/master/protocols/mastodon/TODO.md|TODO]] list. |
| Line 14: | Line 14: |
| }}} Sadly, you currently cannot set username and base URL in one go, and you need to specify the complete URL including API version. {{{#!irc |
|
| Line 21: | Line 16: |
| 14:44 <root> mastodon2 - Logging in: Registering client, please try again in a second | |
| Line 23: | Line 17: |
| }}} This is unfortunate, so for now you need to abort your login and try again: {{{#!irc 14:44 <kensanata> account mastodon2 off 14:44 <root> mastodon2 - Logging in: Signing off.. 14:44 <kensanata> account mastodon2 on 14:44 <root> mastodon2 - Logging in: Login |
|
| Line 33: | Line 18: |
| 14:44 <root> mastodon2 - Logging in: Requesting OAuth access token }}} |
|
| Line 39: | Line 22: |
| <mastodon_oauth> Open this URL in your browser to authenticate: | 14:44 <mastodon_oauth> Open this URL in your browser to authenticate: |
| Line 48: | Line 31: |
| 14:44 <root> mastodon2 - Logging in: Requesting OAuth access token |
Setting up a Mastodon account in BitlBee
BitlBee has native support for Mastodon in the works. You can take a look at this fork with its TODO list.
Connecting
To use your Mastodon account. In your &bitlbee channel:
1 14:43 <kensanata> account add mastodon @kensanata
2 14:43 <root> Account successfully added with tag mastodon2
3 14:43 <kensanata> account mastodon2 set base_url https://mastodon.weaponvsac.space/api/v1
4 14:43 <root> base_url = `https://mastodon.weaponvsac.space/api/v1'
5 14:44 <kensanata> account mastodon2 on
6 14:44 <root> mastodon2 - Logging in: Login
7 14:44 <root> mastodon2 - Logging in: Parsing application registration response
8 14:44 <root> mastodon2 - Logging in: Starting OAuth authentication
9
10 At this point, you'll get contacted by the user `mastodon_oauth` with a big URL that you need to visit using a browser. Authenticate the client and you'll get back a another very long string. Copy and paste this string:
11
12 {{{#!irc
13 14:44 <mastodon_oauth> Open this URL in your browser to authenticate:
14 https://mastodon.weaponvsac.space/oauth/authorize?scope=read%20write%20follow&response_type=code&redirect_uri=urn:ietf:wg:oauth:2.0:oob&client_id=*************
15 14:44 <mastodon_oauth> Respond to this message with the returned authorization token.
16 14:44 <kensanata> ****************************************************************
Once you do that, your login should complete in the &bitlbee channel:
1 14:44 <root> mastodon2 - Logging in: Requesting OAuth access token
2 14:44 <root> mastodon2 - Logging in: Connecting
3 14:44 *** mastodonweaponvsacspace_ JOIN
4 14:44 *** MODE +v mastodonweaponvsacspace_
5 14:44 <root> mastodon2 - Logging in: Verifying credentials
6 14:44 <root> mastodon2 - Logging in: Getting home timeline
7 14:44 <root> mastodon2 - Logging in: Logged in
You should now have a channel called #mastodon.weaponsvs.space@localhost where all the status updates and notifications get shown.
Mastodon gives BitlBee a permanent authentication token, which will be saved in your configuration.
You should probably save this configuration.
Everything else remains unimplemented.
Working on that. 