Skip to content

README.md

Latest commit

 

History

History
108 lines (84 loc) · 3.85 KB

README.md

File metadata and controls

108 lines (84 loc) · 3.85 KB

CrossPost

Post Mastodon Posts to Twitter and/or BlueSky easily!

CrossPost will allows you to create a simple poster from Mastodon->Twitter and/or Mastodon->BlueSky.

Instructions

To run CrossPost, you will need (Twitter and/or BlueSky) and Mastodon API keys.

Twitter

For Twitter you need a Twitter developer application. This can be done at https://developer.twitter.com. You will need to create a Project and assign an application to it. The Free tier for the project is completely fine.

You will need to generate an Access Token and Secret with Read and Write access. This can be done in the Application settings under User authentication settings by clicking Set up and making sure at least Read and Write is the authentication level.

Save the API Key and Secret and Access Token and Secret values.

Mastodon

This is pretty easy. You will need to log into the web interface of the instance you're on and go to your Profile preferences (by clicking Preferences).

Click on the Development tab on the bottom left. Create an application and make sure the read:accounts and read:statuses permissions are selected.

Save the Client key, Client secret and Your access token values.

BlueSky

BlueSky's API is pretty simple, you'll just need a username and password. It's recommended to not your your actual password, but create an App Password via Settings->App Passwords->Add App Password. This will prevent breakage if you change your password or enabled 2-factor (When BlueSky can do that finally) and can be revoked if needed.

Building

Building CrossPost requires running the build.sh binary in this directory. This will build and UPX pack (if upx is installed) the resulting binary. By default, if no arguments are specified, it will build it in the bin directory in the local crosspost directory. Specifying a path as the first argument will build and place the binary at the specified path.

Configuration

Copy a version of the Example Configuration below and fill in the values you got from the instructions above.

Now all you have to do is run it using the ./crosspost -f <config_file> (the "<config_file>" value should be replaced with the path to the config file you created).

Example Configuration

Here is an example configration that covers two separate accounts.

{
    "accounts": [
        {
            "mastodon": {
                "server": "https://<instance_url>",
                "client_id": "client_id_value",
                "client_secret": "client_secret_value",
                "access_token": "access_token_value"
            },
            "bluesky": {
                "username": "bluesky_email",
                "password": "bluesky_app_password"
            },
            "twitter": {
                "consumer_key": "consumer_key_value",
                "consumer_secret": "consumer_secret_value",
                "access_token": "access_token_value",
                "access_secret": "access_secret_value"
            }
        },
        {
            "mastodon": {
                "server": "https://<instance_url>",
                "client_id": "client_id_value",
                "client_secret": "client_secret_value",
                "access_token": "access_token_value"
            },
            "twitter": {
                "consumer_key": "consumer_key_value",
                "consumer_secret": "consumer_secret_value",
                "access_token": "access_token_value",
                "access_secret": "access_secret_value"
            },
            "prefix": "<prefix_short_url>/post/"
        }
    ]
}

The Mastodon section is required, but you can specify either Twitter, BlueSky or both if desired! At least one secondary account is required or the application will return an error on startup.

ko-fi