Differences between revisions 4 and 9 (spanning 5 versions)

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

In this section, we'll sign in as @kensanata@mastodon.weaponvsac.space. Replace username and Mastodon server when trying it.

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

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 another very long string. Copy and paste this string:

   1 14:44 <mastodon_oauth> Open this URL in your browser to authenticate: https://.......
   2 14:44 <mastodon_oauth> Respond to this message with the returned authorization token.
   3 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.weaponsvsac.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.

   1 14:58 <kensanata> save
   2 14:58 <root> Configuration saved

Everything else remains unimplemented.

Working on that.

-  ⇤ ← Revision 4 as of 2017-07-27 13:47:13 → 
  Size: 2413
  Editor: 212-51-157-29
  Comment: Fixed issue with long wait
+   ← Revision 9 as of 2017-08-01 21:23:27 → ⇥
  Size: 2405
  Editor: 212-51-157-29
  Comment: typos
-Deletions are marked like this.
+Additions are marked like this.
 Line 6:
+In this section, we'll sign in as `@kensanata@mastodon.weaponvsac.space`. Replace username and Mastodon server when trying it. :)
-Line 18:
+Line 20:
+}}}
-Line 19:
+Line 22:
-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:
+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 another very long string. Copy and paste this string:
-Line 22:
+Line 25:
-:44 <mastodon_oauth> Open this URL in your browser to authenticate:
 https://mastodon.weaponvsac.space/oauth/authorize?scope=read%20write%20follow&response_type=code&redirect_uri=urn:ietf:wg:oauth:2.0:oob&client_id=*************
+:44 <mastodon_oauth> Open this URL in your browser to authenticate: https://.......
-Line 40:
+Line 42:
-You should now have a channel called `#mastodon.weaponsvs.space@localhost` where all the status updates and notifications get shown.
+You should now have a channel called `#mastodon.weaponsvsac.space@localhost` where all the status updates and notifications get shown.