43

Per-site metas lists some badges that are impossible to get. For example https://tex.meta.stackexchange.com/badges lists:

But these are impossibly to get because per-site metas do not support bounties, were not in a beta stage or Area 51 proposals. I therefore suggest that these badges are removed from the per-site metas. They have no function and they are confusing.

There are already badges that are unavailable on per-site metas but available on the main sites:

This seems to suggest that per-site metas should only contain badges that can be possibly awarded.

Improve this question
2

3 Answers 3

Reset to default
17

I'd think that removing them would be even more confusing. Meta sites are where you go to learn about a Stack Exchange site. As such, I think we want all the badges listed there. The fact that some of the badges can't be awarded on the Meta site is irrelevant. (There's one badge that can't be awarded on Stack Overflow, but it's still listed just for the sake of having a complete list.)

Maybe instead we could add an asterisk (linking to a note at the bottom of the page) to those badges that aren't awarded on a site or its Meta?

Improve this answer
7
  • 1
    which badge is that?
    – ertert3terte
    May 31, 2012 at 23:34
  • 2
    @ShmuelBrin The Precognitive badge can't be awarded on SO.
    – Bill the Lizard
    Jun 1, 2012 at 0:40
  • 14
    Why aren't there Quorum and Convention badges on per-site metas then?
    – doncherry
    Jun 3, 2012 at 22:21
  • 2
    @doncherry Good question! That does seem to be inconsistent.
    – Bill the Lizard
    Jun 4, 2012 at 0:48
  • 3
    @doncherry Neither are the new election participation badges, Caucus and Constituent, on the per-site metas. I think the inconsistency should be fixed by removing all the impossible badges from per-site metas (rather than adding some impossible badges that are not there) and have updated my question accordingly.
    – N.N.
    Jul 10, 2012 at 6:49
  • 3
    @N.N.: Or by adding the missing badges.
    – Martijn Pieters
    Jul 21, 2014 at 20:04
  • 1
    @MartijnPieters Or adding a notice by the end of the list: You are viewing the META.MySite badges. Didn't you intend to see the MySite badges [with link] -- or something in that sense.
    – yo'
    Jul 27, 2014 at 16:50
16
+150

We recently had a question over on User Experience which is related to what is asked here. The accepted answer to the question Show not implemented functions to tease user states:

Quite simply don't do this. False expectations are the biggest source of a disappointing experience. It commits you to features that you may not be able/want to produce, users will assume very short timescales for this functionality to be in action, and it also highlights your apps weaknesses leading users to look for these elsewhere with your competitors.

If you absolutely have to add teasers, make sure that it is clear at the beginning of the path that the feature is not implemented. There is nothing more annoying than putting in some effort to start a process only to have the rug pulled out from under you.

Don't have features that aren't implemented. It confuses users and creates false expectations. Hide what isn't there.

Improve this answer
2
  • @VotetoClose Vote buttons could be better implemented, but the damage is less there, than on badges.
    – Benny Skogberg
    Jul 21, 2014 at 20:59
  • @BennySkogberg Moreover, the voting is implemented, and by clicking on the vote button, the low-rep user learns how SE works (i.e., high-rep users can moderate the site), which is fine.
    – yo'
    Jul 27, 2014 at 16:52
11

I think it's terrible user-experience to show all those badges which are impossible to earn on the meta sites.

To see which badges you haven't got yet, you have to do extra work by going through ones which you can't even earn on the meta sites.

Please remove those completely from the badge pages on the metas.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .