-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Improve federated avatars DNS lookups #1287
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
Labels
Comments
7 tasks
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
techknowlogick
pushed a commit
that referenced
this issue
Sep 6, 2019
* feat: highlight issue references with : e.g. #1287: my commit msg e.g. ABC-1234: my commit msg * ref: update model regex to consistent with issueNumericPattern * test: check highlight issue with : in commits messages
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Oct 6, 2019
* feat: highlight issue references with : e.g. go-gitea#1287: my commit msg e.g. ABC-1234: my commit msg * ref: update model regex to consistent with issueNumericPattern * test: check highlight issue with : in commits messages
techknowlogick
pushed a commit
that referenced
this issue
Oct 7, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment enabling FEDERATED_AVATARS results in some delays whenever the server has to provide the URL to the avatar of users whose federated avatar url is not found in the ad-hoc cache (which has 1 day of lifetime).
While this may not be a big deal in a page with a single user, explore/users page can show many users and if these have emails with many different domains the delay sums up until browser possibly times out.
The situation may be improved in various ways:
In any case it would be useful to document the problem with the setting that enables these.
The text was updated successfully, but these errors were encountered: