Closed reorx closed 1 year ago
Base: 100.00% // Head: 99.59% // Decreases project coverage by -0.40%
:warning:
Coverage data is based on head (
887794a
) compared to base (64e2651
). Patch coverage: 25.00% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Looks great! Makes total sense to filter them if you're mirroring into a personal account in which you also post from other apps (or frontends).
I've looked into Misskey's API but unfortunately it seems they don't expose that info (or I haven't found the way to get it yet), so this would only work for Pleroma and Mastodon.
I'll merge it into the develop branch so I can add some coverage tests and documentation for this. Thank you for your contribution!
This config is used for finding the latest status that is created specifically by this bot, to avoid getting the wrong date if there are new statuses posted from other appliations like Pleroma FE.
If this config is not set, the behavior will be the same as before this commit; If set, when the user post new statuses manually through the Pleroma FE interface after last pleroma-bot run, these statuses will be excluded in get_date_last_pleroma_post(), making the returned date exactly the same as the last synced tweet.