-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List exports might not include all accounts in the list #1
Comments
Ignore errors indicating that an account is already in a list
It turns out that information from this API call is eventually accurate, it's just delayed. This seems to be a caching problem somewhere. Investigating further with the infosec.exchange instance administrator. |
The issue occurs immediately after adding an account to a list, even if the list accounts API call hasn't been made recently, so it's not an issue of the API results being cached, but of a long delay in the accuracy of the data provided by the API call. |
Mastodon bug reported here mastodon/mastodon#22828 |
Disregard. I forgot to paginate |
I used
listmanager.py
to export the list of accounts followed byMeidasTouch@mstdn.social
(meidasTouch@mstdn.social.csv). When I used the same script to import that list into myUS politics
list, API errors were returned for 12 of the 50 accounts.Further investigation revealed that these accounts appeared in the list web UI after a previous run, but for some reason are not listed in the
list_accounts
API call, so the script thinks those accounts need to be added to the list. This results in the API errors, because the accounts ate already in the list.I will open an issue on the Mastodon project, and use this issue for reference.
The text was updated successfully, but these errors were encountered: