[Suggestion / Idea] Make it clear to the user why upvoting on a per-project setting does not work

[rubyFeedback]

Select Topic Area

General

Body

I've recently realised that the github ladybird project disregards my attempts to upvote on suggestions. I noticed others could upvote though.

So what is the problem here? The issue is as follows:

I click on an upvote; but it instantly removes my upvote. I get no explanation or notification as to why my vote is not counted. Others can upvote though.

This is different to other projects on github, so I assume there may be a anti-user setting against me from the ladybird team - but I can only speculate, because I get no explanation about it. So I have to assume things, and perhaps my assumptions are incorrect.

I would thus like to propose that github makes it more clear why my attempt to upvote some suggestions are nullified. If it is a setting on a per-project basis then it could be "You are unable to upvote because of xyz." Right now I get no explanation, which is very strange. How are users supposed to find out what the issue is if a project does not communicate it?

TL;DR: So my issue is not that per-projects can disable upvotes, but that some people can upvote, others can not; and for those who can not, no explanation at all is given. This leads to confusion and people having to make guesses as to why this is the case. The UI should make it more clear as to the cause of this not being possible, whereas it is possible in other projects.

[Talha-Dogan]

Hi there! 👋

That sounds very frustrating. Silent failures in the UI are definitely confusing.

Since the upvote is reverting instantly, the backend is likely rejecting the request, but the frontend isn't displaying a toast message for the error.

To find out exactly why this is happening:

1. Right-click on the page and select Inspect (or press F12).
2. Go to the Network tab.
3. Click the upvote button again.
4. Look for the request that appears in the list (it will likely be red).

If you see a 403 Forbidden or 422 Unprocessable Entity status code, it confirms that there is likely an Interaction Limit set up by the repository maintainers (limiting interaction to established users only) or a specific restriction, rather than a bug.

I agree with your suggestion—the UI should definitely communicate why the action failed instead of just resetting the button.

[alialkhtri3-png]

Goood