-
Notifications
You must be signed in to change notification settings - Fork 239
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
Implement more detailed UA #122
Comments
That's a great addition. Nice job. |
Is there any way to fedifetcher to keep track of previously queried/retrieved statuses? It seems to check for the same stuff over and over, even if the context has already been retrieved. Not sure if this causes a real bad impact or not on instances but if there's any way to make it less needlessly chatty seems like it would be preferable. |
Context may change (ie more replies added) so it’s expected to re-check context. But maybe we can do something to slow this down. I’ll think about this a bit more and open an issue for discussion |
This is because FediFetcher is apparently responsible for very high load on at least some instances, and this would allow some level of more granular blocking
The text was updated successfully, but these errors were encountered: