Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

80%
+6 −0
Meta Leaderboards are live

You might have noticed that challenges now show a leaderboard in addition to the table of contents. This is something this community has wanted for a while, and now, thanks to user contributions a...

4 answers  ·  posted 3y ago by Monica Cellio‭  ·  last activity 3y ago by user‭

Question discussion
#2: Post edited by user avatar Moshi‭ · 2021-06-28T22:56:47Z (over 3 years ago)
Capitalization
  • leaderboards are live
  • Leaderboards are live
You might have noticed that challenges now show a leaderboard in addition to the table of contents.  This is something this community has wanted for a while, and now, thanks to user contributions and a lot of chatting in Discord, it's live.  See [this blog post](https://meta.codidact.com/posts/282420), which I meant to link here more promptly (sorry!).

> The table of contents sorts answers by voting, but golfers wanted a leaderboard that sorts challenge responses by *code size*.  And because it's not really fair for answers in different languages, some verbose and some designed for golfing, to compete head to head, the community also needed a way to show the languages in this leaderboard.  While a userscript can solve the problem for those in the know, we and the community wanted this to be readily available to all.
> 
> Enter one of our users, [Moshi](https://codegolf.codidact.com/users/53196), who made this for the community (no userscripts required):
> 
> ![sorted by size](https://meta.codidact.com/uploads/JoMXU4Q6C8WFafZuqG7SHhW9)
> 
> Or, grouped by language to give folks using Java, C, and others a shot:
> 
> ![sorted by language](https://meta.codidact.com/uploads/LAEWKcfbeg2ukacNFpRkwyrw)

We're aware of a bug on mobile; it's fixed and awaiting deployment.

If you see anything that's not quite right, please let us know.
#1: Initial revision by user avatar Monica Cellio‭ · 2021-06-28T22:48:39Z (over 3 years ago)
leaderboards are live
You might have noticed that challenges now show a leaderboard in addition to the table of contents.  This is something this community has wanted for a while, and now, thanks to user contributions and a lot of chatting in Discord, it's live.  See [this blog post](https://meta.codidact.com/posts/282420), which I meant to link here more promptly (sorry!).

> The table of contents sorts answers by voting, but golfers wanted a leaderboard that sorts challenge responses by *code size*.  And because it's not really fair for answers in different languages, some verbose and some designed for golfing, to compete head to head, the community also needed a way to show the languages in this leaderboard.  While a userscript can solve the problem for those in the know, we and the community wanted this to be readily available to all.
> 
> Enter one of our users, [Moshi](https://codegolf.codidact.com/users/53196), who made this for the community (no userscripts required):
> 
> ![sorted by size](https://meta.codidact.com/uploads/JoMXU4Q6C8WFafZuqG7SHhW9)
> 
> Or, grouped by language to give folks using Java, C, and others a shot:
> 
> ![sorted by language](https://meta.codidact.com/uploads/LAEWKcfbeg2ukacNFpRkwyrw)

We're aware of a bug on mobile; it's fixed and awaiting deployment.

If you see anything that's not quite right, please let us know.