Inconsistencies and UI issues on profile.wordpress.org social icons

[kimjiwoon]

Hi Meta team,

I've noticed a couple of minor but visually important inconsistencies on the [WordPress.org profile page](​https://profiles.wordpress.org/kimjiwoon/).

1. Social Icons Display Issue

• The GitHub profile is shown twice—once as text (GitHub: Jiwoon-Kim) and again as a social icon below (Find me on:). → This feels redundant and might benefit from better deduplication logic.
• The Threads.net account is present but the icon appears invisible or transparent, making it look like a UI bug.
• Are these icons being rendered conditionally via some external source or local logic?

2. Social Metadata Source

• It seems like some parts of the profile (like find me on) are not user-editable. → Are these being pulled from the Gravatar API or another system (e.g. BuddyPress)? It would be helpful to clarify the data source and if users have any way to manage or override it directly.

Would appreciate if these issues could be reviewed for better consistency and usability across the network.

Thanks a lot for your amazing work!

[tobifjellner]

The first Github link reflects the contributor profile integration against Github.
The list of social links is pulled from the corresponding Gravatar account.

The Meta team could probably add some logic, like "IF there is a main Github account linked then skip any Github account from the Gravatar profile

There should probably be some kind of default icon for social links on "unknown" platforms.

[dd32]

Missing Icons: #6682

The GitHub profile is shown twice

I'm not inclined to fix this, seems fine to me.

It seems like some parts of the profile (like find me on) are not user-editable.

These are pulled from the Gravatar account, the top of the Edit Profile account has this message in a yellow callout:

Your avatar and social media accounts are automatically pulled from the Gravatar profile associated with {{EMAIL}}.

Out of the issues listed here, only the missing icons feels like something worthy of fixing, so I'm going to close this as a duplicate of #6682.