sleepy/forgejo

Fork 0

problem: teams page may load too many avatars for large organizations #12448

New issue

Open

opened 2026-05-07 10:20:23 +02:00 by wetneb · 1 comment

wetneb commented

2026-05-07 10:20:23 +02:00

(Migrated from codeberg.org)

Does your problem still exist on the latest Forgejo version?

Yes, the problem still exists (tested on a next instance)

About your usage of Forgejo

Codeberg and third-party instances

Problem description

The page listing all teams of an organization includes the avatars of all members of each visible team.
For instance at https://codeberg.org/org/forgejo/teams :

This also means that my browser will make many requests to fetch each avatar, leading to high bandwidth usage. In the case of Codeberg, I also get blocked (HTTP 429) for making too many requests because of that.

If you are a Codeberg-e.V. member and want to try that, you can go to:

# Watch out, visiting this might temporarily block you!
https://codeberg.org/org/Codeberg-e.V./teams

Potential workarounds

The way GitHub lists contributors to a repository could be an inspiration:

Unfortunately that may require sorting the team members in some sort of a meaningful order so that the ones that get displayed by default aren't completely arbitrary.

Forgejo Version

15.0.1-4-80476238ab

Other details about your environment (software names and versions)

Irrelevant

Solutions

Accepted solutions to address this problem will go here

### Does your problem still exist on the latest Forgejo version? Yes, the problem still exists (tested on a next instance) ### About your usage of Forgejo Codeberg and third-party instances ### Problem description The page listing all teams of an organization includes the avatars of all members of each visible team. For instance at https://codeberg.org/org/forgejo/teams : ![image](/attachments/c7144a81-399b-4a35-9590-bf6f301bf04c) This also means that my browser will make many requests to fetch each avatar, leading to high bandwidth usage. In the case of Codeberg, I also get blocked (HTTP 429) for making too many requests because of that. If you are a Codeberg-e.V. member and want to try that, you can go to: ``` # Watch out, visiting this might temporarily block you! https://codeberg.org/org/Codeberg-e.V./teams ``` ### Potential workarounds [The way GitHub lists contributors to a repository](https://github.com/OpenRefine/OpenRefine) could be an inspiration: ![image](/attachments/992fce57-aada-4aca-8338-72be48c7870e) Unfortunately that may require sorting the team members in some sort of a meaningful order so that the ones that get displayed by default aren't completely arbitrary. ### Forgejo Version 15.0.1-4-80476238ab ### Other details about your environment (software names and versions) Irrelevant ### Solutions *Accepted solutions to address this problem will go here*

mahlzahn commented

2026-05-07 17:46:30 +02:00

(Migrated from codeberg.org)

@wetneb wrote in https://codeberg.org/forgejo/forgejo/issues/12448#issue-4902041:

If you are a Codeberg-e.V. member and want to try that, you can go to:
# Watch out, visiting this might temporarily block you!
https://codeberg.org/org/Codeberg-e.V./teams 

It’s beautiful :) But, yes, shouldn’t be like this.

@wetneb wrote in https://codeberg.org/forgejo/forgejo/issues/12448#issue-4902041:

The way GitHub lists contributors to a repository could be an inspiration:
Unfortunately that may require sorting the team members in some sort of a meaningful order so that the ones that get displayed by default aren't completely arbitrary.

Indeed. I think it would be nice to pick n random members for each team.

@wetneb wrote in https://codeberg.org/forgejo/forgejo/issues/12448#issue-4902041: > If you are a Codeberg-e.V. member and want to try that, you can go to: > > ```text > # Watch out, visiting this might temporarily block you! > https://codeberg.org/org/Codeberg-e.V./teams > ``` It’s beautiful :) But, yes, shouldn’t be like this. @wetneb wrote in https://codeberg.org/forgejo/forgejo/issues/12448#issue-4902041: > [The way GitHub lists contributors to a repository](https://github.com/OpenRefine/OpenRefine) could be an inspiration: > Unfortunately that may require sorting the team members in some sort of a meaningful order so that the ones that get displayed by default aren't completely arbitrary. Indeed. I think it would be nice to pick $n$ random members for each team.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sleepy/forgejo#12448

No description provided.

Rows
Columns