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 »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Native sorting button blocks other sorting orders

Parent

Native sorting button blocks other sorting orders

+4
−0

The sorting buttons at the top of a category's post list include "Activity", "Age", and "Score", which are all orders into which to sort the posts. However, for sites with imported content they also include "Native". This is not a sort order, but a filter, showing only posts that were not imported. This sorts imported content to the end, to give a similar effect to filtering them out, without actually reducing the number of posts displayed.

The sorting buttons above the filters section

In addition to the confusion that can result from putting an apparent filter among the sorting buttons, this also prevents people from using the other sorting buttons with native posts. When "Native" is selected, the sort order is the default order. This cannot be changed to a different sort order without displaying imported content. If "Native" were instead a filter option, then a user who wishes to see only native posts would still be able to sort those posts using the other sorting buttons.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+3
−0

Now that we have filters, we should remove the native button and add a toggle for native (non-imported) posts to the filter options. As you point out, "native" is not, logically speaking, a sort but a binary property. (Edit: Apparently, as discussed in comments, it is implemented as a sort now, but the effect is just to move the imported posts to the bottom. That seems unhelpful.)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

I was wrong - it is a sort (but probably shouldn't be) (2 comments)
I was wrong - it is a sort (but probably shouldn't be)
trichoplax‭ wrote over 1 year ago

A discussion on Discord has made me realise I was wrong about this being a filter - instead of hiding the imported posts it just sorts them to the end, so it is a sort rather than a filter.

I still think it makes more sense as a filter now that we have filters, so it should probably be removed from the sort buttons once the filter exists. I just wanted to correct my mistake. I've also edited the question to reflect this.

Karl Knechtel‭ wrote over 1 year ago

It really shouldn't be a sort - that just makes no sense. "Native" for posts is a binary property. First off, you can really only partition by that, not properly sort. Second, someone who chooses this option is probably only interested in native posts - possibly interested only in imported posts, but certainly not both. Whereas when sorting e.g. by date there is no fixed cutoff that would mark what is interesting to the user.