v4.1.6

Change log

• We can now backfill posts of users that are mentioned in notifications
• Added a sample bash script for a setting up a cron job for FediFetcher
• Provided a quick start / recommended configuration
• Deprecated the USER / --user option.
• Changed the logic with which FediFetcher decides which profiles to re-fill.

Please read the announcement post for more details: https://blog.thms.uk/2023/03/fedifetcher-backfills-notifications?utm_source=github

Full Changelog: v4.1.5...v4.1.6

Update instructions

If you are running from Git Hub Actions

• Update your fork
• If you wish to make use of the option to backfill posts of users that are mentioned in notifications:
  • Add the read:notifications scope to your token, and regenerated it, if needed
  • Add the FROM_NOTIFICATIONS environment variable. I suggest 1 as a starting point.
  • If you currently use MAX_FOLLOWERS or MAX_FOLLOW_REQUESTS I would suggest removing these, as FROM_NOTIFICATIONS should backfill new followers / follow requests, unless you have turned off notifications for these.

If you are running locally

• Get the latest copy of find_posts.py
• If you wish to make use of the option to backfill posts of users that are mentioned in notifications:
  • Add the read:notifications scope to your token, and regenerated it, if needed
  • Add the --from-notifications=1 as argument to your job.
  • If you currently use --max-followers or --max-follow-requests I would suggest removing these, as --from-notifications should backfill new followers / follow requests, unless you have turned off notifications for these.