v4.1.0

Change log

New features

• This release adds the functionality to backfill profiles for your pending follow requests (#7)

Fixes

• Fixes a bug when handling rate limits (#15 - thanks @nikdoof)

Update instructions

If you are running from Git Hub Actions

• Unless you wish to make use of the option to backfill profiles of pending follow requests, no action is required on your side, as the Action will always use the latest release.
• If you do wish to make use of the option to backfill profiles of pending follow requests:
  • Update your fork of the repository.
  • Add the read:follows scope to your access token, regenerate the token, and update the ACCESS_TOKEN Action Secret.
  • Provide the MAX_FOLLOW_REQUESTS environment variable.

If you are running locally

• Get the latest copy of find_posts.py
• If you wish to make use of the option to backfill profiles of pending follow requests, you must add the read:follows scope to your access token, regenerate the token, and supply it, together with the new --max-follow-requests flag

v4.0.4

You can now configure the HTTP timeout for any requests to mastodon APIs, using the HTTP_TIMEOUT variable, or the --http-timeout argument.

v4.0.3

You can now configure the HTTP timeout for any requests to mastodon APIs, using the HTTP_TIMEOUT variable, or the --http-timeout argument.

v4.0.2

Thanks to @nikdoof, this script is also available in a pre-packaged container, mastodon_get_replies. 🎉

1. Pull the container from ghcr.io, using Docker or your container tool of choice: docker pull ghcr.io/nanos/mastodon_get_replies:latest
2. Run the container, passing the command line arguments like running the script directly: docker run -it ghcr.io/nanos/mastodon_get_replies:latest --access-token=<TOKEN> --server=<SERVER>

The same rules for running this as a cron job apply to running the container, don't overlap any executions.

An example Kubernetes CronJob for running the container is included in the examples folder.

v4.0.1

bugfix release

v4.0.0

This release doesn't bring any new features.

It simply changes how configuration options are defined, to make future features easier to implement.

v3.0.2

Fixes two issues:

• Extremely large gaps during rate limit timeout / incorrect handling of time zones #8
• Workflow failing with “IndexError: list index out of range” #9

Users of GitHub actions don’t need to do anything, as changes are applied automatically.

For users who run the script manually, please fetch a new copy of get_context.py

v3.0.1

In this version you can also backfill your most recent followers' posts.

To enable this firstly update your fork to v3.0.1, then provide the following two variables at Settings > Environments > Mastodon:

• MAX_FOLLOWERS: An integer number representing how many of your last followers you want to backfill. (e.g. 80). Leave blank to disable this part of the script.
• USER (if not already provided): The username of the user whose followings you want to pull in (e.g. Michael for the user @michael@thms.uk). Leave blank to disable this part of the script.

For full details see the blog post: Pull missing posts from recently followed accounts into Mastodon

v3.0.0

Allow backfilling of followings. To make use of this:

1. Update your fork - You must have v3.0.0 or later.
2. Provide two additional environment variables:
   • USER This is the user whose most recently followed accounts you wish to backfill. You should only supply the 'local' part of their name. So, if their full name is @michael@thms.uk, simply supply michael.
   • MAX_FOLLOWINGS How many of their most recently followed accounts do you wish to backfill? Provide an integer greater than 0. I suggest a value no greater than 80, to avoid pagination.

For full details see the blog post: Pull missing posts from recently followed accounts into Mastodon

v2.0.3

Better identification in User Agent