In a UX-focused discussion titled ‘Suggestion for fixing the inaccurate link counter value,’ Richie pointed out that the topic link counter stops at 50, even when thousands of links exist, calling the displayed number misleading and suggesting it’s better to show no number than an inaccurate one. Sam asked if this was a pr-welcome issue, noting it seemed like a small, easy fix—perhaps displaying +50 or simply 50 if links exceed that. Lindsey agreed and added the pr-welcome tag. Arkshine quickly submitted a PR to fix it, which Richie praised. Anishlukk123 questioned whether consistency should be maintained by showing full numbers for all metrics (like views and likes), suggesting either adding a + or showing the full count. Arkshine clarified that approved PRs aren’t always merged immediately due to low priority or pending discussions. Pmusaraj later confirmed the PR was merged, and Richie thanked everyone, especially Arkshine, for resolving the issue. The fix was successfully implemented, addressing the UX concern of misleading data display.
Further to what I thought was a bug but is seemingly by design, the topic link counter stops at 50:
Even if there are thousands of links in the topic 
And:
With this in mind, rather than showing an inaccurate number to the end user could we simply display a + symbol if there are more than 50 links in a topic?
For example, this:
Would simply become 50+ like so:
This way the user is not being told inaccurate information 
@lindsey do you feel this is pr-welcome? Seems like a small and easy change (we would over select by 1 and then use that information to decide if we render 50 or 50+)
Agreed, added a pr-welcome to add the + for accuracy.
Thanks @lindsey 
I gave it a try:
Wow, that was quick!
Thanks @Arkshine 
Hey, I have a question: From what I have seen, all the other components, like views and likes, have the full number. For the sake of design consistency, we should either add the plus to the other cases or add the full number to the link count.
Is there a process for getting this PR merged @Arkshine ?
An approved PR is not necessarily merged immediately. There might be some internal concern or discussion about it. Since it’s low priority, let’s wait!
Ok, thanks, just wasn’t sure what the process was 
It is merged now, thanks @Arkshine
Thanks again for working on this one @Arkshine 
