A key draw for downloading Bean was the “group” function - some subject areas have good representation on more than one instance and I wanted to easily collect them all in a single view.
At the moment it seems that the group function does allow this, but with one big caveat - posts are seen effectively grouped by community (so sorting by new doesn’t mean you see all of the new posts from all of the communities in the group, all in chronological order - you see some posts from the first community in the group, then some from the second, then some from the third and so on).
I’m working on improving the sorting so it mixes them a little better but at the moment that’s correct.
Say you have 3 communities in the group, I run 3 requests for posts for community 1, 2, and 3. These are individually sorted by the filter selected by the user (Hot, Active, New…) but not sorted as a group as the API doesn’t have any kind of grouping.
My WIP currently has me mixing them based on the published date which I think would make more sense but the problem there is it kills the “Hot” or “Active” sorting options.
I’m open to any suggestions on how this can be handled better.
That all makes sense; thank you for getting back to me.
The published date works for me and thats actually what I’m most interested in when grouping, at least for me!
I think I might add some options in when creating the group for sorting.