7.0.3

This is mostly a maintenance release fixing a number of bugs, but we also introduce support for the Iceshrimp fork of Misskey.

What's Changed

• Add support for Iceshrimp by @zotanmew in #88
• fix bug when failing to get user's posts by @YoannMa in #75
• remove redundant code for retrying on HTTP 429 by @ToadKing in #71
• examples/k8s-cronjob.yaml: fix job naming by @lhoBas in #80
• Build docker image for arm64 as well by @himynameisjonas in #90
• Update some actions to use Node 20, now that Node 16 is deprecated by @nanos in #94. Thanks @lnlyssg for your help!

New Contributors

• @YoannMa made their first contribution in #75
• @lhoBas made their first contribution in #80
• @zotanmew made their first contribution in #88
• @himynameisjonas made their first contribution in #90

Update instructions

If you are running from Git Hub Actions

1. Update your fork

If you are running locally

1. Update your code
2. Update your requirements: pip install -r requirements.txt

7.0.2

This is mostly a maintenance release fixing a number of bugs, but we also introduce support for the Iceshrimp fork of Misskey.

What's Changed

• Add support for Iceshrimp by @zotanmew in #88
• fix bug when failing to get user's posts by @YoannMa in #75
• remove redundant code for retrying on HTTP 429 by @ToadKing in #71
• examples/k8s-cronjob.yaml: fix job naming by @lhoBas in #80
• Build docker image for arm64 as well by @himynameisjonas in #90
• Update some actions to use Node 20, now that Node 16 is deprecated by @nanos in #94. Thanks @lnlyssg for your help!

New Contributors

• @YoannMa made their first contribution in #75
• @lhoBas made their first contribution in #80
• @zotanmew made their first contribution in #88
• @himynameisjonas made their first contribution in #90

Update instructions

If you are running from Git Hub Actions

1. Update your fork

If you are running locally

1. Update your code
2. Update your requirements: pip install -r requirements.txt

v7.0.1

This is a bug fix release

• fixes Docker container won't run: Bad git executable #70

v7.0.0

What's Changed

• New: FediFetcher now supports Misskey, Firefish (Calckey), and Foundkey server, thanks to @ToadKing 's hard work!
• fix: handle zero notifications by @Teqed in #61
• New: FediFetcher will print it's version number on start up (#58)
• Changed: FediFetcher now uses the .well-known/nodeinfo to determine which software a given server is running. Thanks @ToadKing again for your contribution!

Update instructions

If you are running from Git Hub Actions

1. Update your fork

If you are running locally

1. Update your code
2. Update your requirements: pip install -r requirements.txt

v7.0.0

What's Changed

• New: FediFetcher now supports Misskey, Firefish (Calckey), and Foundkey server, thanks to @ToadKing 's hard work!
• fix: handle zero notifications by @Teqed in #61
• New: FediFetcher will print it's version number on start up (#58)
• Changed: FediFetcher now uses the .well-known/nodeinfo to determine which software a given server is running. Thanks @ToadKing again for your contribution!

Update instructions

If you are running from Git Hub Actions

1. Update your fork

If you are running locally

1. Update your code
2. Update your requirements: pip install -r requirements.txt

v6.0.0

Change log

• Adds Support for Lemmy thanks to @Teqed's hard work (#56)
• Fixes #44

Update instructions

If you are running from Git Hub Actions

1. Update your fork
2. If you haven't updated to v5.x, please refer to the release notes for v5.0.0

If you are running locally

1. Update your code
2. If you haven't updated to v5.x, please refer to the release notes for v5.0.0

v5.0.1

Change log

• Fixes #52

Update instructions

If you are running from Git Hub Actions

1. Update your fork
2. Refer to the release notes for v5.0.0

If you are running locally

No update needed, but please refer to the release notes for v5.0.0

v5.0.0

Change log

• Configuration has been simplified and unified into a json file for GitHub Actions and local execution. This is a breaking change for users of GitHub Actions (#49, #51)
• Accept incorrect provision of server url instead of server host (9edbee7)

Sample config file

{
  "access-token": "Your access token",
  "server": "your.mastodon.server",
  "home-timeline-length": 200,
  "max-followings": 80,
  "from-notifications": 1
}

Warning
Do NOT include your access-token in the config.json when running FediFetcher as GitHub Action. When running FediFetcher as GitHub Action ALWAYS set the Access Token as an Action Secret!

Update instructions

If you are running from Git Hub Actions

No update is needed immediately, but if and when you want to update your fork (e.g. to make use of any new configuration options introduced in the future, or to incorporate bug fixes), you will need to switch to the new, json based configuration.

If you wish to switch to the new json file based configuration:

1. Update your fork
2. Create a config.json file in the repository root, and provide the desired configuration options.

Note
The option previously known as MASTODON_SERVER is now server. All other configuration option names are unchanged.

Warning
Do NOT include your access-token in the config.json when running FediFetcher as GitHub Action.

If you are running locally

Switching to the new json file based configuration is and will continue to be optional. You will continue to be able to use command line flags for both new and existing configuration options.

If you wish to switch to the new json file based configuration:

1. Update your fork
2. Create a config.json file (e.g in the ./artifacts directory, and provide your configuration options in there
3. Call your script with the --config=./artifacts/config.json directive instead of the existing command line flags.

v4.3.0

Change log

This release introduces the --config option, which allows passing configuration options in a JSON file, rather than as command line flags. This is both to improve security (#48) and to make configuration a bit saner.

If you want to use this, you can create a JSON file containing your configuration options. E.g.

{
  "server": "mstdn.thms.uk",
  "access-token": "{token}",
  "home-timeline-length": 200,
  "max-followings": 80,
  "from-notifications": 1
}

Then run FediFetcher with the --config flag supplied:

python find_posts.py --config=path/to/config.json

Update instructions

If you are running from Git Hub Actions

• No update needed, as this doesn't apply to GitHub Actions

If you are running locally

• If you wish to use the new config option, pull the latest version of the code, and create a JSON file with your configuration options.

v4.2.2

Change log

• Fixes a bug in how callback URLs are provided to GitHub Actions (#46)

Update instructions

If you are running from Git Hub Actions

• Update your fork

If you are running locally

• No update needed.

v4.2.1

Change log

• FediFetcher can now fetch context (replies) to favourites (#42)

New configuration options

The following new configuration option is available with this release:

Environment Variable Name	Command line flag	Notes
MAX_FAVOURITES	--max-favourites	Provide to fetch remote replies to any posts you have favourited. Determines how many of your favourites you want to get replies to. Recommended value: 40. Requires an access token with read:favourites scope.

Update instructions

If you are running from Git Hub Actions

• Update your fork, and provide MAX_FAVOURITES if desired.

If you are running locally

• Get the latest copy of find_posts.py, and supply --max-favourites, if desired.